Technology
.png)
Innovative, reliable, and flexible software solutions for portfolio management and trust operations delivered with exceptional and personal client service.
info@hwainternational.com
+800-328-8661
Privacy Policy
If you run a trust department inside a community bank, the accounting system underneath it is one of the most consequential purchases your bank will make — and one of the least frequent. Most departments choose a platform once every fifteen or twenty years. The system will outlast several careers, produce every statement your clients read, and generate the reports your examiners open first. The economics of the whole department ride on it.
This guide is what we’d tell a friend who asked how to run that decision well. We’ve been building trust accounting software for community banks since 1977, so we have a horse in this race — but the advice below holds no matter whose demo you sit through. We’ll tell you where we fit at the end, and keep the rest vendor-neutral.
Before anyone shows you a screen, write down how your department works today. Two banks with identical assets under management can need very different systems, and the differences hide in the operational details.
The inventory worth doing: how many accounts you administer and of what types (personal trusts, agencies, IRAs, estates); how your assets are held — omnibus custody at the bank, or individually registered accounts at brokerage firms — because that single fact determines how reconciliation works and who produces the 1099s; how many people touch trust operations and what each actually does; what your last two exams flagged; and what the system must connect to — your core banking system for ACH movements, your custodians and brokers for data feeds, your tax vendor, your statement expectations.
That one-page inventory does two jobs. It turns vendor demos from tours into auditions, and it becomes the first page of your conversion plan later.
Feature lists in this industry run long and read alike. For a community bank trust department, seven capabilities do most of the separating.
1. Examiner-ready reporting, out of the box. Your system should produce the fiduciary detail behind the RC-T call report schedule, support your Regulation 9 administrative reviews, handle Regulation R fee reporting, and keep audit logs an examiner can follow. Ask every vendor to show these reports from a live system — not a slide about them.
2. Reconciliation that matches your custody model. If your bank holds assets in omnibus custody, you need daily cash and asset reconciliation tools built for that structure, with automated feeds. If your accounts are individually registered at brokerage firms, you need electronic position and tax-lot reconciliation against daily broker data — which also lets you use broker-provided prices instead of paying a third-party pricing service.
3. The full tax cycle. A complete 1099 suite with electronic filing, required minimum distribution calculations, and tax worksheets. If you custody IRAs, the 1099-R and 5498cycle should be native, not an add-on workaround.
4. Statements your clients will actually accept. Statements are the only part of the system your clients ever see. Look for real configurability — layout, content, your logo — and delivery options that include an online portal, because a growing share of beneficiaries expects one.
5. Fee administration that doesn’t leak. Fee schedules set up once, calculated automatically, reported monthly, charged without a spreadsheet in the middle. Manual fee processes quietly cost trust departments real revenue every year.
6. A modern surface for daily work. Your staff spend their day in workflow — account reviews, onboarding, approvals for discretionary distributions, relationship notes — not in the ledger itself. A browser-based front-office layer for that daily work matters more to your team’s Tuesday than what the accounting engine’s screens look like.
7. Continuity when people leave. This is the capability nobody demos and everybody eventually needs. How does the vendor train new staff? How reachable is support, and how senior are the people answering? And the biggest question: if you lose your operations lead, can the vendor run your operations — for a season or permanently? A system should survive your org chart.
Two quotes can look similar on year one and diverge wildly by year five, because trust accounting vendors price on three different bases: per software user, per account administered, or as a percentage of assets under management.
The basis matters more than the sticker. AUM-based pricing means your software bill rises when the market rises— even though your workload didn’t. Per-account pricing tracks your actual volume of work. Per-user pricing tracks the size of your team. None of these is dishonest, but you should know which lever your bill is tied to, and whether that lever is one you control.
Then look at the term. Annual agreements buy flexibility; multi-year agreements should buy something in return — typically a locked price and included updates. Ask what is and isn’t covered across the term: releases, support tiers, year-end updates, new modules.
Finally, compare three-year totals, not license fees. Have every vendor quote the same scenario — your user count, your account count, the modules you’ll actually license — including conversion, training, and ongoing maintenance. And ask directly: what triggers a price increase mid-term?
Every trust officer has heard a conversion horror story, and the fear is legitimate — fiduciary data is unforgiving. But “conversion is disruptive” usually describes do-it-yourself conversions. The variable you control is how much of the work the vendor performs.
A well-run conversion looks like this: the vendor’s team does the data mapping, not yours. There’s a defined parallel or trial period before cutover. Newly converted accounts get audited weekly for the first stretch. You have a named conversion lead you can call. And the timeline is stated honestly — for most community bank departments, somewhere between 90 and 180 days from planning to steady state.
When you call references, don’t ask whether they like the software. Ask what their conversion was like, what surprised them, and what they’d do differently. And weigh the status quo honestly too: staying put has costs — manual workarounds, key-person risk, exam exposure — that just don’t arrive as an invoice.
There’s a choice worth evaluating alongside your software bids, not after them: outsourced trust operations, where the vendor’s team runs your daily back office — posting, reconciliation, fee administration, statements, tax reporting — on their platform, while your bank keeps the fiduciary decisions and the client relationships.
It fits three situations especially well: departments of one to three people, banks staring at a retirement cliff, and institutions that want to stay in the trust business without staying in the trust-operations business. Pricing is typically scoped to your volumes and the services you hand over, which means a small department pays like a small department. If continuity was the reason you started shopping, ask every vendor whether this option exists — the answer tells you a lot about their bench.
• How many of your clients look like us — our size, our custody model? Can we call two of them?
• Who performs the conversion, and what does the plan look like, week by week?
• What’s the pricing basis — users, accounts, or AUM — and what’s our all-in three-year total?
• What triggers a price increase mid-term?
• Show us the RC-T supporting detail and Reg 9review outputs from a live system.
• Which custodian and broker feeds are running today for clients like us?
• Who answers support calls — and how long have they been doing this work?
• What’s not included that clients commonly add later?
• If we lose our operations lead, can you run our operations — temporarily or permanently?
• How long do your clients stay?
Here’s our horse, plainly. HWA International has built trust accounting for community banks since 1977 — our first client was a community bank in Monroe, Wisconsin — and banks remain the largest share of our client family today. TNET runs on three platforms: BackOffice for the accounting, a browser-based FrontOffice for the daily work —Reg 9 and administrative reviews, onboarding, approvals, CRM — and the TNETonline portal for your clients.
You can engage two ways. Technology-only, on a three-year Subscription (priced per software user) or Usage (priced per account) basis — TNET pricing is never tied to your assets under management. Or TNET Trust Services, where our team runs your back office end to end, priced to your volumes and the services you hand over. One in five of our clients has been with us for more than 25 years, which is the statistic we’re proudest of and the one we’d encourage you to demand from anyone you evaluate — including us.
If it would help to talk through your department — your custody model, your staffing picture, your last exam —we’re glad to do that in twenty minutes, no pitch deck required.
What does trust accounting software cost for a community bank?
It depends on the pricing basis— per user, per account, or percentage of AUM — plus the modules you license. The useful move is to make every vendor quote the same scenario (your users, your accounts, your modules) as an all-in three-year total including conversion, training, and maintenance. Comparing license fees alone is how banks get surprised in year three.
How long does a trust accounting conversion take?
For most community bank departments, 90 to 180 days from planning to steady state. Vendor-led data mapping, a parallel period, and weekly audits on newly converted accounts are what separate smooth conversions from horror stories.
What is the RC-T?
The RC-T is the fiduciary schedule of the FFIEC call report — the regulatory filing that summarizes your bank’s trust activities. Your trust accounting system should produce the supporting detail behind it directly, rather than leaving staff to assemble it by hand.
Can a small trust department outsource its operations?
Yes. Trust-services arrangements— where the vendor’s team runs daily posting, reconciliation, fees, statements, and tax reporting on its platform — exist for exactly this. They fit small teams and succession-risk situations, and pricing is typically scoped to account volumes and the services handed over.
