U9cloud Subcontracting: Issue, Receipt, Reconciliation and Cost
Run this manufacturing scenario through governed masters, end-to-end documents and owned exceptions while balancing delivery, inventory, quality and cost.
Learning objective
Build an executable, reconcilable and auditable standard process from business demand to inventory and finance.
Roles
Planning, sales, purchasing, production, warehouse, quality, cost accounting, data owners and consultants.
Prerequisites
- Approve blueprint, organisation scope, accounting policy and approval matrix.
- Clean item, BOM/routing, customer/supplier, warehouse, unit and currency masters.
- Test access, interfaces, exceptions and rollback; qualified Thai owners confirm local rules.
Completion checks
- A result traces to source demand, approved version, execution documents, inventory/quality status and finance.
- Quantity, status, date and value reconcile; variance has reason, owner, approval and closure evidence.
- Positive and unauthorised tests pass; unapproved users cannot reprice, substitute, unblock, release or post.
Common errors
- Going live before master-data governance distorts plan, inventory and cost.
- Changing commitments in sheets or chat without updating the ERP version and status.
- Treating ERP calculation or configuration as Thai tax, customs, quality or legal compliance.
Thailand project note
For Thailand confirm Thai/English masters, THB and foreign currency, Asia/Bangkok timezone, tax documents and segregation of duties. BOI, customs, VAT, withholding tax, recall and contracts require qualified local review; this is not legal or tax advice.
Related modules
Steps
- 01
Confirm organisation, item, supplier, warehouse, unit, currency and ownership masters, then freeze the run baseline.
- 02
Enter approved source demand with order, version, due date, quantity and evidence; prevent duplicate demand.
- 03
Check availability, capacity, quality status and value, and route gaps into an owned exception queue.
- 04
Create execution documents under approved rules; sensitive pricing, substitution, unblock and posting require access and approval.
- 05
Capture actual execution with lot, serial or linkage ID and retain source, time, operator and change audit.
- 06
Compare planned and actual quantity, date, status and value; explain variances and complete quality or finance treatment.
- 07
Business and finance accept the result together; publish it and track open item, owner and deadline on the operating board.
Implementation notes
- Pilot one plant, one product family and complete exception scenarios.
- Give every critical rule a version, effective date, owner, approval evidence and rollback.
- Menus, automation, mobile capture and interfaces depend on licence, release and blueprint.
References
- U9 cloud IC 芯片行业数智化解决方案 ↗用友官方网站 · Accessed: 2026-08-20 · Applicable version: 官方公开能力范围；具体菜单、许可、自动化与接口以客户版本和项目蓝图为准