Days payable outstanding (DPO): definition and how it works in accounts payable

What it means

Days payable outstanding is the average number of days a company takes to pay its suppliers. The formula is DPO = accounts payable / cost of goods sold × days in the period. Ending accounts payable of $1,250,000 and annual cost of goods sold of $9,000,000 give DPO = $1,250,000 / $9,000,000 × 365 = 50.7 days.

AP clerks also see the measure called DPO, creditor days or payable days. It is a summary of payment timing, not an invoice-level status. A DPO figure does not show which invoices are unpaid, disputed or missing from the ledger; the accounts payable aging report and the vendor record show that detail. Use DPO with those records rather than as a stand-alone answer.

The base and period matter. Some teams use total purchases or total spend instead of cost of goods sold; state the base you use. A DPO based on cost of goods sold and a DPO based on total spend are not interchangeable, and comparing them without restating the base can mislead. Payment terms also differ by country, company and contract, so a DPO that is normal for one supplier group may be unusual for another.

How it works in practice

In practice, DPO comes from three things: when invoices are recorded, when they are due under the contract, and when they are paid. An invoice recorded late leaves ending accounts payable lower than it should be, so DPO can look lower even if the team paid on the same schedule. An invoice recorded on time but paid later raises DPO. The AP clerk should be able to trace an invoice from the vendor record to its due date and payment date.

Payment terms set the reference point. A supplier's contractual due date, discount date and payment run schedule all affect actual payment timing. If an early-payment discount is taken, payment may move earlier and DPO may fall; that can be reasonable if the discount is better than your own cost of funds. Dynamic discounting works on the same general principle, and it belongs with the terms review, not with a target DPO set in isolation.

The worked example shows how the inputs produce the result. The same $1,250,000 of ending accounts payable against annual cost of goods sold of $9,000,000 over a 365-day period gives 50.7 days. If a team instead uses total purchases or total spend, it must state that base and must not compare the result directly with the 50.7-day cost-of-goods-sold figure without restating it.

DPO also moves with volume and mix. A period-end balance can be affected by a large invoice recorded near cutoff, a credit note posted late, or a payment run that falls just after period end. Those are recording and timing effects, not necessarily a change in how the AP team negotiates or pays. Explain the driver before treating a change as a performance result.

Where it goes wrong

A common mistake is to calculate DPO from ending accounts payable alone and treat the result as a clean measure of payment behavior. Ending accounts payable is a snapshot, and it can be distorted by unrecorded invoices, late credit notes or goods received not invoiced. Reconcile the accounts payable ledger to the general ledger at period end and review the vendor record for open items before relying on DPO.

Another mistake is mixing bases. A controller may compare a DPO based on cost of goods sold with a DPO based on total purchases or total spend and draw a conclusion that the base does not support. Write down the formula, the period and the base on the report. Use the same definition each period, and restate any comparison that uses a different base.

AP teams also treat a higher DPO as free cash. A higher DPO keeps cash longer but can cost early-payment discounts and supplier goodwill. Review the discount terms and compare the discount rate with your own cost of funds; a discount can be worth taking even if it lowers DPO. Also watch for supplier queries, holds and delivery issues that suggest the delay is hurting the relationship.

Changes in DPO can come from payment terms, payment timing or simply from when invoices are recorded. A DPO increase caused by holding invoices unrecorded is not a cash improvement; it is a recording problem. A DPO decrease caused by paying early to capture a discount is not necessarily a failure. Judge the change against the terms and the cash effect, not against the direction alone.

What to check

Check the inputs first. Confirm the accounts payable balance at period end, the cost of goods sold or other stated base, and the number of days in the period. The formula should match the report label: DPO = accounts payable / cost of goods sold × days in the period. If the report uses total purchases or total spend, make sure the label says so and that prior periods use the same base.

Check cutoff and completeness. Look for invoices received before period end but not recorded, credit notes posted after period end, disputed invoices still open, and goods received not invoiced. These items can change ending accounts payable and therefore DPO. The accounts payable aging report and vendor record are the practical places to find them.

Check payment timing against the contract. Compare payment dates with due dates and discount dates, and review payment runs that fall near period end. A DPO above the contractual terms may point to late payments, disputed items or unrecorded invoices; a DPO below the terms may reflect early payment for discounts or supplier requests. Terms differ by country, company and contract, so use the relevant terms rather than one rule for all vendors.

Check comparisons before acting. Use the same period, base and scope, and read DPO alongside the aging report, discount capture and supplier queries. Do not use DPO alone to judge AP performance, and do not treat a change as good or bad without the underlying payment and recording detail.

Questions