Month-End Close Automation: Recs Ready, Journals Approved

Why does your close take two weeks when the accounting takes two days?

Month-end close automation shortens the close by having software prepare the work your team now does by hand. Bank and subledger reconciliations are prepared overnight, recurring accruals are drafted, intercompany balances are matched across entities and the consolidation is refreshed. A person still reviews and approves every journal before it posts.

If you are a CFO, financial controller or group finance manager, you know the shape of the problem. The parent runs Dynamics 365, NetSuite or SAP Business One. The businesses you acquired still run their own Xero or MYOB files. Consolidation lives in a workbook that one person fully understands.

What is month-end close automation? It is the use of integration, workflow rules and AI to prepare close tasks (reconciliations, accruals, intercompany matching, consolidation and variance commentary) so your finance team reviews exceptions and approves journals instead of building each schedule from scratch.

This guide shows which close tasks are fixed rules, which need AI, and which stay with people. It covers the controls your auditors will test and a phased way to start with one reconciliation.

Working out whether this fits your business? Book a free 30-minute review

How long should a month-end close take?

The most cited benchmark comes from APQC's General Accounting Open Standards Benchmarking survey. It measures calendar days from running the trial balance to completing the consolidated financial statements. Around 2,300 organisations answered the question, as reported by CFO.com in March 2018.

Two cautions before you compare yourself. The figures were published in 2018, and APQC counts calendar days while many vendor surveys count business days. Treat it as a reference point and measure your own baseline.

For listed groups the year-end matters more than the monthly rhythm. ASX Listing Rules 4.2A and 4.3A give non-exploration entities two months after period end to lodge the half-year report and the preliminary final report. ASX has said it will suspend securities for late lodgement and will not waive that rule. A slow monthly close becomes a slow year-end, and the audit squeezes into what is left.

Where do the days actually go?

Consider a hypothetical group with nine entities and a group finance team of twelve. The parent runs an ERP. Four acquired subsidiaries keep their own Xero files and two still run MYOB. There are forty bank accounts, a monthly management charge and shared services recharged across the group.

In a close like that, most of the hours go on preparation:

• Exporting trial balances from six or seven systems and remapping each chart of accounts to the group chart.
• Ticking bank lines that did not auto-match, often with remittance detail sitting in an inbox.
• Chasing the other side of an intercompany charge that one entity booked and the other did not.
• Rebuilding accrual schedules that look almost identical to last month.
• Writing variance commentary after the numbers finally settle, usually late at night.

Intercompany is the stubborn one. In a 2016 Deloitte Dbriefs poll of more than 3,800 finance and accounting professionals, disparate software systems was the most named obstacle to intercompany accounting at 21.4%. Only about 9.2% described their intercompany framework as leading. Acquisitions add systems faster than anyone retires them.

What usually delays a group pack is account mapping, a missing counterparty entry, or the one schedule that lives on someone's desktop.

Which close tasks are rules, which need AI, and which stay human?

This is the split that decides what to build. Much of the preparation is fixed rules that integration and workflow handle well. AI earns its place on the messy middle, where descriptions do not match and someone has to read and judge.

What does AI do that workflow rules cannot?

Rules work when the data is consistent. Intercompany descriptions are not. One entity writes "Mgmt fee Sept HO", the other writes "Head office charge 09/26", and the amounts differ by a GST treatment or an FX rate. A language model can read both, propose the pair and explain why, which a rule built on exact text cannot.

AI also helps with commentary. It can read the transactions behind a movement and draft "Freight up because of two catch-up invoices from the August carrier change". Your controller edits it, which is faster than a blank page.

What should never be automated?

Provisions, impairment, revenue judgements, the release of an accrual and the final sign-off stay with people. So does any decision about whether a mismatch is an error or a timing difference that will reverse. The tool assembles the evidence, and a named person decides.

How does an automated close run, step by step?

The approval step sits in the middle on purpose. Nothing in this flow writes to the general ledger until a person with the right authority approves it.

What controls will your auditors expect to see?

Your auditors will test journals whether or not you automate. Under ASA 240, the Australian standard aligned with ISA 240, the auditor must test the appropriateness of journal entries recorded in the general ledger and other adjustments made in preparing the financial statements. A well-built close makes that testing easier, because every entry carries its source and approver.

Build these four controls in before the first live month:

• An audit trail on every proposal. Each AI match or drafted journal records the source lines, the reason given and who approved or rejected it.
• Segregation of duties. The service account that prepares journals cannot post them, and the preparer and approver are different people.
• Approval before posting. Journals route through the approval workflow your ERP already has, with limits by amount and account.
• Access you control. The integration runs in your own cloud tenant in an Australian region, with credentials your IT team owns and can revoke.

The risk most CFOs raise is an AI match that looks right and is wrong. The control is shadow mode: the tool prepares matches beside your team for several closes, and it moves into co-pilot only when its accuracy passes a threshold you set.

Related: Our guide to what it costs to run AI agents after you build them covers monitoring, model changes and who owns the agent once it is live.

