Input extraction
Recover candidate inputs with their source references and methods.
FP&A agent system · on Olbrain
Inputs arrive from different owners. Assumptions need review. Management needs a clear explanation of what changed. Bring that work into one system, with finance in control.
Phase 1 built · awaiting validation and demonstration · paid production not yet established
FP&A · built on Olbrain
From an operating input to a forecast you can explain. Agents prepare the work; finance controls what becomes part of the plan.
An input carries its source reference, owner and method. Finance can review where a number came from.
The agent extracts a candidate value and explains its basis. A proposal does not change the forecast.
Finance reviews the evidence and accepts the input. Only accepted changes apply.
The financial engine computes the numbers from confirmed inputs and approved formulas. Agents help with the work around the calculation.
A run preserves the input and calculation state. Later changes create another run; they do not rewrite this snapshot.
Explore a scenario and explain its movement: revenue rises ₹12,000 with price held constant. Reporting uses a selected run and templates with mapping and review before release.
Six agents · one objective
Recover candidate inputs with their source references and methods.
Help identify gaps and follow up for the information the forecast needs.
Surface assumptions for finance to assess and confirm.
Investigate changes and connect the explanation to the underlying inputs.
Prepare an explanation of the selected forecast for finance review.
Handle forecast questions and explore scenarios with the finance team.
An orchestrator coordinates the work. Only accepted input changes apply; a deterministic financial engine computes the P&L from human-confirmed inputs and approved formulas. Each run is an immutable snapshot, preserving a basis for comparison and review.
Management reporting comes from a selected run and templates. Mapping, template completion and review happen before release. Finance retains the assumptions, approvals and judgment.
Current work and next steps
Reproduce the existing forecast process and financial model. Validate the numbers with finance, demonstrate the system and establish management approval. No time-saving or forecast-accuracy gain has been measured.
SAP HANA actuals integration is requested next. Evaluate forecasts against actuals to test accuracy. Further agents are planned for 24 drivers, including sales, inventory and raw materials.
Continuously refresh a driver-based outlook, extend its horizon as time advances, and explore management decisions. Refresh speed depends on reliable data and approvals; the live outlook remains distinct from approved reporting snapshots.
The reusable operating layer
FP&A brings the Agent OS into view. Olbrain connects the agents, business tools and human workspace around one objective.
Coordinate specialist agents, tool calls and human decisions across a process.
Connect deterministic engines and business tools to the work agents prepare.
Bring the required data into a system with source references and integration boundaries.
Define what may happen and where a person must review or accept a change.
Carry workflow context and preserve records that support review and attribution.
Give people a place to inspect evidence, compare outputs and decide what happens next.
The same foundation supports lending operations and research. Their customer stages differ: lending agents are in UAT or requirements, with the programme on hold; the first research agent is tested, with paid conversion still open. Reuse supports further systems, while integrations and domain rules still need validation.
Explore the Agent OS →Start with your process
Discuss the inputs, formulas, review decisions and reporting that your first system needs to reproduce.