Auditors need reconciliations that actually tell a story about the accounts, not a stack of numbers with faded initials. You’ll get further — and faster — if you treat reconciling the books as a risk-control exercise, not an administrative chore.
## General Ledger Reconciliation Best Practices For Audit Teams
Get the basics right. The point of general ledger reconciliation best practices is to reduce the chance that material misstatements slip through, and to make the evidence trail defensible. That starts with consistency: clear templates, consistent timing, and an owner for every balance. It sounds mundane, but when every account follows the same rhythm and format, anomalies pop up quickly.
Use a risk-based cadence. High-risk accounts (cash, intercompany, accruals, payroll) deserve monthly attention. Lower-risk, low-balance control accounts can be quarterly. Maintain a simple schedule document that ties each account to a frequency and an owner. This single document becomes your first line of defense during fieldwork.
Make sure the reconciliation process feeds your audit workpapers. If the reconciliations are done so they can be reviewed remotely, with hyperlinks to supporting documents, you save time and reduce requests for additional evidence. In short: build reconciliations for auditors, not for the sake of form.
### Define Clear Ownership And Segregation Of Duties
Assign a single accountable person per account, and a separate reviewer. If one individual prepares and approves a reconciliation, you’ve lost segregation of duties — and you’ve weakened internal controls. For example, the person who posts journal entries should not be the same person who signs off on that account’s reconciliation.
Spell out responsibilities in a short one-page policy. It should say who prepares, who reviews, what evidence must be attached, and the expected turnaround for clearing reconciling items. Hold monthly sign-off meetings where outstanding issues are discussed. That forces transparency and creates a documented trail of who knew what, and when.
### Standardize Templates And Reconciliation Procedures
Standard templates make reviews predictable. A solid template includes beginning and ending balances, a list of reconciling items with dates and descriptions, substantiating documents, aging of items, and a clearance plan. Include a column for the preparer and the reviewer’s initials and dates.
Provide examples in the procedure manual. Show a properly completed bank reconciliation, an intercompany reconciliation, and one for a payroll clearing account. Examples set expectations. Train new staff by walking them through real reconciliations that passed audit scrutiny. Avoid vague checklists; show the artifacts you expect.
### Use Automation, But Don’t Blindly Trust It
Automation reduces error and saves time. Rules-based matching for bank feeds, automated intercompany netting, and reconciliation tools that pull balances from the ERP can shave hours off routine work. But automation is not a substitute for judgment.
Monitor the configuration of your tools as part of IT general controls. Reconcilements that appear to clear automatically should still be spot-checked. An automated match could be based on a wrong mapping or a stale exchange rate. Treat the reconciliation tool’s results as helpful intelligence, not gospel.
Reconcile Suspense And Clearing Accounts Regularly
Suspense and clearing accounts are quiet places where errors accumulate. Reconcile them every month and enforce an aging threshold: items older than a set period (e.g., 90 days) must escalate to a supervisor. Maintain a clearance plan for each aged item: who will investigate, what documentation is needed, and what the expected resolution date is.
Document Reconciling Items And Aging
Record the root cause for reconciling items. Was it timing, a posting error, a duplicate invoice, or missing approval? That diagnosis matters. If aging shows recurring categories, the issue may be a process flaw, not one-off mistakes. Capturing cause-and-effect helps you recommend practical remediation rather than temporary fixes.
## Practical Audit Procedures For Tricky Accounts
Some accounts are routine; others need judgment. Here’s how to approach the ones that give auditors the most grief.
Cash: Trace bank balances to bank confirmations and the cutoff bank statement. Recalculate cleared items and test deposits-in-transit near period end. If lockbox or sweep arrangements exist, verify that swept balances are correctly reflected.
Intercompany: Verify that both sides agree on the balances and that eliminations happen in consolidation. Focus on reconciling differences in functional currency, and ensure there’s a documented timeline for matching claims from both subsidiaries.
Fixed Assets And Depreciation: Tie additions to vendor invoices and capital authorization. For disposals, review board minutes or asset retirement approvals. Reconcile accumulated depreciation roll-forwards to the depreciation schedule.
Accruals And Estimates: Test supporting calculations for reasonableness and consistency with prior periods. For major estimates, review the methodology and any subsequent events that support or contradict the estimate. Re-run the math — small spreadsheet errors cause big problems.
Throughout, apply a materiality lens. Not every small variance requires the same level of investigation. But document why you considered a reconciling item immaterial. That note saves time on rework when your manager reviews the file.
### Sampling Approaches And Evidence To Gather
Choose samples that focus on risk, not convenience. For a reconciling item population, stratify by balance size and age. Test more heavily where dollar value concentrates or where items are older. For each sampled reconciling item, collect source documents: invoices, bank advices, cash receipt logs, intercompany confirmations, and approval emails.
Use confirmations where practicable. Bank confirmations and third-party receivable confirmations remain powerful evidence. For intercompany balances, a confirmation that’s sent and returned by the counterparty is far stronger than a one-sided internal memo.
### How To Handle Old Reconciling Items
Old items smell like process breakdowns. Don’t let them linger. If the item is old and can’t be supported, require management to either reclassify it, make a correcting entry, or provide documented rationale to retain it. For balances that require write-offs, ensure approvals follow policy and are reflected in the accounting records with accompanying narratives in the working papers.
When management proposes a correction, test the correction: will it properly reflect the period affected, and is it consistent with accounting policy? If management resists correction, document the conversation and the basis for your recommendation.
## Maintaining Audit Trail And Documentation
Good documentation is defensive. Keep reconciliations version-controlled, with dates and sign-offs. If a reconciling item is cleared, attach the clearing journal entry and proof of execution. The audit file should show the full lifecycle from initial discrepancy to resolution.
Use folder naming conventions and timestamps. If teams work across locations, require that uploaded supporting documents show metadata (date created, author). That avoids disputes over whether evidence existed at period end.
### Communicate Findings And Build Better Controls
Auditors should not only detect problems but describe practical remedies. When you find recurring reconciling items, map those items to a process failure — for instance, invoice approvals bypassed or mismapped GL codes — and recommend a specific internal controls change. Suggest process owners, deadlines, and a monitoring plan.
Follow up. After recommending a control change, ask for evidence of implementation on a timeline. A one-off comment in an engagement memo is not enough. Effective auditors close the loop.
Make your recommendations incremental and testable. Instead of “fix intercompany process,” propose “implement a monthly intercompany close checklist, with automated notifications and a 15-day SLAs for matching balances.” Concrete steps get implemented. Vague ones do not.
Keep the conversation practical. The goal is reliable financial reporting, not bureaucracy. When proposing controls, balance rigor with the day-to-day realities of the accounting team. A control that doubles the workload rarely survives.
One more thing: watch for too many reconciliations that are perfectly clean because the preparer cleared minor items by booking recurring manual entries. That can mask underlying mismatches. Spot-check the entries and ask for supporting documents. If the same manual working entry appears each month, you’ve likely created a recurring patch, not a reconciling solution.
Recociliation is boring only when it’s working well. When it’s not, it’s where material problems hide. Use the techniques above to make recon processes tight, auditable, and useful — not just a compliance checkbox.
