How to Do Reconciliations: A Complete Guide
Learn how to do reconciliations with this step-by-step guide covering workflows, checklists, automation tips, and common pitfalls
Month-end arrives, the close is already under pressure, and one reconciliation refuses to tie. The ledger balance doesn't agree with the statement, a payment appears twice, and nobody can immediately explain whether the difference is a timing item, a missing entry, or a genuine error. The matching itself may take minutes. Finding the evidence and deciding what to do next can consume the rest of the afternoon.
That's the practical reality behind how to do reconciliations well. Reconciliation isn't comparing two columns until the numbers look similar. It's a controlled process for proving that ledger balances are complete, accurate, supported, and properly adjusted. The method applies across bank, accounts receivable, accounts payable, payroll, inventory, intercompany, fixed asset, and other balance-sheet reconciliations.
The process below focuses on the part that usually demands the most judgment, exception investigation. It also covers the core workflow, accuracy checks, useful metrics, the trade-off between manual and automated work, and a sensible way to introduce tools without weakening control.
Table of Contents
- Why Reconciliation Matters More Than You Think
- The Complete Reconciliation Workflow
- Where Reconciliation Time Goes
- Accuracy Checks and Control Metrics
- Manual vs Automated Reconciliation
- When to Invest in Automation Tools
- Your Reconciliation Action Plan
Why Reconciliation Matters More Than You Think
A reconciliation often looks routine until it catches something that would otherwise reach the financial statements. A duplicate supplier payment can inflate expenses, a missed invoice can understate liabilities, and an unrecorded bank fee can leave cash and expenses misstated. The reconciliation gives the preparer a structured point at which those issues must be identified and explained.
The control is foundational because it compares an external or subsidiary record with the organization's accounting records and requires investigation of differences. For bank reconciliations, Washington State's public-sector control guidance describes reconciling both the ending balance and cash activity across bank statements and accounting records. That principle extends naturally to other account types, where the general ledger is compared with a subledger, statement, schedule, invoice population, or supporting register.
What the reconciliation proves
A completed reconciliation should answer several questions clearly:
- Completeness: Has every relevant receipt, payment, invoice, journal entry, credit, and adjustment been recorded?
- Accuracy: Do amounts, dates, accounts, entities, customers, and vendors agree with the supporting evidence?
- Timing: Are differences explained by cut-off, deposits in transit, outstanding checks, or other valid timing items?
- Ownership: Does someone know who must resolve each open exception and by when?
- Evidence: Can a reviewer understand the conclusion without reconstructing the entire investigation?
The monthly cadence matters because reconciliation must cover receipts, deposits, additions, deductions, and ending balances, then resolve the remaining difference to zero. That's why many finance teams treat it as a recurring close step rather than a one-time cleanup.
Practical rule: A reconciliation isn't complete because the preparer found a difference. It's complete when the difference is explained, corrected or appropriately supported, and reviewed.
Weak reconciliations usually fail through silence. Teams carry forward unexplained items, accept vague descriptions such as “timing,” or force a balance with an unsupported adjustment. A strong process does the opposite. It makes exceptions visible, assigns follow-up, and preserves the reasoning behind the final balance.
The Complete Reconciliation Workflow
The sequence matters. Starting with transaction matching before confirming the opening balance can make a perfectly valid reconciliation appear wrong, while beginning with a disorganized document search makes exceptions harder to trace.
Gather the evidence first
Collect the source records for the same accounting period:
- The external statement or independent source, such as a bank statement, vendor statement, customer aging report, payroll register, inventory count, or intercompany confirmation.
- The general ledger extract for the account and period.
- The prior-period reconciliation, including its closing balance and any approved items carried forward.
- Supporting evidence, such as invoices, receipts, payment confirmations, deposit records, journal-entry support, credit memos, or correspondence.
Make sure the records cover the same entity, account, currency, and period. A reconciliation can appear out of balance because one report includes a later posting date or a different account scope.
Verify the opening balance
Match the current opening balance to the prior reconciliation's closing balance. If it doesn't agree, stop and resolve that issue before working through current-period activity.
An opening mismatch often points to a late journal entry, an amended prior reconciliation, an incorrect brought-forward figure, or an unexplained item that was removed without documentation. Treating it as a current-period exception obscures the source of the problem.
Match transactions and classify differences
Compare the records transaction by transaction. Mark items that agree, then separate items that exist only in the ledger from items that exist only in the independent record.
For a bank reconciliation, common reconciling items include outstanding checks, deposits in transit, bank charges, bank credits, and bank errors. For accounts receivable, the equivalent investigation might involve unapplied cash, misapplied customer payments, missing invoices, credit memos, or timing between receipt and deposit.
Resolve, document, and review
Book missing transactions, correct posting errors, remove duplicates, and investigate suspicious or unsupported entries. Then recalculate the adjusted balances until they agree exactly.
The bank-reconciliation methodology outlined by CentralPay follows this practical logic: gather the records, confirm the opening balance, reconcile each transaction, distinguish ledger-only and statement-only items, and resolve discrepancies through corrections and adjustments.
Finish by attaching or linking the evidence, recording the preparer and review details, and listing any approved unresolved items. A reviewer should be able to see what was matched, what wasn't, why it differed, what action was taken, and whether the adjustment received proper approval.
Where Reconciliation Time Goes
A reconciliation can match most transactions quickly and still consume hours. The delay usually begins when the first unmatched item needs an explanation.
A 2025 industry report summary cited by US Tech Automations says 41% of reconciliation time goes to transaction matching, while 59% goes to investigating exceptions. That split should shape how managers measure performance. A faster matching engine helps, but it cannot remove the larger workload when staff must still locate documents, contact vendors, interpret timing differences, and obtain approval for corrections.
What exception investigation involves
An exception is a question that requires evidence, not merely a highlighted spreadsheet cell.
A payment may appear on the bank statement but not in the ledger because a fee, transfer, or receipt was not posted. A ledger entry may be absent externally because the transaction remains outstanding. Amounts can differ when one side includes tax, a foreign-exchange effect, a credit memo, or a split posting. The preparer must determine which explanation fits the records and document the conclusion.
Investigation often involves:
- Requesting missing invoices, receipts, remittance details, or deposit support.
- Asking a vendor or customer to clarify an unfamiliar amount.
- Separating a valid timing item from a posting error.
- Checking whether a duplicate originated in the source system or during import.
- Escalating unusual transactions for approval instead of clearing them casually.
- Applying the organization's policy to any immaterial difference.
Triage by risk, not frustration
Do not work through exceptions in report order. Rank them by value, age, recurrence, risk, and financial-statement impact.
A small recurring difference may expose a broken process. A larger item with clear evidence of a deposit in transit may need less immediate research than an unfamiliar payment without supporting documentation. Older exceptions deserve attention because ownership may be unclear, and the evidence needed to resolve them can become harder to obtain.
Strong reconciliation teams do more than clear exceptions quickly. They identify recurring exceptions and fix the process producing them.
Write a concise resolution note. “Timing” is insufficient. State what is timing, name the supporting document, record when the item should clear, and assign an owner for follow-up. That record gives the reviewer a clear audit trail and turns recurring exceptions into process-improvement signals.
Accuracy Checks and Control Metrics
A reconciliation can balance and still be poorly controlled. Arithmetic is a useful first filter, but accuracy also depends on the period, source data, supporting evidence, and review record. Use the workflow in the previous section for the balance calculation, then focus this review on whether the result is complete and defensible. The AuditProSuite bank-reconciliation control provides a practical reference for documenting that control.
Run the core checks
Use a consistent checklist rather than relying on memory:
- Confirm the opening balance. It must agree with the prior approved closing balance.
- Confirm the period. The statement date, ledger date, entity, account, and currency must align.
- Compare activity. Check receipts, payments, credits, debits, invoices, deposits, and adjustments.
- Identify timing items. List outstanding checks, deposits in transit, unpresented cheques, and uncleared lodgements where relevant.
- Record external charges and credits. Bank fees, interest, or other items not yet in the general ledger need appropriate entries.
- Review the evidence. Each material adjustment should have a source document, explanation, owner, and expected clearing point.
Deltek's reconciliation guidance calls for identifying the general ledger balance at the statement date, listing outstanding checks, deposits in transit, bank charges, and bank credits, then calculating adjustments until the balances agree. The reviewer should also confirm that unresolved items have not been carried forward without investigation.
Measure the process, not just the balance
A balanced account can conceal a slow or weak process. Track completion rate, exception rate, unresolved difference value, and turnaround time. These measures show whether reconciliations finish on schedule, how much investigation they generate, whether material items remain open, and how long resolution takes.
Exception handling deserves particular attention because investigation, rather than initial matching, consumes much of the reconciliation effort. Review the number of exceptions raised, the age of open items, repeat causes, and the time spent clearing them. A high exception rate may indicate poor source data or weak upstream controls. A low rate paired with repeated late sign-offs may point to under-investigation.
Set a review cadence based on account risk. Review high-risk accounts and overdue items more frequently, and examine material reconciling items by person, department, entity, and account type. If one department repeatedly submits incomplete support, change the submission process or provide targeted training. If one preparer has an unusual exception rate, review the data and workload before drawing conclusions.
Manual vs Automated Reconciliation
A low-volume account with clean source data may be faster to review in a controlled spreadsheet than to configure in a new system. Manual work becomes risky when staff retype repetitive, high-volume transactions and then use their limited judgment time to correct transcription errors or investigate exceptions.
Industry benchmark summaries report that manual bank reconciliation statement preparation can carry a 15% to 25% error rate, described as roughly one mistaken reconciliation in four, according to independent practitioner commentary on AI bank reconciliation. The same verified data cites manual balance-sheet reconciliation error rates of 0.8% to 1.8%, equivalent to 800 to 1,800 errors per 100,000 transactions. These figures do not predict results for every team. They show why manual workflows need review controls, version discipline, and checks over opening and closing balances.
AI-assisted bank reconciliation benchmark summaries report that automation can reduce reconciliation time by about 70%, turning a 500-transaction task from roughly 3.5 hours to about 1 hour, while error rates can fall below 0.5%. Automation changes the allocation of work. It handles extraction and likely matches, while staff spend more time investigating exceptions, approving adjustments, and reviewing unusual accounting.
| Metric | Manual Approach | Automated Approach |
|---|---|---|
| Data extraction | Retype or copy transactions from source documents | Parse structured data from supported files |
| Matching | Compare rows manually or with spreadsheet formulas | Apply matching rules and surface likely matches |
| Exceptions | Search through documents and messages one at a time | Prioritize unmatched or unusual items for review |
| Control risk | Vulnerable to transcription, version, and formula errors | Dependent on source quality, rules, review, and validation |
| Best fit | Low volume, unusual accounts, or one-off investigations | Repetitive volume with consistent source formats |
For PDF statements, manually retyping a multi-page statement takes roughly 30 to 60 minutes, while conversion takes under two minutes. That comparison describes the task, not a measured result for any particular provider. The time saved increases with statement volume, but converted output still requires opening-balance, closing-balance, completeness, and exception checks.
Use this guide to manual data entry in bank reconciliation to identify repetitive steps before choosing a tool. Automation earns its keep when it removes copying and sorting, while qualified staff retain responsibility for exception approval, accounting judgment, and final review.
When to Invest in Automation Tools
Automation should follow the bottleneck. If the team has few transactions and spends its time resolving unusual accounting questions, a conversion tool won't remove the main constraint. If staff spend close time opening PDFs, copying rows, normalizing dates, and checking whether every transaction made it into a spreadsheet, structured extraction is a more direct investment.
The available benchmark context is useful here. 54% of organizations still use no reconciliation tools, while 83% reconcile 100 to 500 accounts at least quarterly, according to Resourceful Finance Pro's reconciliation benchmark coverage. Those figures don't prescribe a purchase decision, but they show that substantial reconciliation activity still occurs without dedicated tooling.
Evaluate the input workflow
For statement imports, check whether the tool supports the files your team receives.
- Digital PDF statements.
- Scanned statements through OCR.
- Password-protected PDFs, with the password supplied for that conversion.
- Bulk uploads.
- Files up to 25 MB.
- CSV or Excel/XLSX output suitable for review and subsequent ledger work.
Autobankstatement converts supported PDF bank statements into CSV or Excel/XLSX tables, including digital, scanned through OCR, and password-protected files. It offers a free guest preview before payment, registered-user download access for 24 hours, and automatic upload deletion within 24 hours. Plans include Starter at $15 per month for 400 pages, Professional at $30 per month for 1,000 pages, and Business at $50 per month for 4,000 pages, with annual discounts and custom enterprise limits. Those plan details are best assessed against your own statement volume, not against a generic promise of efficiency.
For teams handling scanned documents, this explanation of OCR in banking is useful when deciding whether extraction quality will improve the current process. Whatever tool you choose, compare the converted rows with the original statement and validate the opening balance, transaction totals, and closing balance before importing or posting anything.
Pilot without weakening controls
Start with a contained account or period. Keep the original PDF, the converted file, the reconciliation workpaper, and the reviewer's sign-off together. Run the manual and converted workflows in parallel during the transition, then compare omissions, duplicates, dates, and balances.
Don't let automation bypass segregation of duties or approval rules. It should remove repetitive handling, not authorize adjustments or turn an unexplained exception into an accepted transaction.
Your Reconciliation Action Plan
Put the controls in place before buying more technology. Confirm the opening balance, apply opening balance + credits − debits = closing balance, and require a resolution note for every material exception. Then track completion rate, exception rate, unresolved difference value, and turnaround time so the team can see whether the process is improving.
For implementation, assign one preparer and a separate reviewer where staffing permits. Start with one account, document the existing method, test the automated import against the source, and keep both workflows available until the reviewer is comfortable with the evidence trail. People who are used to manual work usually adopt change faster when the new process removes copying but preserves their ability to inspect and challenge every result.
Use this bank-statement import workflow guide to map statement extraction into your broader bookkeeping process, while remembering that conversion is only one stage of reconciliation. The final control remains accounting judgment, documented evidence, and a balance that can be independently explained.
Reconciliation deserves the same care as any other key close control. It protects the ledger by forcing differences into the open, and it gives finance teams a repeatable way to resolve errors before they affect reporting.
Autobankstatement converts digital, scanned, and password-protected PDF bank statements into CSV or Excel/XLSX files, with bulk uploads, a free guest preview, 24-hour download access for registered users, and automatic upload deletion within 24 hours. Visit autobankstatement to turn statement extraction into a controlled first step in your reconciliation workflow.
Convert your next statement in minutes
Upload a bank statement PDF — digital, scanned, or password-protected — preview the extracted table, and download clean CSV or Excel.