Reconciliation software for credit unions has to tie the credit union's own settlement accounts to the general ledger every business day, clear share draft and ATM network activity, age the items that land in suspense, and keep a file the supervisory committee and examiners can follow. A small business tool covers only a slice of that.
What must reconciliation software for credit unions reconcile each day?
A credit union reconciles two kinds of balances: money it holds for members, and money it holds elsewhere. The second group moves daily through settlement accounts, clearing accounts and cash, so those are the accounts that need a daily tie-out. Member share and loan totals are tied to the ledger on a monthly cycle.
The daily group
The daily group is where cash actually moves, and where a missed item grows fastest:
- Settlement accounts held at a corporate credit union or a Federal Reserve Bank. Share draft presentments, ACH files and wires all settle here.
- ATM and debit card settlement, which arrives as net figures from a card network or processor and has to be split back into its parts.
- Shared branching settlement, where another credit union's teller took a deposit or paid out cash for one of your members.
- Teller and vault cash, counted against the teller system's totals.
- Suspense and clearing accounts, the holding places for items that could not post to a member account straight away.
The monthly group
The monthly group is quieter but larger. Member share balances, loan balances and certificate balances in the core system must agree with the general ledger control accounts. The same goes for investments, borrowings and any accounts at other institutions. These rarely break by large amounts, but a small, persistent difference in a share control account is exactly the kind of thing an examiner asks about.
Why a general tool falls short
General reconciliation tools assume one bank statement and one ledger account. A credit union's settlement account receives net entries that each stand for thousands of member transactions, so matching works at the level of a batch, a file or a settlement date. For the broader category of ledger-to-subledger tools, the guide to general ledger reconciliation software and what it ties out covers how those products are built.
Share draft and ATM settlement in credit union reconciliation
Share draft and ATM settlement create timing items because the money moves before, after, or in a different total from the postings to member accounts. A share draft is the credit union version of a check. When drafts clear, the settlement account is debited for the day's presentment total while each draft posts to a member's share draft account.
Share drafts
Share draft clearing breaks in three common ways. A draft is presented but rejected, for example because of a stop payment or insufficient funds, so the member side reverses while the settlement debit stays until the return is processed. A draft is posted twice from a re-sent file. Or a draft is posted to the wrong member, which leaves the totals in balance and hides the error from a summary reconciliation. The last case is why totals alone are not enough: someone has to review rejects and duplicates line by line.
ATM and debit card networks
ATM and card activity settles as a net figure. A single settlement entry may combine your members' withdrawals at other machines, other people's withdrawals at your machines, interchange income and network fees. The reconciliation splits the net entry back into those parts and ties each one to a ledger account. A daily network report is the counterparty record, the document the settlement entry has to agree with.
Shared branching
Shared branching adds a third party. When a member deposits at another credit union's branch, that institution records the deposit, the shared branching network settles between the two, and your core system posts the member credit. Three records, three dates. A good tool matches them as a set and flags the deposit that posted to the member but never settled, or settled but never posted.
Corporate credit union and Federal Reserve settlement statements
The settlement statement from a corporate credit union or the Federal Reserve is the bank statement for the credit union itself. Reconciling it to the general ledger account for that relationship is the core cash reconciliation. Every other daily reconciliation feeds into it, because ACH, share draft, wire and card settlement all post here.
A worked daily settlement reconciliation
The table below is an example. The credit union, the figures and the item descriptions are invented to show the shape of the work.
| Line | Amount | Note |
|---|---|---|
| Balance per settlement statement, end of day | 4,812,350.00 | Corporate credit union statement |
| Add: incoming ACH file received after cutoff, credited next day | 61,200.00 | Timing item, should clear tomorrow |
| Less: share draft presentment posted to GL, not yet debited by corporate | (38,415.27) | Timing item |
| Less: wire sent at 4:55 p.m., on GL today, on statement tomorrow | (125,000.00) | Timing item |
| Adjusted balance per statement | 4,710,134.73 | |
| Balance per general ledger settlement account | 4,710,184.73 | |
| Difference | (50.00) | Unexplained, moved to suspense review |
Three items are ordinary timing differences with a date by which they must clear. The 50.00 is not explained. A tool that forces the difference to zero would hide it. A tool that lists it, and carries it into tomorrow's reconciliation until someone clears it, keeps it visible.
Carrying items forward
Each timing item should reappear on the next day's reconciliation until it clears. If the ACH file from the example is still open on day three, it is no longer timing. A reconciliation tool should show the age of every open item so that a supervisor can spot the ones that have stopped behaving like timing differences.
When the credit union has subsidiaries, such as a credit union service organization, cash moving between entities adds another layer. The guide to intercompany reconciliation software for related entities covers how those balances are paired.
Clearing GL suspense in credit union reconciliation software
A suspense account holds money the credit union has received or paid but cannot yet assign. Examples include an ACH credit for a closed account or an unresolved card dispute. Suspense is meant to be temporary, so the reconciliation's job is to age every item and push each one to its proper account.
A suspense aging table
The example below shows how an aging view helps a supervisor decide where to spend time. The items and amounts are made up.
| Item | Amount | Days open | Owner | Next step |
|---|---|---|---|---|
| ACH credit, closed account | 412.18 | 3 | Deposit operations | Return to originator |
| Shared branch deposit, no member match | 1,050.00 | 6 | Member services | Call the other branch |
| Unexplained settlement difference | 50.00 | 1 | Accounting | Trace through the day's files |
| Card dispute provisional credit | 89.99 | 41 | Card services | Escalate, past target |
| Teller over, branch 2 | 20.00 | 58 | Branch manager | Approve write-off or explain |
Two items are past any sensible target. Neither is large, but the age is the signal. A suspense balance that only grows suggests postings are being parked rather than resolved.
What the tool should do with suspense
Reconciliation software for this job should list every suspense item with its date, amount and source document. It should assign an owner and show the age. It should keep a history when an item is moved out. It should not net debits against credits to make the balance look small, because two unrelated items of 500.00 each, one in each direction, are two problems, not none.
What do examiners and the supervisory committee expect to see?
Examiners and the supervisory committee expect to see reconciliations that are complete, timely, independent of the people who post the transactions, and supported by the source records. They also expect old reconciling items to be explained. A file that only shows a zero difference, with no support, does not meet that bar.
The supervisory committee's role
The supervisory committee has specific duties. According to NCUA's Examiner's Guide on supervisory committee responsibilities, every credit union must perform or obtain an annual audit. The committee must also verify, or cause the verification of, members' accounts once every two years. The same page says the committee must reconcile the member share and loan accounts used in that verification to the general ledger, whichever verification method it uses. It also gives the committee responsibility for reviewing and testing internal controls set by the board and management.
What that means for the reconciliation file
Those duties shape what a reconciliation file needs to contain:
- Share and loan control totals tied to the GL, with the trial balance report that supports them.
- The daily settlement reconciliations, kept in order, with each timing item's clearing date.
- The suspense aging, with owners and the history of cleared items.
- Evidence of review, showing who prepared each reconciliation and who reviewed it.
- Source documents for anything unusual, such as network reports, statements and correspondence.
An auditor working for the committee will test a sample of these items back to source documents and forward to the ledger. The method is explained in vouching and tracing, the two directions of audit testing.
Where an outside firm comes in
Many smaller credit unions hire a CPA firm to perform the supervisory committee audit. That firm brings its own tools, and its own expectations of what a client's reconciliation file should look like. The guide to reconciliation software for accountants running engagements covers the firm's side of that work. For the audit firm, PreciseBankFlow can foot the bank statements it collects and list any difference, duplicate or gap before the testing starts; it is a check on the statements, not a replacement for the credit union's core or reconciliation system.
When credit union reconciliation software is the wrong purchase
Credit union reconciliation software is the wrong purchase when the problem is not the tool. If the core processor already produces settlement reports the staff never read, a new system will produce more reports nobody reads. The fix there is ownership and a daily review routine, not software.
Signs the tool is not the gap
Consider these before buying:
- Small volume. A credit union with one settlement account, little card activity and no shared branching may reconcile well in a spreadsheet with a second reviewer.
- The core has the feature. Many core processors include reconciliation modules. Check what yours offers, and whether the staff were ever trained on it.
- Suspense is a policy problem. If items sit in suspense because nobody has authority to write off small amounts, software will age them nicely and they will still sit there.
- The difference is in the core. If the core system's own totals disagree with its member-level reports, a reconciliation tool downstream will only confirm that something is wrong.
What to do instead
Write down every account that needs a reconciliation, how often, who prepares it and who reviews it. Run that list for a month with the tools you have. If the work is late or the reviewers cannot follow it, you know what the new tool must fix. If you want an outside check on the statements themselves, see how PreciseBankFlow handles a set of statements.