U9 cloud Cost Elements and Allocation: Design Explainable Rules
Separate material, labour and overhead into explainable elements, then give each indirect-cost pool a stable and testable allocation basis.
Learning objective
Create cost-element and allocation rules with owners, extraction logic, exception handling and review evidence.
Roles
Cost accountants, finance leads, production, engineering, purchasing, warehouse, IT, key users and consultants
Prerequisites
- Confirm organisations, periods, currencies, items, routings, resources and access ownership.
- Prepare approved masters plus representative normal, exception and reversal test data.
- Define business cut-off, interface boundaries, approvals and change control.
Completion checks
- Results trace from cost detail to business source and accountable role.
- Quantity, amount, period and status reconcile across business and finance views.
- Exceptions retain cause, approval, correction and repeatable closure evidence.
Common errors
- Masking business-source errors with ledger adjustments.
- Failing to freeze versions and periods, making recalculation irreproducible.
- Testing only the happy path without late, reversal and cross-period cases.
Thailand project note
Thai implementations should confirm Thai/English master data, THB and foreign currencies, Asia/Bangkok time, segregation of duties, approval evidence and local document retention. This tutorial covers ERP controls and reconciliation only; VAT, WHT, BOI, customs and statutory-accounting conclusions require current review by qualified Thai professionals.
Related modules
Steps
- 01
List the cost dimensions management actually uses and remove detail that cannot support a decision.
- 02
For each element, define source system, business document, responsible team, currency and refresh timing.
- 03
Collect direct material and labour directly where practical; allocate only costs that cannot be economically traced.
- 04
Choose a causal basis for each pool, such as machine hours, labour hours or accepted output.
- 05
Define treatment for zero denominators, late data and spikes; never hide them with automatic averages.
- 06
Test high-volume, low-volume and rework scenarios; compare unit cost and residual pool balances.
- 07
Have cost accounting and process owners sign the rule version and set a recurring review date.
Implementation notes
- Pilot one representative loop before expanding scope.
- Every exception needs a source document, cause, owner and closure evidence.
- Menus, fields, licences and automation depend on the current release and approved blueprint.
References
- 标准成本、实际成本与项目成本核算体系 ↗用友 U9 cloud · Accessed: 2026-08-21 · Applicable version: 官方公开能力范围；具体菜单、许可和字段以客户当前版本与批准蓝图为准
- U9 cloud 成本管理数智化 ↗用友 U9 cloud · Accessed: 2026-08-21 · Applicable version: 用于核对成本体系、成本要素、取数公式及标准实际对比的公开说明
- YonSuite 客户成功服务 ↗用友 · Accessed: 2026-08-21 · Applicable version: 用于核对业财对账、历史凭证迁移和实施服务范围