ServicesCAP-03
Connectivity Readiness Review
Most finance teams reach their banks through a mix of portals, file transfers and the occasional API. Each connection has its own format. We map what you have, show where it's fragile, and set out neutral options for simplifying it.
Every bank × channel × format, on one page.
Use the filters to see the gaps, the legacy formats and the banks that need attention before the Swift address rule on 14 November 2026.
| Bank | Channel | Statements | Payments | Postal addresses |
|---|---|---|---|---|
| Bank A | SFTP | BAI2 (legacy) | Proprietary CSV (legacy, gap) | Unstructured (address, gap) |
| Bank B | Swift | camt.053.001.02 (legacy) | pain.001.001.03 (legacy) | Hybrid |
| Bank C | Host-to-host | MT940 (legacy) | pain.001.001.09 | Unconfirmed (address) |
| Bank D | Portal only (gap) | Manual export (gap) | Manual upload (gap) | Unknown (address, gap) |
| Bank E | API | camt.053.001.08 | pain.001.001.09 | Structured |
| Bank F | SFTP | BAI2 (legacy) | pain.001.001.03 (legacy) | Unstructured (address, gap) |
ExampleThe shape of the map a Connectivity Readiness Review delivers. Invented banks and data.
Companies with three or more banks that are weighing ISO 20022 migration, bank APIs, a new TMS or ERP, or simply want fewer portals and manual downloads.
- A list of banks and accounts in scope (account numbers not needed)
- How you connect to each today: portal, SFTP, host-to-host, Swift, API, or a third party
- The file formats in use, plus sample files if you can share synthetic or redacted ones
- Your ERP or TMS, and the pain points you already know about
- A bank × channel × format map of your current setup
- Gaps and risks: single points of failure, legacy formats, manual steps
- Readiness for ISO 20022 changes, including the Swift structured-address rule from 14 November 2026
- Specific questions to put to each bank
- A 90-day plan with options and trade-offs, not a vendor recommendation in disguise
$3,000–$7,500Fixed fee
The exact figure depends on the number of banks and channels in scope, and is confirmed in writing before work starts. The timeline is agreed up front.