Order-to-Invoice Lag

A company accepts an order, ships the goods and sends the invoice two weeks later, and the customer may not start its payment clock until a correct invoice arrives. Order-to-invoice lag isolates the time between a defined order event and invoice issuance so teams can see where billing waits.

APQC describes stages in order-to-cash, including fulfilment and billing, and Hyperbots describes an order-to-invoice cycle measure, but the start and end timestamps vary in practice, so the metric needs an explicit local definition. Choose the start, since order receipt, acceptance or release to fulfilment can each be a different date, and choose the end, since invoice generation, dispatch and customer receipt are not equivalent and an invoice sitting in a queue may not be actionable for the buyer.

Handle partial orders, because one order can ship and invoice in several batches, by measuring each billable shipment or using a documented order-level rule. Measure business days or calendar days with one convention, since holidays and cutoffs affect interpretation.

Separate fulfilment from billing, because a long interval may be legitimate production time, not a billing failure, so break the total lag at the shipment or milestone. Track milestone services, since an invoice may only become due after contractual acceptance and a lawful wait is not an avoidable billing delay.

Watch unbilled work too: goods shipped or services accepted but not invoiced deserve a dated queue and owner, with recognition and contract rules confirmed separately. Record exceptions, because missing purchase order numbers, customer tax details or delivery evidence can block the invoice, and cause codes point to earlier process fixes.

Check master data, since a wrong customer address, invoice portal or billing entity can create rejections even if the invoice was generated quickly, and reconcile invoice delivery because an email sent to an inactive mailbox is not necessarily received. Track reissued invoices, since a first invoice rejected for error may not be usable, and report both initial issue and correct delivery where needed.

Segment order types, because standard stocked items, made-to-order equipment and projects have different normal lead times and a single average can mislead. Show the distribution, since a median can look good while a few large orders sit unbilled for months, and keep currency and value visible because a two-day delay on a large invoice can matter more than a ten-day delay on a tiny one.

Check credit holds and order amendments, deciding whether hold time is in the measure or shown separately, and keep the original accepted version with the amendment date when a changed price or scope pauses billing. Avoid backdating, since an invoice date earlier than dispatch can make the KPI look good while the customer receives it late, so preserve system audit timestamps.

Investigate queues, because orders ready to bill might wait for manual signoff or batch runs, and improve upstream data by capturing billing terms and customer references at order acceptance. Reconcile orders to invoices so every eligible shipment or milestone has a matching invoice or a documented exclusion, since a short lag for invoiced orders can hide orders never invoiced; faster invoicing may start the customer's payment process earlier, but invoice-to-cash payment behaviour is another measure, and for an owner the best analysis separates legitimate fulfilment time from avoidable billing delay.