Actual project costs are recorded postings assigned to work breakdown structure (WBS) elements, network activities or other project account assignment objects. They can arise from financial documents, goods movements, supplier services, internal activity allocations and other posted transactions depending on the solution design. Actual costs are not the same as a plan, an authorized budget, an open procurement commitment or a cash payment.
Trace the project account assignment
Every actual-cost line requires the correct cost object and source document. A goods issue posted to one network activity cannot automatically be interpreted as a cost on a different WBS element just because both describe similar work. A project controller checks project assignment, G/L or cost element, posting date, currency and operational source before accepting the report.
Where actual project costs come from
Internal work can generate actuals through activity confirmations and allocations; external procurement can contribute through material movements, services and supplier invoicing. Other FI postings and period-end allocations may also affect project costs. Exact posting timing and valuation depend on stock treatment, account assignments and configuration. Trace one end-to-end business case before assuming a standard accounting entry.
Example: a project appears under budget
Suppose a project WBS has ₹3.80 million planned, ₹1.65 million posted as actual cost and ₹1.10 million in remaining procurement commitments. The arithmetic difference, ₹1.05 million, is not automatically the expected cost to complete: unraised purchases, unfinished labor, scope changes and risks may still be ahead. Controllers must reconcile posted and outstanding costs before advising the sponsor.
Distinguish four financial signals
Plan estimates the expected cost of defined work. Actual records what has been posted. Commitment shows open procurement obligations that may become actual later. Budget is approved spending authority, not consumption. Comparing only plan and actual may conceal pending purchase orders; adding all historic requisitions to purchase-order commitments may double count procurement demand.
Investigate variance and posting timing
Late invoices, missing goods issues, wrongly assigned WBS values, reversals and overhead allocations can distort current actuals. Reconcile transaction details with physical progress and purchasing evidence rather than changing the baseline to make a report appear better. A variance can be about timing or assignment rather than genuine savings; document the reason and owner of each significant exception.
Questions before a project cost review
Which operational events post actuals? Who owns corrections to a wrongly assigned cost object? Are internal activities and purchased services included consistently? How does project stock affect the cost posting? Who checks open commitments beside actuals? What assumptions underpin the latest estimate at completion? A useful dashboard should make these decisions easier, not replace traceable source evidence.
Read next
Project Cost Planning, Project Budgeting, Availability Control and Network Activities. Return to the SAP PS / EPPM hub.