[{"data":1,"prerenderedAt":725},["ShallowReactive",2],{"blog-\u002Fblog\u002Fcamt-054-notification-explained":3,"blog-related-\u002Fblog\u002Fcamt-054-notification-explained":702,"blog-surround-\u002Fblog\u002Fcamt-054-notification-explained":724},{"id":4,"title":5,"audience":6,"body":9,"cluster":649,"conversionGoal":650,"cornerstone":651,"date":652,"description":653,"draft":651,"extension":654,"factCheckedAt":652,"faq":655,"featured":651,"language":650,"meta":668,"minRead":246,"navigation":669,"order":670,"originalAsset":650,"path":671,"pillar":672,"primaryKeyword":673,"publicationOrder":674,"relatedProject":650,"releaseScope":675,"reviewCycle":676,"reviewMethod":677,"reviewStatus":678,"reviewedAt":652,"reviewedBy":679,"searchIntent":680,"seo":681,"sources":682,"stem":695,"tags":696,"type":700,"updated":650,"__hash__":701},"blog\u002Fblog\u002Fcamt-054-notification-explained.md","camt.054: The Debit\u002FCredit Notification and When You Need It",[7,8],"treasury-system-lead","solution-architect",{"type":10,"value":11,"toc":641},"minimark",[12,31,36,39,133,149,174,178,185,309,322,361,401,405,416,454,469,489,492,496,532,536,559,569,573,613,616,619,637],[13,14,15,19,20,25,26,30],"p",{},[16,17,18],"strong",{},"camt.054 is the ISO 20022 BankToCustomerDebitCreditNotification — the account servicer notifying the account owner of single or multiple debit and\u002For credit entries — and the single most important sentence in its ISO definition is this one: \"It does not contain balance information.\""," It is not a statement. It doesn't compete with one. Its job is detail: telling you that specific movements happened and what is inside them — most valuably when the statement shows one lump-sum booking and the individual direct debits, giro receipts or card settlements that make it up are documented nowhere else. If you're choosing between statement formats, start with the ",[21,22,24],"a",{"href":23},"\u002Fblog\u002Fbank-statement-formats-mt940-camt053-bai2","MT940 vs camt.053 vs BAI2 comparison","; if you're parsing statements, the ",[21,27,29],{"href":28},"\u002Fblog\u002Fcamt-053-structure-and-fields","camt.053 field-by-field walkthrough"," is the sibling of this post. This one is about the message that rides alongside the statement, verified against ISO's own Message Definition Report and Nordea's camt.054 implementation guidelines.",[32,33,35],"h2",{"id":34},"camt053-vs-camt054-vs-camt052-three-messages-one-family","camt.053 vs camt.054 vs camt.052: three messages, one family",[13,37,38],{},"ISO defines the three bank-to-customer cash management messages in one report, and the scope statements draw the lines precisely:",[40,41,42,60],"table",{},[43,44,45],"thead",{},[46,47,48,51,54,57],"tr",{},[49,50],"th",{},[49,52,53],{},"camt.053 Statement",[49,55,56],{},"camt.052 Account Report",[49,58,59],{},"camt.054 Debit\u002FCredit Notification",[61,62,63,78,92,119],"tbody",{},[46,64,65,69,72,75],{},[66,67,68],"td",{},"ISO name",[66,70,71],{},"BankToCustomerStatement",[66,73,74],{},"BankToCustomerAccountReport",[66,76,77],{},"BankToCustomerDebitCreditNotification",[46,79,80,83,86,89],{},[66,81,82],{},"Entries",[66,84,85],{},"Booked entries only",[66,87,88],{},"Pending and booked items",[66,90,91],{},"Pending and booked items; one or more debit and\u002For credit entries",[46,93,94,97,108,116],{},[66,95,96],{},"Balances",[66,98,99,100,104,105],{},"Mandatory — ",[101,102,103],"code",{},"\u003CBal>"," is ",[101,106,107],{},"[1..n]",[66,109,110,111,104,113],{},"Optional — ",[101,112,103],{},[101,114,115],{},"[0..n]",[66,117,118],{},"None — the structure has no balance element",[46,120,121,124,127,130],{},[66,122,123],{},"Role",[66,125,126],{},"The record: complete account activity plus balances for a period",[66,128,129],{},"Interim picture of the account, typically intraday",[66,131,132],{},"Advice of specific entries, with their underlying transaction detail",[13,134,135,136,139,140,143,144,148],{},"Two of those cells do most of the work. ",[16,137,138],{},"camt.053 contains booked entries only, with balances the message structure won't let a bank omit"," — that's what makes it the reconciliation anchor. ",[16,141,142],{},"camt.054 has no balance element at all"," — ISO's usage text says so outright — which is what makes it a notification rather than any kind of statement. camt.052 sits between them: same skeleton as the statement, but balances optional and pending items allowed, which is why it serves as the intraday refresh in a ",[21,145,147],{"href":146},"\u002Fblog\u002Fhow-to-build-a-daily-cash-position","daily cash position",".",[13,150,151,152,155,156,159,160,163,164,166,167,170,171,173],{},"The family resemblance is structural, not cosmetic. One level down, all three messages are a GroupHeader plus a repeating per-account block — ",[101,153,154],{},"\u003CStmt>"," in 053, ",[101,157,158],{},"\u003CRpt>"," in 052, ",[101,161,162],{},"\u003CNtfctn>"," in 054, each ",[101,165,107],{}," with one ",[101,168,169],{},"\u003CAcct>"," and ",[101,172,115],{}," entries. There's even a fourth relative: camt.060, the AccountReportingRequest, is the message a customer sends to ask the bank for any of the three. Versions travel together too — the ISO catalogue currently lists all three at version 14 (camt.054.001.14), while the archive runs from camt.054.001.01 in 2007 through .13 in 2025 — and, exactly as with the statement, what banks deliver is much older: both Nordea camt.054 MIGs implement camt.054.001.02, defined in the 2009 payments maintenance cycle.",[32,175,177],{"id":176},"the-skeleton-a-statement-minus-the-balances","The skeleton: a statement minus the balances",[13,179,180,181,184],{},"The message root is ",[101,182,183],{},"\u003CBkToCstmrDbtCdtNtfctn>",". An illustrative skeleton, built from the elements in Nordea's MIGs (not a complete or valid instance):",[186,187,192],"pre",{"className":188,"code":189,"language":190,"meta":191,"style":191},"language-xml shiki shiki-themes github-light github-dark","\u003CBkToCstmrDbtCdtNtfctn>\n  \u003CGrpHdr>\n    \u003CMsgId>…\u003C\u002FMsgId>            \u003C!-- bank's unique message reference -->\n    \u003CCreDtTm>…\u003C\u002FCreDtTm>\n    \u003CAddtlInf>\u002FCRED\u002F\u003C\u002FAddtlInf> \u003C!-- Nordea: credit-only notification -->\n  \u003C\u002FGrpHdr>\n  \u003CNtfctn>                      \u003C!-- [1..n] one per account -->\n    \u003CId>…\u003C\u002FId>\n    \u003CCreDtTm>…\u003C\u002FCreDtTm>\n    \u003CAcct>\n      \u003CId>\u003CIBAN>…\u003C\u002FIBAN>\u003C\u002FId>   \u003C!-- or \u003COthr> for non-IBAN accounts -->\n    \u003C\u002FAcct>\n    \u003CNtry>                      \u003C!-- [0..n] the notified movements -->\n      \u003CNtryDtls>                \u003C!-- [0..n] -->\n        \u003CTxDtls>…\u003C\u002FTxDtls>      \u003C!-- [0..n] the payload -->\n      \u003C\u002FNtryDtls>\n    \u003C\u002FNtry>\n  \u003C\u002FNtfctn>\n\u003C\u002FBkToCstmrDbtCdtNtfctn>\n","xml","",[101,193,194,202,208,214,220,226,232,238,244,249,255,261,267,273,279,285,291,297,303],{"__ignoreMap":191},[195,196,199],"span",{"class":197,"line":198},"line",1,[195,200,201],{},"\u003CBkToCstmrDbtCdtNtfctn>\n",[195,203,205],{"class":197,"line":204},2,[195,206,207],{},"  \u003CGrpHdr>\n",[195,209,211],{"class":197,"line":210},3,[195,212,213],{},"    \u003CMsgId>…\u003C\u002FMsgId>            \u003C!-- bank's unique message reference -->\n",[195,215,217],{"class":197,"line":216},4,[195,218,219],{},"    \u003CCreDtTm>…\u003C\u002FCreDtTm>\n",[195,221,223],{"class":197,"line":222},5,[195,224,225],{},"    \u003CAddtlInf>\u002FCRED\u002F\u003C\u002FAddtlInf> \u003C!-- Nordea: credit-only notification -->\n",[195,227,229],{"class":197,"line":228},6,[195,230,231],{},"  \u003C\u002FGrpHdr>\n",[195,233,235],{"class":197,"line":234},7,[195,236,237],{},"  \u003CNtfctn>                      \u003C!-- [1..n] one per account -->\n",[195,239,241],{"class":197,"line":240},8,[195,242,243],{},"    \u003CId>…\u003C\u002FId>\n",[195,245,247],{"class":197,"line":246},9,[195,248,219],{},[195,250,252],{"class":197,"line":251},10,[195,253,254],{},"    \u003CAcct>\n",[195,256,258],{"class":197,"line":257},11,[195,259,260],{},"      \u003CId>\u003CIBAN>…\u003C\u002FIBAN>\u003C\u002FId>   \u003C!-- or \u003COthr> for non-IBAN accounts -->\n",[195,262,264],{"class":197,"line":263},12,[195,265,266],{},"    \u003C\u002FAcct>\n",[195,268,270],{"class":197,"line":269},13,[195,271,272],{},"    \u003CNtry>                      \u003C!-- [0..n] the notified movements -->\n",[195,274,276],{"class":197,"line":275},14,[195,277,278],{},"      \u003CNtryDtls>                \u003C!-- [0..n] -->\n",[195,280,282],{"class":197,"line":281},15,[195,283,284],{},"        \u003CTxDtls>…\u003C\u002FTxDtls>      \u003C!-- [0..n] the payload -->\n",[195,286,288],{"class":197,"line":287},16,[195,289,290],{},"      \u003C\u002FNtryDtls>\n",[195,292,294],{"class":197,"line":293},17,[195,295,296],{},"    \u003C\u002FNtry>\n",[195,298,300],{"class":197,"line":299},18,[195,301,302],{},"  \u003C\u002FNtfctn>\n",[195,304,306],{"class":197,"line":305},19,[195,307,308],{},"\u003C\u002FBkToCstmrDbtCdtNtfctn>\n",[13,310,311,312,314,315,317,318,321],{},"The ",[101,313,162],{}," block carries the same furniture as a camt.053 ",[101,316,154],{}," — identification, pagination, sequence numbers, creation time, the account, a transactions summary — with one omission: where the Statement type carries ",[101,319,320],{},"Balance [1..n]",", the Notification type simply has no balance element. That is the entire structural difference at this level, and it's deliberate.",[13,323,324,325,329,330,333,334,337,338,341,342,345,346,170,349,352,353,356,357,360],{},"From the entry downward, the two messages are the ",[326,327,328],"em",{},"same"," structure. In the .001.02 generation, camt.053 and camt.054 both use ",[101,331,332],{},"ReportEntry2"," for the entry, ",[101,335,336],{},"EntryDetails1"," for the details container and ",[101,339,340],{},"EntryTransaction2"," for the transaction — identical types, straight from the MIGs. So everything the ",[21,343,344],{"href":28},"camt.053 walkthrough"," says about ",[101,347,348],{},"\u003CAmt>",[101,350,351],{},"\u003CCdtDbtInd>",", ",[101,354,355],{},"\u003CSts>",", booking versus value date, ",[101,358,359],{},"\u003CAcctSvcrRef>",", the Bank Transaction Code and the Entry → EntryDetails → TransactionDetails nesting applies verbatim here, and I won't repeat it. Two notification-specific observations from Nordea's implementation instead:",[362,363,364,383],"ul",{},[365,366,367,370,371,374,375,378,379,382],"li",{},[16,368,369],{},"Banks often ship camt.054 as two products, not one."," ISO allows a mixed notification — debits, credits, or both. Nordea publishes separate MIGs for a credit notification and a debit notification, and flags the flavor in the GroupHeader's ",[101,372,373],{},"\u003CAddtlInf>",": ",[101,376,377],{},"\u002FCRED\u002F"," for credit-only, ",[101,380,381],{},"\u002FDEBT\u002F"," for debit-only. What you receive is a service decision, so an importer should key on the message content, not on an assumption that one feed carries everything.",[365,384,385,388,389,392,393,396,397,400],{},[16,386,387],{},"The bookkeeping is thorough",": Nordea's notification ",[101,390,391],{},"\u003CId>"," is unique for at least 90 days (built from timestamp, currency and the last four digits of the account), ",[101,394,395],{},"\u003CNtryRef>"," increments by one per entry, and the transaction-level ",[101,398,399],{},"\u003CMsgId>"," in the debit MIG increments per TransactionDetails block. Free ordering and duplicate checks, if you store them.",[32,402,404],{"id":403},"the-reason-it-exists-the-lump-sum-breakdown","The reason it exists: the lump-sum breakdown",[13,406,407,408,411,412,415],{},"Here is the scenario camt.054 earns its keep in. The bank books ",[16,409,410],{},"one collective entry"," on your account for a whole collection — and the statement, correctly, shows one line. Nordea's credit MIG documents the mechanics under the heading \"batch (lump-sum) booking\": the entry-level Bank Transaction Code becomes a batch-level classification, and the individual receipts exist as ",[101,413,414],{},"\u003CTxDtls>"," blocks with their own transaction-level codes. Concretely, from its appendix:",[362,417,418,441,448],{},[365,419,420,421,424,425,428,429,432,433,436,437,440],{},"A Swedish batch credit arrives as an entry classified ",[101,422,423],{},"PMNT-RCDT-NTAV",", and inside it the details resolve to the actual instruments: SEPA credit transfers (",[101,426,427],{},"ESCT","), domestic transfers (",[101,430,431],{},"DMCT","), cross-border credits (",[101,434,435],{},"XBCT","), lockbox deposits (",[101,438,439],{},"LBOX-LBDP",").",[365,442,443,444,447],{},"A Finnish SEPA Core Direct Debit collection arrives as an entry classified ",[101,445,446],{},"PMNT-RDDT-ESDD"," — one credit for the collection run, each collected debit a detail beneath it.",[365,449,450,451,453],{},"The entry's ",[101,452,348],{}," is, in the MIG's own words, \"the total of one or many entry details\" — which hands you the integrity check: sum the details, compare to the entry, and only then clear anything.",[13,455,456,457,460,461,464,465,468],{},"The reconciliation flow that falls out: ",[16,458,459],{},"camt.053 confirms the cash; camt.054 explains it."," The statement's lump-sum entry ties out the position. The notification entry describing the same booking carries the itemisation — per-transaction remittance data (structured creditor references, ",[101,462,463],{},"CINV"," invoice numbers, RF references under ",[101,466,467],{},"SCOR","\u002FISO 11649 in Nordea's implementation) — and cash application clears the individual open items against those details instead of against one opaque total.",[13,470,471,472,476,477,480,481,484,485,488],{},"The same logic runs on the debit side, pointed at your own payments. A ",[21,473,475],{"href":474},"\u002Fblog\u002Fpain-001-structure-and-fields","pain.001"," batch that the bank books collectively is one debit on the statement — and the camt.054 debit notification is where each payment inside it reports back individually. Nordea's debit MIG returns, per TransactionDetails: ",[101,478,479],{},"\u003CPmtInfId>"," (always present when the instruction went through their channel with a payment ID), ",[101,482,483],{},"\u003CInstrId>"," (present if you used it), and ",[101,486,487],{},"\u003CEndToEndId>"," (\"unique reference returned if used by the ordering customer\"). That is the loop closing per payment even though the account moved once.",[13,490,491],{},"One honest nuance from the same MIG: sometimes even the notification doesn't itemise. For card acquiring settlements in Denmark and Sweden (and BankAxept in Norway — where POS settlements are explicitly \"only lump-sum information reported\"), the notification carries a proprietary POS reference and the actual specification of included transactions comes from the external provider. The camt.054 then isn't the breakdown — it's the key to fetch the breakdown somewhere else. Know which of the two you've been sold.",[32,493,495],{"id":494},"what-camt054-doesnt-do","What camt.054 doesn't do",[362,497,498,513,523],{},[365,499,500,503,504,507,508,512],{},[16,501,502],{},"No balances, so no position."," You cannot build a cash position from notifications; there is no opening or closing figure to anchor the arithmetic, and ISO's definition rules one out by design. Positions come from ",[21,505,506],{"href":146},"camt.053 plus intraday camt.052","; global ",[21,509,511],{"href":510},"\u002Fblog\u002Fhow-to-achieve-global-cash-visibility","cash visibility"," is built on statement coverage, not notification coverage.",[365,514,515,518,519,522],{},[16,516,517],{},"Coverage is a service definition."," The statement reports the account's activity; the notification reports what the notification ",[326,520,521],{},"service"," includes. Nordea's MIGs spell this out per country — the credit notification enumerates the included receipt types for Denmark, Finland, Norway and Sweden (down to items like MobilePay and Swish), and the debit notification covers transactions originating from pain.001 plus specific local flows. An entry type outside the list simply never appears in your camt.054, while it will appear on the statement.",[365,524,525,528,529,531],{},[16,526,527],{},"Pending items are possible in the standard, not necessarily in your feed."," ISO's scope allows the notification to report pending as well as booked items; Nordea sends ",[101,530,355],{}," BOOK only. Same discipline as with the statement: check what your bank sends, and filter deliberately.",[32,533,535],{"id":534},"when-you-actually-need-it-and-when-you-dont","When you actually need it — and when you don't",[13,537,538,539,542,543,546,547,550,551,554,555,558],{},"You need a camt.054 feed when the detail you reconcile against doesn't live on the statement. The classic triggers: ",[16,540,541],{},"direct-debit collections"," you present as batches but post per customer; ",[16,544,545],{},"giro \u002F OCR-reference receivables"," where hundreds of consumer payments settle as one credit; ",[16,548,549],{},"card settlement"," streams; ",[16,552,553],{},"lockbox"," deposits; and collectively-booked ",[16,556,557],{},"payment runs"," whose individual invoices your ERP clears one by one. In each case the statement entry is a sum, and cash application without the itemisation degenerates into re-deriving the batch by hand.",[13,560,561,562,564,565,568],{},"You probably don't need it when the detail already reaches you another way. If the bank books singles — or itemises the batch inside the statement's own ",[101,563,414],{}," — the camt.053 carries everything, and a notification feed adds a second copy of the same data plus a deduplication problem. Which of those worlds you live in is the booking arrangement you negotiated with the bank, the exact point the ",[21,566,567],{"href":28},"camt.053 post"," makes about batch versus single booking: it's agreed, not discovered. And on delivery timing — how often and how promptly notifications arrive — the standard says nothing; it's a line in your service agreement, so ask, don't assume.",[32,570,572],{"id":571},"what-usually-goes-wrong","What usually goes wrong",[362,574,575,581,590,601,607],{},[365,576,577,580],{},[16,578,579],{},"Treating it as a statement."," No balances means no completeness anchor. The statement remains the record; the notification annotates it.",[365,582,583,586,587,589],{},[16,584,585],{},"Double-counting."," The same booking arrives in the camt.054 and again in the camt.053. Dedupe deliberately; the natural join key is the bank's entry reference (",[101,588,359],{},", \"will always be reported\" in Nordea's credit MIG) — but the MIGs document each message separately and don't promise the reference is identical across both, so treat cross-message matching as a test case with your bank, not an assumption.",[365,591,592,595,596,170,598,600],{},[16,593,594],{},"Assuming one feed carries both directions."," ",[101,597,377],{},[101,599,381],{}," products exist; subscribe to what you actually need and parse what you actually get.",[365,602,603,606],{},[16,604,605],{},"Assuming full coverage."," The per-country included-transaction lists in the MIG are the contract. If a flow isn't on the list, its detail has to come from somewhere else.",[365,608,609,612],{},[16,610,611],{},"Version drift."," The catalogue is at camt.054.001.14; production channels widely implement .001.02 from 2009. Same caution as for the statement: the bank's MIG and version are the contract, and types change shape between versions.",[13,614,615],{},"The design is coherent once you see the division of labor: one message that is complete and balance-anchored, one that is fast and balance-free, and one — this one — that carries the detail the other two book as a single line. Use the statement to prove the cash, and the notification to explain it.",[617,618],"hr",{},[13,620,621],{},[326,622,623,624,352,627,352,630,633,634,148],{},"See also ",[21,625,626],{"href":23},"bank statement formats: MT940 vs camt.053 vs BAI2",[21,628,629],{"href":28},"the camt.053 field-by-field walkthrough",[21,631,632],{"href":474},"pain.001 structure and fields",", and ",[21,635,636],{"href":146},"how to build a daily cash position",[638,639,640],"style",{},"html .default .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}html.dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}",{"title":191,"searchDepth":204,"depth":204,"links":642},[643,644,645,646,647,648],{"id":34,"depth":204,"text":35},{"id":176,"depth":204,"text":177},{"id":403,"depth":204,"text":404},{"id":494,"depth":204,"text":495},{"id":534,"depth":204,"text":535},{"id":571,"depth":204,"text":572},"connectivity",null,false,"2026-08-03","What camt.054 is — a notification of debits and credits, not a statement — how it differs from camt.053 and camt.052, and the lump-sum breakdown it exists for.","md",[656,659,662,665],{"question":657,"answer":658},"What is the difference between camt.053 and camt.054?","camt.053 is the BankToCustomerStatement: booked entries only, with balance information that the message structure makes mandatory — the complete, balance-anchored record of the account for a period. camt.054 is the BankToCustomerDebitCreditNotification: it notifies single or multiple debit and\u002For credit entries, may include pending as well as booked items, and — in ISO's own words — does not contain balance information. In practice the statement proves the money moved; the notification itemises what moved. The pairing matters most when the statement books one lump-sum entry for a whole collection and the camt.054 carries the individual transactions inside it.",{"question":660,"answer":661},"What is the difference between camt.052 and camt.054?","Both are interim messages next to the end-of-period camt.053, but they answer different questions. camt.052 is the BankToCustomerAccountReport — a picture of the account that can carry entries and balance information (its Balance element is optional, 0..n), typically used intraday to refresh the cash position. camt.054 is entry-centric: it has no balance element at all and exists to notify specific debits and credits with their underlying transaction detail. Use camt.052 to know where the account stands during the day; use camt.054 to know exactly what was booked and what's inside it.",{"question":663,"answer":664},"Can camt.054 replace the camt.053 statement?","No. It carries no balances, so there is nothing to anchor a position or a completeness check against, and its coverage is a service definition, not the account's full activity — Nordea's implementation guides, for example, enumerate per country exactly which transaction types the notification includes. The statement remains the complete record you reconcile against; the notification is the detail channel that explains what individual items sit inside the statement's entries. Run both: camt.053 to prove, camt.054 to explain.",{"question":666,"answer":667},"How do I reconcile a lump-sum credit on the statement using camt.054?","Match the statement entry to the notification entry describing the same booking — amount, booking date and the bank's entry reference are the candidate keys — then run cash application against the TransactionDetails blocks inside the notification entry, each of which carries its own references and remittance information for one collected item. The notification entry's amount is defined as the total of its entry details, so detail-sum-equals-entry is the integrity check to run before clearing anything. And verify with your bank that its entry reference is stable across the two messages: the MIGs document each message separately and don't promise it.",{},true,3.25,"\u002Fblog\u002Fcamt-054-notification-explained","treasury-systems-architecture","camt.054",198,"Scope statements and message structures verified against ISO's Message Definition Report for Bank-to-Customer Cash Management (camt.052\u002F053\u002F054.001.09, Maintenance 2020-2021) and Nordea's camt.054.001.02 credit and debit notification MIGs; the ISO catalogue is at BankToCustomerDebitCreditNotificationV14. Verify against your bank's MIG and version.","on ISO 20022 \u002F bank format changes","editorial-and-factual","reviewed","Tan Gravam","informational",{"title":5,"description":653},[683,686,689,692],{"title":684,"url":685,"accessed":652},"ISO 20022 — Message Definition Report Part 2, Bank-to-Customer Cash Management, Maintenance 2020–2021 (camt.052\u002F053\u002F054.001.09)","https:\u002F\u002Fwww.iso20022.org\u002Fsites\u002Fdefault\u002Ffiles\u002F2020-12\u002FISO20022_MDRPart2_BankToCustomerCashManagement_2020_2021_v1_ForSEGReview.pdf",{"title":687,"url":688,"accessed":652},"Nordea — Corporate Access MIG camt.054.001.02 Credit Notification (v1.9, 2022)","https:\u002F\u002Fwww.nordea.com\u002Fen\u002Fdoc\u002Fcaar-camt-054-001-02-credit-notification-v1.8.pdf",{"title":690,"url":691,"accessed":652},"Nordea — Corporate eGateway MIG camt.054.001.02 Debit Notification (v1.9, 2020)","https:\u002F\u002Fwww.nordea.com\u002Fen\u002Fdoc\u002Fmig-camt-054-001-02-debit-v-1-9-release-2020-11-30-v-02.pdf",{"title":693,"url":694,"accessed":652},"ISO 20022 — Message definitions catalogue and messages archive (camt.054 BankToCustomerDebitCreditNotification)","https:\u002F\u002Fwww.iso20022.org\u002Fiso-20022-message-definitions","blog\u002Fcamt-054-notification-explained",[697,698,699],"treasury","bank-connectivity","integration","text","SCt_9qS3XjY9T6gCdLJEg2D2h6kJ7ELed_qWlFtcGW8",{"related":703,"prev":716,"next":718,"hasOrder":669,"place":721},[704,708,712],{"path":705,"title":706,"description":707},"\u002Fblog\u002Fbai2-file-format-explained","BAI2 File Format: Records, Type Codes and How to Read One","Every BAI2 record explained: the 01–99 hierarchy, balance codes 010\u002F015\u002F040\u002F045, credit vs debit type-code ranges, the funds-type field and control totals.",{"path":709,"title":710,"description":711},"\u002Fblog\u002Fmt101-vs-mt103-vs-mt202","MT101 vs MT103 vs MT202: Which SWIFT Message Does What","MT101 is a corporate's payment instruction, MT103 a bank-to-bank customer transfer, MT202 an interbank transfer. How they differ and what replaced them.",{"path":713,"title":714,"description":715},"\u002Fblog\u002Fiso-20022-payments-pain-001-pain-002","ISO 20022 Payments Explained: pain.001 and pain.002","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.",{"path":28,"title":717,"type":700,"language":650},"camt.053 Structure: Reading the Statement Field by Field",{"path":719,"title":720,"type":700,"language":650},"\u002Fblog\u002Fmt940-format-tags-explained","MT940 Format: The Tags, Line by Line",{"label":722,"position":222,"total":281,"hub":723},"Connectivity","\u002Ftopics\u002Ftreasury-systems-architecture",[],1785752409698]