Procurement / Manufacturing is where ERP discipline either begins or breaks.
Subcontracting / Outside Processing Purchase Order 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: Subcontract operations are fully integrated in the production cost and schedule; no manual reconciliation between purchasing and production; accurate landed cost for outsourced operations improves make-vs-buy decisions.
The control flow a finance team actually needs.
Step 1
Subcontract Operation Flag On Routing Step
Step 2
Automatic PO Generation On Work Order...
Step 3
Transfer-To-Vendor Inventory...
Step 4
Vendor-Managed Inventory At...
Step 5
Receipt-Based Operation Completion Posting
The ERP surface involved.
Module
Procurement / Manufacturing
Actors
Buyer, Subcontractor, Receiving Clerk, Cost Accountant, ERP System
Tier
Tier 2
Finance area
Manufacturing & Production
Region lens
US and UK finance teams
Publication date
May 12, 2026
Subcontract operation flag on routing step; automatic PO generation on work order release or operation trigger; transfer-to-vendor inventory transaction with document; vendor-managed inventory at subcontractor location; receipt-based operation completion posting; subcontract cost element on work order cost; three-way match (PO-receipt-invoice) for subcontract invoices; multiple subcontractors per operation with cost comparison; partial receipt and partial completion; subcontract lead time in capacity planning; scrap and rework handling at subcontractor; duty/freight add-on cost capture.
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 | Subcontract operation flag on routing step | Given a work order routing with a subcontract operation and a designated vendor |
| Control 2 | automatic PO generation on work order release or operation trigger | when the operation is triggered |
| Control 3 | transfer-to-vendor inventory transaction with document | then a subcontract PO is auto-generated referencing the work_order_id, a transfer-to-vendor inventory transaction is posted, and on PO receipt the outside-processing operation is marked COMPLETE with three-way match triggered |
| Control 4 | vendor-managed inventory at subcontractor location | negative) when a subcontract PO receipt quantity exceeds the open PO line quantity then 422 RECEIPT_EXCEEDS_PO_QUANTITY. |
| Control 5 | receipt-based operation completion posting | Subcontract operations are fully integrated in the production cost and schedule; no manual reconciliation between purchasing and production; accurate landed cost for outsourced operations improves make-vs-buy decisions. |
| Control 6 | subcontract cost element on work order cost | Subcontract operations are fully integrated in the production cost and schedule; no manual reconciliation between purchasing and production; accurate landed cost for outsourced operations improves make-vs-buy decisions. |
Audit evidence is a chain, not a folder.
| Evidence layer | What should be preserved |
|---|---|
| Business event | |
| Control rules | Subcontract operation flag on routing step; automatic PO generation on work order release or operation trigger; transfer-to-vendor inventory transaction with document; vendor-managed inventory at subcontractor location; receipt-based operation completion posting; subcontract cost element on work order cost; three-way match (PO-receipt-invoice) for subcontract invoices; multiple subcontractors per operation with cost comparison; partial receipt and partial completion; subcontract lead time in capacity planning; scrap and rework handling at subcontractor; duty/freight add-on cost capture. |
| Acceptance proof | Given a work order routing with a subcontract operation and a designated vendor; when the operation is triggered; then a subcontract PO is auto-generated referencing the work_order_id, a transfer-to-vendor inventory transaction is posted, and on PO receipt the outside-processing operation is marked COMPLETE with three-way match triggered; (negative) when a subcontract PO receipt quantity exceeds the open PO line quantity then 422 RECEIPT_EXCEEDS_PO_QUANTITY. |
| 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
`subcontract_pos` { po_id: string, work_order_id: string, op_id: string, vendor_id: string, service_description: string, qty: numeric, unit_price_minor: int64, currency_code: char(3), status: enum, external_id: string }; `subcontract_receipts` { receipt_id: string, po_id: string, received_qty: numeric, received_at: timestamp, landed_cost_minor: int64, currency_code: char(3) }; (reference, product may differ).API and events
`POST /v1/subcontract-pos` { work_order_id, op_id, vendor_id, qty, unit_price_minor, currency_code } -> 201 { po_id }; `POST /v1/subcontract-pos/{id}/ship-to-vendor` -> 200 { transfer_txn_id }; `POST /v1/subcontract-pos/{id}/receive` { received_qty } -> 200 { receipt_id, three_way_match_status }; emits `subcontract.received` event; idempotent via `external_id`.State transitions
`DRAFT -> SENT -> GOODS_SHIPPED -> RECEIVED -> INVOICED -> CLOSED`; terminal `CANCELLED`; guard: three-way match must pass before PO moves to CLOSED; CANCELLED blocks receipt posting.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.