Rivane

Accounting
made smart

ERP Use CasesTier 2Published April 13, 2026

Reforecasting Mid-Year

Reforecasting Mid-Year for US and UK finance teams: ERP requirements, controls, audit evidence, data model, APIs, state transitions, and implementation checks.

Reforecast / In-Year Forecast Revision is where ERP discipline either begins or breaks.

Reforecasting Mid-Year 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: Board-ready mid-year reforecast reflecting latest business reality, delivered within 5 business days of the reforecast trigger event.

The control flow a finance team actually needs.

Workflow map showing control steps, exceptions, and evidence for this ERP process.Reforecast Versi...Start conditionThe Clearly Labe...Required checksMultiple Reforec...Owner and SLAFull-Year Projec...System updateApproved Reforec...Exception handlingAudit packetEvidence trailException loopReforecast / In-Year Forecast Revision should preserve every override and rejection.
Workflow map for this ERP process, including exception handling and audit evidence.

Step 1

Reforecast Version Lock Prior-Period...

Step 2

The Clearly Label Which Periods Are...

Step 3

Multiple Reforecast Versions May...

Step 4

Full-Year Projected Vs. Original Budget...

Step 5

Approved Reforecast Replace The Prior...

The ERP surface involved.

Module

Reforecast / In-Year Forecast Revision

Actors

FP&A Manager, Business Unit Finance Lead, CFO

Tier

Tier 2

Finance area

Budgeting, Planning & FP&A

Region lens

US and UK finance teams

Publication date

April 13, 2026

Reforecast version must lock prior-period actuals as immutable and open only future periods for editing; the system must clearly label which periods are actuals versus forecast in all reports; multiple reforecast versions may coexist (e.g., Q2 reforecast, Q3 reforecast) without overwriting each other; full-year projected vs. original budget comparison must be a standard report view; approved reforecast must replace the prior forecast as the default comparison in budget-vs-actual reports (configurable); commentary fields must be required on accounts with a configurable variance threshold versus the original budget.

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 1Reforecast version must lock prior-period actuals as immutable and open only future periods for editingGiven H1 actuals locked in the reforecast version
Control 2the system must clearly label which periods are actuals versus forecast in all reportswhen Business Unit Finance Leads revise H2 estimates and FP&A Manager approves the reforecast
Control 3
multiple reforecast versions may coexist (e.g., Q2 reforecast, Q3 reforecast) without overwriting each other
then system displays H1 actuals as immutable, H2 as editable, full-year projected P&L as H1 actuals + H2 reforecast, and commentary is required on accounts with variance versus original budget exceeding threshold
Control 4full-year projected vs. original budget comparison must be a standard report view
negative) when a Finance Lead attempts to modify an H1 actual period then 403 with error_code: actuals_immutable.
Control 5approved reforecast must replace the prior forecast as the default comparison in budget-vs-actual reports (configurableBoard-ready mid-year reforecast reflecting latest business reality, delivered within 5 business days of the reforecast trigger event.
Control 6commentary fields must be required on accounts with a configurable variance threshold versus the original budget.Board-ready mid-year reforecast reflecting latest business reality, delivered within 5 business days of the reforecast trigger event.

Audit evidence is a chain, not a folder.

Evidence layerWhat should be preserved
Business eventAt mid-year (or upon a material business event), CFO instructs FP&A Manager to produce a full-year reforecast. FP&A Manager opens a new reforecast version that locks H1 actuals and opens H2 for revision. Business Unit Finance Leads log in to revise their H2 estimates based on updated pipeline, hiring plans, and known cost changes. System recalculates the full-year projected P&L by summing H1 actuals and H2 reforecast. FP&A Manager compares the reforecast against the original annual budget, highlighting lines where the expected full-year outcome differs materially. CFO reviews and approves the reforecast, which becomes the new performance benchmark for the second half.
Control rules
Reforecast version must lock prior-period actuals as immutable and open only future periods for editing;
the system must clearly label which periods are actuals versus forecast in all reports;
multiple reforecast versions may coexist (e.g., Q2 reforecast, Q3 reforecast) without overwriting each other;
full-year projected vs. original budget comparison must be a standard report view;
approved reforecast must replace the prior forecast as the default comparison in budget-vs-actual reports (configurable);
commentary fields must be required on accounts with a configurable variance threshold versus the original budget.
Acceptance proof
Given H1 actuals locked in the reforecast version;
when Business Unit Finance Leads revise H2 estimates and FP&A Manager approves the reforecast;
then system displays H1 actuals as immutable, H2 as editable, full-year projected P&L as H1 actuals + H2 reforecast, and commentary is required on accounts with variance versus original budget exceeding threshold;
(negative) when a Finance Lead attempts to modify an H1 actual period then 403 with error_code: actuals_immutable.
Data record
reforecast_version { id: rfv_*, budget_version_id: string, name: string, lock_through_period: date, status: enum(OPEN/APPROVED), external_id: string };
reforecast_line { id: rfl_*, version_id: string, account_code: string, entity_id: string, period: date, amount_minor: int64, currency_code: char(3), is_actual: bool, commentary: string, external_id: string };
(reference, product may differ).
System event
POST /v1/reforecast-versions { budget_version_id, name, lock_through_period, external_id } -> 201 { id, status: OPEN };
PUT /v1/reforecast-versions/{id}/lines/{line_id} { amount_minor, commentary };
POST /v1/reforecast-versions/{id}/approve;
emits reforecast.approved event;
idempotent via external_id.
Lifecycle state
OPEN -> APPROVED;
guard: APPROVED replaces prior forecast as default comparison in budget-vs-actual reports (configurable);
H1 actual periods are immutable;
multiple reforecast versions coexist without overwriting.

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

`reforecast_version` { id: rfv_*, budget_version_id: string, name: string, lock_through_period: date, status: enum(OPEN/APPROVED), external_id: string }; `reforecast_line` { id: rfl_*, version_id: string, account_code: string, entity_id: string, period: date, amount_minor: int64, currency_code: char(3), is_actual: bool, commentary: string, external_id: string }; (reference, product may differ).

API and events

`POST /v1/reforecast-versions` { budget_version_id, name, lock_through_period, external_id } -> 201 { id, status: OPEN }; `PUT /v1/reforecast-versions/{id}/lines/{line_id}` { amount_minor, commentary }; `POST /v1/reforecast-versions/{id}/approve`; emits `reforecast.approved` event; idempotent via `external_id`.

State transitions

`OPEN -> APPROVED`; guard: APPROVED replaces prior forecast as default comparison in budget-vs-actual reports (configurable); H1 actual periods are immutable; multiple reforecast versions coexist without overwriting.

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