THE QUESTION

The Number That Means Nothing on Its Own

There’s a working capital lever sitting unused on most UK small business balance sheets, and the reason it stays unused is almost absurd: the number you’d use to spot it is being measured against a benchmark that means nothing to the business holding it. That lever is DSO — days sales outstanding, the gap between issuing an invoice and the cash actually landing in the account. Read correctly, it’s one of the largest sources of cash a business already owns. Read against the wrong yardstick, which is what nearly everyone does, and it’s invisible.

Let’s be precise about the number before doing anything else with it. DSO is the average number of days it takes a business to collect after a sale: outstanding receivables divided by revenue, multiplied by the number of days in the period. The formula is simple enough that most operators can calculate it in a spreadsheet in ten minutes. The figure itself isn’t the point, though — what it represents is. Every day of DSO is a day the business’s own cash is sitting in someone else’s bank account instead of its own.

Two things keep this lever hidden. The first is that DSO drift is slow. A late payment is visible — it pings, it gets chased. DSO creep is different: a couple of days a quarter, widening so gradually that nothing ever trips an alarm. By the time the drift is material, it’s been building for a year, sometimes longer, and nobody can point to the week it started, because there wasn’t one.

The second reason is the more expensive one, because it isn’t about attention, it’s about measurement. Most operators check their DSO, when they check it at all, against a textbook thirty-day figure — the number that shows up in every generic finance article and every accountant’s rule of thumb. That default is wrong for almost everyone, and wrong in a way that actively misleads rather than simply failing to help. An operator sitting above thirty days who measures against the textbook figure starts chasing compression that may not be available in their sector, spending goodwill on days they were never going to recover. An operator sitting near thirty who measures against the same figure feels fine, and completely misses that their actual sector norm might be a fortnight tighter, leaving real cash on the table indefinitely. Same wrong benchmark, two different expensive mistakes, and no way to tell which one you’re making until you have the right yardstick.

The other common misreading is that a DSO gap, once identified, is fundamentally a collections problem — a matter of chasing harder, or an awkward relationship conversation waiting to happen with a client about payment terms. Sometimes that’s true. More often, treating every DSO gap as a chasing problem is exactly the mistake that wastes the most money, because a gap caused by clunky payment mechanics or genuinely structural payment terms doesn’t respond to chasing at all — it responds to a different lever entirely, and reaching for the wrong one is where most of the avoidable cost in this piece actually sits.

This piece is about getting the yardstick right, and then about what to do with the reading once it’s accurate. It maps a UK sector-by-sector DSO benchmark — because the honest answer to “is fifty-two days bad” is always “compared to what” — and then walks through the three categories of FinTech tooling that close a genuine gap once one’s identified, the decision rule for choosing between them, and a ninety-day sequence for taking a business from an unreadable number to a costed, executed plan. It closes with a real worked example: a marketing agency that used the sequence to cut its DSO by more than a fifth and release meaningful working capital in a single quarter.

The question underneath all of it, stated plainly: is your DSO actually a problem, or does it only look like one because you’re reading it against the wrong number? Get that question right first. Everything else in this piece follows from the answer.

THE LANDSCAPE

The Twelve-Sector Map

Real DSO benchmarks are sector-specific, and the spread across the UK SMB economy is large enough that the same number can mean opposite things depending on which business is holding it. The table below is this catalogue’s standing twelve-sector benchmark map, and it’s worth reading across the whole spread before looking at any single row in isolation.

Two things are worth noticing in that spread before moving on. The first is the range: from a sector where DSO barely exists as a concept to one where ninety days is unremarkable, all inside a single, ordinary SMB economy. The second is what sits inside row twelve — healthcare-adjacent has the widest internal spread of any single row on the map, because a veterinary practice collecting from pet owners at the point of care and a domiciliary care provider billing an NHS commissioner are nominally the same sector and operationally unrelated businesses.

Here’s the insight that makes the whole map matter more than a piece of reference trivia. A construction sub-contractor sitting at seventy-five days is operating exactly to sector norm — there is no problem to solve, and treating it as one wastes energy that should go elsewhere. A B2C e-commerce business sitting at that same seventy-five days is in something closer to structural failure — nearly all its revenue should already be sitting in its account by that point, which means the number is describing something seriously wrong, not sector-normal drift. Identical number. Opposite meaning. Every DSO figure in this piece, and every DSO figure an operator calculates for their own business, is only interpretable next to the row of the map it belongs to.

