MT103 → pacs.008

Context: Cross-border customer credit transfer translation, in the spirit of public CBPR+ and PMPG translation guidance. Educational summary — the applicable usage guideline is the rule.

Contributor Shubham Mathure18 July 2026

EXPLORE THE TRANSLATION — SIDE BY SIDE

Click a highlighted field on either side. Its counterparts light up opposite, and the translation note appears below.

MT103

 1{1:F01DEMOUS33AXXX0000000000}
 2{2:I103DEMOGB2LXXXXN}
 3{3:{108:DEMO-ONLY}}
 4{4:
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22-}

pacs.008

 1<?xml version="1.0" encoding="UTF-8"?>
 2<!-- Illustrative non-production data -->
 3<Document xmlns="urn:iso:std:iso:20022:tech:xsd:pacs.008.001.08">
 4  <FIToFICstmrCdtTrf>
 5    <GrpHdr>
 6
 7
 8
 9
10    </GrpHdr>
11    <CdtTrfTxInf>
12      <PmtId>
13        <InstrId>DEMO-INSTR-001</InstrId>
14
15        <TxId>DEMO-TX-001</TxId>
16
17      </PmtId>
18      <PmtTpInf>
19        <SvcLvl><Cd>SEPA</Cd></SvcLvl>
20      </PmtTpInf>
21
22
23
24      <InstgAgt><FinInstnId><BICFI>DEMODEFFXXX</BICFI></FinInstnId></InstgAgt>
25      <InstdAgt><FinInstnId><BICFI>DEMOGB2LXXX</BICFI></FinInstnId></InstdAgt>
26
27
28
29
30
31
32
33
34
35
36
37
38      <DbtrAcct><Id><IBAN>DE02120300000000202051</IBAN></Id></DbtrAcct>
39
40
41
42
43
44
45
46
47
48
49
50
51      <CdtrAcct><Id><IBAN>GB33BUKB20201555555555</IBAN></Id></CdtrAcct>
52
53
54
55
56
57
58
59
60
61
62    </CdtTrfTxInf>
63  </FIToFICstmrCdtTrf>
64</Document>

Nothing selected yet — try the amount field on either side and watch one MT field become two structured MX elements.

MT103 → pacs.008 field mapping
MT103	pacs.008	CORRESPONDENCE	NOTE
`:20:`	`CdtTrfTxInf/PmtId/InstrId`	PARTIAL	The sender's reference becomes the instruction identification; the message-level GrpHdr/MsgId is a separate, new identifier.
`Block 3 / field 121`	`CdtTrfTxInf/PmtId/UETR`	DIRECT	The UETR travels unchanged — it is the same end-to-end tracking key in both worlds.
`:23B:`	none	NO EQUIVALENT	The bank operation code has no single MX element; service level and local instrument elements carry related meaning.
`:32A:`	`CdtTrfTxInf/IntrBkSttlmDt + IntrBkSttlmAmt`	TRANSFORMED	One MT field splits into two structured elements: date and currency+amount separate cleanly in MX.
`:33B:`	`CdtTrfTxInf/InstdAmt`	DIRECT	The originally instructed amount maps to the instructed amount element.
`:36:`	`CdtTrfTxInf/XchgRate`	DIRECT	Exchange rate carries across when currency conversion applies.
`:50a:`	`CdtTrfTxInf/Dbtr + DbtrAcct`	TRANSFORMED	Free-format name/address lines become a structured party plus a separate account element. Going MX→MT, structured addresses risk truncation into 4×35 lines.
`:52a:`	`CdtTrfTxInf/DbtrAgt`	DIRECT	The ordering institution maps to the debtor agent, normally identified by BIC.
`:53a:`	`GrpHdr/SttlmInf`	TRANSFORMED	Correspondent/settlement details restructure into the settlement information block.
`:57a:`	`CdtTrfTxInf/CdtrAgt`	DIRECT	The account-with institution is the creditor agent.
`:59a:`	`CdtTrfTxInf/Cdtr + CdtrAcct`	TRANSFORMED	Beneficiary name/address and account split into a structured party and account element.
`:70:`	`CdtTrfTxInf/RmtInf`	PARTIAL	4×35 characters of free text map into remittance information; MX additionally offers structured remittance the MT side cannot express.
`:71A:`	`CdtTrfTxInf/ChrgBr`	TRANSFORMED	Charge codes translate: OUR→DEBT, SHA→SHAR, BEN→CRED.
`:71F: / :71G:`	`CdtTrfTxInf/ChrgsInf`	TRANSFORMED	Deducted and sender's charges restructure into repeatable charges information entries.
`:72:`	`InstrForNxtAgt / InstrForCdtrAgt`	PARTIAL	Free-format sender-to-receiver text becomes coded instruction elements where a code exists; uncodeable text is a known translation pain point.

Sources for this mapping3

Market practice
Payments Market Practice Group market practice documents ↗ — Payments Market Practice Group
Global market practice for payment messaging, including guidance on structured party data, cover payments, and the coexistence of MT and ISO 20022 formats. · Checked 2026-07-12
The PMPG publishes individual papers via the Swift website; its recommendations are market practice, not binding scheme rules, and adoption varies between institutions.
Market practice
Cross-Border Payments and Reporting Plus (CBPR+) usage guidelines ↗ — Swift (CBPR+ working group)
Defines how ISO 20022 messages (including pacs.008, pacs.009, pacs.002, pacs.004, and camt investigation messages) are used and validated for cross-border payments on the Swift network. · Checked 2026-07-12
What this simplifies: Based on public summaries; the full CBPR+ translation rules require MyStandards access.
Full guidelines require MyStandards access; content here relies on public summaries. MT-to-CBPR+ translation rules are published on Swift's translation portal.
Simplified educational illustration
Payments Signal editorial teaching models — Payments Signal
This site's own simplified teaching models. · Checked 2026-07-12
What this simplifies: Row set curated for learning; option letters, conditional rules, and edge cases omitted.
Used wherever diagrams, scenarios, figures, or example values are didactic constructions rather than sourced facts; every such use carries a simplifications disclosure. All people, companies, banks, and list entries in examples are fictional.