Multi-entity month-end close: A tiered calendar, owners, and an 8-entity example

A multi-entity month-end close runs in two layers: each legal entity, the parent and every subsidiary, closes its own books, then group finance combines the locked entity results into consolidated numbers. The group close can't start until the entities lock, so the slowest entity sets the group's date. Multi-entity means one business that operates through more than one legal entity, each with its own books, and multi-entity accounting keeps those books and combines them.

• Entity closeOne legal entity's month-end close in its own ledger and functional currency, covering cut-off, reconciliations, accruals, and FX revaluation, and ending in a locked trial balance.
• Group closeThe layer above the entities, also called the group month-end close. Group finance translates entity results into the reporting currency, eliminates intercompany balances, revenue, expenses, and any unrealized intragroup profit, reviews, and signs off.
• Entity lockThe point where an entity's trial balance is final for the month. After it, any change needs an approved post-lock journal.

The steps inside each entity are the same as a single-company close, which the guide to the month-end close process walks through.

A multi-entity close loses most of its days at handoffs between entities rather than inside tasks. Late trial balances, intercompany that doesn't match, entities using different FX rates, and local accounts mapped to the wrong group account each hold up everyone downstream.

The first five rows are also where most errors start, so the same fixes reduce both close days and post-close corrections.

Centralizing the close gives the group one calendar, one rate table, one task list, and one status view. The payoff is fewer handoff delays, intercompany agreed before entities lock, the same review standard in every entity, and a controller who knows which entity is late without a status meeting. Execution can stay local: central control doesn't mean moving the work to headquarters.

A well-run group of 6 to 15 entities can usually sign off in 5 to 6 business days, with entities locked by BD3 and the group close taking 2 to 3 more days. Today's survey averages run longer than that.

In Vena's survey of 624 US finance and accounting professionals, fielded August 20–24, 2026, and published October 23, 2026, the average close took 6.2 business days. Single-entity teams averaged 4.7 business days, and teams with more than 10 entities averaged 8.3. In iplicit's survey of 1,000 UK finance leaders at companies with £1 million to £10 million in turnover, fielded in August 2024 and reported that December, 55% said producing month-end accounts took more than a week, and 30% said more than two weeks. Both companies sell finance software, so read the figures as directional.

Entity count is only a rough guide, because the number of currencies, ERPs, and intercompany pairs often matters more. The table below is our planning guidance for each group size, not a survey result.

Track three numbers every close: the day each entity actually locks, the count of open intercompany differences at the cut-off, and the number of post-lock journals. For single-company benchmarks by company size, see how long month-end close should take.

A multi-entity close calendar sets four timed gates in one group time zone: FX rates lock on BD1, intercompany booking cuts off at noon on BD2, entities lock on BD3, and the group signs off by BD6.

BD1 is the first business day after month-end, and BD-1 is the last business day of the month. The group close timetable below runs an 8-entity group on US Eastern time (ET), and the worked example later on this page follows it.

The day between the intercompany cut-off and the entity lock is deliberate. It gives both sides time to fix a mismatch before either one locks, so nobody reopens an entity to correct intercompany.

Set every gate in group time and let entities finish in time-zone order. India's working day ends before New York's starts, so India locks first, Europe follows, and the Americas lock last. In NetSuite OneWorld or any other ERP, run translation and eliminations at the parent only after every subsidiary has locked. Locking an entity closes its period to routine posting. Whether you can close a period for a single subsidiary depends on your ERP: if it lets you lock periods by entity, lock each one at Gate 3; if it shares accounting periods across subsidiaries, enforce the entity lock with posting permissions, then close the shared period at group sign-off. The guide to locking an accounting period covers who can still post after a lock.

To speed up a calendar you already run, work backward from the group sign-off date and give each gate one owner. Then move bank, card, and intercompany matching into the month, so close week handles only the last few days of activity. For a single-entity calendar with 2026–2027 dates, see the month-end close calendar.

What if a foreign subsidiary closes later than the parent?

