U9cloudSupply ChainBeginnerContent quality · 94/100

U9 cloud Procurement: Control Requisition to Receipt

Build an auditable minimum procurement loop across demand, approval, sourcing, purchase order, receipt and exception closure.

Learning objective

Complete a traceable and reconcilable requisition-to-receipt flow in test, including exceptions.

Roles

Requesters, purchasing, warehouse, quality, finance, IT and implementation consultants

Prerequisites

Govern supplier and item masters.
Confirm purchasing access, approval matrix and receipt-inspection boundary.

Completion checks

Requisition, order, receipt and return are bidirectionally traceable by source document.
Quantity, price, stock status and payable results reconcile.

Common errors

Creating duplicate requisitions without a demand source.
Resolving receipt variances offline without system evidence.

Thailand project note

For Thailand, confirm Thai/English business and item masters, THB and foreign currencies, Asia/Bangkok time, segregation of duties, electronic records and local document retention. VAT, WHT, customs, BOI, statutory accounting, product compliance and occupational-safety settings require current review by qualified Thai professionals; this tutorial is not legal or tax advice.

Steps

01Govern supplier, item, unit, lead-time, currency and tax attributes with named data owners.

02Create requisitions from forecast, MRP or approved manual demand, retaining source, quantity, need date and cost object.

03Configure tiered approval for requisitions, price variance, excess quantity and delivery changes; prohibit offline price edits.

04Retain invitations, quotations, comparison rationale and award approval before creating purchase orders when sourcing is required.

05Receive against the order and record lot, quantity, location, inspection status and source document; route variances to exception handling.

06Test short and excess receipt, rejection, return, cancellation and order amendment; reconcile inventory and payable-interface effects.

07Operate an open-order and exception board by supplier, buyer, overdue days and closure owner.

01
Govern supplier, item, unit, lead-time, currency and tax attributes with named data owners.
02
Create requisitions from forecast, MRP or approved manual demand, retaining source, quantity, need date and cost object.
03
Configure tiered approval for requisitions, price variance, excess quantity and delivery changes; prohibit offline price edits.
04
Retain invitations, quotations, comparison rationale and award approval before creating purchase orders when sourcing is required.
05
Receive against the order and record lot, quantity, location, inspection status and source document; route variances to exception handling.
06
Test short and excess receipt, rejection, return, cancellation and order amendment; reconcile inventory and payable-interface effects.
07
Operate an open-order and exception board by supplier, buyer, overdue days and closure owner.

Implementation notes

Pilot one supplier and one material class.
Retain versions for every price, quantity and date change.

References

构建灵活高效的计划模式，U9 cloud让电子行业企业底气十足 ↗用友 U9 cloud · Accessed: 2026-08-21 · Applicable version: 官方公开场景说明；具体字段、菜单与算法参数以客户当前版本和批准蓝图为准