Accounts Payable Metrics: 15 KPIs Every AP Team Should Track

Cost per invoice puts a dollar value on your AP process. It is one of the core measures used in AP benchmarking and a useful starting point for finance leaders.

Example: AP spends $100,000 in a quarter and processes 20,000 invoices. $100,000 ÷ 20,000 = $5.00 per invoice.

What to include: fully loaded staff costs (salary plus benefits), software, scanning and OCR, printing and postage, payment fees, storage, and outsourced services. Leaving out major costs makes the process look cheaper than it is.

Watch out: One blended number hides a lot. Split it by invoice type. PO invoices, non-PO invoices, and exceptions usually cost very different amounts. To estimate what manual processing costs your team today, try our AP cost calculator.

This shows how much volume your team handles relative to its size. APQC uses it as a key AP productivity measure.

Example: 20,000 invoices a year handled by 10 FTEs = 2,000 invoices per FTE, or about 167 a month.

Watch out: Count FTEs honestly. Two people who each spend half their week on AP equal one FTE. And do not use this to rank individuals. Invoice complexity, exception volume, and the number of entities and currencies all change what "productive" looks like.

Invoice cycle time is how many calendar days an invoice takes to move through AP. It is sometimes called invoice processing time. This is the most common metric people calculate wrong, so define it carefully.

Example: 1,000 invoices take a combined 8,000 days from receipt to approval. 8,000 ÷ 1,000 = 8 days.

Pick your end point. You can measure cycle time from receipt to approval, from receipt to payment scheduling, or from receipt to payment, depending on what you want the metric to show. Define the start and end points clearly and use the same definition every month. The first shows how fast your process runs. The second also includes payment terms. If you pay on day 30 on purpose, the second number will always be around 30 days, even if approval took one day. Track both, and label them clearly.

Watch out: Do not mix up cycle time with touch time. Cycle time is elapsed days. Touch time is the minutes someone actually spends working the invoice. An invoice can need 6 minutes of work and still wait 9 days. Touch time drives cost per invoice. Cycle time drives late payments and missed discounts. For where the time goes step by step, see our guide to invoice processing in AP.

Approval time isolates the wait between sending an invoice for approval and getting the final sign-off. It is often the biggest single part of cycle time, and it usually happens outside the AP team.

Example: An invoice is routed at 10:00 a.m. Monday and approved at 2:00 p.m. Tuesday. Approval time is 28 hours.

How to report it: Use the median, not just the average. A few invoices stuck for a month will drag the average up and hide what normally happens. Then break it down by approver and by approval level to see exactly where invoices wait.

Common causes of slow approvals: approvers who are out, invoices sent to the wrong person, unclear approval rules, email-based routing, and no reminders. Rule-based invoice approval software addresses most of these directly.

The share of invoices that cannot move through the normal flow and need someone to review or fix them.

Example: 500 exceptions out of 10,000 invoices = 5%.

Make it actionable with reason codes. A single exception rate tells you there is a problem. Reason codes tell you what it is. Tag every exception, for example: PO mismatch, missing PO number, price variance, quantity variance, unknown vendor, missing approval, tax error, or suspected duplicate. If 60% of exceptions are "missing PO," the fix is in purchasing, not AP.

How often invoice data is captured correctly the first time, whether by a person or by OCR.

Example: 9,800 of 10,000 invoices needed no field corrections = 98%.

Watch out: Decide whether you measure at the invoice level or the field level. Field-level accuracy (correct fields ÷ total fields) always looks higher, because one wrong field in a 20-field invoice still counts as 95% correct. Invoice-level is stricter and closer to the work your team actually has to redo.

For PO-backed invoices, this shows how many match the purchase order and required invoice data on the first try, without manual correction.

Example: 8,500 of 10,000 PO invoices match first time = 85%.

Watch out: Only count PO invoices in the denominator. Including non-PO invoices makes the rate meaningless. A low rate usually points upstream: outdated PO prices, partial receipts not recorded, or vendor master data that does not match the invoice.

How often the same invoice gets paid more than once.