Split its close in two: a management close on the group calendar, using estimates for open items, and a statutory and tax close on the local timetable. The group never waits for the local filing deadline.

When the statutory close changes a number, the fix depends on what changed. An immaterial true-up or a change in estimate goes into the next management close, or the current one if group numbers haven't gone out yet, so the entity's ledger isn't reopened for the group calendar. A material error in a period you've already reported is different: assess it under ASC 250 or IAS 8, which can mean correcting or restating the prior period rather than booking it as current-month activity.

A reporting lag is a different tool. IFRS 10 first requires the subsidiary to prepare additional financial information as of the parent's reporting date, unless that's impracticable. Only then can the group use the subsidiary's own statements, no more than three months old and adjusted for significant transactions or events in the gap. ASC 810 allows a difference of up to about three months, with disclosure or other recognition of material intervening events. A lag mainly suits a subsidiary with a different fiscal year-end, must be applied the same way each period, and is rarely the right fix for a late monthly close.

Give every entity one named close owner and one backup, then group entities under cluster leads by region, time zone, or ERP rather than by count. Group finance owns the calendar, the rate table, intercompany matching, and consolidation, and the group controller signs off.

No task should have two owners. Escalate a missed gate to the cluster lead after two hours and to the group controller after four. Name an owner for a newly acquired entity on the day the deal closes, often a group accountant who knows its ERP, until the local team learns the calendar.

Your controller needs one status view across entities. For each entity, it shows trial balance lock status, reconciliations prepared and reviewed, open intercompany differences, journal entries waiting for approval, and time to the next gate. If it takes a meeting to learn where an entity stands, the view is missing.

Set the intercompany booking cut-off one day before entities lock, at a fixed time in group time. If one side hasn't booked by then, the receiving entity accrues from the seller's invoice, and both sides confirm the balance before lock.

• Match mid-monthRun the matching report around day 15 and again at the cut-off.
• Compare in the transaction currency firstIf both sides agree in the invoice currency, the difference is FX. The entity holding the foreign-currency balance revalues it at the locked closing rate, the gain or loss goes to that entity's P&L, and nobody rebooks the invoice.
• Accrue the missing sideThe receiving entity books an accrual from the seller's invoice or agreement and reverses it when the bill is entered.
• Let the document decideA common policy is that the invoice or intercompany agreement settles disputes on amount, and the side that differs corrects.
• Log what's still openA difference unresolved at lock goes on an exceptions list with an owner and an amount, and the group controller decides how it's treated in the group close.

For matching steps, intercompany journal entries, and eliminations, see the guide to intercompany accounting.

Every entity should use one group rate table: closing rates for balance sheet items and average rates for the P&L, from one named source at one named time. Treasury publishes it on BD1, the group controller approves it, and it's locked before entities revalue.

Name the source and capture time in your FX policy, such as a central bank reference rate or your bank's published rate at a fixed hour on the last business day. Each entity revalues balances held in other currencies at the closing rate. Group translation then uses closing rates for assets and liabilities and average rates for income and expenses. Revaluation gains and losses go to each entity's P&L, while translation differences go to the cumulative translation adjustment in other comprehensive income, not to profit. The accounting standards allow an average rate as an approximation of transaction-date rates, so switch to actual rates for large one-off items in a month when rates swing sharply.

In a multi-currency close, order matters: lock the rates, book and match intercompany, revalue in each entity, then translate at group level. An entity that finishes its day before the table is published waits for Gate 1 before posting revaluation, instead of using its own rate.

You can close acquired entities on another ERP without migrating them first. Map each local chart of accounts to the group chart, put the entity on the same calendar and gates, and bring its trial balance and intercompany detail into the group close by BD3.

That takes three things, whether your main ledger is NetSuite, SAP, Oracle, Microsoft Dynamics 365, or Business Central and the acquired ledger is QuickBooks Online:

