Skip to content
All reading lists

Reading List

SWIFT and ISO 20022 Message Reference Reading List

This reading list follows the operator's task: inspect an MT103, map it to pacs.008, distinguish a status report from a return, examine the cover leg, reconcile account reports, investigate or trace the payment, and interpret the charge option. Read in order for the full path, or use each entry as a lookup next to a payment file.

9 briefings ~108 min total read

Who this is for

Payment operations and treasury teams handling cross-border payments, implementation engineers mapping MT to ISO 20022 during migration, and support teams who have to answer 'where is my money' with a field reference rather than a guess.

Reading order

The full reading list

  1. MT103 Field-by-Field: The Operator Reference

    The single customer credit transfer, field by field. What sits in :50K:, :59:, :71A: and :72:, which fields are mandatory, and which ones correspondents actually read when they decide how to route and how much to deduct.

    14 min read

  2. MT103 to pacs.008 Field Mapping: The Operator Reference

    Find a specific MT103 field or pacs.008 path, then share its field link with an investigator. The source-scoped table keeps the mapping type and operator qualification beside each correspondence; do not treat an approximate mapping as universal.

    14 min read

  3. pacs.002 vs pacs.004: Status, Rejection, and Return

    A status report and a return answer different questions. Use this reference to distinguish pacs.002 status messages from pacs.004 payment returns before treating a rejection or reversal as money moving back.

    8 min read

  4. MT202 COV and pacs.009 COV: The Cover-Payment Operator Reference

    MT202 COV and pacs.009 COV carry underlying customer details alongside the bank-to-bank settlement instruction. Use this reference when a correspondent cover leg needs investigation; do not infer the missing leg from message visibility alone.

    13 min read

  5. pain.001 and pain.002: The Payment Initiation and Status Reference

    The corporate-to-bank side. pain.001 initiates, pain.002 reports status — and the status codes in pain.002 are the difference between knowing a batch was rejected and discovering it from a customer complaint days later.

    12 min read

  6. camt.052, camt.053 and camt.054: The Account Reporting Operator Reference

    Intraday, end-of-day, and debit/credit notification reporting. Which camt message answers which reconciliation question, and why picking the wrong one produces a reconciliation process that is always a day behind.

    13 min read

  7. ISO 20022 Investigation Messages: A camt Operator Reference

    When something has already gone wrong: the camt investigation family for recalls, claims of non-receipt, and cancellation requests. The structured alternative to emailing a correspondent and hoping.

    13 min read

  8. Tracing a SWIFT Payment: UETR, gpi, and Where It Gets Stuck

    Use a UETR as an investigation reference and interpret available gpi status information. A UETR alone does not establish gpi tracking or reveal where funds stopped.

    14 min read

  9. OUR, SHA, and BEN: Who Bears Wire Charges and Why Credit Can Arrive Short

    Finish with charge allocation. OUR, SHA and BEN indicate who is instructed to bear transfer charges; compare the instruction with the actual deductions before explaining why a beneficiary received less.

    7 min read

Related

Global Payments SEPA Return and Reject Codes SWIFT ISO 20022 UETR Correspondent Banking