Skip to content

Department · Finance & Controlling

The current rule should arrive before the old spreadsheet.

Versioned rules, approvals, and budget exceptions, with provenance for audit and the current assumption delivered to the analysis agent.

Start using it

Scenario

How context circulates when ValorBrain is in the flow.

  1. 01

    The BRL/USD planning rate of 5.40 is updated by controlling and becomes a fact with as_of and an owner.

  2. 02

    The new value supersedes the previous one without erasing it: history stays queryable by date.

  3. 03

    The analysis agent receives the assumption in force, not the one on the March spreadsheet still circulating.

  4. 04

    The extra budget approval for the cost center goes in as an exception, with who approved it and until when it holds.

  5. 05

    A later query retrieves the record with its source instead of depending on the approver's inbox.

  6. 06

    Once expired, the exception stops being an answer.

  7. 07

    The auditor asks which assumptions held on a given date and receives the history with sources and versions.

  8. 08

    The provenance chain shows where each number came from and who read what.

  9. 09

    Audit time goes to judgment, not to hunting down versions.

Frequently asked questions

We have an ERP and spreadsheet-based close.

The ERP stays the ERP. The Granatum connector and spreadsheet ingestion come in as sources, and ValorBrain organizes assumptions, approvals, and exceptions to deliver the current one to the agent.

What if someone records a wrong assumption?

An off-spec record goes to SHACL quarantine before reaching any answer, and contradiction between sources is flagged for human review. Controlling's validation still matters.

Does this replace the accounting close?

No. ValorBrain organizes and delivers the context of what holds, when it holds, and who approved it. The close stays in the ERP and in controlling's processes.

Who can see financial data?

The agent inherits the permissions of whoever uses it, per person and per source. Sensitive scope stays isolated per tenant, and every read is logged in the audit trail.

Next step

Less starting over. More continuity

Bring a real project. In one conversation we map where context gets lost between the people and agents on your team, and where to start.

Start with a project