Rivane

Accounting
made smart

ERP Use CasesTier 2Published April 7, 2026

Rolling 12-Month Forecast Update

Rolling 12-Month Forecast Update for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.

Rolling Forecast is where ERP discipline either begins or breaks.

Rolling 12-Month Forecast Update looks operational from far away. In a real finance team, it is a chain of assertions: the right actor started the work, the required records existed, the control policy was applied, the state change was preserved, and the outcome can be explained later without rebuilding the transaction from emails and spreadsheets.

The expected business outcome is specific: Up-to-date 12-month forward P&L, cash flow, and headcount forecast available to CFO within 3 business days of month-end close.

The control flow a finance team actually needs.

Workflow map showing control steps, exceptions, and evidence for this ERP process.Rolling Window A...Start conditionPrior Actuals Be...Required checksDriver-Based Lin...Owner and SLAVersion History ...System updatePublished Foreca...Exception handlingAudit packetEvidence trailException loopRolling Forecast should preserve every override and rejection.
Workflow map for this ERP process, including exception handling and audit evidence.

Step 1

Rolling Window Automatically Shift By...

Step 2

Prior Actuals Be Immutable Once Imported

Step 3

Driver-Based Lines Recalculate Within 5...

Step 4

Version History Be Retained For At...

Step 5

Published Forecast Be Exportable To...

The ERP surface involved.

Module

Rolling Forecast

Actors

FP&A Analyst, Business Unit Finance Lead, Forecast System

Tier

Tier 2

Finance area

Budgeting, Planning & FP&A

Region lens

US and UK finance teams

Publication date

April 7, 2026

Rolling window must automatically shift by one month on each cycle without manual reconfiguration; prior actuals must be immutable once imported; driver-based lines must recalculate within 5 seconds of any input change; version history must be retained for at least 24 prior rolling forecast cycles; published forecast must be exportable to Excel and PDF; system must prevent publishing until all business-unit sections are marked submitted.

US and UK teams have different compliance hooks, but the same control problem.

US teams usually care about clean evidence for audit support, vendor records, payment controls, tax reporting, and management review. UK teams usually care about VAT-ready records, approval evidence, digital-record discipline, and traceable postings. The country-specific details differ, but the operating pattern is the same: the ERP needs controlled records, explicit ownership, defensible state changes, and evidence that survives beyond the person who completed the task.

The control matrix.

Control areaRequirementAcceptance proof
Control 1Rolling window must automatically shift by one month on each cycle without manual reconfigurationGiven a closed GL period with imported actuals
Control 2prior actuals must be immutable once imported
when FP&A Analyst triggers a rolling forecast cycle dropping the closed month and appending the next out-month via POST /v1/forecast-cycles
Control 3driver-based lines must recalculate within 5 seconds of any input changethen a new 12-month forward window is created with prior actuals immutable, driver-based lines recalculate within 5 seconds of any input change, and the cycle blocks publishing until all business-unit sections are marked submitted
Control 4version history must be retained for at least 24 prior rolling forecast cycles
negative) when a business unit attempts to modify an imported actual period then 403 with error_code: actuals_immutable.
Control 5published forecast must be exportable to Excel and PDFUp-to-date 12-month forward P&L, cash flow, and headcount forecast available to CFO within 3 business days of month-end close.
Control 6system must prevent publishing until all business-unit sections are marked submitted.Up-to-date 12-month forward P&L, cash flow, and headcount forecast available to CFO within 3 business days of month-end close.

Audit evidence is a chain, not a folder.

