MT191 / MT291 ↔ camt.106
1 pair on this page · Use case: Charges/interest
Business purpose
Request for Payment of Charges, Interest and Other Expenses — a financial institution requests reimbursement of charges, interest, or other expenses (previously unknown to the receiver) arising from handling a prior transaction. MT191 is the category-1 (customer/FI-facing) variant, MT291 the category-2 (FI-to-FI) variant; both carry an identical official name and differ only in SWIFT message category.
What does NOT map cleanly
Swift lists MT191/MT291 against camt.106 (Charges Payment Request), distinct from MT190/MT290 against camt.105 (Charges Payment Notification). This is a message-purpose mapping, not proof that every field or bilateral charge workflow maps directly. For reconciliation, keep the request and any subsequent charge settlement separate: a request for reimbursement does not by itself prove that the requested amount was paid.
Migration notes
Swift's September 2026 roadmap shows a Standards Release 2028 planning aim for charge messages and says enforcement depends on adoption. The same document warns that roadmap dates are under review after the SR2026 deferral. Do not treat the aim as a confirmed universal retirement deadline for MT191/MT291.
Sources
- Swift — CBPR+ roadmap beyond Standards Release 2025, September 2026 v6 ·Swift lists MT191/291 against camt.106 and MT190/290 against camt.105 in its charges-message table (confirmed)
- SWIFT — SWIFT Training Catalogue, Charges Payment Request (camt.106) ·camt.106 replaces MT191 as the CBPR+ charges-payment-request equivalent; SWIFT's own training catalogue lists 'Charges Payment Request (camt.106) for a Single Charge' as a distinct training module (confirmed)
- Swift — CBPR+ roadmap beyond Standards Release 2025, September 2026 v6 ·Swift's September 2026 roadmap shows an SR2028 migration aim for charges, with enforcement dependent on adoption; it warns that the dates and information are under review following the SR2026 deferral (confirmed)