DPO explained: days payable outstanding, and when to stretch it
DPO explained: the days payable outstanding formula, a worked example at 36.5 days, and where stretching supplier terms starts to cost you money.
Days payable outstanding is the average number of days you take to pay suppliers. Divide accounts payable by cost of goods sold for the period, then multiply by the days in that period. A manufacturer with $2.4M of AP and $24M of annual COGS has a DPO of 36.5 days.
Key takeaways
- DPO = (accounts payable ÷ COGS) × days in period. Using credit purchases instead of COGS is more accurate and usually lands a day or so lower.
- DPO is only meaningful against your weighted average supplier terms, not against the terms of your biggest supplier.
- At $24M of annual COGS, every extra day of DPO is worth $65,753 of cash held — and most of the first few days come from payment-run timing, not renegotiation.
- Stretching past terms is borrowing at an undisclosed rate: lost discounts, price uplifts and lost priority in a shortage.
- A rising DPO with a falling on-time payment rate is not working-capital skill. It is a liquidity signal your suppliers will read before you do.
Supplier credit is the cheapest financing on your balance sheet, right up to the day it isn't. Days payable outstanding measures how much of it you are using. Read alongside the terms you actually agreed, it tells you whether you are leaving free money on the table or quietly borrowing from your supply base at a rate nobody wrote down.
- Days payable outstanding (DPO)
- The average number of days between receiving a supplier invoice and paying it. It converts the accounts payable balance into days so it can be compared directly against the payment terms your suppliers granted you.
The days payable outstanding formula
DPO = (Accounts payable ÷ Cost of goods sold) × Days in the periodThe purist's version replaces COGS with credit purchases, because payables arise from what you bought, not from what you sold. The two agree only when inventory is flat.
Credit purchases = COGS + (closing inventory − opening inventory)
DPO = (Accounts payable ÷ Credit purchases) × Days in the period- Accounts payable — trade payables only. Strip out accruals, intercompany balances, payroll liabilities, tax payable and anything sitting in AP because there was nowhere else to book it. This single clean-up moves most people's DPO by several days.
- Cost of goods sold or credit purchases — for the same period, on the same basis, every period. Pick one and write the definition down.
- Days in the period — actual calendar days: 30, 31, 90, 91, 365. Rounding a month to 30 makes your monthly series wobble for no reason.
Worked example: 36.5 days on paper
A manufacturer, full year. Cost of goods sold $24,000,000. Trade accounts payable $2,400,000. Inventory rose $600,000 over the year, so credit purchases were $24,600,000.
COGS basis:
DPO = (2,400,000 ÷ 24,000,000) × 365 = 0.1000 × 365 = 36.5 days
Purchases basis:
DPO = (2,400,000 ÷ 24,600,000) × 365 = 0.0976 × 365 = 35.6 daysThe gap opens because the company built stock: it bought $24.6M and consumed $24.0M. Whenever inventory is growing, the COGS basis flatters DPO; whenever inventory is being run down, it understates it. Neither is wrong. Reporting them interchangeably is.
Computes DPO on either basis, shows days beyond your weighted supplier terms, and prices what adding or losing days does to your cash.
36.5 days is late — until you weight the terms
The obvious next step is to compare 36.5 days against the terms. If someone says "we're on net 30", the conclusion looks bad: 6.5 days late. That conclusion is usually wrong, because "we're on net 30" is almost never true across a whole supply base.
Split the same $24,000,000 of spend by the terms actually granted: $18,000,000 on net 30, $6,000,000 on net 60. Weight the terms by spend, not by supplier count.
Weighted terms = (18,000,000 × 30 + 6,000,000 × 60) ÷ 24,000,000
= (540,000,000 + 360,000,000) ÷ 24,000,000
= 900,000,000 ÷ 24,000,000
= 37.5 days
Days beyond terms = 36.5 − 37.5 = −1.0 daySame company, same DPO, opposite verdict. Against a headline "net 30" it looks 6.5 days late; against its real weighted terms it is paying a day early and has roughly a day of free credit it is not using. Every DPO conversation should start by rebuilding the weighted terms, and it is the number most AP dashboards never show.
What a day of DPO is worth
Average daily cost of sales is $24,000,000 ÷ 365 = $65,753. Every day of DPO you add is that much cash held one day longer, and it stays held for as long as the new behaviour does.
Those are not clever numbers, they are just $65,753 multiplied by 5 and by 8.5 days. The interesting part is where the days come from. The first three or four are usually free.
| Source of days | Typical gain | Cost to you | Who has to agree |
|---|---|---|---|
| Clean non-trade items out of the AP balance | Reported DPO only — no real cash | None, but your number was wrong before | Nobody |
| Pay weekly instead of twice weekly | About 3.5 days | None, if nothing goes past due | Your AP team |
| Stop paying ahead of due date to clear the queue | 2–6 days, depending on habit | None | Your AP team |
| Renegotiate terms with your top spend suppliers | 10–30 days on that spend | Possible price uplift | The supplier |
| Just pay late | As many as you dare | Discounts, price, priority, goodwill | Nobody — which is the problem |
The payment-run arithmetic is worth spelling out. If invoices fall due evenly across the week and you pay every Friday, an invoice waits on average 3 days past its due date. Move to a fortnightly run and the average wait becomes 6.5 days. That is 3.5 extra days of DPO, or 3.5 × $65,753 = $230,137 of cash, from a calendar change. It also concentrates your outflows, so check the cash forecast before you do it.
Where stretching backfires
Extending DPO past terms is borrowing. The rate is real, it is just never quoted to you. Four ways the bill arrives.
- 1.Lost early payment discounts. Skipping a 2/10 net 30 discount to pay on day 30 costs (2 ÷ 98) × (365 ÷ 20) = 37.2% annualised. Stretching that same invoice to day 45 spreads the 2% over 35 extra days instead of 20, which still costs 21.3% a year. Both rates beat almost any credit facility you have. The full arithmetic, both sides, is in is a 2/10 net 30 discount worth it and in the early payment discount calculator.
- 2.Price uplift at renewal. Suppliers price payment behaviour. A 1% price increase on $24,000,000 of spend is $240,000 a year, every year — permanently more expensive than the $558,904 of one-off cash that eight and a half extra days released.
- 3.Loss of priority when supply is short. In an allocation, the supplier ships to the customer who pays. This cost never appears in a working-capital report; it appears as a stockout and a missed shipment.
- 4.Signalling. Your suppliers' credit insurers watch payment behaviour. A DPO that climbs while your on-time payment rate falls reads as distress, and the response is tighter terms or a credit hold — the exact opposite of what you were trying to achieve.
What is a good DPO?
Days beyond terms close to zero, with a weighted terms figure you deliberately negotiated upwards over time. That is the whole answer. A high DPO achieved by lateness is worse than a low DPO on short terms, because one is a liability and the other is a to-do list.
| Pattern | What it usually means | What to do |
|---|---|---|
| DPO well below weighted terms | Payment runs are too frequent, or AP pays on receipt to clear the queue | Pay on due date. Free cash, no negotiation |
| DPO within a day or two of terms | The process is working as designed | Push on terms at renewal instead of on behaviour |
| DPO above terms, on-time rate healthy | Your weighted terms figure is out of date, or a large supplier group is on longer terms than you thought | Rebuild weighted terms from the spend data |
| DPO above terms, on-time rate falling | You are financing yourself from the supply base | Fix the liquidity problem; do not report the DPO as a win |
DPO in the wider cycle
DPO is the one leg of the working-capital cycle that works in your favour: cash conversion cycle = DIO + DSO − DPO. It is also the leg most easily improved for the wrong reasons. Consolidating purchases onto quarterly buys to win terms will lengthen DPO and lengthen DIO by more, leaving the cycle worse. Always check the cycle, not the leg — the cash conversion cycle calculator does it in one pass.
There is a symmetry worth remembering: your DPO is your suppliers' DSO. Every day you add to yours, you add to somebody's collections problem — and the levers they will use on you are exactly the ones described in how to bring DSO down.
Getting DPO out of your ERP
The hard part is not the division. It is trade AP separated from accruals and intercompany, purchases separated from COGS, and terms weighted by spend rather than by vendor record — for six periods, by entity. That is typically two saved searches, a vendor-terms export and a lookup formula that breaks whenever someone adds a payment term.
Ask "what is our DPO by quarter for the last two years, trade payables only, and what are our spend-weighted supplier terms?" and the answer comes back computed from your own account with the query shown underneath, so you can audit the definition rather than accept it. Read-only by default — nothing in AP moves.
Frequently asked questions
What is the DPO formula?
DPO = (accounts payable ÷ cost of goods sold) × days in the period. The more accurate variant divides by credit purchases, which equal COGS plus the change in inventory. Use trade payables only — accruals, intercompany balances and payroll liabilities do not belong in the numerator.
What is a good DPO?
One that sits within a day or two of your spend-weighted supplier terms, with a healthy on-time payment rate. There is no universal target: 45 days is excellent against net-45 terms and poor against net-60. A high DPO produced by paying late is a liability, not an achievement.
Is a high DPO good or bad?
It depends entirely on how you got it. High DPO from negotiated long terms is cheap financing. High DPO from paying past due costs you discounts, price concessions at renewal and supply priority during shortages, and signals distress to credit insurers. Always read DPO next to on-time payment rate.
Should DPO use COGS or credit purchases?
Credit purchases are technically correct, because payables come from purchases rather than sales. COGS is used more often because it is easier to extract. The two diverge whenever inventory changes: build stock and the COGS basis overstates DPO, run stock down and it understates it. Pick one and stay with it.
How do I increase DPO without damaging supplier relationships?
Take the free days first. Clean non-trade items out of the AP balance, stop paying ahead of due date, and reduce payment-run frequency — moving from twice-weekly to weekly runs is worth roughly 3.5 days. Then negotiate longer terms at renewal, in exchange for volume or forecast commitments rather than silence.
What is the relationship between DPO and DSO?
They are mirror images: your DPO is your supplier's DSO. Both feed the cash conversion cycle, which is DIO + DSO − DPO. Raising DPO and lowering DSO both shorten the cycle and release cash, but only DPO does it using someone else's balance sheet.
Calculators for this
Calculate days payable outstanding from your AP and COGS. See how far you sit from supplier terms and what five more days of DPO is worth in cash.
Work out the annualised cost of 2/10 net 30 from either side, compare it to your cost of capital, and get a clear take-it-or-leave-it answer.
Work out your cash conversion cycle from day figures or raw balances. See CCC, working capital funded, and the cash a five-day move in each leg frees.
Calculate working capital from your current assets and liabilities. Get current ratio, quick ratio, working capital as a % of revenue and days of coverage.
Keep reading
The cash conversion cycle explained: CCC = DIO + DSO − DPO, a full worked example at 65 days, and how to cut each leg without breaking the other two.
Is 2/10 net 30 worth it? The annualised cost is about 37%. Worked maths for buyers taking a discount and sellers offering one, against cost of capital.
DSO explained plainly: the formula, the three variants people confuse, realistic benchmarks by industry, and the seven levers that actually move it.
Collection effectiveness index (CEI) explained: the formula, a worked example at 70.4%, realistic targets, and why CEI beats DSO for judging collections.