Product Engineering / Change Management is where ERP discipline either begins or breaks.
Engineering Change Order (ECO) Management looks operational from far away. In a real finance team, it is a chain of assertions: the right actor started the work, the required records existed, the control policy was applied, the state change was preserved, and the outcome can be explained later without rebuilding the transaction from emails and spreadsheets.
The expected business outcome is specific: BOM changes are controlled, traceable, and implemented consistently across all production orders; quality risks from unauthorized substitutions are eliminated; material dispositions are formally decided rather than ad hoc.
The control flow a finance team actually needs.
Step 1
ECO Document With Affected BOMs, Items,...
Step 2
Red-Line Markup Of BOM Diff
Step 3
Multi-Stage Approval Workflow With Role...
Step 4
Effectivity By Date, Unit Number, Or...
Step 5
Disposition Workflow For Non-Conforming...
The ERP surface involved.
Module
Product Engineering / Change Management
Actors
Design Engineer, Manufacturing Engineer, Quality Engineer, Change Control Board, ERP System
Tier
Tier 2
Finance area
Manufacturing & Production
Region lens
US and UK finance teams
Publication date
May 10, 2026
ECO document with affected BOMs, items, drawings, and reason; red-line markup of BOM diff; multi-stage approval workflow with role assignment; effectivity by date, unit number, or lot number; disposition workflow for non-conforming inventory; automatic BOM version increment on ECO approval; ECO impact analysis report (open work orders, open POs, on-hand inventory affected); ECO implementation tracking; cost impact estimate before approval; integration with PLM systems via API; ECO number with prefix format.
US and UK teams have different compliance hooks, but the same control problem.
US teams usually care about clean evidence for audit support, vendor records, payment controls, tax reporting, and management review. UK teams usually care about VAT-ready records, approval evidence, digital-record discipline, and traceable postings. The country-specific details differ, but the operating pattern is the same: the ERP needs controlled records, explicit ownership, defensible state changes, and evidence that survives beyond the person who completed the task.
The control matrix.
| Control area | Requirement | Acceptance proof |
|---|---|---|
| Control 1 | ECO document with affected BOMs, items, drawings, and reason | Given an active BOM and an ECO referencing the affected BOM with old and new component, effective_date, and disposition |
| Control 2 | red-line markup of BOM diff | when the change control board approves the ECO |
| Control 3 | multi-stage approval workflow with role assignment | then a new BOM version is auto-created with the substitution at effective_date, prior version is ARCHIVED, and procurement is notified |
| Control 4 | effectivity by date, unit number, or lot number | negative) when an ECO is submitted without a completed impact assessment then 422 IMPACT_ASSESSMENT_REQUIRED. |
| Control 5 | disposition workflow for non-conforming inventory | BOM changes are controlled, traceable, and implemented consistently across all production orders; quality risks from unauthorized substitutions are eliminated; material dispositions are formally decided rather than ad hoc. |
| Control 6 | automatic BOM version increment on ECO approval | BOM changes are controlled, traceable, and implemented consistently across all production orders; quality risks from unauthorized substitutions are eliminated; material dispositions are formally decided rather than ad hoc. |
Audit evidence is a chain, not a folder.
| Evidence layer | What should be preserved |
|---|---|
| Business event | A design engineer initiates an ECO to replace a component in an existing BOM due to a supplier discontinuation. The ECO documents the affected BOM(s), old and new component, effective date (by date or serial/lot number), and disposition of existing inventory (use as-is, rework, scrap). The ECO routes through an approval workflow: manufacturing engineering reviews for routability, quality engineering reviews for inspection impact, and the change control board provides final sign-off. Upon approval, the system automatically creates a new BOM version with the substitution applied at the effective date, archives the prior version, and triggers notifications to procurement to order the replacement component. In-progress work orders below the effective serial number continue on the old BOM; new releases use the revised BOM. |
| Control rules | ECO document with affected BOMs, items, drawings, and reason; red-line markup of BOM diff; multi-stage approval workflow with role assignment; effectivity by date, unit number, or lot number; disposition workflow for non-conforming inventory; automatic BOM version increment on ECO approval; ECO impact analysis report (open work orders, open POs, on-hand inventory affected); ECO implementation tracking; cost impact estimate before approval; integration with PLM systems via API; ECO number with prefix format. |
| Acceptance proof | Given an active BOM and an ECO referencing the affected BOM with old and new component, effective_date, and disposition; when the change control board approves the ECO; then a new BOM version is auto-created with the substitution at effective_date, prior version is ARCHIVED, and procurement is notified; (negative) when an ECO is submitted without a completed impact assessment then 422 IMPACT_ASSESSMENT_REQUIRED. |
| Data record | |
| System event | |
| Lifecycle state | |
The useful version of this workflow is not only fast. It is inspectable. A controller, auditor, or operator should be able to move from source event to system record to state transition to final business outcome without guessing.
Implementation contracts.
Reference data model
`ecos` { eco_id: string, affected_bom_id: string, old_component_id: string, new_component_id: string, effectivity_type: enum, effective_date: date, disposition: enum, status: enum, external_id: string }; `eco_approvals` { approval_id: string, eco_id: string, role: string, approved_at: timestamp, comments: string }; (reference, product may differ).API and events
`POST /v1/ecos` { affected_bom_id, old_component_id, new_component_id, effectivity_type, effective_date } -> 201 { eco_id, status: DRAFT }; `POST /v1/ecos/{id}/submit` -> 200 { status: PENDING_APPROVAL }; `POST /v1/ecos/{id}/approve` { role } -> 200; emits `eco.approved`, `bom.version_created` events; idempotent via `external_id`.State transitions
`DRAFT -> PENDING_APPROVAL -> APPROVED -> IMPLEMENTED`; terminal `REJECTED`; guard: all configured approval roles must sign before APPROVED; IMPLEMENTED triggers BOM version increment and archive of prior version.Common implementation traps.
Treating the workflow as data entry
If the ERP only stores the final record, the team loses the decision trail that explains how the record became valid.
Hiding exception logic
Exceptions need owners, reason codes, and time stamps. A vague pending state is not a control.
Posting without recovery design
Retries, duplicate submissions, and partial failures must be explicit so the system does not create inconsistent records.
Skipping evidence design
A workflow that cannot produce evidence on demand will eventually push finance teams back into manual screenshots and spreadsheets.
Where Rivane fits.
Rivane is built for finance workflows where automation must stay tied to source documents, approvals, state transitions, ledger impact, reporting, and audit evidence. Use this guide as a checklist for evaluating whether an ERP workflow is merely digitized or actually controlled.
References and source basis.
These sources provide the standards, regulatory, or government context around the flow. They are included so the guide is useful to finance operators, auditors, and implementation teams, not only buyers reading software copy.