Close Reconciler · AI agent | Built AI

It reconciles every source the moment the period closes

A ten-day close is mostly waiting on reconciliation. The Close Reconciler collapses that by tying the GL to Argus and the model continuously, so by the time the period closes the breaks are already surfaced and the entries already proposed.

A period closes

The end of a reporting period is the trigger to reconcile every source against the others.

It does the work

Reconciles, surfaces, proposes

It ties GL actuals to Argus and the model, surfaces the breaks ranked by size, and proposes the journal entries.

Then it stops

The controller signs off

Every proposed entry waits for a controller. Nothing posts to the ledger without a named human approving it.

The pipeline

A period close in, proposed entries out

  1. Period close
    The end of the period triggers a full cross-system reconciliation.

  2. Reconcile sources
    GL actuals tied to Argus and the model, line by line, on the engine.

  3. Surface breaks
    Differences ranked by size, each traced to the two figures that disagree.

  4. Propose entries
    Journal entries drafted to clear the breaks, then held for sign-off.

Continuous tie-out means the close starts with the breaks already found, not with a blank reconciliation.

See it work

One run, every figure cited

Ask the Close Reconciler to run the period. It returns what matched, the breaks ranked by size, and a set of proposed entries, with both sides of every break traced to source.

Close Reconciler · AI agent
Tenant: Finance & IR

Reconcile the June close for Fund III.

Close Reconciler

Tied 1,184 of 1,191 lines across GL, Argus and the model. 7 breaks remain.

Largest break: $42k recoveries timing between GL and Argus on Block 37.

Proposed 5 journal entries to clear the timing and rounding breaks. draft

Two breaks flagged for review: they need a judgment, not an entry.

The boundary

It drafts and computes, then it waits

It can propose the entries. It cannot post them.

The Close Reconciler does the tie-out and drafts the entries, but posting to the ledger is an irreversible act, so it waits for a controller. The breaks that need judgment rather than an entry are flagged as exactly that.

The boundary, in one line

Trigger: a reporting period closes. Human approval: a controller signs off the entries. What it cannot do: post to the ledger without approval.