What it means
The clock usually starts when an invoice is received, whether by email, post or a supplier portal, and stops when it is fully approved and posted for payment. Some teams stop the clock at payment instead, so the first job when comparing figures is to agree exactly what is being measured.
The metric matters because everything downstream depends on it. A supplier offering 2% off for payment within ten days is worthless if invoices take fourteen days to approve, and chronically slow processing invites suppliers to tighten credit terms or demand payment up front.
Processing time is also a good proxy for how well the whole payables process is designed. Long averages almost always point to specific bottlenecks: invoices sitting in a shared inbox, approvers on holiday with no delegate, or purchase order mismatches that nobody chases.
Calculation is straightforward but the detail matters. Add up the days elapsed for every invoice in the period and divide by the number of invoices, using working days rather than calendar days if that is how the team is measured.
The common variant is to look at the distribution rather than just the mean. A median of four days with a small tail of invoices taking forty days tells a very different story from a uniform seven days, and the tail is usually where the disputes and the damaged supplier relationships live.
In practice
Real-world examples.
Example
A hotel group finds its average processing time is 11 days, driven almost entirely by invoices from one region where approvals still travel by internal post. Moving that region onto the same electronic approval workflow as the rest of the group cuts the group average to 6 days.
Example
A construction contractor discovers that invoices matched to a purchase order clear in 3 days while unmatched invoices take 19. The finance director makes purchase orders mandatory above $1,000, which removes most of the slow tail.
Example
A software company reports a healthy 5 day average to its board but the payables manager points out the median is 2 days and 8% of invoices take more than 30 days. Those slow invoices belong to a single supplier whose contract terms nobody can find.
Think of it
“Invoice processing time is how long it takes to handle and pay invoices-your AP speed.
Formula
Calculation
Average invoice processing time = total days elapsed across all invoices / number of invoices processed
A distribution business processes 4,800 supplier invoices in a quarter. Adding the elapsed days for each invoice gives a total of 33,600 days.
The average is 33,600 / 4,800 = 7.0 days per invoice. Management wants to capture a 2% early settlement discount that requires payment within ten days, which leaves only three days of slack for the payment run itself.
Suppose annual purchases subject to that discount are $24,000,000. Capturing the full 2% would be worth $480,000 a year, so cutting the average from 7.0 days to 4.0 days, and the tail of slow invoices with it, is worth far more than the cost of the workflow software needed to do it.Case study
Seen in the real world.
The following case is illustrative and the company is fictional. Cedarline Foods, an invented regional wholesaler, processed about 18,000 supplier invoices a year and had never measured how long approval took. It knew only that two suppliers had recently moved it from 30 day terms to payment on delivery.
When the controller finally measured it, the average was 16 days and the worst decile stretched past 45. The cause was not laziness but design: invoices arrived at four different email addresses, were rekeyed by hand, and needed two signatures regardless of value.
In this illustrative story, Cedarline set a single intake address, introduced automatic matching against purchase orders, and removed the second signature for invoices under $2,500. Average processing time fell to 5 days within two quarters, the two suppliers restored normal terms, and the company began capturing early settlement discounts worth around $110,000 a year.
Watch out
Common mistakes.
- Reporting only the average, which hides the small tail of very slow invoices that causes almost all the supplier complaints.
- Starting the clock when the invoice is entered into the accounting system rather than when it arrived, which flatters the figure by ignoring time spent in an inbox.
- Treating slow processing as a staffing problem when the real cause is usually approval design, missing purchase orders or unclear ownership.
Questions
People also ask.
What is a reasonable target?
Many finance teams aim for an average of three to five days for matched invoices, with anything beyond ten days treated as an exception to be investigated.
Does this metric include disputed invoices?
It should, but flag them separately, because a genuine dispute is a commercial issue rather than a processing failure and mixing the two distorts the average.
How is it different from days payable outstanding?
Processing time measures internal speed from receipt to approval, while days payable outstanding measures how long you actually take to pay, which is partly a deliberate cash decision.
From the founder's library
Take it further with the book.
Build your financial confidence beyond this definition. Shihan's full-length guide, Accounting Fundamentals, takes the same plain-English approach and turns it into a complete, practical playbook for non-finance managers, business owners and students - with chapter-end quiz answers and presentation slides included.
25% off with code MMHQ25, applied at checkout. Priced in USD - checkout may show the equivalent in your local currency.
View the book and save 25%