In a cross-border acquisition, Day 1 is the moment when employees, customers and suppliers notice for the first time that something has changed, or precisely that it hasn't. Access is the most concrete part of this: something works, or it doesn't. There is no room for a gradual transition on this front. A badge that doesn't work, a login that gets refused or an account that doesn't pay, are visible from the very first minute.
Which access points these exactly are differs per deal. The acquisition of a manufacturing company with its own factory sites requires different things than the acquisition of a software company with a fully cloud-based environment. What remains constant is the need to map this part out completely before the deal closes, not afterwards.
IT access is usually the largest category. Think of email, ERP, CRM, HR systems, financial software and any customer portals. In a cross-border deal, there's the added question of which systems differ per country or entity, and which will be shared. An employee who can't log in on Day 1 to a system they need daily is an operational problem, regardless of how the integration proceeds further.
The question that often gets skipped here: do systems need to be merged, or can they continue to exist side by side until a later moment. Not every access point needs to be integrated on Day 1 already; some only need to keep working the way they worked before. The distinction between "must function" and "must already be merged" is one of the elements worked out in what needs to be arranged on Day 1.
Badges, keys, alarm codes and access to server rooms or warehouses are less visible in the preparation, but just as critical on the day itself. In acquisitions with locations in multiple countries, there's the added question of who has the authority to change these access rights, and whether that needs to be arranged locally or centrally. A security services provider that works on a contract basis in one country and on a subscription basis in another requires clarity on Day 1 already about which agreement applies.
Access to bank accounts, payment authorizations and cash flows is a category that is often underestimated. Who is allowed to approve a payment on Day 1, and at what amount does the limit lie. In a cross-border acquisition, local banking rules also come into play here: an authorization that suffices in one country may not be sufficient in another without additional documentation. Salary payments that fall around Day 1 are one of the few things where delay is not an option.
Some access points are not technical but contractual: a supplier that only delivers to the legal entity as it existed before the deal, a customer accustomed to a specific point of contact, a distribution agreement tied to a name. Which legal entity changes this affects and what needs to already be arranged for that on Day 1 is discussed in which legal entity steps Day 1 requires in a cross-border acquisition.
Not every access point has the same urgency, and not every access point needs to already reflect the end situation on Day 1. The question of who determines which access points temporarily continue to exist side by side and which are merged immediately is a decision that must already have been made before the deal closes, not on the morning itself. How that decision-making around Day 1 is arranged is described in who decides what on Day 1 in a cross-border acquisition. Those same decisions relate to what is communicated externally: a customer who gets a different payment address on Day 1 without explanation experiences that differently than a customer who was informed in advance, a topic addressed in what you communicate on Day 1 in a cross-border acquisition.
The underlying question with every access point is not just "does it work", but also "does it already need to be merged". Two ERP systems can continue running side by side until a more careful decision has been made about migration. Two bank account structures can continue to exist separately until the tax and legal consequences of merging have been calculated. Access on Day 1 is a minimum requirement, not an incentive to integrate everything on an accelerated basis. Which decisions belong in the short term and which deserve room to be made later is worked out in which decisions belong in the first hundred days.
All these access points: systems, buildings, accounts, contracts, must be mapped out, tested and assigned to someone responsible before closing. On Day 1 itself, there is no time left to discover that a password reset requires a local IT department that can't be reached, or that a payment authorization has to go through a notarial power of attorney that hasn't yet been drawn up. The generators and the integration office of mergerintegration.net are designed to systematically inventory this kind of access before the deal closes, with a decision list that establishes what must work on Day 1 and what will only be merged later.
Inventorying and assigning all these access points is itself also work: figuring out which systems exist, who has access to what, which contracts are affected. Part of that investigative work can be structured and accelerated with AI. FTE TO AI's work scan calculates per task which part of that work is suitable for that, so that the people responsible for Day 1 spend their time on the decisions that require attention, rather than on manually gathering the data on which those decisions rest.
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.