Assessment Cycle Leaves a Residual Balance on the Sender

The cost centre owner or the controller closing the period reports that a cost centre still carries a balance after month end even though the assessment run finished without an error message. The complaint is usually phrased as the cost centre is not clearing to zero, or the numbers on my receiver cost centres do not match what I expected from the allocation. Sometimes it surfaces only during reconciliation, when the total on the sender pool does not equal the total picked up by the receivers in a downstream report. It is also common with a cost centre or cost element that was created partway through the fiscal year: the cycle ran cleanly for eleven months, then in the twelfth month someone notices its costs were never touched by the allocation at all.

Pull KSB1 for the sender cost centre for the affected period and sum the actual amounts by cost element. Separately list the cost element interval or group referenced by the cycle segment. Any cost element that appears in the KSB1 total but not in the segment's list is the exact amount left undistributed; that figure should match the residual balance the business is reporting to the decimal.

If the cause is a cost element group or interval missing entries, add the missing cost elements to the sender segment (or to the referenced cost element group) and re-run the cycle for the open period; this is a configuration change to the cycle, made directly in the target system rather than transported through the normal customizing pipeline, since cycles are maintained per client. If the sender rule is fixed amount or fixed percentage and the business actually wants full actual distribution, change the rule to posted amounts or variable portion; this is a functional design change and prior periods run under the old rule will not restate themselves, so a manual correction reposting may be needed to true up history. If a receiver's tracing factor is zero because a statistical key figure was never posted, that is a data correction via KB31N, not a config change, and only affects the periods where the key figure was missing. If a cost centre or cost element was never enrolled in the sender or receiver group, correct the group membership directly; group maintenance is master data, not transportable customizing. If the segment validity window is the problem, extend it in KSU2 and re-run.

The reflex fix is a manual reposting of costs (KB61) to push the leftover balance onto whichever receiver looks closest to correct, closing the gap for the current period's reporting. It does not touch the cycle segment, so the same shortfall reappears the following period. It also breaks the link between the allocation base and the amount actually charged to the receiver, since the manual posting carries no tracing factor logic behind it. If the cycle is later corrected and re-run for the same period, the original manual posting is still sitting there, and the receiver ends up double-charged.

Assessment cycle definitions belong to the controlling process owner responsible for cost centre accounting, not FI. The handover note should name the cycle and segment, the period affected, the specific cost elements or receivers excluded, whether prior periods need a corrective repost or a full re-run, and whether the group maintenance driving the sender or receiver rule was changed in only one client.