Fixed Assets - Disposals & Retirements is where ERP discipline either begins or breaks.
Partial Asset Disposal with Remaining Asset Continuation 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: Partial disposal correctly reduces asset basis; remaining asset depreciates on correct cost basis; gain/loss accurately calculated on disposed portion only.
The control flow a finance team actually needs.
Step 1
Partial Disposal Specifiable By Cost...
Step 2
Recalculates Remaining Asset'S Cost,...
Step 3
Depreciation On Remaining Asset Resumes...
Step 4
Partial Disposal Journal Is A Single...
Step 5
Remaining Asset NBV Equal Original NBV...
The ERP surface involved.
Module
Fixed Assets - Disposals & Retirements
Actors
Fixed Asset Accountant, Controller, ERP System
Tier
Tier 2
Finance area
Fixed Assets & Lease Management
Region lens
US and UK finance teams
Publication date
June 15, 2026
Partial disposal specifiable by cost amount, percentage, or units; system recalculates remaining asset's cost, accumulated depreciation, and NBV after partial removal; depreciation on remaining asset resumes from updated cost basis without useful-life reset unless explicitly changed; partial disposal journal is a single ACID transaction; remaining asset NBV must equal original NBV minus disposed NBV minus any depreciation to disposal date; gain/loss on partial disposal reported separately from full disposals; audit trail links original asset to both disposal record and continuation asset.
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 | Partial disposal specifiable by cost amount, percentage, or units | Given an active asset and a partial disposal specifying disposed cost amount_minor or percentage |
| Control 2 | system recalculates remaining asset's cost, accumulated depreciation, and NBV after partial removal | when the fixed asset accountant posts the partial disposal with proceeds_minor |
| Control 3 | depreciation on remaining asset resumes from updated cost basis without useful-life reset unless explicitly changed | then the system calculates proportional cost/accumulated-depreciation/NBV for the disposed portion, runs depreciation through disposal date, posts a single ACID partial disposal JE, records the gain or loss, reduces the remaining asset's cost basis, and recalculates the depreciation schedule on the remaining NBV without useful-life reset |
| Control 4 | partial disposal journal is a single ACID transaction | negative) when disposed cost_minor exceeds the asset's total cost_minor then the system rejects with 422 DISPOSAL_AMOUNT_EXCEEDS_ASSET_COST. |
| Control 5 | remaining asset NBV must equal original NBV minus disposed NBV minus any depreciation to disposal date | Partial disposal correctly reduces asset basis; remaining asset depreciates on correct cost basis; gain/loss accurately calculated on disposed portion only. |
| Control 6 | gain/loss on partial disposal reported separately from full disposals | Partial disposal correctly reduces asset basis; remaining asset depreciates on correct cost basis; gain/loss accurately calculated on disposed portion only. |
Audit evidence is a chain, not a folder.
| Evidence layer | What should be preserved |
|---|---|
| Business event | A company sells one wing of a building (a component) while retaining the rest. The fixed asset accountant initiates a partial disposal by specifying the percentage or dollar amount of the asset cost being disposed. The system calculates the proportional cost, accumulated depreciation, and NBV attributable to the disposed component, runs depreciation through the disposal date, and posts the partial disposal journal removing the component cost and accumulated depreciation. Proceeds are recorded and gain/loss is calculated. The remaining asset continues with a reduced cost basis, and the depreciation schedule is recalculated for the remaining NBV over the remaining useful life. |
| Control rules | Partial disposal specifiable by cost amount, percentage, or units; system recalculates remaining asset's cost, accumulated depreciation, and NBV after partial removal; depreciation on remaining asset resumes from updated cost basis without useful-life reset unless explicitly changed; partial disposal journal is a single ACID transaction; remaining asset NBV must equal original NBV minus disposed NBV minus any depreciation to disposal date; gain/loss on partial disposal reported separately from full disposals; audit trail links original asset to both disposal record and continuation asset. |
| Acceptance proof | Given an active asset and a partial disposal specifying disposed cost amount_minor or percentage; when the fixed asset accountant posts the partial disposal with proceeds_minor; then the system calculates proportional cost/accumulated-depreciation/NBV for the disposed portion, runs depreciation through disposal date, posts a single ACID partial disposal JE, records the gain or loss, reduces the remaining asset's cost basis, and recalculates the depreciation schedule on the remaining NBV without useful-life reset; (negative) when disposed cost_minor exceeds the asset's total cost_minor then the system rejects with 422 DISPOSAL_AMOUNT_EXCEEDS_ASSET_COST. |
| 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_partial_disposals` { id: string, external_id: string, asset_id: string, disposal_date: date, disposed_cost_minor: int64, disposed_accum_depr_minor: int64, disposed_nbv_minor: int64, currency_code: char(3), proceeds_minor: int64, gain_loss_minor: int64, disposal_pct: decimal, disposal_je_id: string }; `fixed_assets` updated: remaining_cost_minor, remaining_accum_depr_minor, remaining_nbv_minor post-partial; (reference, product may differ).API and events
`POST /v1/fixed-assets/{id}/partial-disposals` { disposal_date, disposed_cost_minor, currency_code, proceeds_minor, external_id } -> 201 { id, gain_loss_minor, remaining_nbv_minor, disposal_je_id }; `GET /v1/fixed-assets/{id}/partial-disposals`; emits `fixed_asset.partially_disposed` event; idempotent via `external_id`.State transitions
asset remains `ACTIVE` after partial disposal with updated cost basis; guard: disposed_cost_minor <= total asset cost_minor; remaining NBV = original NBV - disposed NBV - pre-disposal depreciation; partial disposal JE is a single ACID transaction.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.