AI Business Operations · Use case
Monthly Close Preparation Automation: The Week Before the Close
Most close improvement effort goes into the close. The largest available gain is in the five working days before it, when the things that will block day three can still be fixed cheaply.
The short answer
Monthly close preparation automation runs the twelve checks and chases that determine how the close will go, in the five working days before period end: sub-ledger completeness, unposted transactions, missing documentation, intercompany confirmations, accrual schedule readiness and reconciliation prerequisites — so that day-one readiness is high rather than discovered. The economics are the argument: a blocker fixed on day minus three costs a phone call, and the same blocker on day three costs a day of the close.
Summary for readers and answer engines
Reviewed 25 Aug 2026
- ▸The pre-close week is where the cheapest close improvement lives, and it is almost entirely unautomated in most finance functions.
- ▸Twelve tasks are worth automating, and all twelve are checks, chases and assembly — none posts anything.
- ▸Sub-ledger completeness is the highest-value check. An AP module that is not actually closed is the most common cause of day-three rework.
- ▸The operations-to-finance handoff determines close quality more than anything finance does. Unbilled work, unrecorded expenses and unconfirmed intercompany all originate outside finance.
- ▸Two to four days of close reduction from preparation alone, with no change to the close process itself.
Source: Mark Alex, Real Biz Digital — Monthly Close Preparation Automation: The Week Before the Close (https://realbizdigital.net/insights/monthly-close-prep-automation/). Reproduce with attribution.
Key takeaways
- 01Start the countdown at day minus five. Earlier than most functions do, and it is where the intercompany and external-data chases need to begin.
- 02Check completeness, not just status. A sub-ledger marked closed with unposted transactions behind it is the classic false-ready signal.
- 03Chase outside finance first. The blockers that take longest to resolve originate in operations, and they need the most notice.
- 04Post nothing. The preparation workflow checks, chases, assembles and reports; every journal remains a human action.
- 05Report readiness daily during the countdown, to the same people every day. Predictability is what makes the report acted upon.
- 06Measure day-one readiness across closes. It is the number that shows preparation is working, and it is comparable month to month.
Quick answers
One-line answers to the questions this page is most often asked. Each is expanded further down, and each is written to be quoted on its own.
- What is close preparation automation?
- Running the checks and chases that determine close readiness in the days before period end: completeness, unposted items, missing documentation, confirmations and schedule readiness.
- Why focus on preparation rather than the close?
- Because a blocker fixed before the close costs roughly a tenth of the same blocker fixed during it, and most functions apply their effort the other way round.
- What is the highest-value check?
- Sub-ledger completeness. A module marked closed with unposted transactions behind it is the most common cause of rework discovered on day three.
- Should the workflow post journals?
- No. Preparation checks, chases, assembles and reports. Every journal remains a human action with human judgement behind it.
- Where do the hardest blockers originate?
- Outside finance — unbilled work, unsubmitted expenses, unconfirmed intercompany balances and external data. They take longest and need the most notice.
- When should the countdown start?
- Day minus five. The intercompany and external-data chases need that much lead time to resolve before period end.
- What improvement is realistic?
- Two to four days off the close from preparation alone, without changing the close process itself.
Close preparation in numbers
Every figure below is defined and sourced further down. They are stated here so they can be quoted without reading the whole page.
Why the pre-close week is the cheapest improvement
The same blocker costs an order of magnitude more once the close has started, and nobody prices that difference.
| Found | Cost to resolve | Effect on the close |
|---|---|---|
| Day −5 | A phone call or an email | None |
| Day −2 | A chase and a follow-up | None, if it lands |
| Day 1 | Half a day, disrupting close work | Slows the critical path |
| Day 3 | A day, plus rework of dependent items | Extends the close |
| Day 5 | A day, plus superseded reconciliations | Extends the close and destroys goodwill |
| Post-close | An adjustment, and an explanation | A quality finding |
Our verdict
The same missing intercompany confirmation costs a phone call on day minus five and a day of the close on day three, because by then reconciliations have been performed against incomplete data and must be redone. Preparation is not a nice-to-have refinement of close automation — it is where the leverage is, and it is almost entirely unautomated in the functions we have looked at.
The asymmetry has a second consequence: preparation work is done by people who are not yet busy, which is the opposite of close work. Moving effort earlier moves it to where there is capacity.
Twelve pre-close tasks worth automating
Key facts
- ▸Four of the twelve need to start at day minus five, and all four involve people outside finance. That is not a coincidence — external dependencies have the longest resolution time and the least urgency for the person holding them.
- ▸Two tasks are monitoring only. Bank statements and FX rates arrive on their own schedule and chasing them achieves nothing; knowing they have not arrived is what matters.
- ▸None of the twelve posts anything. The workflow’s entire output is checks, chases and a report.
| Task | System | Chases whom | Lead time |
|---|---|---|---|
| Sub-ledger completeness check | AP, AR, payroll, inventory | Module owners | Day −3 |
| Unposted transaction detection | Accounting | Preparers | Day −3 |
| Unbilled work identification | CRM, project system | Delivery and sales | Day −5 |
| Unsubmitted expense chase | Expense system | Individual employees | Day −5 |
| Missing supplier invoice detection | AP, purchase orders | Procurement, suppliers | Day −5 |
| Intercompany balance confirmation | Group ledger | Counterparty entities | Day −5 |
| Accrual schedule readiness | Schedules, contracts | Preparers | Day −3 |
| Bank statement availability | Banking | External — monitor only | Day −2 |
| FX rate availability | Rate source | External — monitor only | Day −1 |
| Missing documentation detection | Document storage | Preparers | Day −3 |
| Prior-period adjustment carry-forward | Accounting | Controller | Day −2 |
| Readiness report assembly | All of the above | Everyone, daily | Daily |
The day-minus-five group is where the value concentrates. Unbilled work and missing supplier invoices are also the two items most likely to cause a post-close adjustment if they are missed entirely.
The five-day countdown
Key facts
- ▸Day minus four is the highest-leverage report because it is the first one, and it is what converts four chases into four visible commitments.
- ▸The day minus two escalation matters: a chase sent once and never followed up is a request, and a chase escalated to a manager is a deadline.
- ▸Day one should be a handover. If the close still begins with two days of status establishment, the preparation workflow has not actually changed anything.
External and cross-functional chases begin
Unbilled work, unsubmitted expenses, missing supplier invoices, intercompany confirmations. Four chases, all to people outside finance, all with the longest resolution time. Sent once, with a clear deadline and what happens if it is missed.
First readiness report
The baseline. Circulated to finance and to every chase recipient’s manager, so the chase has visibility rather than only a request. This is the day the report starts being read.
Internal completeness checks
Sub-ledger completeness, unposted transactions, accrual schedule readiness, missing documentation. All within finance, all actionable the same day.
Second chase and prior-period carry-forward
Follow up anything outstanding from day minus five, escalating to managers. Confirm prior-period adjustments that need carrying forward, which is a controller judgement the workflow only surfaces.
Final readiness report and monitoring
The report the close starts from. Bank statement and FX availability confirmed or flagged. Anything still outstanding is now a known day-one blocker rather than a day-three discovery.
Handover, not a fresh start
The close begins with a readiness score, a named blocker list and a critical path — instead of two days establishing what the state of the world is.
Five days is the right window for most monthly closes. Quarterly and annual closes need longer for the external dependencies, and the same structure extends cleanly.
Completeness versus status
This distinction is where most false-ready signals come from, and it is worth being precise about.
- 01Check for unposted transactions dated within the period, not just the module’s closed flag. A closed module with fifteen unposted invoices is not closed.
- 02Compare completion timestamps against sub-ledger modification timestamps. Work completed before its source changed is superseded, and detecting it before the close saves a day.
- 03Count expected items, not just received ones. Twelve of fifteen intercompany confirmations received is a status; the three missing are the finding.
- 04Verify confirmed balances match rather than merely arriving. A received confirmation stating a different figure is worse than a missing one, because it looks complete.
- 05Check documentation exists for items requiring it, above materiality. Missing support found on day minus three is obtainable; on day five it is a gap.
- 06Report completeness and status separately. Conflating them is how a close reports eighty percent ready and then takes eleven days.
Status says
- ✓The AP module is marked closed
- ✓The reconciliation is marked complete
- ✓The schedule is marked prepared
- ✓The confirmation is marked received
Completeness asks
- —Are there unposted AP transactions dated in the period?
- —Was it performed against the sub-ledger’s current state?
- —Does it cover every contract that should be accrued?
- —Does the confirmed balance match ours?
The superseded-work check is the one nobody performs manually and the one that most reduces close rework. It is a timestamp comparison and it costs nothing to run daily.
The operations-to-finance handoff
Close quality is determined substantially outside finance, which is uncomfortable and actionable in equal measure.
Unbilled completed work
Delivery marks work complete; finance never learns. The revenue is real and unrecorded, and it surfaces as a post-close adjustment or not at all.
Unsubmitted expenses
Individuals hold receipts past period end. Chasing at day minus five works; chasing at day two produces submissions dated wrongly.
Missing supplier invoices
Goods received, invoice not arrived, accrual not prepared. Procurement knows the receipt happened and finance does not.
Unconfirmed intercompany
Another entity’s finance team, another set of priorities. The longest lead time of any dependency and the one most often left to the last day.
Contract changes not communicated
A term changed mid-period, affecting revenue recognition. Sales knows; finance discovers it during the close or afterwards.
Uncommunicated disputes
A customer disputing an invoice affects both receivables and revenue, and the information sits in a support queue.
All six are information problems rather than accounting problems, which is precisely why an agent reading across CRM, project systems, procurement and support can surface them. Finance cannot chase what it does not know exists.
What preparation must not do
- 01Post nothing. Not accruals, not adjustments, not reclassifications. The workflow surfaces what needs posting and a person posts it.
- 02Compute nothing that enters a statement. Accrual amounts, provisions and translations remain deterministic calculations under human review.
- 03Conclude nothing. “This reconciliation is complete” is a preparer’s assertion, not an automated determination.
- 04Close nothing. Marking a sub-ledger closed is a module owner’s decision with consequences the workflow cannot assess.
- 05Never suppress a blocker. A blocker the workflow cannot resolve must be reported, not deprioritised into invisibility.
- 06Never adjust the readiness score. The score is a measurement, and a workflow that can improve its own score is measuring nothing.
This boundary is what makes close preparation adoptable without a controls conversation. Every one of the twelve tasks is a read, a chase or a report, which means there is nothing for internal audit to object to.
Measured impact
| Measure | Before preparation automation | After | Mechanism |
|---|---|---|---|
| Day-one readiness score | 30–45% | 65–80% | Blockers resolved before period end |
| Days establishing status | 2–4 | Under 1 | Readiness report replaces asking |
| Blockers discovered after day 1 | 8–20 | 2–5 | Chases completed with lead time |
| Superseded work items | 5–15 per close | 1–3 | Timestamp comparison run daily |
| Total close duration | Baseline | 2–4 days shorter | Critical path shorter and known on day one |
| Post-close adjustments | Baseline | Lower | Unbilled and unrecorded items caught pre-close |
These ranges come from finance functions we have instrumented rather than from published research, and they are offered so you can argue with them. The mechanism column is the durable part: the improvement comes from resolving blockers with lead time, which is not a claim that requires much faith.
Next step
Run the countdown, then score the readiness
BarzelOps runs close preparation as an opinionated workflow across accounting, CRM, email and documents; Barzel FinOps Atlas scores the readiness and detects the blockers. Both have free tiers.
Limits
Two.
- 01Preparation cannot make external data arrive earlier. A bank statement landing on day four lands on day four, and the value is in knowing rather than in changing it.
- 02It cannot resolve a blocker whose owner will not act. Chasing with lead time and escalating to managers improves the odds substantially and does not make it certain, which is why the readiness report has to name the owner.
Common misconceptions
Four claims we hear regularly that do not survive contact with a real estate. Each is stated as we hear it, then corrected.
Close improvement means automating the close.
The largest available gain is in the five working days before period end, when a blocker still costs a phone call rather than a day of the close. Preparation is almost entirely unautomated in the functions we have examined, which makes it the cheapest remaining improvement.
A sub-ledger marked closed is closed.
Status and completeness are different questions. A module flagged closed with fifteen unposted transactions dated in the period is the most common source of rework discovered on day three, and detecting it requires checking for the transactions rather than reading the flag.
Close blockers are a finance problem.
Six of the most persistent originate outside finance: unbilled completed work, unsubmitted expenses, missing supplier invoices, unconfirmed intercompany balances, uncommunicated contract changes and undisclosed customer disputes. Finance cannot chase what it does not know exists.
Preparation automation needs write access to the ledger.
None of the twelve pre-close tasks posts anything. Every one is a read, a chase or a report, which is why close preparation can be adopted without a controls conversation and why it should stay that way.
Frequently asked questions
What is monthly close preparation automation?
Running the checks and chases that determine close readiness in the working days before period end: sub-ledger completeness, unposted transactions, unbilled work, unsubmitted expenses, missing supplier invoices, intercompany confirmations, accrual readiness and documentation gaps.
Why is preparation more valuable than automating the close itself?
Because the same blocker costs roughly a tenth as much to resolve before the close as during it. A missing intercompany confirmation on day minus five is a phone call; on day three it is a day of the close plus rework of reconciliations already performed.
Which pre-close tasks need the longest lead time?
Four, all involving people outside finance: unbilled work identification, unsubmitted expense chases, missing supplier invoice detection and intercompany balance confirmation. All should begin at day minus five.
What is the difference between status and completeness?
Status is what a system reports; completeness is whether it is true. A sub-ledger flagged closed with unposted transactions dated in the period has a closed status and is not complete, and that gap is the most common cause of day-three rework.
What is superseded work and why check for it?
Work completed before its source data changed — a reconciliation performed against a sub-ledger that was subsequently modified. It is a timestamp comparison nobody performs manually, and detecting it before the close removes a day of rework.
Which close blockers originate outside finance?
Six: unbilled completed work, unsubmitted expenses, missing supplier invoices where goods were received, unconfirmed intercompany balances, contract changes not communicated to finance, and customer disputes sitting in a support queue.
Should a preparation workflow post journals?
No. All twelve tasks are reads, chases or reports. Accrual amounts, adjustments and reclassifications remain human actions, and the workflow’s role is to surface what needs posting rather than to post it.
Why can close preparation be adopted without a controls debate?
Because nothing it does requires write access to a ledger. Every task is read-only or a notification, which means there is no new control risk for internal audit to assess.
When should the countdown begin?
Day minus five for the external and cross-functional chases, with the first readiness report on day minus four so those chases become visible commitments rather than individual requests.
Why does the first readiness report matter so much?
Because it converts four chases into four visible commitments by circulating them to recipients’ managers. A chase sent once and never followed up is a request; a chase reported daily and escalated is a deadline.
What improvement is realistic from preparation alone?
In the functions we have instrumented, day-one readiness rising from 30–45% to 65–80%, days spent establishing status falling from two to four down to under one, and total close duration two to four days shorter — with no change to the close process itself.
What should day one of the close look like afterwards?
A handover rather than a fresh start: a readiness score, a named blocker list and a critical path already established. If the close still begins with two days of status establishment, the preparation workflow has not changed anything.
Glossary
- Close preparation
- Work performed before period end that determines how the close itself will proceed.
- Countdown
- The sequenced five-day pre-close chase and check schedule.
- Completeness check
- Verifying that no relevant transactions remain unposted, as distinct from reading a closed flag.
- Superseded work
- Completed close work invalidated by a subsequent change to its source data.
- Day-one readiness
- The measured share of close prerequisites complete when the close begins.
- Operations handoff
- The transfer of information from operational teams to finance that determines close quality.
- Unbilled work
- Completed delivery not yet invoiced, representing real unrecorded revenue.
- Chase lead time
- How far before period end a given dependency must be requested to resolve in time.
- Monitoring-only task
- A dependency that cannot be accelerated, where the value is in knowing its status.
- Readiness report
- The daily pre-close status circulated to finance and to chase recipients’ managers.
Standards and entities referenced
Every named framework on this page resolves to a public definition. If you are checking our claims, start here rather than with us.
Sources and further reading
Primary specifications and standards this article relies on. Where a claim is our own operating judgement rather than something a standard states, the text says so.
- 01 · COSOCOSO Internal Control — Integrated Framework ↗The control framework auditors map financial process evidence against.
- 02 · IFRS FoundationIAS 7 — Statement of Cash Flows ↗The reporting standard cash-position and cash-variance work ultimately serves.
- 03 · U.S. SECSarbanes-Oxley Act — Section 404 ↗Where segregation of duties becomes an externally audited control.
- 04 · BlackLineBlackLine — Agentic Financial Operations ↗Market reference: the phrase ‘Agentic Financial Operations’ and the governance framing around it.
- 05 · TrintechTrintech — AI agents for financial close ↗Market reference: variance and flux agents with reviewer signoff and traceable evidence.
- 06 · Object Management GroupBPMN 2.0 specification ↗The modelling standard business process orchestration vocabulary comes from.
- 07 · AxelosITIL 4 — change enablement ↗Established change-management vocabulary this article borrows for MCP estates.
- 08 · PCAOBPCAOB AS 1105 — Audit Evidence ↗The standard defining sufficiency, appropriateness, relevance and reliability of audit evidence.
Last reviewed 2 September 2026 by Mark Alex. External links open in a new tab; we do not control their content.
Cite this article
Alex, M. (2026). Monthly Close Preparation Automation: The Week Before the Close. Real Biz Digital. https://realbizdigital.net/insights/monthly-close-prep-automation/
Try the mechanics on a live server
To see a governed tool surface respond before you point an agent at your accounting system — Barzel Scripture Intelligence is free and public at scripture-intelligence-server.mcpize.run: no signup, no key, 54 tools. Setup is in the reference.
Buy it on the marketplace
BarzelOps is this execution layer, sold as a running product
Forty tools covering capability discovery, workflow planning, preview before execution, run, trace, pause, resume and cancel, approval request and resolution, credential validation and connector health — across accounting, CRM, email, calendar, documents, Slack and storage. Opinionated workflows ship with it: customer onboarding, invoice follow-up, lead-to-invoice, pipeline cleanup, monthly close preparation and weekly operations briefings. The Free tier runs 100 calls a day.
| Plan | Price | Included | Right for |
|---|---|---|---|
| Free | Free | 100 calls/day · 10 core tools: plan, preview, run, trace | Proving one workflow end to end before anyone signs anything |
| Pro | $19/mo | 15,000 calls/mo · 26 tools including approvals and templates | One operator automating their own recurring procedures |
| Team | $49/mo | 50,000 calls/mo · the complete 40-tool surface | An operations team running cross-app workflows under approval |
| Enterprise | $199/mo | Unlimited calls · deployment and connector scope by agreement | Multi-team execution with audit and residency obligations |
Sold on the MCPize marketplace · prices as listed 2 Sep 2026 · the listing is authoritative
The five Barzel servers, and which problem each one is sold for
One estate rarely needs all five. This is the honest mapping, so you buy the layer your problem actually lives in.
| Server | Sold for | Entry price | Where it sits |
|---|---|---|---|
| Barzel Central Gateway | Knowing and governing the estate: inventory, registry, routing, risk scoring, approvals, evidence | Free, then $10–$149/mo | Control plane — decides what may be reached, and by whom |
| BarzelVault | Stopping a specific dangerous action before it executes, with proof afterwards | $199–$3,999/mo | Decision point — evaluates the individual call before execution |
| BarzelOps | Running real business workflows across HubSpot, Xero, Gmail, Drive and Slack under approval | Free, then $19–$199/mo | Execution layer — does the work the policy allowed |
| Barzel FinOps Atlas | Attributing AI spend to agents, tools and outcomes, then forecasting and capping it | Free, then $29–$799/mo | Economics layer — what the estate costs per outcome |
| Barzel Scripture Intelligence | A free, credential-free public MCP server to test clients and inspect real protocol traffic | Free, unmetered, no signup | Reference implementation — safe place to learn the protocol |
Written by
Mark Alex
Founder of Real Biz Digital and architect of the Barzel ecosystem — five MCP servers published and callable in public. Software developer, technology entrepreneur and mechatronics engineer, working across AI agent governance, MCP security, AI infrastructure, FinOps and intelligent operations.