Freeze the allocation driver used in the monthly close

A shared-cost allocation should retain the exact source population behind its percentages. If the driver is headcount, save the approved roster and date convention. If it is floor area or usage, retain the measured population and exclusions. A link to a live system can later produce a different denominator and make the old allocation impossible to reproduce.

Record the entity or department list, measurement period, source owner, extraction time, and version. Ask the policy owner whether the driver uses period-end, average, or another approved measure. Those choices can materially change the result. The calculation should implement a stated policy rather than use whichever report was easiest to export during the close.

Confirm that each recipient's driver amount belongs within the total denominator and that excluded recipients are handled consistently. Check duplicates, missing identifiers, and changes in organizational structure. A person or location appearing in two teams can be counted twice even when the resulting percentages still sum to 100% after normalization.

In a hypothetical $30,000 cost pool allocated over 100 approved units of usage, a department with 25 units receives $7,500. If ten unrelated units enter the denominator later while the department remains at 25, the apparent allocation becomes about $6,818.18. That later recalculation does not explain the amount originally posted. Preserve the accepted 100-unit source snapshot with the $7,500 result.

Reconcile the allocated cost pool to its approved source accounts and adjustments. Then record the driver independently. A change in allocated expense can result from a larger pool, a different recipient share, or both. Separating the two inputs lets the reviewer identify which explanation is supported and prevents a cost-pool error from being hidden by adjusted percentages.

ICAEW's spreadsheet guidance recommends clear inputs, calculations, and outputs with version control. For an allocation workbook, retain the approved cost pool and driver as distinct inputs and avoid silently refreshing either after review. A corrected source should produce a new documented version and an assessment of affected postings.

If the driver owner later identifies an error, quantify the effect on each recipient and provide the original and corrected populations. Ask the accounting or reporting owner whether the correction affects the current release, a later adjustment, or comparative information. The answer depends on the reporting purpose and circumstances, not solely on whether the workbook can refresh automatically.

Keep operational refinements distinguishable from proven errors. A new measurement method can be more useful for future periods without establishing that every earlier allocation was wrong. Document the effective date and rationale for a policy change. Tax, transfer-pricing, or contractual allocations may require separate specialist assessment beyond a management-reporting method.

Create a new period input rather than overwriting the prior accepted snapshot. Reconcile added and removed recipients and inspect unexpected changes in their shares. Have the driver owner confirm the population before the accounting team posts the allocation. That separation makes responsibility for source facts and calculation review visible.

Archive the driver snapshot, cost-pool tie-out, approved calculation, journal reference, and reporting explanation together. A future reviewer should be able to reproduce the allocation using those files without access to a historical live dashboard. Where the source cannot provide a reliable period snapshot, record the limitation and agree a supportable alternative before using the allocation in released results.