Cash conversion cycle calculator: DSO, DIO and DPO in days and dollars

Three ratios and one subtraction. Days sales outstanding is receivables divided by credit sales, times days in the period: DSO = (AR / credit sales) x days. Days inventory outstanding is inventory divided by cost of goods sold, times days. Days payable outstanding is payables divided by cost of goods sold, times days. The cash conversion cycle is DSO plus DIO minus DPO. Every term comes off your own statements except the day count: 365 for a year, 91 or 92 for a quarter, 30 or 31 for a month.

Read the subtraction literally and the cycle stops being an abstraction. DSO is how long a sale sits as somebody else's promise. DIO is how long your money sits on a shelf. DPO is how long your suppliers finance you for free. The cycle is the days between paying for something and being paid for it, which is the number of days you have to fund yourself. It can be negative, and that means suppliers fund your working capital entirely.

Two denominators are where published numbers go wrong. The first is credit sales, not total revenue: a business taking half its money at the till has no receivable for that half, so total revenue underneath a receivables balance divides a partial numerator by a whole one and roughly halves the reported DSO. The second is cost of goods sold, not revenue, for both inventory and payables. Inventory is carried at cost, so measuring it against a revenue flow understates the days by your gross margin.

The Cash Conversion Cycle and DSO Calculator also returns a second DPO measured against purchases, because payables arise from what you bought rather than what you sold. Purchases equal cost of goods sold plus closing inventory minus opening inventory, $1,460,000 in the worked example, and DPO drops from 45.6 days to 45.0. The two diverge as fast as inventory moves, so a page reporting DIO honestly and DPO on cost of sales double counts an inventory build.

DSO, DIO, DPO and the cash conversion cycle are analyst ratios, not accounting measures. No US accounting standard defines any of them, which is why two competent people can compute different numbers from the same audited statements and both be right. The largest source of disagreement is which balance goes on top, and it is a real fork rather than a rounding preference.

Underneath it is a units mismatch: a balance sheet number is a stock measured at one instant, while sales and cost are flows across a whole period. Averaging the opening and closing balance at least approximates the window the flow covers, which is why analysts building a series average. The ending balance is a snapshot, so a large shipment on 31 December lands in the ratio at full weight. Its virtue is reproducibility from one statement, which is why lenders and screening tools use it.

The gap is not a rounding error and it has no fixed sign. Take the trade receivables and net sales the US Census Bureau publishes for all US manufacturing corporations and run both conventions quarter by quarter. In the fourth quarter of 2025 they agree to within a tenth of a day. In the first quarter of 2026 they are 1.61 days apart and the ending balance reads worse. On this page's defaults, a business whose balance sheet grew all year, the spread is 3.04 days.

The rule that follows is unglamorous and load bearing. Pick one convention, write down which one, and never compare a number computed one way against one computed the other. That includes your own DSO against a benchmark, a covenant, or last year: a series that quietly switched convention has an inflection nothing in the business caused. This calculator computes both and prints the spread, so the choice is visible instead of buried.

The simple DSO formula contains an assumption nobody states: that sales were roughly level across the period. It divides a receivables balance by an average daily sales rate, and an average only describes a flat line fairly. Give it a seasonal business, or one growing at forty percent, and it is not slightly wrong. It is wrong in a predictable direction.

When sales are falling into the period end, the balance was built by big months and the formula divides it by a small average, so DSO reads longer than it is. When sales are rising, the balance is mostly recent and the average is large, so DSO reads shorter. That second direction is the dangerous one: a growing business is told its collections are improving at precisely the moment its receivables are growing fastest, and receivables growth is the most common way a profitable company runs out of cash.

Countback DSO, sometimes called the exhaustion method, averages nothing. It walks backwards from the most recent month, retiring the balance against actual sales: whole months while the balance exceeds them, then a pro rata slice of the month where it runs out. On the months loaded into the Seasonal DSO tab, a $300,000 balance consumes the most recent month's $120,000 whole, 31 days, then 180,000 / 200,000 of the prior month, 27.9 of its 31 days. That is 58.9 days against the simple formula's 47.59, a gap of 11.31 days worth about $71,326.

