Try it while you read
This is the tie-out board Reconciler gives you: both sides side by side, matches explained in plain English, exceptions flagged. Read-only, and it never moves money.
Read-only · Never moves money
General ledger reconciliation is the process of confirming that the balance recorded in each general ledger account agrees with the independent source data behind it, such as a bank statement, a subledger, a payout report, or a schedule, and that every difference between the two is identified and explained. You compare the GL balance to its support, list the differences, correct the errors, document the timing items, and sign off. When every material account is supported and every variance is explained, the general ledger is reconciled.
Last updated July 2026.
The general ledger is the account of record for everything your business did financially. Every other report you produce, the balance sheet, the income statement, the numbers you hand to a lender or a board, is a rearrangement of it. If the ledger is wrong, everything downstream inherits the error, and because balance sheet accounts carry forward, a small unreconciled difference in March is still sitting there in December, only now it has company.
How do you reconcile a general ledger?
You reconcile a general ledger by pulling each account's ending balance from the trial balance, comparing it to the independent detail that should support it, listing every difference, resolving each one as either a timing item or an error, posting corrections, and documenting the result with the supporting evidence attached. The workflow is the same for every account, which is what makes it possible to run it at scale.
- Freeze the period. Decide the cutoff and stop posting to the period you are reconciling. Reconciling against a moving balance is how teams end up doing the work twice.
- Pull the trial balance. Take the ending balance for every account you intend to reconcile, straight from the GL, not from a copy someone made last week.
- Gather the supporting detail. Cash ties to the bank statement, receivables to the AR aging, payables to the AP aging, credit cards to the card statement, processor receivables to the payout report, prepaids and fixed assets to their schedules.
- Match at the transaction level. Compare individual items, not just totals. Two balances can agree while both sides contain offsetting errors, and a total-only check will never find that.
- Classify every difference. Each variance is a timing item that will clear on its own, an error that needs a journal entry, or something you do not yet understand. The third category is the one that matters, and it never gets rounded away.
- Post corrections and document. Journal the errors, attach the support, record who reviewed it and when, and sign off. A reconciliation nobody can retrace six months later has not really been done.
What is the difference between general ledger reconciliation and bank reconciliation?
Bank reconciliation is one specific general ledger reconciliation: it ties the cash account in the GL to the bank statement. General ledger reconciliation is the broader discipline of tying every material GL account to whatever independently supports it, which includes cash but also receivables, payables, credit cards, clearing accounts, inventory, prepaids, fixed assets, accrued liabilities, and debt.
The distinction matters because teams that only reconcile the bank often believe the books are clean when they are not. Cash is the easiest account to prove and the least likely to hide a problem, precisely because a third party sends you a statement every month. The accounts that quietly go wrong are the ones with no external referee: clearing accounts that never clear, a processor receivable that grows every month, accrued liabilities that were set up once and never reversed. We go deeper on the boundary between the two in our guide to bank reconciliation vs account reconciliation.
Which accounts should be reconciled to the general ledger?
Reconcile every account with volume, movement, or risk every month, and review the rest on a longer cycle. In practice that means cash, credit cards, receivables, payables, clearing and suspense accounts, payment processor receivables, inventory, prepaids, fixed assets and accumulated depreciation, accrued liabilities, payroll liabilities, and debt get reconciled monthly. Low-activity equity accounts can be reviewed quarterly and reconciled fully at year end.
| GL account | What it ties to | What usually goes wrong |
|---|---|---|
| Cash | Bank statement | Deposits in transit, outstanding checks, unrecorded bank fees |
| Credit cards | Card statement | Uncoded charges, duplicates, personal spend, unbooked annual fees |
| Accounts receivable | AR aging | Unapplied cash, credit memos issued but never journaled |
| Accounts payable | AP aging and vendor statements | Duplicate bills, invoices received after cutoff |
| Processor receivable | Stripe, PayPal, or Square payout report | Fees netted inside the payout, refunds and chargebacks never split out |
| Clearing and suspense | Should net to zero | Items parked there and forgotten, so the balance only grows |
| Prepaids and fixed assets | Amortization and depreciation schedules | Schedule and GL drift apart after a manual entry |
What causes general ledger discrepancies?
Most GL discrepancies come from a short list of causes: timing differences where one side has recorded a transaction and the other has not yet, duplicate postings, transactions coded to the wrong account, amounts entered incorrectly, missing entries for items that never reached the ledger such as bank fees or interest, and net amounts booked gross where fees were deducted before the money landed.
Fraud is on the list too, and it is the reason reconciliation is a control rather than an accounting chore, but the boring causes account for the overwhelming majority of differences. That is useful, because boring causes are systematic, and systematic problems can be caught by software instead of by a person reading rows at 9pm.
How often should the general ledger be reconciled?
Reconcile material accounts monthly, as part of the close. Monthly is the cadence that keeps each reconciliation small enough to actually finish, and small reconciliations are what keep the ledger trustworthy. High-volume accounts such as cash, cards, and processor receivables benefit from a weekly or even daily pass, because catching a duplicate charge in week one costs a minute and catching it at year end costs an afternoon of forensic work.
The teams with the fastest closes are not the ones who work faster during close week. They are the ones who arrive at close week with cash, cards, and processors already tied out, which turns the close into a review instead of an investigation.
A worked example
Say the GL shows a Stripe receivable of $18,420.00 at month end and the Stripe payout report shows $17,905.00 still in transit. A $515.00 difference. Total-only checking tells you there is a gap and nothing else. Matching at the transaction level shows what it is made of: $390.00 of processing fees booked gross in the ledger when the payout arrived net, a $150.00 refund recorded in Stripe but never journaled, and a $25.00 chargeback nobody had seen yet. Two journal entries and one investigation later, the account ties and you have learned something real about the month, which is the actual point of reconciling.
Automating the transaction-level matching
The judgment in general ledger reconciliation, deciding whether a variance is a timing item or an error, is genuinely accounting work. The matching underneath it is not. Comparing thousands of ledger lines against bank lines, card charges, and payout components is mechanical, and mechanical work done by tired people at month end is where errors get introduced rather than found.
That matching layer is what automated transaction matching handles. Reconciler connects your bank feeds, corporate cards, payment processors, and your ledger read-only, scores each candidate pair on amount, date, memo, and reference, and writes a plain English reason for every match, so a reviewer approves the confident batch and spends their attention on the handful of items that genuinely need a decision. Getting the source data in is its own small chore, and if your bank only gives you a PDF, it is worth turning that statement into a clean transaction file before anything else.
It stays read-only by design. Reconciler never moves money and never posts an entry on its own, a person reviews every exception, and every match, flag, and approval is recorded as an audit trail your auditors can follow. It sits on top of QuickBooks, Xero, NetSuite, or Sage Intacct, so nothing migrates and your ledger stays the system of record. If you want the account-level view that sits above this, start with balance sheet reconciliation, and if you want to compress the whole cycle, our month end close checklist lays out the order of operations.
Whatever tool you use, the standard is the same. Every material account tied to independent support, every difference classified and explained, nothing plugged, and the whole thing documented well enough that a stranger could follow it. Hold that line every month and the general ledger stops being a place where surprises accumulate.
This article is for general information and is not financial or tax advice. Consult your accountant about your specific situation.
See your accounts tie out to $0.00
Connect your bank, processors and ledger read-only. Reconciler matches transactions, flags what does not add up, and explains every match, so your books close faster. Read-only, never moves money.