ROUX AFRIQUEGROUP
ROUX AFRIQUE EVS · AFRICA & THE MIDDLE EAST
ASSET DATA RELIABILITY & GOVERNANCE
IDENTIFY · RECONCILE · MAINTAIN
An asset can only be managed effectively when it is identifiable, locatable and linked to a verifiable source
Roux Afrique EVS performs physical inventories of tangible fixed assets and builds structured Operational Asset Registers that reconcile field reality with Finance, Operations, Engineering, Maintenance and Insurance records.
At a defined reference date, each in-scope asset is associated—subject to the agreed granularity—with an identity, location, class, status, verification evidence and source-system identifiers.
Exceptions are isolated, documented and submitted for validation. They are never corrected silently.
FIELD REALITY & RECORD RELIABILITY
An Accounting Fixed Asset Register describes what the systems have recorded. Fieldwork reveals what exists, what has been moved, replaced, modified, shut down or removed.
Over time, discrepancies may arise from:
A structured inventory makes it possible to:
The assignment is not a statutory or financial audit, an accounting certification, or a legal verification of title, security interests or rights over the assets. It observes and reconciles assets within the agreed scope, at the reference date and under the agreed procedures. Recognition, impairment, disposal, scrapping and transfer decisions remain the responsibility of the client and, where applicable, its auditors and advisers.
SIX QUESTIONS BEFORE FIELDWORK
Register reliability, valuation preparation, ERP or CMMS migration, post-acquisition integration, movement control, multi-site consolidation or creation of a new baseline.
Entities, sites, areas, asset classes, leased or third-party assets, strategic spares, capital work in progress, idle assets and exclusions must be defined before counting begins.
Plant, functional unit, equipment, component, subassembly or lot: the level of detail must support the intended decision and remain consistent with the systems to be populated.
Existing tag, serial number, ERP identifier, Accounting Fixed Asset Register, CMMS/EAM or a new unique code: legacy identifiers and their mapping rules must be retained.
Date, method, location, photograph, nameplate reading, scan, tag, captured attributes and area-owner approval determine the traceability of each observation.
The data owner, site owners, approval rules and workflows for additions, transfers, replacements, modifications and disposals must be defined before delivery.
SIX INTEGRATED WORKSTREAMS
Define the data dictionary, asset classes, functional locations, parent-child relationships, statuses, mandatory fields, naming rules and evidence levels.
The structure may follow Group > Entity > Site > Building or Area > System > Asset > Component. It is tailored to the assignment’s purpose and is not presented as a universal model.
Consolidate existing lists, standardise formats, profile fields, detect duplicates and prepare field inventory routes.
Data from the Accounting Fixed Asset Register, ERP, CMMS/EAM, technical lists, drawings, SOV and project records remain identified as separate sources.
Locate and observe in-scope assets, read nameplates and collect the agreed identifiers, quantities, statuses and evidence.
QR codes, barcodes, RFID or other tagging media are used only where the mandate, environment, security and operating conditions permit.
A tag supports identification. It does not prove legal ownership, accounting recognition or fitness for service.
Document the required attributes: function, manufacturer, model, serial number, capacity, location, parent unit and lifecycle status.
Any condition assessment is limited to a first-level visual observation unless further investigations are expressly included. It does not constitute an operational test or an assessment of integrity, safety or compliance.
Reconcile field reality with the different source systems, preserve historical identifiers and classify discrepancies.
Each match may be one-to-one or require mapping.
Produce the structured, reconciled Asset Register for the agreed scope, with quality indicators, import mappings and an exception register.
The assignment also defines responsibilities, controls and update triggers so that the register does not become obsolete after fieldwork.
TWO DIRECTIONAL TESTS
The control starts with entries in the source systems and seeks the corresponding assets on site.
It tests in particular:
On its own, this control cannot identify every physical asset missing from the systems.
The control starts with observed assets and seeks their corresponding entries in accounting and technical systems.
It tests in particular:
It does not automatically validate ownership, carrying amount or accounting treatment.
A responsible assignment combines both directions and separately documents the population, achieved coverage, inaccessible assets and residual exceptions.
DISTINCT RECORDS
These records must interoperate without being conflated.
| Record | Primary purpose |
|---|---|
| Physical asset inventory | Documents the existence and observable attributes of in-scope assets at a reference date. |
| Operational / Master Asset Register | Structures identity, location, hierarchy, status and mappings required for ongoing asset management. |
| Accounting Fixed Asset Register | Holds the accounting representation of fixed assets, including costs, depreciation and carrying amounts under the company’s rules. |
| CMMS/EAM | Supports maintenance, work orders, failures, spare parts and maintenance plans. |
| Statement of Values | Presents values declared for insurance under separately determined valuation bases and structures. |
The Operational Asset Register is the data layer used to establish mappings between physical, technical, accounting and insurance realities.
MASTER ASSET REGISTER
Depending on the mandate, data may be organised around the following families.
Financial and insurance data are reconciled. They are not automatically audited or valued within the inventory assignment.
GRANULARITY & ASSET UNIT
The same industrial installation may represent:
Parent-child relationships and components that may require separate analysis are documented.
Component accounting, cost allocation, useful-life and depreciation decisions remain subject to the client’s policies and approvals.
RECONCILIATION & EXCEPTION REGISTER
The Reconciliation & Exception Register may distinguish in particular:
An asset not located is not automatically an asset that does not exist. A ‘Recorded not Found’ entry remains open until investigation and a documented decision.
Each exception has a source, available evidence, an owner, a proposed action and a validation status.
No discrepancy automatically triggers an accounting entry, derecognition, scrapping decision or legal conclusion.
EIGHT-STEP METHODOLOGY
Define the purpose, entities, sites, areas, asset classes, reference date, access, exclusions, HSE constraints, responsibilities and deliverables.
The approach—wall-to-wall, targeted, cyclical or sample-based—is explicit. A sample-based inventory is never presented as comprehensive.
Set the taxonomy, granularity, hierarchy, mandatory fields, statuses, identification rules and required evidence.
Collect, profile, standardise and deduplicate source data. Plan field routes, area owners and asset-movement controls.
Observe accessible assets and collect the agreed data and evidence in accordance with the protocol.
Access limitations, unvisited areas and non-observable assets are recorded.
Confirm or apply tags where included, read nameplates and document attributes, locations, parent-child relationships and agreed statuses.
Perform Book-to-Floor and Floor-to-Book controls. Link observations to Finance, Engineering, Maintenance and Insurance records without merging their purposes.
Submit sensitive cases to site and data owners. Document decisions, reservations and unresolved exceptions.
Issue the Asset Register, mappings and agreed import files, then formalise the workflow for additions, transfers, replacements and disposals.
Every reconciled entry must be linked to an identifier, location, source, verification method, date and validation status.
DATA ROOM
Depending on the mandate, requested data may include:
Missing, conflicting or unusable data are recorded in a Data Gap & Assumption Register.
QUALITY ASSURANCE / QUALITY CONTROL
Quality control covers in particular:
An assignment cannot be described as comprehensive when the population, access, granularity or exclusions do not support that conclusion.
INVENTYS® & VRA3D
Technology structures data and strengthens traceability without replacing field observation or professional judgement.
Inventys® supports the structuring of physical, technical, accounting and insurance data used in the assignment.
Any interface with an ERP, EAM or CMMS depends on the formats, rules and responsibilities defined in the mandate.
Where the site configuration justifies it, VRA3D can provide visual and spatial documentation of areas, installations and critical assets.
VRA3D is used only where it delivers real value. It is not evidence of ownership, an integrity diagnosis or a substitute for field and business validation.
Technology strengthens expertise. It does not replace controls, professional judgement or final validation.
DELIVERABLES
Depending on the mandate:
DECISION POINTS
Updates should also be triggered by every material acquisition, commissioning, modification, transfer, replacement, loss, disposal or scrapping event.
SECTORS
Relevant sectors include:
Our experts operate across Africa, the Maghreb and the Middle East, adapting protocols to each site’s access, security, document availability, asset mobility and system-maturity constraints.
CLEAR RESPONSIBILITIES
Observes, identifies, locates and characterises in-scope assets, then reconciles them with technical, accounting and insurance records.
Separately determines valuation bases and reconstruction or replacement values. Inventory data may support quantities and specifications; it does not determine values.
Analyses financial values, insured gross profit, dependencies and the Maximum Indemnity Period. An Asset Register does not calculate BI values.
Analyses hazards, protections, vulnerabilities, scenarios and recommendations. An inventory does not conclude on integrity, compliance or risk level.
Addresses Insurance Due Diligence, programme architecture, Risk Financing and strategic decisions. Roux Afrique EVS builds the physical and technical data within its mandate.
After a loss, documents and quantifies damage and loss, structures the claim and supports its defence. A pre-existing Asset Register may provide useful data without predetermining ownership, damage or indemnity.
Physical IT or OT equipment may be inventoried when in scope. Logical asset discovery, configurations, vulnerabilities and cyber exposures require a separate Roux Cyber mandate.
The assignment does not certify financial statements, legal ownership or IFRS, tax or statutory treatment. Those conclusions remain with the client’s authorised functions, auditors and advisers.
FRAMEWORKS
The engagement letter, client policies, accounting framework, internal procedures and local requirements remain determinative.
IAS 16 prescribes neither a universal Asset Register model, a tagging method nor a physical-inventory procedure.
No generic reference turns the assignment into ISO certification, an IFRS compliance attestation or an audit or assurance engagement over the financial statements.
FREQUENTLY ASKED QUESTIONS
It is a documented verification of assets within a defined scope, at a reference date and according to an agreed level of granularity.
A physical inventory records observations at a given date. An Operational Asset Register structures those observations and their mappings in a record designed to be maintained throughout the asset life cycle.
The Accounting Fixed Asset Register holds the financial representation of fixed assets. The Operational Asset Register describes their identity, location, hierarchy and status, and establishes the required mappings between systems.
No. It may be wall-to-wall, targeted, cyclical or sample-based. The scope, population, granularity, access, method, coverage and exclusions are explicitly documented.
No. Tagging depends on the agreed granularity, existing identifiers, operating conditions, security constraints and mandate. Some integrated or difficult-to-access assets cannot be physically tagged.
It is classified as an exception. Further investigation and a documented client decision are required before any correction, disposal or derecognition.
They are treated as separate populations when included in scope. Their physical presence does not establish ownership or accounting classification.
No. Any values reproduced in the Asset Register come from identified sources. Their validation or update requires a separate valuation assignment.
No. It documents physical observations, mappings and exceptions. It is neither legal evidence of ownership nor an audit or assurance engagement over the financial statements.
Mappings and import files can be prepared when the target systems, formats and rules are defined. Technical integration is included only when expressly stated in the mandate.
Through a documented workflow covering acquisitions, commissioning, transfers, replacements, modifications, losses and disposals, supported by periodic controls suited to asset volume, risk and mobility.
Access rights, collection methods, permitted uses, retention periods and disclosure rules are agreed with the client according to the sensitivity of the sites and data.
RELIABLE ASSET DATA
Share your sites, existing registers, source systems and intended decisions with us. Roux Afrique EVS will define the appropriate scope, granularity, verification protocol, reconciliation rules and governance model.
Speak with Roux Afrique EVS