Every sub-ledger. One cockpit.
One closed book.
Rohan is a controller at a four-entity manufacturing company. It’s close day. He uploads every sub-ledger — AR, AP, bank, intercompany, fixed assets, inventory. Forty-seven minutes later all six are tied out, the journal entries are approved, the books are certified, and the CFO pack is ready. Here’s how it actually runs.
Five named agents do the work — same names you’ll see in the chat agent and the audit log. Each one owns one or two stages of the close.
Close day opens itself — every sub-ledger lands
The period auto-opened on day one with the checklist already seeded. Now the inputs arrive: bank statement, AR and AP aging, the intercompany ledger, the fixed-asset register, and the inventory valuation. Rohan uploads them as-is — no cleanup, no header renaming, no row pruning. Six sub-ledgers, one workspace, before his second coffee.
Every source typed — no column mapping, on any of the six
Iris recognises each shape in turn — AR aging, AP bills, bank lines, the intercompany legs, the fixed-asset register, and stock movements. Field roles (amount, date, counterparty, key) are tagged per source automatically. No manual column mapping, on any sub-ledger.
Six tie-outs, one cockpit
Six sub-ledgers reconcile to the GL together. Argus proposes the matching rule per domain — UTR for bank, the mirror pair for intercompany, and a SUM_AGGREGATE rule for the many-to-one cases (AR and AP, where many invoices or bills net into one entry). Rohan approves once; the rules are reusable next month.
on_field: amount
partition_by: counterparty
tolerance: ₹100 + 0.5%
date_window: ±7 days
The hardest case: subset-sum across the close
ACRE runs exact then fuzzy matching across all six tie-outs, then Stage 1.5 — the aggregation blocker — handles the case spreadsheets can't: subsets of invoices or bills summing to one GL entry within tolerance. Twelve AR invoices snap to a ₹25 lakh JE in 240 ms; the same engine clears AP, bank, intercompany, fixed assets and inventory in parallel.
Want to see twelve of your AR invoices snap to one of your GL entries? Bring last month’s extracts.
Run subset-sum on your ledger12 AR invoices, summed to one GL journal entry — in seconds, within tolerance.
Triage, prep, and one approval inbox
What doesn't match becomes work — routed, not dumped. Argus triages the breaks across domains, drafts the prepaid amortization and GRNI accrual entries, and lands everything — journal entries, accruals, rule changes, CoA edits — in one approval inbox. AI proposes; Rohan approves the entries that move the books. Nothing closes itself.
It remembers — and it chases
Clio remembers across runs: a late-settling counterparty is tagged LATE_SETTLER_AVG_4D after three confirmed cycles and auto-links next month before Rohan sees it. The settlement workbench runs alongside — it catches two duplicate vendor payments and drafts the AR collection chase-ups for Rohan to send (it never sends them itself).
Certified, packed, and closed
Certification readiness marks 18 of 21 control accounts machine-verified clean; budget-vs-actual flux names what moved. Rohan signs off, Hermes marks the period CLOSED, exports the approved journal entries as Tally XML, and assembles the CFO close pack — a board one-pager of tie-out status, blockers, judgments, and sign-offs.
- Wall time
- 47 min
- Certified
- 18 / 21 accounts
- Reviewer
- Rohan K · Controller
- Approver
- Priya S · CFO
- rows processed
- 11,240
- tie-outs
- 6
- approvals reviewed
- 4
- wall time
- 47 min
- CFO pack
- 1
What controllers actually ask after walking the journey
Is the controller (Rohan) approving every match by hand?
No. ACRE's aggregation candidates land in a review queue with a confidence score. High-confidence groups can be approved in bulk; only edge cases — wrong vendors, unexplained residuals outside tolerance — require a click. The 47-minute cycle includes the human review time, not just the engine time.
What happens if next month the SUM_AGGREGATE rule needs tweaking?
Argus surfaces tolerance drift when the residual band creeps. The rule is editable; every edit is versioned in the audit log with reviewer, timestamp, and reason. Old runs replay against their historical rule version — reruns stay deterministic.
Does the memory layer ever auto-close exceptions without me looking?
Only after three confirmed cycles of the same fingerprint pattern, and only when a counterparty is tagged (e.g. LATE_SETTLER_AVG_4D). The first auto-close on a new pattern lands as a notification, not a silent action — you can revoke the tag from the counterparty intelligence panel.
Can I run this journey on my own ledger before signing anything?
Yes. The Week-1 plan on the FinanceOps overview page is exactly that — replay your last closed period's AR-to-GL on ReconPe, compare match rate and time-to-close against your spreadsheet, and only commit if the numbers tie.
Does it really run all six tie-outs, or is AR the only real one?
All six are live today — AR-to-GL, AP-to-GL, bank-to-GL, intercompany, fixed-asset-to-GL, and inventory-to-GL — and they run in the one cockpit you just walked. GSTR-2B reconciliation lives on the separate GST surface, not inside the close cockpit. We don't claim shipped what isn't — and these six are.
Next month’s close runs on this month’s memory.
Every confirmed match, every approved subset, every learned pattern carries forward. Your close gets faster every period — without your team writing a single line of code.