Blog
Written by

Naman Mathur
Published on

Key Takeaways
Centralise the close calendar, task templates, materiality thresholds and review evidence, then leave statutory reporting and local tax with the entity teams.
Before any tool is configured, agree one reconciliation policy covering risk tiers, thresholds, frequency and evidence for every entity's accounts.
Every intercompany pair needs a single named owner, with dispute deadlines that fall before working day one.
Run one parallel close on two or three business units with different ERPs and currencies, and judge each tool on that result.
The most common mistake in a shared services close is moving the work before fixing the process. A group lifts 12 entity closes into a shared services centre (SSC), which then inherits 12 versions of the close.
The headcount moves and the cost base looks better for a quarter. Then the centre spends its first year learning how each entity used to close, because nobody standardised the process first.
The decision you face is what to centralise and what to leave local. The standard advice says to centralise first and standardise later, or to consolidate onto one enterprise resource planning (ERP) system before touching the close. Both get the order wrong, and both delay the benefit the SSC was set up to deliver.
This article answers what to standardise across regions, which reconciliation tools work across entities, how to structure intercompany, and how to evaluate close automation.
What Should Shared Services Leaders Consider When Standardising Close Processes Across Regions?
Standardise the calendar, task templates, materiality thresholds, review rules and evidence standards across every region. Keep statutory reporting, local tax and regional cut-off with local teams, set up as tasks inside the group calendar.
That split follows a simple test: anything a group reviewer or auditor compares across entities should work the same way everywhere. American Productivity & Quality Center (APQC) research on finance operating models recommends centralised transaction processing and global process ownership, alongside standardised end-to-end processes. Centralisation only pays off when the process being centralised is already one process.
Someone has to own that process across regions. In our experience, the fastest groups appoint a global process owner (GPO) with authority over templates and thresholds. Entity controllers still own their numbers.
Area | Centralise | Keep local | Why |
|---|---|---|---|
Close calendar | Group deadline, task templates and dependencies | Working-day and public holiday adjustments | One status view for the group, with local dates held as configuration |
Materiality | Review and reconciliation thresholds | Statutory materiality for local accounts | Reviewers apply the same test to every entity |
Foreign exchange (FX) | Rate source and fixing time | Local bank and payment detail | One rate policy keeps consolidation consistent |
Evidence and reporting | Reconciliation and evidence standard | Statutory reporting under local frameworks | Auditors sample one standard, while local frameworks need local expertise |
Controls and tax | Access and segregation of duties (SoD) rules | Local tax filings and VAT returns | Group controls stay consistent as staff move, and tax stays with the people who file it |
Source: Stacks implementation practice, 2026.
Regional Differences: Calendars, Currencies and Regulations
Regional variation belongs at task level, inside one group calendar. Whit Monday is an official holiday on the Dutch public holiday calendar, so it can shift working day one for that entity. The calendar should move the local due dates and leave the group deadline intact.
FX is the area where local discretion causes the most rework at consolidation. Under IAS 21 the rate type is set, but the source and fixing time are still your call, so set them centrally and every entity translates on the same basis.
Statutory frameworks stay local because the expertise is local. Under the FRC's amended FRS 102, most amendments take effect for periods beginning on or after 1 January 2026, so UK subsidiaries carry local transition tasks. A Dutch entity under Book 2, Title 9 of the Dutch Civil Code runs its statutory tasks in the group calendar, under the same evidence rules.
For companies applying the UK Corporate Governance Code, Provision 29 raises the stakes. For financial years beginning on or after 1 January 2026, boards must declare whether material controls were effective at the balance sheet date, so the first declarations appear in 2027 annual reports. That declaration needs evidence from every entity in scope, captured to one standard.
What Tools Help Finance Teams Standardise Reconciliation Processes Across Multiple Entities?
The tools that standardise reconciliation across entities apply one group policy to every entity's accounts, whatever ledger they sit in. They connect to each ERP and bank, then enforce the same risk tiers, thresholds, frequency and evidence rules on every ledger.
Policy comes before tooling. If each entity sets its own thresholds, the software automates 12 policies, and the SSC still has no comparable view of group reconciliation risk.
This category overlaps with close software but is narrower. Close software manages the calendar, task dependencies and sign-off for the whole close, while a reconciliation platform handles the balance-level work inside it. ERP reconciliation modules usually cover one ledger well, which leaves a mixed-ERP group with a separate policy per system.
Option | What it standardises across entities | Where it falls short in a mixed-ERP group |
|---|---|---|
ERP reconciliation module | One policy and status view inside that ledger | A second ERP brings a second policy and a second status view |
Standalone reconciliation platform | Policy, matching and evidence across ledgers and banks | The calendar, dependencies and non-reconciliation tasks sit in another tool |
Close platform with reconciliations | Policy, evidence and status inside one group close calendar | Depth varies, so test intercompany and bank formats in the pilot |
Source: Stacks implementation practice, 2026.
Whichever option you choose, it has to apply the same policy to every source an entity reconciles, and most of those sources sit outside the ERP. Card settlements arrive from Stripe or Adyen, billing from Chargebee and spend from Coupa or Pleo, while one bank sends camt.053 statements and another still sends MT940.
In a demo, ask the vendor to change one threshold at group level and show it apply in every entity, load an MT940 and a camt.053 statement for two different entities, and open one reviewer's queue across three entities.
The mechanics of tiering accounts and assigning exception owners are covered in our guide to running reconciliations across entities. For an SSC, the operating-model question is simpler: does every entity's reconciliation meet the same written standard, and can one reviewer see that it does?
How Should Finance Teams Structure Intercompany Workflows Across Shared Services Centres?
Give each entity pair one owner and run all pairs under one group intercompany policy. A central intercompany team handles matching and eliminations, while local teams resolve disputes with their counterparties because they know the underlying transactions.
The failure we see most often is shared ownership. When both sides of a pair are responsible for the difference, neither is, and the mismatch rolls into the next period as an unexplained elimination.
Activity | Owner | Evidence |
|---|---|---|
Intercompany policy, pricing and settlement terms | GPO or group financial controller | Approved policy with version history |
Matching both sides of each pair | Central intercompany team in the SSC | Match report per pair, with differences listed |
Investigating and agreeing differences | Named owner for each entity pair | Dispute log with resolution and approver |
Eliminations at consolidation | Central consolidation team | Elimination journals tied to matched balances |
Settlement and netting | Group treasury | Settlement confirmations by pair |
Source: Stacks implementation practice, 2026.
Dispute deadlines should fall before working day one. If intercompany charges are agreed by working day minus two, the central team matches confirmed balances during the close. It stops arbitrating last week's disputes.
Once every pair has an owner, the software choice gets much easier. For selection criteria, see our guide to choosing intercompany accounting software.
How Should a Shared Services Team Evaluate Close Automation Tools Across Multiple Business Units?
Test each tool on two or three business units with different ERPs and currencies, in one parallel close. A demo on a single clean entity tells you nothing about how the tool handles the variation your SSC exists to absorb.
In our experience, most SSCs start this evaluation with a close that is still largely manual, so almost any tool looks like an improvement in a single-entity demo. The parallel close is what separates them.
Test | How to run it | What good looks like |
|---|---|---|
One calendar across entities | Load the full close for three business units, including local holidays | One group view, with local due dates moving and the group deadline fixed |
Entity-level permissions and SoD | Give one user preparer rights in entity A and reviewer rights in entity B | The tool blocks self-review and logs every access change |
Mixed-ERP coverage | Connect business units on different ledgers, for example NetSuite at group level with Visma or Fortnox in a Nordic subsidiary, and pull live balances | Balances tie to each trial balance (TB) without manual exports |
FX handling | Run a month-end revaluation using the central rate source | Rates and translated balances trace back to one approved source |
Intercompany matrix | Load a month of intercompany activity across all pairs | Every pair shows a match status, a difference and a named owner |
Audit trail | Pick one signed-off reconciliation and ask for its history | Preparer, reviewer, timestamps and support appear without rebuilding |
Source: Stacks implementation practice, 2026.
Measure before and after the pilot so the result is a number your CFO can compare:
Record days to close for each pilot business unit over the last three periods.
Count reconciliations signed off late and reviewer hours spent on approvals.
Log unmatched intercompany differences at working day three.
Export the audit trail for a sample of five reconciliations and time how long retrieval takes.
For a shortlist to run this test on, see our review of agentic close platforms for enterprise teams.
Why the Standard Advice Fails
The usual advice for a shared services close comes in two versions. One says lift and shift the work into the SSC, then standardise once it is in one place. The other says consolidate onto a single ERP first, because standardisation is impossible on mixed ledgers.
Lift and shift fails because the SSC inherits every local variation along with the work. Staff learn 12 checklists, so the expertise the centre was meant to build splits by entity. The group still cannot compare business units.
The close is the core of what a finance SSC does, so carrying 12 versions of it into the centre is the most expensive way to start.
The single-ERP route fails on timing. In our experience, an ERP consolidation across a European group runs for years, and the close has to keep running across mixed ledgers while it does.
There is a fair counterargument. If your ledgers are at end of support, or your charts of accounts cannot be mapped reliably, ERP consolidation may be the right first project. A common chart of accounts makes every later step easier, and no close tool fixes a ledger that cannot produce a reliable TB.
Most groups, though, do not have that problem. Their ledgers work, but the close process sitting on top of them is inconsistent. Standardise the policy, the calendar and the evidence first, run them across your existing ERPs, and then move the work into the SSC.
Why Choose Stacks for a Multi-Entity Shared Services Close
Stacks puts one close calendar and one set of controls across every entity, with regional variation set as configuration inside the same implementation. Stacks connects natively to NetSuite and works alongside your ERPs as the system of record, so there is nothing to migrate while you standardise.
The calendar, task dependencies and preparer/reviewer sign-off run through close management with multi-entity scope. Entity-level controls and enforced segregation of duties apply across the group, backed by our security and governance controls.
Pairs are matched and differences investigated through intercompany matching across entities, with an owner on every pair. Every entity's balances follow one reconciliation policy through account reconciliations in one workspace. Agents prepare the work as data arrives, and your team reviews the exceptions and signs off.
Epidemic Sound runs 102 bank accounts across 13 entities on Stacks. The team went live five weeks after signing, and its first close on Stacks, on 6 October 2025, tracked all 713 tasks across the 13 entities to completion. Reviewers now save around five hours per close on approvals alone, and you can read how in Epidemic Sound's multi-entity close.
FAQs for Standardising the Close in Shared Services
Is enterprise reconciliation software the same as financial close software?
No. Reconciliation software handles balance-level matching and sign-off, while close software manages the full calendar, dependencies and review across every close task.
What is the difference between intercompany reconciliation and sub-ledger-to-GL reconciliation?
Intercompany reconciliation agrees balances between two group entities so they eliminate at consolidation. Sub-ledger-to-GL reconciliation agrees a sub-ledger, such as receivables, to its control account in one entity's general ledger (GL).
Should every entity close on the same day?
Every entity should work to the same group deadline, but local working days and holidays can shift individual due dates. Hold those shifts as calendar configuration so the group view stays intact.
Which close tasks should stay with local finance teams?
Statutory reporting, local tax filings and counterparty dispute resolution should stay local. Those tasks still belong in the group calendar under the same evidence rules.
How many entities justify a shared services close?
The trigger is variation more than entity count. Once reviewers spend more time reconciling how entities work than reviewing what they report, a standardised shared services close pays for itself.
See How Stacks Maps to Your Close Process
Book a 30-minute walkthrough. We'll discuss your close process, show you which tasks run automatically, and outline the next step from there.
"If you want to achieve an agile, transparent, and significantly faster close without adding headcount, Stacks is the way to go."
Jessica Lindholm, VP of Accounting, Epidemic Sound
Trusted by fast-growing companies including: Datavant, Future, Cleo, Motorway, Nivoda, Yoto, Epidemic Sound

