# The 20-Fold Late-Payment Gap Hiding Behind the Invoice Total Source: https://www.digiparser.com/blog/late-payment-size-gap [See all posts](/blog) Last updated on September 29, 2026 # The 20-Fold Late-Payment Gap Hiding Behind the Invoice Total Research Late payments Small business [![Pankaj Patidar](https://avatars.githubusercontent.com/u/17493609?v=4) Pankaj Patidar @thepantales ](https://x.com/thepantales) ![The 20-Fold Late-Payment Gap Hiding Behind the Invoice Total](https://www.digiparser.com/research/late-payment-size-gap/size-gap.png) **Among UK businesses affected by late payments, microbusinesses had approximately 20 times as much annual turnover tied up in late payments as large businesses: 4.61% versus 0.23%.** DigiParser calculated this ratio from Table 3 of [London Economics' July 2025 research for the Department for Business and Trade and Office of the Small Business Commissioner](https://assets.publishing.service.gov.uk/media/688a089a6478525675738ff9/late_payments_research_impact_on_uk_economy.pdf#page=11). Business size Employees, as labeled in source Late-payment balance / annual turnover Relative to large firms Micro 0-9 4.61% 20.0x Small 10-49 1.47% 6.4x Medium 50-249 0.79% 3.4x Large \>250 0.23% 1.0x The figures describe affected businesses. The report includes overdue invoices and payment terms exceeding 60 days in its definition of late payment. The source does not resolve the 250-employee boundary in this table; we retain its labels. ## The invoice total is a poor measure of supplier strain Our view: a payment dashboard that ranks every unresolved invoice by pounds alone answers an accounting question, but misses an important supplier-management question: **how large is this unpaid amount relative to the business waiting for it?** An invoice has at least two scales. One is its face value. The other is its importance to the supplier. A buyer can see the first immediately. Understanding the second requires context, rather than a guess based on the size of the payment. Consider an illustrative comparison. Two suppliers each have GBP 10,000 awaiting payment. One has GBP 200,000 in annual sales; the other has GBP 2 million. The same balance represents 5% of sales for the first and 0.5% for the second. That is a tenfold difference in exposure created entirely by the denominator. These are example businesses, chosen to show the calculation. This does not tell us either supplier's cash reserves, profit margin or ability to pay wages. It tells us why a list of invoice amounts cannot answer those questions. Treat relative exposure as a prompt for a useful conversation, not a substitute for one. > A small invoice on the buyer's dashboard can be a large cash-flow event for the supplier. ## Build a payment queue that can explain itself We recommend making the reason for every held supplier invoice visible. A generic "pending" status is insufficient for action. Separate missing information, a commercial dispute, an approval delay and a scheduled payment. Give each item a named owner and a next action. A compact weekly scorecard could contain the following fields: Field Question it should answer Agreed due date When did we agree to pay? Invoice received date How long has this document been inside our process? Hold reason What specific fact or decision prevents payment? Responsible owner Who can resolve the next step? Supplier communication date When did we last explain the status? Next action and date What will happen next, and when? Keep an invoice's contractual due date separate from its planned payment date. Otherwise, moving an item to a later payment run can make the dashboard look orderly while hiding the original commitment. When capacity is limited, review overdue items, approaching due dates and unresolved disputes explicitly. Use supplier context to escalate a conversation. Do not require a small supplier to disclose sensitive financial information before it can receive money already due. ## Test the handoff before buying another dashboard Here is a practical exercise for an accounts-payable team. Choose a small, permitted sample of recently delayed invoices. For each one, trace receipt, data entry, approval, exception resolution and payment scheduling. Record the first point at which the next person lacked either the information or the authority to proceed. Then group the cases by that stopping point. Did the invoice arrive at an unattended mailbox? Was its reference missing? Was a receipt awaiting confirmation? Had someone approved it without passing the approval to the person preparing payments? This exercise gives the team a concrete change to test. Agree on a measure before making that change. For example, measure elapsed time from invoice receipt to assignment of an owner, or the proportion of held invoices with a dated next action. Compare the same measure afterward. Avoid calling a faster extraction step a faster payment unless the payment timing also changed. DigiParser can support the document-data stage described in our [supplier invoice processing guide](/blog/vendor-invoice-processing). Extraction, review and export can make invoice information available for the next step. Approval decisions, disputes and payment execution still need their own controls and owners. This page concerns the buyer's supplier-invoice and AP process. The seller's collection process requires a separate view of customers, agreed terms and outstanding receivables. Connecting the two perspectives should make responsibility clearer, not combine two different workflows into a single ambiguous queue. ## How we calculated the comparison We divided each published turnover percentage by 0.23. For microbusinesses, 4.61 divided by 0.23 equals approximately 20.04, reported as 20-fold. Ratios use rounded source inputs. This compares exposure, not payment frequency, delay duration or insolvency risk. Analysis date: 29 September 2026; underlying report: July 2025. ## Download and reuse Download the [comparison CSV](/research/late-payment-size-gap/size-comparison.csv), [calculation script](/research/late-payment-size-gap/reproduce.py), [PNG chart](/research/late-payment-size-gap/size-gap.png) or [SVG chart](/research/late-payment-size-gap/size-gap.svg). Reuse DigiParser's chart with a link to this page and keep the underlying source attribution and affected-business label. Cite the government report for its estimates and this page for the calculated comparison. The script reproduces the CSV and SVG with Python 3 and no additional packages. Suggested citation: DigiParser, "The 20-Fold Late-Payment Gap Hiding Behind the Invoice Total," 29 September 2026. * * * [See all posts](/blog) Automate recurring documents next: [supplier invoice parser](/solutions/invoice-parser), [customer purchase order parser](/solutions/purchase-order-parser), and [extract data from PDF](/solutions/extract-data-from-pdf) hub. ## Transform Your Document Processing Start automating your document workflows with DigiParser's AI-powered solution. [Start Free Trial](https://app.digiparser.com/auth/join)[Schedule Demo](/contact)