TSA Exit Acceleration
Off the seller’s Kyriba instance. With payments controlled.
Fixed-fee proposal in 48 hours. Senior team on day one. The first conversation is always free.
Kyriba TSA separation is the work of standing up a Newco instance, rebuilding bank connectivity, reconstructing the payment factory and cash positioning, and integrating Newco's ERP before the seller's instance still touches Newco's bank accounts and payments. The work sits inside the broader carve-out advisory program and is paced by bank connectivity and payment controls, because Kyriba is the system that initiates real money movement.
Kyriba separation starts with an inventory of the seller instance. The buyer needs the module scope across cash management, payments, bank connectivity, bank fee analysis, and any in house banking or supply chain finance, the bank account structure and the connectivity method whether host to host, SWIFT, or regional protocols, the payment formats and approval workflows, the ERP integration that feeds payments and receives statements, and the fraud and sanctions screening configuration.
The clean end state is a dedicated Newco instance with its own bank connectivity, its own payment factory, and its own ERP integration. A shared seller instance keeps Newco's bank accounts, payments, and cash data under seller administration and seller visibility, which is unacceptable beyond a short bridge. Kyriba initiates real money movement, so the separation carries direct financial and control risk that the firewall and email cases do not.
Target strategy is paced by bank connectivity. Establishing host to host links and SWIFT connectivity for Newco's bank accounts takes weeks to months with each bank, so that work starts as early as the bank account separation allows. The payment factory and cash positioning follow once connectivity is in place, and the ERP integration is sequenced with the finance system separation.
A clean inventory and a settled treasury design drive the downstream sequence: the bank connectivity rebuild, the payment factory reconstruction, the cash and reporting setup, and the ERP integration. The pattern aligns with the broader carve-out treasury plan and the banking separation, because Newco's bank accounts are the foundation the whole instance sits on.
Kyriba is sold as a subscription by module and by scale measures such as the number of bank accounts, payment volume, and connected entities. The seller agreement does not transfer in a carve-out. Newco signs a direct subscription sized to its real account count, payment volume, and the modules it needs, rather than inheriting a contract built for the combined organization's treasury.
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 scoping the modules to Newco's real treasury operation. Where Newco's treasury is simpler than the seller's, the subscription is sized to what Newco actually operates rather than the seller's full module set.
Where the seller provides treasury processing through a TSA window, the pricing is cost-plus or fixed-fee with a defined exit ramp, and the TSA states how Newco accounts and payments are metered. This is among the most sensitive TSA services because it touches payment initiation and bank access, so the controls, the segregation of duties, and the exit are defined precisely rather than left loose.
Where a partner is engaged for the implementation, 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 treasury spend at exit.
Bank connectivity is the foundation and the long pole. Kyriba connects to banks through host to host links, SWIFT, and regional protocols to send payments and receive statements, and in a carve-out Newco's bank accounts are new or newly separated, so the connectivity is built from the ground up. Each bank relationship requires its own setup, testing, and certification, which takes weeks to months and runs in parallel across banks.
Statement retrieval is established so Newco receives prior day and intraday statements for its accounts into the Newco instance. Without statements, cash positioning and reconciliation do not work, so statement connectivity is confirmed early and tested against each account before the instance is relied upon for cash visibility.
Payment connectivity is established and tested with penny tests or controlled low value payments to each bank so that payment files are accepted and processed correctly. The payment formats are configured per bank and per payment type, because each bank and country has its own format and validation rules that must be matched exactly.
Because connectivity depends on Newco's bank accounts existing and being entitled, this workstream is tightly coordinated with the banking separation. An account that is not yet open or not yet entitled for the connectivity channel cannot be connected, so the account opening and the connectivity build are sequenced together.
The payment factory is reconstructed for Newco. Payment templates, the approval workflows with their segregation of duties, the payment limits, and the routing of each payment type to the correct bank and format are rebuilt in the Newco instance. Because this is the control layer over real money movement, the approval matrix and the segregation of duties are designed deliberately rather than copied, so that no single person can both create and release a payment.
Fraud and sanctions screening are reconstructed so that payments are screened before release under Newco's policy. Where the seller's instance integrated a screening service, Newco establishes its own so that screening does not reach back across the boundary. This control is confirmed live before the payment factory processes production payments.
Cash positioning and forecasting are set up against Newco's accounts and statement feeds so the treasury team has accurate visibility from Day One. The bank account hierarchy, the cash pools, and any in house banking structure are rebuilt to reflect Newco's structure rather than the seller's combined pools.
Identity integration binds the instance to Newco's directory. Kyriba authenticates and provisions users through single sign on against the identity provider, and the payment approvers and administrators resolve against Newco identity. Given the payment control sensitivity, the user entitlements and the segregation of duties are reviewed carefully so that access matches role, and the cutover is gated on the identity boundary being live.
The ERP integration feeds payment requests into Kyriba and returns payment status and statements for reconciliation. The integration is repointed at Newco's ERP so that, after cutover, payment requests originate from Newco's finance system and reconciliation posts to Newco's ledger. This is sequenced with the ERP separation so the accounts, the payment data, and the reconciliation align.
Cutover brings Newco's treasury live on its own instance. The runbook covers the bank connectivity activation, the payment factory go live, the screening confirmation, the cash feed validation, the ERP integration switch, the single sign on change, and the validation gate. Because payments move real money, the cutover is rehearsed and the first live payments are watched closely with a controlled run before full volume.
Validation confirms continuity and control. Statements are confirmed to load for every account, a controlled payment is initiated, approved through the segregation of duties, screened, and confirmed received by the bank, and the ERP reconciliation is confirmed to post. The validation is deliberate because an error here is a real financial error, not a configuration inconvenience.
Stabilization runs thirty to sixty days with close attention to the first payment runs and the first reconciliations. Connectivity issues, format rejections, and reconciliation breaks are triaged within agreed service-level commitments. Only after stable, controlled payment operation does the buyer certify treasury for TSA exit. Decommissioning is explicit: the seller removes Newco accounts, payments, and users from its instance and confirms that Newco's bank connectivity and payments no longer route through the seller's Kyriba.
Kyriba separation cost is driven by the module scope, the number of bank connections and their complexity, and the implementation effort across connectivity, the payment factory, and the ERP integration. The discipline is to right size the modules to Newco's real treasury operation and to scope the bank connectivity to the accounts Newco actually uses rather than rebuilding the seller's full structure. A treasury platform scaled for the combined organization is a recurring cost the separation should correct.
The common failure mode is underestimating bank connectivity lead time. Host to host and SWIFT connectivity take weeks to months per bank and depend on the bank accounts being open and entitled, so a separation that starts connectivity late leaves Newco unable to pay or to see its cash at Day One. Buyers that start connectivity in lockstep with the banking separation avoid a treasury gap.
The second failure mode is weakening payment controls in the rush. A payment factory stood up without proper segregation of duties, screening, or tested approval workflows exposes Newco to payment error and fraud the moment it goes live. The fix is to design the control layer deliberately and to validate it with controlled payments before full volume. A PMO maintains the dependency map across Kyriba, the banks, the ERP, treasury, and identity, escalating blocks inside forty eight hours.
A clean Kyriba separation produces a Newco that owns its own treasury instance, its own bank connectivity and payment controls, and its own cash visibility, able to pay and see its cash from Day One under proper control. 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 instance with its own bank connectivity, payment factory, and ERP integration. A shared seller instance keeps Newco's bank accounts, payments, and cash data under seller administration, which is unacceptable beyond a short bridge given that Kyriba initiates real money movement.
Kyriba connects to banks through host to host and SWIFT links that take weeks to months per bank to set up, test, and certify, and they depend on Newco's bank accounts being open and entitled. So connectivity is started as early as the banking separation allows and runs in parallel across banks.
The payment factory is rebuilt with a deliberate approval matrix and segregation of duties so no single person can create and release a payment, and fraud and sanctions screening are confirmed live before production payments. Controls are designed rather than copied, and validated with controlled payments before full volume.
Because bank connectivity, the payment factory, and the ERP integration all have to be built and tested with controls, a Kyriba separation usually runs three to six months, paced by the bank connectivity setup and the banking separation it depends on.
Bank account separation, connectivity, and the cash management cutover.
Read the article →The treasury workstream and how the platform fits the Day One plan.
Read the article →Opening and entitling the accounts that treasury connectivity depends 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.
Sequence to the first standalone close. The ledger, the bank and intercompany all have to land before month-end, or the TSA extends by default.
One tactic, one benchmark, or one pattern from a recent buyer-side engagement. Short. Signal heavy. Free.
Subscribe to The Day One Letter →