TSA Exit Acceleration
Off the seller’s Concur entity. With clean posting.
Fixed-fee proposal in 48 hours. Senior team on day one. The first conversation is always free.
SAP Concur TSA separation is the work of standing up a Newco entity, rebuilding expense policy and audit rules, re establishing corporate card feeds, and repointing the posting into Newco's general ledger before the seller's entity still processes Newco's expenses and payments. The work sits inside the broader carve-out advisory program and is paced by the card feeds and the ERP posting, which take time to establish with the banks and the finance system.
Concur separation starts with an inventory of the seller configuration. The buyer needs the entity structure across Expense, Travel, and Invoice, the user and approver hierarchy, the expense policy and audit rules, the corporate card programs and their feeds, the integration into the general ledger for posting, the tax and value added tax configuration, and the reimbursement method whether through the ERP or a payment provider.
The clean end state is a dedicated Newco entity with its own policy, its own card feeds, its own posting into Newco's general ledger, and its own approver hierarchy. A shared seller entity keeps Newco's expenses, card data, and posting under seller administration and seller visibility, which is unacceptable beyond a short bridge. Concur sits between the cards, the employees, and the ledger, so the separation touches finance operations directly.
Target strategy is paced by the plumbing. The corporate card feeds and the general ledger posting integration take time to establish with the issuing banks and the finance system, so those are started early. The policy and approver configuration follow, and the user population is loaded once the entity structure is set.
A clean inventory and a settled entity design drive the downstream sequence: the policy and audit rule rebuild, the card feed re establishment, the posting cutover, and identity integration. The pattern aligns with the broader carve-out finance plan and the treasury and banking separation, because reimbursement and card settlement depend on Newco's bank accounts.
Concur is sold by transaction volume or by user across Expense, Travel, and Invoice. The seller agreement does not transfer in a carve-out. Newco signs a direct subscription sized to its real user count and transaction volume, rather than inheriting a contract built for the combined organization and its volumes.
A carve-out reads to the vendor as a buyer with a deadline, which is real leverage on the sell side. The buyer offsets that by opening the commercial conversation early and by sizing the subscription to Newco's actual volume. Where Newco's travel and expense footprint is smaller than the seller's, the subscription is right sized rather than carried over at the seller's scale.
Where the seller provides expense processing through a TSA window, the pricing is cost-plus or fixed-fee with a defined exit ramp, and the TSA states how Newco users and transactions are metered. The historical expense data deserves explicit treatment because the seller holds Newco's expense records, and the TSA must define export rights and the access window for audit and tax purposes.
Where a partner is engaged for the configuration rebuild, the contract is fixed fee for defined deliverables with disciplined change control. The subscription audit runs through the broader TSA license consolidation work so Newco right sizes its expense spend at exit.
The expense policy is rebuilt rather than copied wholesale. Spending limits, expense types, per diem and mileage rates, receipt requirements, and the audit rules that flag exceptions are reconstructed in the Newco entity to match Newco's policy. The seller policy is a useful reference, but it carries seller specific limits and approval thresholds that Newco reviews rather than inherits.
The approver hierarchy is reconstructed for Newco's organization. Reporting lines, cost center structure, and the approval routing are rebuilt so that expenses route to the correct Newco approvers rather than the seller's. This depends on the human resources and organizational data being available for Newco, so it is sequenced with the people data separation.
Tax and value added tax configuration is rebuilt for Newco's entities and jurisdictions so that expense capture and reclaim are correct from the first report. Where the seller's configuration assumed the seller's tax registrations, those are replaced with Newco's so the posting and the tax treatment are accurate.
Cost center and general ledger account mapping are reconstructed against Newco's chart of accounts so that expenses post to the right accounts. This mapping is the bridge to the posting integration and is validated against Newco's ledger structure before cutover.
Corporate card feeds are the long pole. Each card program feeds transactions into Concur, and in a carve-out the card programs themselves often move to new accounts or new issuers as part of the banking separation. The feeds are re established from Newco's card programs into the Newco entity, which requires coordination with the issuing banks and lead time that the buyer plans for early so cards and feeds are ready together.
The general ledger posting integration carries approved expenses into the finance system. The posting is repointed at Newco's ERP through the financial extract or the standard integration so that, after cutover, Newco's expenses post to Newco's ledger rather than the seller's. This is sequenced with the ERP separation so the accounts, cost centers, and posting periods align.
Reimbursement is reconfigured to draw on Newco's bank accounts, whether reimbursement runs through the ERP payment process or a payment provider. Because reimbursement moves real money, it is coordinated with the treasury and banking separation so that employees are paid from Newco accounts on the first cycle after cutover.
Identity integration binds the entity to Newco's directory. Concur authenticates and provisions users through single sign on against the identity provider, and the entity is pointed at Newco's identity provider so that user access, the approver hierarchy, and administration resolve against Newco identity. User provisioning and single sign on are gated on the identity boundary being live.
Cutover brings Newco's expense processing live on its own entity. The runbook covers the policy go live, the card feed activation, the posting integration switch, the reimbursement configuration, the single sign on change, and the validation gate. Because expense and posting run on cycles, the cutover is timed to a period boundary where the finance calendar allows it so the books are clean.
Validation confirms continuity. A test expense report is submitted, approved, and posted through to Newco's ledger, the card feed is confirmed to load Newco transactions, reimbursement is confirmed to draw on Newco accounts, the tax treatment is confirmed, and the approver routing is confirmed against Newco's hierarchy. The high volume expense types are validated first so the workforce is not blocked.
Stabilization runs thirty to sixty days. Failed card feeds, posting errors, and approval routing gaps are triaged within agreed service-level commitments. The first full period close is watched closely so that expense posting reconciles to the ledger and any mapping error is corrected before it compounds.
Decommissioning is explicit. Once Newco processes expenses on its own entity with its feeds and posting live, the seller removes Newco users from its entity, stops the card feeds into the seller entity, and confirms that Newco's expense data and posting no longer flow through the seller's Concur, subject to any agreed access window for historical records.
Concur separation cost is driven by the subscription scope, the configuration rebuild effort across policy and posting, and the coordination with the card programs and the ERP. The discipline is to right size the subscription to Newco's real volume and to rebuild only the configuration Newco needs rather than copying the seller's full setup. A subscription and configuration scaled for the combined organization is a recurring cost the separation should correct.
The common failure mode is underestimating the card feed lead time. Card programs and their feeds are tied to the banking separation, and a feed that is not ready at cutover leaves transactions unloaded and employees unable to reconcile their cards. Buyers that start the card and feed work early, in step with treasury, avoid a gap in expense processing.
The second failure mode is the posting and tax configuration. A posting integration repointed without validating the chart of accounts mapping, or a tax configuration left on the seller's registrations, produces a messy first close and incorrect tax treatment. The fix is to validate the mapping and the tax setup against Newco's ledger before cutover. A PMO maintains the dependency map across Concur, the card programs, the ERP, treasury, and identity, escalating blocks inside forty eight hours.
A clean Concur separation produces a Newco that owns its own expense entity, its own card feeds and posting, and its own reimbursement, with expenses flowing cleanly into Newco's ledger from the first period. The discipline runs through the TSA exit acceleration program under a Fixed Fee plus Portfolio Retainer engagement model.
Yes. The clean end state is a dedicated Newco entity with its own policy, card feeds, posting into Newco's ledger, and approver hierarchy. A shared seller entity keeps Newco's expenses, card data, and posting under seller administration and seller visibility, which is unacceptable beyond a short bridge.
Each card program feeds transactions into Concur, and in a carve-out the card programs often move to new accounts or issuers as part of the banking separation. Re establishing the feeds requires coordination with the issuing banks and lead time, so the work starts early so cards and feeds are ready together at cutover.
The general ledger posting integration is repointed at Newco's ERP and the cost center and account mapping is rebuilt against Newco's chart of accounts. The cutover is sequenced with the ERP separation and timed to a period boundary so expenses post cleanly to Newco's ledger from the first cycle.
The entity, policy, and approver configuration can be ready in weeks, but the card feeds and the ERP posting integration usually pace the full separation to two to four months because they depend on the banking and finance system separations.
Bank connectivity, payment factory, cash positioning, and the ERP integration cutover.
Read the article →The ERP separation that expense posting and the chart of accounts depend on.
Read the article →The treasury and banking workstream that card settlement and reimbursement depend on.
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 →