Cash conversion cycle: a component-level worked example

What does a cash conversion cycle calculation answer?

A cash conversion cycle calculation separates the time associated with holding inventory, collecting customer balances and paying trade suppliers. The result is expressed in days. After this exercise you can produce a component-level calculation, change one assumption and explain why the final number is not a dated cash forecast or a promise of liquidity.

Imagine an independent distributor reviewing its annual trading records. The useful first question is not whether its cycle meets a universal benchmark. It is whether the inventory, receivable and payable figures belong to the same reporting period and correspond to the right trading flows. Start by writing that data contract above the calculation, before entering any formula.

Use a weekly cash forecast when the decision concerns next Friday’s payment. Use this exercise when the decision concerns which working-capital component deserves investigation. A yearly ratio cannot identify the date a particular customer will pay. Keeping those outputs separate prevents a convincing-looking dashboard from answering the wrong question.

Build a three-row input contract

This independent English exercise uses a fictional 365-day reporting year. Average inventory at cost is 18,000 currency units and cost of sales is 109,500. Average trade receivables are 8,000 and credit sales are 146,000. Average trade payables are 9,000 and credit purchases are 109,500. None of these inputs is a customer record, market average or observed improvement.

For this teaching model, calculate each average balance from opening plus closing balance divided by two. That convention is part of the example, not a claim that two observations always capture seasonal trading. If monthly averages are available, document the method used and preserve it when comparing periods. Otherwise a change in averaging method can look like an operating improvement.

Check that receivables do not include unrelated loans and that payables do not include every liability on the balance sheet. Match currency, period and tax treatment between numerator and denominator. Credit sales are supplied explicitly here. Do not silently replace them with total revenue. If a justified approximation is unavoidable, name it and keep the calculation visibly provisional.

Calculate days before calculating the combined cycle

Inventory days, often called DIO, equal average inventory divided by cost of sales, multiplied by the period’s days: 18,000/109,500×365=60. Receivable days, DSO, equal 8,000/146,000×365=20. Payable days, DPO, equal 9,000/109,500×365=30. Write each numerator and denominator beside its result rather than publishing three unexplained numbers.

The combined cycle is DIO+DSO−DPO, giving 60+20−30=50 days. Supplier credit offsets part of the operating funding interval in this model. It does not remove the obligation to pay suppliers. Increasing the subtraction by ignoring agreed payment dates would be a different commercial action, not an arithmetic improvement to this exercise.

ABC inventory analysis ranks items by annual consumption value; it does not calculate these financing intervals. Likewise an economic order quantity calculation balances ordering and holding costs. Keep the saved CCC output labelled as days, not units to purchase, cash available or a purchasing instruction.

Compare one controlled scenario

Change only average inventory from 18,000 to 15,000 currency units. Keep annual cost of sales, credit sales, credit purchases and the other balances fixed. Inventory days become 15,000/109,500×365=50. The new cycle is 50+20−30=40 days. The difference is ten days in this explicitly fictional scenario, not an observed release of cash.

The distinction matters when presenting the result to a colleague. “With the stated balances and unchanged trading flows, the ratio falls by ten days” is reproducible. “This will put a particular amount into the bank next week” is unsupported. The latter needs transaction dates, collection evidence, planned purchases and a cash forecast rather than this annual component comparison.

Preserve the base case in one column and the scenario in another. Highlight the single changed input. If both inventory and annual cost of sales change, recalculate both and explain the new business assumption. Do not describe a multi-input scenario as proof that one operational action caused the entire difference. The model can compare assumptions; it cannot establish causation.

What should happen to missing or negative inputs?

A zero or missing denominator does not become a zero-day result. In this exercise it returns an unresolved component. If credit sales are unknown, DSO remains unknown and the combined CCC is not issued. Where all sales are genuinely cash sales and there is no related receivable balance, document a separate no-credit-sales case. Do not divide by zero and conceal the error.

Negative average balances need investigation before using this simple model. Advances, misclassifications or netting may be involved. Do not take the absolute value just to make the formula run. For ordinary applicable components the teaching calculation expects nonnegative average balances and positive matching flows. Record unavailable evidence beside the component instead of inventing a substitute.

A negative final cycle can be meaningful even when the inputs are valid. For example, inventory days of 15, receivable days of zero and payable days of 25 produce −10 days. Collections precede the supplier-payment interval in that model. Payroll, rent and other commitments still exist. A negative CCC is therefore not a guarantee against a cash shortfall.

Leave a reviewable fifteen-minute calculation card

On Windows, find Notepad in Start, open it and create a blank document. Copy the card below and title it “CCC V1 — fictional exercise”. Enter the 365-day basis, averaging convention and three balance/flow pairs with source labels. Open Calculator from Start and calculate 18000÷109500×365, 8000÷146000×365 and 9000÷109500×365 separately. Record 60, 20, 30 days, then 60+20−30=50. Notepad stores the inputs and calculation trail; it does not calculate them. Fifteen minutes is a planning target, not measured completion time. Stop with an incomplete card if suitable source evidence is missing.

Reporting period and days: [...]
Average-balance convention: [...]
Inventory / cost of sales: [...]
Receivables / credit sales: [...]
Payables / credit purchases: [...]
DIO, DSO, DPO, CCC: [...]
Unknown evidence or approximations: [...]
One changed assumption and revised result: [...]
Next document check and owner: [...]

Record the base 60/20/30/50 and all three input pairs. Choose File → Save As, select Documents and save ccc-card-V1.txt. If the name exists, choose another rather than overwrite it. Close Notepad and reopen that file from Documents in File Explorer; check period, units, inputs, component days and unresolved fields. Use File → Save As to create ccc-card-scenario.txt, change only average inventory to 15000 and record 50 DIO/40 CCC. Save and reopen that second file without changing V1. These are proposed reader actions, not an observed save test. Separate code execution does not verify your company file; preserve unknown evidence rather than forcing completion.

Check receivable records with invoice-level payment matching before relying on their totals. Review supplier terms separately from supplier total-cost comparisons. Those tasks establish different facts. End this card with one investigation, such as reconciling an inventory balance, not an unsupported instruction to borrow, delay payment or cut stock immediately.