Payments Training Hub

ISO 20022 Technical Implementation

D04 Messaging and standards · 8 lessons

Version 1.0 | Last reviewed 2026-11-05

How the standard is built, read and validated in real systems

ISO 20022 technical implementation: how the standard is built, read and validated in real systems.

What You Can Do After This Chapter

Learning objective. Learner reads an ISO 20022 schema, explains amounts, timestamps and market practice, and shows how the same pacs.008 differs by rail, with correct ledger entries and validation handling. Learner also explains wash accounts, LEI, and FATF Recommendation 16 debtor and creditor data.

Practical assessment. Learner receives a case where a EUR 10,000 payment must be expressed as pacs.008.001.08 under CBPR+ rules and under SEPA rules, then drafts both messages, lists every field that changes, and explains why each change is required. Learner also drafts the T-account entries, the LEI and travel rule data, and the handling when a message fails schema validation. Learner also notes the current state in 2026, with SWIFT MT coexistence ended and Fedwire live on ISO 20022.

Expected deliverables.

Completion criterion. Learner drafts correct CBPR+ and SEPA pacs.008 messages, lists the field differences accurately, and explains validation, cardinality and ledger entries clearly, and the per rail mapping table is complete and accurate.

In this chapter
  1. Reading an ISO 20022 Schema: XSD Patterns
  2. Currency and Amount: Decimal Precision and Minor Units
  3. UTC Offsets and Timestamps: Why Every Time Is UTC with Offset
  4. Market Practice: PMPG, CBPR+, SEPA, Fedwire, CHAPS and FedNow
  5. T-Accounts and Wash Accounts in Payment Accounting
  6. LEI, FATF Recommendation 16 and Mandatory Versus Optional Elements
  7. Worked Example: The Same EUR 10,000 Payment as pacs.008 Under CBPR+ and SEPA
  8. Validating an ISO 20022 XML file: schemas, errors and fixes

Start Lesson 1: Reading an ISO 20022 Schema: XSD Patterns →