Moving commercial clientsto a new treasury platform.

The stages that move every client intact, from architecture to the last wave's stabilization.

Who owns it

Your technology leaders and your treasury platform provider, with your core and payment providers.

Key projects

• Architecture & integration inventoryThe core, payment hubs, positive pay, remote deposit, reporting, identity, fraud, and every client connection.
• Entitlement & template conversionCompanies, users, accounts, services, limits, approvals, templates and payees.
• Integrations & filesReal-time and batch connections to the core and the payment rails, and every client file format.
• Client connectivityFile transfer and API connections, with new endpoints and credentials, tested with each client.
• Testing & mock conversionsEnd-to-end payment scenarios, and repeated rehearsals of each wave.
• Cutover & stabilizationWave runbooks, the payment switch, and hypercare through each wave's first payroll and month-end.

Led by people who have run treasury conversions before, with one plan for treasury, technology, operations, sales and the vendors, organized around client waves instead of a single date.

Who owns it

Your head of treasury management as sponsor, with technology and operations leaders and a program office.

Key projects

• OversightSponsor, steering committee, decision rights, and who can move a client between waves.
• Integrated technical program planBuild, test, pilot and each wave on one plan, with the technical dependencies between platforms, vendors and teams mapped and aligned, around your clients' busiest days.
• Vendor coordinationThe new platform, the current one's exit, and the payment, positive pay, remote deposit and reporting providers around them.
• Risks, issues & decisionsOne register, reviewed weekly, with anything that touches a client flagged.
• Budget & capacityImplementation specialists, support staff and relationship managers' time, planned wave by wave.
• Go/no-go by waveCriteria for the pilot and each wave, and the evidence each one needs.

The servicing, payment operations, support desk and implementation teams that keep clients' payments running during the waves and after.

Who owns it

Your treasury servicing and operations, payment operations and client support leaders.

Key projects

• Payment operations proceduresACH, wire, real-time and positive pay processing on the new platform, with its cutoffs and exceptions.
• Client support deskStaffing, scripts and hours sized for each wave's first payroll and first month-end.
• Implementation capacitySpecialists for enrollment, entitlement questions and file testing, wave by wave.
• Internal trainingOperations, support, sales and relationship managers trained on the platform clients will see.
• Exception handlingRejected files, held payments and positive pay decisions worked the same day on the new platform.
• Running two platformsBoth platforms side by side until the last wave, with rules for which client is where.

Each service your clients use, mapped to what the new platform does, with a decision for each gap.

Who owns it

Your treasury product managers, pricing and legal teams.

Key projects

• Service mapping & gap analysisACH, wires, real-time payments, positive pay, remote deposit, lockbox, sweeps and reporting, old to new, feature by feature.
• Gap decisionsFor each gap, build it, work around it, retire it, or tell the client.
• Pricing & account analysisService codes, prices and analysis statements carried over, so the first bill matches what clients expect.
• Agreements & service termsTreasury services agreements and service schedules updated where the platform changes the terms.
• Limits & approval policyTransaction and daily limits, dual control and approval rules, set as policy before they become configuration.
• Reporting & filesPrior-day and current-day reporting, statements, and the file formats your clients' systems depend on.

Each client segmented, scheduled, informed, supported and converted, with relationship managers leading the conversation with their clients.

Who owns it

Your treasury sales team, relationship managers and client implementation team.

Key projects

• Segmentation & wave planClients grouped by services, users, file connections and risk, with pilot clients chosen deliberately.
• Relationship manager playbookWhat to say, when, and what each client has to do, before the first letter goes out.
• Client communicationsLetters, guides, webinars and in-app messages, timed to each wave.
• White-glove conversionsYour largest and most complex clients converted with a named specialist.
• Client file testingClients who send files from their own systems test new connections and formats before their wave.
• Enrollment & adoptionUsers re-enrolled, tokens delivered, and the clients who haven't logged in called before payroll day.

Payment controls, fraud defenses and client access as strong on day one as they were the day before.

Who owns it

Your risk, fraud, BSA, information security and compliance teams.

Key projects

• ACH origination riskOriginator limits, risk reviews and agreements carried across, in line with Nacha rules.
• Entitlement & access reviewEach user's rights reviewed as they convert, and access nobody should still have removed.
• Fraud controlsPayment fraud monitoring, out-of-band verification and alerts working on the new platform before the first wave.
• Authentication & tokensMulti-factor authentication and token delivery for every user, without a gap.
• Third-party risk managementDue diligence and oversight of the new provider, and an orderly exit from the old one.
• Audit & evidenceEntitlement reconciliations, payment tests and sign-offs, organized the way auditors read them.