Short answer: there is usually a financial SOR and an operational SOR
In aerospace environments, inventory almost never has a single, universal system of record across all dimensions. Typically, the ERP system is the financial system of record for inventory value, ownership, and official stock balances, because it anchors financial reporting and cost accounting. In parallel, MES, WMS, or specialized logistics systems often act as the operational system of record for where material actually is, how it is consumed, and which serials or lots are tied to which work orders. Treating one tool as the single authoritative source for every aspect of inventory usually breaks down once you consider traceability, qualification, and integration constraints.
Why ERP is usually the financial system of record
ERP systems in aerospace are generally validated and controlled as the primary source for inventory valuation, general ledger postings, and official on-hand balances used for financial statements. Finance, supply chain, and external auditors expect ERP to be the reference for stock quantities and values at period close, even if transactional activity originates elsewhere. Changing this anchor is expensive because you must rework financial controls, segregation of duties, reconciliation procedures, and sometimes regulatory expectations for how you account for inventory. As a result, attempts to move financial inventory SOR outside ERP often stall due to qualification burden, audit impact, and the need to revalidate integrated processes end-to-end.
When MES or WMS becomes the operational system of record
On the shop floor, ERP often lacks the granularity needed for actual operations: container-level locations, work-in-process splits and merges, serial-level status, and nonconformance holds. MES or WMS typically holds the most accurate view of where specific material is and how it has been transformed, which is essential for traceability and conformity investigations. In these cases, MES or WMS effectively becomes the operational system of record for physical inventory state and genealogy, while ERP mirrors summarized balances for planning and finance. This dual model only works if interfaces are clear, reconciled regularly, and exceptions are managed under change control rather than ignored.
Traceability and configuration control considerations
Aerospace inventory is not just quantities and values; it carries configuration, airworthiness, and traceability information that may span decades. Serial numbers, batch/lot IDs, certificates of conformity, and linkage to design baselines and service bulletins may reside in multiple systems (PLM, QMS, MES, ERP). Declaring any one system as the sole SOR for “inventory” can be misleading if, for example, the serial exists in MES, the certificate in a QMS repository, and the engineering applicability in PLM. A more realistic approach is to define, for each data element (quantity, location, serial, certificate reference, status), which system is SOR and how that decision is justified, governed, and audited.
Integration and reconciliation in brownfield environments
In existing plants, inventory data is already fragmented across legacy ERP, homegrown tools, spreadsheets, and point solutions. Full replacement of these systems to create a single SOR normally fails or is heavily constrained due to downtime risk, validation cost, and the impact on ongoing contracts and certifications. Instead, most organizations succeed by tightening interfaces (e.g., MES as source for WIP moves, ERP as source for purchase receipts) and instituting structured reconciliation processes. This includes scheduled stock comparisons, clear rules for which system “wins” on discrepancies, and documented procedures to correct both master data and integration logic when mismatches are systemic rather than one-off errors.
Tradeoffs in declaring MES vs ERP as inventory SOR
Making MES the system of record for all inventory can improve operational accuracy and traceability but pushes more validation and audit expectations onto the MES platform and its integrations to ERP. This increases the qualification burden, change management overhead, and risk if MES is unavailable, because production and financial posting may both be blocked. Keeping ERP as the SOR for inventory balances simplifies financial governance but may force more complex and fragile synchronization logic from MES or WMS, especially for WIP and serialized components. The right choice is usually a split: ERP as SOR for valued stock and MES/WMS as SOR for physical location and consumption, with clearly defined interfaces and fallback procedures.
Governance model: define SOR by data element, not by system brand
A practical and auditable approach is to define system of record at the data-element level rather than arguing “ERP vs MES” in the abstract. For example, you may define ERP as SOR for on-hand quantity by part and storage location, standard cost, and ownership, while MES is SOR for container IDs, physical rack/bin positions inside the shop, and operation-level consumption records. The governance document should specify which system creates each record type, which system can update it, and how downstream systems consume or reference that data. This model is more sustainable in aerospace because it respects existing investments, reduces forced replacements, and provides a clear basis for validation and change control.
Limitations and failure modes to watch for
The dual-SOR or element-level SOR approach fails if interfaces are poorly designed, poorly monitored, or allowed to drift as processes change. Common failure modes include ERP and MES stock drifts that are only discovered at physical inventory, conflicting serial status between systems, and undocumented local tools modifying key data outside any controlled workflow. Another recurring issue is treating an integration hub or data warehouse as a hidden SOR, where corrections are made directly without updating the original authoritative systems. Avoid these patterns by enforcing that corrections always flow back to the declared SOR, and by validating not only the systems but also the interfaces and reconciliation processes themselves.