CapEx vs OpEx: How to Code an Invoice Correctly

Capital expenditure buys something that will produce value for years, so its cost is spread over those years. Operating expenditure pays for something consumed now, so its cost hits this period's profit and loss. That is the whole distinction in one sentence, and it is still the coding decision accounts payable gets wrong most often.

The stakes are not academic. Code a capital item as an operating expense and you understate profit this year and overstate it later. Code an operating cost as capital and you have inflated earnings and put an asset on the balance sheet that does not exist. Auditors look for both. So does the IRS.

CapEx vs OpEx: the difference

Notice the row about cash. This is the thing people find counterintuitive: capitalizing a purchase does not change the cash you paid or when you paid it. It only changes how the accounting recognizes the cost. The money is gone either way. That is why cash flow statements pull CapEx out separately, under investing activities, rather than leaving it in operating.

How do you know if an expense is CapEx or OpEx?

Work through four questions in order. Most invoices are settled by the first two.

1. Will it provide benefit beyond one year? If the useful life is a year or less, it is OpEx. Done.
2. Is it above your capitalization threshold? Every business sets a dollar floor below which it expenses everything, regardless of useful life. Nobody depreciates a $40 stapler over five years. More on the threshold below.
3. Does it acquire, improve, or extend the life of an asset, or just keep it running? This is the repair-versus-improvement line, and it is where the real arguments happen. Fixing a broken part is a repair (OpEx). Replacing an entire roof, upgrading a machine so it produces more, or adapting a building to a new use is an improvement (CapEx).
4. Is the cost necessary to get the asset ready for use? If you capitalize the asset, you also capitalize freight, installation, testing, and sales tax. They ride along on the asset's cost, they do not get expensed separately.

The capitalization threshold and the IRS de minimis safe harbor

Your capitalization policy sets the dollar amount below which purchases are expensed even if they last for years. The IRS de minimis safe harbor election lets most businesses expense items up to $2,500 per invoice or per item (as substantiated on the invoice), rising to $5,000 for taxpayers with an applicable financial statement, which generally means an audited financial statement.

Two practical points AP teams miss. First, the threshold is applied per item or per invoice line, not per invoice total. An invoice for ten laptops at $1,400 each is ten items under the threshold, not one $14,000 capital purchase. Second, the safe harbor requires you to have a written capitalization policy in place at the start of the tax year and to actually follow it. A policy you wrote in December to justify how you coded things in March does not help you.

Whatever your threshold is, write it down and apply it consistently. An auditor is far more interested in whether you followed a defensible policy than in whether the policy uses $2,500 or $5,000.

Is software CapEx or OpEx?

This is now the question that comes up most, because the answer flipped over the last decade.

• SaaS subscriptions are OpEx. You are buying a service, not an asset. Your monthly or annual fee for cloud accounting, a CRM, or AP automation is an operating expense, full stop. This is the main reason the software line moved from CapEx to OpEx across most businesses: you no longer buy the software, you rent it.
• Perpetual licenses you own are CapEx, amortized over their useful life.
• Internally developed software is split. Costs in the preliminary planning stage are expensed. Costs in the application development stage (coding, configuring, testing) are capitalized. Post-implementation training and maintenance are expensed again. Getting this right means your engineers' time has to be tracked against those stages, which is a bigger operational lift than the accounting.
• Implementation costs for a SaaS arrangement can often be capitalized as a prepaid asset and amortized across the contract term, even though the subscription itself is OpEx. This trips up nearly everyone.

Repairs vs improvements, the line that causes arguments

The IRS approach asks whether the work results in a betterment, a restoration, or an adaptation of the asset. If yes, it is capitalized. If it just keeps the thing in its ordinary working condition, it is a repair.

The honest summary: if the invoice restores the asset to what it always was, expense it. If it makes the asset better, bigger, longer-lived, or different, capitalize it.

Why AP gets this wrong, and what actually fixes it

The coding decision lands on whoever enters the invoice, and that person usually has the least context about what was bought and why. They see a vendor name, a total, and a line description like "site works, phase 2." Nothing on that document says whether it extended the life of an asset.

Three failure patterns show up again and again:

• Splitting a capital project across invoices. A $60,000 machine installation arrives as eight invoices from three vendors over four months. Each one, seen alone, looks like a routine expense. Coded individually, the asset never appears on the balance sheet.
• Coding by vendor habit. A vendor who normally sends maintenance invoices sends one for a major upgrade. It gets coded to the account that vendor's invoices always go to. This is the single most common cause, and it is a direct consequence of coding from memory.
• Freight and installation expensed separately. The asset gets capitalized, and then the $3,000 shipping invoice from a different vendor gets dropped into freight expense, understating the asset.

The fix is structural, not a matter of trying harder. Capital purchases should be identifiable before the invoice arrives, through a purchase order tagged to a capital project, so AP is not being asked to make a judgment it lacks the information to make. Where invoices are coded from the document alone, consistency comes from rules and vendor history rather than recall, which is what invoice coding software is for, and it is worth reading alongside our guide to GL coding in accounts payable for the mechanics.

One more control worth having: any invoice over your capitalization threshold should route to someone who knows what was purchased, not just to whoever owns the budget line. That single approval rule catches most miscoded capital spend before it reaches the ledger, and it is straightforward to enforce with invoice approval software that routes on amount and GL code.

Does CapEx or OpEx look better?

Neither, and be suspicious of anyone with a confident answer. Capitalizing improves this year's reported profit and EBITDA, because only the depreciation hits the P&L. That is why aggressive capitalization is a classic earnings-management red flag and why analysts watch the ratio of CapEx to depreciation.

Expensing reduces reported profit now and reduces current-year taxable income, which is real cash saved today. Many owner-managed businesses genuinely prefer that, which is exactly why the de minimis safe harbor exists.

Cash flow does not care either way. The money left when you paid the invoice. The choice is not a lever to pull for the result you want, it is a question with a correct answer determined by what you bought. Code it accurately, apply your policy consistently, and let the numbers say what they say. When an invoice genuinely sits on the line, ask your accountant before it hits the ledger, not after the auditor finds it. And if the item was received before the invoice showed up, make sure it is accrued in the meantime, which is where goods received not invoiced comes in.