Meeting GRAP Requirements Without Disruption

Municipalities and public entities often inherit asset registers that were built for basic compliance rather than the level of detail required by GRAP 17 for complex infrastructure, buildings and plant assets. When significant components are bundled into a single asset line, depreciation becomes unreliable, replacements are difficult to account for, and audit queries follow.

Fixed asset register unbundling is the structured process of splitting a single asset record into significant components so that useful lives, depreciation, and replacement accounting align with GRAP 17. The key is implementing this process in a controlled way that protects service delivery, while keeping the general ledger and annual financial statements stable.

Many municipalities therefore undertake fixed asset register unbundling projects to align their infrastructure asset registers with GRAP 17 componentisation requirements.

What Is Fixed Asset Register Unbundling Under GRAP 17

Defining Fixed Asset Register Unbundling and Componentisation

• Unbundling is the asset register activity of converting one asset line into multiple component records that together represent the same physical asset.
• Componentisation is the accounting principle that requires significant parts of an asset with different useful lives or consumption patterns to be depreciated separately.

Why GRAP 17 Requires Complex Assets to Be Unbundled

GRAP 17 requires depreciation to reflect how service potential is consumed. For complex assets, applying a single useful life rarely reflects reality.

Componentisation also makes it easier to:

• Derecognise replaced parts correctly
• Capitalise renewals consistently
• Focus impairment assessments on the component that is actually affected

Examples of Assets That Typically Require Unbundling

Common candidates include:

• Roads and stormwater networks
• Water and wastewater networks (pipes, valves, pumps, reservoirs)
• Buildings (structure, roof, lifts, HVAC, electrical systems, finishes)
• Treatment works and plants (civil, mechanical, electrical, and control systems)

Why Fixed Asset Register Unbundling Matters for Public Sector Audit Outcomes

How Incorrect Asset Grouping Leads to Audit Findings

Where asset descriptions are vague and components are hidden within single asset lines, auditors struggle to confirm whether depreciation and carrying values are reasonable.

Typical problem patterns include:

• Applying a single useful life to an entire infrastructure network
• Inconsistent capitalisation of renewals
• Disposals that cannot be properly supported

The Impact of Poor Componentisation on Asset Values

Bundled assets often lead to over- or under-depreciation that accumulates over time. They can also hide impairment indicators and distort carrying values and related disclosures.

Why Unbundling Has Become a Priority

For many municipalities and public entities, infrastructure is the largest balance on the statement of financial position. Improving component-level accuracy is one of the most effective ways to reduce recurring asset-related audit findings.

Planning a Fixed Asset Register Unbundling Project Without Disruption

Securing Executive and Governance Support

Treat unbundling as a governance and change project, not just a finance exercise.

Engage the following stakeholders early:

• Accounting officer
• CFO
• Audit committee
• Internal audit
• Engineering and technical leadership

Early alignment helps manage risk, timing, and implementation expectations.

Defining Scope, Objectives, and Timelines

Set clear project parameters:

• Asset classes and regions in scope
• Conversion cut-off date and reporting period
• Systems involved (asset register, ERP, GIS)
• Deliverables, including audit trail schedules and updated policies

Aligning the Project with Financial Reporting Cycles

Plan implementation around:

• Year-end reporting timelines
• Major capital projects
• Budget cycles
• System upgrades

If depreciation will change materially, incorporate the impact into budgeting and financial reporting discussions early.

Step 1: Identify Assets That Require Fixed Asset Register Unbundling

Using GRAP 17 Guidance

Start with a simple diagnostic question:

Are there significant components with different useful lives or replacement patterns?

If yes, the asset is likely a candidate for componentisation.

Prioritising High-Value Assets

Adopt a risk-based approach by prioritising:

• High-value infrastructure assets
• Buildings
• Long-life strategic assets
• Assets previously linked to audit findings

Screening the Register for Weak Descriptions

Red flags in asset registers often include descriptions such as:

• “Infrastructure”
• “Roads”
• “Building upgrades”

Large balances with limited location or component information often conceal multiple components.

Step 2: Design the Componentisation Methodology

Setting Component Materiality Thresholds

Avoid over-engineering the asset register by defining thresholds such as:

• Value thresholds
• Useful life variance thresholds
• Service criticality thresholds

These rules should be clearly documented in asset management policies.

Developing Standard Component Libraries

Create component templates for asset types such as:

• Roads
• Water networks
• Sewer systems
• Electricity networks
• Buildings

Standard libraries improve consistency, efficiency, and future project handovers.

Agreeing Useful Life Ranges

Work with technical departments to determine realistic useful life ranges based on:

• Local environmental conditions
• Maintenance strategies
• Engineering assessments

Maintain a documented record of assumptions and approvals to support audit review.

Step 3: Gather Technical and Financial Data

Collaborating with Engineering and Technical Teams

Successful componentisation requires close collaboration between finance and engineering teams. Structured workshops and formal sign-off processes reduce rework later in the project.

Using Available Documentation

Useful evidence may include:

• As-built drawings
• Bills of quantities
• GIS records
• Completion certificates
• Refurbishment records
• Maintenance histories
• Condition assessments

Where information gaps exist, structured estimates supported by engineering approval may be used.

Allocating Costs Between Components

If original cost splits are unavailable, entities may allocate costs using:

• Replacement cost proportions scaled back to historical cost
• Standard engineering percentage allocations by asset type

Consistency, documentation, and a clear audit trail are essential.

Step 4: Perform Fixed Asset Register Unbundling

Splitting Asset Records

Prepare a conversion schedule mapping each existing asset to its new component records, including:

• Cost allocation
• Accumulated depreciation splits
• Carrying amount allocations

Updating Asset Master Data

