What systems does a shared services back office need after acquisitions?

A shared back office needs common finance, purchasing, and people systems with reporting by company.

A shared services center that supports several acquired companies needs a finance system or consolidated chart of accounts that handles multiple entities, shared purchasing and vendor records, a common approach to HR and payroll where practical, and reporting that shows results for each company and for the group. Workflow tools connect these so requests reach the right team.

The point of shared services is to handle common back-office work once, with consistent controls, rather than repeating it in every acquired company. That only works when the central team can see and act on each company’s transactions without logging into a different set of tools for each one. The systems decision largely determines whether consolidation delivers what the plan expects.

The goal is not identical companies. Acquired businesses keep their customers, brands, and often their legal entities. The shared back office provides common processes and data underneath, while preserving the distinctions that matter for tax, contracts, and reporting. Designing for that balance from the start avoids a later choice between forcing uniformity and giving up on consolidation.

Consolidate finance first, then purchasing, then people processes.

Finance usually consolidates first because it has the clearest rules and the greatest need for consistency. Accounts payable, accounts receivable, the period-end close, and bank reconciliation follow similar steps in most companies. Bringing them onto a shared chart of accounts and a common close calendar makes group reporting possible and gives the central team a stable foundation.

Purchasing tends to follow. A shared vendor list, common approval rules, and consolidated purchasing for items every company buys give the group better terms and clearer spending visibility. Purchase orders, receipts, and invoices should match in one system so accounts payable can pay against evidence rather than chasing approvals through email across several companies.

HR and payroll often come later because they touch employment terms, benefits, and local rules that differ by company and state. Start with shared records for headcount and roles, which reporting needs anyway, and consolidate payroll and benefits administration as contracts and plans allow. Moving too early here risks errors people feel directly in their pay, which damages trust in the whole program.

Handle each company’s differences with explicit mapping and configuration.

Acquired companies arrive with different charts of accounts, vendor lists, cost centers, approval habits, and fiscal practices. Map each one into the shared structure deliberately: which accounts roll into which group accounts, which vendors duplicate existing ones, and which cost centers correspond to which departments or locations. Keep the mappings as maintained data, not as one-time spreadsheets.

Some differences must remain. Separate legal entities need separate ledgers, bank accounts, tax filings, and sometimes separate approval authorities. Customer contracts may require invoices in a particular format or from a particular entity. The systems should support these through entity and location settings rather than exceptions handled from memory by the central team.

Decide which differences are required and which are habit. A company that approves purchases differently only because it always has should move to the shared rules. A company with a regulatory reason for a separate process should keep it, documented and visible. Writing these decisions down prevents the shared service center from accumulating special cases that nobody can later explain.

Report by company and in total from the same underlying data.

Leadership and the fund need two views: each company’s results, so managers stay accountable for their businesses, and the consolidated picture, so the group can be managed and reported as one. Both should come from the same transactions and mappings, so the company-level numbers add up to the total without manual adjustments on a separate spreadsheet.

Intercompany activity needs explicit handling. When the shared service center charges companies for its work, or companies sell to each other, those transactions must be recorded consistently on both sides and eliminated in consolidation. Automating the charges and eliminations removes one of the most common sources of period-end delays and disagreements between entity controllers and the group.

Operational reporting belongs alongside financial reporting. Measures such as invoice processing volume, time to pay vendors, collection performance, and open requests by company show whether the center is working. Reported by company, they also reveal which acquired businesses need more support and which processes still depend on informal local workarounds.

Move each add-on into shared services in stages without disrupting it.

A new acquisition should not have its back office switched over all at once. Start by giving the central team read access to its financial data and mapping it into group reporting. Then move one function at a time, often payables first, running the old and new processes in parallel for at least one full close so differences surface before the local process stops.

Communicate clearly with the acquired company’s staff. Back-office employees may be anxious about their roles, and vendors and customers need to know about any change in who pays or invoices them. A written plan that names what changes, when, and who to contact for each function reduces errors and keeps relationships intact during the transition.

Baybloom builds the integrations, workflows, and reporting that connect acquired companies to a shared back office. Whatever the systems chosen, the pattern repeats with every deal: map the new company into shared structures, report on it before changing its processes, move functions one at a time with parallel running, and keep a documented list of the differences the group has agreed to keep.

Put it into practice

Talk through the project you are considering.

Bring the workflow, the systems around it, and the questions you need to resolve. We can help define a useful next step.