# SAP PM Maintenance Order Settlement Checklist > Source: https://netray.co/tools/sap-pm-order-settlement-checklist > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer A step-by-step checklist for technically completing and settling SAP maintenance orders without period-end surprises. ## Category sap ## Erp SAP ECC / S/4HANA ## Audience - SAP PM consultant - Cost accountant - Maintenance planner ## Tool **Kind:** checklist **Groups:** #### Before technical completion **Items:** **Text:** All planned operations are confirmed or deliberately cancelled **Critical:** true Final confirmation flag set on each completed operation Actual work hours reviewed against the planned work for outliers Unused component reservations deleted or issued **Text:** External services have entered service sheets or goods receipts **Critical:** true Linked notification has breakdown and malfunction dates filled in #### Settlement rule and receivers **Items:** **Text:** Settlement rule exists on the order **Critical:** true **Text:** Receiver is valid for the order type settlement profile **Critical:** true Receiver cost center or asset is open for posting in the period Capital work is split from expense work according to policy Distribution percentages total 100 percent Settlement type matches the receiver (full or periodic) #### Costs and postings **Items:** **Text:** All goods issues for the order are posted **Critical:** true Purchase orders and invoices for the order are matched or accrued Internal activity allocation has run for the period Overhead is calculated if your costing sheet requires it No unexpected cost on the order for wrong account assignment Costs reviewed against the estimate and variances explained #### Technical completion **Items:** Cause, damage and activity codes completed on the notification Order text states what was found and what was done Equipment or functional location counter readings updated where needed **Text:** Order set to TECO by the planner or supervisor **Critical:** true Linked notification completed with the required end date #### Settlement run **Items:** **Text:** Test run executed in KO88 or KO8G before the update run **Critical:** true Error log reviewed and each error assigned an owner **Text:** Update run executed within the open posting period **Critical:** true Orders with errors corrected and re-run Settlement document numbers retained for audit Run date and user recorded for the close file #### After settlement **Items:** **Text:** Order balance is zero after settlement **Critical:** true Receiver cost center or asset shows the expected posting Business completion or close status set when policy requires it Open and unsettled order report cleared for the period Deletion flag and archiving follow the retention policy **Scoring Note:** Mark each item as done. Critical items should be complete before the settlement run. Keep the exported checklist with the period close file. ## Content **Intro:** Maintenance orders that are never settled leave costs stuck on orders and make cost center reports wrong. This checklist walks through the steps from the last confirmation to a zero balance order, so period close does not depend on one person's memory. **Sections:** #### How to use the checklist **Body:** Work through the groups in order. Tick items as you complete them, and use the critical flag to focus on what will block settlement. The checklist is useful per order for large jobs such as shutdowns, and per period for the collective run across all orders. Export the completed list to PDF or Excel and keep it with your close documentation. Planners can use the first two groups, while controllers and cost accountants will focus on the last three. #### How settlement works in SAP PM **Body:** Settlement moves the actual costs collected on an order to one or more receivers, such as a cost center, an asset under construction or a WBS element. It depends on three things: a settlement rule on the order, a settlement profile on the order type that decides which receivers are allowed, and an allocation structure that maps cost elements to settlement cost elements. Orders are settled one at a time in KO88 or in bulk in KO8G. Always run a test run first, because the log shows rule and receiver errors without posting anything. #### Typical errors and their causes **Body:** The most common settlement errors are a missing settlement rule, a receiver that the profile does not allow, a closed posting period, and cost elements that have no settlement cost element in the allocation structure. Another frequent cause is a status that blocks the business transaction, such as an order that was set to closed too early. Before blaming the run, check the order status, the rule and the period. If costs were posted after a settlement, the order has a balance again and must be settled once more. **Bullets:** - No settlement rule: add the rule in the order or default it from the master record - Invalid receiver: check the settlement profile for the order type - Period closed: ask finance to open it or settle in the next period - Unassigned cost element: fix the allocation structure with finance #### Common mistakes **Body:** Do not set orders to closed before final invoices have arrived, because late postings will fail. Do not leave the settlement rule to be filled in at period end, as this is when errors multiply. Do not treat capital and expense work the same way. Agree policy with finance about capitalization thresholds, and make planners aware at order creation. Finally, review orders that stay open for months: they often point to missing confirmations or abandoned work. **Cta:** If you want a live list of unsettled orders, open balances and orders blocked by missing rules, Netray can build a read-only report on your SAP data, with the query visible. **Faq:** #### What is the difference between KO88 and KO8G? **Answer:** KO88 settles one order and is useful for checking a single case. KO8G is the collective transaction that settles many orders in one run, normally at period end, and produces a log with each success and error. #### Why does settlement fail with no settlement rule? **Answer:** SAP needs to know where to send the cost. Add a settlement rule to the order with a valid receiver, or configure defaults from the master record or order type so the rule is created automatically. Then run the settlement again. #### Should I set TECO before or after settlement? **Answer:** Most companies set TECO before the final settlement, once work and goods movements are complete. Costs can still be corrected afterwards in many configurations. Set the closed status only after final settlement and after late invoices have posted. #### Can I settle an order more than once? **Answer:** Yes. If more cost posts to an order after a settlement, it carries a balance again and can be settled again. This is normal for orders with late invoices, but it is a sign you should review your closing sequence. ## Search terms sap maintenance order settlement, sap pm order settlement checklist, ko88 settlement, ko8g collective settlement, sap settlement rule maintenance order, sap teco maintenance order, sap pm period end close --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json