Should this expense be classified as CapEx or OpEx?

Should this expense be classified as CapEx or OpEx?

Decision tree financeaccountingcapexopexfinancial reporting

Determine whether a cost should be capitalised as a fixed or intangible asset or expensed immediately under IFRS and US GAAP standards. Use this tree at the point of purchase order or invoice review to ensure correct treatment before posting to the general ledger. When in doubt, always confirm final treatment with your management accountant or external auditor.

Overview

Type
Decision tree
Tags
finance, accounting, capex, opex, financial reporting
Entry
Q1
Questions
5
Outcomes
4
Author
Andrew
Last updated
2026-05-12

Decision Tree

Start: Does the asset have a useful economic life greater than one year?

yes

  • Continues to question: Is this cost related to internally developed software or a digital intangible asset?

no

  • Outcome: Expense Immediately

Machine-Readable JSON (Canonical Model)

View JSON
{
  "_meta": {
    "schema": "https://www.drawdecisiontree.com/decision-dag.schema.json",
    "source": "https://www.drawdecisiontree.com",
    "description": "DrawDecisionTree.com is a free tool for building, sharing, and embedding interactive decision trees. This file is the machine-readable export of a published decision tree. The `dsl` field contains the original source in the Decision DAG DSL; the `dag` schema is documented at the URL in `schema` above.",
    "links": {
      "interactive": "https://www.drawdecisiontree.com/t/drawdecisiontree/finance-capex-vs-opex.html",
      "embed": "https://www.drawdecisiontree.com/embed/path/drawdecisiontree/finance-capex-vs-opex",
      "dsl_reference": "https://www.drawdecisiontree.com/decision-tree-dsl-reference.html",
      "guides": "https://www.drawdecisiontree.com/guides",
      "schema_docs": "https://www.drawdecisiontree.com/decision-dag.schema.json",
      "author_trees": "https://www.drawdecisiontree.com/trees/drawdecisiontree"
    },
    "generated_at": "2026-05-29T12:05:39.288Z"
  },
  "author": {
    "handle": "drawdecisiontree",
    "first_name": "Andrew",
    "last_name": null,
    "avatar_url": "1d32d828-b6ca-40ec-bdd7-771fe7b9c36a/avatar-1778531481027.svg",
    "display_name": "Andrew"
  },
  "file": {
    "id": "89c5a55c-20b8-487a-a98b-02a1f53de5e3",
    "name": "Should this expense be classified as CapEx or OpEx?",
    "public_slug": "finance-capex-vs-opex",
    "updated_at": "2026-05-12T16:53:43.587978+00:00",
    "url": "https://www.drawdecisiontree.com/t/drawdecisiontree/finance-capex-vs-opex.html",
    "json_url": "https://www.drawdecisiontree.com/t/drawdecisiontree/finance-capex-vs-opex/tree.json",
    "dsl_url": "https://www.drawdecisiontree.com/t/drawdecisiontree/finance-capex-vs-opex/tree.dag"
  },
  "meta": {
    "description": "Determine whether a cost should be capitalised as a fixed or intangible asset or expensed immediately under IFRS and US GAAP standards. Use this tree at the point of purchase order or invoice review to ensure correct treatment before posting to the general ledger. When in doubt, always confirm final treatment with your management accountant or external auditor.",
    "mode": "decision",
    "entry": "Q1",
    "tags": [
      "finance",
      "accounting",
      "capex",
      "opex",
      "financial reporting"
    ],
    "image": "https://images.unsplash.com/photo-1554224155-6726b3ff858f?w=1200&q=80"
  },
  "questions": [
    {
      "id": "Q1",
      "text": "Does the asset have a useful economic life greater than one year?"
    },
    {
      "id": "Q2",
      "text": "Is this cost related to internally developed software or a digital intangible asset?"
    },
    {
      "id": "Q3",
      "text": "Are the costs being incurred in the development phase rather than the research or preliminary phase?"
    },
    {
      "id": "Q4",
      "text": "Does the total cost meet your organisation's capitalisation materiality threshold?"
    },
    {
      "id": "Q5",
      "text": "Is there genuine uncertainty about the correct accounting treatment for this item?"
    }
  ],
  "outcomes": [
    {
      "id": "CAP_FIXED",
      "label": "Capitalise as Fixed Asset"
    },
    {
      "id": "CAP_INTANG",
      "label": "Capitalise as Intangible Asset"
    },
    {
      "id": "OPEX_IMM",
      "label": "Expense Immediately"
    },
    {
      "id": "SEEK_ADVICE",
      "label": "Seek Accountant Guidance"
    }
  ],
  "dsl": "dag: Should this expense be classified as CapEx or OpEx?\nversion: 1.0.0\nimage: https://images.unsplash.com/photo-1554224155-6726b3ff858f?w=1200&q=80\ndescription: Determine whether a cost should be capitalised as a fixed or intangible asset or expensed immediately under IFRS and US GAAP standards. Use this tree at the point of purchase order or invoice review to ensure correct treatment before posting to the general ledger. When in doubt, always confirm final treatment with your management accountant or external auditor.\ntags: finance, accounting, capex, opex, financial reporting\nentry: Q1\n\nQ1: Does the asset have a useful economic life greater than one year?\n  hint: Under both IFRS (IAS 16) and US GAAP (ASC 360), an item must provide economic benefits beyond the current reporting period to qualify for capitalisation. A laptop lasting three years qualifies; printer paper or a one-off workshop fee does not. If the item will be fully consumed, returned, or become obsolete within 12 months of acquisition, it must be expensed immediately regardless of cost. When the useful life is genuinely uncertain, consider the manufacturer's stated lifespan or comparable assets already on the Fixed Asset Register.\n  yes -> Q2\n  no  -> [OPEX_IMM]\n\nQ2: Is this cost related to internally developed software or a digital intangible asset?\n  hint: Software built in-house, purchased licences with an indefinite useful life, patents, trademarks, and similar non-physical assets follow a different capitalisation path than tangible property, plant, and equipment. Cloud SaaS subscriptions are generally treated as an operating expense rather than an intangible asset under both IFRS 15 and ASC 350-40, because the organisation does not control the underlying asset. Answer yes if the primary nature of the expenditure is software development, bespoke system build, or acquisition of an identifiable intangible right. If the cost is a mix of hardware and embedded software, assess the dominant component.\n  yes -> Q3\n  no  -> Q4\n\nQ3: Are the costs being incurred in the development phase rather than the research or preliminary phase?\n  hint: Under IAS 38 and ASC 350-40, only costs incurred once technical and commercial feasibility has been established may be capitalised. Research-phase costs, feasibility studies, vendor selection activities, and early planning must always be expensed. Development-phase costs — detailed design, coding, integration testing, and direct labour once feasibility is confirmed — are eligible for capitalisation. Maintain a phase log with dated milestones so that you can demonstrate to auditors exactly when the capitalisation start date was reached.\n  yes -> [CAP_INTANG]\n  no  -> [OPEX_IMM]\n\nQ4: Does the total cost meet your organisation's capitalisation materiality threshold?\n  hint: Most organisations set a minimum threshold — commonly between £1,000 and £5,000 — below which items are expensed for practical reasons even if they technically qualify as capital assets. Check your Finance Policy or Fixed Asset Register policy document for the exact threshold applicable to your entity and asset class. Aggregating multiple low-value identical assets purchased in the same period (component accounting) may still require capitalisation under IAS 16 if the combined value exceeds the threshold. Do not split a single purchase across multiple invoices or cost centres solely to fall below the threshold, as this constitutes a policy breach.\n  yes -> [CAP_FIXED]\n  no  -> Q5\n\nQ5: Is there genuine uncertainty about the correct accounting treatment for this item?\n  hint: Complex arrangements such as lease modifications under IFRS 16, cloud infrastructure contracts, mixed hardware-software bundles, or assets constructed internally over multiple periods may require professional judgement beyond this decision tree. If any earlier question produced a borderline answer, or if the amount is individually material to the financial statements (typically >0.5% of gross assets), it is prudent to involve your accountant before the period closes. Use this question as a final quality check before defaulting to an expense treatment. Documenting the rationale for your conclusion will protect you in any subsequent audit review.\n  yes -> [SEEK_ADVICE]\n  no  -> [OPEX_IMM]\n\n[CAP_FIXED]: Capitalise as Fixed Asset\n  color: #2E7D32\n  description: Record the cost in the Fixed Asset Register as a tangible asset under Property, Plant and Equipment (IAS 16 / ASC 360). Assign the appropriate asset category, useful life, and depreciation method (straight-line or reducing balance) in line with your Fixed Asset policy, and ensure the Purchase Order is coded to the correct capital nominal code. The asset must be tagged with a unique asset number and recorded in the physical asset inventory within 30 days of delivery. Schedule the depreciation start date from the point the asset is available for use, not from the date of payment. Arrange an insurance valuation if the replacement cost exceeds your policy's automatic reinstatement limit.\n  code: FIN_CAP_FIXED\n\n[CAP_INTANG]: Capitalise as Intangible Asset\n  color: #1565C0\n  description: Record the expenditure as an Intangible Asset under IAS 38 / ASC 350 using the appropriate nominal code in your chart of accounts, referencing the project or system name for traceability. Document the feasibility assessment and the evidence of the development phase start date, as auditors will specifically request this at year-end. Apply an amortisation method and useful life that reflects the pattern of expected economic benefits — typically straight-line over three to five years for bespoke software. Review the asset annually for impairment indicators (e.g. project cancellation, technology obsolescence) and disclose the asset class and amortisation policy in the notes to the financial statements.\n  code: FIN_CAP_INTANG\n\n[OPEX_IMM]: Expense Immediately\n  color: #F57C00\n  description: Post the full cost to the Profit and Loss account in the period it is incurred using the relevant expense nominal code (e.g. IT costs, maintenance, repairs, or professional fees). Ensure the invoice is approved under the standard accounts payable workflow and that input VAT is reclaimed where applicable. No Fixed Asset Register entry is required; however, retain the invoice and all supporting documentation for the standard retention period (seven years in most jurisdictions). If the expensed amount is unusually large compared to historical run rates for this nominal code, add a brief narrative in the period-end commentary to pre-empt management or auditor queries.\n  code: FIN_OPEX\n\n[SEEK_ADVICE]: Seek Accountant Guidance\n  color: #6A1B9A\n  description: The accounting treatment is not straightforward and must be reviewed by your management accountant or external auditor before any ledger entries are made. Prepare a concise briefing note covering the nature of the cost, the contract or invoice details, the total amount, and the specific questions that gave rise to uncertainty. Submit this to the Finance team via your standard technical query process and request a written response with the recommended treatment and the accounting standard reference. Do not post to either a capital or revenue nominal code until written guidance has been received and approved by the Finance Controller. Retain the guidance on the transaction file for a minimum of seven years.\n  code: FIN_SEEK_ADVICE\n"
}

