Project Systemsadvanced

Project Settlement: Rules, Receivers and Period-End Processing

Key takeaway

Move project costs from temporary project objects to their final accounting receivers using controlled settlement rules, valid periods and period-end reconciliation.

Explanation

📌 KEY POINTS
✅ Settlement moves eligible cost balances to final receivers — it does NOT delete project history.
⚠️ Missing receiver, invalid percentage, closed period, or incompatible object status can all stop settlement.
💡 The receiver embodies the accounting purpose of the project — never fake one.

━━━━━━━━━━━━━━━━━━━━
▶ 1. WHAT SETTLEMENT DOES

Transfers eligible WBS/network balances to final receivers per settlement rules
Receivers: fixed assets, cost centers, profitability segments, or other supported CO/FI objects
Investment projects often settle to AuC first, then later to completed fixed assets

━━━━━━━━━━━━━━━━━━━━
▶ 2. THE SETTLEMENT RULE

Defines the receiver, percentage or equivalence, and validity

━━━━━━━━━━━━━━━━━━━━
⚠️ 3. PERIOD-END PREREQUISITES

Postings, allocations, results analysis (where relevant), and valid settlement rules must all be in place
Failure points: missing receiver, invalid percentage, closed period, incompatible object status

━━━━━━━━━━━━━━━━━━━━
▶ 4. THE GOLDEN RULE

Settlement creates CO/FI allocation postings — project reports retain the original cost flow AND the settled values
Never create dummy receivers just to clear an error — the receiver embodies the project's actual accounting purpose

✅ CHECKPOINT: name the four things that can stop settlement at period-end.

Real project scenario

A capital project could not close because WBS balances remained unsettled. The settlement rule still pointed to an obsolete AuC after asset capitalization. Updating the valid final receiver and rerunning settlement cleared the balance correctly.

Common mistakes

Using dummy receivers to pass period end.
Ignoring settlement-rule validity dates.
Confusing settlement with project-cost deletion.
Closing WBS before required settlement.
Running settlement before prerequisite period-end steps.

Best practices

Design receiver logic with Finance/CO.
Validate rules before month end.
Reconcile settled and remaining balances.
Preserve project statuses correctly.
Test capital-project settlement lifecycle.

Interview angle

Explain why projects settle, what a settlement rule contains and typical receiver types.

Practice this lesson

Quick check

1. Move project costs from temporary project objects to their final accounting receivers using controlled settlement rules, valid periods and period-end reconciliation. A production team now has to make a design decision in Project Settlement: Rules, Receivers and Period-End Processing. Which option best preserves reliability and supportability?

2. A team proposes this shortcut while working on Project Settlement: Rules, Receivers and Period-End Processing: "Confusing settlement with project-cost deletion." Which alternative should you recommend?

3. A review of Project Settlement: Rules, Receivers and Period-End Processing finds this risky pattern: "Using dummy receivers to pass period end.". Which corrective action is strongest?

Interview questions

1. You are the senior consultant/architect responsible for Project Settlement: Rules, Receivers and Period-End Processing. The project situation is: A capital project could not close because WBS balances remained unsettled. How would you assess the design, identify the highest-risk failure modes, and define the evidence required before approving it for production?

Answer it in your own words first, then compare.

2. A project manager informs you that the period-end settlement for a major investment project has failed. What are the common technical and configuration-related reasons you would investigate for this failure, and why is selecting the correct final receiver so crucial in this scenario?