The accounts that eat a credit union accounting team's week
A credit union rarely has one big reconciliation problem. It has fifteen or forty medium ones, each with its own report, its own cutover and the one person who knows how it works. The table below is the usual inventory at a credit union with a card program, a shared branching relationship and more than one settlement account.
| Account | External side | Cadence | What usually breaks |
|---|---|---|---|
| Corporate credit union settlement account | Corporate statement or daily activity file | Daily | Wires and ACH settling on a different day from the GL posting |
| Federal Reserve account, where held | Fed statement of account and settlement reports | Daily | Cash letter and ACH settlement entries posted to the wrong clearing account |
| Share draft clearing | Inclearing file and return items | Daily | Returned drafts, duplicate presentments and exception items worked outside the core |
| ACH clearing | ACH settlement and return reports | Daily | Returns and reversals booked a day after the original entry |
| Debit and credit card settlement | Processor and network settlement reports | Daily | Interchange and fees netted into one amount, chargebacks sitting in suspense |
| ATM settlement and cash | Switch activity, network settlement, cash counts | Daily and each replenishment cycle | Cutover timing, partial dispenses, shortages and overages |
| Shared branching settlement | Shared branch network settlement report | Daily | Transactions posted at another credit union that settle net of fees |
| Loan clearing and suspense | Core sub-ledger | Daily or weekly | Payments with no owner and no age, especially after a core conversion |
What the NCUA and your auditors test in a reconciliation
The controls a credit union reconciliation has to evidence are written down. The NCUA supervisory committee audit minimum procedures guide, used by federally insured credit unions under $500 million in assets that choose the "other supervisory committee audit" option under 12 CFR 715.7, tells the auditor to reference each reconciling item by date and check whether any originated more than 60 days before the reconciliation date. It also asks for separate prepared by and reviewed by dates on each reconciliation, and for a written confirmation from the correspondent institution compared to the reconciled balance.
Examiners work from the same material. The NCUA examination procedures for cash operations ask for recent bank and corporate account statements along with the completed, detailed reconciliations behind them. A spreadsheet can satisfy all of this, but only if someone rebuilds the aging, the sign-off dates and the support every month. Software that records them as the work happens turns the audit request into an export.
| What gets tested | Where it lives in a spreadsheet | Where it lives in Bankautomation |
|---|---|---|
| Reconciling items older than 60 days | A formula someone has to remember to add | Every item carries an age from its origin date, filterable by account and age band |
| Separate preparer and reviewer, with dates | Initials typed into a cell | Recorded on the certification with timestamps and the signed-in user |
| Book balance agrees to the GL | A tie-out tab that can be overwritten | Stored with the reconciliation for the period it certified |
| Support for each reconciling item | A shared drive folder, if it exists | Comments and attachments on the item itself |
| Changes to matching rules or tolerances | Not recorded | Versioned, with who approved each change and when it took effect |
Card, ATM and shared branching: where the daily volume is
For most credit unions the heaviest reconciliations are not the investment accounts. They are the card program and the ATM fleet, settled every day through a processor and one or more networks, often a credit union service organization such as Velera (formerly PSCU and Co-op Solutions). Each settlement is a net figure: transactions, interchange, network fees and adjustments rolled into one amount that has to be broken back out before it can agree to the GL.
Shared branching adds a second direction. Your members transact at other credit unions' branches and their members transact at yours, and the network settles the position each night. When the member-side postings and the settlement report disagree, the difference usually traces to a fee, a reversal or a transaction that posted after the cutover. Those are classifiable causes, so they can be matched or routed rather than researched from scratch every morning. ATM balancing has its own page with the full break list: ATM reconciliation software. ACH clearing, returns and Federal Reserve settlement windows are covered on ACH reconciliation software, and the Fed statement itself, FIRD detail and FedNow cycle dates on Federal Reserve account reconciliation software.
From a settlement report to a worked item
Input
- Network settlement report · net settlement 412,806.40 USD, including network fees of 4,215.75 USD
- Core GL · card settlement account · 417,022.15 USD posted from transaction activity
- Difference · 4,215.75 USD
Output
- Fee not accrued 4,215.75 USD. The net settlement includes a network fee line with no matching GL posting.
- Suggested action: propose the fee posting to the network expense account under approval, then add the fee line to the expected categories for this network so it matches on the next cycle.
- Routed to Card Services accounting, aged from the settlement date, with the settlement report attached.
Credit union reconciliation software compared
Credit unions shortlisting reconciliation software usually see the same four options. Each is the right answer for somebody. The deciding questions are whether the work is a month-end certification or a daily exception queue, and whether you want to see a price before a sales call.
| Option | Good at | Weak at | Fits |
|---|---|---|---|
| Spreadsheets and core reports | No new vendor, fully flexible | No aging, no enforced sign-off, and the knowledge sits with one person | Small credit unions with few settlement accounts |
| Trintech (Adra, Cadency, ReconNET, Frontier) | Close and certification across the balance sheet. Trintech says hundreds of credit unions use it, and its credit union page lists share draft, 5300 Call Report, teller cash and ATM reconciliation | Several product lines, so check the proposal against the one you will run. Pricing is quoted | Credit unions buying a full close and certification platform |
| ReconArt | GL, card, ACH and bank reconciliation, with credit union customers such as MIDFLORIDA Credit Union and Catalyst Corporate FCU | Pricing is quoted, though ReconArt states an average annual cost below $50,000 | Mid-size credit unions that want a reconciliation-focused platform |
| Bankautomation | Daily exception work: card, ATM, settlement and GL breaks classified, routed and aged in one queue, with published pricing | A newer vendor, not a close checklist, and it does not replace your core or your card processor | Credit union accounting and operations teams that want a daily worked queue and a price up front |
What credit union reconciliation software costs
Most vendors in this category quote per institution, so the first number arrives after a demo. Bankautomation publishes its prices. Operations is $1,200 a month for one process line, 250,000 matched items a month and three source connections, which suits a credit union starting with card settlement or its corporate account. Platform is $3,900 a month and adds unlimited source connections, maker-checker approvals and SSO, which is where most credit unions land once card, ATM, shared branching and the GL all feed the same queue. Institution is $9,500 a month for multi-entity groups. Every limit is on the pricing page.
A rollout that starts with one account
Step 01
Pick the account that hurts most
Usually card settlement, the corporate settlement account (your due from account at the corporate, covered in detail on correspondent bank reconciliation software) or share draft clearing. One account with a daily spreadsheet is a better start than the whole balance sheet.
Step 02
Send a sample file from each side
A settlement report and a GL export, including plain CSV from your core. Field mapping is configuration and versioned, not an integration build.
Step 03
Agree tolerances with your controller
The date window for cutover, the fee schedule per network and the dollar threshold below which a difference is logged, each approved and recorded.
Step 04
Run in parallel, then retire the spreadsheet
Compare the worklist with the spreadsheet for a few cycles. When they agree, retire the spreadsheet for that account and add the next one.
Try the card settlement sample
The resolver at the top of this page opens on a card settlement file against core postings, with Visa, Mastercard, Amex and ATM lines. It holds the differences credit union card teams see most: a Mastercard settlement that misses its posting by 442.05 USD, a scheme fee line with no GL entry, an Amex settlement posted a day late and a refund batch that appears twice on the ledger side. Move the amount tolerance and watch which differences are absorbed and which stay as breaks. The same engine runs general ledger reconciliation for loan clearing and suspense accounts, and account reconciliation software for certification across the rest of the balance sheet.
Sample data only. The demo never receives member or production data, and nothing you paste into it is stored.
Questions about credit union reconciliation software
What is credit union reconciliation software?
It is software that matches a credit union's external records, such as corporate account statements, card and ATM network settlement, share draft clearing and shared branching reports, against the general ledger, then tracks every unmatched item until it is resolved. The valuable part is the residue: aging, ownership, preparer and reviewer sign-off, and evidence for audits and exams.
How often should a credit union reconcile its accounts?
Accounts with daily activity, such as corporate, card, ATM, ACH and shared branching settlement, are best reconciled daily, while low-activity accounts can follow a monthly cadence set in policy. The NCUA supervisory committee audit guide flags reconciling items older than 60 days, and daily work keeps items from aging into findings.
Does reconciliation software help with an NCUA exam?
It helps with the evidence. Examiners and supervisory committee auditors look for completed reconciliations, separate preparer and reviewer dates, support for reconciling items and how old those items are. Software that records them as the work happens can export them per account and period. It does not make exam determinations or replace your auditors.
Can it reconcile shared branching settlement?
Yes. The shared branching settlement report is read as a source file and matched against the member-side postings and the settlement account in your GL. Fees and reversals are modeled as expected categories, so only genuine differences, such as a transaction posted after cutover, remain as breaks with an owner.
Does it work with our core, such as Symitar, KeyStone or DNA?
Sources are read as files rather than through a core integration, so what matters is that your core can export the GL and the transaction activity, for example as CSV reports. Field mapping is configuration, and the usual first step is a sample export from each source rather than an API project.
How much does credit union reconciliation software cost?
Most vendors quote per institution. ReconArt states an average annual cost below $50,000, and Trintech prices by quote. Bankautomation publishes its plans: Operations at $1,200 a month, Platform at $3,900 a month with unlimited sources and maker-checker, and Institution at $9,500 a month. See pricing.