Answer
The solar cash conversion cycle equals inventory days plus receivable days minus payable days. Use reconciled financial records for that calculation and a separate project cash timeline for deposits, milestones and collections. The deciding factor is consistent scope: each component needs the same reporting period, documented definitions and an accountable owner.
Last updated: November 2026
A solar business can be profitable on a project report and short of cash on payroll day. Modules may be paid for before installation. Field labor may be incurred before a milestone invoice is accepted. A completed system may wait on documents, inspection, lender funding, retainage, or a disputed change order. Revenue, expense, invoice, and cash receipt can all occur on different dates.
The cash conversion cycle is useful because it compresses inventory, receivables, and payables timing into one measure. It is dangerous when the team treats that measure as the whole solar cash story. A company can improve the headline by changing a denominator, delaying supplier payment beyond agreed terms, shifting material into an untracked work-in-progress category, or excluding the very projects creating the cash gap.
The operating answer is a two-layer control. Finance releases the standard cash conversion cycle from reconciled records. Operations maintains a project cash timeline that explains when commitments, supplier payments, labor, milestones, invoices, customer or lender receipts, and exceptions occur. The two views should reconcile where their definitions overlap without pretending they are identical.
The broader solar installer cash-flow guide discusses forecasting, working capital, financing, and general cash controls. This checklist covers exact component definitions, project milestone evidence, reconciliations, owner handoffs, exceptions, and the release record a solar owner can use every period.
No universal CCC target appears here. Business model, contract terms, project duration, purchasing method, accounting policy, billing structure, customer type, financing, and reporting period all affect the result. A shorter cycle is not automatically healthy if it comes from unpaid suppliers, unsafe procurement, incomplete service, aggressive collections, or a classification change.
SurgePV publishes this post and sells solar design software.
Connect a solar estimate to its cash assumptions
Explore project financial modeling while keeping actual receipts and payment obligations in your accounting records.
Book a DemoChecking cost first? See the SurgePV pricing page.
What does the solar cash conversion cycle measure?
The standard cash conversion cycle measures days tied up in inventory and receivables, reduced by days financed through payables: CCC = DIO + DSO - DPO. For a solar operator, it is a finance-controlled period metric. Pair it with a project cash timeline to see deposits, procurement, work, milestones, retainage, and collection exceptions.
Keep the standard formula intact
OpenStax’s working-capital chapter describes the operating and cash cycles and the roles of inventory, accounts receivable, and accounts payable. The same OpenStax chapter illustrates inventory conversion, receivable collection and payable deferral periods, with the latter subtracted to obtain the cash cycle. These are general finance sources, not solar accounting policies.
Each term needs a released definition:
- Days inventory outstanding (DIO) estimates how long eligible inventory value remains before the chosen cost event.
- Days sales outstanding (DSO) estimates how long eligible receivables remain before collection.
- Days payable outstanding (DPO) estimates how long eligible supplier obligations remain before payment.
Finance must approve the balance, flow, averaging, denominator, day count, currency, entity, and period rules. Some formulas use cost of goods sold for inventory and payables; some payable calculations use purchases when reliable. Do not mix definitions across periods and call the movement operational improvement.
A common average-balance convention is DIO = average eligible inventory / period cost of sales × period days, DSO = average eligible receivables / period credit sales × period days, and DPO = average eligible trade payables / period cost of sales × period days. Document alternatives such as a purchase-based DPO denominator. Finance must confirm that balances and flows represent the same scope; zero or inapplicable denominators leave the measure undefined, not zero days. Cash-only sales and some service/project accounting structures need explicit applicability review.
The formula is not cash on hand, a thirteen-week forecast, project margin, backlog, liquidity ratio, or funding requirement. It is also not a promise that every project takes the reported number of days. The result averages different economic events across a chosen population.
Add a project cash timeline without renaming it CCC
A project timeline begins with the events that actually move or constrain cash. It may include a customer deposit, equipment commitment, supplier invoice, supplier payment, permit fee, payroll, subcontractor invoice, milestone acceptance, customer invoice, lender approval, cash receipt, retainage release, refund, credit, and corrective work.
That timeline can expose a cash gap that the company-wide CCC hides. It can also explain why CCC changed. If DSO rises, the project detail may show one disputed milestone, incomplete closeout package, lender condition, or concentrated commercial account. If DIO rises, the cause may be early buying, a schedule slip, cancellation, goods in transit, unmatched receipts, or material assigned to a project that cannot proceed.
Keep the layers named correctly:
| View | Unit | Primary question | Owner | Do not use it as |
|---|---|---|---|---|
| Released CCC | Entity or approved business segment for a period | How long is operating value tied up across inventory, receivables, and payables? | Finance | Project duration or cash forecast |
| Project cash timeline | Contract, project, phase, or funding package | When do expected and actual cash events occur? | Project finance and operations | Financial-statement balance |
| Short-term cash forecast | Bank account and time bucket | Can the company meet upcoming obligations under current assumptions? | Treasury or finance | Profit or CCC |
| Project contribution report | Project and approved cost boundary | What value remains after defined costs? | Finance and project owner | Cash receipt schedule |
The team should be able to move from the headline to the affected projects and back to the ledger. If it cannot, the metric is descriptive but not actionable.
Which records belong in the cash-cycle close?
Use finance-approved inventory, receivable, payable, revenue, cost, purchasing, invoice, and cash records, linked to operational project milestones where relevant. Preserve entity, period, currency, cut-off, ownership, status, and source. Deposits, work in progress, retainage, lender funding, disputed amounts, credits, and late costs need explicit treatment rather than silent inclusion or exclusion.
Build a source-and-owner map
The U.S. Small Business Administration says proper bookkeeping and accounting for revenue and expenses support business finance management. It distinguishes cash and accrual recording at a high level and points businesses to accounting help. That page does not select a method or cash-cycle policy for a solar company.
IRS Publication 583 lists monitoring progress, preparing financial statements and tax returns, and supporting reported items among recordkeeping purposes. It does not define CCC. The narrow lesson is to retain the transactions and supporting documents behind the calculation.
| Record | Required fields for the close | Responsible owner | Exception to route |
|---|---|---|---|
| Inventory or material ledger | Item, quantity, value, ownership, location, receipt, allocation, status, cut-off | Inventory control and finance | Goods in transit, return, damage, cancellation, duplicate receipt |
| Purchase order and supplier invoice | Supplier, project, commitment, invoice, receipt, approval, due date, payment, credit | Procurement and accounts payable | Price variance, unmatched receipt, disputed invoice, hold |
| Project milestone register | Contract, milestone definition, evidence, achieved date, approver, block | Project owner | Partial completion, failed inspection, missing document, change order |
| Customer invoice and receivable | Bill-to entity, project, amount, issue date, due date, status, dispute, collection | Billing and accounts receivable | Rejection, short pay, lender condition, retainage, wrong entity |
| Cash receipt | Payer, amount, date, bank reference, invoice application, restriction | Treasury or finance | Unapplied cash, refund exposure, split payment, chargeback |
| Labor and subcontractor record | Project, work date, approved cost, invoice or payroll state | Operations and finance | Late time, rework, disputed scope, unbilled subcontractor |
| Model release | Entity, period, formulas, source versions, reconciliation, reviewer | Finance model owner | Policy change, restatement, missing ledger, material override |
One system does not need to own every field. Every field needs one authoritative source and a correction path. A project manager may verify milestone evidence without editing the accounts receivable ledger. Accounts payable may correct a due date without changing the project schedule. Finance decides how those records enter the released calculation.
Define cut-off and state before calculating
A period close needs a precise cut-off. Record whether goods received after the cut-off, invoices entered late, receipts in transit, payroll accruals, customer credits, and supplier credits belong to the current period. Preserve preliminary and closed states. Do not overwrite a closed period merely to make the dashboard current.
Operational statuses need definitions too. “Installed,” “substantially complete,” “inspection passed,” “permission received,” “invoiceable,” “invoiced,” and “collected” are different events. A team that uses them interchangeably will move cash expectations earlier than the contract and evidence support.
Work in progress deserves an explicit bridge. Depending on accounting policy and reporting purpose, project costs may sit in inventory, WIP, expense, or another account. This guide does not decide the treatment. Finance should document which balance enters DIO, which project costs appear only on the timeline, and how totals reconcile.
How do you run the solar cash conversion cycle checklist?
Run an eight-step close: lock scope and definitions, reconcile inventory, reconcile payables, reconcile receivables, map project cash milestones, calculate DIO/DSO/DPO and CCC, investigate changes and exceptions, then approve the release. Keep preliminary values separate, record overrides, and assign corrective work to the source owner rather than editing the metric output.
Use this eight-step close sequence
-
Lock the reporting scope. Name legal entities, business segments, currency, period, day convention, averaging method, formulas, materiality rule, prior-period comparison, and decision use. Record prohibited uses and the finance owner who can change a definition.
-
Reconcile eligible inventory. Tie the inventory balance to its responsible ledger. Review physical or system quantities, ownership, location, goods in transit, project allocations, returns, damaged stock, canceled jobs, and aged material. List WIP and committed-but-not-owned material separately if they do not enter the balance.
-
Reconcile payables. Match purchase orders, receipts, invoices, credits, approvals, due dates, and payments. Identify unrecorded liabilities, duplicate invoices, disputed amounts, supplier holds, early-payment terms, and overdue balances. Never improve DPO by ignoring agreed payment obligations.
-
Reconcile receivables. Tie customer and lender invoices to the receivable ledger and cash applications. Review unbilled achieved milestones, rejected invoices, retainage, unapplied cash, short payments, credits, refunds, disputes, and concentrated balances. Confirm the actual payer and funding conditions.
-
Update project cash timelines. For material projects, compare expected and actual commitment, payment, labor, milestone, invoice, receipt, and retainage dates. Record the owner, reason, next evidence, expected resolution, and cash exposure for each variance.
-
Calculate the components and CCC. Use the released balance and flow definitions. Retain calculation code or formulas, source versions, rounding, and zero-denominator handling. Show DIO, DSO, and DPO separately before the net result.
-
Explain the movement. Bridge prior period to current period by volume, mix, cut-off, denominator, classification, project delay, purchasing, billing, collection, payment timing, and correction. Separate operating change from policy or data change.
-
Approve and assign actions. Finance signs the formal release. Operations owns milestone evidence and schedule corrections; procurement owns material and supplier exceptions; billing and collections own invoice and receipt actions. Set a due date, escalation, expected cash effect, and confirmation evidence.
A close that ends with “CCC worsened” is incomplete. The useful output names the record and handoff preventing conversion. A cash action should not be a vague instruction to collect faster or hold inventory less.
Illustrative calculation: a period result, not a target
Illustrative example, not a customer case, company result, forecast, benchmark, accounting policy, or recommendation: Finance has released DIO of 48 days, DSO of 35 days, and DPO of 30 days for one defined reporting scope.
| Component | Illustrative days | Evidence state |
|---|---|---|
| DIO | 48 | Released from the approved inventory balance and denominator |
| DSO | 35 | Released from the approved receivable balance and denominator |
| DPO | 30 | Released from the approved payable balance and denominator |
| CCC = 48 + 35 - 30 | 53 days | Arithmetic result, not a target |
- DIO48
- DSO35
- DPO, subtracted30
- Net CCC53
Source: Illustrative example, not market data; arithmetic from the table above, checked November 2026.
Key Takeaway
The example nets to 53 days, but it does not predict any individual project cash gap. Review the underlying components and dated receipts before changing procurement or collections.
The result means the defined components net to 53 days under that release. It does not mean each project consumes cash for 53 days. If one commercial receivable is concentrated or stocked modules are reserved for a delayed project, the project timeline and distribution may carry more decision value than the average.
The model should also show prior-period definitions. If last period used purchases for DPO and this period uses cost of goods sold without a documented restatement, the two results are not directly comparable.
Review the project behind a delayed receipt
Bring a project with changed equipment or proposal assumptions to see how its modeled inputs can support a clearer handoff.
Book a DemoChecking cost first? See the SurgePV pricing page.
Copy-ready solar cash conversion cycle close record
Use this record each period. It is an operating control, not accounting, tax, legal, financing, investment, contract, or treasury advice. Empty fields remain unresolved.
| Close field | Team entry |
|---|---|
| Entity, segment, period, currency, and day convention | |
| Decision use and prohibited uses | |
| DIO formula, balance, flow denominator, averaging, source, and owner | |
| DSO formula, balance, flow denominator, averaging, source, and owner | |
| DPO formula, balance, flow denominator, averaging, source, and owner | |
| Inventory and WIP treatment | |
| Deposits, deferred items, retainage, lender funding, credits, and refunds | |
| Cut-off policy and late-entry treatment | |
| Ledger reconciliation status and unresolved difference | |
| DIO, DSO, DPO, CCC, and rounding | |
| Prior-period restatement or comparability limitation | |
| Largest period movements and supporting projects | |
| Project cash-timeline exceptions, amount, owner, and next evidence | |
| Supplier-term and customer-term exceptions | |
| Concentration, liquidity, and forecast escalation | |
| Scenario or sensitivity cases and switching assumption | |
| Corrective actions, due dates, expected cash effect, and proof | |
| Finance approver, scoped reviewers, release ID, and timestamp | |
| Next close, policy review, and retirement trigger |
Attach the formula specification and exception list. Preserve the closed version. A later correction should create a successor with the reason and impact, not erase the released record.
What should owners investigate when the cycle changes?
Investigate each component before reacting to the net CCC. Separate volume, mix, cut-off, denominator, policy, and data changes from true operating movement. Trace material changes to projects, invoices, inventory, suppliers, and receipts. Then test cash impact, contractual duties, customer consequences, and forecast sensitivity before changing purchasing, billing, collection, or payment practices.
Use a failure-mode bridge
| Observed change | Questions to test | Unsafe shortcut | Better response |
|---|---|---|---|
| DIO rises | Early buy, schedule slip, cancellation, transit, receiving error, obsolete stock, WIP policy? | Stop buying all material | Segment inventory, correct records, align releases with executable schedules |
| DSO rises | Invoice rejection, missing document, retainage, payer concentration, lender condition, dispute? | Pressure every customer equally | Fix milestone evidence and route the specific collection block |
| DPO falls | Earlier terms, lost credit, supplier pressure, invoice mix, denominator change? | Delay valid invoices unilaterally | Negotiate terms and preserve supplier obligations and continuity |
| DPO rises | Negotiated terms, overdue bills, approval delay, dispute, missing cash? | Celebrate the headline | Separate agreed financing from delinquency and supplier risk |
| CCC improves sharply | Real operations, deposit timing, classification, denominator, write-off, scope change? | Announce a productivity gain | Reconcile definitions and examine project-level cash and obligations |
| CCC is stable | Offsetting DIO, DSO, and DPO movements? | Assume no action is needed | Review all three components and concentration separately |
Do not optimize DPO in isolation. Supplier relationships, early-payment economics, continuity, contract terms, credit limits, and dispute resolution matter. Do not optimize DSO by billing before contractual evidence exists or by obscuring a legitimate customer dispute. Do not optimize DIO by creating jobsite shortages or shifting owned material outside the ledger.
Connect the close to a cash forecast
CCC explains a historical or period-based conversion pattern. The cash forecast asks whether dated receipts and payments leave enough liquidity. Link exceptions into the forecast with amount, earliest and latest date, confidence, dependency, and owner. A delayed large receipt can matter even when average DSO barely moves.
Stress the assumptions that can change the decision. The 2026 HM Treasury Green Book is UK public-sector appraisal guidance, not private solar treasury policy. Its use of sensitivity analysis and switching values offers a bounded process analogy: show which timing or amount assumption would create a funding problem instead of presenting one forecast as certain.
Examples of useful cases include a milestone slipping one billing cycle, a supplier deposit moving earlier, lender funding taking longer, a material return failing, or retainage moving beyond the forecast horizon. Use company records and qualified finance review. Do not import the Green Book’s public social discount rates or appraisal rules.
Pro Tip
Give each cash exception an amount, owner, next evidence and expected resolution date. Update the cash forecast when that date changes.
Review exceptions at the right cadence
Project teams may review material cash milestones weekly. Collections may review overdue and disputed items more frequently. Finance may release formal CCC monthly or quarterly after close. These cadences can coexist if preliminary values are labelled and the definitions remain controlled.
Escalation triggers should be organization-specific. Useful trigger types include a missed payroll or supplier liquidity threshold, a material reconciliation break, an overdue concentrated receivable, a supplier hold, an unbilled achieved milestone, a blocked lender package, a canceled job with committed material, or a forecast date crossing a credit limit. Qualified owners set the amounts and response.
The solar inventory management guide can support material controls, while the solar project intake process helps establish the identifiers and handoffs that later cash records depend on. Neither replaces finance’s close.
Where can SurgePV support the cash-cycle workflow?
SurgePV can support verified solar project functions including financial modeling, bills of materials, proposal generation, roof modeling, layout, shading, yield modeling, and electrical workflow support. It does not replace accounting, inventory ownership, supplier invoices, payroll, customer billing, bank receipts, lender decisions, contract milestones, tax treatment, treasury forecasts, or finance approval of CCC.
In a project-specific demonstration, inspect 3D roof modeling, solar array layout, shading analysis, energy-yield modeling, financial modeling, electrical workflow support, bill-of-materials output, and proposal generation. Results depend on source data, assumptions, equipment models, configuration, and responsible review.
A bill of materials can inform procurement planning, but it is not proof that equipment was ordered, owned, received, paid, returned, or assigned under the accounting policy. A financial model can show a project scenario, but it is not the bank ledger. A proposal can show customer terms, but the executed contract, milestone evidence, invoice, and cash application remain responsible records.
Use the financial modeling workflow to keep solar project assumptions visible and the solar proposal workflow to support customer-document generation. Then return actual cash events and accounting states to their authoritative systems. The cash-cycle close should link to project evidence without asking project software to certify finance records it does not own.
Request a guided project-model walkthrough with a representative design, bill of materials and proposal. Keep cash accounting and CCC approval with finance.
Frequently Asked Questions
What is the solar cash conversion cycle formula?
The cash conversion cycle is days inventory outstanding plus days sales outstanding minus days payable outstanding. Use consistent periods and definitions, then maintain a separate project timeline for deposits, milestones and receipts.
What counts as inventory for a solar cash conversion cycle?
Inventory follows the finance-approved accounting policy and reporting scope. Reconcile ownership, value, location and project allocation, and document the treatment of goods in transit and work in progress.
How do solar project deposits affect the cash cycle?
Deposits affect the project cash position according to their receipt timing, restrictions and accounting treatment. Record them on the cash timeline without forcing them into a CCC component where they do not belong.
How often should a solar company review its cash conversion cycle?
Review frequency should follow cash risk and the reliability of closed records. Teams can review operating exceptions weekly while finance releases formal period metrics after reconciliation.
Can solar design software calculate the full cash conversion cycle?
Design and proposal data alone cannot calculate a complete cash conversion cycle. Inventory, receivables, payables, cash applications and accounting definitions need authoritative financial records.
Sources
Primary research and reference material used for this desk-research article.
Where this fits
This article is part of SurgePV's Solar Business & Operations hub, which works through the topic from first principles to the decisions a project team actually has to make.
