2/18/2017 Field72orField79:SendertoReceiverInformation/NarrativeStandardsMTNovember2016UsageGuidelines

Field72orField79:SendertoReceiver
Information/Narrative
Field72orfield79

FORMAT 6*35x(Field72)/35*50x(Field79)

DEFINITION Forthepurposesofthisguideline,thisfielddetailsthereasonforthereturnorrejection.

VALUES Thefollowingcodewordsmustbeusedtoprovidedetailsonthereturn:

Line1 /REJT/ 2!n[1!a][/2c] M /REJT/meansarejectandis
followedbytheidentificationofthe
or
fieldcausingtherejector
/RETN/
/RETN/meansareturnandis
followedbytheidentificationofthe
fieldcausingthereturn.

Line2 /2!c2!n/ [29x](forfield72) M ReasonCode(seebelow),

optionallyfollowedbyatext
or
descriptionoftheprecedingreason
[44x](forfield79) code.

Line3 /MREF/ 16x M Sender'sReference,thatis,field20

oftheoriginalmessage
(TransactionReferenceNumberor
FileReference).

Line4 /TREF/ 16x O TransactionReference,thatis,field

21oftheactualtransaction,for
exampleanMT102orMT104.

Line5 /CHGS/ 3!a15d O ISOcurrencycodeandcharges

amount.Thismaycontainrelevant,
leviedreject/returncharges,thatis,
chargesthathavebeenappliedto
therejected/returnedtransaction
(forexample,deductedfromthe
returnedprincipal).

Line6 /TEXT/ 29x(forfield72) O Somefurthernarrativedetails.

or
44x(forfield79)

ThefieldcausingtheRejectorReturnisidentifiedby:

Field Description

2!n Thefieldtagofthefieldinwhichtheerroroccurred(forexample,32denotestheerror
occurredinfieldwithtag32).

[1!a] Ifapplicable,thisgivestheletteroptionoftheprecedingfieldtaginwhichtheerror
occurred,(forexample,Aafter32meansfield32A).

[/2c] Ifafieldtagappearsmorethanonceinamessagetype,thisalphanumericcodedetails
thesequenceinwhichtheerroroccurred,(forexample,/Cafter32Ameanstheerror
occurredinfield32AofsequenceC,59/B1denotestheerroroccurredinfield59of
sequenceB1).

https://www2.swift.com/uhbonline/books/public/en_uk/usug_20160722/con_31032.htm 1/3
2/18/2017 Field72orField79:SendertoReceiverInformation/NarrativeStandardsMTNovember2016UsageGuidelines

Theactualreasoncodemustbeoneofthefollowingcodes(ErrorcodeT80):

Code Type Reason

AC01 AccountNumber Formatoftheaccountnumberspecifiedisnotcorrect.

AC02 AccountNumber Formatoftheaccountnumberspecifiedisnonnumeric.

AC03 AccountNumber Formatoftheaccountnumberspecifiedisnotvalidforlocal

sort/nationalclearingcode.

AC04 AccountNumber Accountnumberspecifiedhasbeenclosedonthereceiver's

books.

AC05 AccountNumber Accountnumberspecifiedisnotavalidaccountatthe

AccountWithInstitution.

AC06 AccountNumber Accountspecifiedisblocked,prohibitingpostingof

transactionsagainstit.

AM01 Amount Specifiedtransaction/messageamountisequaltozero.

AM02 Amount Specifiedtransaction/messageamountisgreaterthan

allowedmaximum.

AM03 Amount Specifiedtransaction/messageamountisinanon

processablecurrencyoutsideofexistingagreement.

AM04 Amount Amountoffundsavailabletocoverspecified

transaction/messageamountisinsufficient.

AM05 Amount Thistransaction/messageappearstohavebeenduplicated.

AM06 Amount Specifiedtransactionamountislessthanagreedminimum.

AM07 Amount Amountspecifiedintransaction/messagehasbeenblocked

byregulatoryauthorities.

AM08 Amount Specifiedchargesamountisnotasagreedbetweensender

andreceiver.

BE01 Beneficiary Specificationofbeneficiaryisnotconsistentwithassociated

accountnumber.

BE02 Beneficiary Beneficiaryspecifiedisnotknownatassociatedsort/national

clearingcode.

BE03 Beneficiary Beneficiaryspecifiednolongerexistsinthebooks.

BE04 Beneficiary Specificationofbeneficiaryaddress,whichisrequiredfor

payment,ismissing/notcorrect. Helpful?

BE05 Beneficiary Partywhoinitiatedthetransaction/messageisnot

recognisedbythebeneficiary.

AG01 Agreement Noagreementisonfileatthereceiverforaffecting

associatedtransaction/message.

AG02 Agreement BankOperationcodespecifiedinthetransaction/messageis

notvalidforreceiver.

DT01 Date Invaliddate(forexample,wrongsettlementdate).

https://www2.swift.com/uhbonline/books/public/en_uk/usug_20160722/con_31032.htm 2/3
2/18/2017 Field72orField79:SendertoReceiverInformation/NarrativeStandardsMTNovember2016UsageGuidelines

Code Type Reason

MS01 General Reasonhasnotbeenspecifiedduetosensitivities.

PY01 Party UnknownAccountWithInstitution.

RF01 Reference Transactionreferenceisnotuniquewithinthemessage.

RC01 RoutingCode Routingcodespecifiedinthetransaction/messagehasan

incorrectformat.

RC02 RoutingCode Routingcodespecifiedinthetransaction/messageisnot

numeric.

RC03 RoutingCode Routingcodespecifiedinthetransaction/messageisnot

validforlocalclearing.

RC04 RoutingCode Routingcodespecifiedinthetransaction/messagerefersto

aclosedbranch.

RR01 RegulatoryRequirement Specificationoftheorderingcustomer'saccountorunique

identificationneededforreasonsofregulatoryrequirements
isinsufficientormissing.

RR02 RegulatoryRequirement Specificationoftheorderingcustomer'snameand/or

addressneededforregulatoryrequirementsisinsufficientor
missing.

RR03 RegulatoryRequirement Specificationofthebeneficiarycustomer'snameand/or

addressneededforregulatoryrequirementsisinsufficientor
missing.

TM01 ReceiptTime Associatedtransaction/messagewasreceivedafteragreed

processingcutofftime.

X1!c2!n Bilateral Referstoareject/returncodewhosespecificationand

meaninghasbeenbilaterallyagreedtobySendingand
Receivingparties.

Helpful?

https://www2.swift.com/uhbonline/books/public/en_uk/usug_20160722/con_31032.htm 3/3