Days Payable Outstanding Calculator
The formula
What the days payable outstanding tells you
How long the business holds supplier invoices before paying — the payables mirror of collection speed, and a lever on the cash conversion cycle.
Calculation: DPO = payables ÷ purchases × days. Enter your inputs and every substitution is shown below the result.
Reading the result
Rising DPO boosts cash and the cycle headline; just ask whether suppliers priced the delay back into your costs or added you to their watchlist.
Rules of thumb: 30–45 typical B2B; large retailers push 60–90; auto and aerospace suppliers are famously stretched
Limitations and best practice
DPO is the most gameable working-capital metric — a single quarter-end payment freeze flatters it. Compare against invoiced terms and payment-discount usage.
This calculator gives an estimate based on standard formulas; it is not professional financial, medical, legal or engineering advice. Verify anything you plan to act on with a qualified professional and your own records.
Frequently asked questions
Is high DPO good or bad?
How does DPO interact with the cash cycle?
Source & methodology
Standard payables ratio; norms from supply-chain finance benchmarks.
Days Payable Outstanding: what this tool answers
Time is the one input nobody can renegotiate, which makes getting the arithmetic right worth the minute it takes. Days Payable Outstanding is the kind of number people argue about from memory. This page ends that argument with arithmetic you can watch happen: enter your figures, get Days payable outstanding in real time, and see every substitution printed below.
People rarely disagree about arithmetic; they disagree about assumptions that were never written down. Printing the substitution and the sensitivity ranking removes that category of disagreement for Days Payable Outstanding.
The number itself is the easy part. What takes judgement is knowing which inputs are facts in your situation and which are guesses wearing a decimal point — a distinction this page makes explicit for every field above.
Every figure in the prose is generated by the engine rather than written beside it — the worked example resolves to days payable outstanding = 33.1 days on the default inputs, and the sensitivity section ranks the inputs that move the result — COGS or purchases over period first, at ≈11.1 % of the headline for a ten-percent error either way in that input. Work down the page and by the end you could re-derive the result in a spreadsheet from memory.
How Days Payable Outstanding is computed, line by line
The engine implements a single stated model: DPO = payables ÷ purchases × days. There is no hidden coefficient and no login-gated precision — the formula printed is the formula executed, which is also what makes the result citable.
Accounts payable ($) (example value 239,926) is a plain measured quantity — the unit shown in the label is the unit the formula expects. If you are unsure what belongs in this field, look at the printed steps: the substitution shows exactly how the engine uses it.
COGS or purchases over period ($) (example value 4,900,000) is a plain measured quantity — the unit shown in the label is the unit the formula expects. Replace the example with the figure from your own records — the tool recomputes instantly and the printed steps follow your numbers.
Days in period (example value 675) is a numeric input whose unit is fixed by the label; a wrong unit is a wrong answer wearing a plausible disguise. Be precise about the boundary (exact date, start of month); time inputs decide the exponent in most formulas.
A fully worked Days Payable Outstanding example
Abstract formulas are hard to trust, so here is the complete substitution using the default inputs, written the way an examiner would want it. Starting figures: Accounts payable ($), COGS or purchases over period ($), Days in period. Run to the end, the days payable outstanding resolves to 33.1 days — Paying fast: good terms secured, but the float is leaving early on the bands this tool uses.
- DPO = $239,926 ÷ $4,900,000 × 675 = 33.1 days
- That is how long supplier cash sits on your side of the table
Average daily purchases — $7,259. If your inputs change, this is usually the first companion figure to move.
Supplier float held — $239,926. If your inputs change, this is usually the first companion figure to move.
Value of float at 8% short-term rate — $19,194. Compare it against the main result of 33.1 days before drawing conclusions.
Overwrite any input above and every line of this example updates with it — the substitution is live, not a screenshot of somebody else’s numbers.
How far Days Payable Outstanding can reasonably move
The honest version of any estimate is a corridor, and this one is cheap to produce: Days Payable Outstanding was recomputed at 5 points along the dominant input, with every other field left untouched.
| COGS or purchases over period setting | Days payable outstanding |
|---|---|
| 80 % of the example value | 41.3 days |
| 90 % of the example value | 36.7 days |
| example inputs | 33.1 days |
| 110 % of the example value | 30.0 days |
| 120 % of the example value | 27.5 days |
Across 5 settings of COGS or purchases over period, the result spans 27.5 days to 41.3 days. A decision that only works at one row of this table is a decision waiting for an input to move. Reproduce it in the form above by editing COGS or purchases over period alone; the substitution steps will follow your figures exactly.
What actually moves your Days Payable Outstanding
Generic advice says “it depends on your inputs”; this section says exactly how much. Each field was perturbed by ±10 % in isolation and the days payable outstanding recomputed, so the ranking below is measured rather than asserted. For Days Payable Outstanding the ranking is measured rather than guessed, and it belongs to these defaults: shift the starting point and the order can shift with it.
- Nudge COGS or purchases over period by ±10 % and Days Payable Outstanding lands between 30.0 days and 36.7 days (sensitivity ≈11.1 %)
- Nudge Accounts payable by ±10 % and Days Payable Outstanding lands between 29.7 days and 36.4 days (sensitivity ≈10.0 %)
- Days in period: ten percent up gives 36.4 days, ten percent down gives 29.7 days — ≈10.0 % of the days payable outstanding either way
COGS or purchases over period is the dominant lever here: ten percent either way moves the result by about 11.1 %, from 30.0 days to 36.7 days. Spend your verification effort there first, and treat Accounts payable as the second priority (≈10.0 % per ten percent). The rest of the inputs earn only a rounding-error of attention, and that asymmetry is the practical payoff of measuring rather than asserting.
Interpreting the Days Payable Outstanding verdict
Nobody acts on a bare figure — they act on a figure with a comparison attached. The verdict attached to the default calculation — “Paying fast: good terms secured, but the float is leaving early” — is one band on a ladder your own figure may sit somewhere else on. How much of that band is luck? On COGS or purchases over period alone ten percent either way covers 30.0 days to 36.7 days. The practical reading rules: compare against your own history before comparing against other people; treat band boundaries as zones, not walls — one point on the wrong side of a threshold rarely changes a real outcome; and when a companion output contradicts the headline, believe the pair.
The comparison worth making is not with somebody else’s Days Payable Outstanding but with the version of your own situation measured last quarter — same formula, same conventions, different inputs.
How people get Days Payable Outstanding wrong
DPO is the most gameable working-capital metric — a single quarter-end payment freeze flatters it. Compare against invoiced terms and payment-discount usage. This calculator gives an estimate based on standard formulas; it is not professional financial, medical, legal or engineering advice. Verify anything you plan to act on with a qualified professional and your own records.
Reporting the headline and quietly discarding Average daily purchases. The companions are where the shape of the trade-off survives the rounding.
Attention is also misallocated between fields. Having measured this engine, we can say where it belongs: COGS or purchases over period first, everything else second.
The subtlest error is answering the wrong question precisely. Confirm that days payable outstanding is actually the quantity your decision needs — the arithmetic is flawless either way, which is what makes the mistake invisible.
Days Payable Outstanding verification checklist
- Check that every field the formula needs actually arrived from a document, not from recollection.
- Note the date and the inputs beside the number so the figure can be audited later.
- Check COGS or purchases over period before anything else: it is the measured dominant input, ≈11.1 % of Days Payable Outstanding per ten percent.
- Re-run the calculation with a ±10 % stress on the two most sensitive inputs.
- Confirm the example values are plausible for your own situation before replacing them.
- Repeat the ±10 % test on the inputs that matter and see whether the decision — not just the number — still holds.
Five steps from raw inputs to a figure you can defend
The tool does the arithmetic; the routine below is what makes the arithmetic trustworthy. Five steps, a minute total — and afterwards you will know not just what the number is, but which assumption produced it.
Step 1 — collect, then type. Everything this tool asks for is listed above (accounts payable ($), cogs or purchases over period ($), days in period). Pull each figure from something you can point at — paperwork, a dashboard, a label — before touching a field. Guesswork at the input stage cannot be repaired at the interpretation stage. Say the answer out loud before you save it; if it sounds wrong, the model did not change, your understanding did.
Step 2 — compute the version you would not be embarrassed by. If a stranger audited your inputs, which set would you hand over? Enter that set, read the result, and treat everything else as upside. Compare the calculation to the rough guess you arrived with, and ask why they differ.
Step 3 — isolate your variables. Change one field, observe, revert. The live sensitivity list does the ranking for the default inputs; verify it against your own, because dominance shifts when the starting point shifts. If the answer changes your behaviour, it deserves a second run with different assumptions.
Step 4 — stress before you commit. A decision that survives a ten-percent squeeze on its two biggest inputs needs no luck to be sound. One that does not survive is a decision about hope, not about arithmetic. If the verdict changes with a ten-percent nudge, report the nudge alongside the number.
Step 5 — schedule the next run. In Business & Entrepreneurship the inputs drift quietly. Put a reminder a quarter out, re-enter the same fields, and read the change rather than the level. A calculation you cannot explain to somebody else is a calculation you cannot defend.
Where Days Payable Outstanding matters in practice
Most Financial Analysis disagreements are arithmetic disagreements in disguise. When Days payable outstanding of 33.1 days sits on the table with its working shown, the conversation stops being about who sounds more confident and starts being about which input is wrong. A figure with a date beside it becomes evidence; without one it stays an anecdote.
The companion outputs — Average daily purchases and Supplier float held — exist for the second stage of that screen: the headline sizes the prize, while the companions describe the trade-off you are accepting to get it. One decimal place more than your data supports is one decimal place of fiction.
Re-running this page costs nothing and catches the slow drifts that never announce themselves. In Business & Entrepreneurship the expensive mistakes are rarely sudden; they are small changes in Accounts payable ($) that nobody recalculated for a year. Most surprises in numbers are surprises about inputs, not about formulas.
People also ask about Days Payable Outstanding
What affects Days Payable Outstanding the most?
The short answer: COGS or purchases over period. The longer answer is the sensitivity table on this page, where every numeric input was probed by ten percent and the days payable outstanding recalculated — COGS or purchases over period moved it furthest, by roughly 11.1 % (30.0 days to 36.7 days).
Which matters more: accounts payable or cogs or purchases over period?
By the numbers, COGS or purchases over period: a ten-percent change in it moves the result ≈11.1 %, versus ≈10.0 % for Accounts payable. Spend your measuring effort in that order — precision on the weaker lever buys almost nothing.
What is a typical Days Payable Outstanding?
On the worked example above Days Payable Outstanding comes out at 33.1 days. Treat that as one point on a distribution rather than a norm: the bands, the companion outputs and the sensitivity ranking tell you how wide the plausible range really is.
How do I calculate Days Payable Outstanding by hand?
Three steps: write the formula (DPO = payables ÷ purchases × days), insert your values, and simplify. The worked example section shows exactly that chain for the default inputs; replicating it once on paper teaches you more about Days Payable Outstanding than any number of calculator runs.
What happens to Days Payable Outstanding if cogs or purchases over period changes by 10 %?
The engine was re-run with that field moved by ten percent while everything else stayed fixed: the days payable outstanding goes across 30.0 days to 36.7 days, a swing of roughly 11.1 % around the 33.1 days baseline. That ratio is the practical definition of how much this input matters.
Is the Days Payable Outstanding result of 33.1 days good or bad?
Good and bad are comparisons, so the honest test is three questions: where does your own Days Payable Outstanding sit against the 33.1 days reference above, how far would a plausible input error move it (≈11.1 % per ten percent on COGS or purchases over period), and what does the alternative option compute to?
How often should I check Days Payable Outstanding?
Whenever an input changes by more than a few percent, and otherwise on the rhythm of your decisions — before a purchase, a review, a renewal. Days Payable Outstanding is a snapshot, not a subscription; stale snapshots are the most common silent error in Business & Entrepreneurship planning.
What affects Days Payable Outstanding the most?
Sensitivity depends on where you start, but the inputs Accounts payable ($) and COGS or purchases over period ($) typically move Days Payable Outstanding further than the rest because they enter the formula multiplicatively. If you can only measure two things well, measure those and hold the others at conservative defaults.
Is high DPO good or bad?
Financially good while suppliers stay willing; operationally bad if late fees, lost early-pay discounts, or supply priority quietly offset the float.
How does DPO interact with the cash cycle?
It subtracts directly: one more day of DPO is one day less of self-funded inventory and receivables.
Can this tool see the numbers I type?
It cannot. There is no submission step: the calculation happens in your browser and the result disappears when you close the page. Treat the fields above as a scratchpad rather than a form.
Key terms on this page
- Average daily purchases
- $7,259 for the Days Payable Outstanding worked case; it sits next to the main result because it carries context the headline leaves out.
- Supplier float held
- $239,926 in the default Days Payable Outstanding calculation — one of the secondary figures an experienced reader checks before trusting the primary number.
- Value of float at 8% short-term rate
- $19,194 for the Days Payable Outstanding worked case; it sits next to the main result because it carries context the headline leaves out.
- Days payable outstanding
- The primary output of this tool: 33.1 days for the default inputs, computed exactly from DPO = payables ÷ purchases × days.
- Worked example
- The calculation written out in full so that nothing on this page has to be taken on trust.
- Verdict band
- The interpretation attached to a result (“Paying fast: good terms secured, but the float is leaving early” on these inputs), which turns a bare number into a position on a scale.
- Sensitivity (±10 %)
- How far the Days Payable Outstanding moves when a single input is nudged ten percent either way; the ranked list on this page is computed live from this engine.
Where the Days Payable Outstanding model comes from
There is no black box on this page — the engine evaluates DPO = payables ÷ purchases × days. Source of record: Standard payables ratio; norms from supply-chain finance benchmarks. Specialist software layers extra coefficients on top of the same algebra; none are hidden here, and that transparency is what makes a disagreement traceable to a specific input instead of a black box.
Treat the output as a precise answer to the question you typed: exact arithmetic, transparent formula, published source, no hidden rounding. The sensitivity table above is part of that promise rather than a bonus: it lets you see how much of the result depends on how carefully you measured.
Turning this Days Payable Outstanding into a decision
Mark the computed date or span in your calendar with its assumptions attached; plans drift when the inputs do.
The audience here is people planning around a point or span in time. Everything you need to defend the result — formula, substitution, sensitivity, source — is printed above, so the only remaining variable is the honesty of your inputs.