Fixed Asset Accounting and Depreciation with ERP: Asset Register, Capitalization, and Disposal

Every growing business buys things that are used for years: vehicles, machines, computers, store equipment, office renovations, or custom-developed software. A purchase like this should not be expensed in full in the month of purchase, because its benefit is enjoyed over a long time. This is where fixed asset accounting comes in: recording the asset, spreading its cost as an expense over its useful life through depreciation, and recording what happens when the asset is sold or written off. In businesses that still use spreadsheets, the asset list often becomes a file nobody updates, so financial statements and tax are calculated from questionable data.

This article explains how an ERP system helps manage the fixed asset lifecycle from acquisition to disposal: the asset register, capitalization, depreciation methods, accounting versus tax differences, revaluation and impairment, and how to connect it to purchasing and period closing. The content is general; accounting standards and tax rules can change and differ by entity type, so always consult your accountant or tax advisor.

Summary

• Fixed assets are tangible items used over more than one period and valuable enough to capitalize under the company's policy
• A tidy asset register is the basis for depreciation, insurance, maintenance, and audits
• Depreciation spreads the asset's cost over its useful life; the chosen method must be consistent and documented
• Depreciation for financial statements and for tax often differs, so the system needs to support two books or adjustments
• Asset disposal (sale, write-off, loss) creates a gain or loss that must be recorded correctly
• An ERP enables automatic monthly depreciation journals and connects with purchasing and period closing

What counts as a fixed asset

A fixed asset is a tangible asset held for use in operations, for rental, or for administrative purposes, and expected to be used for more than one period. Examples include land, buildings, vehicles, production machines, office equipment, furniture, and computers. Some often-confusing points:

• **Consumables** such as stationery or small spare parts are usually expensed immediately rather than capitalized
• **Intangible assets** such as software, licenses, and trademarks are treated separately, although the amortization principle is similar
• **Leases** can have special accounting treatment; recognition of right-of-use assets follows the standards applicable to your entity
• **Inventory** is goods for sale, not a fixed asset, even if it looks physically similar

A company needs to set a **capitalization threshold**, the minimum value for a purchase to be recorded as an asset. For example, items below a certain value are expensed directly. The threshold must be written in the accounting policy and applied consistently.

The asset lifecycle inside the system

1. Acquisition

Assets can come from cash purchase, credit, self-construction, donation, or trade-in. The capitalized value is not only the purchase price but also the costs needed to make the asset ready for use: shipping, import duty, installation, testing, and related professional services. That is why it is important to link the asset to purchase documents and additional costs. This principle is in line with landed cost for imported goods.

In an ERP, the flow ideally goes like this: purchase orders and goods receipts are created as usual, and when an item is flagged as an asset, the system offers to create an asset card automatically when the supplier invoice is recorded. This prevents asset purchases from "getting lost" as ordinary expenses. A good purchase approval flow also helps, as discussed in purchase approval workflows.

2. Recording in the asset register

Each asset has a card containing:

• A unique code and number, plus a physical label or QR code if needed
• Name, category, and user location or department
• Acquisition date, acquisition cost, and supplier
• Useful life, residual value, and depreciation method
• Custodian, serial number, and warranty period
• Supporting documents such as invoices and certificates

Asset categories (for example vehicles, office equipment, machinery) provide default settings for useful life and method so new entries are quick and uniform.

3. Periodic depreciation

Each period, the system calculates the depreciation expense and creates the journal: depreciation expense on the debit side, accumulated depreciation on the credit side. Because it runs automatically, depreciation is not forgotten at closing. This supports faster monthly closing with ERP.

4. Changes during the asset's life

While in use, an asset may experience:

• **Transfers** between locations or departments, which affect expense allocation
• **Major improvements** that extend useful life or increase capacity, which are capitalized, as opposed to routine maintenance, which is expensed
• **Impairment** when the recoverable amount is lower than the carrying amount
• **Changes in estimates** of useful life or residual value, applied prospectively

The distinction between routine maintenance and capitalized improvement should be written in policy. Maintenance records themselves are covered in asset management and equipment maintenance with ERP.

5. Disposal

An asset can be sold, written off because it is damaged or lost, or handed over via trade-in. At that point the system stops depreciation, removes the asset together with its accumulated depreciation, and records the gain or loss on disposal, the difference between proceeds and book value. An unrecorded disposal is a classic problem: the asset is gone from the office but is still being depreciated in the books.

Depreciation methods

A few common methods:

• **Straight-line**: the same expense each period, calculated as (cost minus residual value) divided by useful life. The simplest and most widely used
• **Declining balance**: a larger expense early and smaller later, suited to assets that lose value quickly
• **Units of production**: expense follows usage, such as machine hours or kilometers, suited to machines with fluctuating use

The method is chosen based on the pattern of the asset's economic benefits. A straight-line example: a vehicle worth 240 million rupiah, residual value 40 million, useful life 8 years. The annual expense is (240 million minus 40 million) divided by 8, which is 25 million, or about 2.08 million per month. This example is only an illustration of the arithmetic.

A good system also handles practical cases: assets bought mid-month (full or proportional depreciation convention), assets sold mid-period, and assets that are fully depreciated but still in use.

Accounting versus tax