Each component must have complete master data, including:

• Unique asset number
• Location or network reference
• Correct cost centre
• mSCOA segments (where applicable)
• Parent-child asset relationships where supported by the system

Maintaining Reconciliation and Audit Trail

At conversion date:

• Total cost and accumulated depreciation must reconcile to the original asset record
• Maintain signed allocation schedules and before-and-after reports

Step 5: Update Useful Lives and Depreciation

Revising Useful Lives

Once components exist, reassess remaining useful lives using:

• Asset condition assessments
• Replacement history
• Technical input

Residual values should only be updated where clearly supportable.

Aligning Depreciation Methods

Straight-line depreciation is the most commonly applied method, but methods must still reflect the consumption of service potential.

Where usage drives deterioration, consider whether alternative depreciation methods are more appropriate, such as the diminishing balance or units of production methods. For example, motor vehicles are often better suited to the units of production method.

Identifying Impairment Indicators

Component-level data makes it easier to identify impairment indicators such as:

• Damage
• Obsolescence
• Under-utilisation

All judgements should be clearly documented.

Step 6: Reconcile the Unbundled Register to the General Ledger

Reconciling Balances

Reconcile the updated asset register to:

• Asset control accounts
• Trial balance
• Asset classes in the financial statements

Processing Journals and Corrections

Distinguish between:

• Conversion entries (splitting assets without changing totals)
• Corrections of historical errors

Maintain clear approval and audit documentation.

Testing Movements After Conversion

After unbundling, test whether the system correctly processes:

• Additions
• Disposals
• Depreciation
• Impairments

Prepare schedules allowing auditors to trace balances from the old register to the new one.

Managing Operational Disruption During Fixed Asset Register Unbundling 

To minimise operational disruption:

• Implement work in phases by asset class or region
• Run a pilot before full implementation
• Apply change control procedures to system updates

Coordinate with maintenance and capital project teams to ensure new assets are correctly componentised.

Controls, Policies and Systems for Componentised Registers

Long-term sustainability requires:

• Updated asset management policies reflecting componentisation rules
• Defined thresholds and useful life tables
• Systems capable of supporting parent-child asset relationships and partial disposals
• Standard project handover processes ensuring new assets are componentised

Entities should also conduct periodic reviews of useful lives and component structures.

When External Support May Be Required for Asset Register Unbundling 

External support may be useful when:

• Infrastructure portfolios and quantities are extensive
• Technical documentation is fragmented
• Asset management systems have limitations
• Audit remediation timelines are tight

Specialist teams can assist with:

• GRAP interpretation
• Engineering-based component libraries
• Cost allocation methodologies
• Data conversion and reconciliations
• Audit-ready documentation

Knowledge transfer should always be prioritised so internal teams can maintain the register after implementation.

How Fixed Asset Register Unbundling Improves Governance and Asset Management 

When implemented properly, unbundling:

• Reduces GRAP 17 compliance risk
• Improves depreciation accuracy
• Supports correct replacement accounting
• Strengthens maintenance planning and renewal funding decisions
• Improves transparency in reporting to councils, communities, and oversight bodies

 

Frequently Asked Questions

How Long Does Unbundling Typically Take?

A pilot on a defined asset class can be completed quickly. However, full infrastructure unbundling may take several months depending on:

• Asset portfolio size
• Data quality
• System capability
• Technical validation requirements

What If Historical Cost Data Is Missing?

Where historic data is incomplete, entities should use the best available evidence and apply structured estimation methods supported by engineering sign-off.

Consistency and documentation are essential.

Can Unbundling Be Phased?

Yes. Many municipalities phase implementation by asset class, region, or risk level. Each phase must reconcile cleanly to the general ledger and financial statements.

How Often Should Component Structures Be Reviewed?

Component structures should be reviewed:

• At least annually
• When major refurbishments occur
• When condition assessments indicate changes in useful life

How Ducharme Supports Fixed Asset Register Unbundling Projects

Ducharme supports municipalities and public entities through:

• Diagnostic reviews of existing asset registers
• Component library and methodology development
• Practical conversion and system support
• Reconciliation to the general ledger and annual financial statements
• Training for finance and technical teams to maintain compliant asset registers

From Unbundling to Sustainable Asset Management

Fixed asset register unbundling is a critical step towards GRAP 17 compliance, but long-term success depends on how well the register is maintained thereafter. A componentised fixed asset register requires more than structure — it requires systems that can support accuracy, consistency, and audit readiness over time.

Ducharme’s Cloud-based Fixed Asset Register (FAR) provides the foundation. It enables asset accounting life-cycle automation, accurate depreciation calculations, and GRAP / IPSAS-aligned reporting, while maintaining detailed, component-level asset data aligned to AFS reporting periods. This ensures municipalities and public entities can manage complex infrastructure assets with confidence and produce reliable, audit-ready financial information.

To sustain that accuracy, Ducharme’s Dynamic Verify solution brings real-time visibility into the physical asset environment. Through mobile, on-site verification and a centralised cloud dashboard, asset data can be continuously validated — including condition, location, and custodian information — with a clear audit trail and supporting evidence.

Together, FAR and Dynamic Verify create a fully integrated asset management ecosystem:

• FAR ensures structured, compliant asset accounting and reporting
• Dynamic Verify ensures accurate, up-to-date asset data from the field

This integration allows verified data to flow directly into the asset register, strengthening depreciation accuracy, impairment assessments, and overall GRAP / IPSAS compliance.

By combining structured unbundling with technology-enabled asset management and verification, municipalities and public entities can move beyond once-off compliance exercises and establish a sustainable, well-governed asset register that supports better decision-making, stronger audit outcomes, and long-term infrastructure planning.