Finance GuideStandardise spend post acquisition

Why standardising spend is one of the first things you should fix post-acquisition

Henry Bewicke Author Profile Headshot
Written byHenry Bewicke
November 11, 2026
Accounting5 minutes
Spa, fitness hospitality maintenance taming decentralised purchasing across leisure sites

If you're the group finance director of a UK business that has just completed an acquisition, you have two pivotal dates ahead. The first month-end after completion is a few weeks away, and the board wants a combined view of the group for it. The ERP workstream, the one that will eventually put the acquired entity on the group's books properly, starts next quarter at the earliest.

Everything the acquired entity spends between those two dates is spent under rules that sit outside the rest of the group, and the first consolidated close has to be rebuilt from two exports.

In this article we'll look at why ERP integration takes months, what the first close needs from the acquired entity, and which spend decisions you can enforce in the first few weeks without waiting for it.

The first month-end after completion

Say you run finance for a 220-person services group that completed an acquisition in the middle of March, with month-end on the 31st. The business you bought has 60 people, its own finance manager and Xero; the group runs NetSuite.

The acquired entity has eleven company cards, a finance manager who approves her own supplier invoices because there has never been anyone else to do it, and a supplier list in a naming convention that doesn't match yours. The first close is a reconstruction with two exports reconciled by hand, spend already committed under limits nobody at group approved and sign-offs that exist in practice but nowhere on paper.

Why ERP integration takes months

There are a number of reasons that ERP integration tends to be slow after a deal. The chart of accounts has to be harmonised and a cutover planned, but it's often put off because the acquiring side assumes the system it already runs will do for now. Meanwhile the first close after a deal is where investors expect a straight answer and are least forgiving of errors (Binary Stream). A Unit4 survey of 600 finance and IT leaders in professional services put the average integration at eight months, with one in five taking more than a year.

The first thing to put in place is approval rights, because they don't depend on which ledger the spend ends up in. A delegation-of-authority matrix saying who can approve purchases and sign off supplier payments can be issued before any system is touched. Most groups write that matrix and stop there. The step they skip is making it enforceable in the acquired entity's cards and invoice routing, so that a card declines above its limit and an invoice over the finance manager's threshold goes to someone at group before it's paid.

Which decisions can you make before the ERP is integrated?

Groups usually try one of three things in the interim, but each falls short:

1. Push the group ERP onto the acquired entity fast. This runs into the harmonisation work above and takes months.

2. Run the entity on its own stack until migration. This leaves its spend rules and self-approving habits as they were, so every month adds to the reconstruction at close.

3. Issue a group spend policy by email. Limits that live in a document are advisory.

The approach that works is a plain order of operations, with the ERP decision as the line. Before the line, in the first few weeks after completion, set the acquired entity up as its own entity inside a group spend system, reissue its cards with per-card limits that apply at the point of purchase, set up the group's approval rules in that entity so the finance manager approves within a limit and someone at group approves above it, and route every supplier invoice through that approval into one payment run. After the line, when the ERP is chosen, you point the entity's accounting connection at it, and nothing about how the entity spends or approves has to change.

Standardising spend on the acquired entity first, with Moss

Moss is built for exactly this situation. A group admin adds the acquired company as a second entity and decides who works in it. Per-card limits and approval of card requests hold spend at the point of purchase, so the eleven inherited cards are replaced rather than carried over.

Each entity has its own approval rule book, so the group's rules are recreated in the acquired entity rather than inherited, with routing by amount, team, supplier, department or cost centre, and invoices are paid in one run with four-eyes authorisation. Each entity connects to its own ledger, whether that is Xero, NetSuite, Business Central or another system, so in the situation above the acquired entity keeps syncing to its Xero file until the NetSuite subsidiary exists, and then switches.

One thing to decide early: if the acquired company already uses Moss, its existing account can't simply be joined to the group's. It has to be set up again as an entity under the group, so agree that before anyone issues a new card.

What Moss leaves to the ERP: it standardises how the acquired entity spends, approves and pays, and syncs the result to whichever ledger the group chooses. It does not consolidate the group's numbers, eliminate intercompany balances or migrate the ERP; each entity's spend goes to its own ledger, and the consolidated accounts are built in the ERP or consolidation tool.

What the first close looks like

When you reach the first close, the acquired entity's spend arrives in its own ledger coded, approved and paid under the group's rules. The consolidation itself is still a spreadsheet, and that is fine, because the inputs are clean.

Find out more about how Moss works across multiple entities in our help centre.

FAQs

Henry Bewicke Author Profile Headshot

The Author:

Henry Bewicke

Having written for clients inluding the World Economic Forum and Harvard University Press, Henry has spent the last six years in the world of b2B SaaS. As Moss's Senior Content Manager he now writes about the tools and trends reshaping how modern finance teams work.

Blog CTA Headshot 1
Blog CTA Headshot 3
Blog CTA Headshot 2

Experience how Moss can help your business

Get a free 15 min demo by a Moss expert

Book an intro

Related Articles