KO88 — Actual Settlement of Internal Order
KO88 is used to settle actual costs from an internal order to its receiver according to the settlement rule. It is most useful during period-end close when internal orders must transfer accumulated costs to cost centers, assets, profitability segments or other receivers. Start with the exact organizational keys and business date, then prove the result from SAP documents, balances or logs before changing configuration or reposting data.
This page explains KO88 — Actual Settlement of Internal Order — from a consultant's point of view: what it changes or displays, when it belongs in the process, which keys matter, how to prove the result, and the mistakes that create avoidable reconciliation work.
Published 19 Sept 2026· 625 words
Esta página aún no está disponible en español.
Purpose
settle actual costs from an internal order to its receiver according to the settlement rule. The transaction should be read in the context of the full accounting or logistics flow: source document, organizational assignment, posting date, configuration and resulting document all matter. A technically successful save is not enough; the output must reconcile to the intended business event.
When it is used
KO88 is typically used during period-end close when internal orders must transfer accumulated costs to cost centers, assets, profitability segments or other receivers. In project testing it is equally useful for proving configuration and master data with a controlled example. In production, narrow the scope first and capture the before-state so any posting, clearing, settlement or master-data change can be reconciled afterward.
How to use it in practice
- Check order status and settlement rule before execution.
- Review sender balance and already-settled amounts.
- Run settlement for the intended period with test/log review where applicable.
- Investigate errors by receiver and allocation rule.
- Reconcile the order balance and receiver posting afterward.
Key data objects
These are the fields and business objects that usually explain the result in KO88. Capture them in test evidence and incident handovers, because a mismatch in company code, plant, fiscal period, account or reference document is often more important than the screen message itself.
- internal order — verify the exact value, validity/date context and source of derivation.
- settlement period/fiscal year — verify the exact value, validity/date context and source of derivation.
- settlement rule — verify the exact value, validity/date context and source of derivation.
- sender balance — verify the exact value, validity/date context and source of derivation.
- receiver and settlement document — verify the exact value, validity/date context and source of derivation.
How to prove it in the data
Prove the result end to end: identify the source document/master record, inspect the transaction's proposal or status, then open the resulting accounting or logistics document and reconcile amounts, quantities and account assignments. Use document flow, line-item displays and master-data history with the same fiscal period and organizational scope. That distinguishes a true configuration defect from a selection, timing or historical-data difference.
ECC vs S/4HANA
Internal-order settlement remains part of S/4HANA Controlling, with postings flowing into the Universal Journal. On S/4HANA, Universal Journal, Business Partner, Material Ledger or Fiori may change the preferred analysis surface, but the business control behind the transaction still has to be understood and tested.
Common pitfalls and how to diagnose them
- Running settlement with an incomplete or invalid rule. Reconcile the exact document and period before making a configuration change.
- Settling the wrong period after late postings. Reconcile the exact document and period before making a configuration change.
- Treating residual order balance as an execution failure without checking rule percentages and settlement profile. Reconcile the exact document and period before making a configuration change.
Whose problem this is
Primary ownership is Finance/Controlling, with Basis or ABAP involved only when runtime, authorization or custom-code evidence points there. A useful escalation includes the business document, organizational keys, posting/valuation date, expected accounting result and the exact mismatch already proven.
Related SAP objects
Reviewed pages this object connects to in the ERPClimb knowledge graph.
Source: ERPClimb — https://erpclimb.com/sap-tcodes/ko88ERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.