Payment Terms Compliance

Payment terms state when an invoice must be paid and may include early-payment discounts, so a due date should reflect the actual agreement; an invoice issued on Monday is not automatically due thirty days later. For accounts payable, the business tracks whether it pays suppliers on time, while for accounts receivable it tracks whether customers pay it on time, and combining the two into one rate would hide who is responsible.

An agreed due date may depend on acceptance of goods, invoice receipt or a fixed calendar date, so read the contract and invoice terms together and avoid setting an artificial due date from an unsupported rule. A simple count-based measure divides the number of eligible invoices paid by their due date by the number of eligible invoices that reached a due date in the period, then multiplies by 100, and the method should state how partial payments count.

A value-weighted version may divide on-time paid value by total due value and can differ sharply from the count-based rate; ten small invoices paid promptly and one large one late show why both views can help. For a fictional period, 90 of 100 eligible supplier invoices due are fully paid on time, so count-based compliance is 90%, which does not say whether the ten late invoices were large or small.

Clarify what paid means, because a company may initiate a transfer before the due date that reaches the supplier afterward, and the agreement or reporting policy should determine the relevant settlement point. Disputed invoices require a rule: a valid dispute might pause or alter a due date under some agreements while a slow internal approval might not, so log the reason rather than quietly excluding late items.

Credit notes, cancellations and duplicate invoices need a consistent policy; a reversed invoice may be removed with an audit trail, and a partially disputed invoice may need more careful treatment than a simple exclusion. The denominator matters as much as the numerator, because counting only invoices already paid can omit overdue unpaid invoices and inflate compliance.

Include all eligible obligations whose due dates fell in the window, and keep due-date cohorts clear, since an invoice that has not reached its due date belongs in the outstanding balance, not the matured denominator. Payment terms may also change after negotiation, so keep the version effective for each invoice, because using today's standard terms to score an old invoice can rewrite history incorrectly.

Accounts payable teams should capture invoices promptly, since a bill received and entered late can miss the payment run despite sufficient cash, and process time is a separate cause from deliberate late payment. Accounts receivable teams need accurate invoices and clear terms, because an incorrect purchase order or missing details may delay a customer's approval, so follow up on the root cause as well as the headline rate.

A company can also monitor median days late for the misses, since one day late and sixty days late both count as failures in a binary measure. A high compliance rate does not prove fair terms, because a business could pay every invoice within a very long contractual window, so review both the length of terms and actual days to payment.

The UK Fair Payment Code offers example thresholds for paying within set numbers of days, but those belong to a specific voluntary scheme and jurisdictional context and should not be turned into a global legal definition of compliance. Report by supplier or customer segment, not only overall, because a concentrated pattern with small vendors can be masked by large-volume payments elsewhere, and label the direction, due-date cohort and exclusions so late-payment reasons can improve the process.