Free self-check
Is your invoice follow-up controlled, fragile, or founder-dependent?
A receivables process is only as good as its answers to nine questions: who owns the chasing, what was last done, what happens next, whether promised dates are recorded, what happens when a promise breaks, whether disputes are separated from ordinary lateness, whether the evidence is retrievable, whether receipts are matched to specific invoices, and whether any of it survives the owner being away.
Answer them below and one of three words comes back — controlled, fragile, or founder-dependent. This is a self-check on your own description of your own process. It is not an audit, not an assessment of your business, and not professional advice.
Nine statements. Answer them as things are, not as intended.
Answer for the process as it ran last month, not the one described in an onboarding document. Partly is a real answer and the most common honest one — it usually means the behaviour exists for large invoices and disappears for small ones.
None of these statements is about how much you are owed, how old it is, or your days-sales-outstanding figure. An ageing report tells you the size of a problem. These nine tell you whether anything is being done about it, and whether that would continue without you.
This is a self-check, not an audited assessment. It runs entirely in your browser: nothing you answer is sent anywhere and nothing is saved — reload the page and it is blank again. It is not professional advice.
Answer the nine statements
One of three words comes back: controlled, fragile, or founder-dependent. There is no score and no grade.
How the answers are read, in full: if either the ownership statement or the continuity statement is answered No, the result is founder-dependent — whatever the other seven say, because a process that depends on one person is that person’s attention rather than a process. Otherwise, all nine answered Yes, or eight Yes and one Partly, reads as controlled. Anything else reads as fragile. That is the whole rule; there is nothing weighted or hidden behind it.
What each word means, and what usually causes it.
These are descriptions of an operating state, not a judgement of the people running it. Most owner-led businesses land on fragile or founder-dependent, and both are entirely normal at their stage — they only become expensive when the business grows past them without noticing.
| Result | What it means | What usually causes it |
|---|---|---|
| Controlled | The process runs without the owner. A named person drives it, every open invoice has a next action with a date, promises are recorded and broken promises surface on their own. | Someone decided receivables was a job rather than a reflex, and gave it an owner, a rhythm and a written state per invoice. |
| Fragile | It works while everything is ordinary and has no defined behaviour for the cases that actually cost money — the broken promise, the disputed line, the part-payment against three invoices. | A process built for the happy path. Chasing exists, but the exceptions are handled from memory, so they are handled inconsistently or late. |
| Founder-dependent | The process is a person. It is their memory, their attention and their relationships, and it pauses exactly when they are busiest. | Nobody was ever given the job, or the job was given but the owner still takes over whenever an invoice matters. Both produce the same result. |
Five changes, in the order that pays.
Do not start with software. Every item below can be done in a spreadsheet, and none of them works if the first one is missing.
- Give it a name. One person owns follow-up for all customers. Not “whoever spots it”, and not the owner by default. This single change moves more processes out of founder-dependent than anything else.
- Give every open invoice a next action with a date. An invoice with no dated next action is not being chased; it is being remembered, and remembering fails silently.
- Record promised dates where the chase is driven from. A promise noted in a reply and nowhere else is a promise nobody will check. The record needs to sit beside the invoice.
- Define what happens when a promise breaks. Decide it once, in advance: who is contacted, in what tone, within how long, and at what point it stops being a follow-up task and becomes the owner’s commercial decision. A ready-made sequence for that is here: the overdue invoice follow-up pack.
- Separate disputes from lateness. A disputed invoice chased as a late one damages the relationship and does not get paid faster; a late invoice treated as a dispute quietly stops being chased at all.
Why the broken promise matters more than its size is easiest to see in one worked case: one broken payment promise, and what it changes.
Where At Par fits — and the limits.
At Par runs receivables as an operating process for owner-led service businesses: invoices tracked with a state, a next action and a date; promises recorded and revisited; broken promises surfaced rather than remembered; disputes marked as disputes; receipts matched to the invoices they settle; and the evidence for each held together. What that covers in full is set out in receivables and invoice follow-up, and it sits on books kept current by bookkeeping and month-end close.
And if the honest answer to most of the nine statements is that nobody is doing this at all, that is a resourcing question before it is a process question. Follow-up done inconsistently is often worse than follow-up done by someone whose job it is.
Asked by owners who are chasing their own invoices.
How can a business tell whether its invoice follow-up is actually working? +
Pick three overdue invoices at random and ask four questions about each: who owns it, what was last done and when, what happens next and on what date, and whether a payment date was ever promised. If those answers take more than a minute each, or need a person to be asked, the process is running on memory. The total owed and its age say nothing about this — a large ageing balance with clear next actions is healthier than a small one with none.
What is the difference between a receivables process and a person who chases? +
A process holds state outside anyone’s head: each open invoice carries an owner, a last action with a date, a next action with a date, and a promised payment date where one exists. A person who chases holds all of that in memory and in an inbox. Both can collect money. Only one can be handed to somebody else on a Monday morning, survive a fortnight of absence, or show an owner in thirty seconds what is actually happening across every open invoice.
Can a business have a healthy ageing report and an unhealthy follow-up process? +
Easily, and it is the more dangerous combination because nothing looks wrong. A small ageing balance can be the result of a few large customers who happen to pay promptly, not of any process. When the customer mix changes, or one reliable payer slows down, there is nothing underneath to absorb it — no owner, no next action, no record of what was promised. The ageing report reports outcomes; it does not reveal whether anything is being done.
Is days sales outstanding a good measure of receivables health? +
It is a useful summary and a poor diagnostic. DSO moves with customer mix, seasonality, invoice timing and a handful of large accounts, so it can improve while the underlying process gets worse, and deteriorate for reasons nobody in finance controls. It also tells you nothing about what is being done. Operating state — who owns each invoice, what happens next, which promises have broken — explains the number DSO reports.
What does it mean when receivables are described as founder-dependent? +
It means the collection of cash rests on one person’s attention rather than on a defined process. The invoices get chased, often very effectively, because the owner knows the customers and knows what is outstanding. The exposure is structural: nothing is written down in a form anyone else could pick up, so follow-up pauses whenever the owner is travelling, unwell, selling, or delivering the work — and pauses invisibly.
Is a spreadsheet enough to run invoice follow-up? +
For a business with a modest number of open invoices, yes, provided it holds four columns that most spreadsheets lack: who owns this invoice, what was last done and when, what the next action is and on what date, and whether a payment date was promised. Spreadsheets fail not because they are spreadsheets but because they are usually built as a list of balances rather than a list of states, so nothing in them ever falls due.
What can a receivables self-check tell you, and what can it not? +
A self-check tests one thing: whether the defined behaviours exist. It reads back a description of a process against the description its owner gives of it, so it can identify missing structure — no named owner, no dated next action, no rule for a broken promise. It cannot verify that anything described is actually happening, cannot examine records, and is not an audit, an assessment of a business, or professional advice. Its value is that it makes a vague worry specific enough to act on.
What changes first when a business fixes its invoice follow-up? +
Visibility, before cash. The first noticeable difference is usually that nobody has to ask what is happening with a customer, because the answer is written down — who owns it, what was last done, what is next and when. Whether cash arrives sooner depends on customers, contract terms, delivery quality and the mix of who owes what, none of which a follow-up process controls. What it does control is that nothing goes quiet by accident.
Show us your open invoices. We’ll show you the state of each one.
Send an ageing report or a list of what is outstanding. We will come back with what a controlled version looks like for your business — owner, next action, promise dates and the broken-promise rule — and what we would run.
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 · This is a self-check on your own description of your own process, not an audit or an assessment, and nothing you answer leaves your browser. See what we actually do.