ISO 20022 | Data That Pays | Week 2.2 - Pre-validation in the Wild

Mon (Teach) - What pre-validation actually fixes (and doesn't) IBAN/BIC/LEI presence & shape vs real-world reachability; what's in scope. Name/address mismatch...

# Week 2 - Data That Pays: Pre-validation in the wild

Mon (Teach) - What pre-validation actually fixes (and doesn't)
* IBAN/BIC/LEI presence & shape vs real-world reachability; what's in scope.
* Name/address mismatch realities; why pre-check ≠ guarantee.
* Where to put the check (file upload, API, ERP plug-in).
* FLOW for my pre-validation swimlane."

Tue (Advise) - Rolling pre-checks into client UX
* Tactically: reject-with-advice messages; instant hints (IBAN structure, LEI).
* Keep a client-visible 'error library' mapped to business fix-tips.
* Instrumentation: log % caught pre-send vs post-send; show the ROI.
* LIBRARY to get the error-to-fix table."

Thu (Debate) - Transparency beats 'speed demo': prove fewer repairs
* Share before/after repair %, RFI/1k, average repair fee.
* Argue that published outcomes convert better than "fastest corridor" claims.

Fri (Recap Carousel) - Data & controls map
* Who owns LEI, purpose, addresses, pre-check, and logs; where each is stored.
* 30-day plan: ship pre-validation for top 3 corridors; publish first SLA card.
* MAP-S2 for my data-ownership+logging map."

Topics: ISO 20022, Payments, SWIFT, Data Quality, Real-Time Payments