Depreciation for financial statements follows accounting standards and management estimates. Fiscal depreciation, used to calculate income tax, follows tax regulations, which among other things group assets by set useful lives and restrict permitted methods. As a result, the two figures often differ, and the difference becomes part of the fiscal reconciliation.

How an ERP helps:

• **Two asset books** or two depreciation profiles on one asset card, one commercial and one fiscal
• **Difference reports** per asset and per period to prepare the fiscal reconciliation
• **Fiscal asset groups** as an additional attribute on each asset

Detailed rules, including groups and rates, can change, so verify with a tax advisor. Another discussion of tax compliance in an ERP is in e-invoicing and tax compliance with ERP.

Internal controls for assets

Assets are a classic target for misuse. The system should help with:

• **Segregation of duties**: the person who requests a purchase, the one who approves, and the one who records the asset should preferably be different people
• **Approval** for disposal and write-off of assets
• **Periodic asset counts**: match the system list with physical condition, for example once a year, using labels and a scanning app. The approach resembles [stock counts without stopping operations](/blog/stock-opname-tanpa-menghentikan-operasional)
• **Audit trail**: who changed useful life or residual value, when, and why. See [audit trails and internal controls in ERP systems](/blog/jejak-audit-dan-pengendalian-internal-di-sistem-erp)
• **Access rights** that restrict changes to important asset data, as discussed in [designing user access rights](/blog/merancang-hak-akses-pengguna)

Relationship with other modules

• **Purchasing and accounts payable**: supplier invoices for assets flow into asset cards; three-way matching reduces errors, see [accounts payable automation and three-way matching in ERP](/blog/otomatisasi-utang-usaha-dan-pencocokan-tiga-arah-di-erp)
• **Production and product costing**: depreciation of production machines becomes part of product overhead, discussed in [COGS and product cost accounting in ERP](/blog/hpp-dan-akuntansi-biaya-produk-di-erp)
• **Maintenance**: repair history and service schedules link to the asset card
• **Budget**: capital expenditure plans and projected depreciation expense feed into [budget planning and forecasting with ERP data](/blog/perencanaan-anggaran-dan-peramalan-dengan-data-erp)
• **Multi-entity**: assets moved between subsidiaries need intercompany journals, see [multi-currency and multi-entity ERP](/blog/erp-multi-mata-uang-dan-multi-entitas-untuk-ekspansi-regional)

Assets under construction

Unfinished projects, such as building a warehouse or developing internal software, are recorded as assets under construction. Costs accumulate first without being depreciated. When the asset is ready for use, the balance is moved to the appropriate fixed asset category and depreciation begins. The system must support this stage because a common mistake is starting depreciation too early or too late.

Migrating from a spreadsheet to an ERP asset register

Step 1: physical and document inventory

Recount the assets that really exist, match them with the old list and purchase documents. Assets that are lost or broken are formally removed with approval.

Step 2: standardize categories and policy

Set categories, useful lives, residual values, the capitalization threshold, and methods. Document them so they stay consistent across periods.

Step 3: prepare opening balances

For each asset, prepare the acquisition cost, accumulated depreciation up to the migration date, and remaining useful life. Verify that the register total equals the general ledger balance before starting.

Step 4: run in parallel

For one or two periods, compare the system-generated depreciation journals with the old calculations. Differences must be explainable.

Step 5: labeling and routine counts

Attach labels or QR codes to physical assets, then schedule an annual count. Broader data preparation guidance is in preparing data migration for a new system.

Common mistakes

• Capitalizing small purchases so the register swells and becomes hard to manage
• Expensing major improvements directly so that period's profit is too low
• Forgetting to stop depreciation when an asset is sold
• Not keeping acquisition documents, making them hard to prove during an examination
• Changing useful lives without documentation and approval
• Not reconciling the asset register with the general ledger balance
• Using one method for all assets without considering usage patterns

Useful reports

• Asset list by category, location, and custodian
• Forward depreciation schedule and expense per period
• Asset roll-forward: opening balance, additions, disposals, depreciation, and closing balance
• Report of fully depreciated assets still in use
• Difference between commercial and fiscal depreciation
• Assets not yet counted or without a custodian

Frequently asked questions

What is the right capitalization threshold?

There is no single figure. Decide based on business size, materiality, and ease of management, then write it into policy and consult your accountant. Consistency is what matters.

Does custom-developed software count as an asset?

Under certain conditions, software development costs can be capitalized as an intangible asset, depending on the accounting standards applicable to your entity and the development phase. Discuss with your accountant.

What is the difference between depreciation and amortization?

Depreciation is used for tangible assets, amortization for intangible assets. The calculation mechanics are similar.

Can fully depreciated assets be removed from the register?

Not automatically. As long as the asset is still owned and in use, keep it in the register with its remaining book value (usually the residual value or zero). Remove it only when it is actually disposed of.

How often should asset counts be done?

At least once a year, and more often for high-value or easily moved assets such as laptops and vehicles.

Conclusion

Fixed asset accounting is more than a bookkeeping obligation; it gives an honest picture of business investment, keeps financial statements accurate, and reduces the risk of assets vanishing without a trace. With a register connected to purchasing, automatic depreciation, and clear controls, the finance team saves time at each closing and management gets trustworthy data for the next investment decision.

Agsora helps companies implement and integrate accounting and fixed asset modules in ERP systems, including migrating asset data from spreadsheets. Tell us the current state of your asset register and we will help plan the clean-up steps.