Evidence layerWhat should be preserved
Business eventAt month-end close, FP&A Analyst triggers a new rolling forecast cycle that drops the just-closed month and appends the next out-month, maintaining a continuous 12-month forward view. Actuals from the closed GL period are automatically imported into the forecast baseline. Business Unit Finance Leads log in to revise their forward estimates for revenue drivers and headcount. The system re-calculates derived lines (gross margin, EBITDA) using configured formulas. FP&A Analyst reviews the consolidated P&L, flags material variances from the prior forecast, and publishes the updated forecast.
Control rulesRolling window must automatically shift by one month on each cycle without manual reconfiguration; prior actuals must be immutable once imported; driver-based lines must recalculate within 5 seconds of any input change; version history must be retained for at least 24 prior rolling forecast cycles; published forecast must be exportable to Excel and PDF; system must prevent publishing until all business-unit sections are marked submitted.
Acceptance proof
Given a closed GL period with imported actuals;
when FP&A Analyst triggers a rolling forecast cycle dropping the closed month and appending the next out-month via POST /v1/forecast-cycles;
then a new 12-month forward window is created with prior actuals immutable, driver-based lines recalculate within 5 seconds of any input change, and the cycle blocks publishing until all business-unit sections are marked submitted;
(negative) when a business unit attempts to modify an imported actual period then 403 with error_code: actuals_immutable.
Data record
forecast_cycle { id: fc_*, window_start: date, window_end: date, status: enum(OPEN/SUBMITTED/PUBLISHED), external_id: string };
forecast_line { id: fl_*, cycle_id: string, account_code: string, entity_id: string, period: date, amount_minor: int64, currency_code: char(3), is_actual: bool, external_id: string };
driver_input { id: di_*, cycle_id: string, driver_name: string, value: numeric, period: date, external_id: string };
(reference, product may differ).
System event
POST /v1/forecast-cycles { window_start, window_end, external_id } -> 201 { id, status: OPEN };
PUT /v1/forecast-cycles/{id}/driver-inputs { driver_name, value, period };
POST /v1/forecast-cycles/{id}/publish;
emits forecast.cycle_published event;
idempotent via external_id.
Lifecycle state
OPEN -> SUBMITTED -> PUBLISHED;
guard: PUBLISHED blocked until all business-unit sections status=SUBMITTED;
actual periods immutable once imported;
prior 24 cycles retained.

The useful version of this workflow is not only fast. It is inspectable. A controller, auditor, or operator should be able to move from source event to system record to state transition to final business outcome without guessing.

Implementation contracts.

Reference data model

`forecast_cycle` { id: fc_*, window_start: date, window_end: date, status: enum(OPEN/SUBMITTED/PUBLISHED), external_id: string }; `forecast_line` { id: fl_*, cycle_id: string, account_code: string, entity_id: string, period: date, amount_minor: int64, currency_code: char(3), is_actual: bool, external_id: string }; `driver_input` { id: di_*, cycle_id: string, driver_name: string, value: numeric, period: date, external_id: string }; (reference, product may differ).

API and events

`POST /v1/forecast-cycles` { window_start, window_end, external_id } -> 201 { id, status: OPEN }; `PUT /v1/forecast-cycles/{id}/driver-inputs` { driver_name, value, period }; `POST /v1/forecast-cycles/{id}/publish`; emits `forecast.cycle_published` event; idempotent via `external_id`.

State transitions

`OPEN -> SUBMITTED -> PUBLISHED`; guard: PUBLISHED blocked until all business-unit sections status=SUBMITTED; actual periods immutable once imported; prior 24 cycles retained.

Common implementation traps.

Treating the workflow as data entry

If the ERP only stores the final record, the team loses the decision trail that explains how the record became valid.

Hiding exception logic

Exceptions need owners, reason codes, and time stamps. A vague pending state is not a control.

Posting without recovery design

Retries, duplicate submissions, and partial failures must be explicit so the system does not create inconsistent records.

Skipping evidence design

A workflow that cannot produce evidence on demand will eventually push finance teams back into manual screenshots and spreadsheets.

Where Rivane fits.

Rivane is built for finance workflows where automation must stay tied to source documents, approvals, state transitions, ledger impact, reporting, and audit evidence. Use this guide as a checklist for evaluating whether an ERP workflow is merely digitized or actually controlled.

References and source basis.

These sources provide the standards, regulatory, or government context around the flow. They are included so the guide is useful to finance operators, auditors, and implementation teams, not only buyers reading software copy.

Back to ERP use cases