The Two-System Problem: Why EAM and ERP Never Agree
The Divergence Reality
In industrial environments, 15-30% of asset records don't match between the EAM/CMMS and ERP systems. Maintenance says you have 12,000 pieces of equipment. Accounting says you have 9,500 fixed assets. Both are wrong. The physical reality is somewhere in between — and neither system reflects it accurately.
This divergence isn't caused by negligence. It's structural. EAM systems (Maximo, SAP PM, Infor EAM) and ERP financial modules (SAP FI-AA, Oracle FA, NetSuite) are built for different audiences, maintained by different teams, and updated through different workflows:
| Dimension | EAM / CMMS | ERP (Financial) |
|---|---|---|
| Primary audience | Maintenance, reliability, operations | Accounting, finance, tax |
| What it tracks | Equipment, work orders, PM schedules, spare parts, failure history | Acquisition cost, depreciation, book value, cost center, useful life |
| When records are created | When equipment is installed or commissioned | When the invoice is processed and capitalized |
| Granularity | Individual components (motor, pump, valve) | Capitalized units (may group components) |
| Record count | Typically 1.5-3x more than ERP | Fewer records (bulk capitalizations) |
| Update trigger | Maintenance event, replacement, relocation | Journal entry, depreciation run, retirement |
The result: two parallel registers that diverge more each year. When auditors ask "what assets do we own?" — you get two different answers depending on who you ask. For a deeper look at CMMS-specific data quality issues, see our CMMS asset verification guide.
6 Common Divergence Patterns Between EAM and ERP
Pattern #1: Component vs Unit Mismatch
EAM tracks a pump station as 5 components (pump, motor, VFD, coupling, base plate). ERP capitalizes it as 1 asset. When the motor is replaced, EAM creates a new equipment record; ERP sees no change. Over time, EAM has 3x more records.
Pattern #2: Timing Gap
Maintenance installs a new compressor in March. The PO is processed in April. The invoice is capitalized in May. For 2+ months, the asset exists in EAM but not in ERP. If nobody closes the loop, it stays that way permanently.
Pattern #3: Silent Replacements
A failed valve is replaced during a shutdown. Maintenance swaps the EAM record to the new valve. Accounting never knows the old asset should be retired and the new one capitalized. ERP still carries the original asset at original cost.
Pattern #4: Bulk Capitalizations
ERP creates one asset record for a $2M project that includes 50 individual pieces of equipment. EAM has 50 separate records. Reconciliation finds 50 EAM records with no ERP match and 1 ERP record with no individual physical match.
Pattern #5: Ghost Equipment in EAM
Decommissioned equipment is physically removed but the EAM record stays active because "we might need the maintenance history." These ghost records inflate the EAM count and confuse reconciliation.
Pattern #6: Orphan Assets in ERP
ERP carries assets that were scrapped years ago but never retired — classic ghost assets. Maintenance removed the equipment and deleted the EAM record, but nobody told accounting. ERP still depreciates a non-existent asset.
Patterns #5 and #6 are the most financially impactful — ghost assets in either system inflate costs and distort reporting.
The Three-Way Match: Physical Inventory as Ground Truth
Three-Way Reconciliation Methodology
Neither the EAM nor the ERP can be trusted as the source of truth. The only reliable reference is physical reality — what actually exists on the plant floor. A three-way match compares: (1) EAM equipment list, (2) ERP asset register, and (3) independent physical inventory. Discrepancies between any two systems are resolved by the third.
| Scenario | Physical | EAM | ERP | Action |
|---|---|---|---|---|
| Full match | Yes | Yes | Yes | Verify location/description accuracy, link records |
| Physical + EAM, not ERP | Yes | Yes | No | Capitalize in ERP (uncapitalized asset) |
| Physical + ERP, not EAM | Yes | No | Yes | Create EAM equipment record, link to ERP |
| Physical only (neither system) | Yes | No | No | Create records in both systems |
| EAM only (not physical, not ERP) | No | Yes | No | Deactivate EAM record (ghost equipment) |
| ERP only (not physical, not EAM) | No | No | Yes | Retire in ERP (ghost asset — financial impact) |
| EAM + ERP, not physical | No | Yes | Yes | Investigate — may be in storage, transferred, or scrapped |
The physical inventory is the tiebreaker. If an asset exists physically, it needs records in both systems. If it doesn't exist physically, both system records should be cleaned up. For SAP-specific reconciliation workflows, see our SAP fixed asset data guide.
Step-by-Step: EAM-ERP Reconciliation Process
Extract Both Systems
Pull the complete EAM equipment list (equipment ID, description, location, status, parent hierarchy) and the ERP asset register (asset number, description, cost center, acquisition cost, net book value). Include inactive/decommissioned records from both.
Build the Crosswalk
Identify the linking field between systems — ideally a shared tag number, equipment ID, or serial number. If no common identifier exists, match by description + location. Flag records with no match candidate for manual review.
Conduct Physical Inventory
Field teams physically verify every asset within scope. Each asset is tagged (barcode or RFID), photographed, and documented with description, location, serial number, and condition. This becomes the ground truth dataset.
Run Three-Way Match
Join the three datasets (physical, EAM, ERP) using the common identifier. Classify every record into one of the 7 scenarios from the table above. Quantify each category.
Resolve Discrepancies
For each scenario: create missing records, retire ghost assets, link unmatched records, resolve component vs unit mismatches. Document every decision for audit trail. Involve both maintenance and accounting teams in dispute resolution.
Establish Ongoing Sync
Implement a governance process: changes in EAM trigger a review in ERP and vice versa. Options range from manual notification workflows to automated middleware (SAP PI/PO, MuleSoft, Boomi) that syncs asset lifecycle events between systems in real time.
Reconciliation by EAM Platform
IBM Maximo + SAP FI-AA
The most common industrial combination. Maximo equipment hierarchy (location → asset → sub-asset) maps to SAP asset master records at the capitalized-unit level. Reconciliation challenge: Maximo often has 2-3x more records than SAP because it tracks individual components. The crosswalk must map Maximo's component hierarchy to SAP's financial unit structure.
SAP PM + SAP FI-AA (Same ERP, Different Modules)
Even within SAP, the Plant Maintenance module and the Financial Accounting - Asset Accounting module can diverge. PM creates equipment records via IE01; FI-AA creates asset masters via AS01. The "Equipment to Asset" link (technical object → financial object) should connect them, but it's often incomplete — especially for legacy assets loaded during the original SAP implementation.
Infor EAM + Oracle EBS/Cloud
Common in mining and utilities. Infor EAM's hierarchical asset structure must be mapped to Oracle's asset categories and book assignments. Integration typically runs through Infor ION or Oracle's SOA layer. The challenge is maintaining sync when both systems have different administrators and update cycles.
Industries Where EAM-ERP Reconciliation Matters Most
Power Generation & Utilities
FERC-regulated utilities must maintain accurate asset registers for rate-base calculations. Discrepancies between EAM and ERP can affect regulatory filings and customer rate cases. Energy services
Oil & Gas
Upstream and midstream facilities have thousands of maintainable assets with high replacement costs. Component-level tracking in EAM vs unit-level capitalization in ERP creates the largest divergence volumes. Fixed asset services
Manufacturing
Production lines with frequent equipment upgrades and replacements create rapid divergence. Silent replacements (swapping a failed component without accounting notification) are the primary driver. Manufacturing services
Healthcare
Medical equipment is tracked in clinical engineering (EAM-like) systems and in the hospital's financial ERP. Regulatory requirements (Joint Commission, CMS) demand accurate equipment records that match financial reporting. Healthcare services
Do Your Maintenance and Accounting Teams Agree on Asset Count?
CPCON specializes in three-way reconciliation programs for industrial facilities. We bridge the gap between EAM and ERP with physical verification as the ground truth.
EAM-ERP Reconciliation FAQ
What is the difference between EAM and ERP for fixed assets?
EAM systems (Maximo, SAP PM, Infor EAM) track assets from a maintenance perspective — work orders, PM schedules, failure history. ERP systems (SAP FI-AA, Oracle FA, NetSuite) track assets from a financial perspective — cost, depreciation, book value. Both maintain asset records but serve different audiences and often contain different data for the same physical asset.
Why do EAM and ERP asset records diverge?
Divergence happens because two different teams maintain two different systems with different workflows. Maintenance creates records when equipment is installed; accounting capitalizes when invoices are processed. Equipment gets replaced in the EAM without notifying finance. Assets get retired in ERP without telling maintenance. Over time, 15-30% of records typically don't match.
How do you reconcile EAM data with ERP data?
Use a three-way match: (1) EAM equipment list, (2) ERP asset register, (3) physical inventory as ground truth. Match all three by tag number or serial number. Assets in all three = confirmed. In only one or two systems = discrepancy requiring investigation and resolution.
Which system should be the master — EAM or ERP?
Neither should be the unilateral master. EAM owns maintenance data; ERP owns financial data. A shared tag number links records across both. After reconciliation, establish governance so changes in either system trigger updates in the other.
How often should EAM and ERP data be reconciled?
Full physical reconciliation every 2-3 years, with quarterly data cross-checks between systems. Automated sync via middleware can maintain alignment in real time, but periodic physical verification is still needed.
What industries need EAM-ERP reconciliation most?
Power generation, oil & gas, manufacturing, mining, transportation, and healthcare — any industry with high-value capital equipment and active maintenance programs. These typically have 5,000-50,000+ maintainable assets alongside a financial register.
Need Help Aligning Your EAM and ERP Asset Data?
CPCON delivers three-way reconciliation programs for plants and industrial facilities. Physical inventory, RFID tagging, EAM-ERP crosswalk, and clean data files for both systems.