Invoice Cycle Time

Invoice cycle time is the elapsed time between a supplier invoice being received by the business and the invoice being approved and ready for payment. It measures the speed of the AP processing workflow rather than the speed of payment -- cycle time ends when the invoice is approved, not when the bank transfer is executed. Payment timing is then a separate treasury decision based on payment terms and cash flow management.

Cycle time is typically measured in business days, from the timestamp when an invoice enters the AP queue to the timestamp when it receives final approval. Average cycle time, median cycle time, and percentage of invoices approved within a target window (e.g., within 3 business days) are the three most useful forms of this metric for managing AP performance.

Components of cycle time

Invoice cycle time has four stages, each of which can be measured independently. The first is capture time: how long from invoice receipt to the invoice being entered and available in the AP system. In a manual environment, capture time depends on how frequently the AP inbox is checked and how quickly data is keyed in. In an automated environment with real-time email processing, capture time can be under five minutes.

The second stage is coding time: how long from invoice entry to the invoice being assigned to the correct account, cost centre, and GST treatment. Manual coding requires AP staff judgment on each invoice; automated coding with machine learning matching to historical patterns eliminates most of this time for recurring suppliers and standard invoice types.

The third and typically longest stage is approval time: the elapsed time from invoice routing to the final required approver confirming the invoice. Approval time is driven by approver availability, approval queue management, and the number of approval stages required. A straightforward invoice requiring one approval from a manager who reviews their queue daily will have an approval time of zero to one day. An invoice requiring two approvals from managers who review their queues weekly can sit for up to five business days per stage.

The fourth stage is posting time: how long from approval to the invoice being recorded in the accounting system and scheduled for payment. In automated environments this is near-instantaneous. In manual environments it may involve a batch upload or manual journal entry that adds another day.

Why cycle time matters beyond efficiency

Long cycle times create late payment risk. If an invoice arrives on day 1, enters the AP queue on day 3 (manual capture), is coded on day 5, sits in approval for 8 days, and is posted on day 15, a 30-day payment term has already consumed 15 days of processing before the payment run schedule is even considered. Businesses with long cycle times consistently miss payment terms not because of cash flow problems but because of AP processing delays.

From a fraud risk perspective, long cycle times between invoice receipt and system entry create a window during which an invoice exists outside the accounting system and is not subject to duplicate detection or audit trail controls. Invoices that arrive by email and sit in an unprocessed inbox are invisible to the AP system and to any approval controls. Shortening the capture stage removes this blind spot.

Long approval stages where invoices sit unreviewed in email inboxes also create social engineering opportunities: fraudulent invoices that have been submitted and are awaiting approval can be followed up by the fraudster posing as the supplier, creating pressure to approve quickly that can override normal scrutiny.