Once a business knows its sector band, the map converts into an instruction rather than a piece of context. Sitting inside the band means DSO is not the priority this quarter — and, this matters as much as the positive case, it means the business should stop chasing compression that isn’t actually available, because the only outcome of pushing a client who’s already paying to sector norm is a damaged relationship for days that were never coming back. Sitting above the band means there is a genuine, quantifiable gap: a specific number of days of trapped working capital, translatable directly into pounds using the business’s own receivables and revenue figures. That gap, and only that gap, is what the rest of this piece is about closing.

Quantifying the gap is arithmetic, not guesswork. Multiply the number of days above the sector band by the business’s average daily sales, and that’s the pound figure of capital sitting in the gap rather than in the business’s own account. For a business turning over £1.2m a year — roughly £3,300 a day — each day of excess DSO is worth a little over three thousand pounds of trapped capital. A ten-day gap on that turnover is worth close to £33,000. That’s not a rounding error on any SMB balance sheet; it’s very often close to the size of the working capital facility the same business might otherwise be shopping for at a real interest cost.

The gap itself has a shape, and the shape matters for what comes next. A DSO gap is usually one of three things: concentrated in a small number of chronically slow accounts while the rest of the book pays close to term; spread evenly across most customers, suggesting the issue is process rather than any particular relationship; or tied to a specific friction — a payment method, an approval chain, a class of client that structurally pays on longer terms. Diagnosing which of the three a business is looking at is the actual skill this piece is building toward, because the three shapes point to three different levers, and matching the wrong lever to the shape is the single most expensive mistake operators make once they’ve got the benchmark right.

THE MECHANISM

Three Levers, Matched to Cause

Once the shape of the gap is understood, three categories of FinTech tooling do most of the work of closing it, and they are not interchangeable — each is built for a different cause, and reaching for the wrong one is where most of the avoidable cost in this piece actually sits.

Lever one: automated follow-up

Tools like Chaser and Satago, alongside the native follow-up workflows increasingly built into Xero and QuickBooks, compress DSO by removing the friction of manual chasing entirely. For typical B2B services, this lever takes roughly four to eight days out of DSO on its own — the invoice gets followed up on schedule, every time, whether or not anyone remembered to do it that week. This is the lever for the chasing-discipline shape of gap described above: invoices that are perfectly collectable, that simply don’t get chased consistently because whoever’s responsible for it is busy running the rest of the business. It is also, not coincidentally, the cheapest and fastest lever to deploy — most of these tools are a subscription and an integration, live within a week, not a negotiation or a facility application.

Lever two: embedded payments

The second lever puts the means to pay directly inside the invoice, rather than leaving the customer to find their own way to a bank transfer. GoCardless Instant Bank Pay, Stripe payment links, and Open Banking-routed account-to-account payments all do a version of this. It compresses a further six to twelve days on top of what automated follow-up achieves, and it works by removing a specific, well-documented friction: the customer having to leave the invoice, open a banking app, and key in payment details manually, at which point the payment gets deferred to “later” more often than not. The easier a business makes paying, the sooner it happens. This lever fits the payment-friction shape of gap — customers who fully intend to pay and have no dispute about the invoice, but for whom the mechanics of paying are just clunky enough that it slips a few days past when it otherwise would have landed.

Lever three: selective invoice finance

The third lever is different in kind from the first two, and the difference matters. Selective invoice finance — providers including Kriya, Aldermore, Bibby, and Sonovate operate in this space in the UK — releases capital that’s trapped in a business’s slowest decile of receivables: the structurally late accounts where the payment terms themselves, not any process failing, hold cash longer than the business can comfortably carry. The word selective is doing real work in that sentence. This is not a facility against the whole receivables book; it’s finance against the specific slow-paying accounts identified by the benchmark and the shape-of-gap diagnosis, which keeps the cost proportionate to the actual problem rather than financing receivables that were already collecting close to term. This is the lever for the structural-terms shape of gap — a construction sub-contractor being paid on a main contractor’s ninety-day cycle, for instance, where no amount of automated chasing or easier payment links changes a payment term that’s contractually fixed.

The decision rule

Stated as plainly as possible: a chasing-discipline gap calls for follow-up automation. A payment-friction gap calls for embedded payments. A structural-terms gap calls for selective invoice finance. The single most common and most expensive mistake operators make is reaching for the third lever by default, because it’s the most visible option and the one that feels like it’s “doing something” about a working capital problem — when the actual gap was a chasing problem that could have been fixed for a few pounds a month with the first lever alone. Matching the lever to the cause, not to which one feels most substantial, is the entire discipline this section is teaching.

