ZagTrader

Category 5: Securities markets

MT541 Receive Against Payment

Written and maintained by ZagTrader. Last reviewed . How this page is sourced and checked

The MT541 is the instruction an account owner sends to its custodian to receive securities from a counterparty and pay for them at the same time (receive versus payment). Brokers, asset managers and global custodians send it on trade date for every purchase, and it must match the seller’s MT543 at the CSD before anything settles.

Message type
MT541
Category
5
Structure
12 sequences, 72 fields listed

When MT541 is used

An MT541 settles the buyer’s side of a trade. It tells the account servicer which securities to receive into which account, from whom (the delivering agent at the place of settlement), on which date, and how much cash to pay in exchange. The cash leaves the account only when the securities arrive.

The four settlement instructions form a two-by-two grid. Direction: receive or deliver. Cash: free of payment (FOP) or against payment (DVP for a delivery, RVP for a receipt). MT540 is receive free, MT541 receive against payment, MT542 deliver free and MT543 deliver against payment. A trade settles with one instruction from each side: the seller’s custodian receives an MT543 and the buyer’s custodian an MT541, and the CSD matches the two settlement instructions they produce. A free transfer pairs an MT542 with an MT540 in the same way.

The sender is the account owner and the receiver its account servicer. The account owner can be a broker-dealer or an asset manager with an account at its custodian, or a global custodian instructing its local sub-custodian on behalf of a client. The account servicer checks the instruction, turns it into a settlement instruction in the local CSD (or the ICSD) and reports back with MT548 status messages and, once the securities move, the MT545 confirmation.

Send the instruction on trade date, as soon as the trade is confirmed or affirmed, and before the account servicer’s cut-off, which sits ahead of the CSD’s own matching and settlement deadlines. Early instructions give both sides time to fix a mismatch before the intended settlement date. In the US the standard cycle has been T+1 since May 2024, and in the EU late settlement costs cash penalties under the CSD Regulation, so an instruction sent on the evening before settlement date is often already too late. A status reason LATE (market deadline missed) or ADEA (servicer deadline missed) in the MT548 tells you the instruction arrived after a cut-off.

Field 23G says what the message does. NEWM is a new instruction. CANC cancels an instruction sent earlier: put the SEME of the original in 20C::PREV in sequence A1, and repeat the details of the original so the servicer can find it. There is no amendment function: to change a matching field, cancel and send a new instruction with a new reference. Attributes that are not matched, such as a hold or the partial settlement flag, can often be changed with an MT530 transaction processing command where the servicer supports it. PREA pre-advises an instruction that will follow; servicers that support hold and release keep it on hold until a NEWM arrives that quotes it in 20C::PREA (status reason PREA while it waits). Check your servicer’s guide, since support for PREA differs.

The settlement chain sits in sequence E1, one party per occurrence, and is the part most often wrong. PSET is the BIC of the CSD or ICSD where the securities move. DEAG is the counterparty’s participant in that CSD; it is the one party (besides PSET) the network insists on. Further out come the counterparty’s intermediaries and custodian (DEI1, DEI2, DECU) and its client (SELL). Your own side (REAG and BUYR) is optional: the servicer knows it from your safekeeping account. Take the counterparty’s chain from its standing settlement instructions, not from memory.

