What bank reconciliation software actually does
Bank reconciliation software takes the lines on your bank statement and matches each one to the document it settles: an open invoice, a vendor bill, an expense claim or a transfer between accounts. The goal is a ledger that agrees with the bank on any day, not only on the day someone finishes the spreadsheet.
The manual version of this job is familiar. Statements are exported at month end, lines are ticked off against receivables and payables, and the unexplained remainder is chased by email until it is small enough to write off. The work is not hard, but it is late by design: the books are right eventually, not now.
Good software changes the timing more than the logic. Feeds arrive continuously, matching runs as each line lands, and the month-end task shrinks from a reconstruction to a review of the lines the system could not place on its own.
How automated matching works
Matching starts with a bank feed. Where a bank offers a direct feed, lines arrive as they clear; where it does not, a statement import does the same job on a schedule. Either way the line carries a reference, an amount, a date and a counterparty, and those four fields are what the matcher works with.
Each line is compared against open documents. A credit that quotes an invoice number and equals the invoice amount is an easy match. A credit that equals two invoices for the same customer, or covers an invoice less a bank charge, needs partial-payment logic. A recurring debit such as a bank fee or a salary run needs a rule rather than a document.
The threshold matters. Matches above it post automatically; those below it queue for a person with the likely match already selected, so the human step is a confirmation rather than a search. Rules a person confirms are kept, so the same kind of line is handled without them next time.
- Reference, amount and counterparty matching against open invoices and bills
- Partial payments, overpayments and multi-invoice settlements
- Rules for recurring lines such as fees, subscriptions and payroll
- A confidence threshold that decides what posts on its own
Why receivables and payables have to live on the same ledger
Matching only works when the documents being matched are in the same place as the bank lines. If invoices are issued from one tool, bills are approved in email and the bank is reconciled in a spreadsheet, the matcher has nothing to match against, and someone has to export and re-key before it can start.
On a single ledger the invoice posts its receivable when it is issued, the bill posts its payable when it is approved, and the bank line settles one or the other. Aged receivables, the payment run and the cash position are then views on the same record rather than three reports that need to be reconciled to each other.
This is also what lets a matched payment do useful work downstream. When a receipt closes an invoice, the reminder sequence for that invoice stops, the customer's balance updates, and the cash forecast moves, without anyone copying a figure between systems.
What changes at month-end close
With continuous matching, the month-end close is no longer where reconciliation happens. It is where the exceptions are cleared and the period is locked. A useful way to see the difference is to walk through what is left to do.
Before: reconciliation as reconstruction
The statement is exported on the first working day. Receivables and payables are ticked off line by line, unexplained lines are queried with sales, operations and the bank, and the accruals and adjustments wait until the bank balance ties. The close takes as long as the slowest query.
After: reconciliation as review
The bank was matched as the month ran, so the first task is a short queue of lines the system could not place. Once those are confirmed or corrected, accruals, depreciation and prepayments post, the trial balance is checked, and the period locks. Anything posted after the lock is a journal in the next period, not an edit to the old one.
- Clear the queue of unmatched bank lines
- Confirm receivables and payables age correctly
- Post accruals, depreciation and prepayments
- Check that the trial balance ties, then lock the period
How Solonomous ERP handles bank matching and the close
The Invoicing & Finance module in Solonomous ERP is built the way this article describes. Every invoice, bill and payment is a journal on the ERP Core ledger, so there is nothing to export at month end. Bank feeds arrive directly where the bank offers them and by statement import otherwise, and each line is matched to an open invoice, bill, expense or transfer by reference, amount and counterparty.
Matches above the confidence threshold you set post on their own. Everything else is queued with a suggested match for a person to confirm or correct, and rules you confirm are applied to the same kind of line next time. A matched receipt closes the invoice, stops its reminders, updates the customer's balance and moves the thirteen-week cash forecast.
The suite's Close agent runs the month-end sequence on top of this: reconciling the feed against open invoices, flagging the lines that need a person, accruing unbilled project time, posting depreciation and prepayments, and asking for approval before the period locks. It runs with the permissions of the person who asked, every action it takes is a posted, reversible ledger entry, and it stops where a person must decide. That is a design choice, not a limitation: an agent that could lock a period on its own would be harder to trust than one that asks.
Questions to ask before you choose bank reconciliation software
Most products can match an exact reference and amount. The differences show up in the cases that are not clean, and in what happens to a match after it is made. These questions separate a matching screen from a finance system.
The last two are the ones that decide whether month end gets shorter. Matching that lives outside the ledger still leaves a reconciliation between the matching tool and the books, which is the job you were trying to remove.
- Does it take direct bank feeds, and what is the fallback where the bank has none?
- How does it handle partial payments, bundled settlements and bank charges deducted from a receipt?
- Can you set the confidence threshold, and can you see why a match was suggested?
- Are confirmed matches turned into rules that apply next time?
- Does a matched receipt close the invoice and stop its reminders, or is that a second step in another tool?
- Is every match a reversible ledger entry with a record of who confirmed it?