Thirty years of counting what others assume

CPCON has done one thing, intensively, since the 1990s: make asset and stock records match physical reality. That focus has compounded into more than 4,500 engagements — wall-to-wall fixed asset verifications, multi-site stocktaking programmes, RFID implementations and valuations — delivered across Brazil, the United States, Mexico, Spain, the United Arab Emirates and now the United Kingdom. Estates have ranged from a few hundred assets in a single office to hundreds of thousands of items spread across plants, hospitals, branch networks and distribution estates.

Three decades of fieldwork settle a lot of methodological arguments. We use our own trained field teams rather than subcontracted labour, because count quality is set on the floor, not in the report. We reconcile three layers on every engagement — the physical estate, the financial record (fixed asset register or stock ledger) and the operational system (CMDB, CMMS or WMS) — because any two of them can agree and still be wrong. And we treat reconciliation, not counting, as the product: a number with its evidence attached.

What that experience looks like in practice

The methodology, in detail

Experience is only worth anything if it has hardened into method. Every CPCON engagement, whether a single-site stocktake or a multi-country fixed asset verification, runs the same four stages. The work that determines the result happens in planning and reconciliation; the counting in between is the visible part, but it goes right only when the bookends are done properly.

Planning & scoping

We begin from the data, not the floor. The register or stock ledger is extracted, the estate is mapped site by site, and the count basis — wall-to-wall, zoned or cycle — is agreed along with the cut-off point at which book balances are frozen. Count instructions, tolerances and recount thresholds are documented, and the sequence of work is planned so that operations are disrupted as little as possible. On distribution and manufacturing sites this means sequencing zones so the business keeps moving behind the count.

Fieldwork

CPCON’s own counters work the floor with mobile capture, recording identification, location, custodian and condition for fixed assets, or quantity by location for stock. Counts are blind — the counter does not see the expected figure, so there is no anchoring — and any line outside tolerance is recounted independently before the variance is accepted. Photographs and condition grading are captured as the team goes, so the evidence is created during the count rather than reconstructed afterwards.

Reconciliation

Counted data is matched line by line to the financial record. Each difference is classified — matched, found-not-on-register, register-not-found, transferred, mis-located, or genuine loss — and cause-coded so the cause can be acted on, not just the symptom. Net and gross variance are reported separately, because a small net figure can hide a large volume of offsetting errors. For technology estates the reconciliation runs across three sources at once.

Reporting & sign-off

The deliverable is never a raw spreadsheet. It is a posting-ready reconciliation mapped to your chart of accounts, an exception report, a KPI pack, a ghost-asset or write-off schedule where relevant, and the evidence trail an auditor will test. The output is designed around the obligations the finance team answers to — FRS 102 Section 17 measurement, Companies Act 2006 record-keeping, and the asset-level evidence behind capital allowances claims.

Physical, financial and operational — three layers, one reconciliation

The reason CPCON reconciles three layers, not two, is hard-won. A fixed asset register and a count can be made to agree while both are wrong about what an asset actually is or does; a CMDB and a count can agree while the finance system depreciates something that was scrapped two years ago. Reconciling all three — the physical estate, the financial record, and the operational system that runs it day to day — is the only way to surface the discrepancies that each pair would hide. It is the difference between a count and an audit, and it is why our verification work stands up as evidence.

• Physical. What is actually there — confirmed by a trained counter, photographed, located and condition-graded.
• Financial. What the books say you own — the fixed asset register, stock ledger and depreciation schedules the auditor will test.
• Operational. What the business runs on — the CMDB for IT, the CMMS or maintenance system for plant, the WMS for stock. This layer is where ownership of an asset’s working reality lives, and it is the one most often forgotten in a count.

For technology estates, where this three-way gap is widest, the dedicated methodology is described under ITAM & CMDB audit and IT asset inventory.

Asset classes we count

Three decades across every major sector means there is little we have not counted. Each asset class brings its own identification problem, its own regulatory constraint and its own reconciliation logic — and the experience that matters is knowing those differences before the engagement starts, not discovering them on site.

Technology built for counting

CPCON’s technology was built to count, not adapted from something else. The platform pairs our own UHF RFID tags and readers with a reconciliation engine that does the matching and cause-coding automatically. The practical effect is dramatic: RFID lets a counter read an entire bay or a rack of assets in seconds rather than scanning each barcode, cutting counting time by up to 90% and pushing accuracy past 99%. Fixed readers at doorways and aisle entries turn periodic counts into near-continuous visibility. But the technology is a means, not the product — we recommend the level of automation an estate justifies, and many engagements are perfectly well served by durable barcode or QR tagging applied during a verification. Because we are not a software vendor, that recommendation is engineered around your estate, never a licence target. The platform has also added AI-assisted reconciliation, which accelerates the matching of large, messy datasets where descriptions and identifiers are inconsistent.

A genuinely international track record

CPCON operates in six countries, and that footprint is operational, not a marketing map. It means a multi-site or cross-border estate is counted to one methodology by teams who understand the local regulatory and language context, and reconciled to a single consolidated position rather than stitched together from six disconnected counts.

