Capitalise or Expense: Making the Same Call Every Time

Here is the uncomfortable version of the argument, up front. A company that capitalises a category of spend consistently and is later told it should have expensed it has a policy problem, and a policy problem is corrected in one conversation and one entry. A company that treated eleven similar purchases one way and nine the other way has a hundred small problems scattered through a year of transactions, and correcting those means finding them first.

So consistency is the operating requirement, and it is a higher priority in day to day work than being right on any individual item. That sounds wrong and it is not. Being right on individual items is a framework question with an owner, and the owner is the accountant who reports on your statements. Being consistent is an operations question, it has no owner in most companies at this size, and it is the one this matrix is for.

The second uncomfortable thing follows from the first. In nearly every company this size, the person deciding whether a purchase is capital or expense is the person coding the invoice, who is usually the most junior person in the chain and is being handed the hardest judgement in it, with no information beyond the invoice itself. That is not their failure. It is a design failure, and the matrix below exists to take the decision away from them for almost everything, so that the small remainder can go to somebody who can actually answer it.

What this matrix is not

It is not an interpretation of any reporting framework, and it does not tell you where the line sits. That determination is made once, by the company with its accountant, and it is recorded in a policy. Everything in the matrix references that policy rather than restating it, which is deliberate: a matrix that carries its own copy of the threshold is a matrix that goes stale silently the first time the policy changes.

Your policy document is short and holds these fields. The values are yours, and the second column names who has to agree each one.

Field in the policy	Who sets it
The capitalisation threshold, as a value	The company, on the accountant’s advice
The level the threshold is applied at: the invoice line, the item, the decision, or the project	The company, on the accountant’s advice. This one matters more than the threshold and gets less attention.
The asset classes the company uses, and what belongs in each	The company, aligned to how the statements are presented
The depreciation basis for each class	The accountant
Which categories are always expensed regardless of amount	The company, on the accountant’s advice
The approver required above the threshold	The owner
The date the policy was agreed, and with whom	Whoever holds the file
The date it is next reviewed	The finance lead

No amount appears anywhere in this article, on purpose. A number written into a published matrix would be read as a recommendation by somebody who never had the conversation with their accountant, and the whole value of the threshold is that it was set for a particular business by somebody who knows its statements.

The four questions, asked in this order

The order is the useful part. Most people ask the amount question first, which is why bundled and project spend gets miscoded so consistently: by the time you are looking at the number you have already decided what the thing is, and you have usually decided wrongly.

Order	Question	Why it comes here
1	Are we buying a thing, or paying for a period of service?	A support contract, a subscription and a maintenance plan are periods of time. This question removes a large share of invoices from the matrix entirely before anyone thinks about amounts.
2	Does this restore something to the condition it was already in, or does it change what the thing can do or how long it will do it for?	This is the repair question, and it is answered by the work description, not the invoice total. A large repair is still a repair.
3	Is this a standalone purchase, or one component of something bigger that is being bought in pieces?	Asked before the amount, because the amount is meaningless until you know what unit it belongs to. Skipping this question is how a project arrives as fourteen invoices, none of which looks like anything.
4	Applied at the level the policy names, does this clear the threshold?	Last, and now it is arithmetic instead of judgement.

Question three is the one that catches people, and it is worth stating what it costs when it is missed. A piece of equipment arrives on one invoice, its freight on a second, the electrician who wired it in on a third, the platform it sits on as a materials purchase, and the commissioning visit two months later as a service call. Each of those was coded by somebody looking at one document. Nobody in that chain was wrong on the information in front of them and the result is still wrong.

The fix is upstream of the ledger: the purchase order, the project code, or a job number that all five invoices carry. If your system supports one, use it. If it does not, the approval step below is where the connection gets made instead.

The matrix

Read the second column first. It is the fact that settles the row, and if that fact is not on the invoice then the row cannot be coded by whoever opens the post.

Spend category	The fact that decides it	Where that fact comes from	Who answers when it is not on the invoice
Computer hardware, single item	Whether it clears the threshold at the level the policy names	The invoice	Nobody. This is the routine case and it is why the policy exists.
Computer hardware, a batch bought for a rollout	Whether the policy applies the threshold per device or per decision	The policy, not the invoice	Finance lead, once, then the answer is written into the policy and never asked again
Software licence, a term of use	The licence period, and whether it is a right to use for a period or a perpetual purchase	The licence agreement, which is rarely attached to the invoice	Whoever signed it
Software implementation and configuration, external	Which portion of the work is building something and which is training, project management or data cleanup	The supplier’s statement of work, and a request for the invoice to be split at source	The project owner, before the first invoice, not after the fourth
Internal staff time on the same implementation	Whether the company has a policy on internal labour at all, and whether hours are recorded against the project	Timesheets that must exist before the work starts, or the question is unanswerable	Accountant, on the policy. Finance lead, on the hours.
Website work	Whether it is building a capability or publishing content into an existing one	The scope of the engagement	Marketing, in one sentence, per engagement
Leasehold improvements	What was done, and to whose property, and what the lease says happens to it at the end	The contractor’s scope and the lease	Finance lead, with the lease in hand
Repairs	Whether the work returns the asset to its previous condition	The work description on the invoice, which frequently has to be asked for	The person who authorised the work
Work that changes capacity, extends life, or changes what an asset is used for	Same as above, and the difference is a sentence of description	The work description	The person who authorised the work
Spare parts held for a specific machine	Whether they are held for use or held for sale, and whether they will be consumed within a period	Operations, not finance	Operations lead
Tools and small equipment	Whether the policy treats them by item or by purchase, and whether they are consumable	The policy	Finance lead, once
Vehicles, and the fit-out installed on them	Whether the fit-out was part of the acquisition or added later	The invoices, read together	Finance lead
Freight, duty, delivery and installation	Which asset they belong to	The purchase order or job number. Without one, the connection is made by memory.	The person who ordered the asset
Commissioning, calibration and the trial run	Whether the asset was in service before or after the work	Operations, and the in-service date is a real date somebody knows	Operations lead
Extended warranty or multi-year support bought with an asset	Whether it was priced separately	The invoice, if it is itemised. Ask the supplier to itemise.	Purchasing
Training on a new asset or system	Nothing. This is a category the policy should name explicitly so it is never asked again.	The policy	Accountant, once, when the policy is written
Site preparation, and removing what was there before	Whether it relates to the new asset or to the property	The contractor’s scope	Finance lead
Deposits on equipment not yet delivered	Whether the asset has been received, which is not the same as whether it has been paid for	The delivery record	Operations lead
Costs of financing an asset while it is being built	Whether the company has a policy on this at all	The policy	Accountant. Do not improvise this one.
Assets acquired under a lease or financing agreement	The classification of the agreement	The agreement, found through a proper lease search	Accountant, always
Demonstration equipment the company later buys	What the earlier payments were for, and whether any of them apply against the purchase	The supplier’s account history	Purchasing

