Days payable outstanding

Glossary definition of days payable outstanding (DPO), what it measures, how it relates to margin drift, and its limits as a metric. Read the full guide.

Twitter LinkedIn WhatsApp
Ask AI: ChatGPT Claude Gemini Grok
Days payable outstanding

Days payable outstanding is the average number of days a company takes to pay its vendor invoices after receiving them. It is a working capital metric, calculated from accounts payable, cost of goods sold, and a chosen period, and it tells a CFO how supplier credit is being used relative to cash on hand. Finance teams watch it alongside days sales outstanding and cash conversion cycle, but on its own it says nothing about whether the amount being paid is correct.

Days payable outstanding, DPO, measures payment timing, not payment accuracy. A rising DPO can mean a company is managing cash well, or it can mean invoices are stuck in dispute, held up by mismatched purchase orders, or delayed by an AP team working through error corrections. Extending DPO without checking invoice accuracy just delays the payment of an overcharge.

A CFO tracking DPO should treat it as one half of a two-part discipline: how long you take to pay, and whether what you are paying is what the contract actually says.

1. What is days payable outstanding?

Days payable outstanding is the average number of days a company takes to pay its suppliers after receiving an invoice, calculated as accounts payable divided by cost of goods sold, multiplied by the number of days in the period. A higher DPO means the company is holding cash longer before paying vendors; a lower DPO means it is paying faster. It is reported quarterly or annually and compared against prior periods and peers.

The formula uses a balance sheet figure, accounts payable, against an income statement figure, cost of goods sold, over a stated period such as 90 or 365 days. Because it blends a snapshot with a flow, DPO is an average across every vendor and invoice in the period, not a figure for any one payment.

A change in DPO can come from a deliberate shift in payment terms, from a change in purchasing volume, or from invoices sitting unpaid because of a dispute or an error. The calculation does not separate these causes; it only reports the average days outstanding.

2. How does DPO differ from cash flow timing alone?

DPO is often read as a pure cash management lever: pay later, keep cash longer, improve working capital. That reading is only correct if every invoice being paid is correct. If a batch of invoices includes a rate card error or a duplicate charge, holding cash longer on those invoices delays the eventual correction, not the underlying leakage.

The metric measures speed, not the correctness of what is being paid.

Extending terms with a vendor changes DPO by design and is a legitimate cash strategy. But an unmanaged rise in DPO driven by invoices stuck in AP review for accuracy reasons looks identical in the ratio to a deliberate terms extension.

Separating the two requires looking at why individual invoices are aging, not just the average. An AP team that flags invoices for rate or contract mismatches will show a higher DPO on those items until resolved, which is a sign the review process is working, not a sign of cash strategy.

3. Why does DPO matter for margin drift?

Margin drift is the gap between what a vendor contract says and what the invoice actually charges. A company managing DPO by simply delaying all payments, without checking invoice accuracy first, will eventually pay every drifted charge in full, just later than before. The AP hold that improves DPO only creates value when it is also used to catch a pricing error before the invoice clears.

Invoice review for accuracy and invoice review for payment timing can run through the same AP queue, but they answer different questions. One asks when to pay. The other asks whether the amount is right against the rate card and contract terms.

A company that wants both benefits builds the accuracy check into the same hold that produces its DPO number, rather than treating them as separate workflows.

Timing discipline: managing DPO on its own extends the vendor payment cycle to preserve cash, independent of whether the invoiced amount is correct.

Accuracy discipline: checking the invoice against the contract catches rate errors, surcharge misuse, and missed credits before the payment is made, not after.

4. What does DPO fail to show a CFO?

DPO does not show which vendors are overbilling, which invoices contain a rate that no longer matches the contract, or which credit memos were never applied. It is an average across the whole vendor book, so a handful of significantly overpaid or underpaid invoices can sit inside a DPO figure that otherwise looks stable. A stable DPO is not evidence that invoice amounts are correct.

Because DPO aggregates every payable into one ratio, it cannot flag a single vendor category, contract, or invoice line as a problem. Two companies with the same DPO can have very different amounts of billing error sitting inside their payables.

Finding those errors requires a separate review of invoices against contract terms: rate cards, volume tiers, surcharge schedules, and rebate clauses. That review sits underneath DPO and produces its own findings, independent of how many days the company took to pay.

For the wider pattern this sits inside, start with the margin drift guide. See also margin drift vs. legitimate price increases: how to tell them apart and off-contract resources: people billed outside the agreement.

5. Frequently Asked Questions (People Also Ask)

What is a good days payable outstanding number?

There is no single good number; it depends on the company's vendor terms, industry, and cash strategy. A useful comparison is the company's own DPO against its stated payment terms and against its own prior periods, not against an external benchmark figure.

How is days payable outstanding calculated?

DPO equals accounts payable divided by cost of goods sold, multiplied by the number of days in the period being measured, typically 90 or 365 days. The result is expressed as an average number of days.

Does a higher DPO always mean better cash management?

Not necessarily. A higher DPO can reflect a deliberate extension of payment terms, or it can reflect invoices held up by disputes, mismatched purchase orders, or unresolved billing errors. The ratio alone does not distinguish the two.

Can DPO hide overbilling from vendors?

Yes. DPO is an average across the entire vendor book, so a rate card error or a missed credit memo on individual invoices does not show up as a change in DPO. The metric tracks timing, not the accuracy of the amounts being paid.

Is DPO the same as the cash conversion cycle?

