[{"data":1,"prerenderedAt":273},["ShallowReactive",2],{"blog-\u002Fblog\u002Fiso-20022-payments-pain-001-pain-002":3,"blog-surround-\u002Fblog\u002Fiso-20022-payments-pain-001-pain-002":255,"blog-related-\u002Fblog\u002Fiso-20022-payments-pain-001-pain-002":263},{"id":4,"title":5,"audience":6,"body":9,"cluster":220,"date":221,"description":222,"draft":223,"extension":224,"factCheckedAt":225,"faq":226,"featured":223,"language":225,"meta":236,"navigation":237,"order":238,"originalAsset":225,"path":239,"pillar":240,"primaryKeyword":241,"relatedProject":225,"releaseScope":225,"reviewCycle":242,"reviewStatus":243,"reviewedBy":244,"searchIntent":245,"seo":246,"sources":225,"stem":247,"tags":248,"type":253,"updated":221,"__hash__":254},"blog\u002Fblog\u002Fiso-20022-payments-pain-001-pain-002.md","ISO 20022 Payments Explained: pain.001, pain.002 and the camt Family",[7,8],"treasury-system-lead","solution-architect",{"type":10,"value":11,"toc":212},"minimark",[12,30,35,46,49,77,84,88,112,120,124,145,149,175,182,185,188],[13,14,15,19,20,23,24,29],"p",{},[16,17,18],"strong",{},"ISO 20022 is the global standard for financial messaging, built on structured XML — and for corporate payments its key messages are pain.001, the payment instruction you send to the bank, and pain.002, the status report the bank sends back."," Statements come in the related ",[16,21,22],{},"camt"," family. ISO 20022 is ",[25,26,28],"a",{"href":27},"\u002Fblog\u002Fiso-20022-migration-mt-to-mx","replacing the patchwork of legacy and proprietary formats"," across the industry, and its structured data is what makes better straight-through processing and reconciliation possible — provided you handle the bank-specific variations.",[31,32,34],"h2",{"id":33},"what-iso-20022-is","What ISO 20022 is",[13,36,37,38,41,42,45],{},"ISO 20022 is not a single message; it's a ",[16,39,40],{},"standard"," — a common, structured XML language for financial messages across payments, cash management, securities and more. Its value over older formats is ",[16,43,44],{},"structure",": information sits in defined fields rather than free text, so it's richer, cleaner and easier for systems to process automatically. That's why market infrastructures and cross-border payments are migrating to it.",[13,47,48],{},"The messages are organized into families. The two a corporate treasury deals with most:",[50,51,52,64],"ul",{},[53,54,55,58,59,63],"li",{},[16,56,57],{},"pain"," — ",[60,61,62],"em",{},"Payments Initiation"," (customer-to-bank): instructing and tracking payments.",[53,65,66,58,68,71,72,76],{},[16,67,22],{},[60,69,70],{},"Cash Management",": statements and reports (covered in ",[25,73,75],{"href":74},"\u002Fblog\u002Fbank-statement-formats-mt940-camt053-bai2","statement formats",").",[13,78,79,80,83],{},"(You'll also hear ",[16,81,82],{},"pacs"," — the bank-to-bank clearing messages — but those are between banks, not something a corporate sends.)",[31,85,87],{"id":86},"the-payment-messages","The payment messages",[50,89,90,96,106],{},[53,91,92,95],{},[16,93,94],{},"pain.001 — CustomerCreditTransferInitiation."," The payment instruction a corporate sends to its bank: pay these beneficiaries, these amounts, from these accounts, on these dates. This is the file your treasury system or payment factory generates to make payments.",[53,97,98,101,102,105],{},[16,99,100],{},"pain.002 — CustomerPaymentStatusReport."," The bank's reply: the status of the instruction and its payments — accepted, rejected (with reasons), pending. It's what lets you ",[60,103,104],{},"track"," a payment rather than fire and forget.",[53,107,108,111],{},[16,109,110],{},"pain.008 — CustomerDirectDebitInitiation."," The direct-debit equivalent of pain.001, where you're collecting rather than paying.",[13,113,114,115,119],{},"Together, pain.001 out and pain.002 back give you a controlled, trackable payment flow — the backbone of a modern ",[25,116,118],{"href":117},"\u002Fblog\u002Fwhat-is-an-in-house-bank","payment factory",".",[31,121,123],{"id":122},"why-the-migration-matters","Why the migration matters",[13,125,126,127,131,132,136,137,140,141,144],{},"The formats treasury relies on are moving to ISO 20022. ",[25,128,130],{"href":129},"\u002Fblog\u002Fswift-gpi-tracking-cross-border-payments","SWIFT's cross-border payments"," and many market infrastructures are migrating from legacy MT messages to ISO 20022 (MX), and instant-payment schemes are ISO 20022 native. For treasury that means two things: your systems and ",[25,133,135],{"href":134},"\u002Fblog\u002Febics-european-bank-connectivity","bank interfaces"," need to ",[16,138,139],{},"send pain.001 and consume camt"," correctly, and you gain ",[16,142,143],{},"richer data"," — better structured references and remittance information — which improves straight-through processing and reconciliation. The upside is real; it just has to be implemented per bank.",[31,146,148],{"id":147},"what-usually-goes-wrong","What usually goes wrong",[50,150,151,157,163,169],{},[53,152,153,156],{},[16,154,155],{},"Assuming ISO 20022 means identical."," Banks implement the standard with variations — different mandatory fields, different handling of optional ones. A pain.001 that one bank accepts may be rejected by another until mapped to its rules. \"We support ISO 20022\" is a starting point, not a guarantee of interoperability.",[53,158,159,162],{},[16,160,161],{},"Ignoring pain.002."," Sending payments (pain.001) without consuming the status report (pain.002), so you don't actually know what happened to them until something breaks.",[53,164,165,168],{},[16,166,167],{},"Underestimating mapping and testing."," Treating format adoption as a switch rather than a per-bank mapping-and-testing exercise — exactly where connectivity projects run long.",[53,170,171,174],{},[16,172,173],{},"Losing the richer data."," Adopting the XML format but still cramming references into free-text, throwing away the structure that was the whole point.",[176,177,179],"callout",{"type":178},"tip",[13,180,181],{},"Treat ISO 20022 adoption like any bank interface: map and test pain.001 (and pain.002) per bank against real scenarios, and make sure you're using the structured fields — not recreating MT-era free-text habits inside XML. The standard gives you the capability; your implementation decides whether you get the benefit.",[13,183,184],{},"Get the payment messages right — pain.001 out, pain.002 back, mapped and tested per bank — and you have a controlled, trackable, reconcilable payment flow. Half-adopt it and you get XML with none of the benefit.",[186,187],"hr",{},[13,189,190],{},[60,191,192,193,197,198,201,202,206,207,211],{},"Part of the ",[25,194,196],{"href":195},"\u002Ftopics\u002Ftreasury-systems-architecture","Treasury Systems Architecture guide",". See also ",[25,199,200],{"href":74},"bank statement formats"," and ",[25,203,205],{"href":204},"\u002Fblog\u002Ftreasury-bank-connectivity-swift-host-to-host-api-ebics","bank connectivity channels",". The ",[25,208,210],{"href":209},"\u002Fnewsletter","newsletter"," sends one finance-systems pattern, product decision or build lesson every two weeks.",{"title":213,"searchDepth":214,"depth":214,"links":215},"",2,[216,217,218,219],{"id":33,"depth":214,"text":34},{"id":86,"depth":214,"text":87},{"id":122,"depth":214,"text":123},{"id":147,"depth":214,"text":148},"connectivity","2026-07-23","ISO 20022 is the global XML standard for financial messaging. For payments, pain.001 is the instruction you send and pain.002 the status back. What they are.",false,"md",null,[227,230,233],{"question":228,"answer":229},"What is pain.001 and pain.002?","They're ISO 20022 payment messages. pain.001 is the CustomerCreditTransferInitiation — the structured XML payment instruction a corporate sends to its bank to make credit transfers. pain.002 is the CustomerPaymentStatusReport — the message the bank sends back reporting the status of that instruction (accepted, rejected, pending). Together they cover sending a payment and tracking what happened to it.",{"question":231,"answer":232},"What is ISO 20022 in simple terms?","ISO 20022 is a global standard for financial messages built on structured XML. Instead of many proprietary and legacy formats, it provides a common, richly structured language for payments (the pain and pacs families), cash management and statements (camt), and more. Its structured data carries more information more cleanly than older formats, which is why the industry is migrating to it.",{"question":234,"answer":235},"Why is the ISO 20022 migration important for treasury?","Because the formats treasury depends on — payment initiation and bank statements — are moving to ISO 20022, and the richer, structured data improves straight-through processing and reconciliation. Market infrastructures and SWIFT cross-border payments are migrating from legacy MT messages to ISO 20022, so treasuries need their systems and bank interfaces to send pain.001 and consume camt correctly, allowing for bank-specific variations.",{},true,4,"\u002Fblog\u002Fiso-20022-payments-pain-001-pain-002","treasury-systems-architecture","ISO 20022 treasury payments","on ISO 20022 \u002F bank format changes","reviewed","Tan Gravam","informational",{"title":5,"description":222},"blog\u002Fiso-20022-payments-pain-001-pain-002",[249,250,251,252],"treasury","architecture","iso-20022","payments","text","tJXKJe4MQ5VTYYzmx2QkCmYGwVdZunqJDkuSITfWdp0",[256,259],{"title":257,"path":27,"stem":258,"type":253,"language":225,"draft":223,"children":-1},"ISO 20022 Migration: Moving from SWIFT MT to MX (CBPR+)","blog\u002Fiso-20022-migration-mt-to-mx",{"title":260,"path":261,"stem":262,"type":253,"language":225,"draft":223,"children":-1},"Liquidity Items in SAP Cash Management","\u002Fblog\u002Fliquidity-items-in-sap-cash-management","blog\u002Fliquidity-items-in-sap-cash-management",[264,267,270],{"path":204,"title":265,"description":266},"Treasury Bank Connectivity: SWIFT vs Host-to-Host vs API vs EBICS","SWIFT, host-to-host, API and EBICS — how corporate treasury connects to banks, compared on reach, cost, real-time capability and setup effort.",{"path":134,"title":268,"description":269},"EBICS Explained: European Bank Connectivity","What EBICS is — an internet-based European standard for exchanging payment and statement files with banks — and where it fits alongside SWIFT and host-to-host.",{"path":74,"title":271,"description":272},"Bank Statement Formats: MT940 vs camt.053 vs BAI2","MT940, camt.053 and BAI2 are the main bank statement formats treasury imports: legacy SWIFT, modern ISO 20022, a US format. How they differ and which to use.",1785182341019]