Transcription
Usage GuidelineDomestic and International Credit Transfer pain.001.001.03 InsideBusiness PaymentsInsideBusiness PaymentsThis document describes a usage guideline restricting the base message MX pain.001.001.03. You can also consult thisinformation online.Published by ING and generated by MyStandards.06 January 2017
Usage GuidelineTable of Contents.Message Functionality . 31Restriction summary . 42Structure . 53Message Building Blocks . 64Message Components . 95Message Datatypes . 134.Legal Notices . 1742Domestic and International Credit Transfer - pain.001.001.03 InsideBusiness Payments - InsideBusiness Payments
Message FunctionalityMessage FunctionalityOverviewThis Implementation guideline complies with the international definitions for contentand use of an ISO20022 pain.001.001.03 Customer Credit Transfer Initiation and Common Global Implementation - Market Practice (CGI-MP) Credit Transfer Initiation recommendations.This version is specifically for the InsideBusiness Payments channel with initiatingING accounts held at ING network and third party banks.The files sent to ING Bank must be in UTF-8 format, using only the characters included in ISO-8859-1.The restriction rules in the document can be interpreted as follows:- Mandatory: Field must be used, otherwise payment gets rejected- Ignored: Field can be provided, but ING does not act upon it- Removed: Field must be left out, otherwise the payment gets rejected- Details below: On a lower hierarchical level more instructions can be foundThe utmost care has been taken to make sure the information in this publication iscorrect. However, ING by no means can be held liable for any loss or damage incurreddue to any incorrect or incomplete information mentioned in this publication.More information can be obtained via your ING local account managerOutlineThe InsideBusiness Payments / Domestic and International Credit Transfer - pain.001.001.03 InsideBusiness Payments message is composed of 2 building blocksa. GroupHeaderSet of characteristics shared by all individual transactions included in the message.b. PaymentInformationSet of characteristics that applies to the debit side of the payment transactions included in the credit transfer initiation.06 January 20173
Usage Guideline1Restriction summaryThis Usage Guideline restricts the pain.001.001.03 message.Restriction TypeSee pageRemoved elements11, 81, 82, 83, 83, 84, 84, 84, 117,160, 160, 171, 171, 172, 172, 172, 172Make mandatory40, 40, 46, 72, 72, 72, 76, 76, 94,94Reduce Multiplicity105, 113, 114Ignore9, 13, 14, 14, 15, 15, 17, 17, 17,17, 17, 17, 17, 18, 18, 18, 33, 34,35, 36, 36, 37, 37, 38, 38, 39, 41,42, 42, 43, 43, 44, 53, 53, 54, 54,54, 56, 56, 56, 56, 56, 57, 57, 58,58, 60, 60, 60, 60, 60, 60, 63, 64,69, 71, 71, 71, 71, 71, 73, 73, 74,74, 74, 74, 74, 74, 74, 75, 75, 75,75, 75, 77, 77, 78, 78, 78, 78, 78,79, 79, 79, 79, 80, 86, 87, 89, 90,91, 96, 101, 101, 101, 101, 101, 101, 101,101, 101, 102, 102, 102, 102, 102, 102, 102,102, 102, 102, 103, 103, 103, 103, 104, 104,104, 104, 104, 104, 104, 105, 119, 120, 121,121, 122, 167, 167, 167, 167, 168, 168, 168,168, 168, 169, 169, 169, 169, 169, 170, 170,170, 170, 170, 171, 171Text rules19, 20, 21, 25, 25, 26, 26, 46, 47,69, 69, 69, 69, 70, 70, 98, 98, 99,99, 103, 103, 103, 105, 106, 108, 108Conditional rulesn.a.Fixed values58, 58, 85Truncatesn.a.Comments17, 25, 27, 35, 44, 64, 80, 86, 86,87, 90, 105, 105, 114, 117Annotationsn.a.Changed datatypesn.a.Extensionsn.a.Synonymsn.a.Other restrictions4Domestic and International Credit Transfer - pain.001.001.03 InsideBusiness Payments - InsideBusiness Payments
Structure2StructureRemoved -IndexIgnored -!Details below -Message y - R[x.x] Repeatability[details]GroupHeader XML Tag OrMult.UsageGuidelinesPage CstmrCdtTrfInitn [1.1] GrpHdr [1.1]66!1.1MessageIdentification MsgId [1.1]621.2CreationDateTime CreDtTm [1.1]621.3Authorisation Authstn [0.2]621.6NumberOfTransactions NbOfTxs [1.1]631.7ControlSum CtrlSum [0.1]631.8InitiatingParty InitgPty [1.1]1.9ForwardingAgent FwdgAgt [0.1]64 PmtInf ionIdentification PmtInfId [1.1]2.2PaymentMethod PmtMtd [1.1]2.3BatchBooking BtchBookg [0.1]2.4NumberOfTransactions NbOfTxs [0.1]862.5ControlSum CtrlSum [0.1]862.6PaymentTypeInformation PmtTpInf [0.1]!862.17RequestedExecutionDate ReqdExctnDt [1.1]!872.18PoolingAdjustmentDate PoolgAdjstmntDt [0.1]872.19Debtor Dbtr [1.1]872.20DebtorAccount DbtrAcct [1.1]882.21DebtorAgent DbtrAgt [1.1]882.22DebtorAgentAccount DbtrAgtAcct [0.1]892.23UltimateDebtor UltmtDbtr [0.1]892.24ChargeBearer ChrgBr [0.1]2.25ChargesAccount ChrgsAcct [0.1]902.26ChargesAccountAgent ChrgsAcctAgt [0.1]902.27CreditTransferTransactionInformation CdtTrfTxInf [1.*]9106 January 201785!85!90!5
Usage Guideline3Message Building BlocksNoteThe following chapter identifies the building blocks of the CustomerCreditTransferInitiationV03 message definition.Usage Guideline on Root Node on pain.001.001.03/– ING Rule - Number of Transactions GrpHdr:For each [CustomerCreditTransferInitiationV03], [GroupHeader/NumberOfTransactions] value must be equal to the number of occurrences of mation] on pain.001.001.03/– ING Rule - Remittance Infomation MutuallyExclusive:For each [CustomerCreditTransferInitiationV03], the following elements are mutually exclusive: mation/RemittanceInformation/Unstructured] , mation/RemittanceInformation/Structured] and all may be absent on pain.001.001.03/– ING Rule - BIC or Other are mutually exclusive Ultimate Debtor:For each [CustomerCreditTransferInitiationV03], the following elements are mutually exclusive: OrganisationIdentification/BICOrBEI] , OrganisationIdentification/Other] and all may be absent on pain.001.001.03/– ING Rule - BIC or Other are mutually exclusive:For each [CustomerCreditTransferInitiationV03], the following elements are mutually exclusive: sationIdentification/BICOrBEI] , sationIdentification/Other] and all may be absent3.1GroupHeaderXML Tag: GrpHdrPresence: [1.1]Definition: Set of characteristics shared by all individual transactions included in the message.6Domestic and International Credit Transfer - pain.001.001.03 InsideBusiness Payments - InsideBusiness Payments
Message Building BlocksThe GrpHdr block contains the following elements (see datatype "GroupHeader32 1" on page 61for details)Removed Index3.2Ignored -!Details below -Message ItemMandatory - R[x.x] Repeatability[details] XML Tag OrMult.UsageGuidelinesPage1.1MessageIdentification MsgId [1.1]621.2CreationDateTime CreDtTm [1.1]621.3Authorisation Authstn [0.2]621.6NumberOfTransactions NbOfTxs [1.1]631.7ControlSum CtrlSum [0.1]631.8InitiatingParty InitgPty [1.1]1.9ForwardingAgent FwdgAgt [0.1]63!64PaymentInformationXML Tag: PmtInfPresence: [1.*]Definition: Set of characteristics that applies to the debit side of the payment transactions included inthe credit transfer initiation.06 January 20177
Usage GuidelineThe PmtInf block contains the following elements (see datatype "PaymentInstructionInformation3 1"on page 80 for details)Removed -Ignored -Index8!Details below -Mandatory - R[x.x] Repeatability[details]Message Item XML Tag ntification PmtInfId [1.1]2.2PaymentMethod PmtMtd [1.1]2.3BatchBooking BtchBookg [0.1]2.4NumberOfTransactions NbOfTxs [0.1]862.5ControlSum CtrlSum [0.1]862.6PaymentTypeInformation PmtTpInf [0.1]!862.17RequestedExecutionDate ReqdExctnDt [1.1]!872.18PoolingAdjustmentDate PoolgAdjstmntDt [0.1]872.19Debtor Dbtr [1.1]872.20DebtorAccount DbtrAcct [1.1]882.21DebtorAgent DbtrAgt [1.1]882.22DebtorAgentAccount DbtrAgtAcct [0.1]892.23UltimateDebtor UltmtDbtr [0.1]892.24ChargeBearer ChrgBr [0.1]2.25ChargesAccount ChrgsAcct [0.1]902.26ChargesAccountAgent ChrgsAcctAgt [0.1]902.27CreditTransferTransactionInformation CdtTrfTxInf [1.*]918585!!!Domestic and International Credit Transfer - pain.001.001.03 InsideBusiness Payments - InsideBusiness Payments8590
Message Components4Message ComponentsNote4.1The following chapter identifies the CustomerCreditTransferInitiationV03 message components.AccountIdentification4ChoiceDefinition: Specifies the unique identification of an account as assigned by the account servicer.Removed -Ignored -Index!Details below -Mandatory - R[x.x] Repeatability[details]Message Item XML Tag OrMult.UsageGuidelinesPage1.1.1IBAN IBAN {Or[1.1]91.1.2Other Othr Or}[1.1]9Used in element(s)"Identification" on page 164.1.1IBANXML Tag: IBANPresence: [1.1]Definition: International Bank Account Number (IBAN) - identifier used internationally by financial institutions to uniquely identify the account of a customer. Further specifications of the format and content ofthe IBAN can be found in the standard ISO 13616 "Banking and related financial services - InternationalBank Account Number (IBAN)" version 1997-10-01, or later revisions.Datatype: "IBAN2007Identifier" on page 153Usage Guideline details This /Identification/IBAN) will be ignored by the Receiver.4.1.2OtherXML Tag: OthrPresence: [1.1]Definition: Unique identification of an account, as assigned by the account servicer, using an identification scheme.06 January 20179
Usage GuidelineThe Othr block contains the following elements (see datatype "GenericAccountIdentification1" onpage 56 for details)Removed -Ignored -Index4.2!Details below -Mandatory - R[x.x] Repeatability[details]Message Item XML Tag OrMult.UsageGuidelinesPage1.1.3Identification Id [1.1]571.1.4SchemeName SchmeNm [0.1]571.1.7Issuer Issr [0.1]57AccountSchemeName1ChoiceDefinition: Sets of elements to identify a name of the identification schemeRemoved -Ignored -Index!Details below -Mandatory - R[x.x] Repeatability[details]Message Item XML Tag OrMult.UsageGuidelines1.1.5Code Cd {Or[1.1]101.1.6Proprietary Prtry Or}[1.1]10Used in element(s)"SchemeName" on page 574.2.1CodeXML Tag: CdPresence: [1.1]Definition: Name of the identification scheme, in a coded form as published in an external list.Datatype: "ExternalAccountIdentification1Code" on page 1504.2.2ProprietaryXML Tag: PrtryPresence: [1.1]Definition: Name of the identification scheme, in a free text form.Datatype: "Max35Text" on page 1584.3AmountType3ChoiceDefinition: Specifies the amount of money to be moved between the debtor and creditor, before deduction of charges, expressed in the currency as ordered by the initiating party.10PageDomestic and International Credit Transfer - pain.001.001.03 InsideBusiness Payments - InsideBusiness Payments
Message ComponentsRemoved -Ignored -Index!Details below -Mandatory - R[x.x] Repeatability[details]Message Item XML Tag OrMult.UsageGuidelinesPage2.43InstructedAmount InstdAmt {Or[1.1]112.44EquivalentAmount EqvtAmt Or}[1.1]11Used in element(s)"Amount" on page 334.3.1InstructedAmountXML Tag: InstdAmtPresence: [1.1]Definition: Amount of money to be moved between the debtor and creditor, before deduction ofcharges, expressed in the currency as ordered by the initiating party.Datatype: "ActiveOrHistoricCurrencyAndAmount" on page 1344.3.2EquivalentAmountXML Tag: EqvtAmtPresence: [1.1]Definition: Amount of money to be moved between the debtor and creditor, expressed in the currency ofthe debtor's account, and the currency in which the amount is to be moved.The EqvtAmt block contains the following elements (see datatype "EquivalentAmount2" on page 50for details)Removed -Ignored -Index!Details below -Mandatory - R[x.x] Repeatability[details]Message Item XML Tag OrMult.UsageGuidelinesPage2.45Amount Amt [1.1]502.46CurrencyOfTransfer CcyOfTrf [1.1]51Usage Guideline details This unt) is removed.4.4Authorisation1ChoiceDefinition: Provides the details on the user identification or any user key that allows to check if the initiating party is allowed to issue the transaction.06 January 201711
Usage GuidelineRemoved -Ignored -Index!Details below -Mandatory - R[x.x] Repeatability[details]Message Item XML Tag OrMult.UsageGuidelinesPage1.4Code Cd {Or[1.1]121.5Proprietary Prtry Or}[1.1]12Used in element(s)"Authorisation" on page 624.4.1CodeXML Tag: CdPresence: [1.1]Definition: Specifies the authorisation, in a coded form.Datatype: "Authorisation1Code" on page 1374.4.2ProprietaryXML Tag: PrtryPresence: [1.1]Definition: Specifies the authorisation, in a free text form.Datatype: "Max128Text" on page Definition: Set of elements used to uniquely and unambiguously identify a financial institution or abranch of a financial institution.Removed -Ignored -Index!Details below -Message ItemMandatory - R[x.x] Repeatability[details] XML Tag ntification FinInstnId [1.1]126.1.25BranchIdentification BrnchId [0.1]13Used in element(s)"ChargesAccountAgent" on page 90, "CreditorAgent" on page 38, "DebtorAgent" on page 88,"ForwardingAgent" on page 64, "IntermediaryAgent1" on page 35, "IntermediaryAgent2" onpage 36, "IntermediaryAgent3" on page 374.5.1FinancialInstitutionIdentificationXML Tag: FinInstnIdPresence: [1.1]12PageDomestic and International Credit Transfer - pain.001.001.03 InsideBusiness Payments - InsideBusiness Payments
Message ComponentsDefinition: Unique and unambiguous identification of a financial institution, as assigned under an internationally recognised or proprietary identification scheme.The FinInstnId block contains the following elements (see datatype "FinancialInstitutionIdentification7"on page 52 for details)Removed -Ignored -Index!Details below -Mandatory - R[x.x] Repeatability[details]Message Item XML Tag OrMult.UsageGuidelinesPage6.1.1BIC BIC [0.1]536.1.2ClearingSystemMemberIdentification ClrSysMmbId [0.1]536.1.7Name Nm [0.1]546.1.8PostalAddress PstlAdr [0.1]546.1.19Other Othr [0.1]564.5.2BranchIdentificationXML Tag: BrnchIdPresence: [0.1]Definition: Identifies a specific branch of a financial institution.Usage: This component should be used in case the identification information in the financial institutioncomponent does not provide identification up to branch level.The BrnchId block contains the following elements (see datatype "BranchData2" on page 13 for details)Removed -Ignored -Index!Details below -Mandatory - R[x.x] Repeatability[details]Message Item XML Tag OrMult.UsageGuidelinesPage6.1.26Identification Id [0.1]146.1.27Name Nm [0.1]146.1.28PostalAddress PstlAdr [0.1]14Usage Guideline details This ranchIdentification) will be ignored by the Receiver.4.6BranchData2Definition: Information that locates and identifies a specific branch of a financial institution.06 January 201713
Usage GuidelineRemoved -Ignored -Index!Details below -Mandatory - R[x.x] Repeatability[details]Message Item XML Tag OrMult.UsageGuidelines6.1.26Identification Id [0.1]146.1.27Name Nm [0.1]146.1.28PostalAddress PstlAdr [0.1]14Used in element(s)"BranchIdentification" on page 134.6.1IdentificationXML Tag: IdPresence: [0.1]Definition: Unique and unambiguous identification of a branch of a financial institution.Datatype: "Max35Text" on page 1584.6.2NameXML Tag: NmPresence: [0.1]Definition: Name by which an agent is known and which is usually used to identify that agent.Datatype: "Max140Text" on page 156Usage Guideline details This Identification/Name) will be ignored by the Receiver. This gent/BranchIdentification/Name)will be ignored by the Receiver.4.6.3PostalAddressXML Tag: PstlAdrPresence: [0.1]Definition: Information that locates and identifies a specific address, as defined by postal services.14PageDomestic and International Credit Transfer - pain.001.001.03 InsideBusiness Payments - InsideBusiness Payments
Message ComponentsThe PstlAdr block contains the following elements (see datatype "PostalAddress6" on page 99 fordetails)Removed -Ignored -Index!Details below -Mandatory - R[x.x] Repeatability[details]Message Item XML Tag OrMult.UsageGuidelinesPage9.1.2 ,6.1.9 ,6.1.29 ,10.1.0AddressType AdrTp [0.1]1009.1.3 ,6.1.10 ,6.1.30 ,10.1.1Department Dept [0.1]1019.1.4 ,6.1.11 ,6.1.31 ,10.1.2SubDepartment SubDept [0.1]1019.1.5 ,6.1.12 ,6.1.32 ,10.1.3StreetName StrtNm [0.1]1029.1.6 ,6.1.13 ,6.1.33 ,10.1.4BuildingNumber BldgNb [0.1]1029.1.7 ,6.1.14 ,6.1.34 ,10.1.5PostCode PstCd [0.1]1039.1.8 ,6.1.15 ,6.1.35 ,10.1.6TownName TwnNm [0.1]1039.1.9 ,6.1.16 ,6.1.36 ,10.1.7CountrySubDivision CtrySubDvsn [0.1]1049.1.10 ,6.1.17 ,6.1.37 ,10.1.8Country Ctry [0.1]1049.1.11 ,6.1.18 ,6.1.38 ,10.1.9AddressLine AdrLine [0.7]104Usage Guideline details This Identification/PostalAddress) will be ignored by the Receiver. This gent/BranchIdentification/PostalAddress) will be ignored by the Receiver.06 January 201715
Usage Guideline4.7CashAccount16Definition: Set of elements used to identify an account.Removed -Ignored -Index!Details below -Mandatory - R[x.x] Repeatability[details]Message Item XML Tag OrMult.UsageGuidelinesPage1.1.0Identification Id [1.1]161.1.8Type Tp [0.1]161.1.11Currency Ccy [0.1]1.1.12Name Nm [0.1]!1718Used in element(s)"ChargesAccount" on page 90, "CreditorAccount" on page 40, "CreditorAgentAccount" on page 38, "DebtorAccount" on page 88, "DebtorAgentAccount" on page 89,"IntermediaryAgent1Account" on page 36, "IntermediaryAgent2Account" on page 37,"IntermediaryAgent3Account" on page 384.7.1IdentificationXML Tag: IdPresence: [1.1]Definition: Unique and unambiguous identification for the account between the account owner and theaccount servicer.The Id block contains the following elements (see datatype "AccountIdentification4Choice" onpage 9 for details)Removed -Ignored -Index4.7.2!Details below -Mandatory - R[x.x] Repeatability[details]Message Item XML Tag OrMult.UsageGuidelines1.1.1IBAN IBAN {Or[1.1]91.1.2Other Othr Or}[1.1]9TypeXML Tag: TpPresence: [0.1]Definition: Specifies the nature, or use of the account.16PageDomestic and International Credit Transfer - pain.001.001.03 InsideBusiness Payments - InsideBusiness Payments
Message ComponentsThe Tp block contains the following elements (see datatype "CashAccountType2" on page 18 for details)Removed IndexIgnored -!Details below -Mandatory - R[x.x] Repeatability[details]Message Item XML Tag OrMult.UsageGuidelinesPage1.1.9Code Cd {Or[1.1]181.1.10Proprietary Prtry Or}[1.1]19Usage Guideline details This Account/Type) will be ignored bythe Receiver. This ) will be ignored by the Receiver. This /Type) will be ignored by the Receiver. This ccount/Type) will be ignored by theReceiver.4.7.3CurrencyXML Tag: CcyPresence: [0.1]Definition: Identification of the currency in which the account is held.Usage: Currency should only be used in case one and the same account number covers several currenciesand the initiating party needs to identify which currency needs to be used for settlement on the account.Datatype: "ActiveOrHistoricCurrencyCode" on page 134Usage Guideline details This ency) will be ignored by the Receiver. This /Currency) will be ignored by the Receiver. This ccount/Currency) will be ignoredby the Receiver. on CurrencyComment:06 January 201717
Usage GuidelineCurrency can be EUR or absent4.7.4NameXML Tag: NmPresence: [0.1]Definition: Name of the account, as assigned by the account servicing institution, in agreement with theaccount owner in order to provide an additional means of identification of the account.Usage: The account name is different from the account owner name. The account name is used in certain user communities to provide a means of identifying the account, in addition to the account owner'sidentity and the account number.Datatype: "Max70Text" on page 159Usage Guideline details This ) will be ignored by the Receiver. This /Name) will be ignored by the Receiver. This ccount/Name) will be ignored bythe Receiver.4.8CashAccountType2Definition: Nature or use of the account.Removed -Ignored -Index!Details below -Mandatory - R[x.x] Repeatability[details]Message Item XML Tag OrMult.UsageGuidelines1.1.9Code Cd {Or[1.1]181.1.10Proprietary Prtry Or}[1.1]19Used in element(s)"Type" on page 164.8.1CodeXML Tag: CdPresence: [1.1]WarningEither Code or Proprietary must be present, but not both.Definition: Account type, in a coded form.Datatype: "CashAccountType4Code" on page 13918PageDomestic and International Credit Transfer - pain.001.001.03 InsideBusiness Payments - InsideBusiness Payments
Message Components4.8.2ProprietaryXML Tag: PrtryPresence: [1.1]WarningEither Code or Proprietary must be present, but not both.Definition: Nature or use of the account in a proprietary form.Datatype: "Max35Text" on page 1584.9CategoryPurpose1ChoiceDefinition: Specifies the high level purpose of the instruction based on a set of pre-defined categories.Usage: This is used by the initiating party to provide information concerning the processing of the payment. It is likely to trigger special processing by any of the agents involved in the payment chain.Removed -Ignored -Index!Details below -Mandatory - R[x.x] Repeatability[details]Message Item XML Tag OrMult.UsageGuidelinesPage2.15 ,2.40Code Cd {Or[1.1]!192.16 ,2.41Proprietary Prtry Or}[1.1]!19Used in element(s)"CategoryPurpose" on page 944.9.1CodeXML Tag: CdPresence: [1.1]Definition: Category purpose, as published in an external category purpose code list.Datatype: "ExternalCategoryPurpose1Code" on page 150Usage Guideline details on oryPurpose/Code– CGI CategoryPurposeCodeRule:If Cd is populated, Prtry should not be populated. A code from the externalcode list should be used4.9.2ProprietaryXML Tag: Prtry06 January 201719
Usage GuidelinePresence: [1.1]Definition: Category purpose, in a proprietary form.Datatype: "Max35Text" on page 158Usage Guideline details on oryPurpose/Proprietary– CGI CategoryPurposeProprietaryRule:If Prtry is populated, Cd should not be populated. The condition is based onthe need to use a proprietary code not on the external code list per bilateralagreement.All proprietary codes used are part of the country specific addenda.4.10CategoryPurpose1Choice 1Definition: Specifies the high level purpose of the instruction based on a set of pre-defined categories.Usage: This is used by the initiating party to provide information concerning the processing of the payment. It is likely to trigger special processing by any of the agents involved in the payment chain.Removed -Ignored -Index!Details below -Mandatory - R[x.x] Repeatability[details]Message Item XML Tag OrMult.2.15 ,2.40Code Cd {Or[1.1]2.16 ,2.41Proprietary Prtry Or}[1.1]UsageGuidelines20!Used in element(s)"CategoryPurpose" on page 964.10.1CodeXML Tag: CdPresence: [1.1]Definition: Category purpose, as published in an external category purpose code list.Datatype: "categorypurpose ING" on page 1674.10.2ProprietaryXML Tag: PrtryPresence: [1.1]Definition: Category purpose, in a proprietary form.Datatype: "Max35Text" on page 15820PageDomestic and International Credit Transfer - pain.001.001.03 InsideBusiness Payments - InsideBusiness Payments20
Message ComponentsUsage Guideline details on rmation/CategoryPurpose/Proprietary– CGI CategoryPurposeProprietaryRule:If Prtry is populated, Cd should not be populated.4.11Cheque6Definition: Set of characteristics related to a cheque instruction, such as cheque type or cheque number.Removed -Ignored -Index!Details below -Message ItemMandatory - R[x.x] Repeatability[details] XML Tag OrMult.UsageGuidelinesPage2.53ChequeType ChqTp [0.1]222.54ChequeNumber ChqNb [0.1]222.55ChequeFrom ChqFr [0.1]222.58DeliveryMethod DlvryMtd [0.1]222.61DeliverTo DlvrTo [0.1]232.64InstructionPriority InstrPrty [0.1]232.65ChequeMaturityDate ChqMtrtyDt [0.1]232.66FormsCode FrmsCd [0.1]232.67MemoField MemoFld [0.2]232.68RegionalClearingZone RgnlClrZone [0.1]242.69PrintLocation PrtLctn [0.1]24RulesR24ChequeMaturityDateRule If ChequeMaturityDate is present, then ChequeType must be present and equal to DRFT or ELDR.Error handling:– Error severity: Fatal– Error Code: X00101– Error Text: Invalid message content for cheque maturity date.Used in element(s)"ChequeInstruction" on page 3406 January 201721
Usage Guideline4.11.1ChequeTypeXML Tag: ChqTpPresence: [0.1]Definition: Specifies the type of cheque to be issued.Datatype: "ChequeType2Code" on page 1434.11.2ChequeNumberXML Tag: ChqNbPresence: [0.1]Definition: Unique and unambiguous identifier for a cheque as assigned by the agent.Datatype: "Max35Text" on page 1584.11.3ChequeFromXML Tag: ChqFrPresence: [0.1]Definition: Identifies the party that ordered the issuance of the cheque.The ChqFr block contains the following elements (see datatype "NameAndAddress10" on page 66for details)Removed -Ignored -Index!Details below -Mandatory - R[x.x] Repeatability[details]Message Item XML Tag OrMult.UsageGuidelinesPage2.56 ,2.62 ,2.96Name Nm [1.1]662.57 ,2.63 ,2.97Address Adr [1.1]664.11.4DeliveryMethodXML Tag: DlvryMtdPresence: [0.1]Definition: Specifies the delivery method of the cheque by the debtor's agent.The DlvryMtd block contains the following elements (see datatype "ChequeDeliveryMethod1Choice" onpage 24 for details)Removed Index22Ignored -!Details below -Mandatory - R[x.x] Repeatability[details]Message Item XML Tag OrMult.UsageGuidelinesPage2.59Code Cd {Or[1.1]242.60Proprietary Prtry Or}[1.1]24Domestic and International Credit Transfer - pain.001.001.03 InsideBusiness Payments - InsideBusiness Payments
Message Components4.11.5DeliverToXML Tag: DlvrToPresence: [0.1]Definition: Party to whom the debtor's agent needs to send the cheque.The DlvrTo block contains the following elements (see datatype "NameAndAddress10" on page 66for details)Removed -Ignored -Index!Details below -Mandatory - R[x.x] Repeatability[details]Message Item XML Tag OrMult.UsageGuidelinesPage2.56 ,2.62 ,2.96Name Nm [1.1]662.57 ,2.63 ,2.97Address Adr [1.1]664.11.6InstructionPriorityXML Tag: InstrPrtyPresence: [0.1]Definition: Urgency or order of importance that the originator would like the recipient of the payment instruction to apply to the processing of the payment instruction.Datatype: "Priority2Code" on page 1624.11.7ChequeMaturityDateXML Tag: ChqMtrtyDtPresence: [0.1]Definition: Date when the draft becomes payable and the debtor's account is debited.Datatype: "ISODate" on page 1544.11.8FormsCodeXML Tag: FrmsCdPresence: [0.1]Definition: Identifies, in a coded form, the cheque layout, company logo and digitised signature to beused to print the cheque, as agreed between the initiating party and the debtor's agent.Datatype: "Max35Text" on page 1584.11.9MemoFieldXML Tag: MemoFldPresence: [0.2]Definition: Information that needs to be printed on a cheque, used by the payer to add miscellaneous information.06 January 201723
Usage GuidelineDatatype: "Max35Text" on page 1584.11.10RegionalClearingZoneXML Tag: RgnlClrZonePresence: [0.1]Definition: Regional area in which the cheque can be cleared, when a country
XML Tag: IBAN Presence: [1.1] Definition: International Bank Account Number (IBAN) - identifier used internationally by financial institu-tions to uniquely identify the account of a customer. Further specifications of the format and content of the IBAN can be found in the standard ISO 1361
