Ami Close
Runs the period-close checklist and flags unusual entries before the books close, not after.
A slow close is usually not about volume — it is about finding the errors too late. The agent runs the close checklist continuously through the period and raises unusual entries while there is still time to fix them.
Job in hand — here is what the agent does
You handed it over once, above. From there the agent watches the data, runs when a business event happens, does the part you delegated and brings the rest back with its evidence. This is what it has done — and what is still waiting for you.
Done by the agent — nobody had to ask
- Ran the declared close checklist
- Reconciled account balances to sub-ledgers
- Compared each cost line to the prior period
- Flagged entries outside the usual pattern
- Updated the status of every close step
Waiting on you
- Two cost items awaiting reallocationfor you to review
- Period-end adjusting entryfor you to approve
What is still open before we can close the books?
Two cost items are not yet allocated and one adjusting entry needs approval; the rest is done.
Close the steps that reconcile cleanly and leave the gaps to me.
Closed the reconciled steps and recorded the status of each one on the checklist.
The period-end adjusting entry is outside what you delegated — drafted and waiting for your approval.
Why are those two cost items out?
Both were booked to a different cost line than in previous periods. I have attached the original entries and last period's allocation so you can compare.
Audit log · Ami Close · delegated by Financial Controller
The figures in this example are illustrative. In production the agent creates no numbers — it reads and reorders what your system already holds.
- Reads inside your permissions
- Acts only where you delegated
- Every action leaves a trace
Where you meet the agent
- Right inside the module screenSuggestions appear beside the document you already have open, not in a separate app.
- Ask Ami in plain wordsType or speak, in the same language you already use across the system.
- Runs by itself when there is workFires on a business event and brings the work to you, instead of waiting for you to remember.
Where the agent gets its data
The agent has no data store of its own, syncs nothing outward and keeps no copy. It reads directly on the permissioned data layer the module already runs on — within the exact rights of whoever called it.
- Data leaves the company
- Permissions get rebuilt a second time — and can drift
- Figures lag behind the sync cycle
- Entries in the period and account balances
- The declared period-close checklist
- Prior-period figures for comparison
And where does the AI model run?
The diagram above is about where the DATA sits; this is about where the MODEL runs — two different things. Routing follows data sensitivity automatically; you do not pick per task.
See the hybrid AI modelAgents in the same group
Other agents on the same data layer — usually switched on together.
- Ami DocumentsReads incoming invoices and documents, runs the three-way PO–receipt–invoice match and proposes the journal entry.
- Ami ReceivablesTracks receivables and payables, ranks collection risk and drafts reminders based on payment history.
- Ami ContractsReviews risky clauses, compares them with your standard template and flags the differences before signature.
- Ami TuitionTracks tuition receivables by student and class, sends reminders on schedule and forecasts cash flow across the intake season.
- Ami ControlReviews off-budget spend, checks approval limits and assembles the audit file as it goes.
What this agent does not do
- It grants itself nothing.The agent pre-fills forms and can write to the system — but only within what you delegated; beyond that it stops at a suggestion.
- There is no data shortcut.The agent sees exactly what the calling account may see — no private connection of its own.
- It never acts anonymously.The log records which agent acted, under whose delegation and who approved — accountability stays with people.
How to switch this agent on
- Your company needs to be running the Finance & Accounting module — the agent reads that module's own data.
- No separate permission setup: the agent's rights are the rights of whoever calls it.
- Switched on and tuned during rollout, following your existing approval flow.
The exact scope and the order modules are switched on get settled in the demo, against your current setup.
Questions people usually ask
Can the agent change data on its own initiative?+
Not on its own initiative — but it does more than read. The agent pre-fills forms and writes to the system within exactly the scope you delegated to it; anything beyond that stops at a suggestion and waits for someone with authority. Either route, every action lands in the audit log.
What if the agent suggests the wrong thing?+
Every suggestion carries its evidence: which document, which line, and why. The reviewer edits or rejects it before anything is written — and both of those actions leave an audit trail too.
How is this different from a chatbot?+
A chatbot only answers when asked. An agent also takes a job you hand over once, then watches the data on its own, runs when a business event fires, and reports back — that is the half a chatbot never does.
How is this different from an automation flow?+
An automation flow runs the steps it was configured with. An agent reads business data, ranks it by situation and picks what needs doing — within exactly the scope you delegated, and anything needing approval still goes through your existing approver.
Does data leave the company?+
Tasks that touch sensitive data run on Internal AI placed inside your own infrastructure; only non-sensitive tasks use an external model. Routing follows the sensitivity of the data automatically.
See the agents run on your own data.
Book a demo scoped to the modules and industry you actually need.