Month-end close tracker
The close is a checklist held together by chasing. This agent reads the close checklist and the folders the evidence lands in, works out what has arrived and what has not, and drafts the status note. The financial controller approves it before it is posted to the team.
Step by step
Read the close checklist
The agent takes the checklist your team already uses, in whatever wiki or workbook it lives in, and treats it as the definition of what is due.
Match evidence to each item
It looks in the connected folders for the reconciliation, statement or schedule each item expects, and records what it found.
Flag the outstanding gaps
Items with nothing attached, or with a document from an earlier period, are listed as outstanding with the owner named.
Surface the unresolved questions
Where an item has support but a note says it is still open, the agent carries that note forward instead of marking the item done.
Draft the status note
A short note is drafted in your team's format: what is complete, what is outstanding, what is blocked and by whom.
The controller approves the note
The financial controller reviews and approves. Only then is the note posted to the finance channel.
Exactly what this agent can see, touch and change
The same five controls sit behind every ollo agent. These are this one's settings — visible before you build it, not buried in an admin screen afterwards.
Context
What reaches the modelFinancial controllers and close managers running a monthly close across several entities or teams, where evidence arrives in different places from different people.
Escalation
When it asks a personThe financial controller approves the status note before it is posted
Applications & Rights
Which tools it uses, and what it may do in each
Google DriveRead only
SharePointRead only
JiraRead only
SlackReadWrites newCreates new records or documents. Never edits, moves or deletes anything that was already there.Verification
How you know it’s rightEvery claim links to the document it came from. A statement the agent cannot cite does not make it into the output — which is what makes the result reviewable in minutes rather than re-read end to end.
Who it’s for
Financial controllers and close managers running a monthly close across several entities or teams, where evidence arrives in different places from different people.
What you’ll need
- The close checklist in a connected source
- The folders where evidence is filed
- A named owner per checklist item
- A controller to approve the note
What you get
- A checklist status view
- An outstanding items list with owners
- A drafted close status note
What it doesn’t do
It tracks and reports on the close. It does not post journals, sign off a reconciliation, or judge whether the support it found is sufficient. A person still reviews the evidence.
We build the first one with you
Not a template you configure alone. We sit with your team, build it on real data, and hand over the controls.
Scope
One session with the people who actually do the work. We agree what the agent reads, what it may write, and who approves.
Co-build
Built on your own data, not a sandbox. You watch it being made, so you know why it behaves the way it does.
Handover
You own the controls. Change the context, tighten the rights, move the approval gate — without coming back to us.
Parts of the work currently spread across the categories below. It does not replace any of those products outright.
Frequently asked
Does it decide whether an item is complete?
No. It reports what it can see: an expected document that is present, absent, or from the wrong period. Whether the support is good enough is the reviewer's call, and the agent never marks an item signed off.
Our checklist lives in a spreadsheet. Is that a problem?
Not as long as it sits in a connected drive. We map the columns during the co-build so the agent reads your checklist, rather than asking your team to adopt a new one mid-close.
What about entities that close on different days?
Each entity keeps its own checklist and calendar, and the note can be produced per entity or combined. Where the agent could not see evidence for an entity, it says so rather than reporting a single blended position.
Can it chase people directly?
It drafts the chase and names the owner, and the controller decides whether it goes out. Teams usually start with a single note in one channel and add direct chasing later, once they trust what it flags.