• A group chart of accounts mapEvery local account maps to exactly one group account.
• A fixed way to get data out on timeA scheduled trial balance export or a live connection, plus the intercompany detail by counterparty.
• One place where the group close happensOne task list, one rate table, and one consolidation for every entity, whatever ledger it runs on.

Different entities can keep different charts of accounts, as long as each local account maps to one group account. Run a mapping check before each entity submits, because a new local account with no mapping is a common reason numbers land on the wrong line. Live connections beat monthly exports, since mapping gaps and missing intercompany show up before BD3 instead of on BD4.

Tier 1 covers entities above 10% of group revenue: US Parent (50.5%), US Sales (20.5%), and UK Ltd (12.8%). Tier 2 covers entities between 2% and 10%, plus India, which has no external revenue but carries transfer pricing risk. Texas LLC, at 0.7%, is Tier 3. Owners sit under three cluster leads: Americas on NetSuite, Europe plus India (whose working day overlaps Europe's), and the two acquired QuickBooks Online entities under a group senior accountant.

Treasury publishes this table at 10 AM ET on BD1. The group controller approves it, and it's locked in NetSuite and entered in both QuickBooks Online files. German and Dutch revenue translate at 1.0800, UK revenue at 1.2500, and Canada's CAD 625,500 at 1.3900, which gives the USD figures in the entity table.

The India cost-plus recharge, booked on both sides (BD1 to BD2)

India's October engineering cost was INR 20,875,000, which is $250,000 at the 83.50 average rate. The intercompany agreement sets cost plus 15%, so India invoices the US parent $250,000 + $37,500 = $287,500, in USD, dated October 31. The US parent books it on BD1. India's working day on BD1 ends before the rate table locks at 10 AM ET, so India books its side on the morning of BD2, India time, well before the noon ET cut-off.

US Parent Inc (USD):

India Pvt Ltd (INR), at the 84.00 rate on the invoice date: $287,500 × 84.00 = INR 24,150,000.

At the BD2 cut-off, the matching report shows $287,500 on both sides, with zero difference.

A UK management fee break that is pure FX (BD2, 12 PM)

The US parent invoiced UK Ltd a GBP 80,000 management fee on October 15 and booked the receivable at that day's rate of 1.2500, or $100,000. At the BD2 match, UK Ltd's GBP 80,000 payable shows as $100,800 at the locked 1.2600 closing rate. The $800 break equals GBP 80,000 × (1.2600 − 1.2500).

Both ledgers show GBP 80,000, so nothing is missing or wrong: the US parent simply hasn't revalued yet. On the morning of BD3, the US parent runs revaluation at the locked rate:

Both sides now show $100,800, and the break clears without anyone touching the invoice.

Canada Inc misses the cut-off (BD2 to BD3)

The US parent invoiced Canada Inc $42,000 for shared software licenses on October 31. At the BD2 noon cut-off, Canada's part-time bookkeeper hadn't entered the bill in QuickBooks Online. Under the accrual rule, the cluster lead books Canada's side from the US invoice at the 1.4000 closing rate: $42,000 × 1.40 = CAD 58,800.

Both sides confirm $42,000 that afternoon. Canada locks on BD3 by 5 PM ET, and the accrual reverses in November when the bill is entered.

Texas LLC closes on the lean checklist (BD2, 5 PM)

Texas LLC runs the 12-item Tier 3 checklist from the next section, with a flux trigger of 20% and $5,000. It had no intercompany activity in October, so its owner confirms a nil balance with the US parent and submits at 5 PM ET on BD2.

Group close and sign-off (BD4 to BD6)

All seven remaining entities lock by 5 PM ET on BD3. On BD4, the consolidation lead translates results at the locked table and eliminates the three intercompany pairs on both the balance sheet and the P&L. On the balance sheet, $287,500 + $100,800 + $42,000 = $430,300 of receivables and payables come out, each at zero difference. In the P&L, the matching revenue and expense come out, so group revenue and costs show only trade with outside parties:

The consolidation entry debits intercompany revenue $429,500 and credits intercompany expense $429,500. India's revenue and Canada's expense are translated at the rates they were booked, 84.00 and 1.4000, rather than the October average, so each pair eliminates at zero; the average rate is only an approximation of transaction-date rates. The UK fee was booked at 1.2500, which is also the October average, so it eliminates at $100,000. The $800 revaluation gain on the UK receivable stays in group profit, because an exchange difference on an intercompany balance isn't eliminated under ASC 830 or IAS 21. Group profit doesn't change here, because every charge was expensed in October. If one entity had sold inventory or a capitalized asset to another, you would also eliminate the profit still sitting in the buyer's books at month-end.

On BD5, the group controller reviews the three Tier 1 entities, flux above trigger, and the Canada accrual. On BD6, the CFO approves the consolidated statements and the group period locks.

Yes: small subsidiaries can run a shorter checklist, but not weaker controls. Keep the same cut-off, bank reconciliation, intercompany confirmation, and independent review for every entity, and reduce depth on low-risk accounts and variance analysis.

These thresholds are an example starting policy, not a standard. Management sets your own after discussing them with your auditor, and they work as review triggers rather than bright lines. An unusual item below the line still gets a look, and intercompany balances get reviewed in every tier, because they're related-party balances by definition.

A lean subsidiary checklist has 12 items:

1. 1Reconcile every bank account.
2. 2Reconcile company cards.
3. 3Agree AR to the ledger.
4. 4Agree AP to the ledger.
5. 5Post payroll.
6. 6Post accruals.
7. 7Confirm intercompany balances with each counterparty.
8. 8Roll forward fixed assets and prepaids.
9. 9Run FX revaluation with the group rate table.
10. 10Check flux against the Tier 3 trigger.
11. 11Review and lock the trial balance.
12. 12Submit the pack by the deadline.

A multi-entity month-end close checklist has five blocks: pre-close, entity close, intercompany, FX, and group close. Each block ends at one of the four gates, so the checklist and the calendar share the same deadlines.

Track every entity on one tracker with these columns:

To build the task list itself, start from our free month-end close checklist tool, then keep one copy per entity alongside the tracker. For the single-entity task list by close day, see the month-end close checklist.

Yes for the entity close in the right conditions, but rarely for the full group close. Entities on one ERP with daily reconciliations, recurring entries, and automated intercompany matching can lock on day 0 or BD1.

The group close still needs the closing FX rate, final accruals, eliminations, and review, and none of those can finish before month-end. Expect 2 to 4 business days for the group close, not zero. The usual blockers are acquired entities on other ERPs, local statutory work, and intercompany that's only matched at month-end, so fix those first. The guide to zero-day close covers what has to be true in each entity, and the guide to continuous close covers what moves into the month.

A multi-entity close platform should work across every ERP you run and pass six tests, starting with your oldest ERP and your newest acquisition.

Automate in this order: bank and card matching inside the month, recurring and accrual entries, intercompany matching across entities, FX revaluation at locked rates, then reconciliation prep and review. Keep human approval on judgment calls and on any journal posted after an entity locks.

AI agents can now prepare much of the entity-level work across many entities at once: matching bank lines, preparing reconciliations, drafting accruals, and flagging intercompany mismatches before the cut-off. Accountants still approve entries and own the judgment calls. The gain grows with entity count, because the same checks run on every entity in parallel instead of waiting in one person's queue. For what the evidence says about accuracy, see AI in the month-end close, and to compare tools by the work they do, see the best month-end close software.

Our Close Agent prepares close tasks for each of your entities, including intercompany and multi-currency tasks, and keeps the preparer and reviewer separate on every task. It reads from and posts approved entries to NetSuite, Oracle, SAP S/4HANA, Microsoft Dynamics 365, Business Central, and QuickBooks, reads from Odoo, and posts nothing to any ERP until a named approver signs off. It runs in a dedicated AWS account we manage for you, in your own AWS account, or on-premises, so you can explore our Close Agent.