
A working account reconciliation checklist follows five steps in strict order: prepare, match, investigate, adjust, and review with sign-off. The single control that decides whether an audit sample passes or fails is separation between preparer and reviewer, backed by attached evidence, not a plug entry. Get those two things right and every reconciliation lands as a documented, defensible package ready for month-end close or an external audit request.
TL;DR:
- Separating the preparer and reviewer is the critical control that ensures a reconciliation is properly documented and defendable during audits.
- Line-by-line matching of transactions is essential to detect offsetting errors, rather than only comparing total balances.
- Each unmatched line item must be investigated and explained, with a specific cause such as timing or error, to maintain accurate recordkeeping.
- Corrective journal entries should fix underlying discrepancies to prevent error accumulation, not just hide differences with residual adjustments.
- Automation should focus on mechanical tasks like bank feed imports and open-item aging, while manual review remains vital for audit-ready sign-off.
What Is an Account Reconciliation Checklist?
An account reconciliation checklist is the ordered set of tasks a preparer and reviewer follow to confirm a general ledger balance matches independent, third-party evidence for that account. It exists because a reconciliation without a fixed sequence tends to skip steps under close-week pressure, and the step most often skipped is the one auditors check first: reviewer sign-off.
The standard sequence has five stages, and each one has a distinct owner and output.
- Prepare. Close the relevant subledger, pull the bank statement or third-party support, retrieve last month's signed reconciliation, and confirm the opening balance ties to last period's closing balance. If it doesn't tie, stop and resolve that gap before matching anything new.
- Match. Pull the current GL balance and independent support, then compare transactions line by line rather than netting totals against each other. Autopayables recommends closing subledgers first and reconciling against independent evidence like bank statements or signed contracts, not a report pulled from the same ledger you're trying to prove.
- Investigate. Every unmatched line gets a cause: timing, error, duplicate, or omission. This is where most of the actual accounting judgment happens.
- Adjust. Post a correcting journal entry for every real discrepancy and reference the JE number directly in the reconciliation file. Never force the schedule to balance by plugging a residual.
- Review and sign off. A second person, not the preparer, checks the evidence trail and signs with a date before the period locks.
That sequence sounds simple written out. What separates a clean reconciliation from a messy one is the documentation discipline layered underneath it, and that's the part worth walking through in detail.
Prepare: gather evidence before you touch the ledger
Before opening the reconciliation template, gather the bank statement or transaction export, the prior period's completed and signed reconciliation, invoices or receipts for anything unusual, and the relevant subledger report. Aviy's reconciliation guide points out that reconciliation moves faster when this evidence is collected upfront and the books are updated to match the statement date, rather than gathered piecemeal as questions come up mid-process.
Confirm the opening balance on the current reconciliation equals the closing balance signed off last period. A break here means either last month's reconciliation had an error that was never corrected, or someone posted an entry after the period locked. Either way, chase it down before moving forward, because an unexplained opening-balance gap invalidates everything that follows it.
Match: line by line, not total to total
Pull the GL balance for the account and set it beside independent support, whether that's a bank statement, a signed loan schedule, or a merchant processor report. Go line by line. A reconciliation that only compares ending totals will happily hide two offsetting errors that cancel each other out, and those are exactly the kind of errors that surface later in an audit sample.
Every transaction that doesn't have an immediate match becomes a documented reconciling item, not something you tuck into a rounding adjustment.
Investigate: build a case for every unmatched line
For each reconciling item, note the transaction date, amount, expected clearing date if it's a timing difference, and a plain-language explanation. Two numeric checks catch a disproportionate share of manual errors: if a discrepancy is evenly divisible by nine, suspect a transposition (swapped digits, like entering $981 instead of $918). If it's evenly divisible by two, check for a mistakenly added item where a subtraction was intended.
Adjust: correct the ledger, don't force the schedule
Post a journal entry for every confirmed discrepancy and write the JE number into the reconciliation itself. This step is where discipline separates from shortcuts. Plugging a residual to make the schedule tie without fixing the underlying entry doesn't resolve anything. It hides the error and lets it compound into future periods, which is exactly the pattern accounting researchers warn against when documenting best practices around correcting entries instead of forcing balances to match.
Review and sign-off: the control that actually matters
The reviewer checks that every reconciling item has evidence attached, that the math ties, and that the explanation for each item makes sense. Then the reviewer dates and signs the package, and the period locks.
Pro Tip: Name an owner and a due date on every reconciling item the moment you log it, not at month-end when you're trying to remember why a $340 item has been sitting open since October.
Operational hygiene ties this together. Every reconciliation should carry a named preparer, a named reviewer, a due date tied to the close calendar, and an aging column that flags any item open past 30 days for escalation to a controller or fractional CFO.
Which Accounts Need Reconciliation and How Often?
Not every account carries the same risk, so not every account needs the same reconciliation frequency. Cash and anything touching customer money need the tightest cycle; some schedules only need a quarterly or annual check.
- Bank and cash accounts: monthly at minimum, weekly for high-transaction-volume businesses where fraud or error compounds fast.
- Credit cards and merchant processors: monthly, aligned to the statement cycle; processor fees and chargebacks hide easily if left too long.
- Undeposited funds: monthly, and this one gets skipped constantly because it sits between two systems (POS and bank) and nobody owns it clearly.
- Accounts receivable control account: monthly, tied to the aging schedule, with unapplied cash resolved before close.
- Accounts payable control account: monthly, matched against the vendor subledger.
- Payroll liabilities: every pay cycle, because unremitted withholdings are a compliance exposure, not just a bookkeeping one.
- Loans and notes payable: monthly against the amortization schedule.
- Prepaid expenses: monthly, checking the amortization roll-forward against the schedule.
- Inventory: monthly for control account tie-outs, with physical counts on a quarterly or annual cadence depending on volume.
- Intercompany accounts: monthly, and these deserve extra attention below because they fail more often than any other account type.
Assign an owner and a service-level target (typically five to seven business days after period close) to each account type. Undeposited funds and intercompany balances are the two most commonly neglected lines on this list, largely because they don't map cleanly to a single subledger owner.
Diagnosing and Fixing Common Reconciling Items
Most reconciling items fall into a handful of repeatable categories, and each one has a standard diagnostic path.
Timing differences are the most common item on any bank reconciliation checklist. A deposit in transit or an outstanding check simply hasn't cleared yet. Document the expected clearing date and carry it as an open item rather than forcing it to zero out artificially.
Bank fees, interest, and processor charges show up on the bank statement before they hit the books. Scan for anything present on the statement but missing from the ledger, and record it immediately rather than waiting for the next statement to remind you.
Duplicate entries and transposition errors respond well to two quick tests: sort transactions by amount to spot exact duplicates, and check whether a discrepancy divides evenly by nine, a strong signal of swapped digits.
Missing transactions and wrong-period postings usually trace back to a subledger extract pulled with the wrong date range. Re-run the extract with the correct period boundaries before assuming the transaction is genuinely missing.
- Confirm the date range on every subledger extract before investigating further.
- Sort by amount to catch duplicates fast.
- Test discrepancies against the divisible-by-nine rule for transpositions.
- Flag anything on the bank statement not yet in the books, and book it the same day you spot it.
- Convert unresolved items into a tracked open-item list once they've aged past one cycle.
General ledger reconciliation guidance from Autopayables frames this as a fixed-order workflow: cut off the period, reconcile cash first, tie subledgers to the GL, then resolve every difference before anything gets reported externally. Skipping the order is how timing differences get mistaken for real errors, and real errors get written off as timing.
Set a hard threshold, often 30 or 60 days, past which an open reconciling item automatically escalates to a controller review rather than sitting on the preparer's list indefinitely.
Controls and Audit Readiness: Why Segregation of Duties Isn't Optional
Auditors treat an unreviewed reconciliation as a control gap, full stop. UCLA's corporate accounting control guidance is explicit that the preparer and reviewer must be distinct individuals, and a reconciliation lacking that separation gets flagged as a deficiency under frameworks like SOX, regardless of whether the numbers happen to be correct.
The evidence standard matters just as much as the separation itself. A reconciliation package that will survive an audit sample includes:
- Third-party or independent support attached to the file, not just an internal report.
- Date stamps showing when the reconciliation was prepared and when it was reviewed.
- Reviewer initials or a digital sign-off on the final package.
- A locked period once sign-off is complete, so nothing changes retroactively without a trail.
- Documented rationale for every reconciling item, including ones that clear before month-end.
Plugging a difference to force a tie is the single most damaging shortcut in this entire process. It doesn't just hide one error. It compounds, because next month's opening balance carries the same unexplained gap forward, and eventually nobody can tell which period actually introduced the discrepancy. Correct the ledger and document why, every time.
Pro Tip: If an auditor pulls a reconciliation sample, the first thing they check isn't the math. It's whether the reviewer's signature and date actually exist on the file.
Aging thresholds and escalation policies double as control evidence. A written policy stating "items open past 30 days escalate to the controller" shows an auditor the firm has a functioning process, not just a checklist that gets filled out and forgotten.
Where Automation Fits in the Reconciliation Workflow
Automation earns its place in the parts of reconciliation that are mechanical, not the parts that require judgment. Bank feed imports, rule-based transaction matching, evidence attachment, and open-item aging are the four candidates worth automating first, because they're high-volume, low-ambiguity tasks where a person adds little value beyond double-checking the machine's work.
- Start with bank feeds and auto-matching. Connect the account, let matching rules clear the obvious transactions, and route only the exceptions to a human.
- Pilot on one or two low-risk accounts. A single bank account or a credit card feed is a safer test bed than accounts receivable, where misapplied cash creates downstream customer disputes.
- Measure the false-positive rate before scaling. If the matching engine is auto-clearing transactions that shouldn't be cleared, tighten the rules before rolling out to higher-stakes accounts.
- Automate evidence attachment and aging next. Have the system pull supporting documents and flag items crossing your escalation threshold automatically.
- Keep reviewer sign-off manual, permanently. Automation should compress prep time, not replace the second set of eyes that makes a reconciliation defensible.
Done this way, automation strengthens the audit trail instead of weakening it: every match gets a timestamp, every open item ages automatically, and owner SLAs get enforced by the system rather than by someone remembering to check a spreadsheet.
- Automated feeds cut the manual data-entry time that used to eat the first half of close week.
- Auto-aging registers make escalation policy enforcement consistent instead of dependent on someone's memory.
- Faster matching frees reviewer time for the reconciling items that actually need judgment.
A Reconciliation Template You Can Copy Today
A usable reconciliation template needs the following fields, whether it lives in a spreadsheet or inside accounting software: account name, period, GL balance, independent support reference, reconciling items listed line by line, owner, due date, status, JE reference for any correcting entry, preparer name, reviewer name, and a field for attached documentation.
Two short examples show the template in action.
Bank reconciliation example: GL cash balance shows $48,200. Bank statement shows $47,850. The gap breaks down into a $600 deposit in transit (dated the last business day of the month, expected to clear in three days), a $310 outstanding check (issued but not yet presented), and a $60 bank fee not yet booked. Booking the $60 fee and carrying the other two as documented open items ties the schedule to $48,140.
AR control account example: GL accounts receivable shows $112,400 against an aging schedule total of $109,900. A $2,500 customer payment reduced the aging but was posted to a suspense account instead of the AR control account. Correcting the GL coding reduces AR to $109,900. Rerun both reports, confirm the tie, and retain the correction reference in the reconciliation file.
Both examples follow the same rule: identify, document, correct, tie, sign.
Closing the Books: Sign-Off and Escalation
Once every reconciling item has a resolution, or a documented open status with an owner and due date, the reviewer signs the package and the period locks.
- Confirm reviewer sign-off and attached evidence, then mark the reconciliation complete in whatever system tracks close status.
- Post all approved adjusting entries, re-tie the balance, and record every JE reference directly in the reconciliation file.
- Open a cleanup project for anything still unresolved past your policy threshold, with its own timeline and a named owner separate from the routine close cycle.
- Track close metrics month over month: average days-to-reconcile, the percentage of reconciliations signed on time, and the count of items still aging past threshold.
Those four metrics, tracked consistently, tell a controller or fractional CFO exactly where the close process is breaking down long before an auditor has to point it out.
Handling Foreign Currency Reconciliations
Foreign currency accounts add a variable that domestic reconciliations don't have to deal with: the exchange rate used to translate a balance can shift between the transaction date and the reporting date, creating a difference that has nothing to do with an actual error.
Separate rate-driven differences from true reconciling items from the start. If the GL balance and bank statement disagree on a foreign-denominated account, first check whether the ledger and the statement were translated using the same rate and the same date. A mismatch here is a translation issue, not a missing transaction, and it gets resolved with a currency translation adjustment, not a correcting entry to the underlying transaction.
Keep the rate source consistent and documented. Whether you use a spot rate, a monthly average, or a rate pulled from a specific provider, write down which one you used and when, because a reviewer checking the file six months later needs to be able to reproduce the math without guessing.
Intercompany balances denominated in foreign currency deserve extra scrutiny, since both entities need to agree not just on the transaction amount but on the rate applied to translate it. A common failure point is one entity booking a transaction at the transaction-date rate while the other books it at month-end rate, creating a phantom intercompany difference that has nothing to do with either ledger being wrong.
Realized and unrealized gains or losses from currency movement should sit in their own line item on the reconciliation, clearly labeled, so a reviewer can tell at a glance which portion of any variance is a rate effect and which portion is an actual unmatched transaction.
Why Discipline Beats Cleverness in Reconciliation
The firms that close clean every month aren't the ones with the smartest spreadsheet formulas. They're the ones that never skip a step, even when the numbers look close enough to eyeball. A checklist followed loosely under deadline pressure is worse than no checklist at all, because it creates a false sense that controls exist when they don't.
Sources
For segregation-of-duties standards, see UCLA's control practices guidance. For a ready-made template, download Johns Hopkins' monthly reconciliation checklist or review University of Florida's monthly reconciliation procedures.
This article is general information, not a substitute for advice from a qualified financial advisor. Consult a qualified financial professional about your own circumstances before acting on anything here.
- Segregation of duties control practices — UCLA Corporate Accounting
- General ledger reconciliation: process, example, checklist — Autopayables
- How to reconcile business accounts: practical guide — Aviy
FAQ
What Are the Five Steps to Reconcile an Account?
The five steps are prepare (gather statements and confirm the opening balance), match (compare GL to independent support line by line), investigate (assign a cause to every unmatched item), adjust (post correcting journal entries), and review with reviewer sign-off before locking the period.
What Is a Reconciliation Checklist?
A reconciliation checklist is the documented, ordered set of tasks and controls, preparation, matching, investigation, adjustment, and sign-off, that a preparer and reviewer follow to confirm a ledger balance against independent evidence.
What Are the Steps of Account Reconciliation?
Account reconciliation follows the same core steps as the general checklist: close the subledger and gather evidence, match transactions against independent support, investigate discrepancies, post correcting entries, and get reviewer sign-off before the period closes.
What Are the Seven Steps to Bank Reconciliation?
Bank reconciliation typically breaks into: confirm the opening balance, gather the bank statement, list deposits in transit, list outstanding checks, record bank fees or interest not yet booked, investigate any remaining differences, and obtain reviewer sign-off on the final tie-out.
How Often Should Businesses Reconcile Their Accounts?
Bank, credit card, and payroll liability accounts should be reconciled monthly at minimum, with high-volume cash accounts on a weekly cycle; prepaid, loan, and inventory schedules can often run monthly to quarterly depending on transaction volume.
Recommended
- AI for Accounting Firms: Build, Don't Buy
- AI in Finance: Boosting Team Productivity
- Boost Productivity with Agentic Workflows
Choose a next step
For accounting and CAS firm owners, a free, 20-minute Close Teardown is a place to discuss one typical close, repeated work, and where a build would not help. Ask for a one-page map and we send it within 48 hours, with no purchase required.
To record which AI providers already touch client work, use the free AI Register. It records provider exposure, agreement review, and cost evidence. It does not write an AI policy or approve a tool for client use.