
Maintenance
Reading accounts receivable as a beginner bookkeeper: aging, payments and credit notes
A beginner bookkeeper's guide to reading accounts receivable: why balances age, how payments are allocated, and how credit notes, write-offs and provisions differ.
An unpaid invoice is a loan you did not decide to make, on terms you did not negotiate, to a borrower you did not credit-check. Accounts receivable is the ledger of every one of those loans.
That framing explains most of what follows: why the balance needs watching, why age matters more than amount, and why "they always pay eventually" is a sentence that costs businesses their working capital.
What to take away
- Receivables age for four different reasons and only one of them is the customer being unable to pay. Sorting the report by age rather than by size is what separates them.
- Every payment is allocated to named invoices. Cash left floating against a customer makes the aged report wrong in both directions at once.
- A credit note, a write-off and a provision mean three different things. Using one where another belongs quietly rewrites either your sales history or your cost line.
What actually happens in the books
Two events, and beginners routinely merge them.
Two events, two entries
- Raise invoice: revenue up, receivable up
- Bank untouched: no cash yet
- Customer pays: bank up, receivable down
- Revenue stays put: already recorded
- Record deposit as sale: revenue doubled
You raise the invoice. Revenue appears in the profit and loss statement, and an equal amount appears as an asset: money owed to you. Nothing has touched the bank.
They pay. The bank goes up and the amount owed comes down by the same amount. Revenue does not move at all: it was already recorded.
If income appears both when you invoice and again when the payment lands, your sales are doubled and so is your tax exposure. This is the single most common error in a small business's books.
It usually comes from processing the bank feed as if every deposit were a new sale rather than matching it to the invoice it settles. Revenue recording covers the timing side of the same transaction.
Why the balance ages
Receivables age for four different reasons and only one of them is what people assume.
- Terms.An invoice on thirty-day terms is not late on day twenty-nine. Some of your "aged" balance is simply the normal gap between doing work and being paid for it.
- Process on their side.Missing purchase order number, wrong entity name, sent to a person instead of an accounts inbox, arrived after their payment run cut-off. The invoice is not disputed. It is just not in the queue.
- Dispute.They think the work is wrong, incomplete, or not what was agreed. This is a delivery problem wearing a finance costume, and chasing it as a payment problem will not move it.
- They cannot pay.The genuinely bad one, and the reason the other three matter: every week spent on a category-two problem is a week you did not spend finding out that this is a category four.
The whole purpose of an aged receivables report is to separate these. Sorting by size tells you what you would like to collect. Sorting by age tells you what is going wrong.
The ladder, and what to do on each rung
The buckets below use thirty-day steps because that is the common convention, not because there is anything magic about thirty days. Set the steps to match your own terms.
Aged receivables escalation ladder
- Not yet dueConfirm invoice arrived and approved
- 1-30 daysShort factual email, reattach invoice
- 31-60 daysPhone call what must happen to pay
- 61-90 daysEscalate, agree written plan or stop supply
- Over 90 daysFormal recovery, settlement, or write-off
| Age past due | What it usually means | The action that actually works |
|---|---|---|
| Not yet due | Normal | Confirm the invoice arrived and is approved for payment. Ask before it is late, not after |
| 1 to 30 days | Process friction, most of the time | A short factual email plus the invoice attached again. Ask which reference or approval is missing |
| 31 to 60 days | Something is unresolved and nobody has said what | Get a person on the phone. The goal is one sentence: what has to happen for this to be paid, and by when |
| 61 to 90 days | The relationship is now the issue, not the invoice | Escalate to someone with authority on both sides. Agree a written plan or stop supplying |
| Over 90 days | Treat recovery as unlikely without a change of approach | Decide deliberately: formal recovery, negotiated settlement, or write-off. Drifting is the one option with no upside |
Two habits do more than any escalation script. First, contact before the due date, not after: it converts most category-two problems into nothing. Second, always write down what the customer actually said, with the date. A promise recorded is a promise you can quote back.
Payments that do not land cleanly
Partial payments need allocating to specific invoices, not left floating against the customer. An unallocated credit makes the aged report lie: the oldest invoice looks unpaid while a mystery balance sits at the bottom.
Round-sum payments covering several invoices need the remittance advice. If there is none, ask. Guessing the allocation is how a paid invoice gets chased and a disputed one gets marked settled.
Short payments are a message. Someone deducted something: a deduction for a fault, a settlement discount taken without agreement, a bank charge. Find out which before you write off the difference, because a pattern of unexplained short payments is a contract problem.
Overpayments and duplicates are a liability, not a windfall. You owe that money back or against a future invoice, and it belongs where it can be seen.
Credit note, write-off, provision: three different things
Beginners use these interchangeably. They mean opposite things.
A credit note says the invoice was wrong or the sale was canceled. The revenue should not have been there. You issue a document, and both the receivable and the sale come down.
A write-off says the invoice was right and you won't be paid, but revenue stays. The receivable comes down and a bad debt cost appears, recorded like any other cost, as the expense recording guide describes.
Your sales line keeps telling the truth about what you sold; your cost line tells the truth about what you failed to collect.
Whether and when a write-off is recognized for tax is a separate question with its own rules. Start from the federal guide to business expense resources and settle it with your accountant.
Provision for doubtful debts is neither. It is an estimate, made while you are still trying, that some of what is owed will not arrive.
It reduces the asset's value without canceling any specific invoice, so the balance sheet stops implying every dollar owed is a dollar coming. The estimate is a judgment; document your basis.
Prevention beats collection
Everything above is what you do after the fact. These are the levers before it:
- Invoice immediately.The gap between finishing work and sending the invoice is pure delay you control, and it is often the largest single component of how long you wait.
- Invoice correctly the first time.A missing reference number can add a full payment cycle. Ask each customer, once, what their invoice needs to contain and who it goes to.
- State the terms on the document, and make sure they match what was agreed rather than your software's default.
- Take deposits for work with real up-front cost.Remember a deposit is not revenue until you have earned it: it is money held against work owed.
- Check new customers before you extend credit, and set a limit. Reviewing this on the third unpaid invoice is a decision made too late. Granting terms is extending credit, and the federal guidance for businesses on credit and finance is where to check what obligations come with it in your case.
- Reconcile the receivables ledger to the control account and to the bank every month.Errors found in a monthly cycle are small; errors found at year-end are archaeology, and the routine that keeps them small is in the bookkeeping foundations guide.
Where a bookkeeper's judgment ends
Allocating payments, chasing on an agreed schedule, keeping the aged report clean, flagging what has stopped moving: all bookkeeping, all evidence-based.
Estimating how much will never arrive, deciding to write a debt off, the tax treatment when you do, and choosing legal pursuit are not.
The first is an accounting judgment; the last is legal.
Both are better made with the aged report and contact history in front of you, which good bookkeeping produces.
Common questions
Should overdue invoices carry interest?
A customer wants to pay in installments. How is that recorded?
How often should the aged report be looked at?
Which account should a customer deposit sit in?
Is it worth using a collections agency?
In this guide
- Aging report damage comes from a few receivable habits, not oneNine accounts receivable mistakes that wreck the aged report, from receipts booked as income to unallocated cash, each with what it hides and the correcting entry.
- Accounts receivable examples compared across one customer's ledger cardAccounts receivable examples worked through one customer ledger card: invoices, allocation, credit notes, deposits, short payments and the balance after each.
- The seven stages behind every receivable, and the test that catches gapsAn accounts receivable framework in seven stages, each with its trigger, document, ledger entry and owner, plus the control account test that finds what is missing.
- Accounts receivable metrics: aging buckets, days sales outstanding and roll rateHow aging buckets are built by invoice date or due date, why days sales outstanding distorts collection speed, and the roll rate that predicts a bad debt.
- Accounts receivable trends 2027: reminders and matchingAccounts receivable trends 2027: payment links settle invoices, reminders chase by themselves, and matching plus exceptions replace keying receipts.







