A step-by-step guide to get accounting reconciliation right

Accounting reconciliation is the process of comparing two sets of financial records to confirm they agree. That means matching your internal books against external statements, third-party reports, or subsidiary ledgers to verify that every transaction is accounted for and the ending balances are correct.

Reconciliation catches errors before they compound, surfaces unauthorized transactions, and gives your team confidence that the numbers in your financial statements reflect reality. The number of accounts a controller reconciles each month varies widely depending on entity structure and transaction volume. A small company might reconcile a handful of accounts while a multi-entity business can face dozens across cash, payables, receivables, and intercompany accounts.

Reconciliation sits at the core of the financial close process. If reconciliation runs late, everything downstream shifts with it, from internal reporting deadlines to external audit timelines. Getting reconciliation right means getting the close right, and that starts with a repeatable process.

The mechanics of reconciliation are straightforward, but execution breaks down when teams skip steps or rely on inconsistent methods. A standardized process can prevent that drift.

Step 1. Identify the accounts to reconcile

Pull the internal ledger balance for the account you're reconciling and obtain the corresponding external statement. For a bank reconciliation, that means your GL cash balance and the bank statement for the same period. For vendor accounts, you'll need the accounts payable (AP) subledger and the vendor's statement of account. Organize everything by account in your chart of accounts so nothing gets skipped.

Step 2. Compare internal balances to external statements

Line up both records and match transactions one by one. Start with the ending balances and work backward through individual line items. Flag anything that appears in one record but not the other, including timing differences like outstanding checks or deposits in transit.

A clean match means the account is reconciled, while any gap moves to Step 3. Sorting unmatched items by dollar amount before investigating saves time because resolving a few large items often accounts for the entire variance. Most teams run this comparison in a spreadsheet or their enterprise resource planning (ERP) system's reconciliation module, though the format matters less than the discipline of documenting every unmatched item.

Step 3. Investigate discrepancies

Every unmatched item needs an explanation. Common causes include data entry errors, duplicate postings, timing differences between when a payment is recorded and when it clears, and transactions recorded in the wrong period. A $4,500 vendor payment recorded in the GL on March 31 but not clearing the bank until April 2 is a timing difference, not an error, but you still need to document it. Teams that categorize discrepancies by type (timing, error, fraud, missing documentation) resolve them faster because each category has a different resolution path.

Prioritize by dollar amount and age of the item. Duplicate postings in particular are worth flagging early. Stopping them at reconciliation is far less costly than discovering them during an audit. The most reliable way to reduce duplicate postings is to tighten controls upstream in accounts payable before they ever reach the reconciliation stage.

Step 4. Make adjusting entries

Post journal entries for any legitimate corrections. If a bank fee of $35 wasn't recorded, book it. If a duplicate invoice was accrued or expensed in error, reverse the duplicate accounting entry. If a duplicate payment actually left the bank, record the proper vendor receivable or credit and pursue recovery rather than simply reversing the cash entry. Every adjusting entry needs a clear description and supporting documentation attached to the journal entry in your ERP.

For teams still tracking these manually, a guide on common accounting errors can help you spot patterns worth correcting at the source. Fixing the current period's entries matters, but identifying the systemic issues that produce the same error month after month is what actually moves the needle.

Step 5. Document the reconciliation

Save the completed reconciliation with all supporting evidence, including the original comparison, discrepancy notes, adjusting entries, and the final matched balance. This documentation is what auditors review, and incomplete records are one of the most common triggers for audit findings.

Step 6. Review the completed reconciliation

A second person reviews the completed reconciliation before it's marked final. This separation of duties is a core component of internal controls over financial reporting. Reconciliations typically need documented preparation, review, and evidence that the control operated. Where staffing makes full segregation impractical, compensating controls should be documented. Companies with strong internal controls catch errors that the original preparer missed because a fresh set of eyes approaches the data without assumptions.

Reviewer sign-off should occur within the company's documented close calendar, typically within one to two business days for high-risk accounts. Delays in the review cycle are one of the top reasons reconciliation backlogs build up.

Your staff accountant pulls the March bank statement on April 3, showing an ending balance of $1,247,832.15. The GL shows $1,243,617.15 for the same account. The $4,215 difference breaks down into three items: two outstanding checks totaling $3,900 that hadn't cleared the bank by March 31, and a $315 bank interest credit posted on March 28 that was missing from the GL.

The accountant records the $315 interest credit as an adjusting entry, bringing the GL up to $1,243,932.15. The bank statement balance of $1,247,832.15 less the $3,900 in outstanding checks also equals $1,243,932.15. The account reconciles.

That $315 missing entry would have compounded if left unresolved. Small unrecorded items can accumulate across accounts and periods, and depending on company size, qualitative factors, and aggregation with other errors, they may contribute to audit adjustments or control findings. Catching them in real time keeps the close on schedule and the audit trail clean.

Not all reconciliations follow the same playbook. The data sources, frequency, and complexity vary depending on which accounts you're matching. Finance teams typically handle several of these each close cycle, and knowing the differences helps you allocate time and resources appropriately.

