ERP
Month-end close
4 hrs
was 9 days
- Owner
- Financial Controller
- Cadence
- Runs nightly from day −2
- System
- ERP
Close is not one task. It is four hundred small ones, most of which are the same every month, performed by people who are too senior to be doing them at eleven at night.
What the agent does
Anvil starts two days before close. It reads open items across every entity, matches them against the close checklist your team already maintains, and posts what is unambiguous — accruals with a prior-period pattern, intercompany balances that net to zero, recurring journals with an unchanged basis.
- 41 journal entries posted per entity on an average month
- 3 to 9 exceptions raised with the reasoning attached
- Every posting reversible from the ledger, by batch
What it does not do
It does not decide materiality. It does not sign anything. Anything outside the checklist becomes an exception with a named owner and the evidence it used, and it waits.
The first month it ran, it found a recurring accrual we had been posting twice since a 2024 reorganisation.
Getting there
Two weeks. One week connecting to a sandbox copy of your tenant and reading a completed close, one week running in parallel against the live one while your team watches the ledger and disagrees with it.
Other runs
- P2P Three-way invoice matching Invoice against purchase order against receipt, with contract terms checked and duplicates held before the payment run.
- ITSM Access reviews The quarterly attestation pack assembled from the real entitlement data, with dormant accounts revoked on the same run.
- HCM Joiner and leaver runs Policy answers, benefits changes and the twenty-three tasks that follow a start date, filed against the right records.
- FIN Variance packs Actuals against budget across every entity, with the flux commentary drafted from the underlying transactions.