Look at the fourth column. Most rows say either “nobody” or “once”, and that is the design goal: a matrix that keeps sending questions to a person every month has not removed the judgement call, it has just documented where it happens.

Routing, which is the half people forget

Knowing the deciding fact does not tell you who codes it. Three routes, and everything falls into one of them.

Route	When	What has to happen
Coded on the spot	The policy answers the row without interpretation	Nothing. Code it and move on. Most invoices are here and should be.
Held for the finance lead	The deciding fact is missing, or the purchase is part of something bigger	It waits in a queue with a note saying what is missing and who was asked. It does not get coded to a best guess and revisited later, because it never gets revisited.
To the accountant, before the period closes	A new category, a new kind of agreement, anything touching internal labour or financing costs, or anything material enough that being wrong would matter to how the statements read	The question goes in writing with the documents attached and a proposed answer. The proposal makes it a five minute reply instead of a meeting.

The middle route is the one that needs protecting. A held item is uncomfortable because it sits in a queue and the queue is visible. A guessed item is comfortable because it disappears. Every company drifts toward the comfortable option unless somebody counts the queue.

The approval step

Above the threshold, capitalisation stops being a coding decision and becomes an authorisation. Somebody with a name approves it, before the commitment, and the approval says which project it belongs to.

That approval does two jobs at once. It applies the authority grid you already have to a category of spend that frequently escapes it, because capital purchases often arrive as a quotation rather than as a purchase order. And it creates the project code that solves question three above, which no amount of careful coding downstream can solve on its own.

The rule that survives at every size: the person who approves a capital purchase is not the person who codes it. If those two are the same person, the policy is being applied by the only person with a reason to prefer one answer, and there is nobody to notice.

How to tell your matrix is failing

Three measures, all of which you can count without building anything.

The escalation count. How many invoices went to the accountant this quarter because nobody knew. A handful in the first quarter after the policy is written is expected. The same number four quarters later means the answers are not being written back into the policy.

The reclassification count. How many entries your accountant moved between capital and expense at the last year end, and in which direction. This is the honest score and it is sitting in their adjusting entries, where nobody in the company usually looks.

The consistency test. Pick one category and pull every transaction in it for the year, across all accounts. If the same kind of purchase appears in two places, the matrix is not being used, whatever anybody says about it.

There is a fourth thing worth watching that is not a measure of the matrix but of something else. If the proportion of spend being capitalised moves noticeably in a year when a covenant is tight or a sale is being contemplated, somebody outside the company will notice, and the conversation that follows is not about accounting. Capitalisation decisions change reported results and they change them in a direction that is always convenient. A policy fixed in advance, applied consistently, and reviewed on a schedule rather than on a need is the only defence that works, and it only works if it was in place first.

Reviewing the policy, once a year

Once, on a fixed date, ideally alongside the year end planning conversation described in the ninety days before year end.

Four inputs go into the review: the escalation log for the year, your accountant’s reclassifications, any new category of spend the business started buying, and the register itself, which after a rebuild tells you whether the classes still describe what the company actually owns.

Two outputs come out: an updated policy with a date on it, and a note of what changed. Off-cycle changes are allowed for exactly one reason, which is that the business started doing something genuinely new, and they carry the same requirement as the annual review: the accountant is asked before the change, not after the first year of transactions has been coded under it.

Do not change the threshold because a particular purchase is awkward. That is the change that guarantees the following year’s transactions cannot be compared with this year’s, and awkward purchases have a route already; it is the escalation route above.

What we do not do

We do not set the capitalisation threshold, the asset classes or the depreciation basis. Those are determinations for the accountant who reports on the statements, and the matrix is built to reference them rather than to substitute for them.

We do not interpret the reporting framework, and we do not treat a rule of thumb that circulates among bookkeepers as if it were one.

We do not let an invoice sit coded to a best guess with an intention to revisit it. It goes into the held queue with a note, or it goes to the accountant with a question.

And we do not build a matrix that has to be consulted every month. If the monthly close still contains a capital versus expense argument a year after the policy was written, the policy is the thing that needs work, not the people applying it.