Project billing converts an approved contractual entitlement into a customer invoice. In SAP Project System integrations, billing-relevant WBS elements can connect to sales documents, while the commercial arrangement determines whether charges arise from milestones, agreed fixed amounts or eligible project expenditures. Project costs, customer billing and financial revenue recognition are related but not identical events.
Start with the contract, not the WBS cost total
A work breakdown structure organizes delivery scope and control. In supported SAP PS scenarios, sales-order items can reference WBS billing elements. This links project work with SD billing, but a cost posting does not automatically entitle the company to invoice the customer. The billing basis belongs to the contract and sales document.
Ask which deliverables are priced, when acceptance is required, and who may release a billing claim. Those decisions make the invoice auditable.
Milestone, fixed-price and resource-related billing
Milestone billing uses a billing plan tied to contract dates or project milestones where configured. Milestone completion can release a planned billing date in relevant SAP PS integrations. Resource-related billing instead derives claims from eligible project work or materials, subject to pricing and determination rules. These routes need different evidence and must not be mistaken for automatic invoice generation.
In supported SAP S/4HANA Cloud services scenarios, billing requests and billing document requests also play a role. Exact document flows vary by edition and configuration.
Review progress evidence before release
The project lead confirms work performed, the commercial owner verifies contractual entitlement, and the billing analyst checks agreed pricing, prior claims and customer acceptance. A milestone marked complete in the plan is not necessarily an approved customer acceptance event. Contract amendments, retention clauses and disputed scope can change what is billable.
Worked example: a ₹30 lakh contract
Suppose a project is billed 30% after design acceptance, 40% following factory tests and 30% after handover. The amounts are ₹9 lakh, ₹12 lakh and ₹9 lakh. If the tests are delayed, the second invoice should follow the actual contract condition rather than the original calendar target. Reconcile accepted milestones to billed documents and monitor any advance payments separately.
For a time-and-materials engagement, validate approved hours, eligible materials, rates and already-billed entries instead of using a milestone percentage.
Billing controls and the milestone timeline
Review billing blocks, delivery evidence, tax and currency details, duplicates, credit adjustments and authorized release. Ensure changes in scope and pricing reach the commercial records before invoicing. Finance should reconcile accounts receivable to the sales billing documents and review whether an invoice is late, premature or disputed.
Do not confuse an invoice with recognized revenue
Customer invoicing records a billing claim under the configured commercial process. Financial revenue recognition may follow different timing under applicable accounting policies. Likewise, a customer down payment need not represent earned revenue. A consultant should design project costs, billing plans, cash application and financial reporting as connected but distinct controls.
Useful questions: which WBS is billing-relevant, what triggers release, which expenditures qualify, and how are reversals after billing resolved?
Related project concepts
Compare project cost planning, actual project costs, commitments, and project stock. Return to SAP PS / EPPM.