An outsourced processing control system needs to do more than digitize purchase orders. When a manufacturer sends its own material or work in progress to a subcontractor, ownership and physical custody separate. The system must show what was sent, what the partner acknowledged, where each lot is, how far processing has progressed, what returned, what inspection released, and what processing charge can be posted. This guide turns that requirement into an event ledger, a practical rollout, and RFP, FAT and SAT tests for a Thailand-based factory.
Define the boundary before selecting an outsourced processing system
The focus here is processing performed outside the factory, particularly when company-owned material crosses the subcontractor boundary. A supplier that sources and sells a finished component creates a different accounting and custody pattern. Classify each transaction by material ownership, chargeable or free issue, contractual scrap treatment, acceptance terms and accounting policy before configuring a common workflow. Specific BOI privileges or procedures depend on the approved project and conditions; consult the BOI FAQ and the project approval rather than assuming one rule covers all subcontracting.
The existing articles on purchasing management, job-order or seiban control and work in progress cover the wider order and factory context. This article concentrates on the handoff of company-owned work to an external processor and its return as inspected output. A purchase order balance alone cannot explain the physical state. If 100 blanks are supplied and the subcontractor reports 92 good pieces, three rejected pieces and five still in process, recording only “92 received” hides the other eight.
Make the supplied-material event ledger the source of truth
Keep the outsourced instruction as a plan, and record dispatch, carrier handoff, subcontractor acknowledgement, processing milestones, return dispatch, factory receipt, inspection and disposition as separate events. Store the event time, entry time, actor, evidence and confirmation status. Do not overwrite the original dispatch quantity to make a later balance appear correct. Use an instruction ID and line ID connected to item, revision, job order, operation, subcontractor, issue type, lot or serial, quantity and unit. Choose lot or serial granularity according to the product risk; a universal serial requirement can add work without value. Preserve the version of unit-conversion and rounding rules so that a later master-data change does not rewrite history.
The time material leaves the plant and the time the partner accepts it are different. A shortage or damage claim at receipt should create a discrepancy event with an owner and deadline, while preserving both parties’ observations. A processing-complete message is also different from a physical return. A portal, mobile screen, CSV or EDI message may all feed the same internal event model, provided the original message and mapping are retained. NIST’s 2026 manufacturing traceability meta-framework discusses linking time-ordered data across organizations and selective disclosure. It offers useful design principles; it is not a mandatory software specification for factories. NIST’s manufacturing-data trustworthiness recommendations have a defined technical scope, so their process coverage should not be generalized to every subcontracting case.
Reconcile quantity by location and status
Define a quantity identity for each instruction line: accepted input at the subcontractor must be accounted for as partner stock or work in process, returned goods, approved scrap, authorized transfers, and any rework returned to the partner. The detailed equation changes when lots split, merge or transform. The invariant is that no unexplained quantity disappears between factory, carrier, partner and inspection hold.
For an illustrative case, dispatch 100 blanks; the partner acknowledges 98 and two are under transit-discrepancy investigation. The partner returns 60, the factory receives 58, and two remain in transit. Partner stock is 38; transit and disputed quantities are shown separately. If 56 of the 58 received pieces pass inspection and two remain on hold, the partner balance is still 38. These are invented test quantities, not yield benchmarks. For a cutting operation that turns one bar into four pieces, retain input-output lineage and compare appropriate units or mass. Do not display a false shortage of three units. At month end, reconcile the partner’s balance confirmation to the event ledger and correct mistakes with reasoned reversal or adjustment events, not silent deletion.
Track outsourced-process progress at verifiable decision points
A single “60% complete” field does not tell the planner whether good stock will be available on the customer date. A workable minimum state model is instruction sent, material dispatched, partner received, started, processing completed, returned, factory received, inspection decided and closed, with hold, rework and loss investigation as exceptions. Keep forecast dates separate from actual timestamps and provisional phone reports separate from confirmed events. Ask each partner to report the milestones that matter to the process rather than every machine action. Heat treatment may need load, cycle completion and test result; surface treatment may need pre-treatment, coating, thickness check and ready-to-return. A statement that work is “on schedule” is not evidence of completed processing.
Alerting should use downstream need date, transit time, inspection lead time and available alternatives as well as the partner’s promised return date. A one-day partner delay may have no customer effect; an on-time return held in inspection may stop the next operation. Display expected processing completion, expected factory receipt and expected date of usable accepted stock separately. Store timestamps with time zones when parties are in different locations. GS1 EPCIS 2.0.1 offers an event-sharing vocabulary that can inform integration, but a small factory need not implement EPCIS simply to gain control. Shared identifiers, quantities, locations, times and meanings come first.
Separate physical receipt from inspection release
Returned work should enter a receipt or quarantine location before it becomes available to the next operation. Record package and piece counts, item, lot, documents and visible damage at physical receipt. Then record pass, conditional acceptance, hold, rework, return or approved scrap with authorized decision makers. Sampling rules, inspection characteristics, instrument records and whether partner test certificates suffice depend on product and customer requirements. Link inspection evidence to instruction, shipment, input lot, output lot and drawing revision. A reworked item must retain its original nonconformity and return history so that the system does not receive it twice.
The ISO/IAF Auditing Practices Group’s January 2016 external-provider auditing paper discusses procurement and supply-chain audits in the context of ISO 9001:2015. Its 2023 QMS-scope guidance also predates the new edition. ISO states that ISO 9001:2026, published on 16 September 2026, is the current edition. Use the older APG papers as historical prompts for an audit discussion, not as an interpretation of the 2026 clauses. They do not prescribe a particular software product. Confirm the applicable edition, certification transition, customer contract and audit scope with the quality team and certification body.
Post outsourced processing cost against the agreed basis
State whether the processing unit price applies to input pieces, completed pieces, received pieces or accepted pieces. Keep setup fees, minimum charges, rush work, transport, tooling, currency and taxes as distinct terms. A contract decides who pays for rework, damaged supplied material and scrap; the system should not infer fault and deduct a charge automatically. Reconcile outsourced instruction, return and receipt evidence, inspection outcome, and supplier invoice. If 100 are supplied, 92 returned, 90 accepted and two held, a payable quantity of 90, 92 or 100 could each be appropriate under a different contract. Keep the selected rule and approval visible while continuing to show the eight outstanding physical pieces. These figures are an example, not an industry defect rate.
Post to ERP only when the chosen accounting and period criteria are met. The event ledger describes physical and quality facts; journal entries reflect accounting policy. Test receipts across month end, later corrections, accruals, foreign exchange, invoice disputes and held pieces. Do not confuse a processing-cost estimate with a finalized payable. Preserve a path from each journal or invoice line back to the accepted quantity and evidence.
Integrate with ERP and MES without duplicating decisions
One practical division is ERP for orders, cost and accounting, MES for in-house operation execution, WMS for internal warehouse moves, and the outsourced-process ledger for custody, partner progress, returns and inspection transitions. A particular product may combine these roles. What matters is that one event is not independently finalized in two systems. A received but held lot may appear in inventory while remaining unavailable for MES consumption. Synchronize status meanings and effective times, not just document numbers.
Give each partner only the current approved drawing revision, relevant lot and due date, inspection conditions and change notices. Separate rights to view, update progress, upload evidence and report discrepancies; remove access when the relationship ends. For email or CSV import, retain the source file and mapping version. For API transfer, use an event ID so retrying after a communication failure cannot duplicate stock. Address partner item-code mapping, multilingual item names, time zones and versioned drawing applicability in the RFP. An emergency engineering change needs a documented approval path rather than an uncontrolled file replacement.
Build an RFP from real exceptions, then prove it in FAT and SAT
Before issuing the RFP, test traceability in both directions. From a rejected output lot, identify the supplied input lots, subcontractor operation, process or test evidence, and affected customer shipments. From a suspect input lot or outside operation, list all affected finished goods and work still at the partner. If several lots share one instruction, the instruction number alone is too coarse. Choose identification granularity that can survive actual processing; for a shared treatment bath, link every input lot to the batch. Do not claim serial-level traceability where parts cannot be individually identified. Keep structured search fields alongside the original certificate or drawing so that investigations do not require opening every attachment.
Balance data quality with shop-floor workload. Scan the existing warehouse label at dispatch, let the partner confirm receipt or report only a discrepancy, use the same identifier at return, and verify the physical item at factory receipt. A scan alone does not prove the label was on the correct box. Include relabelling, mixed containers and manual entry in SAT. Mark phone reports and extracted email data as provisional until a person confirms them. Where the partner uses photos, retain the image as supporting evidence and capture lot, quantity and time as searchable fields. Failed extraction should enter a review queue rather than silently becoming a successful receipt.
Review improvement measures against real operations: unexplained quantities, unconfirmed partner balances, overdue milestones, inspection-hold age and invoice exceptions. A rise in reported discrepancies may mean previously hidden problems are now visible, while a zero count may mean the partner has not acknowledged any receipt. Define each metric’s denominator and period. Assign handoffs across purchasing, warehouse, planning, quality and finance; an unresolved discrepancy needs an owner, deadline, known facts and an escalation path, not an automatic assignment of supplier fault. Version changes to item masters, unit conversions, process routes, partner accounts and drawing applicability so that an unfinished instruction does not silently inherit new rules.
Use real historical cases to define requirements: partial issue and receipt, dispatch/partner quantity discrepancy, split and merged lots, late return, inspection hold, rework, scrap, drawing change and month-end cutover. Ask vendors to reproduce an illustrative ledger: 100 dispatched, 98 acknowledged, two under investigation, 60 returned, 58 received, two still in transit, 56 passed and two held. Inspect both event history and current balances. Request export of event ID, source ID, item, job, lot, quantity, unit, event and entry timestamps, correction reference, actor and evidence URL. Verify role-based partner separation, backup and restore, and a usable manual process during an outage.
Compare proposals on the same scope: licences, partner accounts, labels and scanners, ERP connection, migration, training, support, data growth and exit terms. No universal price or return-on-investment figure can be derived from this list. Start with a high-variance subcontractor or item family, establish opening balances, and extend to more partners after the basic dispatch, acknowledgement, return, receipt and inspection events work. Track unexplained quantity, unmatched partner balances, inspection-hold age, time to detect schedule risk and invoice exceptions against a measured baseline.
In FAT, verify values and histories after normal and exception scenarios, including duplicate message replay and reversal. In SAT, test the actual warehouse labels, Thai-language item names, partner communication, inspection stations, ERP/MES connection and approval cover during absences. Run the old ledger in parallel for a defined period, reconcile discrepancies, then authorize the cutover. Do not manufacture missing historical events to make migration look complete. Agree FAT/SAT acceptance criteria with the supplier before testing.
Prepare a current-workflow evidence sheet before implementation
Before explaining requirements to vendors, select several completed or ongoing subcontracting cases and place their evidence in time order from material issue through invoice. Include a normal full return plus partial returns, partner receipt discrepancies, inspection holds, rework and transactions crossing month end. For each case, collect the outsourced instruction, warehouse dispatch record, partner acknowledgement, progress message, return note, factory receipt, inspection decision and invoice. Check whether every record points to the same lot and unit. Existing documents alone are insufficient if their identifiers cannot be reconciled. Decide which identifiers must be captured and investigate why a process step currently cannot capture them.
Create an approval-decision matrix by role. Specify when the warehouse calls goods “dispatched,” who accepts a partner’s quantity discrepancy, when planning reflects a delay in the customer promise, who may release held pieces in quality, and which state allows finance to post processing cost. For each transition, record the condition, evidence, approver and substitute approver during absence. Two departments can use the word “complete” for different facts; agreeing on the word without agreeing on its transition rule will make the new system ambiguous.
Set a definite date for retiring paper or spreadsheet ledgers. During parallel running, declare which ledger is authoritative for each day and keep approval of reconciled differences. If staff must enter the same facts twice for too long, they will stop trusting the slower record. For every open instruction at migration, establish approved opening balances separated into partner stock, transit, inspection hold and rework. Keep unexplained quantities in an investigation category rather than hiding them inside “partner stock.” Weak legacy data are not a software fault, but their treatment determines trust after launch.
Observe the partner’s physical operation too. If it stores the same item for several customers, can it segregate or identify stock by customer? In a hot process where a part label cannot survive, how are the container, rack and traveller linked before and after processing? For a night-shift or weekend return, who acknowledges the physical receipt and which event is formally confirmed on the next working day? Decide how evidence follows actual material flow before increasing the number of input fields. This evidence sheet turns an RFP from a feature list into a set of behaviours that can be demonstrated on site.
Questions frequently asked about outsourced processing control
Is outsourced processing control the same as purchasing management?
The workflows overlap, but supplied-material custody, partner work-in-process, return inspection, residual material and processing-charge basis need explicit coverage. A purchasing product that handles these cases may be sufficient; assess the events and reconciliation rather than the product label.
Does supplied-material control cover only free issue?
No. Free and chargeable issue can differ in title, valuation, billing and residual return. Configure the workflow according to the contract and seek project-specific tax, customs or BOI advice where relevant.
Must the subcontractor report progress every day?
Choose reporting points according to process and delivery risk. Confirming start, a critical operation, test result, ready-to-return and delay forecast may be more valuable than a daily percentage.
What happens when received pieces fail inspection?
Keep them unavailable for use, record the nonconformity by lot and quantity, and link the authorized rework, return, concession or scrap decision to the original instruction. Preserve the history when pieces return for reinspection.
Can processing cost be posted automatically?
Calculation can be automated when the contract defines its quantity basis and exceptions. Held goods, rework, setup fees and disputed loss may still need approval. Show the difference between physical, accepted and invoiced quantities.
Are EPCIS or a particular international standard mandatory for every implementation?
The cited NIST and GS1 documents are design references and do not impose one implementation on every factory. Check the buyer’s contract, applicable standards and regulation, transaction volume and partners’ integration capability before choosing a format.
Conclusion
Implement outsourced processing control around a verifiable event ledger from supplied material dispatch to inspected return. Separate planned from actual events, receipt from usability, and custody balances from cost posting. Define the contract-specific quantity equation first, then use real exception cases to select a product and test FAT and SAT.
TOMAS TECH can help a Thailand factory map supplied-material dispatch, subcontractor balances, inspection holds and ERP/MES interfaces before a product decision is made. If that is your current stage, contact us to review the workflow and existing records.
