The First Quarter After Completion: A Working Ledger for UK Acquirers

Completion is a legal event. Integration is an operating one. The sale and purchase agreement may transfer shares or assets, but it does not transfer the habits, relationships and informal knowledge that made the target work. For an owner-manager buying a smaller UK firm, the first 90 days are less about grand transformation than about preventing drift. Integration becomes an unmanaged project when nobody can say, on a given Friday, which customer conversations have taken place, which key staff are unsettled, which systems are still running in parallel and what the cash position will look like in thirteen weeks.

A one-page ledger is a modest instrument, but it gives the acquirer something more useful than a lengthy integration plan: a weekly control point. The ledger should sit alongside the completion checklist, not replace it. Its purpose is to convert the promises made during the deal into named actions, owners and dates, and to surface problems while they are still small enough to resolve.

Start with the customer, not the org chart

Acquirers often begin with structure: reporting lines, job titles and the shape of the combined management team. That is understandable, but it is rarely the most urgent risk. For a smaller UK business, revenue is usually concentrated in a modest number of customer relationships. The first ledger line should therefore be customer communications.

List the top twenty customers by revenue, together with the account owner, the last contact date and the next planned contact. Decide who will speak to each customer, what will be said and when. The message does not need to be elaborate, but it should be consistent. Customers will notice uncertainty quickly, particularly where the acquisition affects pricing, service levels, account management or delivery. A vague assurance that nothing will change is less credible than a clear statement of what will change, what will not, and whom to contact.

The ledger should also record any customer-specific commitments made during the sale process. If the seller promised continuity of terms or a particular service arrangement, that promise now belongs to the acquirer. It needs an owner and a date, not a place in a diligence file.

Retention is a ledger line, not a hope

Key-staff retention is the second line. In a smaller firm, a handful of people often carry customer knowledge, supplier relationships, technical know-how and the informal authority that keeps daily operations moving. The ledger should name the people who matter, not simply the people who appear on the organisation chart.

For each, record the risk, the planned conversation and the retention position. That may include revised terms, clearer decision rights, a defined role in the combined business or simply a near-term commitment about what will not change. The point is not to offer blanket guarantees. It is to remove avoidable uncertainty and to identify where a departure would cause operational damage.

Payroll continuity deserves specific attention. Changes to PAYE arrangements, pension administration or payroll providers can unsettle staff even when the legal employer remains the same. The ledger should show when payroll will run, who owns the handover and what checks have been completed before the first post-completion pay date.

Systems cutover: sequence and fallback

The third line is systems cutover. Smaller acquisitions often involve a patchwork of accounting software, customer records, stock systems, banking arrangements and specialist operational tools. The acquirer does not need to harmonise everything in 90 days. It does need to know the sequence, the dependencies and the fallback position.

A practical ledger entry for each system should cover the current owner, the intended cutover date, the data migration check, the period of dual running and the person authorised to stop or delay the change. Banking and payroll should be treated with particular care. A cutover that works in principle but fails at the first payment run is not a systems issue; it is a cash and credibility issue.

The ledger should also record access. New authority, removed passwords and amended bank mandates are mundane matters, but they are exactly the sort of detail that drifts when integration is treated as a background task.

Supplier terms and the cash consequence

The fourth line is supplier terms. List the top ten suppliers by spend or operational criticality. Record the contract term, notice period, change-of-control clause and payment terms. Some suppliers will need to be told about the acquisition; others will simply need to know that invoices, purchase orders and contacts remain valid. The ledger should distinguish between communication, consent and renegotiation.

Cash timing belongs alongside supplier terms, not in a separate finance exercise. The first 90 days often bring integration costs, professional fees, dual-running expenses and working-capital movements that were anticipated in the deal model but not assigned to a weekly forecast. A thirteen-week cash view should be reviewed at the same time as the ledger. Deferred consideration, earn-out mechanics and any completion adjustments should be visible, with clear ownership for the calculations and the supporting evidence.

The weekly rhythm

A ledger only works if it is reviewed. The most practical rhythm is a standing 45-minute meeting each week, chaired by the acquirer or the person accountable for integration. The agenda should be short: review each ledger line, confirm red, amber or green status, agree the next action and record the decision. One owner per line is essential. Shared ownership is usually another way of saying that nobody is accountable.

Every fourth week, the review should extend to a short written update for the board or funder. That update need not be elaborate. It should state what has changed, what has slipped, what cash effect is expected and what decision is required. The purpose is to create a record that can be relied upon later, when memories of the deal have faded and the operating reality has taken over.

What good looks like at day 90

By the end of the first quarter, a well-run integration should be able to demonstrate several simple things. Customer communication is complete for the most important accounts. Key staff have had a clear conversation about their future. Critical systems are either stable or have a documented fallback. Supplier terms are understood and the cash forecast reflects the post-completion operating pattern. None of this guarantees success, but it reduces the chance that integration will drift into an unmanaged project.

The ledger is not bureaucracy. It is a form of organisational memory and a practical test of whether the signed deal is becoming a working operation. For UK owner-managers buying smaller firms, that transition is where value is either protected or quietly eroded.