Venture Growth Partners outsourced CFO services
SuivreVue d'ensemble
-
Fondée Date 27 février 1963
-
Les secteurs Informatique
-
Offres D'Emploi 0
-
Vu 20
Description De L'Entreprise
Accounting integration after a business acquisition: 5 checks
Accounting integration after a business acquisition is the work of turning two sets of books into one you can actually run the company from. If you just closed a deal and your monthly close now takes twice as long, the problem is rarely the software. It is that nobody decided who owns which account, which rules survive, and how the two calendars line up. The fix is a short list of checks, done in order.
Start with the chart of accounts, not the software
The first instinct after closing is to pick a platform and migrate everything into it. That order is backwards. The chart of accounts is the skeleton of every report you will produce, and merging two skeletons is a design decision, not a technical one. Do it before anyone touches a migration tool.
Pull both charts side by side and mark every account that exists in only one company. Some of those are real differences in how the businesses operate. A distributor may track freight separately while a service business buries it in cost of sales. Others are just naming drift: the same expense called « office » in one file and « administrative » in the other.
Decide on one structure and write down the rule for each account. The rule matters more than the label. If you cannot say in one sentence what belongs in an account, it will collect junk within a quarter.
Watch for the accounts that feed your key reports. Revenue lines, cost of goods, payroll, and anything an investor or lender will ask about need to be stable from day one. Everything else can be cleaned up later.
A practical test: take last month’s close from both companies and try to produce a single combined statement using only the new chart. If you have to invent a mapping on the fly, the chart is not finished.
Keep a mapping table that shows every old account and where it lands in the new structure. This is the document you will reach for when someone asks why a number moved. Without it, every question about a prior period turns into an archaeology project, and the person who built the original chart may not be around to answer.
Reconcile the balance sheet before you trust any report
A combined income statement can look reasonable while the balance sheet underneath it is wrong. That is the trap. Revenue and expenses are flows that reset every period, but the balance sheet carries history, and history from two companies rarely lines up on the first pass.
Start with cash. Bank reconciliations from both sides need to be current to the same date before you combine anything. If one company is three weeks behind, you are merging a snapshot with a guess.
Then work through the accounts that hide problems:
- Accounts receivable, where the two aging policies may differ
- Inventory, if either business carries stock and counts it differently
- Fixed assets, including how each side depreciates and what thresholds it uses
- Accrued liabilities, especially payroll, bonuses, and vacation
- Intercompany balances, which should net to zero once you combine
Intercompany is where most integrations stall. If the parent funded the acquired company before closing, there are balances on both sides that need to cancel. They rarely cancel on the first attempt, and the difference is usually a timing gap or a transaction one side never recorded.
Do not move past the balance sheet until every material account ties to something you can point at. A report is only useful if the underlying records are current. Make ownership and review part of the routine, not a one-time cleanup.
Set a materiality threshold before you start, so you know which differences to chase and which to write off with a note. Chasing a small variance for a week costs more than the variance itself. The threshold should be low enough that nothing meaningful slips through and high enough that the team is not buried in rounding differences.
Pick one close calendar and one set of cutoff rules
Two companies almost never close on the same schedule. One finishes in five days, the other takes three weeks. One cuts off on the last business day, the other waits for the final bank statement. Merging the books without merging the calendar produces numbers that look combined but are not comparable.
Choose the tighter calendar as the target, then work backward. If the combined close needs to land in ten business days, list what has to happen on each of those days and who does it. The list will expose the gaps fast.
Cutoff rules matter just as much. Decide the last day for revenue recognition, the last day for expense accruals, and how you treat transactions that arrive after the cutoff. Write these down. Verbal agreements about cutoff dissolve the first month someone is on vacation.
Expect the first two or three combined closes to run long. That is normal and not a sign the process is broken. What matters is whether each close is shorter than the last and whether the same problems keep appearing.
If the same account is wrong three months running, the issue is not effort. It is that the rule is unclear or the wrong person owns it.
One more habit helps: keep a running list of everything that delayed the close, with the reason. After three cycles, the list tells you exactly where to invest. Most teams find that two or three recurring bottlenecks cause most of the delay, and fixing those is cheaper than rebuilding the whole process.
Map who does what, and where the handoffs break
Integration fails more often on people than on systems. Two accounting teams, two sets of habits, and often two people who each think the other is handling a task. The handoffs are where things disappear.
Write down every recurring task in the close and name one owner for each. Not a team, a person. Shared ownership is the same as no ownership when a deadline slips.
Then look at the handoffs specifically. The moment work moves from one person to another is where errors and delays concentrate. Common ones:
- Someone in the acquired company sends a file that the parent team has to reformat
- Approvals that used to happen in person now cross time zones or offices
- Bank access and system permissions that were never granted to the new owner
- Questions that go to a person who left after the deal closed
Each handoff needs a defined trigger and a defined receiver. « Send the payroll file when it is final » is not a handoff. « Payroll sends the final register to the controller by the second business day » is.
Give the combined team a single place to raise problems during the first few closes. A short weekly call or a shared list works. The goal is to catch the same issue twice, not five times.
Watch for the tasks that quietly lost an owner in the transition. Someone who handled a reconciliation at the acquired company may now report to a different manager and assume the parent team took it over. Nobody notices until the account is wrong at close. A simple owner list, reviewed once a month, catches these before they become a pattern.
Decide which policies survive and which get replaced
Every company has its own way of handling revenue recognition, capitalization thresholds, expense approvals, and reserves. After a deal, you have two versions of each. Leaving both in place means your combined statements are built on inconsistent rules.
Go policy by policy and pick one. For revenue, the standard is ASC 606, so the question is not which framework to use but how each company applied it and where the judgments differ. Contract terms, performance obligations, and timing of recognition are the usual friction points.
For smaller items, set thresholds and stick to them. What gets capitalized versus expensed, what needs a second approval, how large a variance triggers an investigation. These sound minor until you are explaining to a lender why two divisions treat the same purchase differently.
Document each decision in one page or less. The document is not for auditors. It is for the person who joins in a year and needs to know why the rule exists.
Where the two policies are close, pick the simpler one. Complexity has a cost every single month, fractional chief financial officer Advisory and the benefit of a more precise rule is often invisible in the reports anyone actually reads.
Pay attention to the policies that touch cash. How each company handles customer deposits, prepayments, and refunds changes when revenue lands and how working capital looks. Two reasonable approaches can produce very different cash pictures for the same underlying business, and that difference shows up the moment a lender asks for a cash flow forecast.
Rebuild reporting around the questions people ask
Once the records are combined, the reports usually are not. You end up with a stack of statements that technically include both companies but do not answer the questions the business now has. That is the point where integration stops paying off.
Start from the questions, not the statements. What does the owner want to see monthly? What will a lender ask for? What does an investor want before the next round? Build the reporting package backward from those.
Most growing companies land on a similar core:
- A combined income statement with comparison to budget and to the prior period
- A cash flow view that shows where cash came from and where it went
- A working capital summary covering receivables, payables, and inventory
- A short list of the metrics the business is actually managed by
Keep the package short enough that someone reads it. A twenty-page report that nobody opens is worse than a two-page one that drives a decision.
Set a review routine around it. Someone prepares, someone reviews, and the two are not the same person. That separation is what catches errors before they reach a lender or an investor.
Give each report a clear owner and a deadline that sits before the meeting where it will be used. A report that arrives the morning of the board call is a report nobody had time to question. Building in a day of buffer turns the package from a formality into something the team can actually act on.
Watch the common beliefs that slow integration down
Several assumptions sound reasonable and cause most of the delay. Naming them helps you spot them in your own plan before they cost you a quarter.
| Common belief | What usually happens | What to do instead |
|---|---|---|
| New software will fix the mess | The same unclear rules move into a cleaner system | Decide the chart and policies first, then migrate |
| One combined close is enough to settle things | Problems surface over several cycles, not one | Plan for three closes before the process stabilizes |
| The acquired team will adapt on its own | Habits persist and handoffs stay undefined | Name owners and write the handoffs down |
| Reporting can wait until the books are clean | Decisions get made without usable numbers | Build a short package early and improve it |
The software belief is the most expensive. A platform migration is a project with a start and an end, and it feels like progress. But if the account structure and the cutoff rules are still ambiguous, the new system just holds the same confusion in a nicer interface.
The reporting belief is the most common. Teams postpone reporting until the records are perfect, then make hiring, pricing, and spending decisions on gut feel for months. A rough combined report reviewed on a schedule beats a perfect one that arrives late.
There is a quieter belief underneath these: that the acquired company’s way of doing things was somehow less rigorous. Often it was simply different, and occasionally it was better. Treating the integration as a merger of practices rather than a takeover of one by the other tends to surface improvements the parent team would otherwise miss.
Set the first ninety days as a sequence, not a sprint
Trying to finish everything at once is how integrations stall. The work has a natural order, and skipping ahead creates rework. Treat the first months as a sequence with clear checkpoints.
A workable order looks like this:
- Agree on the combined chart of accounts and the mapping rules
- Reconcile the balance sheet to a common date
- Set one close calendar and one set of cutoff rules
- Assign an owner to every recurring task and define the handoffs
- Choose which policies survive and document the decisions
- Build a short reporting package and start a review routine
Each step depends on the one before it. Rebuilding reports before the chart is settled means doing it twice. Assigning owners before the calendar is fixed means assigning the wrong work.
Set a checkpoint at the end of each combined close to ask what broke and what to change. Small corrections each month beat a large overhaul later.
Expect the sequence to take longer than the deal itself. That is normal. The acquisition closes on a date; the accounting behind it takes a few cycles to settle into something repeatable.
Resist the urge to add steps to the sequence. Every extra workstream competes for the same people, and the ones that matter most are the ones that unblock the next close. If a task can wait a quarter without affecting the numbers anyone relies on, it can wait.
Know when to bring in outside help
Some integrations run fine with the existing team. Others need outside capacity, and the signal is usually capacity rather than complexity. If your controller is closing the books at midnight for the third month running, the problem is not skill.
Outside Venture Growth Partners Support For Preparing To Sell A Business tends to make sense in a few situations. A transaction is coming, whether a raise, a loan, or a sale, and the combined records need to hold up to review. The internal team is small and the integration is competing with day-to-day work. Or the two companies used genuinely different accounting approaches and nobody internally has seen the other one before.
What outside help should not be is a substitute for decisions. A good engagement clarifies the chart, the policies, and the reporting routine, then hands them back. If the work stays dependent on the outside person to function, the loop never closed.
Scope should match the stage. A company that just closed its first acquisition needs different support than one integrating a third. Ask what the engagement produces and who owns it afterward. If the answer is a set of documents and a trained internal owner, the scope is right.
Be skeptical of any promise about outcomes. Integration work improves the reliability of your records and the speed of your reporting. It does not guarantee a financing, a sale, or a particular financial result, and anyone who says otherwise is selling something else.
Ask one more question before signing anything: what does the handover look like on the last day? A clear answer names the documents, the training, and the internal person who will own each routine going forward. A vague answer usually means the dependency is the point, and that is the opposite of what you need.
Use this test to decide if your integration is actually working
The clearest signal is not whether the books are combined. It is whether you can answer a question about the business without asking someone to go check. If a lender asks for trailing revenue by month, or you want to know whether margins moved after the deal, the answer should come from a report you already have.
Apply three tests at the end of each close:
- Can you produce a combined statement without manual adjustments that only one person understands?
- Did the close finish on the same calendar as last month, or faster?
- Were the same accounts wrong again, or did the errors change?
If the answer to the first is no, the chart or the mapping is still unfinished. If the second is no, the calendar or the handoffs need attention. If the third is yes, the rules are unclear and the same problem will keep returning.
Repeat the test each cycle. Integration is not a project you finish and file away. It is a routine that either gets tighter or drifts, and the drift is quiet until a lender or an investor asks a question you cannot answer from your own reports.
When all three tests pass for two closes in a row, the loop is closed. From there, the work shifts from fixing the integration to using it, which is the only reason to do any of this in the first place.
