Grading the Payer: A Four-Tier Method for Pricing Customer Risk Before Invoicing

Late payment rarely arrives without warning. It is usually the visible end of a pattern that was present at onboarding: a slow purchase ledger, a culture of querying invoices, a sector under margin pressure, or a monthly payment run that swallows invoices submitted after a cut-off. UK suppliers often treat each overdue invoice as a fresh surprise. A payment behaviour scorecard treats it as data.

The scorecard is not a credit rating and it is not a substitute for formal credit checks. It is an internal ranking of how a customer is likely to behave once an invoice has been issued. Used properly, it should shape terms, deposits, credit limits and the intensity of chasing before any work begins. As of November 2026, the case for doing this is straightforward: cash is still expensive, and the cost of financing a slow payer falls most heavily on smaller suppliers.

Start with four measurable inputs

A workable scorecard can be built from four inputs. First, average days late. Measure from the contractual due date to the date cleared funds arrive, not from the invoice date. Use your own ledger for existing customers and trade references for new ones. Exclude genuinely disputed invoices from the late-payment figure, but record the dispute separately. Second, dispute frequency. Track how often a customer raises a query, how long it takes to resolve, and whether disputes cluster around the same issue, such as missing purchase order numbers or poorly specified milestones.

Third, sector pressure. A customer in a sector with thin margins, long retention periods or heavy subcontracting may be slower than its own intentions suggest. Fourth, payment-run patterns. Many larger UK organisations pay on fixed weekly or monthly cycles. An invoice that misses the cut-off can wait another month even if the payer is not in financial difficulty. Ask about the payment run schedule during onboarding and record it.

Weight the inputs and score each customer

A simple weighting is 35% for average days late, 25% for dispute frequency, 20% for sector pressure and 20% for payment-run pattern. Score each input from one to four, where one is best and four is worst. Multiply by the weight and add the totals. The exact weights matter less than consistency. If construction retentions are a material risk for your business, increase the sector weighting. If your invoices are routinely queried for administrative reasons, increase the dispute weighting.

The output should be a band, not a false precision. An A customer pays on or before the due date, raises few disputes and has a predictable payment run. A B customer pays up to 14 days late on average and occasionally queries an invoice. A C customer is 15 to 30 days late, disputes more often or operates in a pressured sector. A D customer is more than 30 days late, has unresolved disputes or pays unpredictably. New customers should be scored provisionally and reviewed after the first three invoices.

Turn the band into terms and chase intensity

The scorecard only earns its keep if it changes behaviour. For A customers, standard 30-day terms may be appropriate, with automated reminders three days before the due date and a polite follow-up on day one. For B customers, consider shorter terms, a modest deposit or a lower credit limit. Call two days before the due date and escalate within three days of non-payment. For C customers, a deposit of 30% to 50%, stage payments and a weekly ledger check are more appropriate. Pause work if a stage payment is seven days overdue. For D customers, require prepayment or milestone-only billing. Do not extend credit simply because the customer is well known.

Chase intensity should be planned, not emotional. The same overdue invoice should trigger the same sequence every time: reminder, phone call, formal letter, suspension of work and, where necessary, statutory demand or debt recovery. The scorecard tells you how quickly to move through those steps. It also gives you evidence for a conversation about terms. If a customer objects to a deposit, the scorecard is the commercial reason: the risk is priced, not personalised.

Use sector data carefully

Sector pressure is context, not an excuse. The UK construction sector is well known for retentions, complex supply chains and payment practices that can leave subcontractors waiting. Hospitality and retail can be similarly exposed to seasonal cash flow. Public sector bodies often have prompt payment targets, but their administrative processes can still be slow. A scorecard should not stereotype every customer in a sector; it should adjust the default risk and then let actual behaviour modify the score. A construction customer with a clean payment record should not be treated as a D simply because of its sector.

Payment-run patterns deserve more attention than they usually receive. A customer that pays on the last Friday of the month is not necessarily late-paying, but an invoice issued after its cut-off may effectively be 30 days slower. Ask for the cut-off date, the payment run frequency and the portal requirements. Then invoice earlier. A supplier that understands the payment run can improve its cash flow without changing a single contract term.

Keep the process fair and defensible

Use business data lawfully. Under UK GDPR, keep records relevant and proportionate, and avoid collecting personal data that you do not need. Record the evidence behind a score: the dates, the invoice numbers, the dispute notes and the source of any trade reference. Do not rely on informal hearsay or on protected characteristics. The scorecard should be reviewed quarterly and whenever a customer changes ownership, procurement system or payment process. A good payer can become a bad one after a merger; a bad payer can improve after a finance director change.

The scorecard will not guarantee payment. It will, however, stop you from cross-subsidising slow payers with the cash flow of faster ones. In a year when UK suppliers are still being asked to do more with less working capital, that is a modest but useful discipline. Rank the customer before the invoice is raised, and the overdue invoice becomes a managed event rather than a surprise.