There is a predictable moment in the life of a Sage X3 deployment when fixed assets comes up. The register is a spreadsheet, depreciation is a monthly manual journal, and an auditor has asked a question that the spreadsheet cannot answer convincingly. Adding the module is straightforward work, but it is unforgiving in one specific area: the opening balances have to reconcile, and most abandoned attempts failed exactly there.
This page sets out what the implementation covers, the sequence we use, and the problems that most often surface afterwards. Depreciation methods, plan structures, and event handling vary by version and localization, so the policy decisions below should always be confirmed against your own configuration and with your auditors.
Reasons companies start this project
- The asset register still lives in Excel or a legacy tool
- Depreciation is posted by manual journal every month
- Capitalized purchases are not linked back to the purchase invoices that created them
- Book and tax depreciation differ with no system support for both
- Multi-company or multi-currency asset reporting is required
- A previous attempt at the module was abandoned because opening balances never tied out
What the implementation covers
Structure and accounting codes
Companies, sites, and asset families or categories, with accounting codes covering the asset account, accumulated depreciation, depreciation expense, and disposal gain or loss. Incomplete codes on disposal and impairment are a common cause of a blocked entry months after go-live.
Depreciation contexts and plans
A book plan for accounting alongside additional plans for tax, IFRS, or group reporting, each with its own method — straight-line, declining, units of production and others — durations, and fiscal calendars.
Capitalization flow
Expense lines on purchase invoices flagged as capital expenditure can feed asset creation, linking the asset directly to the invoice. Assets can also be created manually or loaded by import where that flow does not fit.
Opening balances
Existing assets are imported with cost, accumulated depreciation, and remaining life. This has to reconcile to the general ledger to the cent at the cutover date; everything downstream depends on it.
Periodic processing
Depreciation calculation, posting to the ledger, and period and year close in the asset module, aligned to the accounting calendar.
Asset events
Transfers between sites and companies, splits, revaluations, impairments, and disposals or sales with the resulting gain or loss.
Reporting
The register itself, the movement schedule or roll-forward that auditors ask for, and depreciation forecasting for budgeting.
How we run the implementation
- 1. Agree depreciation policy per category and plan
Set out the method, life, and start-date convention for each asset category and each plan, and confirm the treatment with your auditors before configuration begins.
- 2. Configure structure and simulate every journal
Build families, accounting codes, and plans, then simulate the accounting entry for each event type — acquisition, depreciation, transfer, impairment, disposal — so no code gap is discovered in production.
- 3. Build and reconcile the opening balance import
Convert the current register into the import structure with cost, accumulated depreciation, dates, and remaining life, and reconcile the result to the general ledger before signing it off.
- 4. Run parallel depreciation
Calculate one to two periods in Sage X3 alongside the legacy register and investigate every difference, however small. This is where start-date and remaining-life problems surface cheaply.
- 5. Train finance on the monthly cycle
Cover capitalization from purchasing, the monthly depreciation run, posting, and close — including what happens if a period close in assets is skipped.
- 6. Cut over at a period end
Go live on a clean period boundary with the reconciled opening position, and keep the legacy register available for one reporting cycle.
Where fixed assets implementations go wrong
- Opening accumulated depreciation loaded without matching remaining life, so monthly depreciation is wrong from the first run
- Depreciation start-date conventions — full month, mid-month, pro-rata — not matching the previous system
- The asset module fiscal year not aligned with the accounting fiscal year
- Accounting codes incomplete for disposal or impairment, discovered only when the first disposal is attempted
- Capitalization from invoices left unused, so assets get created twice or created late
- Period close in assets skipped, which later blocks the accounting close
When this needs a senior consultant
- Opening balances will not reconcile to the ledger
- Multiple depreciation books are required
- The module was partially implemented and then left
- Auditors have flagged the asset register
- The original implementation partner never scoped assets at all
PRH implements fixed assets as a standalone phase on existing Sage X3 deployments and takes over attempts that stalled. The work centers on opening balance reconciliation, depreciation policy that finance and the auditors both accept, and connecting capitalization to the purchasing process so the register maintains itself.
Fixed assets questions
Does Sage X3 include a fixed assets module?
Yes. It forms part of the finance suite and requires configuration and activation before it can be used.
Can Sage X3 handle book and tax depreciation separately?
Yes, through multiple depreciation plans or contexts held against each asset, each with its own method and duration.
Can assets be created automatically from purchase invoices?
Yes. Capital expenditure lines on invoices can generate asset records linked back to the originating invoice, which keeps the register current without duplicate entry.
How are existing assets loaded into Sage X3?
Through an import carrying cost, accumulated depreciation, dates, and remaining life. Reconciling that import to the general ledger is the step that determines whether the project succeeds.
Why is depreciation wrong after go-live?
Most often opening balance or remaining life mismatches, start-date conventions that differ from the previous system, or a fiscal calendar misalignment between the asset module and accounting.
Can fixed assets be added to an existing Sage X3 implementation?
Yes, and it commonly is. A follow-on phase scoped around a period-end cutover is the normal approach.
Related services and pages
- Finance and accounting consulting
The wider finance practice this work sits inside.
- Sage X3 Bank Reconciliation and Bank Statement Import
The other finance module most often added after go-live.
- Sage X3 Purchase Invoice Errors and Matching Problems
Capitalization starts with a correctly posted supplier invoice.
- Sage X3 implementation consulting
Senior-led implementation and phased module rollouts.
- Implementation services
How we scope and run implementation work.
- Migrating to Sage X3
When assets are part of a wider move from a legacy platform.
- Year-end close issues
Where a skipped asset period close shows up later.