Month-End Close Agent
Reads the reconciliation, not the tick beside it
- 8hard rules
- Things it must never do, enforced in every run
- 5handover rules
- Conditions where it stops and gives the work to a person
- 11output fields
- A structured result, not a paragraph you have to re-read
- ≤8steps per run
- Bounded work: at most 7 tool calls, enforced by the runtime
Read-only by design. This agent has no path to sending, spending, publishing or committing anything. Where that limit is the product, removing it would remove the reason to trust the output.
Overview
Close takes a week every month, runs the same checklist, and is late more often than not. The software that exists tracks whether a task was ticked — which is project management, not accounting, and it misses the failures that cost money.
A reconciliation can be marked complete and not reconcile. A balance can be signed off with an unexplained difference inside it. A journal can be posted that nobody can now explain, and an accrual can be carried forward for eleven months because it is easier than asking. All four pass a checklist. All four are found in year-end fieldwork, when fixing them costs ten times more.
This agent runs the close as a process and reads the work as an accountant would. It knows your timetable and who owns each task, reports what is late and what is blocking what, and checks the substance: whether balances agree, whether differences are explained, whether an accrual has a basis, whether this month looks like last month for reasons anybody recorded. It posts nothing and approves nothing — every finding goes to the person whose name is on the close.
Benefits
Close on the day you planned
Because what is late is visible on day two, not day seven.
Findings before the auditor
When fixing them is a journal rather than a restatement.
The same standard every month
Including the month the person who normally does it is away.
What it does
Reads the work, not the tick
A reconciliation marked complete that does not reconcile passes every close tracker on the market and fails an audit.
Runs the whole timetable
Every task, owner, dependency and deadline from your own close calendar — what is late and what it blocks.
Finds the unexplained difference
A balance signed off with a residual inside it. The single most common audit finding there is.
Catches the accrual nobody revisits
Carried forward for eleven months because asking is harder than rolling it.
Compares against last month
Movements nobody has explained, and accounts that did not move when they always do.
Posts nothing, approves nothing
Every finding goes to the person whose name is on the close. It has no path to the ledger.
What this changes
What this changes about your week
- It takes over
- Chasing the close by hand: who has done what, and re-checking the reconciliations that came back.
- Done today by
- The financial controller, for a week, every month, forever.
- How often
- Monthly, and the same week is lost each time.
- Typical manual effort
- Five to ten working days of a finance team, and late more often than not.
Why Finance & Accounting in particular. Every close tool on the market tracks whether a task was ticked. A reconciliation can be marked complete and not reconcile — that passes a checklist and fails an audit, and it surfaces in year-end fieldwork when fixing it costs ten times more.
Runs unattended
Started by you or by an event, and it finishes on its own. Nothing waits for someone to be at a desk.
The same standard every time
The two-hundredth item is held to the bar the first one was. Consistency is the part people cannot sustain.
It cannot act on its own
Month-End Close Agent has no path to sending, spending or committing. That limit is why its output is safe to act on.
How it runs
This agent runs server-side through the PROMIVO runtime. Each run is logged step by step and every tool call is permission-checked before it executes.
- 1InputValidated against the agent input schema
- 2Modelclaude-opus-5 with automatic fallback
- 3Toolssearch_knowledge, extract_structured_data
- 4PermissionsRuns READ actions automatically; anything higher waits for approval
- 5OutputStructured result matching the output schema
- 6LoggingTokens, duration and every step recorded
Demo
Demo dataIllustrative sample output, abridged.
Input
{
"period": "August 2026",
"currency": "USD",
"materialityThreshold": 5000
}Output
{
"escalate": true,
"disclaimer": "A review of the close as performed. Nothing has been posted or approved, no accounting judgement has been made, and this is not a statement that the accounts are correct or audit-ready.",
"closeStatus": {
"late": 4,
"blocked": 2,
"complete": 31,
"onCriticalPath": [
"Bank reconciliation — late, and revenue cut-off cannot start without it."
],
"forecastCloseDate": "Working day 9 against a planned working day 6, unless the bank reconciliation lands today."
},
"forJudgement": [
"Whether the accrued income difference is a timing item or an error. The facts are above; the call is yours."
],
"timetableFound": true,
"accrualFindings": [
"Legal fees accrual of 12,000 carried for 11 periods. Your policy supports three."
],
"journalFindings": [
"Three entries totalling 60,000 posted two days after the stated cut-off, by a preparer who posts no other journals.",
"One entry of exactly 25,000 with no narrative."
],
"escalationReason": "A reconciliation was marked complete carrying an unexplained difference above materiality, and journals were posted after cut-off.",
"movementFindings": [
"Repairs is flat at 4,200 for the fourth month running. An account that never moves usually means something is being posted elsewhere."
],
"auditWouldRaiseFirst": [
"Accrued income signed off with an unexplained 18,400 inside it.",
"Post-cut-off journals by an unusual preparer."
],
"reconciliationFindings": [
{
"issue": "unexplained-difference",
"account": "Accrued income",
"difference": 18400,
"markedCompleteAnyway": true
}
]
}Requirements
Integrations
No integrations required.
Before you start
- A knowledge base holding your close timetable and accounting policies
- The period's trial balance, reconciliations and journals
- Requires the All-Access plan or higher
Use cases
Running the close
Daily status: what is late, what it blocks, what needs a person.
Pre-audit review
What fieldwork will find, while it is still cheap to fix.
A new finance lead
Learn what this close actually involves and where it breaks.
Pricing
All-Access
Billed monthly through your PROMIVO subscription. Cancel at any time.
Runs consume your plan allowance for agent executions and tokens. See plan limits
FAQ
Does it post journals?
No, and it has no path to your ledger. It reads and reports. A journal carries the name of the person who posted it and that must stay true.
How is this different from close-management software?
Those track whether a task was ticked. This reads whether the work behind the tick is right — whether the balances agree, whether the difference is explained, whether the accrual has a basis. Opposite jobs.
Does it replace the accountant?
No. It finds what an auditor would find first and hands it to them. Judgement about a provision or an estimate is theirs, and it will not offer one.
What does it need?
Your close timetable and policies in a knowledge base, plus the reconciliations, trial balance and journals for the period. It works from what you already produce.
Reviews
Reviews open once customers have run this agent.
Need this agent to work differently?
Tell us what to change and our team will scope a customised version for your business.
Customize this agent