
Automating month-end close
How Mercury Digital’s agents reconcile through the period, draft entries with support attached, and route every posting to your controller for sign-off.
The short answer
Why close is a scramble today
The checklist only starts once the period shuts. Accruals get rebuilt from memory of last month, support gets chased after the fact, and everyone already knows which accounts will break. The work piles up behind a calendar date, not because it's hard, but because none of it started earlier.
With a Mercury Digital agent
AI can automate much of the month-end close legwork for a small finance team by doing the reconciling during the period instead of after it. With Mercury Digital, an agent watches the subledgers, matches accounts as items post, drafts recurring and accrual entries with their support attached, and flags variances with evidence. Nothing posts until your controller signs off.
What changes with an agent: before and after
| Close task | Typical manual close | With a Mercury Digital agent | Who decides |
|---|---|---|---|
| Bank and subledger reconciliation | Done in a batch after period end | Matched continuously as items post. The matched state is kept up to date. | Agent matches; a person reviews unmatched items |
| Close checklist | Spreadsheet or one person's memory | Built automatically, with live status per item before period end | Controller owns the checklist |
| Recurring and accrual entries | Rebuilt from last period by hand | Drafted from the prior-period pattern, with support attached | Controller approves each entry |
| Variances and unmatched items | Found late, explained later | Flagged when they happen, with source records attached | Accountant or controller resolves |
| Journal entry posting | Posted by preparer | Gated. Nothing reaches the ledger without a named person's sign-off | Controller (always) |
| Audit support file | Reassembled for the auditor | Assembled during the period | Controller signs the close package |
How it works, step by step
Monitor the period
Reconcile continuously
Keep the checklist live
Draft recurring and accrual entries
Flag variances with evidence
Hold the human gate
File support as it goes
Guardrails for an agent that touches financial data
Read and write scopes are separate
The agent gets read access to the records it reconciles. Write access covers only entries a person has approved.
Named approver per gate. The gate belongs to the controller by name, not to "finance." See approval gates.
Shadow mode first
The agent runs next to your current close and its output is compared with what your team actually booked. Under Mercury's standard policy, it acts on its own only after it has run in shadow for at least 50 items of each type and at least 2 weeks, with 95%+ agreement with the human reviewer and zero critical errors. See shadow mode.
Rules written down, judgment routed
Accounts that "always break" get written rules once. Anything the rules can't decide goes to a person and is never guessed.
Everything is logged. Every match, draft, flag and approval is recorded with who decided and when.
Where this fits
This is a Tier 1 engagement (Automate a Workflow): one process, end to end. Close is a strong first candidate because it repeats, most of its rules are already written somewhere, and it already ends in a sign-off.
What to measure. Days to close (period end to signed close package), the share of reconciliations matched before period end, the number of open checklist items at period end, and how many drafted entries the controller approves without changes. Mercury sets a baseline for these in week 1 and reports against it.
How this compares with close-management software (FloQast, BlackLine)
FloQast and BlackLine are close-management platforms you license. Their product pages describe close checklists, account reconciliations, transaction matching and journal-entry workflows, and both now market built-in AI agents that prepare reconciliations, flag exceptions and draft entries for human review (FloQast Close Management, FloQast; BlackLine Financial Close, BlackLine). Mercury Digital isn't a replacement category. It builds and runs a custom agent for your close inside the systems and tools you already use, with your controller's sign-off as the control. Some teams will want the platform, some a custom agent, and some both.
| Question | Close-management platform | Mercury Digital agent build |
|---|---|---|
| What you get | A licensed product your team operates | A governed agent workflow built for your close, run on your cloud |
| Who does the matching and drafting | Your team, inside the platform, plus the platform's own automation and AI agents | The agent, with people reviewing exceptions and approving entries |
| Fits best when | You want a standard close system of record | Your close rules live in spreadsheets and people's heads, and you want the legwork done for you |
| Human control | The platform's review, approval and sign-off workflows | A named human gate on every posting, closed by default |
Product descriptions checked against the vendors' own pages on Oct 27, 2026. Features and packaging change, so check each vendor's site for current details.
Related reading
- Related use cases: Invoice intake and exception triage · Approval gates · Shadow mode · Readiness checklist · The AR clerk as an AI employee
- Offer pages: Tier 1 / Automate a Workflow · How It Works · Book your audit