Example: 6 duplicates in 12,000 payments = 0.05%. Small as a percentage, but worth reporting in dollars too.

Track two numbers. Duplicates paid is the lagging number: the damage already happened. Duplicates caught before payment is the leading number: it shows your controls working. Duplicates usually slip through when the same invoice arrives by email and mail, vendor names are entered differently, or invoice numbers are not validated. Regular AP reconciliation helps catch the ones that get past capture.

The share of payments that go out correct the first time: right vendor, right amount, right bank account, right date, with no reversal or correction later. APQC tracks this as "percentage of disbursements that are first time error free."

Example: 24 payments needed correction out of 12,000. (12,000 − 24) ÷ 12,000 = 99.8%.

Why it matters: This is the control check on every speed metric. A team that gets faster while this number falls is not improving. Errors in bank details deserve extra attention, since they can signal vendor fraud, not just a typo.

Also called straight-through processing rate. It is the share of invoices that move through the defined AP workflow without manual AP intervention.

Example: 7,000 of 10,000 invoices flowed through untouched = 70%.

Define "touch" in writing. Does a required business approval count as a touch? Most teams say no, since that approval is a control, not rework. Does an AP clerk checking a flagged field count? Yes. Without a written definition, the number can be inflated by simply changing what counts. Many teams also track a broader "automation rate" (share of AP steps handled by workflow), but touchless rate is easier to define and compare.

Watch out: Always read it next to data accuracy and error-free payments. Touchless only helps if the data flowing through is right. For how straight-through processing works in practice, see our page on touchless invoice processing.

How often invoices are paid by their due date.

Example: 9,500 of 10,000 invoices paid on time = 95%.

Late is not the only problem. Also watch invoices paid well before the due date with no discount. Paying a Net 45 invoice on day 10 for no reason gives up cash you could have kept. Good payment timing means paying on time, not as early as possible. Consistent timing is also one of the easiest ways to build stronger vendor relationships.

Some suppliers offer a discount for paying early. This metric shows how much of that available discount you actually take.

Example: $40,000 captured of $50,000 offered = 80%.

Why it's worth tracking: Common terms like "2/10 net 30" offer a 2% discount for paying 20 days earlier than the normal due date. The implied annualized benefit can be substantial, depending on the calculation method. Few uses of cash beat that. If discounts are missed because approvals are slow, this metric ties a dollar value directly to your approval time.

Watch out: Measure in dollars, not just invoice count, and record why each missed discount was missed (late approval, invoice received late, cash decision). Taking a discount can be the wrong call when cash is tight, so this is a finance decision, not only an AP one.

DPO is the average number of days a company takes to pay suppliers. It is a working capital metric that sits alongside days sales outstanding (DSO) in the cash conversion cycle, which we cover in our guide to accounts payable vs accounts receivable.

Example: Average AP of $2 million, annual COGS of $12 million. ($2M ÷ $12M) × 365 = 60.8 days.

Some companies use purchases instead of COGS, depending on their business and reporting methodology. The important point is to use a consistent formula and clearly state which denominator you use.

Watch out: Higher DPO is not automatically better. It keeps cash longer, but a DPO far beyond your standard terms often means late payments, late fees, and unhappy suppliers. Read it next to on-time payment rate and discount capture.

AP turnover shows how many times a company uses and settles its average accounts payable balance during a period.

Example: $12 million in credit purchases and $2 million average AP = 6 times a year.

How it connects to DPO: Divide the days in the period by turnover and you get average days to pay. 365 ÷ 6 ≈ 61 days, matching the DPO above when both use the same base. They are two views of the same behavior, so you rarely need to present both to leadership. Pick the one your CFO already uses.

How often suppliers contact AP asking about invoice or payment status. It is a metric many AP dashboards skip, but it captures work that never shows up in invoice counts.

Example: 300 inquiries against 10,000 invoices = 3 per 100 invoices.

Why it matters: Every "where's my payment?" email is time your team is not processing invoices. A rising rate is often the first sign of slow approvals or poor payment visibility, before on-time rate starts to fall. Tag inquiries by reason to see what drives them.