Your ERP records every supplier invoice, every production order, every stock movement. But what happens when a tax authority requests a detailed fixed asset register during a compliance audit? In too many organisations, the answer is an ageing spreadsheet, maintained manually by a diligent but overstretched accountant — one whose figures have never been formally reconciled with the underlying accounting records.
The fixed assets module is often the forgotten corner of an ERP project. Priority goes to purchase-to-pay flows, stock management, and production: fixed assets come last, under-configured and sometimes hurriedly migrated from a legacy system. The consequences surface at month-end close, during tax audits, or when the transition to IFRS standards arrives.
This guide covers the complete fixed asset lifecycle in an ERP — from acquisition to disposal, including physical inventory and IFRS 16 compliance.
Why the Fixed Assets Module Is Often the Forgotten Corner of ERP Projects
An Under-Configured Module That Breeds Compliance Errors
In mid-market ERP projects, the fixed assets scope is frequently addressed in the final weeks of the implementation, with fewer resources and less testing than general ledger or procurement modules. The result: asset categories are too broad, balance sheet accounts are poorly mapped, and depreciation rules are copied from the legacy system without checking whether they comply with current tax legislation.
ERP implementation specialists regularly report that anomalies uncovered during post-go-live audits are concentrated in fixed assets: incorrect useful lives, wrong tax categories, or absent component accounting for complex assets.
The Real Stakes: Tax Audits, Month-End Close, IFRS
Three factors make a properly configured fixed assets module non-negotiable:
- Tax authority audits: During a corporate tax review, inspectors routinely cross-reference the fixed asset register against the general ledger. Any discrepancy between accumulated depreciation in the trial balance and the asset register total risks triggering adjustments and penalties.
- Month-end close: Depreciation charges often represent a significant share of an industrial SME’s total costs. Automated, reliable calculation in the ERP eliminates manual re-entries at monthly or quarterly reporting dates.
- IFRS 16: Since 2019, companies reporting under IFRS must recognise lease assets as right-of-use assets on the balance sheet. This complex treatment requires either a dedicated module or specific ERP configuration.
The Fixed Asset Lifecycle in an ERP
Acquisition and Commissioning
Creating an asset record in the ERP is the starting point for all subsequent tracking. A standard asset card includes:
- Identification: unique asset number, description, location, responsible person
- Accounting category: determines the balance sheet account (property, plant and equipment vs. intangible assets), the default useful life, and the depreciation method
- Carrying value: acquisition cost excluding VAT, or cost of production, plus directly attributable costs (freight, installation, commissioning tests)
- Service date: the start date for depreciation
The integration with the procurement module is critical here. A well-configured ERP automatically creates the asset record from the purchase order receipt whenever the item code is flagged as “capitalisable.” This flow prevents duplicate data entry and ensures consistency between the supplier invoice and the balance sheet value.
Depreciation Methods: Straight-Line, Declining Balance, Units of Production
An ERP must manage two simultaneous depreciation plans for eligible assets:
The accounting plan (typically straight-line) reflects the actual economic decline in value of the asset. It is required for published financial statements under both IFRS and most local GAAP.
The tax plan (declining balance / accelerated depreciation) applies multiplier coefficients that vary by useful life: 1.25× for 3–4 years, 1.75× for 5–6 years, 2.25× beyond 6 years in many jurisdictions. It enables accelerated tax deductions in earlier years.
The deferred tax difference between the accounting and tax plans must be tracked and reversed as the tax plan eventually falls below the accounting plan. A properly configured ERP generates these entries automatically and reverses them at the right time.
Some industrial assets whose wear depends on volume of use lend themselves to units-of-production depreciation: cost per machine hour or per unit produced. The ERP then pulls the usage counter from the production or CMMS module to calculate the period charge.
Useful Life Revision
A change in the remaining useful life of an asset — following a renovation, change of use, or accounting review — must be treated prospectively under IFRS and most local standards: the net book value at the revision date is depreciated over the new remaining life. The ERP must allow this revision without altering the historical depreciation schedule, with a full audit trail of the change (date, user, justification).
Component Accounting
For complex assets, accounting standards (IFRS and most local GAAP) require decomposing the asset into components with distinct useful lives. Example for an industrial building:
| Component | Depreciation Period |
|---|---|
| Structure / shell | 40 years |
| Facades and waterproofing | 20 years |
| Technical installations | 10 years |
| Interior fit-out | 7 years |
Each component becomes a separate asset record in the ERP with its own depreciation plan. When a component is replaced (roof renovation, electrical systems renewal), the net book value of the retired component is written off and the replacement component is capitalised at its replacement cost.
This treatment, overlooked in many SMEs, can have a material impact on annual depreciation charges and taxable profit.
Physical Inventory of Fixed Assets: From Manual Reconciliation to Automation
Technologies: RFID, QR Code, Mobile Scanning
Modern ERPs include mobile applications for physical asset inventory. The standard process:
- The ERP generates an asset list to be counted, by site or zone
- An operative scans the RFID tag or QR code on the asset using a tablet or smartphone
- The app records GPS location, observed condition, and a photo if required
- Data flows back in real time to the fixed assets module
RFID technology enables rapid inventories in dense environments (warehouses, IT equipment rooms) without requiring direct line-of-sight to each asset. For organisations that prefer not to invest in RFID infrastructure, printed QR codes offer a cost-effective alternative: negligible marginal cost, compatible with any smartphone, no specialist hardware required.
Accounting vs. Physical Reconciliation
The physical inventory must be reconciled against the accounting fixed asset register. Common discrepancy types:
- Asset physically present, absent from the register: asset purchased without creating a record, or transferred from another site without updating the register
- Asset in the register, not found physically: asset scrapped without an accounting entry (the most frequent case and the most problematic from a tax standpoint)
- Asset recorded at wrong location: inter-site transfer not logged in the ERP
The ERP produces a discrepancy report at the end of the inventory cycle, forming the basis for accounting adjustments: write-offs for missing assets, capitalisation of unrecorded assets, and location updates.
Recommended Frequency
Most accounting standards require a physical inventory at least annually. In practice, a rolling inventory strategy is more effective: 20% of the asset base counted each month gives a complete cycle in five months. This approach spreads the workload and surfaces anomalies during the year rather than at year-end.
Disposal, Write-Off and Inter-Entity Transfers
Disposal: Automated Journal Entries
Disposing of a fixed asset triggers several simultaneous journal entries that the ERP should automate:
- Removal of the gross asset from the balance sheet: debit accumulated depreciation, debit or credit the gain/loss account, credit the asset account
- Recording the sale proceeds: debit the buyer’s receivable or cash account, credit the proceeds account
- VAT regularisation calculation: disposing of an asset on which input VAT was originally recovered may require a partial VAT clawback if the asset is sold within the applicable adjustment period (5 years for moveable assets, 10–20 years for real property depending on jurisdiction)
A poorly configured ERP forces the accountant to calculate and post these entries manually — a source of errors, lost time, and the risk of mismatches between the general ledger and the asset register.
Write-Off
Write-off differs from disposal: the asset is removed from the register without any sale proceeds. Accounting-wise, the net book value at write-off becomes a non-recurring expense. Tax-wise, this charge is deductible if the write-off is justified: a destruction certificate, a decommissioning record, or a dated and signed certificate of unusability.
Inter-Entity Transfers
In a group with multiple legal entities, transferring a fixed asset from one subsidiary to another requires a disposal in the first entity and an acquisition in the second, with intercompany flow management. These transfers — carried out at market value or net book value depending on group policy — must be eliminated in consolidated accounts. Enterprise ERPs (SAP, Oracle) handle these mechanisms natively; for mid-market ERPs, this treatment often requires specific configuration or manual elimination entries.
IFRS 16 and Right-of-Use Assets: The ERP as Compliance Guarantor
Since 2019, IFRS 16 requires companies applying IFRS to recognise virtually all lease contracts on the balance sheet. The asset is recorded as a “right-of-use” (ROU) asset and the counterpart as a “lease liability.”
The impact on the fixed assets module is direct:
- Each lease contract must be entered with its characteristics: term, lease payments, renewal options, discount rate
- The ERP calculates the initial liability (present value of future payments) and the corresponding asset
- Each period, it generates the ROU asset depreciation entries and the unwinding of the lease discount
Exemptions remain: leases of 12 months or less and low-value assets (threshold generally indicated at USD 5,000 by the IASB) may continue to be expensed as incurred.
For mid-market ERPs, two approaches coexist:
- Native IFRS 16 module: built directly into the fixed assets module (SAP S/4HANA, Oracle Fusion, Microsoft Dynamics 365 Finance, Sage X3 with add-on)
- Dedicated add-on: specialist solutions connected to the ERP via API, for organisations with a complex lease portfolio or an ERP without a native IFRS 16 module
Fixed Assets Module Comparison: Leading ERP Platforms
SAP Asset Accounting (FI-AA): The Benchmark for Large Groups
SAP S/4HANA’s FI-AA module is widely recognised as the functional benchmark: multi-entity, multi-currency, simultaneous multiple accounting standards (local GAAP and IFRS in parallel), full automation of timing differences, and native integration with general ledger (FI-GL), procurement (MM), and maintenance (PM). Its configuration complexity matches its capabilities: a standalone FI-AA implementation in a mid-size group typically takes several months of consulting work.
Oracle Fixed Assets: Project Accounting Integration
Oracle Cloud ERP (Fusion) includes a Fixed Assets module tightly coupled with Project Accounting. This integration is particularly well suited to organisations whose assets originate from construction or development projects: real estate developers, engineering firms, extractive industries. Assets under construction are tracked as CWIP (Construction Work in Progress) and automatically transferred to fixed assets on project completion.
Sage Fixed Assets: Suited to Mid-Market Companies
Sage offers fixed asset management across its Sage Intacct, Sage X3, and Sage 200 product lines. The module covers straight-line and declining-balance depreciation, timing differences, and physical inventory via mobile app. Its ease of use makes it more accessible than SAP for SME finance teams, and its configuration aligns with common mid-market accounting practices.
Microsoft Dynamics 365 Finance: Configurability and Limitations
The Fixed Assets module in Dynamics 365 Finance handles the main depreciation methods and provides a physical inventory function through the Dynamics 365 Asset Management mobile app. Its main limitation for some jurisdictions: tax-specific requirements (accelerated depreciation elections, specific timing adjustments) may require precise configuration or complementary development, as the module is designed for generic international use.
5 Common Mistakes to Avoid
| Mistake | Tax/Accounting Risk | Correction |
|---|---|---|
| Categories too broad (single “equipment” category) | Incorrect useful lives, wrong balance sheet account assignment | Create 8–15 categories aligned with the chart of accounts: IT equipment, vehicles, industrial tooling, furniture, technical installations… |
| Not tracking timing differences between accounting and tax depreciation | Errors in the tax return, potential adjustments | Configure dual depreciation plans and automatic timing difference entries from go-live |
| Ignoring component accounting | Understated depreciation on complex assets, non-compliance with IFRS | Identify multi-component assets during migration and decompose them |
| Physical inventory not reconciled with the ERP | Ghost assets on the balance sheet, unrecorded assets, missed VAT regularisation | Plan a monthly rolling inventory with mandatory ERP reconciliation |
| Disposals without VAT regularisation configuration | VAT due not declared on asset sales within the statutory adjustment period | Configure automatic VAT regularisation calculation in the disposal module |
Going Further
Fixed assets management fits within a broader financial chain: capital expenditure planning to integrate investments into the financial plan, cost accounting to allocate depreciation charges by cost centre, and treasury management to forecast the cash impact of acquisitions and disposals.
To deepen your approach:
- Our guide ERP and Management Accounting: Cost Centres and Budget Control details how to allocate depreciation charges by cost centre in a live ERP environment.
- Our article ERP Business Case for the Board: ROI, TCO and Presentation will help you quantify the impact of migrating to a compliant fixed assets module.
- Our guide ERP and Treasury Management covers how to integrate capital expenditure flows into the cash flow statement.
Download our ERP evaluation scorecard (30 criteria, 100 points) to compare fixed assets modules from several vendors side by side, including criteria specific to tax compliance and IFRS 16 readiness.
