Rebalance audits that produce the evidence, run by run.

Turn nightly rebalance and reconciliation checks into a governed workflow where AI reconciles, a person approves exceptions, and the record is ready for the auditor.

A portfolio operations analyst's hands checking a printed positions report against on-screen charts, a pen resting on one flagged line.
§ 01 · How it works

One run, end to end.

Kora runs rebalance and reconciliation audits as governed workflows: agentic checks reconcile positions and flag breaks, a person approves the exceptions, and each run produces a hash-chained, replayable record that an auditor can accept.

  1. Scheduled

    The nightly run starts

    Positions and targets load from the systems you already run, under the released process version.

  2. AI agent

    The agent reconciles

    It checks positions against targets and tolerances, clears what matches, and flags each break with its context.

  3. Approval

    A person clears the breaks

    Genuine exceptions route to their owner with the evidence attached. Nothing is cleared silently.

  4. Record

    The run becomes evidence

    Inputs, checks, decisions, and outcomes land in the append-only record, ready for the auditor.

One record per nightly run: the checks, the breaks, who cleared them, and why. Hash-chained, replayable.

§ 02 · The approach

Rebalance audit

What you get

  • A run that takes the same path nightly

  • Breaks cleared by their owner

  • The audit trail is the run itself

01

Reconciliation as a governed run

The nightly check is a released workflow, so every run follows the same path and produces the same evidence, rather than a script whose behavior drifts over time.

02

Breaks route to a person

The agent reconciles and proposes, and genuine exceptions go to an owner with the context attached instead of being cleared silently.

03

Auditor-ready by construction

Inputs, checks, approvals, and outcomes land in a hash-chained, replayable record, so the audit evidence exists the moment the run finishes.

§ 03 · FAQ

Questions, answered.

What teams ask when they evaluate Kora for this problem.

A hash-chained, replayable record of the positions reconciled, the breaks found, the agent's proposal, the person who approved, and the outcome, tied to the process version that ran.

No. The agent reconciles and proposes a resolution, but a person approves exceptions before they are cleared. The record shows both.

A script leaves you reconstructing what happened from logs. A governed workflow captures the run itself, under release control, with approvals and evidence as first-class parts of the process.

No. The workflow reads positions and targets from the portfolio, accounting, and custodian data you already run, executes the governed checks, routes exceptions to their owners, and writes results back. Kora governs the audit path and its evidence; your systems of record stay in place.
§ 04 · Next step

Bring one nightly check.

In a demo, bring a rebalance or reconciliation check you run today. We will run it as a governed workflow: the agent reconciles, a person clears the breaks, and you see the auditor-ready record each run leaves.