Two failure modes are worth naming because neither throws an error. Month order is load bearing: entered oldest first, the method retires the balance against the wrong sales and returns a confident wrong number. And a balance that outruns every month supplied cannot be counted back, only extrapolated, which usually means long dated receivables a ratio was never going to explain. The Cash Conversion Cycle and DSO Calculator says so rather than printing the extrapolation as a measurement.

A card sale is not cash on the day it clears. It is a receivable from your processor until the payout lands, so your payout schedule sits inside DSO the way invoice terms do. Almost nothing written about the cash conversion cycle acknowledges this: the finance literature was written for businesses that invoice, and the payments literature is about fees. For a merchant taking most of its money by card, the processor is the largest customer on the receivables ledger and nobody has aged it.

The arithmetic is simple and the amounts are not. At steady state you always wait on one payout cycle of card revenue. Stripe publishes a US settlement timing of two business days; a merchant on a five day hold who moves to that is not saving a fee, they are handing back three days of card revenue, once and permanently. On $1,440,000 of annual card volume that is $11,835.62 of cash and $798.90 a year of interest at 6.75 percent.

A rolling reserve is the far bigger lever and is almost never modelled. A reserve of r percent released after h days holds r multiplied by h days of card revenue at steady state. Ten percent held for 180 days is eighteen days of card revenue in someone else's account, $71,013.70 on the same volume, six times what the faster payout was worth. A merchant negotiating high risk terms should spend their leverage on the reserve percentage and hold period before the rate.

The last piece is the channel mix. Sixty percent by card at five days and forty percent invoiced at 45 days blends to a DSO of 21.0 days, the floor your terms and processor imply, not a measurement. Where the balance sheet says more, the difference is collections performance: invoices past terms, disputes, work delivered but not billed. In the worked example that is 21.6 days and about $141,918, usually the cheapest part of the cycle to fix, needing no supplier concession and no capital.

The translation from days to dollars is where this page earns its place, and it has one trap. A day of DSO is worth a day of credit sales. A day of DIO or DPO is worth a day of cost of goods sold, which at any positive gross margin is smaller. Valuing all three at revenue overstates an inventory or payables improvement by exactly the gross margin, throws no error, and reads perfectly well. Here it would inflate a five day inventory saving from $19,726 to $32,877.

The financing cost is what makes days actionable. Working capital in the cycle is receivables plus inventory less payables, $330,000 in the worked example, and carrying it a year at the 6.75 percent bank prime loan rate posted in the Federal Reserve H.15 release of 4 September 2026 costs $22,275, or $61.03 a day. That is the price of a day of delay, and the number to set beside whatever the fix costs. If a lockbox or a faster processor costs less than the interest it saves, the case is closed.

For context rather than as a target: aggregate DSO for all US manufacturing corporations, computed from the Census Bureau Quarterly Financial Report for 2026 Quarter 1, sat between 45.5 and 48.6 days on ending balances across five quarters, and manufacturers with assets under $50 million came in at 44.0 days. The Atradius Payment Practices Barometer for the US in 2025 reports average terms of 45 days from invoicing, 43 percent of B2B invoice value overdue and 5 percent written off. Together those say a DSO near your stated terms is normal and one twenty days above them is a collections problem. Any tighter band is this page's reasoning, not a published standard.

Finally, the cases where the correct action is nothing. Stretching DPO is the only lever taking its money from someone else, and it is not free: pushing past terms costs supplier goodwill, priority during a shortage, and often an early payment discount worth more than the interest. Cutting DIO below what service levels need buys working capital with stockouts. And if your cycle already sits close to what your terms and settlement schedule imply, there is no gap left to close.