Bank reconciliation

Bank reconciliation matches your GL cash balance against the bank statement to identify outstanding checks, deposits in transit, and unrecorded bank fees. Most companies reconcile bank accounts monthly, though high-volume businesses do it weekly.

The most frequent discrepancy source is timing. A payment initiated on the last business day of the month often won't clear for one to three business days, creating a gap that resolves itself but still requires documentation.

Vendor reconciliation (accounts payable)

Vendor reconciliation compares your AP subledger against each vendor's statement of account to confirm all invoices, payments, and credits are recorded on both sides. This matters most for vendors with high transaction volume, where a single missed invoice can cascade into duplicate payments or strained vendor relationships.

Customer reconciliation (accounts receivable)

Accounts receivable (AR) reconciliation ties the AR subledger to the GL control account, using cash receipts, remittance advices, credit memos, and aging analysis to investigate and resolve differences. The core challenge is cash application, specifically matching incoming payments to the correct open invoices when customers pay multiple invoices with a single remittance or short-pay disputed line items.

A company with $2M in monthly receivables and 150 active customers might have a significant number of unapplied payments at any given time. Each one needs investigation to determine whether it's a timing issue, a customer dispute, or a recording error. Tracking your accounts receivable aging helps you identify which customers consistently generate exceptions so you can address root causes.

Corporate card reconciliation

Corporate card reconciliation matches card transactions against receipts and GL expense entries. This is one of the highest-volume reconciliation types for companies with distributed spending, and the one most likely to generate exceptions from missing receipts, miscoded expenses, or personal charges slipping through.

Intercompany reconciliation

Intercompany reconciliation matches transactions between subsidiaries or business units within the same parent company so that consolidation entries can eliminate them. When one entity invoices another for shared services, management fees, or intercompany loans, both sides need matching entries before the consolidation can proceed cleanly. A $150,000 management fee recorded as revenue by the shared services entity needs a corresponding $150,000 expense on the receiving entity's books.

The complexity scales with entity count. A company with three entities might handle 10 to 15 intercompany transactions per month, while a company with 20 entities across multiple currencies can face hundreds. Each requires conversion rate alignment and elimination entries during consolidation. Timing mismatches are the primary challenge because entities often close on slightly different schedules.

Balance sheet reconciliation

Balance sheet reconciliation verifies that every account on the balance sheet ties to supporting documentation. Prepaid expenses should match amortization schedules. Accrued liabilities should match to underlying contracts or calculations. Fixed assets should reconcile to the depreciation schedule and physical asset records. This is often the final reconciliation before a company can certify its trial balance is complete and accurate.

Bank reconciliation is largely mechanical and benefits the most from automation. Intercompany and balance sheet reconciliations involve multiple data sources and subjective judgment calls, which is why they tend to take the longest to resolve.

Not every account needs the same level of attention each close cycle. Prioritizing based on risk and volume helps your team focus effort where it matters most.

Transaction volume and materiality thresholds

Accounts with the highest transaction volume are the most likely to contain errors simply because there are more opportunities for something to go wrong. A corporate card program processing 2,000 transactions per month needs more frequent reconciliation than a prepaid insurance account with one entry per quarter. Start with high-volume, high-dollar accounts and work down.

Materiality thresholds need to be risk-based and consider both quantitative and qualitative factors. Many companies use preliminary percentage screens as a starting point, but thresholds should be documented and aligned with audit expectations rather than applied as a fixed rule. What's material for a company with $10M in assets may be immaterial for one with $500M, and qualitative factors like fraud risk, covenant compliance, or trend effects can make smaller amounts significant. Set and document your thresholds with your auditors before the close begins.

Audit exposure

Some accounts attract more audit scrutiny than others. Revenue recognition accounts, cash and cash equivalents, debt balances, and intercompany accounts are near-universal audit focus areas. If your company is preparing for an external audit, reconcile these accounts first and with the most thorough documentation. The cost of remediation when auditors flag a control deficiency far outweighs the time spent on thorough reconciliation upfront.

Historical error frequency

Track which accounts produce the most discrepancies over time. An account that generates adjusting entries three months in a row has a process problem worth investigating. The issue might be a recurring timing difference that a cutoff procedure change could eliminate, or a data entry pattern that needs additional controls. Tracking accounts payable metrics alongside reconciliation results helps you spot which vendors or processes generate the most rework. Accounts with consistently high error rates deserve monthly reconciliation even if their dollar balances don't meet your materiality threshold.

Reconciliation itself is straightforward. The mistakes that derail it are usually process failures, not technical ones.

Waiting until month-end to start

Most reconciliation delays trace back to a single pattern. The finance team treats reconciliation as a month-end task rather than a continuous process. By April 1, they're staring at 30 days of unmatched transactions across every account, and the first week of close turns into triage.

Shift to rolling reconciliation. Reconcile bank accounts weekly. Match corporate card transactions against receipts as they post, not at statement close. Run AP reconciliation against your top vendors by the 15th. By the time month-end arrives, a significant portion of the work is already done, and your team is only handling the final cutoff entries and timing items. A solid month-end close checklist makes this cadence repeatable. The close shifts from a sprint to a checkpoint.