What it costs, and what it’s worth

The first two levers are inexpensive enough that most SMBs don’t need a business case to justify them: the combined toolchain of follow-up automation and embedded payments typically runs under £100 a month, and pays back inside the first quarter for any business carrying a meaningful receivables book. The third lever has a real cost — selective invoice finance is priced against the specific accounts financed, not free capital — but because it’s deployed selectively rather than across the whole book, the cost is proportionate to a genuine, quantified problem rather than a blanket facility taken out against uncertainty. Compare that combined cost against the arithmetic from the previous section — a ten-day gap on £1.2m turnover worth roughly £33,000 in trapped capital — and the toolchain typically pays for itself many times over inside the first year, a rare enough claim in FinTech tooling that it’s worth stating plainly rather than as a marketing flourish.

Why most operators still don’t deploy any of this

If the levers are this well understood and this inexpensive relative to the problem, the obvious question is why DSO drift remains as common as it is across the UK SMB economy. The honest answer sits upstream of the levers entirely: most operators never get as far as this section, because they never get an accurate, sector-benchmarked read on whether they have a gap at all. Without the map in the previous section, there’s no way to distinguish a business at sector-normal ninety days from one at a genuinely costly ninety days, so the lever conversation never starts. Fixing DSO is, in that sense, less a tooling problem than a measurement problem wearing a tooling problem’s clothes — which is exactly why this piece spent as long as it did on the benchmark before ever naming a tool.

It’s worth stepping back from any single balance sheet to see why this matters at the scale of the UK SMB economy, not just one business at a time. When policymakers and lenders discuss small business finance, the conversation almost always defaults to the supply side — credit availability, approval rates, the terms on offer from banks and alternative lenders. Those matter, and they get the attention because they’re visible: a declined application is a clear, countable event. A DSO gap is not a declined application. It’s capital a business already owns, sitting unclaimed on its own balance sheet, invisible precisely because nothing about it triggers a rejection letter or a headline. Multiply a fixable ten-or-so-day gap across even a fraction of the UK’s trading SMB population and the aggregate figure is not small — and unlike a lending facility, none of it carries interest, none of it dilutes equity, and none of it requires anyone’s approval to access. It’s simply unmeasured.

THE PLAN

The 90-Day Sequence

Between diagnosis and result sits execution, and the sequence below is the one this catalogue uses with its own worked example, ordered so that each thirty-day block only starts what the previous one has made possible.

Days 1–30: measure, benchmark, diagnose

The first month is entirely diagnostic, and it’s tempting to skip it in favour of switching a tool on immediately — resist that. Calculate DSO properly from the actual receivables ledger, not from memory or a rough sense of “we’re always a bit slow to get paid”. Place the number against the correct row of the sector benchmark map, not the textbook thirty-day default. If there’s a gap, quantify it in pounds using the arithmetic from earlier — days above band times average daily sales — so the rest of the plan is justified against a real number rather than a vague sense of unease. Finally, diagnose the shape of the gap: pull the aged receivables list and sort it by account, and look for whether the drift is concentrated in a handful of names, spread evenly across the book, or clustered around a specific payment method or client type. This diagnosis is what makes days 31 to 60 a decision instead of a guess.

Days 31–60: deploy the matched lever

With the shape of the gap known, month two is deployment, and the sequencing inside this month matters too. If any part of the gap is a chasing-discipline problem — which it usually at least partly is — automated follow-up goes on first, because it’s the cheapest, fastest lever and it will resolve a meaningful share of most gaps on its own within a few weeks. If part of the gap is a payment-friction problem, embedded payment links go into the invoice template for the affected accounts in parallel, not sequentially, since the two levers don’t interfere with each other and there’s no reason to wait. Selective invoice finance, if the diagnosis points to a genuinely structural gap in a specific slow-paying segment, is evaluated in this window too, but drawn down only against the accounts the diagnosis actually flagged — not the whole book, and not pre-emptively.

Most real gaps aren’t one shape cleanly — they’re a mix, and the aged receivables list from month one usually shows this once it’s actually read account by account rather than skimmed as a single total. A business might find eighty per cent of its gap is chasing discipline, spread thinly across dozens of small, otherwise-healthy accounts, and the remaining twenty per cent is two specific clients on genuinely long contracted terms. That’s not a contradiction requiring a single lever to fit all of it — it’s the normal case, and it’s exactly why the levers are deployed against the accounts that match them rather than against the book as a whole. Automated follow-up covers the eighty per cent; the two structural accounts either get left alone, if the terms are commercially fine and simply long, or get evaluated for selective finance if carrying them is genuinely constraining the business.

