Name the owner of the shared-cost rule

Separate data and policy ownership

Assign responsibility for source ingestion, mapping quality, shared-cost rules and published reporting. These may belong to different teams.

A pipeline owner can fix a duplicate charge. A finance or platform policy owner may need to decide whether a shared service remains central or is allocated to workloads.

Document that distinction so a disputed amount reaches the person able to resolve it.

Hand over one complete example

Trace a source charge through ownership mapping, shared calculation, currency treatment if applicable and the final report. Include rule versions and the reconciliation result.

Use a synthetic example that includes an unresolved item or rounded residual, not only the easiest direct charge.

The receiving team should be able to reproduce the result and explain why each transformation exists.

Define the correction process

Show how teams report an incorrect owner or challenge a calculation. Record the evidence required and how a corrected report is versioned.

Keep historical policy changes discoverable. A team reorganisation should not make past reports impossible to explain.

Assign a regular review of unresolved cost and obsolete mappings. Missing ownership tends to accumulate when no one has a clear action after the report runs.

Verify operational continuity

Have another operator ingest a safe fixture, resolve a missing mapping and publish a reconciled test report. Observe where the process relies on personal files or undocumented spreadsheet edits.

Move those dependencies into the maintained workflow and protect access according to the data involved.

The handover is complete when the organisation can reproduce the numbers, explain the policy and correct mistakes without depending on the original author. A scheduled report that nobody can defend is not a finished cost-allocation service.

Reproduce a shared charge and its missing-data case

Use a synthetic shared charge of AUD 900 during handover: AUD 300 split equally across three teams and AUD 600 distributed by agreed usage shares of 50, 30 and 20 percent. The resulting allocations are AUD 400, AUD 280 and AUD 220. Ask the receiving owner to reproduce the result and identify the source of the usage shares.

Then remove one team's usage data. The documented missing-data rule should determine whether allocation waits or uses an approved fallback, rather than quietly spreading its cost across the other teams.