Fixed Assets - Disposals & Retirements is where ERP discipline either begins or breaks.
Asset Disposal - Full Retirement with Gain/Loss Calculation looks operational from far away. In a real finance team, it is a chain of assertions: the right actor started the work, the required records existed, the control policy was applied, the state change was preserved, and the outcome can be explained later without rebuilding the transaction from emails and spreadsheets.
The expected business outcome is specific: Full asset retirement posted in a single workflow with correct gain/loss; asset removed from depreciation schedule immediately; GL balances for asset cost and accumulated depreciation reduced correctly.
The control flow a finance team actually needs.
Step 1
Disposal Triggers Automatic Calculation...
Step 2
Gain/Loss GL Accounts Configurable Per...
Step 3
Proceeds Split By Payment Type Supported
Step 4
Prevents Disposal Of Assets With Open...
Step 5
Disposal Journal Is Reversible Only...
The ERP surface involved.
Module
Fixed Assets - Disposals & Retirements
Actors
Fixed Asset Accountant, Controller, ERP System
Tier
Tier 1
Finance area
Fixed Assets & Lease Management
Region lens
US and UK finance teams
Publication date
June 13, 2026
Disposal triggers automatic calculation and posting of depreciation through disposal date before retirement entries; gain/loss GL accounts configurable per asset category; proceeds split by payment type (cash, trade-in, installment) supported; system prevents disposal of assets with open CIP or pending transfers; disposal journal is reversible only within the same period before period close; retired assets excluded from future depreciation runs; disposal report by period showing cost removed, accumulated depreciation removed, proceeds, and net gain/loss.
US and UK teams have different compliance hooks, but the same control problem.
US teams usually care about clean evidence for audit support, vendor records, payment controls, tax reporting, and management review. UK teams usually care about VAT-ready records, approval evidence, digital-record discipline, and traceable postings. The country-specific details differ, but the operating pattern is the same: the ERP needs controlled records, explicit ownership, defensible state changes, and evidence that survives beyond the person who completed the task.
The control matrix.
| Control area | Requirement | Acceptance proof |
|---|---|---|
| Control 1 | Disposal triggers automatic calculation and posting of depreciation through disposal date before retirement entries | Given an active asset with cost, accumulated depreciation, and NBV as of disposal date |
| Control 2 | gain/loss GL accounts configurable per asset category | when the fixed asset accountant initiates full disposal with proceeds amount_minor and proceeds currency_code |
| Control 3 | proceeds split by payment type (cash, trade-in, installment) supported | then the system runs partial-period depreciation through disposal date, calculates gain (proceeds minus NBV) or loss, posts disposal JE (credit asset cost, debit accumulated depreciation, debit proceeds receivable/cash, post gain/loss to configured GL account) atomically, and sets asset status to RETIRED with disposal_date stamped |
| Control 4 | system prevents disposal of assets with open CIP or pending transfers | negative) when disposal is attempted on an asset with open CIP charges then the system rejects with 422 OPEN_CIP_BLOCKS_DISPOSAL. |
| Control 5 | disposal journal is reversible only within the same period before period close | Full asset retirement posted in a single workflow with correct gain/loss; asset removed from depreciation schedule immediately; GL balances for asset cost and accumulated depreciation reduced correctly. |
| Control 6 | retired assets excluded from future depreciation runs | Full asset retirement posted in a single workflow with correct gain/loss; asset removed from depreciation schedule immediately; GL balances for asset cost and accumulated depreciation reduced correctly. |
Audit evidence is a chain, not a folder.
| Evidence layer | What should be preserved |
|---|---|
| Business event | The fixed asset accountant initiates a full disposal of an asset (sold, scrapped, or abandoned). The system retrieves the asset's cost, accumulated depreciation, and net book value as of the disposal date, running any partial-period depreciation through the disposal date first. The accountant enters the proceeds (zero for scrapped assets). The system calculates gain (proceeds minus NBV) or loss (NBV minus proceeds), then posts the disposal journal: remove asset cost (credit), remove accumulated depreciation (debit), record proceeds received (debit cash/receivable), and post gain to other income or loss to other expense. The asset master status is set to Retired with disposal date stamped. |
| Control rules | Disposal triggers automatic calculation and posting of depreciation through disposal date before retirement entries; gain/loss GL accounts configurable per asset category; proceeds split by payment type (cash, trade-in, installment) supported; system prevents disposal of assets with open CIP or pending transfers; disposal journal is reversible only within the same period before period close; retired assets excluded from future depreciation runs; disposal report by period showing cost removed, accumulated depreciation removed, proceeds, and net gain/loss. |
| Acceptance proof | Given an active asset with cost, accumulated depreciation, and NBV as of disposal date; when the fixed asset accountant initiates full disposal with proceeds amount_minor and proceeds currency_code; then the system runs partial-period depreciation through disposal date, calculates gain (proceeds minus NBV) or loss, posts disposal JE (credit asset cost, debit accumulated depreciation, debit proceeds receivable/cash, post gain/loss to configured GL account) atomically, and sets asset status to RETIRED with disposal_date stamped; (negative) when disposal is attempted on an asset with open CIP charges then the system rejects with 422 OPEN_CIP_BLOCKS_DISPOSAL. |
| Data record | |
| System event | |
| Lifecycle state | |
The useful version of this workflow is not only fast. It is inspectable. A controller, auditor, or operator should be able to move from source event to system record to state transition to final business outcome without guessing.
Implementation contracts.
Reference data model
`asset_disposals` { id: string, external_id: string, asset_id: string, disposal_date: date, disposal_type: enum(SOLD,SCRAPPED,ABANDONED), proceeds_minor: int64, currency_code: char(3), cost_removed_minor: int64, accum_depr_removed_minor: int64, nbv_at_disposal_minor: int64, gain_loss_minor: int64, disposal_je_id: string, status: enum(PENDING,POSTED,REVERSED) }; (reference, product may differ).API and events
`POST /v1/fixed-assets/{id}/disposals` { disposal_date, disposal_type, proceeds_minor, currency_code, external_id } -> 201 { id, gain_loss_minor, currency_code, disposal_je_id, status: POSTED }; `GET /v1/fixed-assets/{id}/disposals`; `GET /v1/asset-disposals/report?period_start&period_end`; emits `fixed_asset.disposed` event; idempotent via `external_id`.State transitions
`ACTIVE -> RETIRED`; guard: partial-period depreciation must post before retirement JE; disposal reversible only within same period before close; RETIRED assets excluded from future depreciation runs.Common implementation traps.
Treating the workflow as data entry
If the ERP only stores the final record, the team loses the decision trail that explains how the record became valid.
Hiding exception logic
Exceptions need owners, reason codes, and time stamps. A vague pending state is not a control.
Posting without recovery design
Retries, duplicate submissions, and partial failures must be explicit so the system does not create inconsistent records.
Skipping evidence design
A workflow that cannot produce evidence on demand will eventually push finance teams back into manual screenshots and spreadsheets.
Where Rivane fits.
Rivane is built for finance workflows where automation must stay tied to source documents, approvals, state transitions, ledger impact, reporting, and audit evidence. Use this guide as a checklist for evaluating whether an ERP workflow is merely digitized or actually controlled.
References and source basis.
These sources provide the standards, regulatory, or government context around the flow. They are included so the guide is useful to finance operators, auditors, and implementation teams, not only buyers reading software copy.