On the day of closing, nothing changes about the physical reality of a company, and everything changes in the legal and financial layer beneath it. Invoices that went through normally yesterday can get stuck today because an account, a mandate, or a currency flow was not included in the transfer. Payments are one of the few parts of an integration where a gap of a few days becomes immediately visible to suppliers, employees, and tax authorities. That makes this component suitable for a fixed checklist rather than improvisation after the fact.
The basics are easy to name, but in a cross-border deal every point runs through multiple jurisdictions. It concerns: which bank accounts are usable on Day 1 and for whom, which payment mandates remain valid and which need to be re-established with the bank, how salary payments in the country of the acquired entity continue without interruption, how accounts payable and receivable flows are recognized and processed as long as systems are not yet linked, and which currency and intercompany agreements are needed once money starts moving between the parent and the new entity. Each of these points needs an owner and an answer to the question of whether it is already done, in progress, or still needs to be figured out.
In addition, there is often a transition period during which the acquired entity still runs on the previous owner's banking relationships and payment infrastructure, governed by a transitional services agreement. What that agreement states, and until when it applies, determines how much room there is to transfer payments in an orderly manner rather than under time pressure.
Within a single country, a bank switch is already an operation with a lead time. Across borders, this is compounded by jurisdictions, regulators, and local banking practices that do not follow the same pace or the same documentation requirements. A mandate that is arranged with a signature in one country requires a notarial step or a registration with a central bank in another. Anyone who does not map this out in advance discovers the difference at the moment a payment should already have gone out.
This directly touches on the question which access rights need to be in order on Day 1 for a cross-border acquisition: payment systems are access in the most literal sense, and an employee who cannot check an account or approve a payment is effectively sidelined on day one.
Payments are a component where the question of whether centralization is desirable does not automatically deserve a positive answer. One shared payment system can provide overview and control, but it can also mean that a local entity becomes dependent on a process that does not properly follow the local rhythm of salary payments, tax remittances, or supplier terms. Before deciding to merge payment flows, it is worth determining what is lost in speed or local knowledge, and what that gains in control or cost savings. That weighing belongs to how you sort decisions by uncertainty cost: not everything that can be merged should be merged on Day 1, and sometimes postponement is the cheapest option.
Changing a payment mandate affects both the financial function and the legal structure of the acquired entity, and the question of who decides on this is not equally clearly answered in advance in every deal. Does it rest with the buyer's CFO, with the local country manager, or with a shared integration team? This connects to the question who decides what on Day 1 during a cross-border acquisition: without an established decision line, delay arises exactly at the moment speed is needed, namely when a payment must be approved and no one knows who is authorized to sign off.
The legal form of the acquired entity also plays a role here: a merger, a share transfer, or an asset deal each has different consequences for which accounts and contracts automatically transfer and which need to be newly established. That is precisely where which legal-form steps are Day 1 for a cross-border acquisition fills in what is already legally in place and what still needs to be arranged before an account is actually usable.
A complete list of what needs to be in place on Day 1 for payments does not prevent a bank from delaying a request or a local regulator from asking for more documentation than expected. What a list does do is prevent someone from discovering on the day itself that a step was overlooked. That is the difference between a problem that is solved before it becomes visible, and a problem that becomes visible to a supplier or an employee who does not get paid.
For this kind of work — figuring out mandates, drawing up overviews per jurisdiction, keeping track of the status of each action item — less human effort is often needed than it seems. FTE TO AI's work scan calculates per task which part of it can be taken over by AI, making it clear where a deal team's time is needed most and where a system can keep track of the overview.
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.