Internal Order Settlement Rule Missing At Period Close

Controlling reports that the order balance did not clear at month end. The language is usually something like: 'this order still shows an open balance after the settlement run', 'the actual costs never landed on the receiving cost center', 'the asset under construction never picked up the capitalized spend', or 'the settlement run finished with errors and nothing actually posted'. Sometimes the first sign is a profit center or divisional P&L report where costs are sitting on the order object itself instead of the expected receiver, distorting the reported result for that area. On capital projects, a project manager may notice the WBS or internal order still carries expense that finance already reported as complete, and asks why the fixed asset register has not picked it up.

Ranked from most to least common in practice.

Work from the order outward, not from the settlement run backward.

Pull the CO actual line item report (KOB1) for the order, or a cost center actual line item comparison, filtered to the closing period, and show the order balance is nonzero after the settlement run completed. Cross-check against the settlement run log for that period, which lists every order it attempted and the error text for each failure, giving an auditable list of exactly which orders lacked a valid rule versus which failed for status or profile reasons.

Branch on what the check sequence found. If the rule is simply missing or incomplete, this is a master data fix: add or correct the distribution rule directly on the order in KO02, or for a batch of orders use mass settlement rule maintenance rather than opening each order individually. If the rule exists but the validity period is wrong, extend or add a new rule line for the current period without deleting the historical one, since deleting can affect prior-period reversals. If the order status is blocking settlement, release the order or adjust the user status before settling, then re-run. If the root cause is the settlement profile or allocation structure not permitting the required receiver category, that is a configuration change owned by the CO configuration team and must go through transport; do not attempt to work around it by changing the receiver type on individual orders, since the same block will recur on every new order of that type until the profile is corrected.

The reflex fix is to write off the order balance with a manual FI journal entry, or to force the settlement run through by reassigning the receiver to whatever category the system will accept, regardless of whether that is the correct cost object. Both close the period cleanly on paper but leave the actual root cause, whether a missing rule template or a profile restriction, untouched, so the same order or the next one of that type produces the identical unsettled balance next month, and the manual journal entry now has to be reversed once the real settlement eventually runs.

Order master data, including the settlement rule, is owned by the controlling team or the project team that created the order. Settlement profile and allocation structure configuration is owned by the CO configuration team and moves through transport. The handover note should list the affected order numbers, the specific defect found in the settlement log, the period impacted, and whether the fix applied was a master data correction or a configuration change awaiting transport.