DSL Representation

dag: Should this expense be classified as CapEx or OpEx?
version: 1.0.0
image: https://images.unsplash.com/photo-1554224155-6726b3ff858f?w=1200&q=80
description: Determine whether a cost should be capitalised as a fixed or intangible asset or expensed immediately under IFRS and US GAAP standards. Use this tree at the point of purchase order or invoice review to ensure correct treatment before posting to the general ledger. When in doubt, always confirm final treatment with your management accountant or external auditor.
tags: finance, accounting, capex, opex, financial reporting
entry: Q1

Q1: Does the asset have a useful economic life greater than one year?
  hint: Under both IFRS (IAS 16) and US GAAP (ASC 360), an item must provide economic benefits beyond the current reporting period to qualify for capitalisation. A laptop lasting three years qualifies; printer paper or a one-off workshop fee does not. If the item will be fully consumed, returned, or become obsolete within 12 months of acquisition, it must be expensed immediately regardless of cost. When the useful life is genuinely uncertain, consider the manufacturer's stated lifespan or comparable assets already on the Fixed Asset Register.
  yes -> Q2
  no  -> [OPEX_IMM]

Q2: Is this cost related to internally developed software or a digital intangible asset?
  hint: Software built in-house, purchased licences with an indefinite useful life, patents, trademarks, and similar non-physical assets follow a different capitalisation path than tangible property, plant, and equipment. Cloud SaaS subscriptions are generally treated as an operating expense rather than an intangible asset under both IFRS 15 and ASC 350-40, because the organisation does not control the underlying asset. Answer yes if the primary nature of the expenditure is software development, bespoke system build, or acquisition of an identifiable intangible right. If the cost is a mix of hardware and embedded software, assess the dominant component.
  yes -> Q3
  no  -> Q4

