Most acquisitions of a division or business unit close before the buyer can run every function on its own. Payroll still runs through the seller's system, customer invoices go out from the seller's accounting platform, and staff log in with credentials the seller controls. A transition services agreement (TSA) is the contract under which the seller (or sometimes the buyer) keeps providing defined services such as IT, accounting, and HR for a fixed period after closing, at an agreed price and standard, so the acquired business keeps operating while the buyer builds its own infrastructure.
In mergers and acquisitions, the TSA is where business continuity becomes a set of enforceable promises. A vague one leaves the buyer paying for services it cannot measure and leaves the seller supporting a business it no longer owns, with no clear end date. At Beganyi Law, we negotiate these agreements alongside the purchase documents and the tax plan, so the post-closing support matches what the parties priced into the deal.
If you are preparing to buy or sell part of an Ontario business and want the transition terms settled before closing, you can arrange a confidential consultation or call us at +1 647-977-7749.
Key Takeaways
- A TSA keeps shared services running after closing while the buyer becomes self-sufficient.
- Precise service schedules, measurable standards, and clear fees prevent most post-closing disputes.
- Every service needs its own end date, exit milestones, and a plan for data and knowledge handover.
When Does a Deal Need Temporary Post-Closing Support?
A deal needs a TSA whenever the business being sold depends on people, systems, or contracts that stay with the seller after closing. That dependency is most common in carve-outs and divestitures, where one company sells a division but keeps the shared back office that served it.
What Does a TSA Do for the Buyer and Seller?
For the buyer (the recipient), a TSA buys time. It keeps the acquired company running on familiar systems while the buyer migrates payroll, licenses software, hires finance staff, and stands up its own operational support.
For the seller (the provider), the TSA caps and defines an obligation that would otherwise be informal and open-ended. Without a written agreement, a seller's IT team ends up fielding requests from the buyer months after closing, with no fee and no limit on liability.
The arrangement can also run the other way. In a reverse TSA, the buyer provides services to the seller because the sold business housed a function the seller's retained operations still need. Some deals use a bilateral TSA where each side serves the other. Decide which model applies before the first draft, because a bilateral agreement pushes both parties toward balanced terms: any burden one side imposes will be requested in return.
Why Carve-Outs and Divestitures Create Shared-Service Dependencies
A standalone company sold through a share purchase usually brings its own functions with it. A carve-out is different. The division being sold has relied on its parent's centralized finance, legal, HR, tax, and IT functions, often with no separate staff or contracts of its own.
The same issue arises in corporate restructuring that precedes a sale, and in asset deals where the buyer takes only selected assets. The choice of share or asset transaction structure shapes how much transitional support the buyer needs, because an asset buyer starts with no existing employer entity, contracts, or system accounts.
In some carve-outs, regulatory or contractual restrictions prevent the buyer from operating the business immediately, and the seller effectively runs it on the buyer's behalf for a period. Those arrangements need far more detail than a typical back-office TSA.
How Does the TSA Fit With the Purchase Agreement at Closing?
The TSA is an ancillary agreement to the main purchase agreement, whether that is an asset purchase agreement or a stock (share) purchase agreement. The form of TSA is usually attached as an exhibit (Exhibit A or Exhibit F, depending on how the deal documents are organized), and the purchase agreement requires it to be executed and delivered at closing.
That structure has practical consequences:
- Negotiate the TSA alongside the purchase agreement. Once the purchase agreement is signed, the seller has little reason to agree to generous service terms.
- Align definitions. Terms like "Business," "Excluded Assets," and "Closing Date" should mean the same thing in both documents.
- Coordinate remedies. The purchase agreement's indemnity regime and the TSA's liability cap must not contradict each other.
On the buy side, our buy-side advisory work treats the TSA as a closing deliverable with the same priority as the purchase agreement itself.
How Does Contract Negotiation Differ From Integration Planning?
The TSA and the integration plan answer different questions. The TSA is a binding contract: it states what the provider must deliver, to what standard, for what fee, until what date, and what happens if it fails. The integration plan is the buyer's internal roadmap for absorbing the business: system migration, reporting lines, culture, and combined operations.
The two must connect. Each TSA end date should match a milestone in the integration plan, such as payroll going live on the buyer's platform. But the seller is not bound by the buyer's integration plan, and the buyer cannot enforce a step that never made it into the TSA. Our approach to post-merger integration in Ontario starts by turning integration assumptions into TSA obligations before signing.
What Should Service Schedules, Standards, and Fees Cover?
The schedules are the working heart of the TSA: each one should name the service, who performs it, how well, at what price, and until when. The body of the agreement handles legal mechanics, while the schedules decide whether the transition succeeds.
Define IT, Accounting, HR, and Other Essential Services
The scope of services is usually set out in Schedule A, broken into separate service descriptions. Common categories include:
Function | Typical TSA services |
|---|---|
IT support | Network and email access, ERP and application hosting, help desk, user provisioning, cybersecurity monitoring |
Accounting | Accounts payable and receivable, general ledger, month-end close, financial reporting |
Human resources | Payroll processing, benefits administration, HR records |
Tax | Return preparation support, sales tax filings for the transition period |
Business operations | Procurement, warehousing, logistics, customer service, shared office space |
Sellers want the scope limited to services listed in the schedules. Buyers want a right to add omitted services that the business received before closing, at comparable terms. A reasonable compromise is an "omitted services" clause that covers services the business used in the 12 months before closing, requested within a set window after closing.
Build a Service Schedule With Clear Responsibilities and Dependencies
Each service schedule should cover:
- A specific description of the service, with volumes where relevant (for example, payroll for up to 85 employees, biweekly)
- The provider entity and whether any part is subcontracted
- The recipient's own responsibilities, such as submitting timesheets by a deadline
- Dependencies on other services or third-party systems
- Service period and any extension right
- Fees and the charging method
- Named service coordinators on each side
Dependencies cause the most trouble in our experience. If payroll relies on the HR information system, ending HR system access early breaks payroll. Map services by level (entity, system, and individual user) so these links are visible before the schedules are finalized.
Set Measurable Service Levels and Performance Remedies
Providers usually agree to perform services in substantially the same manner, scope, and quality as before closing, using commercially reasonable efforts. That baseline is fair, because the seller is not a professional outsourcer, but it only works if "the same manner" can be measured.
For critical services, set specific performance standards: system uptime percentages, invoice processing within a fixed number of business days, payroll errors corrected before the next pay run. Remedies usually include service credits, a requirement to re-perform the service at no charge, and escalation. Sellers resist termination rights tied to service failures, so focus hard service levels on the few functions where a failure stops the business.
Negotiate Service Fees, Pass-Through Costs, and Tax Treatment
Service charges follow one of a few models:
- At cost: the buyer reimburses the provider's out-of-pocket and allocated internal costs.
- Cost-plus: cost plus a fixed markup, compensating the seller for diverting resources.
- Fixed monthly fee: simple to administer, with a true-up for volume changes.
- Threshold billing: internal staff time is free up to an agreed number of hours, then billed hourly.
The agreement should also cover pass-through costs (third-party licence and consent fees), invoicing and payment terms, set-off rights, and fee step-ups if the buyer extends a service. Stranded costs deserve their own clause: when a service ends, the seller may be left paying for software seats or staff it no longer needs.
Tax treatment needs attention too. TSA services such as accounting are taxable supplies for GST/HST purposes, and a supply made in Ontario attracts 13% HST. State whether fees are exclusive of HST and who issues invoices, and coordinate any cross-border services with your accountant.
How Should the Parties Allocate Legal and Operational Risk?
Risk allocation in a TSA reflects one commercial fact: the provider earns modest fees for a service it does not normally sell, so it will not accept the liability of a full outsourcing contract. The buyer, in turn, needs enough protection that a service failure does not destroy the value it just paid for.
Identify Third-Party Consents and Vendor Restrictions During Due Diligence
Many TSA services run on third-party software, cloud platforms, and vendor contracts. Those contracts frequently restrict use to the licensee and its affiliates, and the acquired business stops being an affiliate at closing. Providing access without vendor consent can put the seller in breach.
Identify these restrictions early. During due diligence for an Ontario acquisition, list every system each TSA service depends on and review the licence terms, including any change of control clause that the transaction triggers. Then decide in the TSA:
- Which party seeks each consent
- Who pays consent and transfer fees
- What happens if consent is refused (a workaround, a substitute service, or an early direct contract between the buyer and the vendor)
Protect Data Access, Confidential Information, and Intellectual Property
During the TSA period, the seller's systems often hold the buyer's data, and the buyer's users may have access to the seller's network. Both sides need firm confidentiality obligations, logical separation of data where possible, and access controls limited to the users who need them.
Privacy laws apply to the personal information moving between the parties. In Ontario, private-sector organizations collecting personal information in commercial activity are generally subject to PIPEDA, and health information custodians are governed by the Personal Health Information Protection Act, which requires secure retention, transfer, and disposal of records. The TSA should address safeguards, breach notification, and return or destruction of data at the end of each service.
On intellectual property, confirm that the buyer receives a limited licence to use the provider's tools and processes only to receive the services, and that data and work product belonging to the acquired business remain the buyer's.
Negotiate Liability Caps, Exclusions, and Indemnification
A common limitation of liability caps the provider's exposure at the fees paid under the TSA, sometimes over a trailing 12-month period. Indirect and consequential losses are usually excluded. Carve-outs from the cap are where negotiation happens, and buyers typically seek uncapped liability for:
- Gross negligence or wilful misconduct
- Breach of confidentiality or data protection obligations
- Intentional abandonment of a service
Indemnification under the TSA should not duplicate or override the purchase agreement. Our guide to the indemnification clause in Ontario business deals explains how those indemnity regimes are structured, and the TSA should state which regime governs a given loss.
Establish Escalation, Dispute Resolution, and Service Continuity Procedures
TSA disputes need fast answers because the business keeps running while the parties argue. Build a tiered process: service coordinators resolve operational issues within a few business days, then senior executives, then mediation or arbitration for unresolved matters.
Two continuity provisions protect the buyer most:
- No suspension during disputes. The provider keeps performing while a fee or performance dispute is resolved, unless the buyer fails to pay undisputed amounts.
- Business continuity commitments. The provider applies the same disaster recovery and backup protections to the buyer's services that it applies to its own operations.
How Do You Set a Workable Term and Exit Plan?
A workable term ends each service when the buyer can provably run it alone, and the exit plan defines that point in advance. Both parties want the TSA to end quickly, but buyers push for longer periods to protect operations, while sellers push for shorter ones and a covenant that the buyer will work toward self-sufficiency.
Set Service-Specific End Dates and Readiness Milestones
One end date for the whole TSA rarely fits. Payroll may migrate in three months, while ERP hosting may need twelve. Set a term for each service, with readiness milestones the buyer must reach, such as a parallel payroll run or completed user acceptance testing.
Milestones give both sides visibility. If the buyer misses a milestone, the parties know early that an extension discussion is coming.
Plan Data Migration, Knowledge Transfer, and Final Handover
The exit is where most TSAs fall short. The agreement should require the provider to deliver data in a usable, agreed format at the end of each service, support a reasonable number of test extractions, and cooperate with the buyer's new vendor.
Knowledge transfer matters as much as the data itself. Specify documentation of processes, access to key staff for a set number of hours, and a final handover checklist. Then confirm the provider deletes or returns the buyer's data and terminates the buyer's system access.
Agree on Extensions, Early Termination, and Wind-Down Charges
Extension rights usually take one of two forms: a one-time extension of a defined length on notice, or an extension available only where the buyer shows good-faith progress toward migration. Expect a fee step-up for extended periods.
Early termination lets the buyer stop a service once it is ready, typically on 30 to 60 days' notice. The seller will ask for wind-down charges to cover stranded costs it cannot cancel, so cap those charges and require documentation of the costs claimed.
Check Exit Obligations Against the Purchase Agreement Before Signing
Before signing, compare the TSA exit terms against the purchase agreement. Look at employee transfer dates, non-solicitation covenants that might block the buyer from hiring the seller staff who run a service, and assignment of contracts the buyer will take over directly.
Sellers should also confirm that the TSA does not quietly extend their obligations beyond what the deal priced in. Our sell-side representation includes this check, because an open-ended support obligation is a cost the seller absorbs after the purchase price is paid.
Negotiate Clear Support Obligations Before Closing
A transition services agreement works when it is negotiated with the same care as the purchase agreement and finished before closing. In corporate transactions involving carve-outs or shared systems, the TSA is what keeps the acquired business operating on day one.
The essentials are consistent across deals:
- Service schedules that describe each service, its volumes, and its dependencies
- Measurable standards for the services that would stop the business if they failed
- A clear fee model with pass-through costs, stranded costs, and HST addressed
- Third-party consents identified during due diligence, with a fallback for refusals
- Data, confidentiality, and liability terms that fit with the purchase agreement
- Service-specific end dates, migration milestones, and a documented handover
Business continuity after closing depends on these terms being agreed while both sides still have leverage. If you are buying or selling a business in Ontario, we can draft or review the TSA together with the transaction documents and the related tax planning.
Frequently Asked Questions
Is a transition services agreement required for every business acquisition?
No. A TSA is needed only when the acquired business relies on the seller's systems, staff, or contracts after closing. Share purchases of standalone companies frequently close without one, while carve-outs almost always need one.
How long should a transition services agreement last?
Most TSAs run between three and twelve months, with each service carrying its own end date. The right term matches the time the buyer needs to replace each function, plus a limited extension option.
Can the buyer provide transition services to the seller?
Yes. This is called a reverse TSA, and it applies when the sold business housed a function the seller's retained operations still need. Some deals combine both directions in a bilateral agreement.
Can I use a TSA template for an Ontario business sale?
A TSA template is a useful starting point for structure, but the schedules must be built from the specific business. Fees, HST, privacy obligations, and third-party consents all depend on the deal, and generic schedules are the usual source of post-closing disputes.
What happens if a third-party vendor refuses consent?
The TSA should already answer this. Common fallbacks include a substitute service, an alternative arrangement that avoids breaching the vendor contract, or the buyer signing its own agreement with the vendor earlier than planned.
Can a buyer stop one service before the rest of the TSA ends?
Yes, if the term and termination provisions allow partial early termination, which buyers should insist on. The seller will usually require notice of 30 to 60 days and may claim documented wind-down costs, and dependent services must be checked so stopping one does not disrupt another.