The cpcongroup.com methodology is already relied on by FTSE-scale and Fortune-500 organisations. The UK operation brings that same senior methodology — not a franchised count crew — to organisations across the United Kingdom. You can read more about the firm and its leadership on the about page.

Sized to the engagement

The methodology is the same at every scale; what changes is its shape. Experience across thousands of projects means we right-size the approach rather than forcing every client through an enterprise process — or leaving a large estate under-resourced.

• Single-site and SME. One mobilisation: verify the estate, tag what is untagged, reconcile to the register or ledger, and hand back a clean baseline the in-house team can maintain. Fast, fixed-scope, and proportionate.
• Multi-site national. A programme of counts scheduled around operational windows across a branch or distribution network, run by rotating field teams to one playbook, and consolidated into a single reconciled dataset and KPI view.
• Enterprise and cross-border. Multi-country estates counted to one methodology, reconciled to one position, with governance, reporting cadence and integration to the group ERP and CMDB designed in from the start.
• Ongoing accuracy. Where a one-off count is not enough, a rolling cycle counting programme keeps the estate accurate between full verifications and removes the year-end scramble.

Why organisations choose CPCON

• Independence with no conflict. We issue no audit opinions and sell no software licences, so our verification work serves as evidence for your auditor and our technology advice serves your estate.
• Own teams, consistent quality. The people on your floor are CPCON’s, working to a documented method — the reason results are the same on site one and site fifty.
• Reconciliation as the deliverable. You receive a diagnosed, posting-ready dataset, not a raw count — net and gross variance separated, causes coded, evidence attached.
• Built for the standards you answer to. Outputs map to FRS 102, Companies Act 2006 s.386 and ISA (UK) 501 expectations, and to the asset detail behind capital allowances.
• Scale without losing rigour. The same discipline runs from a single unit to a multi-country estate, with proprietary RFID where the volume justifies it.

The reconciliation taxonomy, in plain terms

The single most important thing we hand a finance team is not a count but a classified reconciliation — every line resolved into a category it can act on. A raw variance figure tells you something is wrong; a classified reconciliation tells you what, where and what to do about it. Across thousands of engagements the categories have settled into a consistent taxonomy.

• Matched. The asset or stock line is present, in the expected place, agreeing with the record. The healthy majority, and the baseline everything else is measured against.
• Found, not on register. Real, in use, but never capitalised — equipment bought locally, transferred in without paperwork, or capitalised under a description no one can now match. These often carry unclaimed capital allowances.
• On register, not found. The ghost asset — still depreciating, still insured, physically gone. Each one needs a disposal or write-off decision and has a P&L and tax consequence.
• Mis-located / transferred. Right asset, wrong recorded location or cost centre. Common with mobile plant, IT and warehouse stock; corrected in the record rather than written off.
• Mis-described or duplicated. One physical asset carried as two register lines, or a description so generic it could be anything — the noise that makes registers untrustworthy and that a verification cleans up.
• Genuine loss / shrinkage. The residual that remains once every explicable category is removed. Only this should ever be treated as loss — and treating only this as loss is what separates an honest reconciliation from a lazy one.

Reporting net and gross variance separately falls straight out of this taxonomy: offsetting errors that net to nearly nothing still represent a register or a warehouse full of disorder, and only the classified view exposes it.

Quality control on the floor

Count quality is decided during the fieldwork, so that is where our controls concentrate. Counts are blind by default: the counter is not shown the book figure, which removes the single biggest source of soft error — unconsciously confirming the number the system expected. Tolerances and recount rules are agreed in advance, and any line that falls outside tolerance is independently recounted by a second person before the variance is accepted, so a genuine difference is confirmed and a counting slip is caught. Supervisors track coverage and hit rate live, so no location is skipped and none is counted twice. Evidence — photographs, location, condition — is captured as the team works, because evidence reconstructed afterwards is not evidence. Because the counters, supervisors and reconciliation analysts are CPCON’s own people working to one written method, these controls are applied the same way on a single-site count and on the fiftieth site of a national programme.

Data, integration and the systems we work with

A reconciliation is only useful if the finance and operations teams can actually post and act on it, so the output is shaped to the systems the client already runs. We deliver reconciled data mapped to the structure of the target system — SAP (including S/4HANA and EWM), Oracle, Microsoft Dynamics, Sage, Infor and others on the finance and ERP side; the WMS on the stock side; and the CMDB on the IT side — with each line classified and ready to import rather than rekeyed. For technology estates we reconcile across the fixed asset register, the CMDB and discovery tooling at once, because those three sources almost never agree and the gaps between them are where the real exposure sits. The AI-assisted layer in our platform accelerates the hardest part of this — matching large, messy datasets where descriptions and identifiers are inconsistent — but a human reconciliation analyst owns the result. Automation speeds the matching; it does not sign it off.

RFID, deployed not demonstrated

