Worked example · not a case study
One invoice, from issued to reconciled.
Receivables is a process with states, not a list of overdue balances. An invoice moves through issued, approaching due, due, followed up, queried, corrected, promised, promise broken, payment claimed, received but unmatched, and matched — and at every one of those points three things should be answerable: what happened, what is now known, and who owns the next action.
Illustrative worked example. Not a customer case study. Northline Studio and Halcyon Retail are invented, and every figure below is made up to demonstrate the sequence. Nothing here describes a real client, a real customer or a real payment.
Eleven states. One invoice.
Northline Studio is an invented design studio. It issues a single invoice to Halcyon Retail, an invented customer, for £6,400 on 30-day terms. What follows is the ordinary life of that invoice — not a disaster, not a success story, just a normal one that takes fifty-nine days and passes through four different owners on the way.
| Day · state | What happened | What the record now knows | Who owns the next action |
|---|---|---|---|
| Day 0 · Issued | Invoice NL-0412 is raised and sent to Halcyon Retail for £6,400 on 30-day terms. | Amount, currency, terms, due date, and evidence of what was sent, to whom, and when. | Nobody. The invoice is not late and there is nothing to chase. A dated watch is set for day 25. |
| Day 25 · Approaching due | A short note confirms the invoice arrived and asks whether anything is needed in order to pay it. | The invoice reached a person rather than an inbox. No query has been raised and no payment made. | Halcyon Retail. Everything that can be done before the date has been done. |
| Day 30 · Due | The due date passes with no payment and no message. | The invoice moves from current to outstanding and begins to age. Nothing about it is yet unusual. | Northline. A follow-up is prepared; Northline authorises it before it goes. |
| Day 34 · Followed up | The first follow-up goes out: the invoice, the due date, the amount, and a direct question about when it will be paid. | Contact attempted, on a date, through a named channel, to a named person — held against the invoice rather than in somebody’s memory. | Halcyon Retail. |
| Day 36 · Queried | Halcyon replies. The invoice cannot enter their payment run because it carries no purchase-order reference. | This is not a cash problem. It is a document defect, which is a different problem with a different owner. | Northline. Chasing Halcyon again would be chasing the wrong party. |
| Day 38 · Corrected | The purchase-order reference is added and the invoice re-issued. The original is kept; the change is recorded as an amendment with a reason rather than written over. | Two versions and one history. The amount and the terms did not change, so the ageing continues from the original due date. | Halcyon Retail. A re-issue is not a new invoice. |
| Day 45 · Promised | Halcyon confirms the invoice is approved and will be paid in the run on day 52. | A promised amount, a promised date, and the name of the person who gave it. That is a dated expectation, not a payment. | Halcyon Retail, until day 52. Nothing further is sent before then. |
| Day 53 · Promise broken | Day 52 passed. No payment, no message. | A broken promise is its own state. It is not the same as an invoice nobody ever responded to, and it changes who the next conversation should be with. | Northline. A message to Halcyon’s finance contact is prepared; Northline decides whether it goes, and to whom. |
| Day 58 · Payment claimed | A remittance advice arrives stating that NL-0412 has been paid. | A claim, and evidence that the claim was made. The invoice is not settled and nothing is closed. | Nobody acts on the claim. The record waits for the bank. |
| Day 59 · Received, unmatched | £18,180 lands in Northline’s account as a single credit covering three invoices, and it is £20 short of their total. | Cash has arrived and cannot yet be attributed to any one invoice. The receivables position has not moved, because nothing has been allocated. | Northline’s books. Allocate the receipt and explain the difference. |
| Day 59 · Matched | The credit is allocated across the three invoices. The £20 is identified from the statement as an intermediary bank charge and recorded as a cost, not as a shortfall from Halcyon. | NL-0412 is settled, with the bank line, the remittance advice and the allocation held against it. Ageing, the receivables total and the bank reconciliation now agree with each other. | Nobody. This is the only row where that is the right answer. |
Fifty-nine days, one document defect, one broken promise, and eight days lost to a missing purchase-order reference that nobody was chasing because everybody assumed it was a cash problem.
A status is a label. A state is a position with an owner.
Most accounting systems will tell you an invoice is overdue. That is a status: it is derived from a date and it is true of every unpaid invoice past its terms, whatever the reason. It does not distinguish the customer who has a cash-flow problem from the customer who cannot pay because your invoice is missing a reference number, and those two need completely different actions from completely different people.
A state carries three things a status does not, and they are the three columns in the table above.
- What happened. A dated event, not an inference. “Followed up on day 34” is an event. “Overdue” is arithmetic.
- What is now known. Each event adds something: that the invoice reached a person, that a reference was missing, that a date was promised. That accumulated knowledge is what makes the next action sensible instead of generic.
- Who owns the next action. The single most useful field, and the one almost never present. On day 36 the owner of this invoice was Northline, not Halcyon — and a system that only knew “overdue” would have sent another chaser to a customer who had already explained the problem.
Claimed is not received. Received is not reconciled.
Days 58 and 59 carry the whole point. A remittance advice is a customer telling you they have paid. It is useful, it is evidence, and it is not money. Marking an invoice as settled when the remittance arrives feels efficient and produces a receivables figure that is quietly wrong until the bank agrees with it.
Then the money arrives, and it still is not finished. One credit of £18,180 covering three invoices, twenty pounds short of their total, is not information about any single invoice until somebody allocates it. Until then the cash is in the bank and the receivables ledger has not moved — and both of those statements are correct at the same time.
The short difference is the part most often handled badly. Twenty pounds is not worth an argument, so it gets absorbed — written off against the customer, or left in a suspense account, or quietly ignored. Here it is identified from the statement as an intermediary bank charge and recorded as a cost. That takes a minute, and it means nobody later has to reopen a settled invoice to work out why it was short.
Evidence held against the invoice: the invoice as issued · the re-issue and the reason for it · four dated contact records · the remittance advice · the bank line · the allocation across three invoices · the bank-charge entry. Every figure above is illustrative.
What did not happen.
A worked example is only honest if it is clear about what it did not include. Across fifty-nine days, none of the following occurred, and none of them would have.
- No money was moved by anyone but Northline. Payments are prepared for a business to release. At Par records settlement on evidence — a bank line, a statement — and never executes the transfer.
- No message left the business without authorisation. Every contact with Halcyon was prepared and then sent under Northline’s authority. Anything going out in a client’s name is the client’s decision, on each occasion.
- No legal escalation and no debt collection. At Par is not a collection agency and provides no legal debt recovery. The day-53 escalation was a message to a finance contact, prepared for Northline to approve.
- No concession, discount or write-off. The £20 was a bank charge identified from the statement, not a decision to accept less. Commercial concessions belong to the business and are never made on its behalf.
- No promise that this invoice would be paid faster. Nothing here shortens fifty-nine days. What the sequence changes is that the eight days blocked on a purchase-order reference were visible on day 36 rather than discovered at month-end — and that the twenty-pound difference has an explanation rather than a hole.
The value in this walkthrough is not speed. It is that at no point was the answer to “where is this invoice, and whose move is it” a guess.
Where At Par fits — and the limits.
This is the shape of the work At Par does on receivables for owner-led service businesses: invoices tracked with a state and an owner rather than an age, follow-up prepared on a cadence and sent under the client’s authority, promises recorded as dated expectations, receipts allocated against invoices, and differences explained rather than absorbed. The reasoning behind that approach is set out in receivables and invoice follow-up; this page is only the demonstration.
It sits on top of the ordinary work: bookkeeping and month-end close, catch-up where the books have fallen behind, and management reporting — with a qualified accountant (ACCA) accountable for the work. A receivables position is only as good as the reconciliation underneath it.
Buying this kind of arrangement rather than reading about it? The questions worth asking are in the provider checklist, and the scope standard behind them is what a provider should own.
Asked by owners looking at an ageing report.
What are the stages of an invoice from issue to payment? +
Issued, approaching due, due, followed up, queried where something blocks payment, corrected where the query was a document defect, promised where a payment date is given, broken where that date passes, claimed where a remittance advice arrives, received where cash lands, and matched where the receipt is allocated to the invoice and any difference is explained. Not every invoice passes through all of them, but every one of them is a distinct position with a different owner.
What is the difference between an invoice marked paid and an invoice reconciled? +
Marked paid usually means somebody recorded a payment against it. Reconciled means the money is visible on a bank statement, has been allocated to that specific invoice, and any difference between what was expected and what arrived has been identified and recorded. An invoice can be marked paid on a remittance advice and still not be reconciled, which is how receivables figures drift away from the bank without anyone noticing.
Why do invoices go unpaid when the customer has the money? +
Frequently because the invoice cannot enter the customer’s payment process rather than because they will not pay. Missing purchase-order references, the wrong entity name, a wrong or absent contact, a mismatch against an agreed rate, or delivery to a person who has left are all common. These look identical to a cash-flow delay on an ageing report and need the opposite response: the next action belongs to the supplier, not the customer.
What should happen when a customer breaks a promise to pay? +
It should be recorded as a distinct event rather than folded back into ordinary overdue. A promise carries an amount, a date and a named person, so a broken one identifies who to go back to and what was said. Practically, the next contact is usually a different one — often a finance contact rather than the original recipient — and it should reference the promise specifically. Escalation beyond that is a commercial decision belonging to the business.
Does a remittance advice mean an invoice has been settled? +
No. A remittance advice is a customer stating which invoices a payment covers. It is evidence of an intention and it is genuinely useful for allocation, but it is not confirmation that funds have moved and it can be sent for a payment that is later cancelled, delayed, or made for a different amount. An invoice should not be treated as settled until the corresponding credit appears on the bank statement and has been allocated.
How should one payment covering several invoices be allocated? +
By matching it against the specific invoices it was intended to cover, using the remittance advice where one exists and the customer’s own reference where one does not. The total should be reconciled to the sum of the invoices, and any difference identified rather than absorbed — a bank or intermediary charge, a deduction the customer applied, a currency movement, or a short payment that needs a conversation. A lump receipt posted to a customer account without allocation leaves every invoice in it unresolved.
Should an incorrect invoice be amended or re-issued? +
Either can be right, but the original should be preserved and the change recorded with a reason rather than written over. Where the amount is wrong, a credit note and a new invoice is usually the cleaner route. Where the defect is a missing reference or a wrong contact, a re-issue that keeps the same commercial terms is normally sufficient. What matters is that the history remains readable later, because an invoice that silently changed cannot be explained to a customer or an auditor.
Is it worth contacting a customer before an invoice is due? +
A short note before the due date confirming the invoice arrived and asking whether anything is needed in order to pay it is low-cost and surfaces document defects while there is still time to fix them. It is not a chase and should not read like one. It will not make a customer with no cash pay, and it should never be presented as a guarantee of faster payment — its value is that it moves the discovery of a blocked invoice from after the due date to before it.
Send us an ageing report. We’ll tell you what state each one is in.
Not a proposal. Take one page of outstanding invoices, and we will come back with which are cash problems, which are blocked on something you have not supplied, and which nobody owns.
Prefer to reach us directly? Tell us a little and we'll come back with a time.
Talk it throughWe use your details only to prepare for and hold this call. No spam, ever.
Reviewed by an ACCA on the At Par team · Last updated 29 July 2026 · Illustrative worked example. Not a customer case study. Northline Studio, Halcyon Retail and every figure shown are invented. See what we actually do.