A close coordinator that works the checklist with your team.
The close coordinator follows the checklist your controller follows today. It checks each task against the ledger, chases owners inside the organisation, and posts only the entries its level allows.
The close calendar: every task, its owner and its deadline, in your close tool or task list.
It reads the ledgers and the close checklist. It writes task status, internal messages to owners and, once trusted, recurring accruals.
You set materiality and the entries in scope. It posts recurring accruals below materiality and proposes everything else for approval.
It never reassigns a task, never posts a one-off adjustment and never signs off the close. Ownership and sign-off stay with people.
“Keep the month-end close on schedule. Check each task against the ledger, chase owners before deadlines, post recurring accruals below materiality when trusted, and tell the controller early what will slip. Report to the financial controller.”
The floors no configuration can weaken
Seven limits sit under every level, level 5 included. Your own limits can only tighten them.
A person decides. The threshold is yours to lower, never to remove.
Nothing is signed, agreed, or terminated without a person.
A relationship is not a record to be closed. It stops with a person.
Reporting lines, roles, and who is accountable are set by people.
No AI employee can raise its own level or anyone else’s.
Anything leaving the organisation is gated, whatever the level.
Handled under your rules, with a person deciding on anything that acts on it.
An accrual posted below materiality, and a late task escalated in time.
Both records show what it knew on the day, so the close can be replayed exactly as it ran.
Handoff on the record: the controller moved the task, and the coordinator picked up the new owner and deadline from the record.
The controller chases owners from a spreadsheet.
Owners are chased before deadlines, and the controller sees only what is at risk.
A task marked done is taken on trust.
Done means checked against the ledger, with what it found attached.
Recurring accruals are keyed by hand every month.
Recurring accruals below materiality are posted once it has earned it.
Two weeks on last month’s close.
It proposes a status and an action for every task in last month’s close. You compare its proposals with what actually happened, and nothing in your systems changes.
Two-week retrospective evaluation
You see which tasks it would have marked done, chased or escalated, and which accruals it would have proposed, with what it found in the ledger.
Budgeted like an operational role · Zero token metering
Expenditure is tied to completed operational outcomes, not token consumption or prompt volume. A high-volume month or quarter never generates a variable surprise bill, providing fixed annual forecasting for CAIOs, CFOs, and Procurement leads.
Month-end close
The pilot role. Routine tasks marked done and owners chased, everything at risk escalated.
Control monitoring
Tests financial controls on schedule and raises every failure to its owner.
Spend approvals
Decides purchase requisitions within budget, policy and its band.
