Transition services agreement

Editorial approval scope: The team checked current source fidelity, scope boundaries, dates, arithmetic, reader usefulness, practical workflow, and general-information limitations.

A TSA bridges a defined operating gap

A buyer may own the practice on closing day while still relying on the seller’s payroll platform, billing team, phone system, email domain, EHR administration, purchasing account, or facilities support. A TSA gives those dependencies a controlled life while the buyer builds or migrates replacements.

The agreement should sit beside the purchase agreement, closing checklist, integration plan, payer transition plan, and privacy documents. Each has a different job. The TSA supplies services; it does not transfer ownership, licensure, clinical authority, payer participation, or an authorization.

The SBA M&A guide emphasizes that transaction agreements should address access, operations, assets, liabilities, and ownership-transfer terms. It is general business guidance rather than healthcare contract language.

Define every service as an operating unit

Use a schedule with one row per service. A useful row includes:

• provider and recipient legal entities
• named service owner and receiving owner
• included work, excluded work, locations, and hours
• systems, records, vendors, and required credentials
• service level, evidence, incident route, and escalation time
• fee basis, invoice detail, taxes, pass-through costs, and dispute path
• dependencies, migration milestone, earliest exit, and final end date
• return, transfer, retention, and destruction requirements

“Billing support for six months” leaves too much unresolved. A stronger row names payer queues, claim stages, correction authority, bank and remittance access, reports, response times, staffing assumptions, and the evidence required before the buyer accepts the replacement process.

Preserve clinical and payer decision rights

Seller staff may keep a workflow running without gaining authority to change goals, dosage, risk controls, signatures, supervision, or clinical documentation. Qualified clinicians remain responsible for case decisions within their credentials, competence, state authority, and assigned role.

Treat enrollment, contract, roster, authorization, claim submission, adjudication, and payment as separate payer states. A TSA can assign administrative work, yet the payer or program controls its own records and effective dates. Record which entity is the billing provider, rendering provider, data owner, bank recipient, and correction owner for each service date.

The OIG General Compliance Program Guidance offers voluntary, nonbinding healthcare compliance principles. A transaction team can use it to keep reporting, auditing, training, and issue escalation active through the handoff.

Control PHI, credentials, and vendor access

Map who creates, receives, maintains, or transmits protected health information. If the relationship makes a party a HIPAA business associate or subcontractor, use the required agreement and safeguards before access begins.

The HHS sample business associate provisions address permitted uses, safeguards, incident reporting, subcontractors, and termination handling. A TSA can incorporate or sit beside those terms, but a service label cannot settle HIPAA status by itself.

Use role-based accounts. Keep an access register with user, system, role, approving owner, start, expiry, last review, and removal evidence. Shared seller credentials make audit trails and departure control unreliable.

Price work and change requests clearly

Fees may be fixed, usage-based, cost-plus, or tied to an agreed staffing model. Define units, minimums, caps, pass-through costs, taxes, invoice evidence, and late-payment rules. State how a change in scope becomes approved work.

An apparently inexpensive TSA can become costly when the buyer lacks an exit owner or when seller knowledge remains undocumented. Price transition effort separately from steady service. Require deliverables such as configuration exports, runbooks, vendor introductions, reconciliations, and training evidence.

A fictional eight-service transition

Summit ABA enters closing with eight TSA services. By the first acceptance date, six have a receiving owner, tested replacement, reconciled data, completed access transfer, and signed acceptance. Payroll lacks a tested bank-file route, and EHR administration lacks a complete role map.

Accepted-service readiness is 6 of 8, or 75%. The two gaps remain in the denominator. Summit extends only the affected rows through a written change, sets new tests, and preserves the original end dates for the other six services.

The team also reports incidents, late service levels, open data transfers, disputed charges, and days to exit by service. A single blended percentage would hide a payroll or clinical-record risk.

Exit through evidence

Define acceptance before work starts. Evidence may include parallel runs, reconciled totals, access tests, restored backups, payer acknowledgments, complete runbooks, receiving-team demonstrations, and resolved exceptions.

At exit, remove access, recover property, return or destroy data as required, settle invoices, transfer open issues, notify affected parties, and record residual duties. Keep survival terms for confidentiality, records, audit, indemnity, and unresolved disputes where counsel advises.

The SBA growth guide provides broad context for expanding a business. It supplies no TSA safe harbor, so the parties still need transaction-specific drafting and operational proof.