Table of Contents
Build the On-Ramp Before You Need It
Part 2 of our nine-part Multi-Entity ERP Implementation series. Previously: Why Adding a Company Never Just Doubles the Work
The term “acquisition-ready” often comes up in ERP discussions as if it has a specific meaning. Usually it means “the software can technically add another company.” That is true of almost every platform on the market and tells you almost nothing useful. The real question is whether your team already knows what to do with a new company before the deal is finalized.
Being ready for the next acquisition, or the next joint venture, is a question of structure, not system features. The decision is shaped by how you think about your group today, long before a letter of intent is drafted.
Understand Your Group’s Identity
Before you can plan for a company you have not bought yet, you need a working answer to a bigger question: is this group trying to operate more like one unified business, or more like a portfolio of unique brands? Neither answer is wrong, but each one points to a completely different strategy for future acquisitions.
Not Every “Acquisition” Is Actually an Acquisition
Here is something worth saying out loud in the planning stage: plenty of deals called acquisitions start life as joint ventures or minority stakes. The system implications are wildly different depending on which one you are doing. Buying a controlling interest and consolidating is one project. Taking a minority position and getting an equity pickup is another. Standing up a joint venture where you are not the managing partner is a third, and it may not touch your ERP environment at all. Determine which of these may apply before anyone starts discussing the new company code or ID.
Five Ways a New Company Can Land
Once you know what kind of deal you are doing, the next decision is how the new company should integrate into your environment. There is no single right answer, but there are only so many reasonable options, and naming them up front saves a headache later.
| Landing Type | What It Means | What Day 1 Success Looks Like |
|---|---|---|
| Tuck-in | Merge into an existing company where legally possible, using your existing template | One set of books, nothing new to reconcile |
| Integrate and keep | New company in the same environment, matching business-model template, full trade setup with the rest of the group | Balanced intercompany and a clean group reporting pack |
| Shared services only | New company keeps its own operations but plugs into group AP, AR, or treasury | Visibility to cash and a period close that works |
| Hold separate | New company (or delayed onboarding) with minimal integration, isolated master data | Statutory books, plus a line in the consolidation |
| Partner or JV | Your own company, a shell company, or sometimes no company in your ERP at all, depending on who manages it | An agreed system of record, and an unwind path everyone has already acknowledged |
Notice that “Day 1 success” is different in every row. A tuck-in that produces one clean set of books on day one is a win. Similarly, a hold-separate arrangement that produces one clean set of books and nothing else is also a win, for a completely different reason. Evaluating every type of integration against the same standard can lead teams to either under-integrate a company that should be fully incorporated or over-build a company that was only meant to remain passive.
Day 1 Is Not Day 100, and Confusing Them Is Costly
Day 1 needs are generally consistent regardless of landing type: can we pay people, can we manage cash, can we close the books. Day 100 needs focus on processes, templates, and master data, and they can vary enormously depending on the landing type you picked. Teams that build a 100-day system plan when they needed a 100-day operational plan tend to spend the first month solving the wrong problems. Meanwhile, the issues that mattered, such as payroll, cash visibility, and a closeable set of books, may be left unattended.
What Diligence Should Provide the ERP Team
Diligence in a joint venture or acquisition scenario typically results in a straightforward set of earnings adjustments, which may seem sufficient at first glance. However, for a team that plans to continue acquiring or partnering, diligence should also produce several key components: an entity-purpose statement, a preliminary chart-of-accounts crosswalk, an intercompany process flow for transactions that don’t yet exist but will once the deal is finalized, and a landing type.
None of this requires the acquisition team to have in-depth knowledge of your ERP system. Instead, it requires finance and legal to join the design discussions before the letter of intent is prepared, not after.
Develop an Essential Toolkit
A group that is genuinely ready for its next company typically has a concise list of tools at the ready rather than created under a tight deadline:
- A shared chart of accounts that aligns with the target without redesigning.
- A clear strategy for consolidation that does not require operational integration.
- A known path for intercompany, if the plan is to integrate.
- Established data-sharing and security rules, so a new sibling does not inherit the entire group’s customers, vendors, and profit information on day one.
While it may not seem glamorous, these artifacts are essential. They prepare the sixth company for a smooth transition, avoiding the need to revisit decisions made by the first five companies.
The Container Comes Next
Picking a landing type answers how a new company should behave once it exists. It does not answer whether it should be a legal entity, a reporting segment, or something else in your ERP at all. That is a different decision, and it is where teams tend to make companies out of things that were never companies to begin with. More on that in the next blog!
Map your next deal with our free Landing Matrix, which compares tuck-in, integrate-and-keep, shared services only, hold separate, and partner or JV approaches side by side. Download the Landing Matrix
Multi-Entity ERP Template Download Form 2