# Reconcile the rounded shares back to the pool

Independent rounding can make allocated totals differ from source cost. Define how residuals are handled and test the edge cases explicitly.

By Cobnex editorial. Published 2026-09-10. Updated 2026-09-11.

## Choose the calculation basis

State the source amount, currency, recipients and weighting rule. Preserve sufficient precision during calculation and apply the approved reporting rounding at the intended stage.

Do not mix currencies before conversion under the defined policy. Keep original values traceable so a reviewer can distinguish allocation differences from conversion differences.

Use numeric representations appropriate to the required precision rather than relying on uncontrolled binary floating-point arithmetic for financial totals.

## Work through an uneven split

An illustrative AUD 100 pool divided equally across three teams produces repeating fractional amounts. Rounding each independently to AUD 33.33 leaves AUD 0.01 unassigned.

Choose a deterministic residual policy, such as assigning the remaining cent according to a documented ordering or largest-remainder method suitable to the reporting requirement. The choice should be visible and repeatable.

Test negative adjustments and zero-value pools as well. A rule written only for positive charges may behave unexpectedly for credits.

## Inspect weighting failures

Handle missing usage, zero total weight and a recipient leaving the pool. Do not divide by zero or silently assign the entire amount to the first available team.

Record unresolved cases under an explicit policy. A complete-looking report is worse than a visible exception if the calculation lacks a defensible input.

Verify that recipient weights cover the intended period and do not mix current ownership with historical usage accidentally.

## Require conservation and traceability

Assert that rounded allocations plus any explicit central or unresolved amount equal the selected source pool on the same basis.

Keep the source reference, rule version and intermediate values needed to explain the result. Re-running the same inputs should produce the same allocation.

Review the reporting policy with its responsible owner when the amounts support financial decisions. The technical implementation should faithfully execute that policy, not invent one through incidental rounding behaviour.

## Sources

- [FinOps Foundation: allocation capability](https://www.finops.org/framework/capabilities/allocation/)