CPCON has deployed RFID in production at enterprise scale, not as a proof of concept. That experience is mostly about the unglamorous details that decide whether a deployment actually works: choosing the right tag and label for the material and environment — metal-mount tags for machinery and racking, on-metal and high-temperature variants where needed, the correct adhesive for the surface — placing fixed readers and antennas so they read what they should and not what they shouldn’t, and tuning read zones at dock doors and aisle entries to avoid stray reads from adjacent areas. Get those wrong and an RFID system produces confident nonsense; get them right and it counts a bay in seconds at better than 99% accuracy. Because we have done it across hundreds of sites and several countries, the configuration is engineered for the estate in front of us rather than sold from a catalogue — and where RFID is not the right answer, we say so and tag with durable barcode or QR instead, captured under asset tagging.

We leave the client able to maintain it

A verification or a stocktake is worth far less if the record drifts straight back out of true the moment we leave. So part of every engagement is leaving the organisation able to keep the record accurate: a clean, tagged baseline with a sensible numbering convention, a register or ledger structured to hold the data properly, and — where it fits — a cycle counting cadence and a stock reconciliation routine the in-house team can run. Because we are not a software vendor, the data we produce belongs to the client and is delivered to the client; the goal is an accurate, owned record, not a dependency on us. Many clients do come back — for the next full verification, a new site, or an ongoing programme — but they come back by choice, not because the engagement locked them in.

Engagements at every scale

The 4,500-project figure spans a genuinely wide range, and the experience that matters is having run the full spread rather than one size repeatedly. At the smaller end, a single professional-services office or a one-site manufacturer might need a few hundred to a few thousand assets verified, tagged and reconciled in a single mobilisation — fast, fixed-scope, and proportionate. In the middle, a retail chain, a hospital trust or a regional logistics operator might need a programme of counts across dozens of sites, scheduled around trading hours, clinical sessions or despatch windows and consolidated into one dataset. At the top end, an industrial group or a multinational might need hundreds of thousands of assets across multiple countries counted to one methodology and reconciled to a single group position, with governance and ERP integration designed in from the start. The method is the same throughout; what changes is the mobilisation, the scheduling and the reporting cadence — and knowing how to flex those without losing rigour is itself the product of thirty years.

Where we stand — and where we deliberately don’t

Experience has also taught us which roles not to occupy. CPCON is not an audit firm: we issue no opinions, which is why statutory auditors can observe and test our counts under ISA (UK) 501 without conflict. We are not a software vendor: our technology recommendations are engineered around your estate, not a licence target. And we are not a certification body: where clients pursue ISO 27001, Cyber Essentials or any other certification, the certificate is granted by their auditor or certification body — CPCON’s contribution is the verified, tagged, reconciled field evidence those assessments sample. Thirty years of delivering exactly that evidence, at scale, is the credential we offer.

Experience that is sector-specific, not generic

The same four-stage method runs everywhere, but the constraints that shape it are different in every sector, and knowing them before mobilising is itself the experience. In manufacturing the challenge is componentisation and capital allowances — a production line is not one asset but many, with materially different useful lives, and the verification has to capture it at the level the register and the tax claim need. In healthcare medical devices have to be reconciled to clinical-engineering and maintenance records, with service and safety status captured, and counted around clinical sessions and infection-control rules. In retail store and stockroom counts have to fit around trading hours and feed a shrinkage picture the business can act on. In energy and utilities the estate is dispersed, high-value and often GIS-referenced, sitting inside a regulated asset base. In financial services the focus is branch networks and IT estates and the controls evidence assurance teams expect. And in logistics and warehousing it is bin-level accuracy, WMS reconciliation and independent 3PL client stock audits. The breadth is the point: a generic count crew learns each of these on your time; we already know them.

What working with CPCON looks like

Experience changes the client’s experience, not just the result. Because we have scoped thousands of engagements, the proposal is realistic from the start — about access, downtime, cut-off and the data we need — rather than optimistic and then renegotiated on site. Because the teams are our own and the method is written down, mobilisation is quick and the standard is the same on every site. Because reconciliation is the product, the hand-over is a walkthrough of a posting-ready dataset, not a spreadsheet lobbed over the wall. And because we are independent, there is no upsell waiting at the end: the recommendation about tagging, RFID or an ongoing programme is the one the estate justifies. Clients tend to notice the difference most in the parts that usually go wrong — the count that was supposed to take a day and took three, the variance report nobody could explain, the “final” number that moved twice after sign-off. Those are the failure modes thirty years of fieldwork is designed to remove.

Outcomes our clients measure

The point of all this experience is a set of outcomes a finance or operations leader can actually measure. A cleaned register removes the depreciation, insurance and lease cost attached to assets that no longer exist, and surfaces real assets that were never capitalised so capital allowances can be claimed. A reconciled warehouse lifts pick accuracy and cuts oversells and short-ships by fixing location errors, while separating genuine shrinkage so it can be tackled at source. An evidenced count shortens and de-risks the year-end audit, because the physical-evidence work an auditor would otherwise scramble for is already done and documented. And a tagged, well-structured baseline cuts the cost and time of every subsequent count — the second count after a CPCON verification is measured in hours, not weeks. These are not abstract benefits; they are line items, and they are why organisations come back.