Transition Services Agreement: How to Set Service End Dates
Ownership changes on Monday, but Riverbend's old payroll account still has to fund Friday's pay run.
What belongs in a transition services agreement?
A transition services agreement covers work a seller performs temporarily after a sale while the buyer establishes its own capability. Each service needs a defined output. Name who provides it, who owns the buyer handoff, what the work costs, and what event ends it.
Payroll can end after the buyer controls the provider and employee data. It also needs bank authority and buyer approval plus an accepted cycle.
On this page 6 sections
Recurring service cost and one-time cutover work
Friday's work has a recurring part. The payroll specialist reviews changes, resolves exceptions, prepares the file, and answers questions. The provider may charge its normal per-run or per-employee fees. Those inputs consume capacity every time the seller runs payroll for the buyer.
Moving payroll creates different work. Employee data has to be converted, earning and deduction codes mapped, bank authority established, administrators provisioned, and at least one test file checked. That work exists because the buyer is leaving Riverbend's environment. It should not be mistaken for another ordinary pay cycle.
Late buyer setup creates a staffing problem. The J&J-Kenvue filing addresses extension notice and charges, termination mechanics, and an outside deadline. 1 It is a complex public-company separation, not a rate card or calendar for Riverbend. More time can affect both capacity and cost.
A service payment and the sale price also answer different questions. The enterprise-value and equity-value guide explains the purchase-price bridge. Riverbend's payroll discussion stays with the people, provider charges, migration work, and extra capacity involved in delivering the temporary operation.
If the buyer already controls its payroll provider and employee records, holds bank authority, and has trained staff on Monday, payroll may need no post-close service at all. A TSA is a response to a dependency, not a ritual that every deal must include.
Payroll, hosted email, and ERP archive end conditions
Riverbend's draft support list also says accounts payable, hosted email, and historical ERP access. Those labels begin at the same closing and then split apart.
Payroll depends on provider setup and employee data. It also needs buyer approvals and bank authority. Accounts payable depends on a buyer-controlled vendor master and approval queue, followed by opening balances and payment controls. Hosted email moves through tenant administration and tested mailboxes. Historical ERP access ends after the buyer restores the agreed archive and removes the temporary accounts.
Filed transition agreements do not converge on one operating pattern. GE and GE Vernova place managers and steering beside service limits and migration. Other filings address changes in scope and third-party providers. 245 These are negotiated records, not evidence that Riverbend should copy their language or dates.
The fictional Riverbend comparison below gives each service a buyer owner, a cost or dependency, and an observable end condition. Payroll ends after an accepted buyer-run cycle, while payables ends after a reconciled payment run. Email ends after users test the move and seller administrator rights disappear. ERP history ends only after the buyer restores and accepts the archive.
The broader owner-transition desk covers work outside these company services, including what happens to your own role. A shared closing date does not finish any of those jobs.
Service-by-service exit tests
Scroll for all columns| Temporary service | Buyer control needed | Cost or outside dependency | End condition |
|---|---|---|---|
| Payroll | The buyer controls provider setup and employee data and holds approval and bank authority | The seller incurs payroll staff time and provider charges plus one-time data conversion | Buyer runs and reconciles an accepted payroll cycle, then seller credentials are removed |
| Accounts payable | The buyer controls the vendor master and approval queue with opening balances and payment authority | The seller incurs finance time while bank setup and vendor-data transfer move to the buyer | Buyer completes and reconciles a payment run using its own approval and bank controls |
| Hosted email | The buyer administers the tenant and user accounts after the mailboxes have migrated | License rights govern the migration work and the testing available to each user | Users accept the move, then seller administrator roles and shared credentials are removed |
| Historical ERP access | The buyer restores the agreed archive inside an environment under its own control | Export work depends on license permission and buyer storage during temporary account access | Buyer accepts the restored archive, after which temporary seller-controlled access is disabled |
Licenses, accounts, and consents that keep a service open
Suppose Riverbend delivers the ERP archive on time. Once restored, it contains the old invoices, yet the database still authenticates through a seller-controlled account. The data move is complete, while the access move remains open.
The same gap appears when a software license restricts eligible users or entities, a vendor contract limits subcontracted work, or a bank will not accept the buyer's approval path. The people doing the task cannot grant a right that the seller does not have. A clean operating test therefore includes the account or permission behind the task.
One 2025 filed agreement addresses third-party services and service-specific periods. 5 It does not decide whether Riverbend can extend access under a particular license. The vendor and the transaction documents answer that question.
Connected documents matter for the same reason. In a 2022 federal court order, allegations involving support services and a TSA appeared beside a warranty deposit, licenses, a noncompete covenant, and an asset purchase agreement. 6 The order is a case-specific procedural record under Georgia law. It shows that the labels can interact and supplies no interpretation for another seller.
Riverbend's operating notes should identify the license, account, consent, payment provision, or individual duty that changes a service. Counsel can then review the connected deal terms against the actual documents instead of trying to recover the dependency from a vague promise after closing.
The first buyer-run payroll is the end condition
Riverbend cannot stop after sending one final seller-run file. That would prove only that the old process still works.
Provider setup comes first, followed by Riverbend's transfer of the employee population and current pay data. Deductions and bank instructions move with them. Buyer administrators receive their own credentials before they approve a test file, resolve differences, and run live payroll. Finance then reconciles the funded amount and employee results.
Now the work has crossed the line that matters. Buyer ownership of the process is proven by an accepted cycle that pays employees without Riverbend's payroll account. Seller administrators can be removed, shared credentials can be retired, and retained files can follow the agreed handling rules.
A failed test or missing bank approval may leave payroll open even if the scheduled date has arrived. Any extension, notice, charge, or outside deadline belongs to the negotiated documents, and the filed examples show variation rather than a market standard. 135
For this fictional service, the finish is exact: the buyer has run and reconciled payroll in its own environment, and no Riverbend credential can release the next payment.
Filed transition agreements and one connected court record6 sources
- U.S. Securities and Exchange Commission EDGAR — Johnson & Johnson and Kenvue Form of Transition Services Agreement
Service periods, exit plans, coordinators, extension notices, surcharges, early termination mechanics, and outside service-period deadlines in one public agreement. Limit: One complex separation agreement. Its negotiated terms do not establish suitable terms, duration, or pricing for another transaction. Accessed 2026-07-26.
- U.S. Securities and Exchange Commission EDGAR — General Electric Company and GE Vernova Inc. Transition Services Agreement
Agreement structure covering services, duration, managers, steering, limitations, and migration. Limit: One large public-company separation. It is not a small-company template or benchmark. Accessed 2026-07-26.
- U.S. Securities and Exchange Commission EDGAR — AMPAC-ISP transition services agreement and form of service schedule
Service-schedule fields for function, dates, sites, description, standards, fees, managers, cost drivers, adjustment mechanics, and software. Limit: One 2012 transaction record. Its provisions do not establish current or suitable contract terms for another deal. Accessed 2026-07-26.
- U.S. Securities and Exchange Commission EDGAR — Avery Dennison and 3M Form of Transition Services Agreement
Bidirectional service structure, exhibit priority, and treatment of a missing transition service in one filed agreement. Limit: One negotiated public-company transaction. It does not decide obligations in another sale. Accessed 2026-07-26.
- U.S. Securities and Exchange Commission EDGAR — Transition Services Agreement filed as Exhibit 10.1
Service-by-service time periods, historical-performance concepts, scheduled scope, and third-party service treatment. Limit: One filed agreement. It does not supply standard duration, service level, price, or liability terms. Accessed 2026-07-26.
- United States District Court for the Middle District of Georgia — American Southern Homes Holdings LLC v. Erickson Document 129
A motion-to-dismiss record discussing allegations spanning a warranty deposit, licenses, support services, a noncompete covenant, a TSA, and an asset purchase agreement. Limit: One 2022 procedural order applying Georgia law. It does not interpret another agreement. Accessed 2026-07-26.
Read the editorial standards or report a correction.