Now accepting guest editorial from SAP, Oracle, Workday and ServiceNow practitioners.Pitch a guide
The Sign-Off Table

Lesson 2 of 5

Settlement and proving nothing was left behind

11 min

Listen to this lesson

0:00 / 8:10

A maintenance order is a temporary cost collector. Settlement moves its actual costs to one or more receivers named in its settlement rule, usually the cost center of the technical object. SAP's training notes that settlement usually, but not always, goes to the technical object's cost center, and that after settlement controlling sets the order to business complete.

The settlement rule

The rule is proposed from the reference object when the order is created and can be changed until settlement. Each line names a receiver (cost center, fixed asset, WBS element or another order), a percentage or amount, and a settlement type: periodic settlement moves the costs of each period, full settlement moves everything at once, typically for capital work. Which receivers and types are allowed depends on the settlement profile behind the order type, configured by controlling.

The settlement rule's structure: each distribution line names a receiver, a share and a settlement type, within what the order type's settlement profile allows.
The Sign-Off Table · thesignofftable.com/academy/sap-eam-301
Contoso caseReceiverWhy
Breakdown repair on winding machineCost center 17101107, rotor lineOrdinary maintenance expense of the line
Quarterly compressor serviceCost center of compressed air utilitiesShared service, later allocated by controlling
Rebuild that extends the winding machine's lifeFixed asset or asset under constructionCapital work, decided by Dan's team, not the planner
Repair during a plant improvement projectWBS element of the projectCosts belong to the project budget

Settlement receivers by type of work.

Running settlement

Contoso settles maintenance orders in the period-end run, collectively (for example with KO8G), in the first working days of the next period; a single order can be settled with KO88, which also offers a test run. The settlement posts a credit to the order and a debit to each receiver. Orders with status TECO can still collect late costs, such as a contractor's invoice, and the next period's run settles those too. Business completion (CLSD) comes last and requires a zero balance.

A TECO order can collect costs across periods: each period-end run settles what arrived, and business completion waits until the balance is zero and nothing more is expected.
The Sign-Off Table · thesignofftable.com/academy/sap-eam-301
  1. Test runSettlement in simulation for plant 1710's maintenance orders
  2. Review errorsMissing rules, locked receivers, closed periods
  3. Fix and runReal settlement run for the period
  4. Check balancesList of orders with a non-zero balance after settlement
  5. CloseBusiness complete eligible orders; report receivers' totals
Contoso's monthly settlement routine for maintenance orders.
The Sign-Off Table · thesignofftable.com/academy/sap-eam-301

Proving nothing was left behind

The control that matters is completeness: after settlement, the order balance should be zero for every order that had costs in the period. Three checks prove it. First, the settlement log has no errors, or every error is explained. Second, a list of maintenance orders with a remaining balance is empty, or each item has a reason (for example, an invoice that arrived after the run). Third, the total settled from maintenance orders equals the maintenance costs received by the cost centers, fixed assets and WBS elements for the period.

CheckSourceExpectedSeptember result (test)
Settlement logPeriod run, plant 1710No unexplained errors2 errors: locked cost center, missing rule; both fixed and rerun
Orders with balanceOrder list with balance filterEmpty or explained1 order: invoice after the run, settles in October
TotalsSettled total vs receivers' maintenance costsEqual$186,400 = $186,400
Three settlement completeness checks, with a sample result.
The Sign-Off Table · thesignofftable.com/academy/sap-eam-301

What would you do?

In the second mock period close, the settlement run for plant 1710 reports an error on 11 orders: the receiver cost center 17101107 is locked for secondary postings in the period. Dan's team says the lock was set deliberately for a reorganization. What should Priya's test team do?

Settlement is also where maintenance meets audit. Auditors ask whether maintenance spend was expensed or capitalized correctly, and they sample orders settled to fixed assets. Keep the reason for every capital settlement on the order, agreed by Dan's team, and test at least one capital rebuild end to end in the mock closes, from order to asset value change.

Walkthrough: settling one order with KO88

  1. Run KO88 for order 4001250, period 09, processing type automatic, with Test run set. Read the basic list: sender, receiver 17101107, amount $1,054.50.
  2. Read the detail list and the log. Any message in red (missing rule, receiver locked, period closed) stops here; fix the cause, not the symptom.
  3. Remove the test-run flag and execute. The order is credited and the cost center debited with the settlement cost element.
  4. Check the order balance (zero) and the cost center line items for 17101107 (for example in KSB1 or the Cost Centers - Actuals app): the settled amount appears once, with the order as partner object.
  5. Only now set business completion, if no more costs are expected. A late invoice after CLSD is rejected, so in Contoso's process CLSD is set by controlling at the end of the following period.

For the period-end run, Contoso schedules collective settlement (KO8G, with a selection variant for plant 1710 maintenance order types) as a background job in the closing task list, so it runs in the same sequence every month. In SAP S/4HANA Cloud Public Edition, period-end settlement is also run as a scheduled application job rather than a transaction; check the job template available in your release.

Settlement message typeTypical causeWho fixes it
No settlement ruleOrder created without a reference object cost center, or rule deletedPlanner adds the rule; controlling confirms the receiver
Receiver locked or not valid on the dateCost center locked for secondary costs, or validity endedControlling (Dan's team) decides: unlock or change receiver
Posting period not openPeriod closed in FI or CO before the runFinance reopens or reschedules the run
Profit center mismatchOrder and receiver derive different profit centersControlling checks derivation; usually intentional and allowed
Receiver type not allowedSettlement profile of the order type excludes fixed assets or WBSControlling changes the profile or the order type is wrong

Common settlement errors in a mock close and their owners.

Key points
  • Settlement moves actual costs from the order to receivers in its settlement rule.
  • Receivers include cost centers, fixed assets, WBS elements and orders; the settlement profile limits the choice.
  • Run settlement in simulation first, fix errors, then run and check balances.
  • Prove completeness: clean log, no unexplained balances, settled totals equal receivers' totals.

Check your understanding · not graded

Lesson check

  1. 1. Which statement about the settlement rule is accurate?

  2. 2. After settlement, what should the order balance be?

  3. 3. Who should decide that a rebuild is capital work settled to a fixed asset?

  4. 4. Which check proves settlement completeness at period end?