Capital Expenditure (CapEx)

The engineering team submitted a $1.8M server purchase for approval. Finance asked whether it should be capitalized or expensed, and nobody had a clear answer. The decision affects this year's P&L, the balance sheet, and the depreciation schedule for the next five years, and it is being made under time pressure without a clear policy. Capital expenditure (capex) is money spent to acquire, upgrade, or maintain physical or intangible assets that provide economic benefit over more than one accounting period. Operating expenses are recorded on the income statement in the period they are incurred. Capex is recorded on the balance sheet as an asset and then expensed gradually through depreciation (for tangible assets like equipment and buildings) or amortization (for intangible assets like software and patents). That makes a capex decision a multi-year commitment as well as an accounting choice: it affects reported earnings, cash flow, balance sheet ratios such as debt-to-assets, and tax planning at the same time. A company that capitalizes a $5M infrastructure investment instead of expensing it reports higher profit this year and lower profit over the next five years. The cash outflow is the same; only the timing of the income statement impact changes. Finance teams that understand capex mechanics can structure investments deliberately and avoid surprises when auditors or board members look closely at the balance sheet.

How capex decisions flow through the financial statements

When a company makes a capital expenditure, the cash payment appears as an outflow in the investing section of the cash flow statement, not as an operating expense. The asset is recorded on the balance sheet at cost, and a portion of that cost is recognized as depreciation expense on the income statement each period over the asset's useful life. A $1.8M server with a five-year useful life generates $360K of annual depreciation expense, spread across five years instead of hitting the P&L in year one. This treatment has three effects. First, reported net income is higher in the year of purchase than it would be if the cost were expensed immediately. Second, the balance sheet carries the asset at its net book value (cost minus accumulated depreciation), which affects total assets and asset-based financial ratios. Third, the annual depreciation charge appears as an expense on the income statement for every year of the asset's life, long after the cash has left the business. This multi-year flow drives capital planning: the capex plan sets the depreciation schedule, which sets future opex, which affects future EBITDA and earnings. Finance teams that don't model the depreciation tail of their capital plans tend to underestimate future opex in multi-year forecasts.

Where it gets complicated

Not every capital purchase meets the threshold for capitalization. Companies set a materiality threshold, usually a dollar amount below which costs are expensed regardless of their multi-year benefit, so they don't have to track small items in a fixed asset register. A common threshold is $2,500 or $5,000, though this varies by company size. Items below the threshold are expensed; items above it are capitalized. The threshold is easy to apply to equipment and vehicles and harder to apply to internally developed software. Under ASC 350-40, certain costs incurred in the application development stage of internal-use software can be capitalized, but only during that stage, not during preliminary project assessment or post-implementation maintenance. That creates a classification problem: developer time spent building a feature has to be tracked and attributed to the right phase, which takes time-tracking systems and finance judgment that many companies don't have. The most common error is capitalizing preliminary planning costs that should be expensed, or failing to capitalize eligible development costs because the tracking system can't support the distinction. Both errors distort the income statement and create audit risk.

How platforms handle it

In a well-configured ERP, a capital expenditure follows a set workflow: a purchase requisition is created and tagged as a capital item, an approval route is triggered based on the dollar amount and asset category, the purchase is recorded against a capital project code, and once the asset is placed in service, a fixed asset record is created that drives the depreciation schedule automatically. In practice, many companies have the accounting system but not the workflow. Capex gets approved informally over email, the purchase is recorded to the balance sheet correctly, but the fixed asset record isn't created until quarter-end, when Finance notices the balance sheet has built up a large 'construction in progress' balance. When evaluating ERP or fixed asset systems, ask three questions. Does the system enforce the capital project approval workflow before the purchase is made, or only after? Does it calculate and post depreciation automatically from the asset record, or does Finance enter depreciation journal entries by hand? And can it handle partial disposals, when an asset is retired or sold before the end of its depreciation schedule, without a manual calculation?

Questions to ask when evaluating a capex process or system

• Is there a documented capex policy with a defined materiality threshold and useful life guidelines by asset category?
• Does the approval workflow enforce capex authorization before the purchase is committed, or only after the invoice arrives?
• Are software development costs tracked by project phase so that capitalizable costs can be distinguished from expensed costs?
• Does the fixed asset system calculate and post depreciation automatically, or does Finance enter it manually each period?
• Is there a regular fixed asset review to identify assets that are fully depreciated, retired, or no longer in service?
• When a large capex is planned, is the depreciation tail modeled into the multi-year financial forecast?

Common mistakes

The most common capex mistake is starting a significant capital project without a documented policy. Without one, each purchase decision is made ad hoc, and inconsistent capitalization across periods or departments makes the financial statements hard to audit and the trend analysis meaningless. A company that capitalizes certain IT infrastructure costs in year one and expenses similar costs in year two, with no documented reason for the difference, has a comparability problem in every multi-year analysis. The second mistake is capitalizing costs that should be expensed, particularly in software development, where preliminary planning and post-implementation maintenance costs should be expensed under GAAP. Capitalizing them inflates assets and understates current-period expenses. The reverse error, expensing costs that meet capitalization criteria, inflates current expenses and understates asset values. Both are audit findings. The third mistake is leaving the depreciation tail of a capital plan out of the financial forecast. A company that plans $10M of infrastructure capex over the next two years is also planning $1.5 to 2M of annual depreciation expense for the five years after that, and if that depreciation isn't in the model, future-period opex will be consistently understated.

CapEx against OpEx

The test is whether the spend buys something with a useful life beyond the current period. A server bought outright is capital expenditure: it is capitalised and depreciated. The same compute bought as a monthly cloud subscription is operating expenditure and hits the income statement as incurred. The accounting difference drives the planning difference, since capital requests usually run through a separate approval path and a separate budget.

Comparing planning platforms

Planning platforms separate on who can maintain the model after go-live, which is a staffing question as much as a software one. Once Capital Expenditure (CapEx) is settled as a requirement, read the Forecasting Software category guide for how the market splits, then weigh the Anaplan profile against the Pigment profile on that requirement rather than on the feature list. Our Anaplan pricing breakdown records what the vendor publishes and what is quote-based. The Anaplan against Pigment comparison sets two of them side by side on the same criteria. Before you book demos, put your own numbers through the forecasting ROI calculator so the business case is written down before a vendor writes it for you.

Capital Expenditure (CapEx) questions

Related terms

Budget vs Actual Variance, Cash Flow Forecasting, and Driver-Based Planning come up in the same workflow as Capital Expenditure (CapEx), and the rest of the planning platforms cluster is indexed in the finance operations glossary.