Project Execution, Billing and Settlement: End-to-End PS Flow

Key takeaway

Understand the full SAP PS lifecycle from project structure and planning through procurement/execution, customer billing where applicable, period end, settlement and closure.

Explanation

📌 KEY POINTS
✅ One PS structure connects logistics and finance across the entire project lifecycle.
⚠️ Never close a project based only on task completion.
💡 Support should trace the full chain as ONE story, not separate silos.

━━━━━━━━━━━━━━━━━━━━
▶ 1. LIFECYCLE FLOW

Project definition, WBS, optional networks → control and execution structure
Planning → dates, cost, resources, budget
Execution → procurement and internal work create commitments and actual costs

━━━━━━━━━━━━━━━━━━━━
▶ 2. CUSTOMER VS. INVESTMENT PROJECTS

Customer projects: sales/billing integration creates milestone or other billing; Results Analysis may value period-end separately from billing
Investment/internal projects: settlement moves eligible costs to assets, cost centers, or other final receivers

━━━━━━━━━━━━━━━━━━━━
▶ 3. STATUS GOVERNS THE LIFECYCLE

Release enables execution
Technical/business completion should occur only after open work, commitments, billing, and settlement are handled per project type

━━━━━━━━━━━━━━━━━━━━
⚠️ 4. THE CLOSURE TRAP

Never close a project based only on task completion if purchasing, billing, or settlement remains open
Support should trace WBS/network status, procurement, actual cost, billing, settlement, and open commitments as one chain

✅ CHECKPOINT: explain why "work is done" is not the same as "project can close."

Real project scenario

A customer project finished physically, but closure was blocked by an open PO commitment and unsettled WBS balance. Completing procurement and settlement allowed controlled project close.

Common mistakes

Treating execution completion as financial closure.
Ignoring commitments.
Confusing billing with revenue recognition.
Leaving settlement rules until close.
Managing schedule outside project financial context.

Best practices

Align project type with finance process.
Monitor commitments and billing.
Run period-end processes in sequence.
Settle before final close.
Keep statuses meaningful.

Interview angle

Trace a project from creation to closure and explain differences for customer versus investment projects.

Practice this lesson

Quick check

1. In the lesson "Project Execution, Billing and Settlement: End-to-End PS Flow", consider this project situation: A customer project finished physically, but closure was blocked by an open PO commitment and unsettled WBS balance. Which statement is correct?

2. Design an end-to-end architecture for a large EPC (engineering, procurement, construction) project where procurement costs flow through PO commitments, milestone billing is tied to SD billing plans on WBS, and revenue must be recognized per POC. What are the key design decisions? Choose the response that best aligns with the expected SAP approach.

3. During period-end, RA results are calculated correctly but the settlement run fails to post WIP to the correct balance sheet account, and asset settlement of AuC-related capitalized costs is also affected. How would you diagnose this cross-area issue? Choose the response that best aligns with the expected SAP approach.

Interview questions

1. Using this SAP project situation — A customer project finished physically, but closure was blocked by an open PO commitment and unsettled WBS balance — explain Project Execution, Billing and Settlement: End-to-End PS Flow. What should happen, which concepts or process steps matter, and what common mistake would you avoid?

Answer it in your own words first, then compare.

2. Describe the end-to-end process by which costs accumulated on a customer project WBS are recognized as revenue through a milestone billing plan and subsequent settlement.

Answer it in your own words first, then compare.

Practice more with Interview AI →

Reference-verified: the steps are checked against official SAP documentation and tutorials, and object and field names in the sample code are checked for consistency. The code has not been compiled or run on an SAP system by ERPClimb. Syntax marked release-dependent varies by SAP release, so check it in your own system.