Study guide
13.5 Implementing Treasury Products & Services: Bank Onboarding, TMS Deployment & Cutover
Certified Treasury Professional CTP
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Introduction & Corporate Treasury Fundamentals
1.1 CTP Credential, Exam Format & Testing Strategy 1.2 The Role of Corporate Treasury, Organization & Governance 1.3 Financial Statement Analysis, Working Capital & Cash Conversion Cycle
2 Chapter 2: Cash Positioning & Cash Flow Forecasting
2.1 Daily Cash Positioning & Short-Term Liquidity Balancing 2.2 Short-Term Cash Flow Forecasting Methodologies (Direct vs Indirect) 2.3 Medium- and Long-Term Forecasting & Scenario Modeling 2.4 Forecast Variance Analysis, Distribution Tracking & Error Metrics 2.5 Cash Balance Review, Bank Reconciliation & Transaction Verification
3 Chapter 3: Short-Term Investing & Borrowing
3.1 Short-Term Money Market Instruments & Investment Policy Guidelines 3.2 Money Market Yield Calculations, Compounding & Valuation 3.3 Short-Term Borrowing Facilities: Commercial Paper, Credit Lines & Factoring 3.4 Borrowing Cost Calculations, Commitment Fees & Debt Covenants 3.5 Investment Portfolio Construction, Laddering & Duration Management
4 Chapter 4: Cash Concentration & Global Banking Structures
4.1 Cash Concentration Systems, ZBAs & Target Balancing 4.2 Notional Pooling, Physical Sweeping & Cross-Border Liquidity 4.3 Multi-Bank Architecture & Global Account Hierarchy Design 4.4 Intercompany Loans, In-House Banking & Multilateral Netting
5 Chapter 5: Payment Systems, Collections & Disbursements
5.1 Payment Clearing Rails: Fedwire, CHIPS, ACH & Real-Time Payments 5.2 Collections Optimization: Lockbox Systems, Remote Deposit & Merchant Processing 5.3 Disbursement Management: Controlled Disbursement, Positive Pay & Virtual Cards 5.4 Cross-Border Settlement, SWIFT Messaging & ISO 20022 XML Standards
6 Chapter 6: Trade Finance & Financial Supply Chain
6.1 Letters of Credit (Commercial vs Standby) & Bank Guarantees 6.2 Documentary Collections, Open Account & Incoterms 2020 Rules 6.3 Supply Chain Financing, Reverse Factoring & Dynamic Discounting
7 Chapter 7: Capital Structure, Cost of Capital & Valuation
7.1 Capital Structure Theory, Modigliani-Miller & Optimal Leverage 7.2 Weighted Average Cost of Capital (WACC), CAPM & Hurdle Rates 7.3 Long-Term Capital Budgeting: NPV, IRR, Payback & Profitability Index 7.4 Dividend Policies, Share Repurchases & Capital Allocation Strategy
8 Chapter 8: Long-Term Debt & Equity Financing
8.1 Long-Term Debt: Corporate Bonds, Debentures, Private Placements & Covenants 8.2 Syndicated Loan Facilities: Term Loans, Revolvers & Arranger Roles 8.3 Bond Valuation, Duration, Convexity, Yield Curves & Rating Agencies 8.4 Equity Financing, IPOs, Follow-On Offerings & M&A Treasury Due Diligence
9 Chapter 9: Treasury Relationship Management & Banking Administration
9.1 Financial Service Provider Selection, RFPs & Scorecards 9.2 Bank Account Analysis Statements, Earnings Credit Rates (ECR) & Pricing 9.3 Bank Account Administration, FBAR Compliance & Delegations of Authority 9.4 Treasury as Internal Trusted Advisor, Consultant & Project Finance Partner 9.5 Internal Stakeholder Partnership: Accounting, FP&A, Tax, Legal, Audit, IT & Investor Relations
10 Chapter 10: Enterprise Financial Risk Management & Controls
10.1 Treasury Policy Manuals, Internal Controls & Segregation of Duties 10.2 Counterparty Credit Risk Assessment, Scoring & Exposure Limits 10.3 Regulatory Frameworks: SOX 404, Dodd-Frank, Basel III & AML/KYC 10.4 Business Continuity Planning (BCP), Disaster Recovery & Treasury Resilience
11 Chapter 11: Market Risk & Derivatives Hedging
11.1 FX Risk Types: Transaction, Translation & Economic Exposure 11.2 FX Hedging: Spot, Forwards, Futures, Options & Non-Deliverable Forwards 11.3 Interest Rate Risk: Swaps, Caps, Floors, Collars & SOFR Transition 11.4 Commodity Price Hedging & Hedge Accounting (ASC 815 / IFRS 9)
12 Chapter 12: Fraud Prevention, Information Security & Compliance
12.1 Treasury Fraud Vectors: Check Fraud, Business Email Compromise & ACH Tampering 12.2 Defense-in-Depth: Positive Pay, Dual Approvals, Out-of-Band Callbacks & Tokens 12.3 Merchant Services Security, PCI DSS Standards & Identity Access Governance
13 Chapter 13: Treasury Management Systems & Emerging Technologies
13.1 Treasury Management Systems (TMS) Architecture & Core Modules 13.2 ERP Integration, Application Programming Interfaces (APIs) & H2H Connectivity 13.3 Bank Connectivity: SWIFT gpi, ISO 20022 XML Messaging & EBICS 13.4 Artificial Intelligence, Robotic Process Automation & Future Treasury Trends 13.5 Implementing Treasury Products & Services: Bank Onboarding, TMS Deployment & Cutover
13.5 Implementing Treasury Products & Services: Bank Onboarding, TMS Deployment & Cutover
Key Takeaways Explain This Topic AI
Task 5.D carries 2 to 4 scored questions and separates implementation from selection: KYC/AML documentation and account opening routinely take 8 to 14 weeks for a multinational and run on the bank's clock, so onboarding must start first even though it runs parallel to build.
The penny test — sending a nominal-value real transaction to prove routing and beneficiary details before material value moves — is the highest-value control in a payment implementation and should be repeated for every new beneficiary bank.
Exception-path testing of rejected payments, duplicate files, failed connections and over-limit approvals is the step teams skip; a system tested only on the happy path is untested.
Payment-critical implementations warrant a parallel run of at least one full business cycle followed by a phased cutover, and cutover must never be scheduled into month-end, quarter-end or year-end close.
Decommissioning is a distinct workstream: close superseded accounts and remove signers, revoke certificates, archive legacy data, and cancel the legacy services that would otherwise keep billing indefinitely.
Last updated: August 2026
13.5 Implementing Treasury Products & Services: Bank Onboarding, TMS Deployment & Cutover
Executive Summary: Selecting a product and implementing it are separate competencies, and the 2026–2028 blueprint separates them. Task 5.D — "Implement treasury products and services (including banking products, treasury workstations)" — carries 2–4 scored questions. It is the task that turns the RFP of §9.1 and the TMS architecture of §13.1 into working infrastructure, and it is where most treasury technology value is actually won or lost.
1. The Implementation Lifecycle
Every treasury implementation — a new lockbox, a new pooling structure, a full TMS — follows the same eight stages:
- Stage Purpose Principal Deliverable
- 1. Requirements & selection Define what the product must do (§9.1 RFP process) Scored provider selection
- 2. Contracting Commercial and legal terms, SLAs, security schedules Executed agreement + SLA schedule
- 3. Planning Scope, timeline, resourcing, governance Project charter, RACI, critical-path plan
4. Documentation & onboarding KYC/AML, account opening, mandates, authority Account numbers, signer mandates, connectivity credentials
5. Build & configure Interfaces, file formats, workflow, entitlements Configured environment; format specifications signed off
- 6. Test Prove every path works, including the failure paths Signed UAT results, penny-test evidence
- 7. Cutover Move production volume to the new service Go/no-go decision and executed cutover plan
8. Hypercare & benefits realization Stabilize, then verify the business case Issue log closed; measured benefits against the case
Warning
Stage 4 is the stage that destroys timelines. KYC/AML documentation and account opening routinely take 8–14 weeks for a multinational, longer where beneficial-ownership documentation must be gathered across jurisdictions. It runs on the bank's clock, not yours, and no amount of project pressure compresses it materially. Start it first.
- 2. Bank Product Implementation
- Documentation and Onboarding
Before a single file moves, the bank requires: entity formation documents, beneficial ownership certification under the FinCEN CDD rule, board resolutions or delegations of authority, signer mandates and specimen signatures, tax forms (W-9/W-8 series), and — for cross-border structures — local regulatory filings.
Technical Enablement
Item What Must Be Agreed
File formats ISO 20022 pain.001 payment initiation, camt.053 prior-day statement, camt.052 intraday, plus any legacy NACHA or BAI2 formats retained
- Connectivity Host-to-host SFTP, API, SWIFT, or EBICS — including certificate exchange and IP allow-listing
- Security Encryption standard, key exchange, digital signature requirements, dual-control release
- Reference data Account structures, BAI transaction-type code mapping, cost-center and entity codes
- Cutoff times Per rail, per currency — the operational constraint most often discovered after go-live
- The Testing Ladder
Testing is not one activity. A CTP is expected to know the sequence:
Connectivity test — can the systems establish an authenticated session at all?
Format validation — does the bank's parser accept the file structurally? Run with a zero-value or test-flagged file.
Penny test (zero-dollar or nominal-value test) — send a real transaction of $0.01 to each beneficiary account to prove routing and account details before any material value moves. This is the single most valuable control in a payment implementation , and it should be repeated for every new beneficiary bank, not just once per project.
Integration test — end to end from ERP through TMS through bank and back into reconciliation.
User acceptance testing (UAT) — the business, not IT, confirms the process works for real scenarios.
Exception-path testing — the step teams skip. Test a rejected payment, a duplicate file, a failed connection, a partial statement, and a payment above an approval limit. A system that has only been tested on the happy path is untested.
Security and disaster recovery testing — penetration testing where contractually available, and a failover rehearsal.
3. TMS Implementation Specifics
Beyond the bank layer, a treasury workstation implementation adds:
Data migration. Existing debt schedules, investment positions, hedge relationships, entity hierarchies, and bank account inventory must be cleansed before loading. Data cleansing is consistently the most underestimated task in the plan — legacy spreadsheets contain duplicate accounts, closed accounts still listed as open, and signers who left the company.
Interface build. ERP to TMS (accounting entries, AP/AR data), market-data feeds, bank connectivity, and the GL posting interface back to the ERP.
Configuration versus customization. Configure inside the vendor's supported framework wherever possible. Custom code is the primary driver of failed upgrades — every future release must be regression-tested against it, and a heavily customized SaaS deployment forfeits the upgrade economics that justified SaaS.
Entitlements and segregation of duties. Build the approval matrix in the system so that the maker/checker separation of §12.2 is enforced by software rather than by convention.
Training and documentation. Role-based training plus written procedures. Vendor training covers the software; only internal documentation covers your process.
Cutover Strategy
Approach Description Best For Principal Risk
Big bang All entities and functions move on one date Small scope; strong hard deadline No fallback; a failure is a full outage
Phased By entity, region, or module Large multinationals Prolonged dual-running cost and complexity
Parallel run Old and new operate simultaneously; results compared High-risk payment and reconciliation processes Double the workload during the overlap
Best practice for payment-critical implementations is a parallel run of at least one full business cycle — commonly one month, so that a month-end and a full reconciliation cycle are both exercised — followed by a phased cutover.
Warning
Never schedule a cutover into month-end, quarter-end, or year-end close. Treasury and accounting resources are fully consumed, error tolerance is at its lowest, and any rollback happens under reporting deadline pressure. The corollary applies to seasonal businesses: a retailer does not cut over in November.
4. Backward-Planning a Critical Path
Scenario — Meridian Group must have a new global payments and TMS platform live on Monday, January 5. Planning backward from that date, with the sequenced minimums:
- Activity Duration Must Start By
- Hypercare (post-go-live) 4 weeks Jan 5
- Go-live — Jan 5
- Parallel run (one full cycle) 4 weeks Dec 8
- User acceptance testing 6 weeks Oct 27
- Integration & exception-path testing 4 weeks Sep 29
- Interface build & configuration 8 weeks Aug 4
- Bank onboarding / KYC / mandates 12 weeks May 12
- Contracting 6 weeks Mar 31
The critical path totals roughly 40 weeks before go-live , and the binding constraint is bank onboarding — which must launch in mid-May for a January go-live . Two structural lessons the exam rewards:
Onboarding runs in parallel with build, but it starts earliest. A team that begins KYC after contracts are signed and interfaces are built has already lost the timeline.
A December go-live for a calendar-year company is the wrong date regardless of readiness. Meridian's January 5 target deliberately clears year-end close.
5. Hypercare, Decommissioning & Benefits Realization
Hypercare — an elevated support period, typically 4–8 weeks — keeps the project team and the vendor engaged after go-live with a defined issue-triage path and daily standups. Releasing the project team on go-live day is a common and expensive error.
Decommissioning is a distinct workstream, not an afterthought:
Close the superseded bank accounts formally, and remove the signers (see §9.3). An account left open with stale mandates is an open fraud channel.
Revoke connectivity credentials and certificates for the retired service.
Archive legacy data to satisfy retention requirements before switching off the old system.
Stop paying for it. Legacy bank services and software licenses that were never cancelled are one of the most reliably recoverable costs in a treasury fee review.
Benefits realization closes the loop against the business case that funded the project:
- Benefit Claimed How It Is Verified
- Bank fee reduction Compare account analysis statements (§9.2) pre- and post-implementation
- Improved cash visibility Percentage of global cash balances reported by 9:00 a.m. local
- Straight-through processing rate Payments requiring no manual intervention ÷ total payments
- Reconciliation efficiency Auto-match rate and days-to-reconcile (§2.5)
- Reduced idle balances Average uninvested overnight balance before versus after
- Ongoing Vendor Assurance
Implementation does not end the diligence obligation. For any hosted service, obtain and read the provider's SOC 1 (financial reporting controls) or SOC 2 (security, availability, confidentiality) report annually, and specifically review the complementary user entity controls — the controls the report assumes you are performing. Those assumptions are frequently untrue at the client, and that gap is a standard audit finding.