[{"data":1,"prerenderedAt":578},["ShallowReactive",2],{"blog-\u002Fblog\u002Ftreasury-management-system-implementation-guide":3,"blog-surround-\u002Fblog\u002Ftreasury-management-system-implementation-guide":560,"blog-related-\u002Fblog\u002Ftreasury-management-system-implementation-guide":568},{"id":4,"title":5,"audience":6,"body":10,"cluster":526,"date":527,"description":528,"draft":529,"extension":530,"factCheckedAt":531,"faq":532,"featured":529,"language":531,"meta":542,"navigation":241,"order":543,"originalAsset":531,"path":544,"pillar":545,"primaryKeyword":546,"relatedProject":531,"releaseScope":531,"reviewCycle":547,"reviewStatus":548,"reviewedBy":549,"searchIntent":550,"seo":551,"sources":531,"stem":552,"tags":553,"type":558,"updated":527,"__hash__":559},"blog\u002Fblog\u002Ftreasury-management-system-implementation-guide.md","Treasury Management System Implementation Guide",[7,8,9],"treasury-system-lead","programme-manager","group-treasurer",{"type":11,"value":12,"toc":510},"minimark",[13,27,30,35,38,98,101,105,121,127,131,138,143,147,150,155,159,162,173,178,182,189,194,198,209,214,218,229,280,285,289,292,297,301,304,392,395,399,473,477,485,488],[14,15,16,26],"p",{},[17,18,19,20,25],"strong",{},"A TMS implementation ",[21,22,24],"a",{"href":23},"\u002Fblog\u002Ftms-implementation-timeline-and-phases","runs in phases"," — mobilize, design, build, bank connectivity, data migration, testing, cutover and hypercare — usually over several months to more than a year, with bank connectivity and data migration as the real critical paths."," The software configuration is rarely what takes the time. What takes the time is everything around it: onboarding banks, cleaning and migrating data, testing properly, and running it as a treasury change programme rather than an IT install.",[14,28,29],{},"This guide walks the whole thing end to end — the phases, what each one delivers, a realistic timeline, and the team you need — so you can plan a programme that goes live on schedule instead of one that discovers connectivity and data three months in.",[31,32,34],"h2",{"id":33},"the-shape-of-a-tms-implementation","The shape of a TMS implementation",[14,36,37],{},"At a high level, every implementation moves through the same arc, even if the labels differ by vendor and method:",[39,40,41,48,54,60,71,80,86,92],"ol",{},[42,43,44,47],"li",{},[17,45,46],{},"Mobilize & scope"," — team, governance, requirements, plan.",[42,49,50,53],{},[17,51,52],{},"Design"," — target operating model and the configuration decisions.",[42,55,56,59],{},[17,57,58],{},"Build & configure"," — set the system up to the design.",[42,61,62,65,66,70],{},[17,63,64],{},"Bank connectivity"," — statements and payments, live with every bank ",[67,68,69],"em",{},"(runs in parallel from early)",".",[42,72,73,79],{},[17,74,75],{},[21,76,78],{"href":77},"\u002Fblog\u002Ftms-data-migration","Data migration"," — clean and load master and open data.",[42,81,82,85],{},[17,83,84],{},"Testing"," — system integration testing, then user acceptance testing.",[42,87,88,91],{},[17,89,90],{},"Cutover & go-live"," — the controlled switch to the new system.",[42,93,94,97],{},[17,95,96],{},"Hypercare"," — intensive support after go-live.",[14,99,100],{},"The mistake is to run these strictly in sequence. Bank connectivity and data cleaning have long lead times and external dependencies, so they start early and run alongside build — not after it.",[31,102,104],{"id":103},"phase-1-mobilize-scope","Phase 1 — Mobilize & scope",[14,106,107,108,111,112,115,116,120],{},"Stand up the programme before the software. Name a ",[17,109,110],{},"single accountable owner"," for the outcome, embed treasury subject-matter experts (not part-time advisors), and put a technical\u002Fintegration lead and a data owner in place. Confirm scope against a ",[17,113,114],{},"prioritized requirements list"," — see the ",[21,117,119],{"href":118},"\u002Fblog\u002Ftreasury-management-system-requirements-checklist","requirements checklist"," — and agree governance: who decides, how changes are controlled, how risk is surfaced.",[14,122,123,126],{},[17,124,125],{},"Delivers:"," charter, team and RACI, agreed scope, plan, governance.",[31,128,130],{"id":129},"phase-2-design","Phase 2 — Design",[14,132,133,134,137],{},"Design the target operating model, then the configuration to support it. The single most consequential decision here is the ",[17,135,136],{},"system of record"," — which system owns bank master data, payment status, exposures — especially where a TMS coexists with an ERP. Get these boundaries right and the landscape stays clean; get them wrong and you buy years of reconciliation.",[14,139,140,142],{},[17,141,125],{}," target operating model, configuration\u002Fdesign document, integration design, system-of-record map.",[31,144,146],{"id":145},"phase-3-build-configure","Phase 3 — Build & configure",[14,148,149],{},"Configure the system to the design: entities, accounts, workflows, limits, accounting rules, reports. Keep it anchored to the design and the requirements, not to whatever the demo showed or a stakeholder asks for mid-flight — undisciplined scope here is how a system ends up doing many things adequately and your two real needs poorly.",[14,151,152,154],{},[17,153,125],{}," configured system in a build\u002Ftest environment; interface build underway.",[31,156,158],{"id":157},"phase-4-bank-connectivity-the-critical-path","Phase 4 — Bank connectivity (the critical path)",[14,160,161],{},"Start this early and treat it as the critical path it almost always is. For each bank you must agree the channel (SWIFT, host-to-host, EBICS, API), the statement formats (MT940, camt.053, BAI2) and payment formats (pain.001 \u002F ISO 20022, local formats), then test statements in and payments out end to end — including acknowledgements (pain.002).",[163,164,166],"callout",{"type":165},"tip",[14,167,168,169,172],{},"The software is \"live\" in weeks; getting every bank onboarded, formats agreed and flows tested takes far longer and depends on third parties you don't control. If connectivity isn't already running while you configure, it ",[67,170,171],{},"will"," become the thing holding go-live.",[14,174,175,177],{},[17,176,125],{}," each bank connected and tested for statements and payments.",[31,179,181],{"id":180},"phase-5-data-migration","Phase 5 — Data migration",[14,183,184,185,188],{},"Migrate master data (bank accounts, counterparties, cost centres, signatories, payment details) and open items (deals, loans, investments). The rule that saves programmes: ",[17,186,187],{},"clean the data before you migrate it, and give it an owner."," Migrating dirty master data \"to fix later\" is how a wrong-account payment or an unreconcilable position traces back, months on, to a record no one owned.",[14,190,191,193],{},[17,192,125],{}," cleaned, migrated, reconciled data; migration and reconciliation controls.",[31,195,197],{"id":196},"phase-6-testing","Phase 6 — Testing",[14,199,200,201,204,205,208],{},"Test in two passes. ",[17,202,203],{},"System integration testing (SIT)"," proves the system and its interfaces work together — ERP in, bank flows out, accounting back. ",[17,206,207],{},"User acceptance testing (UAT)"," proves it works for the people who'll run it, against real business scenarios: a real month-end, a real payment run, a real forecast. Protect this window; it's the one most often squeezed when earlier phases run long, which just moves the defects into production.",[14,210,211,213],{},[17,212,125],{}," passed SIT and UAT; a defect log worked down to an agreed go\u002Fno-go bar.",[31,215,217],{"id":216},"phase-7-cutover-go-live","Phase 7 — Cutover & go-live",[14,219,220,221,224,225,228],{},"Cutover is the controlled switch from old to new. Plan it as a sequenced runbook — final data loads, connectivity cutover, reconciliation, sign-offs — and rehearse it with at least one ",[17,222,223],{},"dry run",". Gate go-live on an explicit ",[17,226,227],{},"readiness assessment",", not a calendar date.",[230,231,234,244,250,256,262,268,274],"ul",{"className":232},[233],"contains-task-list",[42,235,238,243],{"className":236},[237],"task-list-item",[239,240],"input",{"disabled":241,"type":242},true,"checkbox"," Data migrated and reconciled; balances tie out",[42,245,247,249],{"className":246},[237],[239,248],{"disabled":241,"type":242}," All banks connected and confirmed in production",[42,251,253,255],{"className":252},[237],[239,254],{"disabled":241,"type":242}," UAT passed; open defects within the agreed threshold",[42,257,259,261],{"className":258},[237],[239,260],{"disabled":241,"type":242}," Cutover runbook rehearsed (dry run completed)",[42,263,265,267],{"className":264},[237],[239,266],{"disabled":241,"type":242}," Roll-back plan defined",[42,269,271,273],{"className":270},[237],[239,272],{"disabled":241,"type":242}," Users trained; support model stood up",[42,275,277,279],{"className":276},[237],[239,278],{"disabled":241,"type":242}," Go\u002Fno-go decision taken by the accountable owner",[14,281,282,284],{},[17,283,125],{}," live system; signed-off go-live.",[31,286,288],{"id":287},"phase-8-hypercare","Phase 8 — Hypercare",[14,290,291],{},"For the first weeks after go-live, run intensive support: the project team stays close, issues are triaged fast, and the first real month-end is treated as part of the programme, not \"business as usual.\" Exit hypercare on stability criteria, not a date.",[14,293,294,296],{},[17,295,125],{}," stabilized operation; formal handover to run-and-maintain.",[31,298,300],{"id":299},"a-realistic-timeline","A realistic timeline",[14,302,303],{},"Resist a fixed number — it's driven by scope. What actually moves it:",[305,306,307,323],"table",{},[308,309,310],"thead",{},[311,312,313,317,320],"tr",{},[314,315,316],"th",{},"Driver",[314,318,319],{},"Faster",[314,321,322],{},"Slower",[324,325,326,340,353,366,379],"tbody",{},[311,327,328,334,337],{},[329,330,331],"td",{},[17,332,333],{},"Banks to onboard",[329,335,336],{},"1–2",[329,338,339],{},"Many, across regions",[311,341,342,347,350],{},[329,343,344],{},[17,345,346],{},"Entities & currencies",[329,348,349],{},"Single",[329,351,352],{},"Many, global",[311,354,355,360,363],{},[329,356,357],{},[17,358,359],{},"Scope",[329,361,362],{},"Cash visibility only",[329,364,365],{},"Cash + payments + risk + accounting",[311,367,368,373,376],{},[329,369,370],{},[17,371,372],{},"Data quality",[329,374,375],{},"Clean already",[329,377,378],{},"Needs remediation",[311,380,381,386,389],{},[329,382,383],{},[17,384,385],{},"Decision-making",[329,387,388],{},"One accountable owner",[329,390,391],{},"Committee, slow sign-off",[14,393,394],{},"A tightly scoped, few-banks implementation can be a few months. A multi-bank, multi-entity global rollout with full scope is comfortably a year or more — and the difference is mostly connectivity, data and decision speed, not the software.",[31,396,398],{"id":397},"the-team-you-need","The team you need",[305,400,401,411],{},[308,402,403],{},[311,404,405,408],{},[314,406,407],{},"Role",[314,409,410],{},"Owns",[324,412,413,423,433,443,453,463],{},[311,414,415,420],{},[329,416,417],{},[17,418,419],{},"Programme owner (treasury)",[329,421,422],{},"The outcome, end to end — accountable, not a committee",[311,424,425,430],{},[329,426,427],{},[17,428,429],{},"Treasury SMEs",[329,431,432],{},"The business design; how cash, payments and risk actually run",[311,434,435,440],{},[329,436,437],{},[17,438,439],{},"Technical \u002F integration lead",[329,441,442],{},"ERP and bank interfaces, environments",[311,444,445,450],{},[329,446,447],{},[17,448,449],{},"Data owner",[329,451,452],{},"Master-data quality, migration, reconciliation",[311,454,455,460],{},[329,456,457],{},[17,458,459],{},"Vendor \u002F implementation partner",[329,461,462],{},"Product configuration and method",[311,464,465,470],{},[329,466,467],{},[17,468,469],{},"Test lead",[329,471,472],{},"SIT and UAT, scenarios, defect triage",[31,474,476],{"id":475},"what-usually-goes-wrong","What usually goes wrong",[14,478,479,480,484],{},"Every failure pattern here has the same root: the change is treated as software, not treasury. It's covered in depth in ",[21,481,483],{"href":482},"\u002Fblog\u002Fwhy-tms-implementations-fail","why TMS implementations fail"," — but the short version is: own the outcome, start connectivity and data early, be honest about what a forecast can do in year one, and protect testing. Do that and the phases above go from a gamble on the vendor to a change you're genuinely running.",[486,487],"hr",{},[14,489,490],{},[67,491,492,493,497,498,500,501,504,505,509],{},"Part of the ",[21,494,496],{"href":495},"\u002Ftopics\u002Ftreasury-management-systems","Treasury Management Systems guide",". See also the ",[21,499,119],{"href":118}," and ",[21,502,503],{"href":482},"why implementations fail",". The ",[21,506,508],{"href":507},"\u002Fnewsletter","newsletter"," sends one finance-systems pattern, product decision or build lesson every two weeks.",{"title":511,"searchDepth":512,"depth":512,"links":513},"",2,[514,515,516,517,518,519,520,521,522,523,524,525],{"id":33,"depth":512,"text":34},{"id":103,"depth":512,"text":104},{"id":129,"depth":512,"text":130},{"id":145,"depth":512,"text":146},{"id":157,"depth":512,"text":158},{"id":180,"depth":512,"text":181},{"id":196,"depth":512,"text":197},{"id":216,"depth":512,"text":217},{"id":287,"depth":512,"text":288},{"id":299,"depth":512,"text":300},{"id":397,"depth":512,"text":398},{"id":475,"depth":512,"text":476},"tms-implementation","2026-07-23","How a TMS implementation really runs — mobilize, design, bank connectivity, data migration, testing, cutover, hypercare. The phases, timeline and critical path.",false,"md",null,[533,536,539],{"question":534,"answer":535},"How long does a TMS implementation take?","For a mid-to-large corporate, plan on several months to over a year end to end, depending on the number of banks, entities and the scope. Software configuration is rarely the long pole — bank connectivity onboarding, data migration and testing are. A single-entity, few-banks implementation can be much faster; a multi-bank, multi-entity global rollout is a programme, not a project.",{"question":537,"answer":538},"What are the phases of a TMS implementation?","Typically: mobilize and scope, design (target operating model and configuration decisions), build and configure, bank connectivity, data migration, testing (system integration testing then user acceptance testing), cutover and go-live, and hypercare. Bank connectivity and data run in parallel from early on because they are the usual critical paths.",{"question":540,"answer":541},"Who should own a TMS implementation?","Treasury should own it, as a treasury change programme — not IT, and not the vendor. You need a single accountable owner for the outcome, treasury subject-matter experts embedded (not just consulted), a technical\u002Fintegration lead, a data owner, and clear governance. The most common failure is running it as an IT install with treasury on the sidelines.",{},10,"\u002Fblog\u002Ftreasury-management-system-implementation-guide","treasury-management-systems","TMS implementation","annual","reviewed","Tan Gravam","informational-commercial",{"title":5,"description":528},"blog\u002Ftreasury-management-system-implementation-guide",[554,555,556,557],"treasury","tms","implementation","finance-systems","text","DwFsQAMcvp0wQWrQ4c2Fzp8WZvsrkLXqCZScj9OTavU",[561,565],{"title":562,"path":563,"stem":564,"type":558,"language":531,"draft":529,"children":-1},"Building the Business Case for a Treasury Management System","\u002Fblog\u002Ftreasury-management-system-business-case","blog\u002Ftreasury-management-system-business-case",{"title":566,"path":118,"stem":567,"type":558,"language":531,"draft":529,"children":-1},"Treasury Management System Requirements Checklist","blog\u002Ftreasury-management-system-requirements-checklist",[569,572,575],{"path":23,"title":570,"description":571},"TMS Implementation Timeline and Phases","The phases of a TMS implementation in order, and what actually drives how long it takes — banks, entities, modules, data quality and decision speed.",{"path":77,"title":573,"description":574},"TMS Data Migration","TMS data migration means moving master data, open positions and live deals into a new treasury system — cleanly, and reconciled so your positions still tie out.",{"path":482,"title":576,"description":577},"Why TMS Implementations Fail (and How to De-Risk Yours)","Why TMS implementations fail: rarely the software — it's the treasury change. IT-project thinking, bank connectivity, dirty data, no one owning the outcome.",1785182343150]