Reconciling from a single data source

Reconciliation by definition requires two independent data sources. Matching your GL cash account against your own cash receipts log doesn't verify anything because both records originate from the same system. If the original entry was wrong, the comparison will still show a match.

Every reconciliation needs an external or independently prepared source. For cash, that's the bank statement. For AP, that's the vendor's statement of account. For accounts without an external counterpart, such as prepaid expenses or accruals, the support should be an independently prepared amortization schedule, contract, or subsequent invoice that doesn't simply duplicate the GL posting. Support used to verify a balance shouldn't originate from the same entry being tested. Teams that skip this are performing a review, not a reconciliation, and the distinction matters when auditors test your controls. A $12,000 duplicate payment that clears a single-source reconciliation will surface during an external audit, along with questions about why your process didn't catch it.

Even automated reconciliation tools can mask this problem if they're configured to match GL entries against GL entries in a different subledger. Always verify that your matching logic crosses at least one system boundary, just as invoice matching requires purchase orders, receiving reports, and invoices as independent verification points.

Skipping documentation on cleared items

A $7,500 discrepancy that gets investigated, explained, and resolved without documentation produces no audit value. Auditors don't just want to see that the account reconciles today. They want to see the trail of how you got there, including what didn't match initially and what you did about it. Teams that clear items without notes during busy periods create a documentation gap that compounds. By year-end, your auditors are asking about 50 undocumented reconciling items, and nobody remembers why they were cleared.

Efficient reconciliation requires consistency and structure, not heroic effort at month-end.

Standardized reconciliation templates

Create a single template for each reconciliation type that includes the account name, period, preparer, reviewer, beginning and ending balances, reconciling items, adjusting entries, and sign-off fields. When every reconciliation follows the same format, reviewers spend less time figuring out what they're looking at and more time evaluating whether the work is correct. Templates also make it easier to train new team members and maintain quality when someone is out of office. Reviewing your accounts payable best practices alongside your reconciliation templates ensures documentation standards are consistent across the AP workflow.

Rolling reconciliation schedules

Map every account to a reconciliation frequency (weekly, monthly, quarterly) based on the decision criteria covered earlier. Assign owners and deadlines in a shared tracker. The goal is to convert reconciliation from a month-end fire drill into a distributed workload. Historical benchmark data from the American Productivity and Quality Center (APQC) put the median monthly close at 6.4 calendar days across more than 2,300 organizations, with top-quartile companies closing in 4.8 days or fewer. Finance teams that adopt rolling close practices consistently cut into that timeline, with three-to-five day closes achievable for some teams depending on systems, transaction complexity, and process maturity.

Automated matching rules

Configure your accounting software or reconciliation tool to auto-match transactions that meet exact criteria, such as matching amount, date within a specified tolerance window (typically three to five business days), and reference number. Automated matching handles the majority of straightforward transactions, freeing your team to focus on the exceptions that require judgment, though actual match rates depend on data quality, transaction complexity, rule configuration, and exception thresholds. Even at more conservative match rates, automation meaningfully reduces the manual workload each close cycle. Teams looking to automate accounting processes more broadly can apply the same logic to journal entry posting and intercompany eliminations.

Exception-based review workflows

Instead of reviewing every matched transaction, build a workflow where reviewers focus only on exceptions: items that couldn't be auto-matched, items above a dollar threshold, or items flagged by matching rules as potential duplicates. This approach scales with transaction volume because the review workload grows with complexity, not with total count. A company processing 5,000 transactions might generate only a few hundred exceptions worth human review, turning a multi-day process into a few focused hours.

Finance teams buried in reconciliation spreadsheets aren't just losing hours. They're losing the time they'd otherwise spend on cash forecasting, vendor negotiations, and financial planning. Every hour chasing a missing receipt or manually coding a GL entry is an hour pulled from work that actually moves the business forward.

With Brex, GL coding is automated through mappings and rules, including rules tied to spend limits or p-card setup, which means the coding work happens before your team opens the reconciliation workpaper. Where spend limits and policy rules are configured, out-of-policy spend can be flagged or blocked before it posts, so your team reviews fewer exceptions. For teams managing expense reconciliation across multiple entities, that distinction determines whether adding 50 new cardholders means 50 more hours of monthly reconciliation work or roughly the same workload with better data.

The same logic applies to invoice reconciliation workflows where automated approval routing keeps vendor payments accurate without manual intervention at close. Learn more about how accounting automation can change what your close looks like, or get started for free to see what your close looks like when reconciliation becomes continuous and exception-based rather than a month-end scramble.

This article reflects Brex's perspective at the time of publication and is intended for general informational purposes. Information may change over time.

This content is for informational purposes only and isn’t intended as legal, tax, accounting, or financial advice. Laws and guidance can vary based on your specific situation, and results or interpretations may differ. It’s always a good idea to consult your own qualified legal, tax, accounting, or financial advisors before making decisions.