What the CSD compares. In T2S (the ECB’s matching guide) the mandatory matching fields are: payment type (free or against payment) and direction (receive or deliver), both given by the message type; the ISIN (35B); trade date (98a::TRAD); intended settlement date (98a::SETT); quantity (36B::SETT); the delivering and receiving parties (95a::DEAG and REAG); the CSD of each party (PSET or derived from the account); and, for against payment, the currency and settlement amount (19A::SETT), within a tolerance. Additional matching fields, which must match once either side fills them, are the opt-out indicator (22F::STCO//NOMC) and the cum or ex indicator (22F::TTCO with CCPN or XCPN). Optional matching fields, compared only when both sides send them, are the common reference (20C::COMM), the client of each participant and their securities accounts. Other CSDs use similar lists. When the two sides differ, the MT548 reports NMAT with a reason such as DDAT, DQUA, DSEC, DMON, DEPT or ICAG; see why an instruction is unmatched.

After sending, expect a chain of MT548 messages: accepted (PACK) or rejected (REJT), then matched (MACH) or unmatched (NMAT), then pending (PEND) or failing (PENF) with a reason such as MONY (not enough cash), and finally the MT545 confirmation on settlement. A cancellation request is answered with CAND (cancelled) or CANP (cancellation pending). The settlement lifecycle guide walks through the whole flow.

MT541 format: sequences and fields

Sequence AGeneral InformationMandatory

Identifies the instruction and says what to do with it (new, cancel, pre-advice).

TagQualifierNameStatusFormatMeaning
16RStart of blockMGENLOpens the General Information block.
20CSEMESender's Message ReferenceM:4!c//16xYour own unique reference for this instruction (16 characters at most). The account servicer quotes it in every MT548 status message and in the MT545 confirmation, so it must be unique per instruction. Do not reuse the reference of a cancelled instruction for its replacement.
23GFunction of the MessageM4!c[/4!c]NEWM for a new instruction, CANC to cancel one sent earlier, PREA to pre-advise an instruction that will follow. An optional subfunction marks a copy (COPY), a duplicate (DUPL) or a copy of a duplicate (CODU). Many servicers ask for no subfunction on a live instruction.
98aPREPPreparation Date/TimeOA: :4!c//8!n C: :4!c//8!n6!n E: :4!c//8!n6!n[,3n][/[N]2!n[2!n]]When the message was created, usually as 98C::PREP with date and time.
99BSETTCurrent Settlement Instruction NumberO:4!c//3!nPosition of this instruction in a set of linked instructions (for example 001 of 003), used with pools and linked settlement.
99BTOSETotal of Linked Settlement InstructionsO:4!c//3!nHow many instructions the set contains. If TOSE is present, 99B::SETT must be present too (network error E90).
16SEnd of blockMGENLCloses the General Information block.

Sequence A1LinkagesOptional, repeatable

One occurrence per reference. Field 20C is mandatory in every A1; each 20C row below is one qualifier to choose from. Common qualifiers only.

TagQualifierNameStatusFormatMeaning
16RStart of blockMLINKOpens the Linkages block.
22FLINKLinkage Type IndicatorO:4!c/[8c]/4!cHow this instruction depends on the linked one: WITH (settle together), BEFO (settle this one first), AFTE (settle this one after) or INFO (link for information only). Not every servicer or CSD supports every code.
13aLINKLinked MessageOA: :4!c//3!c B: :4!c/[8c]/30xThe message type of the linked message in option A, for example :13A::LINK//543 when two instructions form a back-to-back.
20CPREVPrevious Message ReferenceM:4!c//16xThe SEME of the instruction you want to cancel. When 23G is CANC, at least one A1 must be present and exactly one of them must carry 20C::PREV (network error E08).
20CRELARelated Message ReferenceM:4!c//16xReference of a related message, for example a linked instruction or the account servicer’s own reference.
20CPREAPreadvice Message ReferenceM:4!c//16xThe SEME of the PREA message that this NEWM follows up. Servicers that hold pre-advised instructions use this link to release them.
20CCOMMCommon ReferenceM:4!c//16xA reference both counterparties agreed on, such as a trade ID from a confirmation platform. In T2S it is an optional matching field: it may be blank on one side, but if both sides send it, it must be equal.
20CPOOLPool ReferenceM:4!c//16xGroups several instructions that belong together, for example the deliveries that make up one large trade.
20CTRRFDeal ReferenceM:4!c//16xThe trade or deal reference from the order or trading system.
36BPAIRQuantity of Financial Instrument to be Paired-offC:4!c//4!c/15dQuantity to pair off against the linked instruction. Allowed only when 22F::SETR is PAIR or TURN (network error C50). 36B::TURN works the same way for a turnaround.
16SEnd of blockMLINKCloses the Linkages block.

Sequence BTrade DetailsMandatory

Dates, price and the security. Common qualifiers only.

TagQualifierNameStatusFormatMeaning
16RStart of blockMTRADDETOpens the Trade Details block.
94aTRADPlace of TradeRepeatableOB: :4!c/[8c]/4!c[/30x] L: :4!c//18!c2!nWhere the trade was done: EXCH with the market identifier code of the exchange, OTCO for over the counter, PRIM or SECM for primary or secondary market.
98aSETTSettlement Date/TimeMA: :4!c//8!n B: :4!c/[8c]/4!c C: :4!c//8!n6!nIntended settlement date as YYYYMMDD. A mandatory matching field in T2S and in other CSDs. Option B with the code WISS (when and if issued) is for securities that do not exist yet.
98aTRADTrade Date/TimeOA: :4!c//8!n B: :4!c/[8c]/4!c C: :4!c//8!n6!n E: :4!c//8!n6!n[,3n][/[N]2!n[2!n]]Trade date. Optional in the standard, but T2S treats it as a mandatory matching field and the European matching standards do too, so send it on every trade. T2S compares the date only, not the time.
90aDEALDeal PriceOA: :4!c//4!c/[N]15d B: :4!c//4!c/3!a15dThe price agreed: 90A with PRCT (percentage of face value, for bonds) or YIEL, 90B with ACTU and a currency (amount per unit, for shares). Not a matching field in T2S, but some markets compare it.
99ADAACNumber of Days AccruedO:4!c//[N]3!nNumber of days of accrued interest, for bonds, as three digits (for example 052).
35BIdentification of the Financial InstrumentM[ISIN1!e12!c] [4*35x]The security: the word ISIN, a space and the ISIN, optionally followed by up to four lines of description. Use the ISIN whenever one exists. A wrong ISIN shows up as reason DSEC in the status message.
22FTTCOTrade Transaction Condition IndicatorRepeatableO:4!c/[8c]/4!cConditions of the trade, for example CCPN or XCPN (cum or ex coupon) and CDIV or XDIV (cum or ex dividend). T2S uses only CCPN and XCPN for matching, as an additional matching field.
11AFXISCurrency to SellO:4!c//3!aAsks the account servicer to buy the settlement currency by selling this currency, to fund the purchase. Use it only when agreed with the servicer and when no standing FX instruction exists.
25DMTCHMatching StatusO:4!c/[8c]/4!cMACH says the trade was already matched outside the CSD, for example by a central counterparty or a matching utility; NMAT says it was not. Mostly used by CSD participants. T2S turns an already matched instruction into two instructions.
70ESPROSettlement Instruction Processing NarrativeO:4!c//10*35xFree-text processing instructions. Many account servicers route any instruction with narrative to manual handling, so keep it out of automated flows.
16SEnd of blockMTRADDETCloses the Trade Details block.

Sequence B1Financial Instrument AttributesOptional

Optional details about the security. The account servicer normally knows them from the ISIN, and some servicers ignore this block. Common qualifiers only.

TagQualifierNameStatusFormatMeaning
16RStart of blockMFIAOpens the Financial Instrument Attributes block.
12aCLASClassification TypeOA: :4!c/[8c]/30x C: :4!c//6!cType of instrument, for example the six-letter CFI code in option C.
11ADENOCurrency of DenominationO:4!c//3!aCurrency in which the security is denominated.
98AMATUMaturity DateO:4!c//8!nMaturity date of a debt instrument.
92AINTRInterest RateO:4!c//[N]15dCurrent coupon rate of a bond, as a percentage.
92ACUFCCurrent FactorO:4!c//[N]15dCurrent pool factor of an amortising instrument such as a mortgage-backed bond. The factor links the face amount (FAMT) to the amortised value (AMOR).
16SEnd of blockMFIACloses the Financial Instrument Attributes block.

Sequence CFinancial Instrument/AccountMandatory

Quantity and the account. Common qualifiers only.

TagQualifierNameStatusFormatMeaning
16RStart of blockMFIACOpens the Financial Instrument/Account block.
36BSETTQuantity of Financial Instrument to be SettledRepeatableM:4!c//4!c/15dQuantity to settle: UNIT for shares and fund units, FAMT (face amount) for bonds, AMOR (amortised value) for factor-bearing debt. It may appear twice only as one FAMT plus one AMOR (network error C71). A mandatory matching field.
95aACOWAccount OwnerOP: :4!c//4!a2!a2!c[3!c] R: :4!c/8c/34xThe owner of the safekeeping account, when the account number alone does not identify it, for example on an omnibus account.
97aSAFESafekeeping AccountMA: :4!c//35x B: :4!c/[8c]/4!c/35xYour securities account at the account servicer, the account the securities are received into. It must be an open account that the servicer holds for you: a wrong or closed account is rejected with reason SAFE.
97aCASHCash AccountOA: :4!c//35x E: :4!c//34xThe cash account to debit for the purchase, when it is not the one linked to the safekeeping account by standing instruction.
94aSAFEPlace of SafekeepingRepeatableOB: :4!c/[8c]/4!c[/30x] C: :4!c//2!a F: :4!c//4!c/4!a2!a2!c[3!c] L: :4!c//18!c2!nWhere the servicer holds the securities, for example :94F::SAFE//NCSD/CSDXAEADXXX (a national CSD) or ICSD with the ICSD’s BIC. Needed only when the servicer holds the security in more than one place.
16SEnd of blockMFIACCloses the Financial Instrument/Account block.

Sequence C1Quantity BreakdownOptional, repeatable

Breaks the quantity into lots, mainly for tax lot or cost reporting. Use it only where the market or servicer asks for it.

TagQualifierNameStatusFormatMeaning
16RStart of blockMBREAKOpens the Quantity Breakdown block.
36BLOTSQuantity of Financial Instrument In The LotO:4!c//4!c/15dQuantity that belongs to this lot.
98aLOTSLot Date/TimeOA: :4!c//8!n C: :4!c//8!n6!n E: :4!c//8!n6!n[,3n][/[N]2!n[2!n]]Date the lot was acquired.
90aLOTSBook/Lot PriceOA: :4!c//4!c/[N]15d B: :4!c//4!c/3!a15dPrice at which the lot was acquired.
16SEnd of blockMBREAKCloses the Quantity Breakdown block.

Sequence DTwo Leg Transaction DetailsOptional

Only for one leg of a two-leg deal: a repo, reverse repo, buy-sell back or securities loan (22F::SETR such as REPU, RVPO, BSBK, SECL). Many servicers ignore it for plain trades. Common qualifiers only.

TagQualifierNameStatusFormatMeaning
16RStart of blockMREPOOpens the Two Leg Transaction Details block.
98aTERMClosing Date/TimeOA: :4!c//8!n B: :4!c/[8c]/4!c C: :4!c//8!n6!nDate of the closing leg, or the code OPEN in option B for an open-ended deal.
20CSECOSecond Leg ReferenceO:4!c//16xReference of the instruction for the other leg.
92aREPORepurchase RateOA: :4!c//[N]15dRepo rate agreed for the deal.
19ATRTETermination Transaction AmountO:4!c//[N]3!a15dAmount due on the closing leg.
16SEnd of blockMREPOCloses the Two Leg Transaction Details block.

Sequence ESettlement DetailsMandatory

Indicators for how the instruction settles. 22F::SETR is the only mandatory field. Common qualifiers only.

TagQualifierNameStatusFormatMeaning
16RStart of blockMSETDETOpens the Settlement Details block.
22FSETRType of Settlement Transaction IndicatorM:4!c/[8c]/4!cWhat kind of business the movement settles: TRAD for a trade, OWNE or OWNI for account transfers (between two account servicers, or within one), PORT for a portfolio move between managers, REPU or RVPO for repos, SECL or SECB for securities lending and borrowing, COLI or COLO for collateral. Some markets compare it during matching, and a code the servicer does not support is rejected with reason SETR.
22FSTCOSettlement Transaction Condition IndicatorRepeatableO:4!c/[8c]/4!cConditions such as NPAR (no partial settlement), PART (partial settlement allowed), NOMC (no automatic market claim, an additional matching field in T2S), SPST (separate settlement of cash and securities) or PHYS (physical delivery). Repeat the field for several conditions.
22FRTGSSecurities Real-Time Gross Settlement IndicatorO:4!c/[8c]/4!cYRTG to settle in the real-time gross process, NRTG to settle in the non-RTGS (batch) process, in markets that offer both.
22FDBNMSettlement Standing Instruction Database IndicatorO:4!c/[8c]/4!cTells the servicer to take the settlement chain from a standing instruction database instead of sequence E1: INTE (the servicer’s own database), BRKR (the broker’s) or VEND (a vendor’s). With DBNM, E1 no longer needs PSET and DEAG, but a SELL party is required (network error E70), and with VEND a vendor in sequence F (D71).
22FSTAMStamp Duty IndicatorO:4!c/[8c]/4!cStamp duty treatment in markets that charge it, usually with a market code list in the data source scheme part of the field.
22FBENEBeneficial Ownership IndicatorO:4!c/[8c]/4!cYBEN or NBEN: whether the beneficial owner changes. Some markets ask for it on free of payment transfers, to tell a change of owner from a move between custodians.
16SEnd of blockMSETDETCloses the Settlement Details block.

Sequence E1Settlement PartiesMandatory, repeatable

One occurrence per party, each holding one 95a party field (the field is mandatory in every occurrence; the qualifier is your choice). Network rules decide which parties must appear across the occurrences. The delivering chain runs from the CSD outwards: PSET, DEAG, DEI1, DEI2, DECU, SELL. Common qualifiers only.

TagQualifierNameStatusFormatMeaning
16RStart of blockMSETPRTYOpens the Settlement Parties block.
95aPSETPlace of SettlementMC: :4!c//2!a P: :4!c//4!a2!a2!c[3!c] Q: :4!c//4*35xThe CSD or ICSD where the securities move, identified by its BIC in option P (for example :95P::PSET//CSDXAEADXXX). Unless 22F::DBNM is used, one E1 must hold PSET and another must hold DEAG (network error E93). The occurrence with PSET must not carry 97a::SAFE (E52). A place of settlement that differs from the counterparty’s gives reason DEPT.
95aDEAGDelivering AgentMP: :4!c//4!a2!a2!c[3!c] Q: :4!c//4*35x R: :4!c/8c/34xThe counterparty’s participant at the place of settlement, the one that delivers the securities: a BIC in option P, or the local participant code in option R with the CSD’s scheme. Mandatory unless 22F::DBNM is used (E93). A mandatory matching field: a wrong agent gives reason ICAG.
95aREAGReceiving AgentMP: :4!c//4!a2!a2!c[3!c] Q: :4!c//4*35x R: :4!c/8c/34xYour side’s participant at the place of settlement, normally your account servicer or its sub-custodian. Not required by the network, but some markets and servicers ask for it, and the counterparty’s instruction will quote it as their REAG.
95aDEI1Deliverer's Intermediary 1MP: :4!c//4!a2!a2!c[3!c] Q: :4!c//4*35x R: :4!c/8c/34xA party between the DEAG and the counterparty’s custodian. If DEI2 is present, DEI1 must be present; if DEI1 is present, DECU must be present (network error E86). DEI2 works the same way one level further out.
95aDECUDeliverer's CustodianMP: :4!c//4!a2!a2!c[3!c] Q: :4!c//4*35x R: :4!c/8c/34xThe counterparty’s custodian, when the DEAG is a sub-custodian acting for it. If DECU is present, SELL must be present too (E86).
95aBUYRBuyerMP: :4!c//4!a2!a2!c[3!c] Q: :4!c//4*35x R: :4!c/8c/34xThe party that ends up with the securities, usually you or your client. Many servicers fill it from the safekeeping account and do not need it.
95aSELLSellerMP: :4!c//4!a2!a2!c[3!c] Q: :4!c//4*35x R: :4!c/8c/34xThe party that delivers the securities: the counterparty’s client. T2S compares the client of each participant as an optional matching field; which MT party carries it depends on the chain and the CSD’s mapping. Required when 22F::DBNM is used (E70).
97aSAFESafekeeping AccountCA: :4!c//35x B: :4!c/[8c]/4!c/35xAccount of the party in the same occurrence, for example the counterparty’s account at the CSD in the DEAG occurrence. Not allowed in the PSET occurrence (E52). In T2S the securities account of each party is an optional matching field.
20CPROCProcessing ReferenceO:4!c//16xA reference for the party in this occurrence, for example the counterparty’s own reference.
70aPACOParty NarrativeO:4!c//4*35xFree text about the party (70C). Usually means manual handling.
16SEnd of blockMSETPRTYCloses the Settlement Parties block.

Sequence E2Cash PartiesOptional, repeatable

Only needed when the cash does not follow the standing instructions linked to the safekeeping account. Many servicers handle E2 manually. Common qualifiers only.

TagQualifierNameStatusFormatMeaning
16RStart of blockMCSHPRTYOpens the Cash Parties block.
95aPAYEPaying InstitutionMP: :4!c//4!a2!a2!c[3!c] Q: :4!c//4*35x R: :4!c/8c/34xBank that pays the cash for the purchase, when not the account servicer itself.
95aDEBTDebtorMP: :4!c//4!a2!a2!c[3!c] Q: :4!c//4*35x R: :4!c/8c/34xThe party whose cash pays for the purchase.
97aCASHCash AccountOA: :4!c//35x E: :4!c//34xCash account of the party in the same occurrence.
16SEnd of blockMCSHPRTYCloses the Cash Parties block.

Sequence E3AmountMandatory, repeatable

One occurrence per amount: each E3 carries one 19A amount qualifier, and the same qualifier cannot appear in two occurrences (network error E87). The 19A rows below are the choices. Common qualifiers only.

TagQualifierNameStatusFormatMeaning
16RStart of blockMAMTOpens the Amount block.
17BACRUAccrued Interest FlagO:4!c//1!aY or N: whether the settlement amount includes accrued interest.
19ASETTSettlement AmountM:4!c//[N]3!a15dThe cash that moves against the securities, in the settlement currency (for a bond: deal amount plus accrued interest, plus or minus costs). One E3 must carry it (network error E92). A mandatory matching field: CSDs accept only a small difference (in T2S EUR 2 up to EUR 100,000 and EUR 25 above, per the ECB’s matching guide); beyond that the instruction stays unmatched with reason DMON, and a different currency gives NCRR.
19ADEALTrade AmountM:4!c//[N]3!a15dPrice times quantity, before costs and accrued interest.
19AACRUAccrued Interest AmountM:4!c//[N]3!a15dAccrued interest on a bond, from the last coupon date to the settlement date.
19AEXECExecuting Broker's AmountM:4!c//[N]3!a15dCommission of the executing broker.
19ARESUResulting AmountO:4!c//[N]3!a15dThe amount after currency conversion, together with 92B::EXCH.
98aVALUValue Date/TimeCA: :4!c//8!n C: :4!c//8!n6!nValue date of the cash. Allowed only for separate settlement of cash and securities: 22F::STCO//SPST must be present and 19A::SETT must be in the same E3 (network error C28).
92BEXCHExchange RateO:4!c//3!a/3!a/15dRate used to convert the amount. If present, 19A::RESU must be in the same E3; without a rate, RESU is not allowed (E62).
16SEnd of blockMAMTCloses the Amount block.

Sequence FOther PartiesOptional, repeatable

Parties that do not take part in the settlement chain but must be named or reported. Common qualifiers only.

TagQualifierNameStatusFormatMeaning
16RStart of blockMOTHRPRTYOpens the Other Parties block.
95aINVEInvestorRepeatableMC: :4!c//2!a P: :4!c//4!a2!a2!c[3!c] Q: :4!c//4*35x R: :4!c/8c/34xThe investor, or in option C the investor’s country. Some markets require it for certain securities or for foreign ownership limits.
95aBRKRBrokerMP: :4!c//4!a2!a2!c[3!c] Q: :4!c//4*35x R: :4!c/8c/34xThe broker that executed the trade, when the servicer needs it for reporting.
95aVENDVendorMP: :4!c//4!a2!a2!c[3!c] Q: :4!c//4*35x R: :4!c/8c/34xThe provider of the standing instruction database, required when 22F::DBNM//VEND is used (network error D71).
97ASAFESafekeeping AccountC:4!c//35xAccount of the party in the same occurrence. Not allowed when the party is a stock exchange (EXCH) or trade regulator (TRRE) (E63).
16SEnd of blockMOTHRPRTYCloses the Other Parties block.

Format notation: n digits, a upper-case letters, c upper-case letters and digits, x any character of the Swift character set, d a decimal number with a comma, ! fixed length, [ ] optional, 4*35x up to 4 lines of 35 characters. M mandatory, O optional, C conditional (a rule decides).

Rules worth knowing

  • Sequences A, B, C and E are mandatory, and E1 must occur at least once. A1, B1, C1, D, E2 and F are optional. E3 (amounts) is mandatory in an against payment instruction. There is no E1a: the party chain is built by repeating E1.
  • Unless 22F::DBNM is present in sequence E, one E1 occurrence must contain 95a::DEAG and another must contain 95a::PSET (network error E93).
  • With 22F::DBNM present, an E1 occurrence must contain 95a::SELL (E70); with 22F::DBNM//VEND, sequence F must contain 95a::VEND (D71).
  • Each party qualifier (BUYR, SELL, DEAG, REAG, DECU, RECU, DEI1, DEI2, REI1, REI2, PSET in E1, the cash parties in E2, and the parties of sequence F except INVE) may appear only once in the message (E84).
  • The chain must be complete going outwards: DEI2 needs DEI1, DEI1 needs DECU, DECU needs SELL; on the receiving side REI2 needs REI1, REI1 needs RECU, RECU needs BUYR (E86).
  • The E1 occurrence that holds PSET cannot also hold 97a::SAFE (E52).
  • When 23G is CANC, at least one A1 must be present and 20C::PREV must appear in exactly one of them (E08).
  • One E3 occurrence must contain the settlement amount 19A::SETT (E92). No amount qualifier may appear in more than one E3 (E87).
  • A value date (98a::VALU) is allowed only with 22F::STCO//SPST and with 19A::SETT in the same E3 (C28). An exchange rate (92B::EXCH) requires 19A::RESU in the same E3, and RESU is not allowed without a rate (E62).
  • 36B::SETT may appear at most twice, and then once with FAMT and once with AMOR (C71). A quantity in sequence A1 (36B::PAIR or TURN) is allowed only with 22F::SETR//PAIR or TURN (C50). If 99B::TOSE is present, 99B::SETT must be present (E90).
  • The rule numbers (C1, C2 and so on) differ between MT540, MT541, MT542 and MT543 and between standards releases, so search for the error code, not the rule number. Newer releases added further rules, for example on the LEI options of 94a and 95a.

MT541 example

A London asset manager (FUNDGB2LXXX) bought EUR 500,000 nominal of a 4% bond (XS00ZAGT0013) at 101.25% from a broker (BRKRGB2LXXX). It instructs its custodian CUSTGB2LXXX to receive the bond at the ICSD (ICSDLULLXXX) against EUR 509,138.89: the deal amount of EUR 506,250.00 plus 52 days of accrued interest, EUR 2,888.89 (30/360 basis).

{1:F01FUNDGB2LAXXX0000000000}{2:I541CUSTGB2LXXXXN}{4:
:16R:GENL
:20C::SEME//FM541261020007
:23G:NEWM
:98C::PREP//20261020141500
:16R:LINK
:20C::TRRF//OMS-77815
:16S:LINK
:16S:GENL
:16R:TRADDET
:98A::TRAD//20261020
:98A::SETT//20261022
:90A::DEAL//PRCT/101,25
:99A::DAAC//052
:35B:ISIN XS00ZAGT0013
4 PCT ZAGTRADER DEMO NOTES 2031
:16S:TRADDET
:16R:FIAC
:36B::SETT//FAMT/500000,
:97A::SAFE//FM-SAFE-0042
:97A::CASH//FM-EUR-0042
:16S:FIAC
:16R:SETDET
:22F::SETR//TRAD
:16R:SETPRTY
:95P::DEAG//BRKRGB2LXXX
:97A::SAFE//12345
:16S:SETPRTY
:16R:SETPRTY
:95P::REAG//CUSTGB2LXXX
:97A::SAFE//67890
:16S:SETPRTY
:16R:SETPRTY
:95P::PSET//ICSDLULLXXX
:16S:SETPRTY
:16R:AMT
:17B::ACRU//Y
:19A::SETT//EUR509138,89
:16S:AMT
:16R:AMT
:19A::DEAL//EUR506250,
:16S:AMT
:16R:AMT
:19A::ACRU//EUR2888,89
:16S:AMT
:16S:SETDET
-}
Decode this example in the parser

Line by line

LineWhat it says
{1:F01FUNDGB2LAXXX0000000000}{2:I541CUSTGB2LXXXXN}{4:Basic header (sender FUNDGB2LXXX) and application header (input MT541 to CUSTGB2LXXX).
:16R:GENL
:20C::SEME//FM541261020007Sender’s reference.
:23G:NEWMA new instruction.
:98C::PREP//20261020141500
:16R:LINKOptional linkage block.
:20C::TRRF//OMS-77815Deal reference from the order system, kept for reconciliation.
:16S:LINK
:16S:GENL
:16R:TRADDET
:98A::TRAD//20261020Trade date.
:98A::SETT//20261022Intended settlement date.
:90A::DEAL//PRCT/101,25Price as a percentage of face value.
:99A::DAAC//05252 days of accrued interest.
:35B:ISIN XS00ZAGT0013The bond, by ISIN (made up, valid check digit).
4 PCT ZAGTRADER DEMO NOTES 2031
:16S:TRADDET
:16R:FIAC
:36B::SETT//FAMT/500000,Face amount 500,000: bonds settle in FAMT, not UNIT.
:97A::SAFE//FM-SAFE-0042The asset manager’s securities account at the custodian.
:97A::CASH//FM-EUR-0042The EUR cash account to debit.
:16S:FIAC
:16R:SETDET
:22F::SETR//TRADSettlement of a trade.
:16R:SETPRTY
:95P::DEAG//BRKRGB2LXXXDelivering agent: the selling broker’s participant at the ICSD. Mandatory (E93).
:97A::SAFE//12345The broker’s account at the ICSD.
:16S:SETPRTY
:16R:SETPRTY
:95P::REAG//CUSTGB2LXXXReceiving agent: the custodian itself, as ICSD participant.
:97A::SAFE//67890The custodian’s account at the ICSD.
:16S:SETPRTY
:16R:SETPRTY
:95P::PSET//ICSDLULLXXXPlace of settlement: the ICSD.
:16S:SETPRTY
:16R:AMT
:17B::ACRU//YThe settlement amount includes accrued interest.
:19A::SETT//EUR509138,89Settlement amount: 506,250.00 + 2,888.89. Mandatory (E92) and a matching field.
:16S:AMT
:16R:AMT
:19A::DEAL//EUR506250,Trade amount: 500,000 x 101.25%.
:16S:AMT
:16R:AMT
:19A::ACRU//EUR2888,89Accrued interest: 500,000 x 4% x 52 / 360.
:16S:AMT
:16S:SETDET
-}

The broker’s custodian sends the mirror image, an MT543 with REAG CUSTGB2LXXX and the same ISIN, dates, face amount and settlement amount.

All BICs, accounts, the ISIN and the bond name are made up. The ISIN carries a valid check digit.

Common errors and rejects

  1. Network reject: no DEAG or no PSET (E93)

    Without 22F::DBNM, one E1 must name the delivering agent and another the place of settlement. The network rejects the message otherwise. Put each party in its own E1, and keep 97a::SAFE out of the PSET occurrence (E52).

  2. Unknown safekeeping or cash account (REJT, SAFE)

    The 97a::SAFE in sequence C is not an open account the custodian holds for you, so the instruction is rejected with reason SAFE. A cash account in 97a::CASH that does not belong to the same client is a common variant of the same problem.

    How to fix it
  3. Wrong place of settlement (DEPT)

    The seller settles at a different CSD or ICSD from the one in your PSET, or the BIC is wrong. The instruction is rejected or stays unmatched with reason DEPT. Check the seller’s standing settlement instructions and your custodian’s market guide, especially when one side settles at a CSD and the other at an ICSD.

    How to fix it
  4. Settlement amount mismatch (NMAT, DMON)

    The most common bond mismatch: one side computed accrued interest with a different day count or number of days, or used the clean amount. If the difference is above the CSD’s tolerance, the instruction stays NMAT with reason DMON. Recalculate from the confirmation and re-instruct the side that is wrong.

    How to fix it
  5. Wrong quantity type or SETR code (DQUA, SETR)

    Sending a bond quantity as UNIT instead of FAMT gives DQUA. A 22F::SETR code that the market does not support, or that differs from the seller’s where it is compared, gives reason SETR.

    How to fix it
  6. Late instruction or not enough cash (LATE, MONY)

    An instruction received after the cut-off is reported with LATE or ADEA. A matched receipt that cannot be funded on settlement date goes pending with MONY until cash is credited.

    How to fix it

MT541 in ISO 20022

In ISO 20022 one message, sese.023 (Securities Settlement Transaction Instruction), replaces all four instructions. The direction and the payment type become data elements: an MT541 is a sese.023 with SttlmTpAndAddtlParams/SctiesMvmntTp = RECE and SttlmTpAndAddtlParams/Pmt = APMT. The status message MT548 becomes sese.024, the confirmation MT545 becomes sese.025, and a cancellation is a separate message, sese.020 (Securities Transaction Cancellation Request), instead of 23G CANC.

Securities messages (category 5) were not part of the November 2025 end of MT/MX coexistence for cross-border payments, and MT540 to MT543 remain in use on FIN alongside their ISO 20022 equivalents. T2S and the CSD participants connected directly to it work in ISO 20022 (sese and semt messages); many custodians and CSDs accept both formats and translate between them. See how the securities migration differs from payments.

MT541 questions

What is the difference between MT541 and MT540?
Both receive securities. An MT541 pays cash in exchange (receive against payment), an MT540 receives free of payment, with no cash moving through the settlement system, for example on a transfer between custodians.
Which MT541 fields must match the seller’s MT543?
In T2S: the ISIN, trade date, settlement date, quantity, the delivering and receiving agents, the CSD of each, and the settlement currency and amount (within a small tolerance). The direction and payment type are given by the two message types. Other CSDs use very similar lists.
How do I quote a bond quantity in an MT541?
Use the face amount with the FAMT code, for example :36B::SETT//FAMT/500000,. UNIT is for shares and fund units. For amortising debt some markets also need AMOR in a second 36B::SETT.
Does the MT541 settlement amount include accrued interest?
Yes for bonds: 19A::SETT is the cash that actually moves, so it includes accrued interest and any costs. You can show the parts in separate E3 blocks (19A::DEAL, 19A::ACRU) and flag it with 17B::ACRU//Y.
What confirms that an MT541 settled?
An MT545 receive against payment confirmation from the custodian, after MT548 status messages reporting acceptance, matching and any pending reasons.
What is the ISO 20022 equivalent of MT541?
sese.023 with the securities movement type RECE and payment type APMT.

The trading side of the trade: FIX

Before a settlement instruction is sent, the trade is usually executed, allocated and confirmed over FIX, and the instruction must copy what was agreed there. Read those messages on the free ZagTrader FIX Parser:

All MT messages · Category 5 messages · ISO 20022 messages · Codes · Troubleshooting