TSA Exit Acceleration
Carve Ariba out before the next renewal.
Fixed-fee proposal in 48 hours. Senior team on day one. The first conversation is always free.
TSA Ariba procurement separation is the work of moving the Newco off the seller's SAP Ariba environment and onto its own procurement platform, whether that is a fresh Ariba realm, Coupa, Workday Strategic Sourcing, or a leaner alternative. Ariba sits at the centre of the seller's source to pay process and the Newco's TSA exit strategy has to plan for the disentanglement early. A late start exits the procurement workstream after the broader TSA milestone, which is the most common pattern in carve-outs that overrun.
SAP Ariba is rarely a single application. It is a family of products that includes Ariba Buying and Invoicing, Ariba Contracts, Ariba Sourcing, Ariba Supplier Lifecycle and Performance, and connections through the Ariba Network to thousands of supplier accounts. The seller's realm holds master data for suppliers, contracts, catalogs, approval workflows, and historic spend. Each of these has to be either migrated to a Newco platform or excluded from the carve-out scope.
An accurate inventory of the Newco's procurement footprint in the seller's realm is the first deliverable. Suppliers used only by the carved-out business. Contracts assigned to Newco entities. Catalogs that serve Newco buyers. Approval hierarchies that reflect Newco organisational structure. Each is a row in a workstream inventory that drives the migration plan.
The procurement workstream usually runs longer than the broader TSA. The Newco continues consuming Ariba services under the TSA while the destination platform is selected, configured, integrated, and populated. The pattern overlaps with the broader carve-out procurement strategy playbook.
Most contracts on the seller's Ariba realm are signed under seller entities. When the Newco carves out, each contract relevant to the Newco's business needs to be assigned, novated, or replaced. The legal work happens outside Ariba. The Ariba update follows. The system level migration is the smaller part of this workstream. The negotiation with each supplier is the larger part.
Many suppliers will use the change of legal entity as a moment to reopen the commercial terms. Volume rebates, payment terms, and pricing tiers that the seller negotiated may not transfer cleanly. The Newco often loses the most aggressive seller pricing and has to settle at standalone terms. The procurement workstream needs a clear position on which contracts to preserve, which to renegotiate, and which to let lapse.
The pattern overlaps with the broader carve-out vendor contract assignments playbook. The work is sequenced so the highest spend contracts are addressed first and the long tail is handled in waves.
Ariba catalogs are configured per organisation. Hosted catalogs hold pricing and item data inside Ariba. Punchout catalogs redirect users to a supplier site for selection. CIF and OCI integrations carry the experience through to ERP. Each of these has to be rebuilt on the Newco's destination platform if buyer experience is to survive the cutover.
Suppliers will resist rebuilding catalogs they have already built for the seller. The buyer needs to negotiate this with each supplier individually. Top suppliers usually agree, especially where the spend justifies the effort. Long tail suppliers often refuse and the Newco moves to manual purchase orders or supplier portals for those items. The decision is commercial as much as technical.
A category by category review of catalog content during the TSA period catches the items that need rebuild attention before the cutover date. The review is unglamorous and absolutely essential. A cutover without a working catalog returns the Newco's buying process to email and spreadsheets and damages the value creation plan.
Ariba is integrated with the seller's ERP, typically SAP. Purchase requisitions flow from Ariba to SAP for invoicing and accounting. Master data flows from SAP to Ariba for supplier, cost centre, and chart of accounts synchronisation. The Newco's ERP carve-out and Ariba carve-out are linked. The Newco's destination procurement platform needs to integrate with the Newco's destination ERP from Day One of cutover or the data flow is broken.
The sequencing matters. The Newco often migrates ERP first and procurement second, with procurement consuming the new ERP as the system of record. The opposite sequence is also possible and sometimes preferred. The choice should be made in pre-signing based on which migration carries the larger risk and which sequence minimises double work.
The pattern overlaps with the broader TSA SAP separation playbook for environments where Ariba is part of a larger SAP estate.
SAP Ariba licensing is typically based on document volume, supplier count, and module enablement. During the TSA the seller invoices the Newco for the Newco's allocated share. The methodology should be transparent and the buyer should validate the allocation against the Newco's actual document and supplier counts. Buyers that accept the seller's allocation without question often overpay by a meaningful margin.
The Newco's own platform procurement happens during the TSA period. Whether the Newco stays on Ariba in a new realm, moves to Coupa, or moves to a different platform, the decision should be made within ninety days of close. The implementation timeline for a new procurement platform is typically nine to fourteen months. Starting late forces extension fees on the Ariba TSA invoice.
When the cutover completes the seller's invoice should drop to zero on the procurement line. A residual on a long contract tail does happen and should be documented under a short post-close services agreement. The pattern overlaps with the broader TSA invoice validation process playbook.
A clean Ariba exit closes three records. The seller's realm retains no active Newco suppliers, no active Newco contracts, and no active Newco buyer accounts. The Newco's destination platform holds the full record under its own master data. The Ariba Network supplier relationships have been transferred to the Newco's new buyer ID or replaced under the new platform.
The exit is documented in a cutover report. Every supplier and every contract appears with its disposition. The report supports the broader TSA exit certificate and feeds into the Newco's audit trail for procurement controls. Open items are tracked under the post-close services agreement and closed on schedule.
Specialist support across the procurement workstream is part of the TSA Exit Acceleration service when the milestone is at risk. The work coordinates with the buyer's procurement lead, the seller's Ariba administrators, and the implementation team on the destination platform.
How buyers move suppliers, contracts, and catalogs out of a Coupa environment.
Read the article →How buyers carve out SAP ERP, master data, and adjacent modules at exit.
Read the article →How buyers stand up a procurement function in a Newco from Day One.
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 proposal 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.
Start vendor consents on Day One. Third-party assignment is the long pole, and the systems rebuild is the easy part by comparison.
One tactic, one benchmark, or one pattern from a recent buyer-side engagement. Short. Signal heavy. Free.
Subscribe to The Day One Letter →