Glossary · Metrics and reports

Invoice cycle time: definition and how it works in accounts payable

The time from receiving a supplier invoice to approving it for payment, usually measured in days.

Definition

The time from receiving a supplier invoice to approving it for payment, usually measured in days.

Also called: invoice processing time, receipt-to-approval time

What it means

Invoice cycle time runs from the moment the invoice arrives, whether that is a PDF in the AP inbox or a paper invoice at the mail desk, to the moment someone with authority approves it for payment. The clock starts on arrival, not on the invoice date. Those two dates can be days apart, and mixing them flatters the number or hides a problem depending on which way the gap runs.

People also call it invoice processing time or receipt-to-approval time. The definition is the same: elapsed days from receipt to approval. It stops at approval, not at payment. Payment timing depends on terms, payment runs and cash decisions, so keep the two measures separate or you will never know which one moved.

Track it per invoice and then summarize. The median shows the normal case, the typical invoice on a normal week. The slowest tenth shows where the exceptions sit, and that is where the cost hides. A fast median with a slow tail means most invoices sail through and a stubborn group does not.

Long cycle times cost early-payment discounts and bring reminder invoices. Those reminders are a common source of duplicates, because a second copy arrives while the first is still sitting in approval, and someone keys it in as new.

How it works in practice

The simple formula is approval date minus receipt date, in days. If an invoice arrived on Thursday, Jan 15, 2026 and was approved on Thursday, Jan 22, 2026, the cycle time is 7 days. Run that for every invoice, then look at the median and the slowest tenth rather than the average, which a few stalls can drag around.

Break the total into stages so you know where the days go: receipt to coding, coding to first approver, first approver to final approver. A 7 day total might be 1 day of coding and 6 days waiting on one approver. That tells you what to fix. A single total tells you only that something is slow.

Discounts make the number matter in dollars. Suppose a supplier offers 2 percent for payment within 10 days. An invoice for $10,000 earns $200 if it is approved and paid inside that window. If your cycle time runs past the deadline, you lose the $200. Compare the discount rate with your own cost of funds and decide case by case; that is a general financing judgment, not a rule.

Group results by supplier and by approver. One supplier with a slow cycle usually means a coding dispute or a missing purchase order. One approver with a slow cycle usually means a queue nobody watches when that person is away.

Where it goes wrong

The most common mistake is measuring from the invoice date. An invoice dated Monday, Jan 5, 2026 that reached the inbox on Thursday, Jan 15, 2026 has already lost 10 days before anyone touched it. Counting from the invoice date hides that gap and makes the team look faster than it is.

A second mistake is stopping the clock at data entry or at the first approval. Neither is approval for payment. If three people must sign off, the cycle ends when the last one does. Report the full span, then show the stages underneath.

Exceptions distort the picture. An invoice held for a missing receipt, a price mismatch or a vendor master change can sit for weeks, and a plain average smears that across everything. Look at the slowest tenth on its own. That is also where duplicates breed: a reminder copy arrives, gets keyed in, and now two records are moving toward payment for one delivery.

Unapplied vendor credits and overpayments often trace back to the same long tail. A credit note that arrives during a slow approval can get lost, and an overpayment can slip through when nobody compares the invoice to the purchase order before approval.

What to check

Confirm the start date on a sample of invoices. Pull 20 and compare the date the invoice arrived with the invoice date recorded in your ERP. If they differ, find out why and fix the capture step first, because every downstream number depends on it.

Check that approval means final approval for payment. Ask who the last signer is on a typical invoice and confirm the timestamp is captured. If your ERP does not record the approval timestamp, the vendor record and the approval trail may still show it.

Review the slowest tenth by supplier, approver and exception reason. Look for repeat offenders and ask what holds them. Then check whether any of those invoices missed an early-payment discount they could have earned, and put a dollar figure on the delay.

Finally, scan the slow tail for duplicate risk. Compare reminder invoices against invoices already in the system before they are keyed in, and reconcile vendor statements monthly to catch credits and overpayments that never got applied. Small checks on the slow group catch more money than another report on the fast one.

Questions

What is invoice cycle time?

It is the time from receiving a supplier invoice to approving it for payment, usually measured in days. Count it from the date the invoice arrived, not the invoice date. It stops at approval, not at payment.

Should I measure from the invoice date or the date received?

From the date the invoice arrived. The invoice date can be days earlier, and counting from it hides the gap between the supplier sending the invoice and your team receiving it. Use the arrival date every time so the number is comparable.

Why do long invoice cycle times cost money?

They cost early-payment discounts, because the payment window can close before approval. They also bring reminder invoices, and those reminders are a common source of duplicates when a second copy gets keyed in as new. Compare any discount rate with your own cost of funds before deciding what to chase.

Updated Nov 18, 2026. Figures on this page are calculated by ERPSav from the definitions shown. The explanatory text is drafted with AI from those figures and checked automatically before it is published. General information only, not legal, tax or financial advice.