Days 61–90: track, hold, and quantify the release

The final month is where most operators stop paying attention, and it’s exactly the window where a fix that’s working can quietly start reverting if nobody’s watching the trend. The DSO trend sheet gets checked weekly, not glanced at occasionally, watching specifically for whether the gap identified in month one is actually closing at the rate the levers should be producing. By day 90, the plan produces two concrete outputs: an updated DSO figure to compare against the day-1 baseline, and a pounds-released figure calculated the same way the gap was quantified at the start — days of compression multiplied by average daily sales. That figure is the actual return on ninety days of a fairly modest amount of attention and, for most businesses, well under £100 a month of tooling cost.

Ninety days closes the initial gap. It does not, on its own, guarantee the gap stays closed — a DSO fix that isn’t reviewed on some ongoing cadence tends to drift back exactly the way it drifted in the first place, quietly and without anyone noticing until the trend sheet is checked again after too long a gap. That’s a different problem from the one this piece is solving, and it’s covered properly elsewhere in this catalogue; the plan above is specifically for closing a diagnosed, quantified gap, not for the operating discipline that keeps it closed afterwards.

THE WORKED EXAMPLE

Clarity Marketing Agency: 52 to 41

Clarity Marketing Agency is a B2B marketing agency on £1.2m of annual turnover, and it’s a useful worked example precisely because nothing about its situation was unusual. At the point it ran this plan, it was carrying roughly £170,000 in outstanding receivables against that turnover — capital the business owned outright but couldn’t reach, sitting in the gap between invoicing and payment rather than funding anything.

Days 1–30 gave the diagnosis its shape. Calculated properly, Clarity’s DSO was 52 days. Placed against the benchmark map, Clarity sits in professional services / recurring B2B services territory — a sector band of roughly 30–50 days — which put it meaningfully above its own sector norm rather than in some genuinely slow sector where 52 days would have been unremarkable. That distinction mattered: this was a real, quantifiable gap, not sector-normal drift being mistaken for a problem. The aged receivables list showed the drift wasn’t spread evenly: it was concentrated in a handful of mid-size accounts, all paying reliably eventually, just slowly and inconsistently, with no pattern suggesting a structural payment-term problem across the book.

That diagnosis pointed clearly at levers one and two rather than three. Days 31–60 switched on automated follow-up across the full receivables book, and added an embedded payment link specifically to invoices for the flagged mid-size accounts, making it a one-click action to pay rather than a manual bank transfer. No selective invoice finance was drawn down — the diagnosis hadn’t found a structural-terms problem, and pulling that lever would have priced finance against a gap that chasing and easier payment mechanics were already positioned to close for a few pounds a month.

Days 61–90 held the course and tracked it weekly. The mid-size accounts that had been drifting responded to the combination of consistent, automated chasing and a lower-friction way to pay faster than the rest of the book, which is exactly what the diagnosis predicted. By day 90, DSO had moved from 52 days to 41 — an eleven-day compression, just over a fifth of the starting figure. Using the same arithmetic that quantified the original gap, eleven days at roughly £3,300 a day released approximately £36,000 of working capital that had been sitting, unreachable, in the receivables book three months earlier.

Nothing about the fix required new capital, a lending relationship, or a difficult conversation with a client about payment terms. It required an accurate benchmark, an honest diagnosis of where the gap actually was, and two inexpensive tools switched on in the right order for the right reason. That’s the entire argument of this piece compressed into one business: DSO isn’t hidden because the fix is hard. It’s hidden because almost nobody measures it against a number that means anything, and a business can carry tens of thousands of pounds of reachable capital for years without ever correctly identifying that it’s there.

The 2028 baseline this catalogue is built against assumes a UK SMB population that can read this number correctly as a matter of course — not as a specialist skill, but as a standard operating literacy, the same way most operators already read a profit and loss account. Getting there is mostly a measurement problem, not a capital problem: the tools in this piece cost less in a year than most businesses lose to a single quarter of unread DSO drift. For operators who want the working template behind this piece — the four-sheet tracker, the full sector benchmark, and the lever-decision dashboard built to run this diagnosis on a business’s own numbers — that’s what the DSO & Working Capital Benchmark Capsule is built to hand over.

Read also

The Operating Rhythm Problem — the companion piece that follows this one three months later, on why a fix that holds in month one can drift back by month four. DSO & Working Capital Benchmark Capsule (CAP-002) — the full working template, in production now.