PSAB 3150 is the Canadian public-sector accounting standard for tangible capital assets. For municipalities, it affects ERP modernization because roads, bridges, buildings, fleet, water infrastructure, land improvements, equipment, and other capital assets must be recorded, tracked, amortized, supported with evidence, and connected to finance reporting.
When a municipality modernizes its ERP or finance workflows, PSAB 3150 should not be treated as a year-end reporting issue only. It should be considered early in system design, data migration, asset management, reporting, and audit-readiness planning.
What is PSAB 3150?
PSAB 3150, Tangible Capital Assets, sets out how public-sector organizations account for and report tangible capital assets.
In practical municipal terms, it applies to physical assets that are held for use, support service delivery, have useful lives beyond one accounting period, and are not held for sale in the ordinary course of operations.
For municipalities, this can include:
- Roads
- Bridges
- Water and wastewater infrastructure
- Buildings
- Land improvements
- Vehicles and fleet
- Machinery and equipment
- Parks and recreation assets
- Technology infrastructure
- Fire, public works, and operations equipment
The accounting question is not only whether the municipality owns the asset. It is whether the asset record, cost, useful life, amortization, classification, and supporting evidence can be maintained and reported reliably.
Why PSAB 3150 matters during ERP modernization
ERP modernization changes how finance, asset, operations, and reporting data move across the organization.
If tangible capital asset records are incomplete, inconsistent, or maintained across spreadsheets and side systems, a new ERP project may expose gaps that were previously hidden by manual effort.
PSAB 3150 matters during modernization because the municipality needs to understand:
- Which assets exist
- Where asset records are maintained
- How historical cost is supported
- How useful lives are assigned
- How amortization is calculated
- How disposals and write-downs are recorded
- How additions are captured
- How asset categories map to financial reporting
- How audit evidence is retained
- How asset records connect to public works, finance, and capital planning
Without that mapping, the future system may not support the municipality’s reporting and audit needs. Using a specialized PSAB Fund Accounting Accelerator can help align ledger structures early.
How PSAB 3150 connects finance and operations
Tangible capital assets are not only a finance concern. They often sit at the intersection of finance, public works, asset management, engineering, facilities, utilities, and capital planning.
Finance may need the asset record for amortization and reporting. Public works may need the same asset for maintenance, condition, location, and lifecycle planning. Asset management may track replacement timing, inspections, and capital forecasts.
During ERP modernization, the municipality should avoid treating these as disconnected records. The same asset may need to support:
- Financial reporting
- Asset hierarchy
- Work orders
- Maintenance history
- Capital project tracking
- Grant reporting
- Insurance records
- Audit evidence
- Council or leadership reporting
A modernized environment should clarify how these records relate, even if every function does not live in the same system.
Common PSAB 3150 issues municipalities discover during modernization
Many municipalities only discover asset-data issues when they begin migration planning or year-end preparation.
Common issues include:
- Asset registers maintained in spreadsheets
- Missing historical cost support
- Inconsistent asset categories
- Useful lives that are not consistently documented
- Amortization schedules outside the finance system
- Differences between public works asset lists and finance asset records
- Capital projects not clearly linked to asset additions
- Disposals or replacements not updated consistently
- Limited audit trail for asset changes
- Asset records that do not align with reporting structures
- Supporting evidence stored in shared drives without a clear retention pattern
These issues do not always mean the municipality is doing something wrong. They often reflect years of practical workarounds created to keep reporting moving. The modernization risk is carrying those workarounds into the new environment without understanding them.
What should be mapped before changing systems?
Before selecting, configuring, or migrating to a new ERP or finance environment, municipalities should map their tangible capital asset process from end to end. This is especially true if planning a Dynamics GP migration, as legacy assets must be carefully reconciled.
At minimum, this should include:
- Asset categories
Identify the categories used for accounting, reporting, operations, maintenance, and capital planning. - Asset register location
Document whether asset records are in the ERP, spreadsheets, asset management tools, public works systems, or multiple locations. - Source of historical cost
Identify where original cost, contributed asset values, betterments, and capital project costs are supported. - Useful life and amortization logic
Document useful life assumptions, amortization methods, residual value treatment, and review processes. - Additions and betterments
Map how new assets, capital improvements, and project closeouts become finance records. - Disposals and write-downs
Document how retired, replaced, impaired, or disposed assets are approved and recorded. - Reconciliation process
Map how finance asset records are reconciled with operational asset lists and supporting evidence. - Reporting outputs
Identify year-end schedules, financial statement inputs, audit requests, management reports, and council reporting needs. - Evidence storage
Document where invoices, project files, valuation support, approvals, and audit evidence are retained. - Ownership and controls
Clarify which teams own asset creation, updates, review, approval, and reporting.
This mapping gives the municipality a clearer basis for system design and migration decisions.
How PSAB 3150 affects data migration
During ERP modernization, asset data should not be treated as a simple spreadsheet upload.
Key migration questions include:
- Which asset records are active?
- Which historical records must remain accessible?
- Which fields are mandatory in the future system?
- Which asset categories need to be standardized?
- Which records have incomplete cost or useful-life data?
- Which records need supporting documentation?
- Which asset IDs should be preserved?
- How will opening balances be validated?
- How will migrated asset values reconcile to the general ledger?
- How will audit evidence be linked or retained?
If these questions are not answered early, asset migration can become a late-stage project risk.
How PSAB 3150 affects reporting and audit readiness
PSAB 3150 readiness depends on more than having an asset list. Municipalities need evidence that supports the numbers used in reporting.
That means the ERP modernization plan should consider:
- Financial statement note support
- Asset continuity schedules
- Additions and disposals
- Amortization expense
- Accumulated amortization
- Net book value
- Capital work in progress
- Contributed assets
- Write-downs
- Betterments
- Audit evidence and approvals
A stronger reporting design helps the municipality reduce manual year-end effort and respond more confidently to audit requests.
Why this should be addressed before procurement
Municipalities often evaluate ERP systems based on modules, features, demonstrations, and pricing. Those are important, but PSAB 3150 readiness depends on how the municipality’s asset and finance reality will be handled in practice.
Before procurement or implementation, municipalities should understand:
- Current asset-data gaps
- Reporting requirements
- Audit evidence needs
- Operational asset dependencies
- Migration complexity
- Required reconciliations
- Future-state ownership
- Configuration versus customization needs
This gives the municipality a better basis for vendor discussions and reduces the risk of discovering asset-data problems during implementation.
What this means for your municipality
PSAB 3150 should be treated as a modernization design requirement, not a year-end afterthought.
For Canadian municipalities, the practical starting point is to map tangible capital asset records, finance reporting needs, operational asset dependencies, and audit evidence before ERP configuration or migration decisions are made.
A well-planned approach can help the municipality protect reporting continuity, reduce manual reconciliation, and improve confidence in year-end and audit-readiness workflows.
Sources
Frequently Asked Questions
What is PSAB 3150?
PSAB 3150 is the Canadian public-sector accounting standard for tangible capital assets. It guides how public-sector organizations account for and report physical assets used to deliver services.
Why does PSAB 3150 matter for municipalities?
It matters because municipalities manage significant tangible capital assets such as roads, bridges, buildings, vehicles, water infrastructure, and equipment. These records affect financial reporting, amortization, audit evidence, and capital planning.
How does PSAB 3150 affect ERP modernization?
It affects ERP modernization because asset records, historical cost, useful life, amortization, categories, audit evidence, and finance reporting structures may need to be mapped, cleaned, migrated, or redesigned.
Should asset records be reviewed before ERP migration?
Yes. Municipalities should review asset records before migration so they understand data gaps, reconciliation needs, reporting requirements, and evidence trails before configuring the future system.
What is the biggest PSAB 3150 risk during modernization?
The biggest risk is assuming asset data is ready for migration when records are actually spread across finance systems, spreadsheets, public works tools, project files, and shared drives.
How can municipalities improve PSAB 3150 readiness?
Municipalities can improve readiness by mapping asset categories, registers, cost support, useful lives, amortization logic, additions, disposals, reconciliations, reporting outputs, and audit evidence.