Where customer invoicing breaks: handoffs, exceptions and workarounds

Customer invoicing usually breaks at handoffs: order or contract terms arrive at billing incomplete, and customer records drift away from what sales agreed. Exceptions then get fixed by hand, often through credit notes and off-system edits. Each break leaves a trace in disputes and in cash that nobody can apply.

Customer and product records that drift

An invoice is only as accurate as the master file behind it. Customers move offices, change legal entities and switch to new purchase order rules. Sales negotiates a special price and never updates the price list. The billing system keeps using the old record because nobody owns the change.

The evidence is usually easy to find. Look for invoices returned because of a wrong address or a missing purchase order reference. Check how often billers override prices at the point of invoicing. Search for duplicate accounts that belong to one legal entity. Watch for tax codes corrected by hand after the invoice is drafted. Any of these means the master data process sits outside billing, and billing is cleaning up after it.

The handoff from order to billing data

Billing depends on someone else confirming that goods shipped or work was accepted. That confirmation often arrives late, partial or in the wrong form. Contract amendments live in email threads. Milestone sign-offs sit with a project manager who is travelling. Usage data comes from an operations system that billing cannot query directly.

When this handoff fails, the billing team becomes a chasing function. Signs include an unbilled accrual that keeps growing, invoices raised and then cancelled because the quantity changed, and billers keeping their own trackers of what they are waiting for. If staff describe billing runs in terms of who they had to ring first, the problem sits upstream.

Getting the invoice to the customer

Large customers increasingly require portals, structured electronic formats or their own reference fields. A rejection in a customer portal is often silent. The invoice looks sent in the billing system while the customer has nothing payable on file.

The giveaway is collectors hearing that an invoice was never received. Ask whether anyone checks portal rejection inboxes. Ask how often PDFs are resent by email to get something paid. Where one person knows the quirks of a key customer's format, the process depends on that person being at their desk.

Posting the receivable

The invoice and the ledger entry should be the same event. In practice they separate. Invoices are drafted in one period and released in the next. Manual journals adjust revenue without touching the subledger. Interface failures leave entries in suspense.

The receivables subledger failing to agree with the general ledger is the clearest symptom. So are reconciling items that carry forward with the same description each period, and revenue adjustments posted by people outside the billing team.

Inquiries, credits and adjustments

This is where rework multiplies. A customer disputes a line. The query goes to sales, then back to billing, then to the customer again. Eventually someone issues a credit note and a fresh invoice. The root cause, usually a master data error or a late order change, is never recorded, so it happens again.

Look for credit notes followed by reissued invoices against the same order. Look for dispute reason codes where most entries fall under a generic option. Customer short payments and deductions taken without agreement point the same way. When credits can be raised without a reason that links back to an earlier step, the adjustment process is absorbing failures it cannot see.

Workarounds that hide the problem

Workarounds keep cash coming in, which is why they survive. Common ones include holding invoices in draft until someone confirms details informally, maintaining a spreadsheet of customer billing rules outside the system, and approving price overrides by message. Each one makes the formal process look healthier than it is. Before changing anything, map these, because a redesign that removes them without fixing the cause will slow billing down.

Questions to ask the people who run it

Documented procedures describe the intended path. The people doing the work know the real one. Useful questions include:

• Which invoices get held back before release, and who decides when they go?
• Where do order or contract changes reach billing from, and how do they arrive?
• Which customers need special handling, and where is that handling written down?
• What happens when a customer portal rejects an invoice? Who finds out?
• When a credit note is raised, who approves it and what reason gets recorded?
• Which corrections are made directly in the ledger instead of in the billing system?
• What spreadsheets or personal lists are used to get a billing run out?
• If one person were away during a billing run, what would stop?

The answers often contradict the process map. That contradiction is the most reliable guide to where the real breaks are.

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.