Where cash collection breaks: what 40+ UK businesses told us
2026-09-23
Every problem in this research was observed in a real ledger, named by a real finance team, and mapped to a resolution an expert has signed off. None of it is inferred from a market study.
How the research was done
We interviewed finance leaders, owners and AR teams at more than 40 UK businesses — the people who actually collect the money — and then went into the ledger to see what they described.
- 40+ UK businesses researched
- 83 validated failure patterns, each observed in a real ledger
- 488 resolution actions — the real human sequence that fixes each failure
- 480 of those actions signed off by the expert reviewer; 122 recur often enough to be reusable across businesses
A failure pattern qualified only if it was named by a finance team and then found in the ledger data. The 83 sit across four areas: billing and invoicing (24), debtors (20), cash flow and internal process (19) and queries (20). The largest single category is billing — problems created before anyone sends a reminder.
What they told us
Cash collection failure is systemic, not an effort problem.
- Late payment: 60% of businesses
- PO and reference breakdowns: 60%
- No clear view of payment status after the invoice is issued: 50%
- Manual follow-up: 37%
- Disputes: 30%
- Broken promises to pay: 23%
The two largest problems are data problems, created upstream before any reminder is sent. Half of businesses are working blind, so effort goes to the loudest debtor rather than the most valuable one. Manual follow-up, disputes and broken promises are all downstream of the first two.
It is not the same problem at every size
For small businesses, visibility and late payment dominate: the finance function is one or two people and there is no queue, only a pile. In the middle, prioritisation becomes the problem — the question is which debtor to work, not whether to work at all. For larger businesses, disputes, escalation governance and audit rise to match late payment: the constraint becomes control and evidence, not effort.
They described the product before we built it
Asked what they would want, businesses named the same things, in the same order as their problems: overdue detection and prioritisation (60%), PO and reference validation (60%), payment status visibility (50%), less manual follow-up (37%), dispute tracking (30%), broken-promise tracking (23%), and escalation governance and audit (17%).
Only 17% asked for governance and audit — but it decides whether an accountancy practice, or a regulated business, can adopt any of this at all. We built to the 17%.
What the research changed
Validate before you collect
Because the two largest failures are upstream data problems, more reminders cannot fix them. collects.io checks an invoice before anything is sent, and holds anything that would fail.
Trust is the adoption barrier, not price
The largest barriers named were internal resistance to change (47%) and loss of control over collections (30%) — not cost, and not security. So the design is read-only first, with a person approving every escalation.
Depth has to scale with the business
One platform, layered: visibility for the smallest, prioritisation in the middle, dispute, escalation and audit controls at the top.
Source: collects.io research with 40+ UK businesses — finance leaders, owners and AR teams, 2026. Findings are stated as researched, not as forecasts. The underlying failure map is available on request: support@collects.io.