Fixed Assets - Depreciation is where ERP discipline either begins or breaks.
Depreciation Run and GL Posting (Straight-Line) 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: Monthly depreciation posting completed in under 5 minutes; zero manual spreadsheet calculation; accumulated depreciation sub-ledger reconciles to GL to the cent.
The control flow a finance team actually needs.
Step 1
Depreciation Calculation Be...
Step 2
Half-Month, Half-Year, And Full-Month...
Step 3
Preview Show Period And Year-To-Date...
Step 4
Posting Creates One Summarized JE Per...
Step 5
Prevents Double-Posting The Same Period
The ERP surface involved.
Module
Fixed Assets - Depreciation
Actors
Fixed Asset Accountant, ERP System, GL Module
Tier
Tier 1
Finance area
Fixed Assets & Lease Management
Region lens
US and UK finance teams
Publication date
June 11, 2026
Depreciation calculation must be deterministic and reproducible for any historical period; half-month, half-year, and full-month conventions configurable per asset category; preview must show period and year-to-date depreciation before posting; posting creates one summarized JE per GL account combination with asset-level detail in sub-ledger; system prevents double-posting the same period; re-run after correction voids prior entry and reposts; depreciation run completes for 10,000+ assets in under 60 seconds.
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 | Depreciation calculation must be deterministic and reproducible for any historical period | Given active fixed assets with assigned straight-line depreciation books and an open accounting period |
| Control 2 | half-month, half-year, and full-month conventions configurable per asset category | when the fixed asset accountant initiates a depreciation run, reviews the preview report, and approves posting |
| Control 3 | preview must show period and year-to-date depreciation before posting | then the system posts a batch JE debiting depreciation expense and crediting accumulated depreciation per GL account/cost-center combination, updates each asset's net book value and accumulated depreciation balance, and marks the period as depreciation-posted |
| Control 4 | posting creates one summarized JE per GL account combination with asset-level detail in sub-ledger | negative) when the same period has already been posted then the system rejects with 409 DEPRECIATION_ALREADY_POSTED and requires a void-and-repost workflow. |
| Control 5 | system prevents double-posting the same period | Monthly depreciation posting completed in under 5 minutes; zero manual spreadsheet calculation; accumulated depreciation sub-ledger reconciles to GL to the cent. |
| Control 6 | re-run after correction voids prior entry and reposts | Monthly depreciation posting completed in under 5 minutes; zero manual spreadsheet calculation; accumulated depreciation sub-ledger reconciles to GL to the cent. |
Audit evidence is a chain, not a folder.
| Evidence layer | What should be preserved |
|---|---|
| Business event | At month-end the fixed asset accountant initiates a depreciation run for the current period, selecting the entity and depreciation book. The system calculates straight-line depreciation for every active asset (cost minus salvage value divided by useful life in periods), proration-adjusting any assets placed in service mid-period using the half-month convention. A preview report lists asset ID, description, depreciation amount, and accumulated depreciation balance. The accountant reviews, approves, and posts; the system generates a batch journal entry debiting depreciation expense and crediting accumulated depreciation by cost center and asset category. The asset's net book value and accumulated depreciation balances update in real time. |
| Control rules | Depreciation calculation must be deterministic and reproducible for any historical period; half-month, half-year, and full-month conventions configurable per asset category; preview must show period and year-to-date depreciation before posting; posting creates one summarized JE per GL account combination with asset-level detail in sub-ledger; system prevents double-posting the same period; re-run after correction voids prior entry and reposts; depreciation run completes for 10,000+ assets in under 60 seconds. |
| Acceptance proof | Given active fixed assets with assigned straight-line depreciation books and an open accounting period; when the fixed asset accountant initiates a depreciation run, reviews the preview report, and approves posting; then the system posts a batch JE debiting depreciation expense and crediting accumulated depreciation per GL account/cost-center combination, updates each asset's net book value and accumulated depreciation balance, and marks the period as depreciation-posted; (negative) when the same period has already been posted then the system rejects with 409 DEPRECIATION_ALREADY_POSTED and requires a void-and-repost workflow. |
| 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_runs` { id: string, external_id: string, entity_id: string, book_id: string, period_start: date, period_end: date, convention: enum(HALF_MONTH,HALF_YEAR,FULL_MONTH), status: enum(PREVIEW,POSTED,VOIDED), posted_je_id: string, asset_count: int, total_depreciation_minor: int64, currency_code: char(3) }; `depreciation_run_lines` { id: string, run_id: string, asset_id: string, period_depreciation_minor: int64, ytd_depreciation_minor: int64, accumulated_depreciation_minor: int64, net_book_value_minor: int64 }; (reference, product may differ).API and events
`POST /v1/depreciation-runs` { entity_id, book_id, period_start, period_end, convention, external_id } -> 201 { id, status: PREVIEW, lines: [...] }; `POST /v1/depreciation-runs/{id}/post` -> 200 { status: POSTED, je_id }; `POST /v1/depreciation-runs/{id}/void` -> 200 { status: VOIDED }; `GET /v1/depreciation-runs/{id}/preview-report`; emits `depreciation_run.posted` event.State transitions
`PREVIEW -> POSTED`; `POSTED -> VOIDED` (same period only, before period close); guard: POSTED blocks re-run of same period without void first; void creates reversing JE and resets assets to prior-period balances.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.