TSA Pre-Signing Review
Scope every jurisdiction before you commit.
Fixed-fee review in 48 hours. Senior team on day one. The first conversation is always free.
An international carve-out TSA spans countries, legal entities, currencies, and regulators, and what looks like one agreement is really many local transitions stacked together. A service that exits cleanly in one country can be blocked by employment law or data rules in another. Mapping that jurisdictional complexity is the core of a cross-border TSA exit strategy.
An international carve-out separates a business that operates across multiple countries, which means the TSA is not one transition but a set of them running in parallel. Each country has its own legal entity, its own employment rules, its own tax and statutory reporting, and often its own local systems. A service that the deal team treats as a single line in the catalog may have to be exited differently in every country it touches.
The headline risk is treating the carve-out as global when it is actually local everywhere. Payroll, benefits, statutory accounting, and employee transfers are governed country by country, and a plan that assumes one approach will break wherever local law differs. The buyer that maps the carve-out jurisdiction by jurisdiction sees the real shape of the work. The buyer that maps it globally discovers the local complications during execution, when they are most expensive.
Entity setup is often the gating item. In many countries the buyer cannot run payroll, hold contracts, or employ people until a local legal entity exists and is registered, which can take months. The TSA has to bridge the period until each local entity is operational, and that timeline, not the buyer's preference, sets how long the TSA must run in each country.
Employee transfer rules vary enormously and frequently control the whole timeline. In much of Europe, automatic transfer regimes move employees with the business and constrain how and when changes can happen. Elsewhere, employees must be terminated and rehired, with local notice and consultation requirements. The TSA covering HR and payroll has to accommodate whichever regime applies in each country, and those regimes can add months no one planned for.
Data protection is the other hard constraint. Moving employee and customer data between the seller's systems and the buyer's crosses regulatory lines, and regimes like the European rules restrict cross-border data transfer in ways that directly affect how IT services exit. A migration that is trivial domestically can require specific legal mechanisms and safeguards when the data crosses a border, and the TSA exit plan has to build those in rather than discover them.
Works councils and local consultation add real time in several jurisdictions. Where employee representative bodies must be consulted before changes, the buyer cannot simply execute a migration on its own schedule. These requirements are not obstacles to work around, they are fixed inputs to the timeline, and the TSA term in each country has to respect them or the exit will not be lawful.
An international TSA moves money across currencies and tax jurisdictions, which complicates the charging mechanics. Cost-plus charges raised in one country and paid from another involve currency conversion, transfer pricing rules, and local tax treatment that a domestic TSA never faces. The buyer needs clarity on which entity is charging which, in what currency, and how the mark-up is treated for tax, because errors here create disputes and unexpected cost.
Transfer pricing deserves particular attention. Intercompany service charges between the seller's entities and the buyer's have to satisfy the tax authorities in every country involved, and a TSA charging structure that ignores this can create tax exposure for both sides. The pricing has to be defensible as arm's length in each jurisdiction, which is a higher bar than a single country TSA has to clear.
Permanent establishment risk lurks in cross-border services. Where the seller's people deliver services into a country, or the buyer's people operate in the seller's, tax authorities may treat that as a taxable presence. The TSA has to be structured to manage that risk, and the buyer that ignores it can inherit a tax problem long after the services have ended.
Governing an international TSA exit means coordinating many local migrations that each move at the pace their jurisdiction allows. A central program gives visibility and consistency, but local execution has to respect local law and local timelines. The structure that works is a central program office setting standards and tracking the portfolio, with local leads who own execution in each country and know the local constraints.
Sequencing follows the jurisdictional realities, not the org chart. Countries where entity setup and employee transfer are fast can exit early. Countries with long consultation requirements or complex data rules need more time and have to be planned around their constraints. A single global exit date is almost always wrong. A schedule of country specific exit dates, rolled up into a portfolio view, is how an international carve-out actually completes.
Visibility across the whole picture is essential. With many countries each on their own clock, the buyer needs a portfolio dashboard showing every jurisdiction's status, exit date, and blockers. Without it, a single delayed country can extend the entire TSA and its cost. With it, the program can focus resources on the jurisdictions on the critical path and keep the overall exit on track.
The hardest balance in an international carve-out is between central consistency and local accuracy. Run it entirely centrally and the program will trample local law and stall. Run it entirely locally and it fragments into inconsistent transitions with no portfolio control. The buyer needs a central program that sets standards, pricing discipline, and governance, paired with credible local knowledge in each jurisdiction.
Local input has to be real, not assumed. Employment regimes, data rules, entity requirements, and tax treatment differ in ways that genuinely change the plan, and a central team that guesses at them creates risk. The program brings in local legal, tax, and operational expertise for each material jurisdiction, and feeds those constraints back into a central plan that stays consistent where it can and adapts where it must.
That combination is what an experienced buyer-side advisor brings to a cross-border deal. The work starts before signing, scoping each jurisdiction's service catalog and constraints so the TSA term and price reflect local reality. Our TSA Pre-Signing Review maps that complexity early, so the buyer commits to a term it can actually meet in every country rather than a global guess that breaks at the first border.
It spans multiple countries, legal entities, currencies, and regulators, so what looks like one agreement is really many local transitions running in parallel. Each country has its own employment law, data rules, tax treatment, and entity requirements. A service that exits cleanly in one country can be blocked or delayed in another, so the carve-out has to be mapped jurisdiction by jurisdiction.
Employment transfer rules and entity setup. In many countries the buyer cannot run payroll or employ people until a local entity is registered, which can take months. Employee transfer regimes, works council consultation, and local notice requirements add fixed time that the TSA term must respect. These are inputs to the timeline, not obstacles to work around.
Moving employee and customer data between the seller's and buyer's systems across borders crosses regulatory lines. Regimes such as the European rules restrict cross-border data transfer and require specific legal mechanisms and safeguards. A migration that is trivial domestically can need particular legal structures when data crosses a border, and the exit plan has to build those in from the start.
Almost never. Countries move at the pace their law allows, so a single global date is usually wrong. Plan country specific exit dates, sequence the jurisdictions where entity setup and transfer are fast to exit early, and give those with long consultation or data constraints more time. Roll the country dates into a portfolio view governed centrally with local execution leads.
How transition services survive a Section 363 asset sale and a winding down estate.
Read the article →Negotiating transition services when the seller is under financial stress.
Read the article →Unwinding public company corporate functions when a sponsor takes a company private.
Read the article →The 90-day governance, IT, finance, HR and procurement separation plan we run on live carve-outs. Get the playbook plus the bi-weekly Day One Letter — short, signal-heavy, buyer-side.
No spam. Unsubscribe in one click. · Read the overview first →
Fixed-fee review in 48 hours. Senior team on day one. The first conversation is always free.
Seven buyer-side moves to exit a Transition Services Agreement on time and below budget. The mark-up, the extension-fee curve, exit sequencing, and the 11-month calendar.
A representative $120M-revenue carve-out runs a Transition Services Agreement across eight functions in five jurisdictions. Borders multiply every separation by entity, regulator, and data-residency rule. The moves below cut the exit from a 17-month drift to an 8-month managed exit and remove $2.7M of mark-up and stranded cost — with the long-lead-time items, not the systems, on the critical path.
One tactic, one benchmark, or one pattern from a recent buyer-side engagement. Short. Signal heavy. Free.
Subscribe to The Day One Letter →