Fixed Assets - Depreciation Books is where ERP discipline either begins or breaks.
Multiple Depreciation Books (Book vs Tax) 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: Single asset register drives both GAAP and tax depreciation without dual maintenance; book-tax temporary differences computed automatically; tax depreciation report ready for CPA/tax preparer without manual recalculation.
The control flow a finance team actually needs.
Step 1
Unlimited Depreciation Books Per Asset...
Step 2
Each Book Has Independent Method,...
Step 3
Only Designated Reporting Book Posts To GL
Step 4
Tax Book MACRS Recovery Periods And...
Step 5
Bonus Depreciation Percentage...
The ERP surface involved.
Module
Fixed Assets - Depreciation Books
Actors
Tax Accountant, Fixed Asset Accountant, ERP System
Tier
Tier 2
Finance area
Fixed Assets & Lease Management
Region lens
US and UK finance teams
Publication date
June 14, 2026
Unlimited depreciation books per asset per entity; each book has independent method (SL, DB, MACRS, units of production), useful life, convention (half-year, mid-quarter, mid-month), and salvage value; only designated reporting book posts to GL; tax book supports MACRS recovery periods (3, 5, 7, 10, 15, 20, 27.5, 39 years) and Section 179 expensing; bonus depreciation percentage configurable per tax year; book-tax difference report computes temporary differences by asset for deferred tax schedules; mid-quarter convention auto-triggered when more than 40% of depreciable basis placed in service in Q4.
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 | Unlimited depreciation books per asset per entity | Given an asset created in a multi-book entity (GAAP book and tax book configured |
| Control 2 | each book has independent method (SL, DB, MACRS, units of production), useful life, convention (half-year, mid-quarter, mid-month), and salvage value | when the depreciation run is executed |
| Control 3 | only designated reporting book posts to GL | then the GAAP book calculates straight-line depreciation and posts a GL journal entry, the tax book applies MACRS (with Section 179 and bonus depreciation applied first) but does NOT post to the GAAP GL, and the book-tax difference report shows temporary differences per asset with deferred tax amounts |
| Control 4 | tax book supports MACRS recovery periods (3, 5, 7, 10, 15, 20, 27.5, 39 years) and Section 179 expensing | negative) when a non-reporting book is configured to post to the GL then the system rejects with 422 NON_REPORTING_BOOK_CANNOT_POST_GL. |
| Control 5 | bonus depreciation percentage configurable per tax year | Single asset register drives both GAAP and tax depreciation without dual maintenance; book-tax temporary differences computed automatically; tax depreciation report ready for CPA/tax preparer without manual recalculation. |
| Control 6 | book-tax difference report computes temporary differences by asset for deferred tax schedules | Single asset register drives both GAAP and tax depreciation without dual maintenance; book-tax temporary differences computed automatically; tax depreciation report ready for CPA/tax preparer without manual recalculation. |
Audit evidence is a chain, not a folder.
| Evidence layer | What should be preserved |
|---|---|
| Business event | The entity maintains two depreciation books simultaneously: a GAAP book using straight-line depreciation for financial reporting and a US tax book using MACRS (Modified Accelerated Cost Recovery System) for tax return purposes. When an asset is created, it is automatically added to both books with book-specific depreciation methods, useful lives, and conventions. Each book runs its depreciation independently; only the GAAP book posts to the GL. The tax book accumulates tax basis and provides data for Form 4562 reporting. The system computes book-tax temporary differences for deferred tax calculations. |
| Control rules | Unlimited depreciation books per asset per entity; each book has independent method (SL, DB, MACRS, units of production), useful life, convention (half-year, mid-quarter, mid-month), and salvage value; only designated reporting book posts to GL; tax book supports MACRS recovery periods (3, 5, 7, 10, 15, 20, 27.5, 39 years) and Section 179 expensing; bonus depreciation percentage configurable per tax year; book-tax difference report computes temporary differences by asset for deferred tax schedules; mid-quarter convention auto-triggered when more than 40% of depreciable basis placed in service in Q4. |
| Acceptance proof | Given an asset created in a multi-book entity (GAAP book and tax book configured); when the depreciation run is executed; then the GAAP book calculates straight-line depreciation and posts a GL journal entry, the tax book applies MACRS (with Section 179 and bonus depreciation applied first) but does NOT post to the GAAP GL, and the book-tax difference report shows temporary differences per asset with deferred tax amounts; (negative) when a non-reporting book is configured to post to the GL then the system rejects with 422 NON_REPORTING_BOOK_CANNOT_POST_GL. |
| 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
`depreciation_books` { id: string, entity_id: string, book_name: string, method: enum(STRAIGHT_LINE,DECLINING_BALANCE,MACRS,UNITS_OF_PRODUCTION), convention: enum(HALF_MONTH,HALF_YEAR,HALF_QUARTER,MID_MONTH), posts_to_gl: boolean, is_reporting_book: boolean }; `asset_book_values` { id: string, asset_id: string, book_id: string, cost_minor: int64, currency_code: char(3), salvage_value_minor: int64, useful_life_periods: int, accumulated_depreciation_minor: int64, net_book_value_minor: int64 }; (reference, product may differ).API and events
`POST /v1/depreciation-books` { entity_id, book_name, method, convention, posts_to_gl, is_reporting_book } -> 201 { id }; `GET /v1/fixed-assets/{id}/book-values`; `GET /v1/depreciation-reports/book-tax-difference?entity_id&tax_year` -> { asset_id, gaap_nbv_minor, tax_basis_minor, temporary_difference_minor, currency_code }[]; emits `depreciation_run.posted` event (reporting book only); idempotent via `external_id`.State transitions
depreciation books are `ACTIVE` or `INACTIVE`; depreciation run status `PREVIEW -> POSTED -> VOIDED`; guard: only the is_reporting_book=true book triggers GL posting; MACRS book requires recovery_period and convention configured per asset.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.