Q3: Are the costs being incurred in the development phase rather than the research or preliminary phase?
  hint: Under IAS 38 and ASC 350-40, only costs incurred once technical and commercial feasibility has been established may be capitalised. Research-phase costs, feasibility studies, vendor selection activities, and early planning must always be expensed. Development-phase costs — detailed design, coding, integration testing, and direct labour once feasibility is confirmed — are eligible for capitalisation. Maintain a phase log with dated milestones so that you can demonstrate to auditors exactly when the capitalisation start date was reached.
  yes -> [CAP_INTANG]
  no  -> [OPEX_IMM]

Q4: Does the total cost meet your organisation's capitalisation materiality threshold?
  hint: Most organisations set a minimum threshold — commonly between £1,000 and £5,000 — below which items are expensed for practical reasons even if they technically qualify as capital assets. Check your Finance Policy or Fixed Asset Register policy document for the exact threshold applicable to your entity and asset class. Aggregating multiple low-value identical assets purchased in the same period (component accounting) may still require capitalisation under IAS 16 if the combined value exceeds the threshold. Do not split a single purchase across multiple invoices or cost centres solely to fall below the threshold, as this constitutes a policy breach.
  yes -> [CAP_FIXED]
  no  -> Q5

Q5: Is there genuine uncertainty about the correct accounting treatment for this item?
  hint: Complex arrangements such as lease modifications under IFRS 16, cloud infrastructure contracts, mixed hardware-software bundles, or assets constructed internally over multiple periods may require professional judgement beyond this decision tree. If any earlier question produced a borderline answer, or if the amount is individually material to the financial statements (typically >0.5% of gross assets), it is prudent to involve your accountant before the period closes. Use this question as a final quality check before defaulting to an expense treatment. Documenting the rationale for your conclusion will protect you in any subsequent audit review.
  yes -> [SEEK_ADVICE]
  no  -> [OPEX_IMM]