Where should you start: which reconciliation first?

Start with one reconciliation, measured, before touching the whole close. The right first one is high volume, painful and low judgement.

If the subsidiaries run several Xero files, the consolidation mechanics are covered in our guide on how to consolidate multiple Xero organisations. For the consolidation and FX side in more depth, see AI for multi-entity financial consolidation. This post covers the close end to end; those two go deeper on the group pack itself.

What does a phased rollout look like?

Each phase is fixed price and ends at an exit point where you decide to proceed, pause or stop. You keep everything delivered at each stage.

A few practical points from how these projects tend to run:

• Shadow mode needs at least two closes. One month can hide a quarterly accrual or an unusual recharge.
• Fix the mapping before the matching. If the group chart mapping is wrong, AI will match the wrong things faster.
• Expect the second entity to be harder. Acquired files often carry legacy codes and tracking categories nobody documented.
• Keep the workbook alive in Phase 2. Your team runs its normal close while the tool runs beside it.

The integration work underneath is usually the bulk of the effort. Our system integration service covers connecting ERPs, Xero and MYOB without replacing them. The workflow and approval side sits under process automation.

What results can you expect, and how will you know?

We will not quote you a percentage. Your result depends on how many entities you run, how clean the mapping is and how much of the close is judgement. What you can measure is the gap between your baseline and the shadow-mode results.

Track these numbers from Phase 1:

• Business days from period end to the consolidated pack reaching the CFO.
• Hours spent on the reconciliation you chose to start with.
• Number of intercompany differences still open at day three.
• Share of AI-proposed matches your controller accepts without change.

If the accepted-match rate stays under your threshold, you stop or adjust at the exit point. If it passes, you widen to the next reconciliation and the next entity. The same pattern applies upstream: groups that also automate invoice processing have fewer hand-keyed entries in the AP subledger to reconcile at month end.

The lead on every Solve8 engagement spent 18 years on operations and data systems for BHP, Rio Tinto and Senex Energy, gained while working with previous consulting employers. These companies are not Solve8 clients. That work included reporting programs where several systems had to agree before a pack could go to leadership.

Getting started

Pick the one reconciliation that costs your team the most close hours. Write down how long it took last month and how many items were still open at day three, and use those two numbers as your baseline.

Then book a scoping call. You will leave with a straight answer on whether that reconciliation is worth piloting, what the controls would look like in your ERP, and what you would need from IT.

Common Questions

How do you automate the month-end closing process?

Start by splitting close tasks into fixed rules, messy matching and judgement. Use integration and workflow for trial balance collection, bank rules and recurring accruals, use AI for intercompany matching and draft commentary, and keep provisions and sign-off with people. Begin with one reconciliation and measure it.

Can AI post journals to our ledger automatically?

It should not. The safe design has AI prepare matches and draft journals, then a person with the right authority approves each one before it posts. The service account that prepares entries cannot post them, which keeps segregation of duties intact for your auditors.

Does month-end close automation work across different ERPs and Xero files?

Yes, as long as each system can be reached by API, database or export. Dynamics 365, NetSuite, SAP Business One, MYOB Acumatica and Xero all expose their data in some form. The integration reads each ledger and maps it to your group chart without replacing any system.

What is intercompany reconciliation automation?

It is software that pairs the two sides of transactions between entities in your group and flags differences early in the close. Rules handle exact matches, and AI handles the entries where descriptions, dates or amounts differ because of wording, GST treatment or FX rates.

Will our auditors accept an AI-assisted close?

Auditors test journal entries under ASA 240 regardless of how they were prepared. An AI-assisted close that records the source lines, the reason for each proposal and who approved it gives them a clearer trail than a spreadsheet. Talk to your audit partner about the controls before go-live.

Which reconciliation should we automate first?

Choose the one that is high volume, painful and low judgement. For many groups that is intercompany matching between the two entities that trade most, or bank reconciliation for the busiest accounts. Measure its baseline first so you can judge the shadow-mode results.

Related Reading:

• AI for Multi-Entity Financial Consolidation - Goes deeper on consolidation, FX revaluation and eliminations for the group pack.
• Consolidate Multiple Xero Organisations: Guide - The practical options when your subsidiaries each run their own Xero file.
• Xero Reconciliation Agent: Your AI Bookkeeper - How an AI agent handles day-to-day bank reconciliation inside a single Xero organisation.
• AI Agent Governance: Privacy and Human Override - How to set data access and human override rules before any agent touches finance data.

Sources: APQC General Accounting Open Standards Benchmarking survey, reported in Perry D. Wiggins, "Metric of the Month: Cycle Time for Monthly Close", CFO.com, 5 March 2018; Deloitte Dbriefs poll on intercompany accounting, 26 May 2016; ASX Listing Rules 4.2A, 4.3A and 17.5 and ASX compliance updates on lodgement deadlines (2022 to 2024); AUASB ASA 240 The Auditor's Responsibilities Relating to Fraud in an Audit of a Financial Report, aligned with ISA 240.