A Finance Integration Playbook for Serial Acquirers

The reusable artefacts that let a serial acquirer integrate the tenth company as fast as the first, and faster

A finance integration playbook is the standard method a serial acquirer uses to make every newly acquired company report reliably into the group, written down as a set of reusable artefacts rather than rebuilt from memory each time. In finance integration under private equity, where a platform is designed to make repeated bolt-on acquisitions, the difference between a group that scales and one that stalls is often whether this playbook exists. This article sets out what goes into it: the standard artefacts, the fixed sequence, the roles, and the one measure that tells you whether the playbook is actually working across deals.

Why Serial Acquirers Need a Playbook, Not a Plan

A plan is written once for one deal; a playbook is written once and run many times, so it is built to be handed to a different person on each acquisition and still produce the same result. A private equity backed platform that makes three or four bolt-ons a year cannot afford to rediscover the integration process every time, because the people running it change and the deals overlap.

The difference shows up in three ways:

• Transferable. A plan lives in the head of whoever wrote it. A playbook is a document a new deal lead can open and execute without a briefing.
• Improvable. Because it is written down, a playbook accumulates fixes. When one deal exposes a gap, the artefact is updated, and every later deal benefits.
• Measurable. A playbook has a defined start and end per deal, so time to first clean close can be tracked and compressed across the portfolio.

The Five Standard Artefacts

A working playbook is not a slide deck. It is a small set of files a deal lead actually opens on day one. These five carry most of the weight.

Artefact	What it contains	Why it saves time
Data request pack	The exact list of files needed from the target: trial balance at close, general ledger detail, AR and AP aging, fixed asset register, bank reconciliations, in the group’s own template	The subsidiary returns data in a usable shape the first time, not after three rounds of clarification
Chart of accounts mapping template	The group chart down one side, a column for the local account, and a precedent log of decisions made on earlier deals	Most accounts map by precedent in minutes, leaving only genuinely new items for judgement
Reporting package	The fixed group submission format: same tabs, same subtotals, same built-in validation checks	Every subsidiary submits identically, so consolidation is not reconciling ten different spreadsheets
Integration action tracker	Open items with an owner, a due date, a status and a materiality flag, one row per issue	Nothing found in the review is lost; the tracker is the single source of what is done and what is outstanding
Closing calendar	The group timetable with the subsidiary’s working day 4 to 6 deadline and the rehearsal date	The first live close is not the first time the deadline has been tested

The action tracker is the artefact that separates a real playbook from a tidy folder. Its columns are the working file: item, entity, account, description, owner, materiality, target date, status. A group that acquires often keeps one standard tracker layout so a controller moving between deals reads it instantly. The mechanics of building one belong to a dedicated method, and the balance-level version of it is set out in the review of accounts receivable and other accounts a CFO runs on entry.

The Fixed Integration Sequence

The artefacts are run in a set order. Writing the order down is what makes the process transferable.

• Step 1. Send the data request pack. On or before the day of close, from the standard template, so nothing is designed under time pressure.
• Step 2. Load and check the trial balance. Confirm it ties, sub-ledgers reconcile to control accounts, and the opening balance sheet agrees to the diligence figures. Discrepancies open a tracker row.
• Step 3. Complete the mapping. Local chart to group chart using the precedent log. Escalate only the genuinely new accounts.
• Step 4. Run a trial close on prior period data. This is the rehearsal. It exposes an untested mapping and an unrehearsed calendar cheaply, before a live deadline.
• Step 5. First live submission. Into the group package, on the group deadline, with open items tracked rather than blocking.
• Step 6. Update the playbook. Any gap this deal exposed is written back into the artefact so the next deal does not hit it.

Steps 2 and 3 draw on the standard review a group runs on any new entity, set out in what to review immediately after an acquisition, and the point at which the entity is ready to submit is covered in preparing a subsidiary that is ready for group reporting.

A Worked Example: Deal One Versus Deal Five

The figures below are illustrative, not a real engagement, and show only how a playbook changes the shape of the work.

A private equity backed platform integrates a run of similar bolt-ons, each a services business of roughly 30 to 50 million euros in revenue.

Deal five is not simpler than deal one. The company is the same size and no easier to integrate. The compression comes entirely from the artefacts: the data pack that lands usable data once, the precedent log that answers most mapping questions, and the rehearsed close. That is the return a playbook is meant to deliver, and the reason a serial acquirer builds one after the first or second deal rather than the tenth.

Roles and Cadence

A playbook needs owners, or it ages into a folder no one maintains.

The cadence that keeps it alive is the step 6 review: a short session after each first clean close where the deal lead and the owner update the artefacts. Skip it, and the playbook slowly stops matching how deals actually run. Consolidated accounts are a statutory requirement for the parent under the EU Accounting Directive 2013/34/EU, so a group that cannot integrate quickly is not just slow, it is exposed at every year end. The wider method the playbook operationalises is the first 100 days of finance integration.

Where the Playbook Does Not Apply

A playbook assumes the acquired company keeps ordinary accounting records that the standard sequence can run against. When that is not true, applying the playbook on its normal timeline produces a false sense of control.

• If the target has no monthly close, only an annual statutory position, step 4’s trial close has nothing to run against. Rebuild a monthly trial balance first, then start the playbook.
• If the target has no sub-ledger detail, only control account totals, step 2 cannot reconcile AR and AP, and those balances have to be reconstructed before mapping is meaningful.
• For a carve-out with no standalone history, the opening balance sheet is built, not requested, so the data request pack is the wrong starting artefact.

The discipline is to recognise these cases at step 2 and route them to a remediation track, rather than forcing them through a sequence built for companies that already keep monthly accounts. A playbook that cannot tell its normal case from its exceptions will apply the wrong clock to both.

Frequently Asked Questions

What is a finance integration playbook?

A finance integration playbook is the written, reusable method a serial acquirer runs on every deal to make an acquired company report reliably into the group. It is a set of artefacts, a data request pack, a mapping template, a reporting package, an action tracker and a closing calendar, plus a fixed sequence for running them.

Why does private equity finance integration rely on a playbook?

Because a private equity backed platform makes several bolt-on acquisitions a year, often with overlapping timelines and changing staff. A playbook lets a new deal lead run the integration to the same standard without a briefing, and it compresses the time from close to first clean group submission with each successive deal.

What is the single best measure of a good integration playbook?

The number of weeks from deal close to first reliable group submission. If that figure falls across successive acquisitions of similar size, the playbook is working. If the fifth deal takes as long as the first, the method is not being written down and reused, only repeated.

When should a group build its finance integration playbook?

After the first or second deal, not the tenth. The first integration teaches the sequence and exposes the hard mapping decisions. Writing those into artefacts straight away means the third deal already runs faster, rather than the group re-learning the same lessons on every acquisition.