[CAP_FIXED]: Capitalise as Fixed Asset
  color: #2E7D32
  description: Record the cost in the Fixed Asset Register as a tangible asset under Property, Plant and Equipment (IAS 16 / ASC 360). Assign the appropriate asset category, useful life, and depreciation method (straight-line or reducing balance) in line with your Fixed Asset policy, and ensure the Purchase Order is coded to the correct capital nominal code. The asset must be tagged with a unique asset number and recorded in the physical asset inventory within 30 days of delivery. Schedule the depreciation start date from the point the asset is available for use, not from the date of payment. Arrange an insurance valuation if the replacement cost exceeds your policy's automatic reinstatement limit.
  code: FIN_CAP_FIXED

[CAP_INTANG]: Capitalise as Intangible Asset
  color: #1565C0
  description: Record the expenditure as an Intangible Asset under IAS 38 / ASC 350 using the appropriate nominal code in your chart of accounts, referencing the project or system name for traceability. Document the feasibility assessment and the evidence of the development phase start date, as auditors will specifically request this at year-end. Apply an amortisation method and useful life that reflects the pattern of expected economic benefits — typically straight-line over three to five years for bespoke software. Review the asset annually for impairment indicators (e.g. project cancellation, technology obsolescence) and disclose the asset class and amortisation policy in the notes to the financial statements.
  code: FIN_CAP_INTANG

[OPEX_IMM]: Expense Immediately
  color: #F57C00
  description: Post the full cost to the Profit and Loss account in the period it is incurred using the relevant expense nominal code (e.g. IT costs, maintenance, repairs, or professional fees). Ensure the invoice is approved under the standard accounts payable workflow and that input VAT is reclaimed where applicable. No Fixed Asset Register entry is required; however, retain the invoice and all supporting documentation for the standard retention period (seven years in most jurisdictions). If the expensed amount is unusually large compared to historical run rates for this nominal code, add a brief narrative in the period-end commentary to pre-empt management or auditor queries.
  code: FIN_OPEX

[SEEK_ADVICE]: Seek Accountant Guidance
  color: #6A1B9A
  description: The accounting treatment is not straightforward and must be reviewed by your management accountant or external auditor before any ledger entries are made. Prepare a concise briefing note covering the nature of the cost, the contract or invoice details, the total amount, and the specific questions that gave rise to uncertainty. Submit this to the Finance team via your standard technical query process and request a written response with the recommended treatment and the accounting standard reference. Do not post to either a capital or revenue nominal code until written guidance has been received and approved by the Finance Controller. Retain the guidance on the transaction file for a minimum of seven years.
  code: FIN_SEEK_ADVICE

Machine Access

Questions in this decision tree

Possible outcomes

How to use this decision tree

Click "Open interactive version" to step through the questions. Your answers narrow the tree until a recommended outcome is reached. You can also embed this tree on your own site.

More decision trees by Andrew

Which API design pattern is right for my project?
Which API design pattern is right for my project?
Determine the right API design style for your integration scenario.
Authentication Method Selection
Authentication Method Selection
Authentication is a security-critical, high-friction decision to reverse — migrating users from one auth method to another requires coordinated password resets or credential migration campaigns. This tree eliminates methods that don't match your user type, enterprise requirements, and security posture, giving you a clear shortlist before you write a line of code.
Caching Strategy Selection
Caching Strategy Selection
Premature or misapplied caching adds complexity — stale data bugs, invalidation logic, and distributed consistency problems — without solving the actual bottleneck. This tree routes you to the caching pattern that matches your data access profile, so you apply the right tool to the right problem rather than defaulting to Redis for everything.
CI/CD Pipeline Tool Selection
CI/CD Pipeline Tool Selection
Choosing a CI/CD platform is a long-term infrastructure commitment — pipelines accumulate config, custom scripts, and team muscle memory that make switching painful. This tree eliminates tools that don't fit your source control host, infrastructure model, or team scale, leaving only the options genuinely viable for your situation.
Which cloud provider should I use — AWS, Azure, or Google Cloud?
Which cloud provider should I use — AWS, Azure, or Google Cloud?
Answer a few questions to identify the most suitable cloud platform for your workload.
Container Orchestration Platform Selection
Container Orchestration Platform Selection
Container orchestration is foundational infrastructure — the platform you choose shapes how you deploy, scale, network, and operate every service you run. This tree eliminates options that don't match your operational maturity, cloud provider commitment, and workload complexity, so you land on the platform that fits your team today without over-engineering for a scale you haven't reached.