Publicité
ERP IMPLEMENTATION
🇫🇷 Lire en français →

2027 Budget Campaign in Your ERP: How to Build, Approve and Track the Budget Step by Step

Run your 2027 budget cycle inside your ERP: versions, analytical dimensions, approval, commitment control, reforecasting and a T-8 to T0 checklist.

2027 Budget Campaign in Your ERP: How to Build, Approve and Track the Budget Step by Step

Every autumn, the same scene plays out in many small and mid-sized companies. The financial controller exports actuals from the ERP, pastes them into a multi-tab Excel workbook, sends it to every cost centre owner, then spends three weeks consolidating files that came back in different formats. In January, the approved budget is rekeyed (or re-imported) into the ERP so that variances can be tracked. In the meantime, three versions have been circulating and nobody is sure which one is the reference.

Your ERP can do better, provided you know what to ask of it. This guide is for CFOs and financial controllers who want to run the 2027 budget campaign inside the ERP, from preparation to monthly follow-up, before considering a dedicated planning tool. We will not reopen the ERP versus EPM debate, already covered in our ERP vs EPM comparison (SAP, Oracle, Anaplan, OneStream). Here, we focus on what happens inside the ERP.

What an ERP Can (and Cannot) Do for Budgeting

An ERP is first and foremost a transactional system: it records orders, invoices and journal entries. Its strength in budgeting comes from something spreadsheets lack: it knows actuals at the finest level, using the same dimensions (account, cost centre, project, product) as the budget.

What the ERP does well:

  • storing several budget versions side by side, on the same dimensions as the general ledger;
  • comparing actuals, commitments and budget in real time by account, cost centre or project;
  • blocking or warning when a purchase order exceeds the envelope;
  • locking an approved version and tracing who changed what;
  • feeding management dashboards (see our 15 financial KPIs for the CFO).

What it does poorly or not at all:

  • simulation (“what if sales fall by 8%?”) with instant cascading recalculation;
  • large-scale collaborative input from dozens of contributors, with reminder workflows;
  • complex calculation models (headcount, capacity, seasonality) without custom development;
  • multi-entity consolidation with currency translation and intercompany eliminations, depending on the vendor.

These limits explain why budgeting in the ERP suits a small company with a handful of cost centres or a single-entity mid-market firm very well, and becomes painful as complexity grows. We come back to this below with five concrete signals.

Preparing the Campaign: Calendar, Analytical Dimensions, Versions, Scope

Most campaigns that go off the rails do so because preparation was rushed, not because the build is hard. Four decisions need to be made before the first entry is opened.

The Calendar

Set a backward-planned schedule in weeks (see the checklist at the end of this article) with a non-negotiable lock date. For a calendar-year company, the build phase typically runs from September to November, with approval in December. If you are reading this in November 2026, do not try to do everything: aim for a simple, clean 2027 budget, then enrich it through reforecasts.

Analytical Dimensions: The Classic Trap

This is the costliest point of the entire campaign. If you change analytical dimensions mid-year (creating a cost centre, merging two departments, adding a new project breakdown), budget and actuals are no longer comparable: actuals land on a cost centre that does not exist in the budget, and vice versa. You then spend the year maintaining mapping tables in Excel, which defeats the purpose of having the budget in the ERP.

Practical rule: freeze the analytical structure for the whole fiscal year, including secondary dimensions. Any reorganisation is budgeted as a version change, not as a patch to the master data. Our year-end configuration and 2027 fiscal-year rollover checklist (in French) details the chart-of-accounts and dimension checks to run before the rollover, and our article on analytical accounting and budget management explains how to structure that framework.

Versions

Agree on a version convention from the start, for example:

VersionPurposeEditable?
B2027-V0Initial framing (top-down envelopes)No, archived
B2027-V1Budget under constructionYes, by contributors
B2027-FINALApproved budget, reference for trackingNo, locked
RF2027-xxSuccessive reforecastsYes, until approved

The decisive point: variance tracking is always done against B2027-FINAL, never against the latest reforecast. Otherwise you are measuring your ability to move the target, not your performance.

Scope

Be explicit about what is budgeted in the ERP and what stays out of scope. A reasonable choice for a first campaign: income statement (revenue and expenses) by cost centre, plus capital expenditure by project. The forecast balance sheet and cash flow can stay in a workbook in year one.

Building the Budget: Historical Baselines, Assumptions, Controlled Excel Import or Direct Entry

Start from Historical Baselines

