Day 1 is the day the deal is legally closed and practice begins. With an acquisition within a single country, much of that falls under existing routines. With a cross-border acquisition, it's different: different legal systems, different banking systems, sometimes different languages on the payslip, and a time zone difference that determines who already has a problem at nine in the morning and who still has to wake up. Day 1 is not about the strategy of integration. It's about the question of whether the organization can keep functioning tomorrow.
The core of Day 1 is not progress, but preventing standstill. Can staff be paid. Do the systems that customers and suppliers need work. Are the people who need to make a decision tomorrow authorized to make it. That last point is less obvious than it seems in a cross-border deal, because signing authority and mandate are arranged differently per jurisdiction, and because who decides what on Day 1 is not automatically the same as who already decided things for the deal.
Not every contract needs attention on Day 1, but a limited group does: agreements with a change-of-control clause, contracts tied to a specific legal entity that changes as a result of the deal, and arrangements with suppliers or customers that technically expire without reconfirmation. Exactly which ones these are depends on the sector and the deal structure, but the question of which contracts need Day 1 attention in a cross-border acquisition is one that can have a different answer per country, because which contracts need Day 1 attention partly depends on local contract law. A contract that continues automatically in one country may require explicit confirmation in another.
Salaries, tax remittances and payments to critical suppliers form the core of what must not falter on Day 1. In a cross-border deal, there's an additional question of which banking relationships, which currencies and which local payment systems must remain intact while the legal structure above them changes. It's not about reviewing all payments, but about determining which flows must continue without interruption. What happens to payments on Day 1 is therefore one of the first questions that must be answered, and what happens to payments on Day 1 varies strongly by country, banking system, and whether the acquired entity retains its own account structure or not.
A common Day 1 problem is not strategic but practical: people who no longer have access to systems they need, or, conversely, people who retain access they should no longer have. In a cross-border acquisition, there's an additional question of which IT environments, which data centers and which local data protection legislation determine what does and doesn't transfer automatically. Which access rights need to be correct on Day 1 is a question that touches both security and continuity, and which access rights need to be correct on Day 1 partly depends on how the IT landscapes of both parties were already set up before the deal.
A cross-border deal often brings a series of legal steps that must be completed on or around Day 1: registration with local trade registers, changes to statutory directors, notifications to regulators. Some of these are legally bound to a deadline, others are practically necessary to, for example, keep bank accounts functioning. Which legal-form steps Day 1 requires differs by jurisdiction, and which legal-form steps are Day 1 requirements is a question that often needs to have been discussed with local advisors early in the process, not just on the day itself.
Employees, customers, suppliers and regulators should not all hear the same thing at the same time. In a cross-border deal, there's an additional layer: differences in works council rights, notification obligations and cultural expectations around how news is delivered. What is communicated on Day 1, and in what order, largely determines how the first weeks unfold, and what you communicate on Day 1 is therefore not a matter of drafting a press release, but of a sequence that can differ per country.
The biggest pitfall in Day 1 planning is wanting to arrange too much. A Day 1 list that feels like a complete integration is usually a sign that it contains items that could just as well wait until Day 30 or Day 100. Every item on the list should therefore also be checked against the question of whether it really needs to happen on Day 1, and sometimes even whether that part needs to be merged at all. Not everything that can be integrated needs to be integrated; making that distinction is part of the Day 1 planning itself, not a step afterward.
These points only become a Day 1 plan once they are placed in a concrete sequence, with owners and dependencies. That is precisely what the Day 1 generator from mergerintegration.net is for, together with the integration office that keeps track of what is still outstanding. The tool is under construction; anyone who wants to work with it already can join the waiting list.
Much of the work behind a Day 1 plan consists of searching through contracts, researching local regulations and drawing up checklists per jurisdiction. That is exactly the kind of work for which the work scan from FTE TO AI shows, per task, which part can be taken over by AI, and which part remains human work.
Vraag maar wat er op Day 1 moet staan, of wat integreren juist kapotmaakt.
Answers come from this site’s knowledge base. Not tailored advice, and not a scan of your company.