What does SAP budget planning usually look like?
In many companies, the budget is a set of Excel files built from SAP exports, emailed between departments and consolidated by hand. It works, but it is hard to know which version is current, who changed a figure, or how the plan compares with actual once the year starts.
Common pain points at budget time:
- This year's actuals are exported and pasted into templates, then pasted again when the figures move.
- Department heads send back files in slightly different layouts.
- Approvals happen by email, and the approved version is whichever file was sent last.
- Plan versus actual is rebuilt by hand each month for the management pack.
| Spreadsheets built from SAP exports | LendraBI | |
|---|---|---|
| Starting point | Actuals exported and pasted | This year's SAP actuals |
| Versions | Files named by date or by person | Budget, forecast and what-if versions |
| Changes | Hard to trace | Comments and full change history with every figure |
| Approvals | Email threads | Multi-level approval with deadlines and reminders |
| Plan versus actual | Rebuilt each month | Plans next to actuals on any dashboard |
How do you build a budget from SAP actuals in LendraBI?
You start from this year's actuals in SAP and shape them into a plan yourself, or let the planning assistant draft a version that you review before you apply it.
- Start from actuals. Use this year's SAP actuals as the base for the new version.
- Draft with the planning assistant. Describe what you want, for example "next year's budget based on this year's actuals, with growth in the Riyadh branch," and the assistant drafts a version for you to check.
- Use drivers. Work from drivers rather than typing every cell. Volume plans take units and prices from your SAP actuals, and headcount plans by position fill in staff costs.
- Spread by month. Spread annual figures across the months of the year.
- Allocate. Allocate shared costs, for example rent, across departments.
- Set currencies. Plan exchange rates can be filled from SAP's standard rates, and amounts in different currencies are never added together as they stand.
The guide on how to build a budget from SAP actuals walks through these steps in more detail.
How do budget, forecast and what-if versions work together?
Each one is a separate version, so you can keep the approved budget as it is while you build a forecast and test what-if scenarios beside it. All of them can be shown next to actuals on the same dashboard.
For example, a finance team might:
- Approve the annual budget and lock it.
- Build a forecast during the year, starting again from this year's actuals.
- Build a what-if version to see the effect of opening a new branch or losing a large customer, without touching the budget or the forecast.
Because each version is kept separately, the conversation in a review meeting can move from "which file is right?" to "what changed between budget and forecast, and why?"
How do approvals, locks and history keep the plan under control?
Plans go through multi-level approval with deadlines and reminders, and data locks and validation rules keep figures from changing when they should not.
- Approvals: each level reviews the plan in turn, with deadlines and reminders so it does not stall in someone's inbox.
- Data locks: stop approved figures from being changed.
- Validation rules: check entries against the rules you set.
- Comments and change history: see who changed a figure and read the comments left with it, long after the budget meeting.
- Forms: collect inputs such as sales targets or headcount requests through forms, approve them, and fill a plan from the approved entries.
Access profiles limit what each person can see to the business areas and company codes you choose, and a searchable activity log records every sign-in, share and admin change.
Can you keep using Excel for planning?
Yes. You can bring figures in from Excel and take them back out to Excel, so people who prefer a spreadsheet can still work in one. The difference is that the plan itself, with its versions, approvals and history, is kept in one place instead of in many files.
Forms also accept Excel upload, which helps when a department sends its inputs as a spreadsheet. For the board pack, dashboards export to PowerPoint and charts to Excel, and you can also export to PDF.
How do you track plan versus actual during the year?
You show any plan version next to actuals on any dashboard. Variance and waterfall charts show the gap, split into volume and price effects, and "Ask why…" on any chart explains in plain words what moved a figure.
- Compare budget, forecast and actual, for example by company code or department.
- Set KPI alerts that tell you when a figure crosses a limit you set, for example when monthly spending passes a level you choose. Limits are checked hourly.
- Send scheduled email reports to management, in the email itself and as a PDF.
Plan versus actual is a large part of SAP reporting for finance teams, and plans can appear on any of the SAP dashboards your teams already use. To see planning on SAP actuals for yourself, book a demo.
Questions
Does LendraBI write budgets back into SAP?
No. LendraBI reads SAP through a read-only SAP user. Budgets, forecasts and what-if versions are built and approved in LendraBI and shown next to SAP actuals on dashboards.
What does a new budget start from?
From the SAP actuals of a year you choose, usually the year before the plan year. You then adjust it with drivers, spreading by month and allocations, or ask the planning assistant to draft a version that you review and apply.
Can we keep using Excel for budgeting?
Yes. Plans support Excel in and out, and forms accept Excel upload.
How are currencies handled in a plan?
Plan exchange rates can be filled from SAP's standard rates, and amounts in different currencies are never added together as they stand.
Can a plan be locked after approval?
Yes. Data locks stop approved figures from being changed, and validation rules check entries. Approval is multi-level, with deadlines and reminders.