Most ERPs offer a function to copy prior-year actuals (or the latest version) into a new budget version, with an adjustment factor per line. This is the best starting point: you eliminate blank-sheet entry and guarantee that accounts and cost centres exist. Be careful to restate non-recurring items (litigation, disposals, one-off projects) before copying, otherwise you will budget 2026’s exceptional items as recurring in 2027.

Assumptions: One Sheet, Documented

Macro assumptions (inflation, supplier price changes, exchange rates, salary reviews) must be explicit and shared: a single parameter sheet that every contributor uses. Many ERPs have no native assumptions table. In that case, keep it outside the ERP, versioned, and reference it in the description of each budget version.

Controlled Excel Import or Direct Entry

The two modes almost always coexist.

  • Direct entry in the ERP: suited to small scopes and to managers who are comfortable with the tool. Advantage: immediate consistency checks (unknown account, closed cost centre). Drawback: usability is often less flexible than a spreadsheet.
  • Controlled Excel import: contributors work in a template generated from the ERP (locked dimensions, protected total formulas), then the controller imports the file. “Controlled” means three things: the template is exported from the ERP, never built by hand; the import is rejected if an analytical key is unknown; and the import is logged (who, when, which version).

For a smaller company, controlled import is the most realistic compromise: it keeps business users in a familiar tool without breaking the integrity of the dimensions.

By way of non-exhaustive examples: in SAP, cost planning by cost centre and version (the CO module, or integrated planning depending on the release) supports version copy and file upload; in Odoo, the budget module (budgetary positions and analytic budgets, depending on the edition) works by account or analytic dimension, with lighter data entry; in Dynamics 365 Business Central, general ledger budgets can be entered, imported and exported via Excel with several budget names in parallel; in Sage (X3, Intacct, 100), budgets by analytical section are supported, with features and import capabilities that vary by product. Check in your exact release what is standard, what is a paid option and what requires development.

Sales, Purchasing, Payroll and Capex Budgets

These four blocks do not follow the same logic and are not built the same way.

Sales budget. Build it in quantities and prices, by product family or key account, rather than as a lump sum. The order book and recurring contracts in the ERP provide the firm base; the gap to target is the “still to find” that sales teams must document. A budget in value alone makes it impossible to explain a variance between price effect and volume effect.

Purchasing budget. It is largely derived from the sales and production budgets (material requirements, subcontracting), completed by indirect purchases per cost centre. Framework agreements and supplier prices in the ERP serve as references. This is where purchase commitments (see below) really matter.

Payroll. In most cases it comes from the HRIS or payroll system, not from the financial ERP: you import a budget by cost centre (headcount, salaries, employer costs, variable pay) built from actual December headcount plus planned hires, departures and pay rises. See our article on payroll and workforce planning. One precaution: budget employer social charges with a single documented rate, revisable at reforecast.

Capital expenditure. Budget it by investment project, with a project number (internal order, WBS element, analytical project) that will follow the purchase order, goods receipt and fixed-asset capitalisation. Separate the investment envelope from the depreciation it generates, which is calculated separately. For Capex and Opex logic, see our Capex vs Opex guide for the CFO.

Approval Workflow and Version Locking

A budget that is not locked is not a budget. Plan a short, three-step workflow:

  1. Submission by cost centre: the owner validates their entry or imported file (status “submitted”).
  2. Management control review: consistency with assumptions, variances against prior year explained, envelope-by-envelope trade-offs.
  3. Executive approval: the version is copied to B2027-FINAL and then locked.

In the ERP, three mechanisms help: version statuses (open, approved, locked, depending on the product), access rights by version (only management control can write to FINAL) and the approval workflow where one exists as standard. Where it does not, an approval by email, validated and archived, remains acceptable as long as the FINAL version is properly locked in the system.

Two simple governance rules: a single reference version, and any change after locking goes through a reforecast, never through an edit to the original budget.

Budgetary Control: Purchase Commitments, Overrun Alerts, Actual vs Budget Variances

This is where the ERP pulls ahead of the spreadsheet. Budgetary control compares the budget not only with posted actuals but also with commitments.

Actuals, Commitments, Available Budget

  • Actuals: what has been posted (supplier invoices, payroll, journal entries).
  • Commitments: what has been ordered but not yet invoiced (purchase orders, approved purchase requisitions).
  • Available budget = budget − actuals − commitments.

Without the notion of commitments, you discover overruns when invoices arrive, when it is too late to make trade-offs. Commitment tracking is the number one argument for keeping the budget alive in the ERP.

