Fixed or capped contract values

Once the contract is signed, you absorb most cost increases yourself.

Long supply chains

Steel, cables, transformers, and imported equipment all carry price and delivery risk.

Multiple parallel workstreams

Engineering changes affect procurement, procurement delays affect site work, and site delays affect cash flow.

1. Budgets approved but never enforced

Many companies build a detailed estimate, then lose the link between that estimate and day-to-day spending. Purchase orders get raised without anyone checking the remaining budget.

2. Late visibility of commitments

Actual costs are a lagging indicator. By the time an invoice posts, the decision that caused it was made weeks ago. The real exposure sits in open purchase orders and subcontracts, which many finance teams can’t see per project.

3. Uncontrolled scope changes

A client asks for a small design change. Engineering approves it verbally. Nobody updates the budget, and the cost lands in the final account.

4. Poor forecasting

Many teams compare “spent so far” with “total budget” and call that a forecast. That shows how much you’ve used, not how much you’ll need to finish.

5. Manual, delayed reporting

If your monthly project report takes ten days to compile from Excel files, it is out of date before it reaches the management meeting.

6. Weak links between schedule and cost

A delayed activity extends site overheads, equipment rental, and labour. Without a connected schedule, these knock-on costs stay hidden.

1. Build a WBS That Mirrors How You Execute

The Work Breakdown Structure is the backbone of SAP PS. You break a large EPC contract into manageable elements, for example engineering, procurement, civil, mechanical, electrical, and commissioning, and then into smaller packages below each.

Each WBS element becomes a cost collector. Planned costs, budgets, actual costs, and commitments are all stored at that level. A project manager can see exactly where the money goes: Is the electrical package running hot? Is civil on track?

Practical tip: design the WBS around how you control cost, not only how you invoice. A WBS built purely for billing will hide the very detail you need to spot an overrun early.

2. Lock the Budget with Availability Control

This is one of the most powerful features for preventing overruns. Availability control compares planned spend, including open commitments, against the approved budget as transactions are entered. It can be set up in three ways:

• Warning: a user sees an alert when spending nears the limit.
• Warning with email: the project manager is notified automatically.
• Error (hard stop): the system blocks the purchase order or posting once the budget is exhausted.

Consider a procurement officer in Pune raising a PO for switchgear. If it would push the electrical package over 95% of its budget, the system flags it before the order goes out. That is the difference between preventing an overrun and explaining one later.

Your tolerance limits can be graded, say a warning at 80%, an email at 90%, and a block at 100%, so the control matches your risk appetite.

3. See Commitments, Not Just Actuals

In EPC, the money is committed long before it is spent. SAP PS captures purchase requisitions, purchase orders, and subcontract commitments against the WBS element the moment they are created. You get a true picture of exposure: budget, minus actuals, minus open commitments, equals what is truly left.

For finance leaders, this is the biggest shift. Instead of finding out in month nine that a vendor contract was larger than expected, you see it in week two.

4. Handle Scope Changes Through Budget Revisions

Scope changes will happen, and no system can stop clients from asking. What SAP PS can do is make every change visible and approved. Budget supplements, returns, and transfers are logged with a history, so you can see who approved what and why.

Combined with a proper change-order process, this protects your margin. When a client requests extra work, you have the cost impact calculated and documented before you agree, which supports a variation claim instead of leaving you out of pocket.

5. Forecast Cost-to-Complete, Not Just Cost-to-Date

SAP PS supports cost forecasting and earned value analysis, which compare the value of work completed with the money spent on it. Two numbers matter most:

• Cost Performance Index (CPI): a value below 1.0 means you are spending more than the work completed is worth.
• Estimate at Completion (EAC): a realistic projection of the final cost, based on current performance.

If your EAC is 8% above budget at the 40% completion mark, you have time to renegotiate, re-sequence, or find savings. At 90% completion, you don’t.

6. Connect the Schedule to the Cost

SAP PS uses networks and activities to model the project schedule. Activities link to WBS elements, so a delay shows its cost impact. When a critical activity slips, you can see its effect on site overheads, equipment hire, and milestone billing.

This matters for EPC projects with liquidated damages clauses. A two-week delay on a milestone may carry a penalty larger than the original cost of the delayed work. Seeing that link early changes decisions.

7. Settle Costs Correctly and Report in Real Time

Settlement moves project costs to the right accounts, such as assets under construction, cost of sales, or profitability segments. With SAP PS built into S/4HANA, reporting is live. There is no month-end scramble to consolidate Excel files.

Dashboards and Fiori apps can show budget versus actual, commitments, forecasts, and margin by project, by business unit, or by city, so a CFO in Mumbai and a site head in Chennai are looking at the same numbers.

Over-complicated WBS structures

Too many levels create data entry fatigue, and users start bypassing the system. Aim for the level of detail you will actually control.

Switching off availability control “to speed things up”

If the control is disabled, you have lost the main safeguard. Tune the tolerances instead.

Ignoring master data discipline

Inconsistent cost elements and vendor data make reports unreliable.

Skipping user training

A control only works if site engineers, procurement officers, and finance teams use it consistently.

Treating implementation as an IT project

The project controls and commercial teams must lead the design.

GST and e-invoicing

Milestone billing, retention, and works contract taxation need to flow correctly from the project into billing documents.

Multi-state operations

Projects spread across states mean different tax treatment and statutory requirements.

Price escalation clauses

Many Indian government and PSU contracts include escalation formulas that should be reflected in forecasting.

Subcontractor-heavy execution

Strong commitment and measurement tracking for subcontractors is critical.

Currency exposure

Imported equipment adds exchange rate risk to the cost forecast.