Lesson 5 of 6
Plan/actual variance reporting
9 min
Listen to this lesson
The monthly cost center review is where planning and postings meet. The plant manager opens the plan/actual report for Detroit Maintenance and sees: plan $48,000 for period 5, actual $55,600, variance $7,600 or 15.8% over plan. The number is the start of a conversation, not the end of one. The controller's job is to explain it: which accounts, which postings, which causes, and whether anything must be corrected.
- Open the reportCost Centers - Plan/Actual for cost center 17101102, period 5, plan category Budget
- Find the accountsWhich G/L accounts carry the variance? Here: external repair services and maintenance materials
- Drill to line itemsOpen the postings behind the accounts: documents, suppliers, dates, users
- Classify the causePrice, volume, one-off event, timing, misposting or missing allocation
- ActCorrect errors, explain real variances, adjust the forecast if needed
Where to report
SAP's learning material names the Cost Centers - Plan/Actual Fiori app for this comparison and the Query Browser for ad-hoc reporting on analytical queries. Both belong to SAP S/4HANA embedded analytics, which reads Universal Journal data directly through CDS views without copying it, so a reposting made at 10:00 shows in the report at 10:01. Classic report transactions are also still used in many private edition systems; whichever report Contoso uses, the test is the same: does the report show what was posted?
Classifying the causes
| Cause | What it looks like | Contoso period 5 example | Action |
|---|---|---|---|
| One-off event | A single large posting not in the plan | $5,200 emergency repair of a test bench | Explain; consider a forecast update |
| Misposting | A posting that belongs elsewhere | $2,400 Chicago parts on Detroit | Repost the line item |
| Price | Same quantities, higher prices | Lakeside Components parts up 4% | Explain; review the plan basis |
| Volume | More activity than planned | Extra shift maintenance in a busy month | Explain; link to production volume |
| Timing | Cost in the wrong month, not the wrong year | Quarterly service invoice booked in one month | Consider accruals for smoother periods |
| Missing allocation | Sender or receiver totals off after period end | Energy distribution not yet run | Run or fix the allocation cycle |
Common variance causes and responses.
Working the example: $5,200 emergency repair plus $2,400 misposted parts explains $7,600 exactly. After the reposting, Detroit Maintenance is $5,200 over plan for a documented one-off reason, and Chicago Maintenance shows the $2,400 it really consumed. The misposting was not a performance problem in Detroit at all, which is why the drill-down matters before anyone draws conclusions.
- Is the variance above the review threshold (for example $2,000 and 5%)?No → no explanation needed this month · Yes → continue
- Is it caused by a posting that belongs to another cost object?Yes → repost, then re-run the report · No → continue
- Is it a timing difference within the year?Yes → note it; consider accruals for irregular costs · No → continue
- Is it a real price, volume or one-off effect?Yes → explain it to the manager; update the forecast if it will continue
Timing and accruals
Irregular costs make monthly variances noisy: a quarterly service invoice makes one month look terrible and the next two look excellent. SAP's material describes accrual calculation in controlling for this purpose, with methods such as percentage, plan equals actual, and target equals actual, so that irregular expenses are spread across periods. Contoso uses it for annual bonuses on its production cost centers; the service contract remains a timing note in the review.
What would you do?
Detroit Maintenance is $7,600 over plan in period 5. The plant manager wants to cut overtime immediately. What should the controller do before that decision?
- Plan/actual reports start the conversation; drill-down to line items explains it.
- SAP names the Cost Centers - Plan/Actual app and the Query Browser for this reporting.
- Classify variances: one-off, misposting, price, volume, timing, missing allocation.
- Correct mispostings by reposting before judging performance.
- Use thresholds to focus the review; use accruals for irregular costs.
Check your understanding · not graded
Lesson check
1. Which Fiori app does SAP name for comparing plan and actual cost center values?
2. A variance is caused by a posting that belongs to another cost center. What comes first?
3. What do accruals in controlling help with?
4. Why does a reposting show in the embedded report almost immediately?