Invoices that fail the customer's match: stale master data in billing

The most common failure in customer invoicing starts in the master files. A purchase order, price or bill-to contact changes on the customer's side, the billing record does not, and invoices go out that the customer's payables team cannot match. They sit on hold while receivables look healthy.

How it starts

Customers change things without telling the billing team. A new purchase order replaces one that has been used up. A contract renewal moves a unit price. An accounts payable mailbox is retired after a reorganisation. Sales usually hears about these changes first. The news rarely travels as far as the customer and product master files.

Billing data is then generated from the old record. The invoice looks correct inside the seller's own system because it agrees with everything that system knows. It is transmitted on schedule and the receivable posts cleanly.

On the customer's side, the invoice meets a matching step. Their payables staff compare it against the order and the receiving record. When the order reference is closed or the price differs from what was agreed, the invoice fails validation and gets parked. Some customers send a rejection notice. Many send nothing.

Why nobody notices at first

The ledger shows an open item that is not yet overdue. Nothing about it looks unusual. Collections staff only start chasing once the due date passes, and by then several more invoices have gone out carrying the same bad reference.

Electronic delivery makes this worse in one particular way. A portal or e-invoicing channel may accept the file and still reject it later in the customer's workflow. The seller's transmission log reports success. Few people think to look further.

How it gets spotted

The first real signal tends to come from collections. A customer says they have no record of an invoice, or that it is "on hold pending a valid PO." When the same answer comes back for several invoices to one customer, the pattern points at master data and not at a single billing slip.

Other clues are worth watching. Overdue balances concentrate on a few accounts that historically paid well. Cash arrives short, with the customer paying the old price and leaving the difference open. Billing inquiries rise right after contract renewals or customer system changes. Credit memos and rebills cluster on the same customer records.

An ageing report sorted by customer will show the concentration. An ageing report sorted by invoice date will not, which is why this failure hides for so long.

Fixing the invoices already out

Start by confirming with the customer exactly what their system needs: the live order reference, the agreed price, the correct remit and contact details. Get it in writing from their payables team. Sales contacts often give an answer that differs from what the matching rules require.

For each held invoice, decide whether the customer can update it on their side or needs a fresh document. Where a new invoice is required, issue a credit memo against the original and rebill with correct data. Record the adjustment against the receivable so the open item and the replacement do not both age. Skipping the credit and simply sending a second invoice creates duplicates that someone will have to unpick at month end.

Short payments need a separate decision. If the old price was wrong, credit the difference. If the new price was never agreed, it becomes a commercial dispute and should leave the billing queue.

Fixing the cause

The lasting fix is ownership of the master record. One role should be accountable for customer billing attributes, with a defined trigger to update them whenever a contract, order or customer contact changes. Contract renewals and new purchase orders belong in that trigger list explicitly.

Add a check before billing data is generated. Invoices referencing an order that is expired, exhausted or missing should stop for review. The same applies to prices that disagree with the active contract.

Close the loop on transmission too. Wherever a customer portal returns status, read the rejection messages and route them back to billing promptly. A delivery confirmation is not acceptance.

Finally, treat billing inquiries as data. Tag each one with its root cause when it is resolved. Master data errors then show up as a trend that can be acted on, and stop being a stream of one-off complaints.

Questions to ask the people who run it

• When a customer issues a new purchase order, who finds out, and how does it reach the master file?
• Do billing staff ever override the order number or price on an invoice by hand? Why?
• Which customers reject invoices through a portal, and who reads those rejections?
• When collections hears an invoice is on hold, where does that information go next?
• How is a rebill handled today: credit and reissue, or a second invoice sent alongside the first?
• Are there customers whose invoices are always corrected manually before sending? What is wrong with their record?
• Who is allowed to change customer billing data, and is anyone checking those changes?
• When a billing inquiry is closed, is the reason recorded anywhere that someone reviews?

APQC's Process Classification Framework® (PCF) is an open standard developed by APQC, a nonprofit that promotes benchmarking and best practices worldwide. To download the full PCF or to view definitions and measures, please visit www.apqc.org/pcf.