Alerts and Hard Stops

Depending on the product and its configuration, control can be:

  • informational: the ERP displays the available amount without preventing the order;
  • warning: a message when the requisition or purchase order is validated;
  • blocking: validation is impossible beyond a threshold (for example 100% of the envelope, or a tolerance percentage).

For a smaller company, good practice is to start in warning mode for one season, while analytical assignments are cleaned up, then switch to blocking on high-stakes accounts (subcontracting, professional fees, travel). Going straight to blocking in January creates stuck orders and workarounds.

Tracking Variances

A monthly rhythm is enough for most SMEs: close, extract actuals and commitments by cost centre, analyse variances above a threshold you define (in value and in percentage), and require a written comment from the owner. Two pitfalls: commenting on every variance (the signal drowns) and comparing only month by month (seasonality distorts the reading, hence the value of a year-to-date view). Always break a sales variance down into price effect, volume effect and mix effect.

Reforecast and Rolling Forecast: Frequency, Sliding Version, ERP Limits

A reforecast updates the year-end outlook at a given date: actuals for closed months plus the best estimate for the remaining months. A rolling forecast projects a constant horizon (for example 12 months or 4 quarters) that shifts at each close. For the principles and the zero-based budgeting case, see our rolling forecast and ZBB guide.

A reasonable frequency for an SME or mid-market company in the ERP: a quarterly reforecast, possibly a quarterly rolling forecast over four sliding quarters. A monthly rhythm assumes dedicated tools and teams.

Implementation in the ERP:

  • create a new version for each reforecast (RF2027-Q1, RF2027-Q2…), initialised by copying actuals for closed months and the latest estimate for the rest;
  • do not touch B2027-FINAL;
  • for a rolling forecast, create budget periods beyond the current fiscal year: possible when the ERP accepts periods in year N+1, harder when the fiscal year is a rigid frame.

Limits to be aware of: repeated version copying becomes heavy, assumptions do not propagate automatically, and the history of successive forecasts is rarely analysable natively (“when did we downgrade the margin forecast?”). This is often the first place where you hit a wall.

When the ERP Is No Longer Enough: 5 Signals to Move to a Planning Tool

Staying in the ERP is a healthy choice as long as things stay simple. Here are five signals that a dedicated planning tool is becoming justified.

  1. The campaign cycle gets longer every year despite a stable scope: consolidation and back-and-forth cost more time than analysis.
  2. More than ten active contributors must enter their assumptions, with reminders and progress tracking that cannot be managed in the ERP.
  3. A need for scenarios (optimistic, pessimistic, currency shock) recalculated within minutes for the executive committee.
  4. Several entities or currencies with consolidation and intercompany eliminations that the ERP does not handle well.
  5. The models live in Excel: the more calculation logic (headcount, capacity, drivers) sits outside the ERP, the heavier the maintenance debt.

One signal is not enough. Three or more is. In that case, re-read the ERP vs EPM comparison before launching a tender.

Campaign Checklist (T-8 to T0 Weeks)

T-8: scoping

  • Confirm the budgeted scope and the versions (B2027-V0, V1, FINAL).
  • Freeze the analytical structure for the year (accounts, cost centres, projects).
  • Appoint an owner for each cost centre.

T-7 to T-6: technical preparation

  • Create the versions in the ERP and set up access rights.
  • Copy restated prior-year actuals; document non-recurring items.
  • Publish the assumptions sheet (inflation, exchange rates, pay reviews).

T-5: launch

  • Distribute the templates exported from the ERP and the instructions.
  • Train contributors in one hour (entry, import, statuses).

T-4 to T-3: build

  • Collect the sales, purchasing, payroll and capex budgets.
  • Import with analytical key checks; handle rejections as they occur.

T-2: review and trade-offs

  • Consistency check: variances against prior year explained, sales consistent with production and purchasing.
  • Trade-offs with executive management, envelope by envelope.

T-1: approval

  • Copy the selected version to B2027-FINAL and lock it.
  • Archive the working versions.

T0: go-live and tracking

  • Activate budgetary control (warning mode at start), commitments and alerts.
  • Schedule the first monthly variance review and the reforecast calendar.

Going Further

To turn your 2027 ERP budget into a defensible IT spending plan, read our 2027 ERP budget guide for the CIO. And to check that your ERP is ready to carry the new campaign, download our ERP evaluation scorecard: 30 criteria across 100 points to compare your options side by side.