Reconciliation Automation for Accounting Firms
A controlled reconciliation workflow for accounting firms, with matching rules, evidence, exception review, posting approval, and pilot measures.
Reconciliation automation should compare approved record sets, clear only matches that satisfy documented rules, and give reviewers a short exception file with the source evidence attached. It should not treat a zero difference as proof that the work is complete. An authorized person should approve adjustments and the final close.
The work is a sensible automation candidate because much of it is structured. The Bureau of Labor Statistics lists checking figures and postings, reconciling records, and reporting differences among the duties of bookkeeping, accounting, and auditing clerks. That description does not set an automation target. It helps separate repeatable comparison work from the judgment needed to resolve a difference.
A controlled reconciliation workflow
| Step | Automated role | Control |
|---|---|---|
| Set scope | Read the approved entity, account, period, and source list | Lock the scope before matching starts |
| Import | Pull read-only copies of both record sets | Record source, extraction time, row count, and file hash where available |
| Normalize | Standardize approved fields such as dates, signs, references, and currency codes | Preserve every raw value beside the normalized value |
| Match | Apply exact rules first, then approved tolerance rules | Store the rule and source IDs for every proposed match |
| Package exceptions | Attach candidate items, history, and supporting records | Do not hide contradictory or missing evidence |
| Review | Let staff approve, correct, reject, or request more evidence | Record reviewer, decision, reason, and time |
| Post | Prepare an approved entry or status update | Require the firm’s posting authority and separation rules |
| Close | Recalculate the difference and complete the checklist | A named reviewer approves completion |
Start with deterministic rules. A shared transaction ID, amount, currency, and valid period boundary is easier to test than a similarity score. One-to-many matches, duplicate references, changed bank details, stale checks, foreign exchange differences, and proposed journal entries belong in an exception queue unless the firm has a tested rule for that exact case.
Keep the evidence with the match
For engagements under PCAOB standards, AS 1105, Audit Evidence, distinguishes the quantity of evidence from its relevance and reliability. It also says reliability depends on the source, nature, and circumstances. A ledger export and a copied spreadsheet may agree while still relying on the same faulty source. The system therefore needs to identify where each record came from, not merely show two equal amounts.
AS 1215, Audit Documentation, requires documentation for PCAOB engagements to show the procedures performed, evidence obtained, conclusions reached, and who performed and reviewed the work. It also calls for a clear link to significant findings or issues. A useful reconciliation log follows that shape:
- source record identifiers and extraction details
- raw and normalized values
- the rule that produced a proposed match
- evidence inspected for an exception
- the preparer’s conclusion and reason
- the reviewer, decision, and date
- any later change, with its author and reason
PCAOB standards do not govern every service an accounting firm performs. A firm must apply the professional, legal, contractual, and documentation requirements that govern its engagement. These standards are cited here for their specific evidence and documentation requirements, not as a universal rule for bookkeeping work.
Worked bank reconciliation
This example is illustrative, not a client result. Suppose the ledger cash balance is $248,900 and the bank statement balance is $251,650. The approved exception list contains a $1,450 deposit in transit and $4,200 of outstanding checks.
| Item | Amount |
|---|---|
| Bank statement balance | $251,650 |
| Add deposit in transit | $1,450 |
| Subtract outstanding checks | ($4,200) |
| Adjusted bank balance | $248,900 |
| Ledger cash balance | $248,900 |
| Difference | $0 |
The calculation is:
Adjusted bank balance = statement balance + deposits in transit - outstanding checks
The system can calculate the zero and assemble the records. The reviewer still checks that the deposit belongs to the period, each check remains outstanding, no item appears twice, and the source records are reliable enough for the engagement. If a bank fee is missing from the ledger, the system may draft an adjustment, but the approved person decides whether and where it posts.
Measure the pilot without hiding review work
Use the same account types and definitions before and during a supervised pilot.
| Measure | Formula or definition |
|---|---|
| Confirmed match rate | Confirmed machine-proposed matches divided by eligible lines |
| Correction rate | Machine proposals changed by reviewers divided by reviewed proposals |
| Exception age | Time from exception creation to documented resolution |
| Review minutes | Staff time spent checking matches, exceptions, and close approval |
| Reopened rate | Completed reconciliations reopened for a missing or wrong item |
| Unsupported posting count | Entries posted without the required evidence or approval |
A high match rate can coexist with poor evidence or many later corrections. Review the measures together and inspect samples from both matches and exceptions. Set tolerances from the firm’s records and risk policy, not a vendor’s generic threshold.
The Reconciliation Prep shows one bounded exception workflow. The human review guide explains how to place approval where the consequence changes, and the Profitable Line Audit measures the current process before a build.
Limitations
Automation cannot repair incomplete source records, decide the economic substance of an unfamiliar transaction, or establish that evidence is authentic merely because fields match. Timing differences, split settlements, intercompany activity, foreign currency, fees, reversals, duplicates, and changed account mappings need tested handling. Access controls and approval rights also matter. A sound matching engine connected to an over-permissioned posting account is still a poor control.
Sources
Questions this article answers
What parts of a reconciliation can an accounting firm automate?
A system can import approved records, preserve the source data, normalize fields, apply documented matching rules, prepare exceptions, and update status. An authorized person should review uncertain items and approve any posting or account close.
Should reconciliation software post adjustments automatically?
Not by default. A proposed adjustment can affect the ledger and may require judgment about timing, classification, or supporting evidence. Route it to an authorized reviewer and log the decision.
How should a firm measure reconciliation automation?
Track eligible lines, confirmed matches, corrections, exception age, reopened items, review time, and unsupported postings. Define each measure before the pilot and compare like periods and account types.
Bring us your worst workflow.
Book the Profitable Line Audit