Cloud spend belongs in the P&L as operating expense for the consumption you use, but the full picture is more nuanced: prepaid commitments are recognised over their term, capitalised software labour can sit on the balance sheet first, and the part of cloud cost that directly serves customers belongs in cost of revenue rather than general overhead. Getting it right means classifying each component correctly, splitting the customer serving portion into cost of goods sold so gross margin is honest, and reporting cloud as a unit economic the board can track. Done well, cloud stops being the line that surprises finance every quarter and becomes one that forecasts cleanly.
This is where FinOps meets the controller. The mechanics below are what separate a defensible cloud line from a number nobody can explain.
Where does cloud spend sit in the P&L?
The bulk of cloud spend is consumption based and recognised as operating expense in the period you use it, the same month the provider invoices it. The complication is the parts that behave differently. A prepaid commitment, such as an all upfront Savings Plan, an Azure Reservation paid in advance, or an OCI Universal Credits drawdown, is a prepayment recognised as the capacity is consumed across the term, not expensed in full on purchase. Internal engineering labour that builds qualifying capitalised software may be capitalised and amortised under the relevant standard, which moves part of a migration or platform build off the immediate P&L. Treating all of this as one undifferentiated monthly expense is the most common reason cloud forecasts miss.
How should commitments and prepayments be handled?
Commitments are both a discount mechanism and an accounting event. A prepaid commitment is carried as a prepayment on the balance sheet and drawn down into expense as you consume the capacity, which smooths the P&L impact even though cash left early. The risk that finance must track is the obligation side. An Azure MACC carries a shortfall clause, so unspent commitment is still owed; an AWS Enterprise Discount Program and Oracle Universal Credits carry the same use it or lose it structure. That unspent obligation is a real liability for forecasting and disclosure even when no invoice has arrived. The buyer side discipline is to forecast drawdown against the commitment monthly so an emerging shortfall is visible quarters ahead, not discovered at true up.
Why split cloud into cost of revenue?
Cloud spend that directly serves paying customers, the production infrastructure behind your product, is a cost of revenue and belongs in cost of goods sold. Cloud spend that supports the business broadly, such as internal tooling, data warehousing for analytics, and development environments, is closer to operating overhead. Splitting the two is what makes gross margin honest. If all cloud cost sits in overhead, gross margin looks inflated and the board cannot see the true unit economics of the product. For a software business, the cloud cost of goods sold is often the single largest input to gross margin, so misplacing it distorts the most watched number in the company.
A scaling fintech reported all cloud spend as overhead, showing a flattering gross margin while the board questioned why net margins kept slipping. Reclassifying production infrastructure into cost of revenue revealed cloud cost of goods sold was eroding gross margin as usage outpaced revenue. The same exercise exposed prepaid commitments expensed incorrectly and untracked drawdown against an enterprise agreement. Correcting the classification and then optimising the underlying spend through rightsizing and disciplined commitment coverage left the estate materially lighter and the margin story credible. Figures are verified against billing data and anonymised.
What cloud metrics belong in the board pack?
An absolute cloud number tells the board almost nothing on its own, because spend rising with a growing business can be perfectly healthy. Report cloud as a unit economic instead. Cloud cost as a percentage of revenue shows whether spend scales with the business. Cloud cost of goods sold as a share of gross margin shows the product efficiency trend. Cost per customer, per active user, or per transaction shows whether each incremental unit of business is getting cheaper to serve. When these unit metrics improve while the absolute number grows, the board sees efficiency; when the absolute number grows and the unit metrics flatten, that is the signal to act. The FinOps Foundation FOCUS specification, by standardising billing data across providers, makes building these metrics consistent across AWS, Azure, GCP, and OCI far easier.
Frequently asked questions
Is cloud spend opex or capex?
How are cloud commitments treated in the accounts?
What cloud metric should a CFO report to the board?
Make the cloud line one your board can trust
We work with CFOs and FinOps leaders to classify cloud spend correctly across the P&L, track commitment obligations before they become true up surprises, and report the unit economics a board will act on, all as an independent advisory that takes zero provider commissions. Our guarantee: we reduce your cloud spend or we reimburse our service fee, on a Fixed Fee or no risk Gainshare basis. Read the wider FinOps operating model guide, see cloud spend KPIs for the CFO, and subscribe to The Cloud Spend Navigator.
Put a defensible number on your cloud spend.
No provider in the room, no published price list. Tell us your footprint and we will scope the savings against your billing data — we reduce your cloud spend or we reimburse our service fee.
The Cloud Spend Navigator: what changed in cloud pricing, commitments, and FinOps — no vendor spin.