U9cloudCostingIntermediateContent quality · 94/100

U9 cloud Shared-Expense Allocation: Explainable Cost-Centre Rules

Allocate shared services and common expenses to cost centres using verifiable drivers, with version and balance checks.

共享费用分摊 / Shared Expense Allocation18 minUpdated 2026-08-21
01

Learning objective

Create a complete flow for source, pool, basis, receiver and review evidence.

Roles

Finance, process owners, key users, IT, consultants and internal audit

Prerequisites

  • Confirm entity, period, currency, masters and access.
  • Prepare approved normal and exception data.
  • Define approvals, cut-off and change control.

Completion checks

  • Results trace to source and accountable role.
  • Quantity, amount, period and status are reviewable.
  • Exceptions retain cause, approval, action and closure evidence.

Common errors

  • Overwriting history and losing traceability.
  • No segregation of duties.
  • Testing only normal flow.

Thailand project note

Thai implementations should confirm Thai/English masters, THB and foreign currencies, Asia/Bangkok time, segregation, approvals and local retention. This covers ERP management controls only; VAT, WHT, BOI, customs and statutory-accounting conclusions require qualified Thai professional review.

Related modules

finance-governancemanagement-accountinginternal-control

03

Steps

01List shared pools with source account, organisation, currency and owner.
02Post directly attributable cost first; only shared portions enter pools.
03Choose causal drivers such as headcount, area, labour hours or transaction volume.
04Freeze driver date and rule version, handling zero denominator and missing data.
05Simulate and reconcile pre-allocation total, detail and residual balance.
06Obtain provider, receiver and finance approval before posting and periodically review rules.
  1. 01

    List shared pools with source account, organisation, currency and owner.

  2. 02

    Post directly attributable cost first; only shared portions enter pools.

  3. 03

    Choose causal drivers such as headcount, area, labour hours or transaction volume.

  4. 04

    Freeze driver date and rule version, handling zero denominator and missing data.

  5. 05

    Simulate and reconcile pre-allocation total, detail and residual balance.

  6. 06

    Obtain provider, receiver and finance approval before posting and periodically review rules.

04

Implementation notes

  • Pilot one entity and representative period.
  • Exceptions require source, owner and closure evidence.
  • Menus and fields depend on current release and blueprint.
05

References