No. DPO is one input into the cash conversion cycle, which also includes days sales outstanding and days inventory outstanding. Cash conversion cycle measures the full time between paying for inputs and collecting cash from sales.

Should a company extend DPO to improve cash position?

Extending payment terms can improve cash position, but it should follow, not replace, a check that invoiced amounts match the contract. Holding cash longer on an invoice that contains a pricing error only delays paying that error, it does not prevent it.

How does invoice accuracy review interact with DPO?

An AP hold used to check an invoice against contract terms will extend that invoice's days outstanding until resolved. This raises DPO on those items, but it reflects a working accuracy check, not a cash strategy.

What is the difference between DPO and a rate card audit?

DPO reports how long a company takes to pay across all invoices. A rate card audit checks whether the price on a specific invoice matches the contracted rate. They answer different questions and neither substitutes for the other.

1. What is days payable outstanding?

Days payable outstanding is the average number of days a company takes to pay its suppliers after receiving an invoice, calculated as accounts payable divided by cost of goods sold, multiplied by the number of days in the period. A higher DPO means the company is holding cash longer before paying vendors; a lower DPO means it is paying faster. It is reported quarterly or annually and compared against prior periods and peers. The formula uses a balance sheet figure, accounts payable, against an income statement figure, cost of goods sold, over a stated period such as 90 or 365 days. Because it blends a snapshot with a flow, DPO is an average across every vendor and invoice in the period, not a figure for any one payment. A change in DPO can come from a deliberate shift in payment terms, from a change in purchasing volume, or from invoices sitting unpaid because of a dispute or an error. The calculation does not separate these causes; it only reports the average days outstanding.

2. How does DPO differ from cash flow timing alone?

DPO is often read as a pure cash management lever: pay later, keep cash longer, improve working capital. That reading is only correct if every invoice being paid is correct. If a batch of invoices includes a rate card error or a duplicate charge, holding cash longer on those invoices delays the eventual correction, not the underlying leakage. The metric measures speed, not the correctness of what is being paid. Extending terms with a vendor changes DPO by design and is a legitimate cash strategy. But an unmanaged rise in DPO driven by invoices stuck in AP review for accuracy reasons looks identical in the ratio to a deliberate terms extension. Separating the two requires looking at why individual invoices are aging, not just the average. An AP team that flags invoices for rate or contract mismatches will show a higher DPO on those items until resolved, which is a sign the review process is working, not a sign of cash strategy.

3. Why does DPO matter for margin drift?

Margin drift is the gap between what a vendor contract says and what the invoice actually charges. A company managing DPO by simply delaying all payments, without checking invoice accuracy first, will eventually pay every drifted charge in full, just later than before. The AP hold that improves DPO only creates value when it is also used to catch a pricing error before the invoice clears. Invoice review for accuracy and invoice review for payment timing can run through the same AP queue, but they answer different questions. One asks when to pay. The other asks whether the amount is right against the rate card and contract terms. A company that wants both benefits builds the accuracy check into the same hold that produces its DPO number, rather than treating them as separate workflows. Timing discipline: managing DPO on its own extends the vendor payment cycle to preserve cash, independent of whether the invoiced amount is correct. Accuracy discipline: checking the invoice against the contract catches rate errors, surcharge misuse, and missed credits before the payment is made, not after.

4. What does DPO fail to show a CFO?

DPO does not show which vendors are overbilling, which invoices contain a rate that no longer matches the contract, or which credit memos were never applied. It is an average across the whole vendor book, so a handful of significantly overpaid or underpaid invoices can sit inside a DPO figure that otherwise looks stable. A stable DPO is not evidence that invoice amounts are correct. Because DPO aggregates every payable into one ratio, it cannot flag a single vendor category, contract, or invoice line as a problem. Two companies with the same DPO can have very different amounts of billing error sitting inside their payables. Finding those errors requires a separate review of invoices against contract terms: rate cards, volume tiers, surcharge schedules, and rebate clauses. That review sits underneath DPO and produces its own findings, independent of how many days the company took to pay. For the wider pattern this sits inside, start with the [margin drift](/insights/margin-drift-spend-leakage-guide) guide. See also [margin drift vs. legitimate price increases: how to tell them apart](/guides/margin-drift-vs-legitimate-price-increases-how-to-tell-them) and [off-contract resources: people billed outside the agreement](/guides/off-contract-resources-people-billed-outside-the-agreement).

Questions & Answers

What is a good days payable outstanding number?

There is no single good number; it depends on the company's vendor terms, industry, and cash strategy. A useful comparison is the company's own DPO against its stated payment terms and against its own prior periods, not against an external benchmark figure.

How is days payable outstanding calculated?

DPO equals accounts payable divided by cost of goods sold, multiplied by the number of days in the period being measured, typically 90 or 365 days. The result is expressed as an average number of days.

Does a higher DPO always mean better cash management?

Not necessarily. A higher DPO can reflect a deliberate extension of payment terms, or it can reflect invoices held up by disputes, mismatched purchase orders, or unresolved billing errors. The ratio alone does not distinguish the two.

Can DPO hide overbilling from vendors?

Yes. DPO is an average across the entire vendor book, so a rate card error or a missed credit memo on individual invoices does not show up as a change in DPO. The metric tracks timing, not the accuracy of the amounts being paid.

Is DPO the same as the cash conversion cycle?

No. DPO is one input into the cash conversion cycle, which also includes days sales outstanding and days inventory outstanding. Cash conversion cycle measures the full time between paying for inputs and collecting cash from sales.

Margin Drift Resources