Illustrative worked example
One broken payment promise, and what it changes.
When a promised payment date passes, an invoice does not simply get older. It becomes a different object: a commitment has broken, the next action changes, the person the matter belongs to changes, and what the invoice is worth to a cash plan changes. An ageing report registers none of that — on the morning after a broken promise it reads exactly as it did the morning before.
Illustrative worked example. Not a customer case study. Ridgeway Content, a nine-person content studio, and its customer Calder Retail are invented for this page, as are the invoice, the dates and the amount.
Forty-five days, one invoice, two promises.
Day 0. Ridgeway Content issues invoice 1042 to Calder Retail for $14,800, thirty-day terms, for a content programme delivered across February. The invoice goes to the address Calder’s accounts team asked for, carrying their purchase order reference. Nothing about it is unusual.
Day 25. A short note goes out: the invoice falls due in five working days, and if anything is needed to process it — a statement, a different address, a missing reference — it will be sent the same day. No reply, which is normal.
Day 30. Due. Nothing arrives. Nothing has been queried.
Day 31. A first message: the invoice was due yesterday and no payment has been recorded against it. Either it is in a payment run and not yet visible, or something is holding it up — a one-line reply tells Ridgeway which. Still no reply.
Day 38. A follow-up asks for one thing only: the date Calder expects to pay. At twenty to five, a reply arrives from Calder’s accounts assistant. “Should go out Friday.”
Day 38, twenty minutes later. Friday is day 41. It is written back to Calder in a line of confirmation and recorded against invoice 1042 as a promised payment date. Ridgeway will not chase again before then. This is the moment most processes skip, and everything after it depends on the fact that this one did not.
Day 41, Friday. Nothing arrives. No message either.
Day 44, Monday. Invoice 1042 appears on the follow-up list on its own, flagged as a promise that has passed — not because anyone remembered a Friday three days earlier. A message goes out that afternoon: the date expected was Friday, it has not reached us, what changed, and what date should be recorded now. If instead the amount or the invoice is in question, say so and it will be treated as a query rather than a late payment.
Day 44, an hour later. Calder replies. The approver was on leave and the run went out without invoice 1042 in it. The new date is day 55. That date is recorded too — and invoice 1042 now carries something it did not carry on day 40: two promises, one of them broken.
The ageing report did not move. The invoice did.
Nothing that mattered between day 41 and day 44 was visible in an ageing report, because an ageing report measures one thing: how long ago the invoice was issued. That is a fact about the calendar rather than about the customer.
| Morning | What the ageing report showed | What was actually true |
|---|---|---|
| Day 31 | $14,800, bucket 1–30 days | Due yesterday. One message sent, no reply yet. Nothing known about intent. |
| Day 41, Friday | $14,800, bucket 31–60 days | Payment was promised for today. By this evening either the money has arrived or a commitment has broken — and those are not the same invoice. |
| Day 44, Monday | $14,800, bucket 31–60 days | The promise broke. A second promise now exists for day 55, from a customer whose first one did not hold. The report reads identically to Friday. |
Between the second and third rows the report is unchanged — same amount, same bucket, same customer — while the only genuinely new information in the whole forty-five days arrived. That is the limit of ageing: it records how long money has been outstanding, and says nothing about whether anybody is doing anything, what was undertaken, or whether an undertaking held.
This page follows one invoice. What should happen the moment any promised date passes, as a general rule, is set out separately.
What actually needed deciding — and by whom.
On day 45 the position went to Ridgeway’s founder. Not an opinion, not a recommendation to escalate: a page of facts. The invoice, the amount, the dates, every contact made, what was promised and by whom, that the first promise passed without notice, that a second exists for day 55, that nothing has been disputed, and that a second project for Calder is due to start in a fortnight.
That last line is why the decision is the founder’s and nobody else’s. Every option available at this point changes a commercial relationship rather than an accounting record.
- Accept the second date and keep the sequence running. Reasonable where a customer has a long clean history and the explanation is ordinary.
- Ask for part of it now and the balance on day 55. Tests intent without changing the terms.
- Start the second project on a revised commercial basis — a deposit, a shorter payment term, a smaller first phase. A decision about the future, not about the past.
- Hold the start of the second project until 1042 clears. A supply decision, taken by the person who owns the relationship and the consequence.
- Take the matter outside the finance function. Rare at day 45, and entirely the owner’s call, taken with whatever advice they choose.
In this illustration the founder took the second option and started the new project with a deposit. What matters is not which option was right — it depended on facts about Calder that only the founder held — but that a deliberate decision was taken on day 45 by the person entitled to take it, on a complete picture. The failure mode this replaces is the same invoice reaching day 90 with nobody having decided anything, because nothing ever surfaced.
No message in the whole sequence raised interest, penalties, credit standing or a legal step. None was needed to reach a decision, and none of them would have been finance’s to raise.
Where At Par fits — and the limits.
The thing that made day 44 happen was not diligence. It was a record. The promise was written against the invoice on day 38, so on the Monday it surfaced by itself. That is what At Par runs for owner-led service businesses: an invoice carries a state rather than an age, promises are recorded where the next follow-up reads them, a passed date raises itself, disputes are marked as disputes, and the position goes to the owner when the question stops being administrative. In full: receivables and invoice follow-up, over books kept current by bookkeeping and month-end close.
The wording used at each stage of the sequence above is set out in the overdue invoice follow-up pack. Whether your own process would have caught the Friday is nine questions: the invoice follow-up health check.
Asked after a promised date has gone quiet.
What information does a business owner need before deciding what to do about an unpaid invoice? +
Six things, on one page: the invoice and the amount, the dates it was issued and due, every contact made and the reply to each, what was promised and by whom, whether anything has been disputed, and what other work or invoices are open with the same customer. Given those, a decision takes minutes. Given a balance and an age, the owner is choosing between options without the facts that distinguish them, which is usually why nothing gets decided at all.
Can an outsourced accounting provider chase invoices without authority to negotiate? +
Yes, and that separation is the right default. Following up is administrative work: confirming the position, asking for a date, recording what was said, and surfacing the invoice when a date passes. Negotiating is commercial: agreeing a discount, a payment schedule, revised terms or a write-off changes what the business is owed. A provider can prepare each option with the facts behind it, and the business owner decides which one happens.
What does it mean to say an overdue invoice has a state rather than an age? +
Age is one number: days since issue. State is what is actually happening — who owns the invoice, what was last done and when, what the next action is and on what date, whether a payment date was promised, whether that promise held, and whether anything is disputed. Two invoices with identical ages can be in completely different states, and the state determines what should happen next. Age determines only which column of a report the invoice appears in.
Does pausing further work on an unpaid account count as debt collection? +
No. Deciding whether to keep supplying a customer is an ordinary commercial judgement about future trade, made by the business owner, and it is separate from any attempt to recover what is already owed. It should be taken deliberately, communicated plainly and in advance, and weighed against the relationship and any contractual commitment already given. It is not a lever a finance function should reach for on its own, and it is not a substitute for legal advice where a contract is in question.
What should be recorded when a customer explains why a payment was missed? +
The reason in the customer’s own words, the date it was given, who gave it, and any new date that came with it — held against the invoice rather than in an inbox. The reason matters twice: it usually says what needs to change to get paid, and it accumulates. One approver on leave is an ordinary event. The same explanation three times across two quarters is a pattern, and only a written record turns the second into something anyone notices.
What does a broken payment promise mean for a cash forecast? +
It means an expected receipt should stop being treated as expected. A forecast built on invoice due dates assumes every customer pays to terms; a forecast built on recorded promises is better, but only while the promises hold. Once a date has passed unmet, the honest treatment is to move that amount out of the near-term expectation and mark it as uncertain rather than simply re-dating it — and to note that this customer has now missed one commitment.
Show us your open invoices. We’ll show you the state of each.
Send an ageing report or a list of what is outstanding. We will come back with what is actually known about each invoice — owner, last action, next action, promises made and promises passed — and what we would run from here.
Prefer to reach us directly? Tell us a little and we'll come back with a time.
Review our receivablesWe 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. Ridgeway Content, Calder Retail, the invoice and the dates are all invented. See what we actually do.