Answers
How do you test an ISO 20022 migration?
In short
Test an ISO 20022 migration by validating schema, business rules, enrichment, downstream consumption and reconciliation — for every message type in scope (pacs, pain, camt) and every counterparty.
Short answer
Test an ISO 20022 migration by validating schema, business rules, enrichment, downstream consumption and reconciliation — for every message type in scope (pacs, pain, camt) and every counterparty.
What this actually means in practice
Schema testing catches structural breaks; business rule testing catches semantic gaps; enrichment testing proves you preserve structured data end-to-end. Run translation tests in both directions until co-existence ends. Reconcile against the previous MT equivalents until the scheme cutover completes.
The most common pitfall
Truncating structured data on the way into the ledger and losing the regulatory benefit of ISO 20022.
What to do next
Build an end-to-end ISO 20022 harness with schema + business + reconciliation gates.
Frequently asked questions
Does Forth Systems help with this?
Yes — Forth Systems works with banks, payment institutions, insurers and infrastructure operators on exactly this kind of work. Engagements start with a fixed-scope assessment so you see the shape before committing.
How experienced is the team?
Engagements are staffed by named, UK-based senior engineers — not a rotating offshore pool. References from the second line of comparable clients are available on request.
Where are you based?
Edinburgh-based, delivering UK-wide with onsite presence in London and across Scotland as required.
How fast can we start?
Most engagements start within 2-4 weeks of a signed SoW, faster where an existing supplier framework is in place.