Close tasks tracked, variances explained.
The Close Agent loads trial balance and your close calendar, scans GL accounts for material flux versus prior period and budget, ties variances to supporting detail where available, proposes accruals and amortisation entries, and reconciles intercompany pairs — each with journals waiting for controller approval.
How it works
The same pipeline you see in the live module, step by step.
- 1
Load period context
Import trial balance, prior period, and close checklist status. Map accounts to owners and materiality thresholds.
- 2
Run flux analysis
Calculate dollar and percent change per account. Flag accounts over materiality or with missing commentary from the prior close.
- 3
Explain drivers
Link large movements to sub-ledger detail, open AP/AR items, or manual journals. Draft variance narrative controllers can edit.
- 4
Propose adjustments
Suggest accruals, prepaid amortisation, and reclasses with debits and credits explicit. Enforce maker-checker before post.
- 5
Track the calendar
Update BD-minus timeline tasks as items clear. Surface blockers — unreconciled IC, open flux, pending approvals.
Worked example on demo data
Illustrative run on fictional Aster Bank data — not a customer result.
September flux on professional fees
- Account 6200 Professional fees moves from $375k to $517k month over month — above the 10% / $50k flux policy on the Aster Bank demo ledger.
- The agent ties $118,400 to legal matter LM-2026-14 that was incurred in September but not yet accrued.
- It drafts JE-2026-09-0931 for controller approval and marks the flux line explained in the close checklist.
Checks and rules
Deterministic logic on every action; optional intelligence enriches text when configured.
- Flux threshold by account class (percent and dollar)
- Required commentary on material accounts
- Prepaid schedule vs GL balance
- Intercompany pair balance to zero
- Suspense account aging
- Close task dependencies on calendar
What you get
Artifacts land in the shared finance record and activity log.
- Flux report with explained and unexplained buckets
- Proposed journal entries with approval chain
- Intercompany reconciliation worksheet
- Close calendar progress and blockers
- Audit-ready trace per account reviewed
Integrations (built during pilot)
- ERP trial balance and journal APIs (read-first)
- Sub-ledger detail for AP, AR, and fixed assets
- Close checklist tools or spreadsheet import
- Intercompany matrix from treasury
Where teams use Close Agent
All industriesQuestions
Does FinanceAI need live API access on day one?
No. Many pilots start with scheduled BAI2/MT940/CAMT.053 files and GL exports over SFTP. Read-only APIs come next once security review passes. The live demo uses the shared Aster Bank synthetic ledger.
What if Stellitron Intelligence is unavailable?
Every decision still runs through deterministic rules: amount matching, transposition checks, UBO percentage math, screening score thresholds, and flux materiality gates. Optional intelligence only improves extraction and narrative.
Who approves agent proposals?
Your org chart. Reconciliation journals route to treasury or accounting managers by amount. KYC dispositions require onboarding or BSA approval per your policy. Close entries respect maker-checker and each user's approvalLimit in the app.
Can it post directly to the GL?
Only after explicit approval and within the interfaces you enable in pilot. Default mode is propose-and-review; write-back scope is documented per connector.
How does this relate to reconciliation?
Reconciliation clears cash accounts; Close handles P&L flux, accruals, prepaids, and balance sheet accounts. Open cash exceptions can block close tasks until the Reconciliation Agent clears them.