What auditors look for in a reconciliation — and how to be ready before they ask

Someone on r/Accounting finally asked the quiet question out loud — "Why do accountants hate reconciliations?" — and the thread mostly answered with a shrug. Here is the part that actually helps you: an auditor is not checking whether your reconciliation balances. They are checking whether you can prove it. A clean zero with no trail behind it is worth almost nothing to them; a small, explained, supported difference is fine. The work that makes a reconciliation hold up is the exact work people skip when they are racing the close — naming every reconciling item, backing it with a document, and getting a second set of eyes on it. Do that during the month and year-end stops being a fire drill. Here is what auditors actually look for, item by item, and how to leave the trail as you go.

What is an auditor actually testing?

Start with the thing most explanations get wrong. The auditor is not re-performing your reconciliation to see if they land on the same number. They are testing whether the reconciliation worked as a control: does the general ledger balance tie to an independent source, are the differences between them identified and explained, and is there evidence that a competent person checked the work. A reconciliation is only doing its job when it answers all three.

This is why "it reconciles, I checked" is not an answer. Public-company audit standards are explicit on the point — under the PCAOB's audit-evidence standard, asking a person whether something reconciled does not, on its own, count as sufficient evidence. The reconciliation has to stand on documents, not on your word. That single idea drives everything an auditor asks for next.

A balanced reconciliation and an audit-ready one are not the same thing

Here is the trap, and it is worth saying plainly: a reconciliation that nets to zero can still be wrong, and a green checkmark can hide the error that sinks you. A commenter on a thread about reconciliations that "say MATCHED but hide duplicates" described it exactly — they "stopped trusting the green checkmarks in standard reconciliation templates" and "learned the hard way when auditors found duplicate vendor payments that looked clean because amounts offset perfectly" (r/Accounting). Two offsetting errors net to zero. A duplicate payment and a missed credit cancel out. The total ties and the detail is garbage.

The opposite failure is just as common: making the number tie by force. When a close gets compressed, the temptation is to "stop reconciling the small stuff" — a habit a skeptical reply on an FP&A thread flagged as "cutting corners on the audit trail." A round-number plug labeled "adjustment to balance" is not a reconciled account; it is an unexplained difference wearing a disguise, and it is one of the first things a reviewer pulls.

The duplicate-payment case is not rare, and it is catchable. Offsetting amounts are exactly what slips past one-to-one matching, which is why catching them is a fuzzy-matching problem, not a "look harder" problem. The reconciliation that survives an audit is the one where the total ties and every line under it is real.

The five things an auditor wants to see

Strip away the jargon and an audit-ready reconciliation has five parts. Miss any one and the reconciliation is, in audit terms, incomplete — even when the math is perfect. This is the checklist a reviewer runs, so run it on yourself first.

Institutions that get audited constantly publish exactly this expectation. Yale's balance-sheet reconciliation and certification policy and Stanford's account reconciliation and attestation guidance both require the same shape: compare the ledger to an independent source, document and support every reconciling item, and have someone other than the preparer certify it. If you want a free, specific model, those two are it.

The reconciling items that draw the most scrutiny

Auditors do not spread their attention evenly. A few kinds of reconciling item get pulled first, because they are where errors and fraud hide. Know them and you know where to spend your own review time.

• Stale items. A difference carried forward 60 or 90 days with no owner and no resolution path reads as an unresolved error — or worse, something nobody understands anymore. Age every open item and chase the old ones.
• Round-number plugs. Anything that exactly offsets the difference — a tidy "$1,200.00 adjustment to balance" — invites the question you do not want: what is this, really?
• Offsetting pairs. Two items that cancel to zero, like a duplicate charge and a missed credit, can mask two separate mistakes. A net of zero is not proof the detail is clean.
• Items cleared with no note. Clearing a difference during a busy close without writing down why creates a gap that compounds; by year-end nobody remembers, and the auditor is the one left asking.
• Differences you created on the bank side. In a well-run book the bank is rarely the source of an entry, so a reconciling item that traces back to your own duplicated or miscoded posting is more concerning than a genuine timing difference like an outstanding check.

Who signs off — and why it cannot be the same person

The single control auditors check most reliably is also the one small teams skip most often: the person who prepares the reconciliation should not be the person who approves it. This is separation of duties, and it exists because a second independent look catches honest errors and deters the dishonest ones. A reconciliation with no reviewer is, to an auditor, a reconciliation that no control operated on.

A former auditor answering a bookkeeper on r/Bookkeeping put the same point bluntly: "You shouldn't be the sole decision maker!" Their advice for an audit was concrete — show "where the transactions are happening" and "how they get into the books," and be ready to "export PP activity to Excel, group it together, and show how it all reconciles." That is the whole game: a documented path from the source system to the general ledger, checked by someone other than you.

On a one- or two-person team, true separation is hard — but "hard" is not "skip it." The reviewer can be an owner, an outside accountant, or a manager who spends ten minutes scanning the reconciling items and initials the work. What matters to the auditor is evidence that a second person actually looked, not who they report to. And this is the one part an AI agent cannot do for you — a model can prepare and explain a reconciliation, but it cannot be the independent human accountable for approving it.

How to leave the trail during the month, not at year-end

The reason year-end audits hurt is that the trail gets reconstructed under pressure, months after the memory faded. The fix is boring and it works: leave the trail as you close each month. None of these steps needs a tool — they need a habit.

1. Save the source with the reconciliation — the bank statement, the processor or payout report, the subledger export you reconciled against. Store it next to the rec, not in someone's inbox.
2. Write one line of explanation per reconciling item, with a reference to its support. "Outstanding check #1042, cleared 4/3" beats "timing" every time.
3. Log open items and age them. Keep a running list of unresolved differences with a date opened and an owner, so nothing silently becomes a stale item.
4. Get the review in the same close cycle. A reviewer who signs off three months later is not a control. Book the ten minutes while the detail is fresh.
5. Store it where a stranger could find it. The test for a clean audit trail is simple — could someone who has never seen the account follow your reconciliation from the GL back to the source without asking you a single question?

This is the same discipline behind a sound bank reconciliation and a sequenced month-end tick-and-tie — do the work in order, leave evidence at each step. If your systems never shared a clean primary ID, the trail is also where you show how you bridged them, which is precisely what an auditor needs in order to trust the match.

Do subledgers like AR and AP need to be reconciled to the GL?

Yes — and it is a standard audit ask that surprises people. A NetSuite user asked the exact question — Is it necessary to "reconcile" subledger reports? — assuming the aged AR and AP subledgers would always equal the balance sheet. They usually do, and "usually" is the point: when the aged subledger does not tie to its GL control account, something posted to the control account outside the subledger — a manual journal entry, a misposting — and that gap is exactly what an auditor wants explained. Tie the subledger to the GL every close and the difference, if any, is a short list instead of a year-end mystery.

None of this requires software. It requires leaving a trail you would be willing to hand to a stranger. A reconciliation that explains itself — every item named, supported, and reviewed — is the whole job, whether a person, a spreadsheet, or a tool produces it. Build that habit monthly and the audit becomes a formality instead of an excavation.

← All writing