Your A/R aging doesn’t match your balance sheet

Your balance sheet says accounts receivable is one number. The A/R aging summary says another. Both are produced by QuickBooks from the same file, and they are describing the same account — so one of four things is happening.

Three are settings. Rule those out first, because they take about a minute and they account for most cases.

The three settings

1. The aging report defaults to today

This is the single most common cause and the easiest to miss. The A/R aging summary defaults to the current date, regardless of what date you ran the balance sheet for.

Run a balance sheet as at 31 August and an aging report today, and of course they differ — a month of invoicing and collection sits between them. Set the aging report's date to match the balance sheet date.

2. The two reports are on different accounting bases

The balance sheet can be run on cash or accrual. The aging report behaves differently.

Run the balance sheet on accrual when comparing. On a cash basis there is arguably no receivable at all — income is recognised when paid — so a cash-basis balance sheet and an accrual aging report are not measuring the same thing and never will agree.

3. The aging method

The aging report can age transactions from the due date or from the report date. These produce different bucket allocations and, depending on the report, different totals.

Open the Aging dropdown and select Report date when reconciling to the balance sheet.

Then the one that's real: unapplied payments

If the two reports still disagree after aligning date, basis and aging method, the difference is transactional.

Unapplied payments are the usual culprit. A customer payment was recorded but never applied to a specific invoice. It reduces what the customer owes in total, but it isn't attached to anything — so it appears on the aging report as a negative amount, sitting in a bucket with no invoice behind it.

Any negative on an aging report should be looked at. It means one of:

• A payment received and not applied to its invoice.
• A credit memo not applied.
• An overpayment.

The fix: apply them. Open the payment, attach it to the invoice it was for. If the customer genuinely overpaid, that is a credit to be applied to a future invoice or refunded — a decision, not a data-entry step.

This matters beyond the report reconciling. An unapplied payment means an invoice is still showing as owing when it has been paid. Your aging report is telling you to chase a customer who already paid you, which is the kind of error that costs a relationship rather than a number.

The other real cause: entries that bypassed the sub-ledger

Journal entries posted directly to accounts receivable, without a customer name attached.

The balance sheet picks them up — it reports the account. The aging report cannot show them, because there is no customer for them to appear under. The result is a permanent difference that no amount of re-running will resolve.

Look through the A/R account for anything that is not an invoice, a payment or a credit memo. Those entries are the difference.

If it still won't reconcile

Where the difference survives all of the above, the remaining possibility is damaged list data. Re-sorting the primary names, chart of accounts and item lists is the standard remedy, and it is a genuine last resort rather than a first step — if you find yourself there, it is worth having someone look at the file rather than continuing alone.

Why this is worth getting right

The aging report is the operational document — it is what tells you who owes you money and for how long. When it doesn't agree with the balance sheet:

• You cannot trust the collections list. Someone on it may have paid.
• Your receivables figure is unverified, and that is a number lenders look at directly.
• Revenue timing may be wrong if invoices and payments aren't linked properly.
• Year-end takes longer, because your CPA has to reconcile the two before using either.

When this stops being a DIY job

Handle it yourself when aligning date, basis and aging method makes them agree, or when there are a few unapplied payments you can attach to their invoices.

Get help when:

• There are many unapplied payments, which points at a process problem rather than isolated mistakes.
• You find journal entries posted straight to A/R that nobody can explain.
• The aging report shows old invoices you believe were paid — the receivable ledger has lost track of reality, and chasing customers from it will cause damage.
• The difference survives a re-sort of the lists.
• A/P shows the same pattern, which usually means both sub-ledgers have been bypassed and the problem is systemic.

That is monthly bookkeeping work when it's about keeping the sub-ledger clean going forward — payments applied as they arrive, so the aging report stays usable. Where there is a backlog of unapplied payments and direct journal entries across a long period, it is scoped as a cleanup first, because the receivable ledger has to be rebuilt to a point where it can be relied on.

TechBrot does the operational bookkeeping and hands your CPA a file they can file from. If the answer is "your aging report was set to today", we'll tell you that and there's no engagement in it.