← All guides

How to Manage a Treasury System Migration

Manage a treasury management system (TMS) migration with a structured project plan covering selection, integration, parallel processing, and cutover.

How to Manage a Treasury System Migration

Treasury System Migrations Fail at Integration, Not Configuration

The core TMS configuration — entities, bank accounts, counterparties, deal types — is rarely where implementations go wrong. It's achievable in 6–8 weeks with vendor support. The problem is almost always bank connectivity.

Getting bank statements to flow in automatically and payment instructions to flow out reliably requires coordination between your TMS vendor, your banks, and often SWIFT or a middleware provider. Each bank has different connectivity requirements. Some support APIs; others are still on SWIFT MT messaging or proprietary file formats. A bank that says "we support that" in the sales call can take 3 months to actually complete testing.

Plan your TMS migration with bank connectivity as the long-lead item, not an afterthought. Here's the full project structure.

Phase 1: Requirements and Vendor Selection (Months 1–2)

Start by documenting what treasury actually does today — not what it ideally does.

Current state documentation:

  • How do you achieve daily cash visibility? Manual bank statement download? Existing connectivity?
  • What payment types do you process? ACH, wire, SWIFT, checks, FX settlements?
  • Do you have debt, investment portfolios, or FX positions to track?
  • How many bank accounts, in how many currencies, at how many banks?
  • How does treasury currently post to the GL? Manual journal entries? ERP integration?

Requirements by module:

  • Cash management: daily position, bank statement reconciliation, cash pooling
  • Payments: payment initiation, approval workflow, dual control, fraud prevention
  • Risk management: FX exposure, hedge accounting if applicable
  • Debt management: loan tracking, covenant monitoring, interest calculations
  • Reporting: cash position dashboard, bank account inventory, cash flow forecast

Vendor evaluation:

  • TMS vendors by company size: Kyriba, ION Treasury, FIS Quantum, GTreasury, Coupa Treasury, Bottomline
  • Evaluate bank connectivity coverage: does the vendor have established connections to your key banks?
  • Evaluate ERP integration: does a pre-built connector exist for your ERP, or is it custom?
  • Reference checks: specifically ask references about bank connectivity timelines

Phase 2: Project Setup and Architecture (Month 3)

Establish governance before any configuration begins.

Project team structure:

  • Treasury lead: functional owner, subject matter expert
  • IT lead: manages technical integrations and infrastructure
  • Bank connectivity lead: dedicated resource to manage bank onboarding (this role is often underserved)
  • Finance lead: GL integration and accounting treatment
  • Vendor implementation manager

Architecture decisions to make in this phase:

  • SWIFT connectivity: direct SWIFT membership, SWIFT Service Bureau, or bank API?
  • Bank statement format: MT940 (SWIFT), BAI2 (US banks), camt.053 (ISO 20022)?
  • Payment file format: MT101, NACHA, proprietary bank format?
  • ERP integration: real-time vs. batch, which data flows in which direction?

Set the go-live date and work backward. A typical TMS implementation is 6–9 months. Bank connectivity is often the critical path.

Phase 3: System Configuration (Months 3–5)

Configuration runs parallel to bank connectivity work. Don't wait for banks to finish before configuring.

Tasks:

  • Bank account master data: all accounts, currencies, bank codes, account numbers
  • Entity and company structure: legal entities, reporting hierarchies
  • Counterparty setup: banks, broker-dealers, investment counterparties
  • Cash pooling structures: notional pooling or zero-balance sweeping arrangements
  • Deal capture workflows: FX, money market, debt draw/repayment
  • Payment approval workflows: dollar thresholds, dual authorization requirements
  • Investment portfolio setup if applicable

Phase 4: Bank Connectivity (Months 4–6)

This is the critical path. Start early and apply consistent pressure.

For each bank:

  1. Submit bank connectivity request form (each bank has its own process)
  2. Execute bank agreement for data sharing and payment initiation
  3. Configure bank statement delivery: schedule, format, delivery method
  4. Test statement delivery in test environment: receive, parse, confirm balances match
  5. Configure payment channel: test payment file delivery and receipt acknowledgment
  6. Confirm fraud controls: IP whitelisting, dual authorization, positive pay

Realistic timelines by bank type:

  • Large US banks (JPMorgan, Bank of America, Wells Fargo): 8–12 weeks from request to production
  • Regional banks: 4–8 weeks
  • International banks: 10–16 weeks
  • Banks requiring SWIFT: add 4–8 weeks for SWIFT onboarding if new

Track each bank as its own workstream with weekly status updates. Banks are notorious for going quiet on implementation requests.

Phase 5: ERP Integration (Months 4–7)

Treasury transactions must flow to the GL. Map the data flows precisely.

Data flows to configure:

  • Bank statement → TMS → GL: cash balances, interest income, bank charges
  • Deal booking → TMS → GL: FX gains/losses, interest expense, investment income
  • Payment initiation → TMS → ERP: payment posting, invoice clearing
  • Cash position → TMS → forecasting model

Test each data flow with actual transactions before go-live. A payment that processes correctly in TMS but fails to clear the AP invoice in ERP creates a reconciliation problem.

Phase 6: Testing and Parallel Run (Months 7–8)

Run both the old process and the new system simultaneously.

Tasks:

  • UAT with treasury team: test all daily workflows
  • Parallel processing: run daily cash position in both old and new system
  • Reconcile daily: TMS cash position vs. manual process position vs. actual bank balances
  • Payment testing: initiate test payments in production TMS to confirm delivery
  • Statement reconciliation: confirm all bank statements arriving in TMS, balance to bank statements downloaded manually

Parallel run length: minimum 4 weeks, ideally one full month-end cycle. Don't shorten this phase to hit a go-live date.

Phase 7: Cutover and Go-Live (Month 9)

Cutover weekend:

  • Confirm all bank connections are in production
  • Confirm ERP integrations are live
  • Migrate any open positions (FX deals, outstanding loans) into TMS
  • Confirm opening cash position matches bank balances
  • Decommission manual cash position spreadsheet

Post-go-live:

  • Daily reconciliation of TMS position to bank statements for 30 days
  • Track any bank connectivity failures and resolve
  • Confirm month-end GL postings are accurate

Build your TMS migration timeline in gantt-chart.io with bank connectivity as a swimlane per bank. Having each bank's status visible in the project plan makes it easy to escalate banks that are falling behind and see the dependency between bank readiness and overall go-live.