Formats for Internet Bank
|
|
|
- Bernard Miller
- 10 years ago
- Views:
Transcription
1 1/42 Formats for Internet Bank This document specifies payment initiation and account statement formats in LHV Internet Bank. PAYMENT INITIATION... 2 XML FORMAT (ISO PAYMENT INITIATION MESSAGE PAIN )... 2 TH5 FORMAT (DOMESTIC PAYMENT) TH5 FORMAT (FOREIGN PAYMENT) TH6 FORMAT (DOMESTIC PAYMENT) TH6 FORMAT (FOREIGN PAYMENT) ACCOUNT STATEMENT XML FORMAT (ISO ACCOUNT STATEMENT MESSAGE CAMT ) TH6 FORMAT CSV FORMAT... 42
2 2/42 Payment initiation XML format (ISO Payment Initiation Message pain ) The ISO Payment Initiation Message pain is a payment initiation standard that covers SEPA and other payments made at LHV Bank. The ISO format allows to include information that is not supported by LHV Bank. That information is not processed by LHV Bank. MESSAGE STRUCTURE Group Header mandatory, occurs once. Payment Information mandatory and repetitive. Contains information related to mostly the debit side of the payment. Credit Transfer Transaction Information mandatory and repetitive. Contains information related to the payment(s) included in the message. MESSAGE ROOT INDEX MULT. MESSAGE ELEMENT XML TAG [1..1] +MessageRoot <CstmrCdtTrfInitn> GROUP HEADER INDEX MULT. MESSAGE ELEMENT <XML TAG> LHV REQUIREMENT 1.0 [1..1] +GroupHeader <GrpHdr> 1.1 [1..1] ++MessageIdentification <MsgId> 1.2 [1..1] ++CreationDateTime <CreDtTm> 1.6 [1..1] ++NumberOfTransactions <NbOfTxs> Number of payments in all Payment Information blocks included in this message. If this number is not correct, the file upload will be cancelled. 1.7 [0..1] ++ControlSum <CtrlSum> Control sum of all individual amounts for all Payment Information blocks included in this message, irrespective of currencies. If this number is not correct, the file upload will be cancelled. 1.8 [1..1] ++InitiatingParty <InitgPty> LHV Bank does not support credit transfers on behalf of the remitter. Information in this block will be ignored.
3 3/ [0..1] +++Name <Nm> 1.8 [0..1] +++Identification <Id> 1.8 {Or ++++OrganisationIdentification <OrgId> 1.8 {{Or +++++BICOrBEI <BICOrBEI> 1.8 Or}} +++++Other <Othr> 1.8 [1..1] Identification <Id> 1.8 [0..1] SchemeName <SchmeNm> 1.8 [1..1] Code <Cd> 1.8 Or} ++++PrivateIdentification <PrvtId> 1.8 {Or +++++DateAndPlaceOfBirth <DtAndPlcOfBirth> 1.8 [1..1] BirthDate <BirthDt> 1.8 [1..1] CityOfBirth <CityOfBirth> 1.8 [1..1] CountryOfBirth <CtryOfBirth> 1.8 Or} +++++Other <Othr> 1.8 [1..1] Identification <Id> 1.8 [0..1] SchemeName <SchmeNm> 1.8 [1..1] Code <Cd> PAYMENT INFORMATION INDEX MULT. MESSAGE ELEMENT <XML TAG> LHV REQUIREMENT 2.0 [1..n] +PaymentInformation <PmtInf> 2.1 [1..1] ++PaymentInformationIdentification <PmtInfId> 2.2 [1..1] ++PaymentMethod <PmtMtd> Only the value TRF (credit transfer) is allowed here. If any other value is entered, it will be ignored.
4 4/ [0..1] ++BatchBooking <BtchBookg> Not used. 2.4 [0..1] ++NumberOfTransactions <NbOfTxs> Number of payment included in the current Payment Information block. If this number is not correct, the file upload will be cancelled. 2.5 [0..1] ++ControlSum <CtrlSum> Control sum of all individual amounts in the current Payment Information block, irrespective of currencies. If this number is not correct, the file upload will be cancelled. 2.6 [0..1] ++PaymentTypeInformation <PmtTpInf> 2.7 [0..1] +++InstructionPriority <InstrPrty> 2.8 [0..1] +++ServiceLevel <SvcLvl> 2.9 [1..1] ++++Code <Cd> 2.11 [0..1] +++LocalInstrument <LclInstrm> 2.12 {Or ++++Code <Cd> 2.13 Or} ++++Proprietary <Prtry> Payment priority information [0..1] +++CategoryPurpose <CtgyPurp> The value here applies to all payments included in the current Payment Information block. See the supported values in Code Set: Payment Priority [1..1] ++++Code <Cd> See the supported values in Code Set: Category Purpose [1..1] ++Requested Execution Date <ReqdExctnDt> Date on which the remitter s account is debited [1..1] ++Remitter <Dbtr> Party from whose account the amount of payment is to be debited. If a different party s information is entered, it will be ignored [1..1] +++Name <Nm> Remitter s name [0..1] +++PostalAddress <PstlAdr> 2.19 [0..1] ++++Country <Ctry> Remitter s country ISO code [0..2] ++++AddressLine <AdrLine> Remitter s address [0..1] +++Identification <Id>
5 5/ {Or ++++OrganisationIdentification <OrgId> 2.19 {{Or +++++BICOrBEI <BICOrBEI> Remitter s BIC or BEI code Or}} +++++Other <Othr> 2.19 [1..1] Identification <Id> Organisation s identification code [0..1] SchemeName <SchmeNm> 2.19 [1..1] Code <Cd> See the supported values in Code Set: Organisation Identification Or} ++++PrivateIdentification <PrvtId> 2.19 {Or +++++DateAndPlaceOfBirth <DtAndPlcOfBirth> 2.19 [1..1] BirthDate <BirthDt> Remitter s birth date [1..1] CityOfBirth >CityOfBirth> Remitter s city of birth [1..1] CountryOfBirth <CtryOfBirth> Remitter s birth country ISO code Or} +++++Other <Othr> 2.19 [1..1] Identification <Id> Remitter s identification code [0..1] SchemeName <SchmeNm> 2.19 [1..1] Code <Cd> See the supported values in Code Set: Private Person Identification [1..1] ++RemitterAccount <DbtrAcct> Remitter s account from which the amount of payment is to be debited [1..1] +++Identification <Id> 2.20 [1..1] ++++IBAN <IBAN> Remitter s IBAN. If the remitter s account does not correspond to the selected account, the payment will be either replaced with the selected account or will not be imported. A relevant error message will appear [0..1] +++Currency <Ccy> Not required to be filled in. The payment will be made in the currency of the payment amount. If there are not enough funds available on the account, a relevant error message will appear [1..1] ++ RemitterAgent <DbtrAgt> Remitter s bank information [1..1] +++FinancialInstitutionIdentification <FinInstnId>
6 6/ [1..1] ++++BIC <BIC> If the LHV BIC is faulty or missing, it will be replaced with the correct code [0..1] ++UltimateRemitter <UltmtDbtr> SEPA specific information. Ultimate party that owes an amount of money to the (ultimate) beneficiary. If ultimate remitter information is filled in at the Payment Information level, it will apply to all payments included in this block. Usage rule: Only to be used if different from the beneficiary [0..1] +++Name <Nm> Ultimate remitter s name [0..1] +++Identification <Id> 2.23 {Or ++++OrganisationIdentification <OrgId> 2.23 {{Or +++++BICOrBEI <BICOrBEI> Ultimate remitter s BIC or BEI code Or}} +++++Other <Othr> 2.23 [1..1] Identification <Id> Organisation s identification code [0..1] SchemeName <SchmeNm> 2.23 [1..1] Code <Cd> See the supported values in Code Set: Organisation Identification Or} ++++PrivateIdentification <PrvtId> 2.23 {Or +++++DateAndPlaceOfBirth <DtAndPlcOfBirth> 2.23 [1..1] BirthDate <BirthDt> Ultimate remitter s birth date [1..1] CityOfBirth >CityOfBirth> Ultimate remitter s city of birth [1..1] CountryOfBirth <CtryOfBirth> Ultimate remitter s birth country ISO code Or} +++++Other <Othr> 2.23 [1..1] Identification <Id> Ultimate remitter s identification code [0..1] SchemeName <SchmeNm> 2.23 [1..1] Code <Cd> See the supported values in Code Set: Private Person Identification [0..1] ++ChargesBearer <ChrgBr> See the supported values in Code Set: Charges Bearer [0..1] ++ChargesAccount <ChrgsAcct> LHV Bank does not support charge debiting from other than remitter s
7 7/42 account [1..1] +++Identification <Id> 2.25 [1..1] ++++IBAN <IBAN> 2.25 [0..1] +++Currency <Ccy> 2.27 [1..n] ++CreditTransferTransactionInformation <CdtTrfTxInf> This block contains a set of elements providing information on the payment(s) included in the message [1..1] +++PaymentIdentification <PmtId> 2.29 [0..1] ++++InstructionIdentification <InstrId> Payment order number 2.30 [1..1] ++++EndToEndIdentification <EndToEndId> Not used [0..1] +++PaymentTypeInformation <PmtTpInf> Set of elements used to specify the type of payment [0..1] ++++ServiceLevel <SvcLvl> Not used [1..1] +++++Code <Cd> 2.36 [0..1] ++++LocalInstrument <LclInstrm> 2.37 {Or +++++Code <Cd> 2.38 Or} +++++Proprietary <Prtry> Payment priority information [0..1] ++++CategoryPurpose <CtgyPurp> The value here applies to the payment included in the current Credit Transfer Transaction Information block. See the supported values in Code Set: Payment Priority [1..1] +++++Code <Cd> See the supported values in Code Set: Category Purpose [1..1] +++Amount <Amt> 2.43 {Or ++++InstructedAmount <InstdAmt> Payment amount and the currency ordered by the initiating party. All currencies accepted by the bank for payment services are allowed. If there are not enough funds available on the account in a given currency, a relevant error message will appear Or} ++++EquivalentAmount <EqvtAmt> Not used.
8 8/ [0..1] +++ChargeBearer <ChrgBr> See the supported values in Code Set: Charges Bearer [0..1] +++UltimateRemitter <UltmtDbtr> SEPA specific information. Ultimate party that owes an amount of money to the (ultimate) beneficiary. If ultimate remitter information is filled in at the Credit Transfer Transaction Information level, it will apply only to the current payment. Usage rule: Only to be used if different from the beneficiary [0..1] ++++Name <Nm> Ultimate remitter s name [0..1] ++++Identification <Id> 2.70 {Or +++++OrganisationIdentification <OrgId> 2.70 {{Or BICOrBEI <BICOrBEI> Ultimate remitter s BIC or BEI code Or}} Other <Othr> 2.70 [1..1] Identification <Id> Organisation s identification code [0..1] SchemeName <SchmeNm> 2.70 [1..1] Code <Cd> See the supported values in Code Set: Organisation Identification Or} +++++PrivateIdentification <PrvtId> 2.70 {Or DateAndPlaceOfBirth <DtAndPlcOfBirth> 2.70 [1..1] BirthDate <BirthDt> Ultimate remitter s birth date [1..1] CityOfBirth <CityOfBirth> Ultimate remitter s city of birth [1..1] CountryOfBirth <CtryOfBirth> Ultimate remitter s birth country ISO code Or} Other <Othr> 2.70 [1..1] Identification <Id> Ultimate remitter s identification code [0..1] SchemeName <SchmeNm> 2.70 [1..1] Code <Cd> See the supported values in Code Set: Private Person Identification [0..1] +++IntermediaryAgent1 <IntrmyAgt1> Information about the beneficiary s bank s correspondent bank. Used for foreign payments.
9 9/ [1..1] ++++FinancialInstitutionIdentification <FinInstnId> 2.71 [0..1] +++++BIC <BIC> Bank s BIC code [0..1] +++++ClearingSystemMemberIdentificatio n <ClrSysMmbId> 2.71 [0..1] ClearingSystemIdentification <ClrSysId> 2.71 [1..1] Code <Cd> For the clearing system s identification code see the External Code Sets spreadsheet on the ISO website [1..1] MemberIdentification <MmbId> Identification of the beneficiary's bank's correspondent bank in a clearing system [0..1] +++++Name <Nm> Name of the beneficiary s bank s correspondent bank. Used when the BIC or the clearing system s member identification is not known to the initiating party [0..1] +++++PostalAddress <PstlAdr> 2.71 [0..1] Country <Ctry> Country ISO code of the beneficiary s bank s correspondent bank [0..2] AddressLine <AdrLine> Country address of the beneficiary s bank s correspondent bank [0..1] +++IntermediaryAgent1Account <IntrmyAgt1Acct> Not used [1..1] ++++Identification <Id> 2.72 {Or +++++IBAN <IBAN 2.72 Or} +++++Other <Othr> 2.72 [1..1] Identification <Id> 2.77 [0..1] +++BeneficiaryAgent <CdtrAgt> Beneficiary agent s information is required if agent is situated outside Estonia [1..1] ++++FinancialInstitutionIdentification <FinInstnId> 2.77 [0..1] +++++BIC <BIC> Beneficiary s bank s BIC [0..1] +++++ClearingSystemMemberIdentificatio n <ClrSysMmbId> 2.77 [0..1] ClearingSystemIdentification <ClrSysId> 2.77 [1..1] Code <Cd> For the clearing system s identification code see the External Code Sets spreadsheet on the ISO website [1..1] MemberIdentification <MmbId> Beneficiary s bank identification in a clearing system. For RUB payments to
10 10/42 Russia, the BIK code is entered here [0..1] +++++Name <Nm> Beneficiary's bank name. Usage rule: The name is limited to 70 characters in length. Used when the BIC or the clearing system s member identification is not known to the initiating party [0..1] +++++PostalAddress <PstlAdr> 2.77 [0..1] Country <Ctry> Beneficiary s bank s country ISO code [0..2] AddressLine <AdrLine> Beneficiary s bank s address [0..1] +++BeneficiaryAgentAccount <CdtrAgtAcct> Beneficiary s bank account at its correspondent bank [1..1] ++++Identification <Id> Usage rule: Used only for RUB payments {Or +++++IBAN <IBAN> 2.78 Or} +++++Other <Othr> 2.78 [1..1] Identification <Id> For RUB payments to Russia, the beneficiary s bank's correspondent account with the Russian central bank is entered here [1..1] +++Beneficiary <Cdtr> Beneficiary s information [1..1] ++++Name <Nm> Beneficiary s name [0..1] ++++PostalAddress PstlAdr> Beneficiary s address [0..1] +++++Country <Ctry> Usage rule: Client who is a resident of Estonia will enter the beneficiary's country ISO code and the code of the balance of payment, if the payment is sent outside Estonia and the payment amount exceeds 50,000 euros or its equivalent in a foreign currency [0..2] +++++AddressLine <AdrLine> 2.79 [0..1] ++++Identification <Id> Beneficiary s identification {Or +++++OrganisationIdentification <OrgId> 2.79 {{Or BICOrBEI <BICOrBEI> Beneficiary s BIC or BEI code Or}} Other <Othr>
11 11/ [1..1] Identification <Id> Organisation s identification code [0..1] SchemeName <SchmeNm> For RUB payments to Russia, INN and KPP codes are entered here {{Or Code <Cd> See the supported values in Code Set: Organisation Identification Or}} Proprietary <Prtry> Scheme names INN and KPP are be entered here Or} +++++PrivateIdentification <PrvtId> 2.79 {Or DateAndPlaceOfBirth <DtAndPlcOfBirth> 2.79 [1..1] BirthDate <BirthDt> Beneficiary s birth date [1..1] CityOfBirth <CityOfBirth> Beneficiary s city of birth [1..1] CountryOfBirth <CtryOfBirth> Beneficiary s birth country ISO code Or} Other <Othr> 2.79 [1..1] Identification <Id> Beneficiary s identification [0..1] SchemeName <SchmeNm> 2.79 [1..1] Code <Cd> See the supported values in Code Set: Private Person Identification [1..1] +++BeneficiaryAccount <CdtrAcct> Beneficiary s account [1..1] ++++Identification <Id> 2.80 {Or +++++IBAN <IBAN> Beneficiary s IBAN Or} +++++Other <Othr> 2.80 [1..1] Identification <Id> Beneficiary s account number [0..1] +++UltimateBeneficiary <UltmtCdtr> SEPA specific information. Ultimate beneficiary is the ultimate beneficiary of the payment [0..1] ++++Name <Nm> Ultimate beneficiary s name [0..1] ++++Identification <Id> 2.81 {Or +++++OrganisationIdentification <OrgId>
12 12/ {{Or BICOOrBEI <BICOrBEI> Ultimate beneficiary s BIC or BEI Or}} Other <Othr> 2.81 [1..1] Identification <Id> Ultimate beneficiary s organisation identification [0..1] SchemeName <SchmeNm> 2.81 [1..1] Code <Cd> See the supported values in Code Set: Organisation Identification Or} +++++PrivateIdentification <PrvtId> 2.81 {Or DateAndPlaceOfBirth <DtAndPlcOfBirth> 2.81 [1..1] BirthDate <BirthDt> Ultimate beneficiary s birth date [1..1] CityOfBirth <CityOfBirth> Ultimate beneficiary s city of birth [1..1] CountryOfBirth <CtryOfBirth> Ultimate beneficiary s birth country ISO code Or} Other <Othr> 2.81 [1..1] Identification <Id> Ultimate beneficiary s identification [0..1] SchemeName <SchmeNm> 2.81 [1..1] Code <Cd> See the supported values in Code Set: Private Person Identification [0..1] +++Purpose <Purp> SEPA specific information. Reason for the payment [1..1] ++++Code <Cd> See the supported codes in Code Set: Purpose [0..10] +++RegulatoryReporting <RgltryRptg> Information about the declaration of payments [0..1] ++++Authority <Authrty> Information required by the Russian central bank: For RUB payments to Russia, the VO code and in some cases the KBK code are entered here [0..1] +++++Country <Ctry> 2.89 [0..n] ++++Details <Dtls> 2.89 [0..1] +++++Type <Tp>
13 13/ [0..1] +++++Country <Ctry> 2.89 [0..1] +++++Code <Cd> 2.89 [0..1] +++++Information <Inf> 2.98 [0..1] +++RemittanceInformation <RmtInf> Used to enter the payment description (unstructured) and the reference number (structured). If both structured and unstructured information is filled in, the beneficiary reference under the structured information will be lifted to the unstructured information tag in accordance with the EACT standard for unstructured remittance information formatting rules. If the remittance information will, as a result, be longer than 140 characters, the bank will deliver only the first 140 characters of the remittance information [0..1] ++++Unstructured <Ustrd> Payment description is entered here [0..1] ++++Structured <Strd> [0..1] +++++BeneficiaryReferenceInformation <CdtrRefInf> [0..1] Type <Tp> [1..1] CodeOrProprietary <CdOrPrtry> [1..1] Code <Cd> Only the value SCOR is allowed here. If any other value is entered, it will be ignored [0..1] Issuer <Issr> [0..1] Reference <Ref> Payment reference number is entered here. CODE SET: PAYMENT PRIORITY CODE NORM DESCRIPTION Normal payment. HIGH Urgent payment. EXPR Extra urgent payment. If payment priority is not provided or faulty, default values will be used. For additional information see Payment processing time limits and settlements.
14 14/42 CODE SET: CATEGORY PURPOSE CODE CASH DESCRIPTION Cash management. CORT Trade settlement payment. DIVI Dividends payment. GOVT Government payment. HEDG Hedging. INTC Intra-company payment. INTE Interest payment. LOAN Transfer of a loan to a borrower. PENS Pension payment. SALA Salary payment. SECU Securities payment. SSBE Social security benefit payment. SUPP Supplier payment. TAXS Tax payment. TRAD Trade finance transaction payment. TREA Treasury payment. VATX VAT payment. WHLD Withholding tax payment. OTHR Other payment. EPAY Payment via online banking. FCOL Fee collection.
15 15/42 CODE SET: PURPOSE CODE ACCT DESCRIPTION Account management. CASH Cash management. COLL Collection payment. INTC Intra-company payment. LIMA Liquidity management. NETT Netting. AGRT Agricultural payment. BEXP Business expenses. COMC Commercial payment. CPYR Copyright. LICF Licence fee. GDDS Purchase and sale of goods. SCVE Purchase and sale of services. SUBS Subscription. SUPP Supplier payment. CHAR Charity payment. HLRP Housing loan repayment. INSU Insurance premium. INTE Interest. LBRI Labour insurance. LIFI Life insurance.
16 16/42 LOAN Loan to borrower. LOAR Loan to lender. PPTI Property insurance. ADVA Advance payment. CCRD Credit card payment. DCRD Debit card payment. GOVT Government payment. MSVC Multiple service types. NOWS Not otherwise specified. OTHR Other. PADD Preauthorised debit. RENT Rent. STDY Study. DERI Derivatives. DIVD Dividend. FREX Foreign exchange. SAVG Savings. SECU Securities. TREA Treasury payment. DNTS Dental services. HLTI Health insurance. HSPC Hospital care. LTCF Long-term care facility.
17 17/42 MDCS Medical services. ALMY Alimony payment. BONU Bonus payment. BECH Child benefit. COMM Commission. PENS Pension payment. SALA Salary payment. SSBE Social security benefit. HSTX Housing tax. INTX Income tax. TAXS Tax payment. VATX VAT payment. AIRB Air transport. BUSB Bus transport. FERB Ferry transport. RLWY Railway transport. CBTV Cable TV bill. ELEC Electricity bill. ENRG Energies. GASB Gas bill. NWCH Network charge. NWCM Network communication. OTLC Other telecom related bill.
18 18/42 PHON Telephone bill. WTER Water bill. DEBT Deposit. GDSV Purchase and sale of goods and services. CDBL Credit card bill. EDUC Education. IVPT Invoice payment. TBIL Telecommunication bill. INVS Investment and securities. ALLW Allowance. PAYR Payroll. UBIL Utilities. CODE SET: PRIVATE PERSON IDENTIFICATION CODE ARNU CCPT CUST DESCRIPTION Number assigned by a social security agency to identify a non-resident person. Number assigned by an authority to identify the passport number of a person. Number assigned by an issuer to identify a customer. DRLC Number assigned by an authority to identify a driver's license. EMPL Number assigned by a registration authority to an employee. NIDN SOSE TXID Number assigned by an authority to identify the national identity number of a person. Number assigned by an authority to identify the social security number of a person. Number assigned by a tax authority to identify a person.
19 19/42 CODE SET: CHARGES BEARER CODE SLEV DESCRIPTION Allowed only for SEPA payments. Shared charges. SHAR Shared charges. DEBT Remitter pays charges. If the payment priority is not provided or faulty, default values will be used. For additional information see Payment processing time limits and settlements. CODE SET: ORGANISATION IDENTIFICATION CODE BANK CBID DESCRIPTION Unique and unambiguous assignment made by a specific bank or similar financial institution to identify a relationship as defined between the bank and its client. A unique identification number assigned by a central bank to identify an organisation. CHID A unique identification number assigned by a clearing house to identify an organisation. COID Country authority given organisation identification (e.g., corporate registration number). CUST DUNS Number assigned by an issuer to identify a customer. Number assigned by a party to identify a beneficiary or remitter relationship. A unique identification number provided by Dun & Bradstreet to identify an organisation. EMPL Number assigned by a registration authority to an employer. GS1G SREN SRET TXID Global Location Number. A non-significant reference number used to identify legal entities, functional entities, or physical entities according to GS1 numbering scheme rules. The number is used to retrieve detailed information that is linked to it. The SIREN number is a 9 digit code assigned by INSEE, the French National Institute for Statistics and Economic Studies, to identify an organisation in France. The SIRET number is a 14 digit code assigned by INSEE, the French National Institute for Statistics and Economic Studies, to identify an organisation unit in France. It consists of the SIREN number, followed by a five digit classification number, to identify the local geographical unit of that entity. Number assigned by a tax authority to identify an organisation.
20 20/42 TH5 format (domestic payment) A alphanumeric (character) * Mandatory field Ø space N numeric ** Not processed in payment importing Amount aligned to the right NO POS DESCRIPTION TYPE LENGTH COMMENT 1 1 Subject code A* 4 MKUØ 2 5 Record code A* 3 1ØØ ordinary 3 8 Remitter s bank N* Remitter s account A* Beneficiary's bank N* Beneficiary's account A* Beneficiary s reg. no A Beneficiary s name A* Amount N* 12 In cents as integer Payment date N 6 YYMMDD Doc. no A* Doc. date N* 6 YYMMDD Additional information A* Currency A* Client reference A 20
21 21/42 TH5 format (Foreign Payment) A alphanumeric (character) * Mandatory field Ø space N numeric ** Not processed in payment importing Amount aligned to the right NO POS DESCRIPTION TYPE LENGTH COMMENT 1 1 Subject code A* 4 MKUØ 2 5 Record code A* 3 1ØØ ordinary FPO, 2ØØ urgent FPO, 3ØØ express VMK. 3 8 Remitter s bank N* Remitter s account A* Beneficiary's bank A* 140 Full name, address and codes of the beneficiary s bank Beneficiary's account A* 35 Final beneficiary s account no at the beneficiary s bank Beneficiary's address A 105 Full address of the beneficiary Beneficiary s name A* SWIFT A 11 SWIFT code of the beneficiary s bank Amount N* 12 Amount in cents as integer Payment currency A* 3 12** 368 Debit currency A Payment date N 6 Debiting date (value date) specified by the client. YYMMDD Document no A* 8 15** 385 Document date N 6 Date of making the payment order Additional information A* 140 Details of payment Charges A* 3 OUR remitter; SHA shared (each party pays its own costs) Payment balance N* 6 Code identifying content of the payment according to the qualification of the Estonian central bank. Mandatory for payments over 50,000 (or equivalent).
22 22/ Correspondent bank A 140 Full name, address and codes of the beneficiary s bank s correspondent bank SWIFT A 11 SWIFT code of the beneficiary s bank s correspondent bank. 21** 691 Correspondent account A 35 Correspondent bank. 22** ** 866 Intermediary bank A 140 Correspondent bank of the beneficiary s bank s correspondent bank. SWIFT A 11 SWIFT code of the intermediary bank. 24** ** 912 Correspondent account A 35 Number of the correspondent account at the intermediary bank. Country A 2 Beneficiary s country of residence. 26** 914 Bank reference A 50 27** 964 State treasury reference A 20
23 23/42 TH6 format (domestic payment) A alphanumeric (character) * Mandatory field Ø space N numeric ** Not processed in payment importing Amount aligned to the right NO POS DESCRIPTION TYPE LENGTH COMMENT 1 1 Subject code A* 4 MKUØ 2 5 Record code A* 3 1ØØ ordinary, 2ØØ urgent. 3 8 Remitter s bank N* Remitter s account A* 20 International account no IBAN Beneficiary s bank N* Beneficiary s account A* 20 International account no IBAN Beneficiary s reg no A Beneficiary s name A* Amount N* 12 In cents as integer Payment date N 6 YYMMDD Doc no A* Doc date N* 6 YYMMDD Additional information A* Currency A* Client reference A 35
24 24/42 TH6 format (Foreign Payment) A alphanumeric (character) * Mandatory field Ø space N numeric ** Not processed in payment importing Amount aligned to the right NO POS DESCRIPTION TYPE LENGTH COMMENT 1 1 Subject code A* 4 MKUØ 2 5 Record code A* 3 1ØØ ordinary FPO; 2ØØ urgent FPO; 3ØØ express FPO. 3 8 Remitter s bank N* Remitter s account A* 20 International bank account no IBAN Beneficiary s bank A* 140 Full name, address and codes of the beneficiary s bank Beneficiary s account A* 35 Final beneficiary s account no at the beneficiary s bank Beneficiary s address A 105 Full address of the beneficiary Beneficiary s name A* SWIFT A 11 SWIFT code of the beneficiary s bank Amount N* 12 Amount in cents as integer Payment currency A* 3 12** 372 Debit currency A Payment date N 6 Debiting date (value date) specified by the client. YYMMDD Document no A* 8 15** 389 Document date N 6 Date of making the payment order Additional information A* 140 Details of payment Charges A* 3 OUR remitter; SHA shared (each party pais its own costs). 18** 538 Payment balance N* 6 Code identifying content of the payment according to the qualification of the Estonia central bank. Mandatory for payments over 50,000 (or equivalent).
25 25/ Correspondent bank A 140 Full name, address and codes of the beneficiary s bank s correspondent bank SWIFT A 11 SWIFT code of the beneficiary s bank s correspondent bank. 21** 695 Correspondent account A 35 Correspondent bank. 22** ** 870 Intermediary bank A 140 Correspondent bank of the beneficiary s bank s correspondent bank. SWIFT A 11 SWIFT code of the intermediary bank. 24** ** 916 Correspondent account A 35 Numer of the correspondent account at the intermediary bank. Country A 2 Beneficiary s country of residence.
26 26/42 Account Statement XML format (ISO Account Statement Message camt ) The ISO Account Statement Message camt standard is used to report account booked transactions and balances of a selected time period. The message includes information about the opening balance, the closing balance, and the available balance together with all booked transactions of a reporting period. The ISO format allows to include information that is not supported by LHV Bank. That information is not provided by LHV Bank. MESSAGE STRUCTURE Group Header mandatory, occurs once. Statement mandatory and repetitive per currency. Balance mandatory and repetitive. Contains elements such as Opening Booked Balance and Closing Booked Balance. Entry included in the Statement block. Contains information related to an entry on the account. Entry Details included in the Entry block. Contains detailed information related to the entry. MESSAGE ROOT INDEX MULT. MESSAGE ELEMENT XML TAG [1..1] +MessageRoot <BkToCstmrStmt> GROUP HEADER INDEX MULT. OR MESSAGE ELEMENT XML TAG LHV REQUIREMENT 1.0 [1..1] +GroupHeader <GrpHdr> 1.1 [1..1] ++MessageIdentification <MsgId> Account owner s unique message identifier generated by LHV Bank. 1.2 [1..1] ++CreationDateTime <CreDtTm> Date and time (UTC + 2) when the account statement message is created at LHV Bank. 1.3 [0..1] ++MessageRecipient <MsgRcpt> Not used. 1.4 [0..1] ++MessagePagination <MsgPgntn> Not used. STATEMENT INDEX MULT. OR MESSAGE ELEMENT XML TAG LHV REQUIREMENT 2.0 [1..n] +Statement <Stmt>
27 27/ [1..1] ++Identification <Id> Unique identification provided by LHV Bank. Identification is generated from the value of GrpHdr.MsgId and the currency for which this Statement block is generated. 2.2 [0..1] ++ElectronicSequenceNumber <ElctrncSeqNb> Not used. 2.3 [0..1] ++LegalSequenceNumber <LglSeqNb> Not used. 2.4 [1..1] ++CreationDateTime <CreDtTm> Date and time when the account statement is generated at LHV Bank. 2.5 [1..1] ++FromToDate <FrToDt> [1..1] +++FromDateTime <FrDtTm> Start date of the reporting period. [1..1] +++ToDateTime <ToDtTm> End date of the reporting period [1..1] ++Account <Acct> [1..1] +++Identification <Id> [1..1] ++++IBAN <IBAN> IBAN for which this statement is generated. [0..1] +++Currency <Ccy> Account currency for which this statement block is generated. [0..1] +++Servicer <Svcr> Full information about LHV Bank. [1..1] ++++FinancialInstitutionIdentific ation <FinInstnId> [0..1] +++++BIC <BIC> LHVBEE22 [0..1] +++++Name <Nm> LHV Bank [0..1] +++++PostalAddress <PstlAdr> [0..1] AddressType <AdrTp> BIZZ [0..1] StreetName <StrtNm> Tartu mnt [0..1] BuildingNumber <BldgNb> 2 [0..1] PostCode <PstCd> [0..1] TownName <TwnNm> Tallinn [0..1] CountrySubdivision <CtrySubDvsn> Harjumaa [0..1] Country <Ctry> EE
28 28/42 [0..7] AddressLine <AdrLine> 2.11 [0..1] ++RelatedAccount <RltdAcct> Not used [1..n] ++Balance <Bal> 2.24 [1..1] +++Type <Tp> 2.25 [1..1] ++++CodeOrProprietary <CdOrPrtry> 2.26 [1..1] +++++Code <Cd> See the codes in Code Set: Balance [0..1] +++CreditLine <CdtLine> Not used [1..1] +++Amount <Amt> Balance amount [1..1] +++CreditDebitIndicator <CdtDbtInd> See the codes in Code Set: Credit and Debit Code [1..1] +++Date <Dt> [1..1] ++++Date <Dt> Balance date 2.43 [1..1] ++TransactionsSummary <TxsSummry> 2.44 [0..1] +++TotalEntries <TtlNtries> Not used [1..1] +++TotalCreditEntries <TtlCdtNtries> 2.50 [0..1] ++++NumberOfEntries <NbOfNtries> Number of credit entries in a given Statement block [1..1] ++++Sum <Sum> Sum of all credit entries in a given statement block [1..1] +++TotalDebitEntries <TtlDbtNtries> 2.53 [0..1] ++++NumberOfEntries <NbOfNtries> 2.54 [1..1] ++++Sum <Sum> Sum of debit entries in a given Statement block [0..n] +++TotalEntriesPerBankTransac tioncode <TtlNtriesPerBkTxCd> Not used [0..n] ++Entry <Ntry> 2.77 [0..1] +++EntryReference <NtryRef> 2.78 [1..1] +++Amount <Amt> Transaction amount (may be zero).
29 29/ [1..1] +++CreditDebitIndicator <CdtDbtInd> See the codes in Code Set: Credit and Debit Code [0..1] +++ReversalIndicator <RvslInd> Not used [1..1] +++Status <Sts> BOOK 2.82 [1..1] +++BookingDate <BookgDt> [1..1] ++++Date <Dt> Booking date [0..1] +++ValueDate <ValDt> Not used. [1..1] ++++Date <Dt> 2.84 [1..1] +++AccountServicerReference <AcctSvcrRef> Unique payment ID assigned by the bank [1..1] +++BankTransactionCode <BkTxCd> 2.92 [1..1] ++++Domain <Domn> 2.93 [1..1] +++++Code <Cd> XTND 2.94 [1..1] +++++Family <Fmly> 2.95 [1..1] Code <Cd> NTAV 2.96 [1..1] SubFamilyCode <SubFmlyCd> NTAV 2.97 [0..1] ++++Proprietary <Prtry> Not used [0..1] +++AdditionalInformationIndicat or <AddtlInfInd> Not used [1..n] +++EntryDetails <NtryDtls> [0..1] ++++Batch <Btch> Not used [0..n] ++++TransactionDetails <TxDtls> [1..1] +++++References <Refs> [0..1] MessageIdentification <MsgId> Not used [0..1] AccountServicerReferen ce [0..1] PaymentInformationIden tification <AcctSvcrRef> <PmtInfId> Unique payment ID assigned by the bank. Unique identification assigned by a sending party.
30 30/ [0..1] InstructionIdentification <InstrId> Payment order number or NOTPROVIDED [0..1] EndToEndIdentification <EndToEndId> [0..1] TransactionIdentification <TxId> Not used [0..1] MandateIdentification <MndtId> Not used [0..1] ChequeNumber <ChqNb> Not used [0..1] Proprietary <Prtry> Not used [0..1] +++++AmountDetails <AmtDtls> Not used [0..1] +++++BankTransactionCode <BkTxCd> Not used [0..n] +++++Charges <Chrgs> Not used [0..n] +++++Interest <Intrst> Not used [0..1] +++++RelatedParties <RltdPties> [0..1] InitiatingParty <InitgPty> Not used [0..1] Remitter <Dbtr> [0..1] Name <Nm> Remitter s name. [0..1] PostalAddress <PstlAdr> [0..1] AddressType <AdrTp> [0..1] Department <Dept> [0..1] SubDepartment <SubDept> [0..1] StreetName <StrtNm> [0..1] BuildingNumber <BldgNb> [0..1] PostCode <PstCd> [0..1] TownName <TwnNm> [0..1] CountrySubdivision <CtrySubDvsn>
31 31/42 [0..1] Country <Ctry> Remitter s country ISO code. [0..7] AddressLine <AdrLine> Remitter s address. [0..1] Identification <Id> [1..1] {Or OrganisationIdentifica tion <OrgId> [0..1] BICOrBEI <BICOrBEI> Remitter s BIC or BEI. [0..n] Other <Othr> [1..1] Identification <Id> Remitter s identification. [1..1] Or} PrivateIdentification <PrvtId> [0..1] DateAndPlaceOfBirt h <DtAndPlcOfBirth> [1..1] BirthDate <BirthDt> Remitter s birth date. [1..1] CityOfBirth <CityOfBirth> Remitter s city of birth. [1..1] CountryOfBirth <CtryOfBirth> Remitter s country of birth. [0..n] Other <Othr> [1..1] Identification <Id> Remitter s identification [0..1] RemitterAccount <DbtrAcct> [1..1] Identification <Id> [1..1] {Or IBAN <IBAN> Remitter s IBAN. [1..1] Or} Other <Othr> [1..1] Identification <Id> Remitter s account number [0..1] UltimateRemitter <UltmtDbtr> [0..1] Name <Nm> Ultimate remitter s name. [0..1] Identification <Id> [1..1] {Or OrganisationIdentifica tion <OrgId>
32 32/42 [0..1] BICOrBEI <BICOrBEI> Ultimate remitter s BIC or BEI. [0..n] Other <Othr> [1..1] Identification <Id> Ultimate remitter s identification. [1..1] Or} PrivateIdentification <PrvtId> [0..1] DateAndPlaceOfBirt h <DtAndPlcOfBirth> [1..1] BirthDate <BirthDt> Ultimate remitter s birth date. [1..1] CityOfBirth <CityOfBirth> Ultimate remitter s city of birth. [1..1] CountryOfBirth <CtryOfBirth> Ultimate remitter s country of birth. [0..n] Other <Othr> [1..1] Identification <Id> Ultimate remitter s identification [0..1] Beneficiary <Cdtr> [0..1] Name <Nm> Beneficiary s name. [0..1] PostalAddress <PstlAdr> [0..1] Country <Ctry> Beneficiary s country ISO code. [0..1] AddressLine <AdrLine> Beneficiary s address. [0..1] Identification <Id> [1..1] {Or OrganisationIdentifica tion <OrgId> [0..1] BICOrBEI <BICOrBEI> Beneficiary s BIC or BEI. [0..n] Other <Othr> [1..1] Identification <Id> Beneficiary s identification. [1..1] Or} PrivateIdentification <PrvtId> [0..1] DateAndPlaceOfBirt h <DtAndPlcOfBirth> [1..1] BirthDate <BirthDt> Beneficiary s birth date.
33 33/42 [1..1] CityOfBirth <CityOfBirth> Beneficiary s city of birth. [1..1] CountryOfBirth <CtryOfBirth> Beneficiary s country of birth. [0..n] Other <Othr> [1..1] Identification <Id> Beneficiary s identification [0..1] BeneficiaryAccount <CdtrAcct> [1..1] Identification <Id> [1..1] {Or IBAN <IBAN> Beneficiary s IBAN. [1..1] Or} Other <Othr> [1..1] Identification <Id> Beneficiary s account number [0..1] UltimateBeneficiary <UltmtCdtr> [0..1] Name <Nm> Ultimate beneficiary s name. [0..1] Identification <Id> [1..1] {Or OrganisationIdentifica tion <OrgId> [0..1] BICOrBEI <BICOrBEI> Ultimate beneficiary s BIC or BEI. [0..n] Other <Othr> [1..1] Identification <Id> Ultimate beneficiary s identification. [1..1] Or} PrivateIdentification <PrvtId> [0..1] DateAndPlaceOfBirt h <DtAndPlcOfBirth> [1..1] BirthDate <BirthDt> Ultimate beneficiary s birth date. [1..1] CityOfBirth <CityOfBirth> Ultimate beneficiary s city of birth. [1..1] CountryOfBirth <CtryOfBirth> Ultimate beneficiary s country of birth. [0..n] Other <Othr> [1..1] Identification <Id> Ultimate beneficiary s identification.
34 34/ [0..1] +++++RelatedAgents <RltdAgts> [0..1] RemitterAgent <DbtrAgt> [1..1] FinancialInstitutionIden tification <FinInstnId> [0..1] BIC <BIC> BIC of the remitter s bank. [0..1] Name <Nm> Name of the remitter s bank [0..1] BeneficiaryAgent <CdtrAgt> [1..1] FinancialInstitutionIden tification <FinInstnId> [0..1] BIC <BIC> BIC of the beneficiary s bank. [0..1] Name <Nm> Name of the beneficiary s bank [0..1] IntermediaryAgent1 <IntrmyAgt1> Not used [0..1] IntermediaryAgent2 <IntrmyAgt2> Not used [0..1] IntermediaryAgent3 <IntrmyAgt3> [1..1] FinancialInstitutionIden tification <FinInstnId> [0..1] BIC <BIC> BIC of the beneficiary s correspondent bank. [0..1] Name <Nm> Name of the beneficiary s correspondent bank [0..1] ReceivingAgent <RcvgAgt> Not used [0..1] DeliveringAgent <DlvrgAgt> Not used [0..1] IssuingAgent <IssgAgt> Not used [0..1] SettlementPlace <SttlmPlc> Not used [0..1] +++++Purpose <Purp> [1..1] {Or Code <Cd> See the codes in Code Set: Purpose [1..1] Or} Proprietary <Prtry> [0..10] [0..10] +++++RelatedRemittanceInform ation <RltdRmtInf> Not used.
35 35/ [0..1] +++++RemittanceInformation <RmtInf> [0..n] Unstructured <Ustrd> Payment description [0..n] Structured <Strd> [0..n] BeneficiaryReferenceIn formation <CdtrRefInf> [0..1] Type <Tp> [1..1] CodeOrProprietary <CdOrPrtry> [1..1] {Or Code <Cd> SCOR [1..1] Or} Proprietary <Prtry> [0..1] Issuer <Issr> [0..1] Reference <Ref> Payment reference number [0..1] +++++RelatedDates <RltdDts> Not used [0..1] +++++Tax <Tax> Not used [0..1] +++++ReturnInformation <RtrInf> Not used [0..1] +++++AdditionalTransactionInfor mation <AddtlTxInf> Not used [0..1] +++AdditionalEntryInformation <AddtlNtryInf> Not used [0..1] ++AdditionalStatementInformatio n <AddtlStmtInf> Not used. CODE SET: BALANCE CODE OPBD DESCRIPTION Opening booked balance. CLBD Closing booked balance. CODE SET: CREDIT AND DEBIT CODE CODE CRDT DESCRIPTION Positive amount or zero.
36 36/42 DBIT Negative amount. CODE SET: PURPOSE CODE ACCT DESCRIPTION Account management. CASH Cash management. COLL Collection payment. INTC Intra-company payment. LIMA Liquidity management. NETT Netting. AGRT Agricultural payment. BEXP Business expenses. COMC Commercial payment. CPYR Copyright. LICF Licence fee. GDDS Purchase and sale of goods. SCVE Purchase and sale of services. SUBS Subscription. SUPP Supplier payment. CHAR Charity payment. HLRP Housing loan repayment. INSU Insurance premium. INTE Interest. LBRI Labour insurance.
37 37/42 LIFI Life insurance. LOAN Loan to borrower. LOAR Loan to lender. PPTI Property insurance. ADVA Advance payment. CCRD Credit card payment. DCRD Debit card payment. GOVT Government payment. MSVC Multiple service types. NOWS Not otherwise specified. OTHR Other. PADD Preauthorised debit. RENT Rent. STDY Study. DERI Derivatives. DIVD Dividend. FREX Foreign exchange. SAVG Savings. SECU Securities. TREA Treasury payment. DNTS Dental services. HLTI Health insurance. HSPC Hospital care.
38 38/42 LTCF Long-term care facility. MDCS Medical services. ALMY Alimony payment. BONU Bonus payment. BECH Child benefit. COMM Commission. PENS Pension payment. SALA Salary payment. SSBE Social security benefit. HSTX Housing tax. INTX Income tax. TAXS Tax payment. VATX VAT payment. AIRB Air transport. BUSB Bus transport. FERB Ferry transport. RLWY Railway transport. CBTV Cable TV bill. ELEC Electricity bill. ENRG Energies. GASB Gas bill. NWCH Network charge. NWCM Network communication.
39 39/42 OTLC Other telecom related bill. PHON Telephone bill. WTER Water bill.
40 40/42 TH6 format A alphanumeric (character) * Mandatory field Ø space N numeric ** Not processed in payment importing Amount aligned to the right HEADER NO POS DESCRIPTION TYPE LENGTH COMMENT 1 1 Subject code A* 4 VVØØ 2 5 Record code A* Bank code N* Account number A* 20 Bank account number in the IBAN format Date N* 6 YYMMDD, query date Time N* 4 HHMM, query time. TRANSACTIONS NO POS DESCRIPTION TYPE LENGTH COMMENT 1 1 Subject code A* 4 VVØØ 2 5 Record code A* 1 1 transaction, 2 opening balance, 3 closing balance. 3 6 Bank reference A* 16 Displayed in the format YYYYMMDDXXXXXXXX Tr. type A* 4 Transaction code (MK domestic payment, MV foreign payment) Own account number A* 20 Bank account number in the IBAN format Currency A* Bank A* 35 Counterparty s bank code and account number Name A* 35 Counterparty s name Doc. no A* Description A* 140
41 41/ C/D A* 2 C credit, D debit Amount N* 12 In cents and always positive Client reference A* 35 Payment reference no. FOOTER NO POS DESCRIPTION TYPE LENGTH COMMENT 1 1 Subject code A* 4 VVØØ 2 5 Record code A* A 190 Unused Checksum N* 12 Last 12 positions A 20 Unused.
42 42/42 CSV format Under the Internet Bank settings, you yourself can define the field and decimal separators. HEADER NO COLUMN COMMENT 1 Client account Account from which the statement was prepared. 2 Document number Payment number. 3 Date Payment date. 4 Beneficiary s/remitter s account Other party s IBAN. 5 Beneficiary s/remitter s name Other party s name. 6 Beneficiary s bank s code 7 Empty Not used. 8 Debit/Credit (D/C) 9 Amount Payment amount. Debit entries with a minus sign. 10 Reference number Payment reference number. 11 Archival ID Provided as AAAAKKPPXXXXXXXX. 12 Details Details of payment. 13 Service charge 14 Currency Payment currency. 15 Personal identification code or registry code Other party s private person s identification code or legal entity s registry code. 16 Beneficiary s/remitter s bank s BIC 17 Payment initiator s name Final remitter s name. 18 Entry reference 19 Account service provider s reference Unique payment ID assigned by the bank.
ISO 20022 PAYMENT GUIDE. Messages: Pain.001.001.03 Pain.002.001.03
ISO 20022 PAYMENT GUIDE Messages: Pain.001.001.03 Pain.002.001.03 20.11.2012 1 ISO 20022 Payment Guide Table of Contents 1 Background... 3 1.1 SEPA and ISO 20022... 3 1.2 Usage of ISO 20022 in Finland...
ISO 20022 Message Implementation Guide for Payment Initiation
ISO 20022 Message Implementation Guide for Payment Initiation Pain001 Pain002 Version: 1.5 Issue date: 16 November 2015 Author: Swedbank Table of Contents 1. Introduction 2. Customer Credit Transfer Initiation
XML message for Payment Initiation Implementation Guideline. Version 1.02
XML message for Payment Initiation Implementation Guideline Version 1.02 Version 1.02 Changes Updated 20131211 1) SEB specific rule added under tag 2.44 Equivalent Amount 2) To the tag 2.89 Regulatory
Format description XML SEPA Credit Transfer. Format Description
Format description XML SEPA Credit Transfer Format Description CONTENTS 1 SEPA CT Import format 3 1.1 SEPA CT import format description 3 1.1.1 Description 3 1.1.2 General characteristics 3 1.1.3 Difference
XML message for SEPA Credit Transfer Initiation Implementation Guidelines for the Netherlands
XML message for SEPA Credit Transfer Initiation Implementation Guidelines for the Netherlands Disclaimer These guidelines may be subject to changes. Utmost care has been taken to ensure the information
Record description XML File Transfer Balance and Transaction list camt.052.001.02
Record description XML File Transfer Balance and Transaction list camt.052.001.02 15.11.2012 Page 2 of 14 Change date Version Changed 10.10.2011 1.0 07.02.2012 1.1 2.1 Identification kentän pituus muuttunut,
OUTGOING PAYMENTS ISO 20022 APPLICATION GUIDELINE
Version 2.5 13.4.2016 OUTGOING PAYMENTS ISO 20022 APPLICATION GUIDELINE 2 (54) CONTENTS VERSION INFORMATION... 4 1 OUTGOING PAYMENTS, ISO 20022 APPLICATION GUIDELINE... 5 1.1 ISO 20022 MESSAGE DESCRIPTION
XML message for SEPA Direct Debit Initiation Implementation Guidelines for the Netherlands
XML message for SEPA Direct Debit Initiation Implementation Guidelines for the Netherlands Core and Business-to-Business Implementation Guidelines Disclaimer These guidelines may be subject to changes.
Format Description XML SEPA CT
Format Description XML SEPA CT SWIFT FileAct Rabobank Format Description XML SEPA CT - SWIFT FileAct November 2015 Version 2.2 1 Contents SEPA CT Import Format 3 SEPA CT Structure 4 Segment description
XML message for SEPA Direct Debit Initiation Implementation Guidelines for the Netherlands
XML message for SEPA Direct Debit Initiation Implementation Guidelines for the Netherlands Core and Business-to-Business Implementation Guidelines Disclaimer These guidelines may be subject to changes.
OUTGOING PAYMENTS ISO 20022 APPLICATION GUIDELINE
Version 1.94 13.4.2016 OUTGOING PAYMENTS ISO 20022 APPLICATION GUIDELINE Pain.001.001.02 Pain.002.001.02 2 (51) Sisällysluettelo MANUAL VERSION INFORMATION... 4 1 SEPA CREDIT TRANSFER, ISO 20022 APPLICATION
Format description XML SEPA Credit Transfer
Format description XML SEPA Credit Transfer Rabo Cash Management Colophon Title Format description XML SEPA CT Version, date 1.7, April 30, 2014 Our reference Format description XML SEPA Credit Transfer
Payment Status Report
Payment Status Report Implementation Guidelines Version 1.0 Beligian Finance Sector Federation rue d Arlon, 82 B-1040 Brussels http://www.febelfin.be T +32 2 507 68 11 F +32 2 888 68 11 2 Table of Contents
Appendix for BSK Implementerings Guides ISO 20022
Appendix for BSK Implementerings Guides ISO 20022 PAIN 001.001.03 CustomerCreditTransferInitiation PAIN 002.001.03 CustomerPaymentStatusReport Eksempelfiler for transaksjoner i norske betalingssystemer
ISO 20022 XML pain.001 implementation guide in Handelsbanken Estonia, Latvia, Lithuania
ISO 20022 XML pain.001 implementation guide in Handelsbanken Estonia, Latvia, Lithuania Version: 1.0 Date: 12.10.2015 1 1 Introduction This document describes the Implementation Guide for CustomerCreditTransferInitiation
SEPA CREDIT TRANSFER SCHEME INTER-BANK IMPLEMENTATION GUIDELINES
Doc: EPC115-06 25 November 2014 (Version 8.0 Approved) EPC SEPA CREDIT TRANSFER SCHEME INTER-BANK IMPLEMENTATION GUIDELINES Abstract Document Reference Issue This document sets out the rules for implementing
Danish Implementation Guideline for Common Global Implementation (CGI) Customer Payment Status Report
Danish Implementation Guideline for Common Global Implementation (CGI) Customer Payment Status Report based on documentation from ISO 20022 Message Definition Report December 15th 2012 FINAL VERSION Page
CONDITIONS FOR MAKING PAYMENT TRANSACTIONS
CONDITIONS FOR MAKING PAYMENT TRANSACTIONS 1. GENERAL PROVISIONS 1.1 In the Conditions for Making Payment Transactions (hereinafter referred to in this document as the Conditions) the bank issues the terms
XML ACCOUNT STATEMENT. Service Description
XML ACCOUNT STATEMENT Service Description October 2011 OY SAMLINK AB SERVICE DESCRIPTION 2 (18) Table of contents Table of contents Error! No table of contents entries found. OY SAMLINK AB SERVICE DESCRIPTION
Format Reference Guide
Fedwire Funds Service Effective November 10, 2014 This provides an overview of the Fedwire Funds Service message format requirements. Please refer to Section 4.3 of the Fedwire Application Interface Manual
ISO 20022 ACCOUNT STATEMENT GUIDE. v 1.3
ISO 20022 ACCOUNT STATEMENT GUIDE v 1.3 4.10.2012 1 ISO 20022 Account Statement Guide Table of contents 1 Introduction... 3 2 General... 3 2.1 Effects on customer routines... 4 2.2 Activities... 4 3 Electronic
FAQ on the UAE Funds Transfer System (FTS)
FAQ on the UAE Funds Transfer System (FTS) What is UAEFTS? The UAEFTS is the UAE based funds transfer mechanism, for moving funds from one Bank to another through the UAE Central Bank System. Why has the
Format description XML SEPA Credit Transfer
Format description XML SEPA Credit Transfer Version, date Project 1.4, 24 April 2013 Rabo Cash Management 1 Colophon Title Format description XML SEPA CT Version, date 1.4, 24 April 2013 Our reference
RECOMMENDATION ON CUSTOMER REPORTING OF SEPA CREDIT TRANSFERS AND SEPA DIRECT DEBITS
Doc: EPC188-09 27 October 2009 (Version 1.01 Approved) EPC RECOMMENDATION ON CUSTOMER REPORTING OF SEPA CREDIT TRANSFERS AND SEPA DIRECT DEBITS 0 Background With ISO 20022 standards mandatory in the Rulebooks
Format Description XML SEPA DD
Format Description XML SEPA DD RDC (Rabobank Direct Connect) Rabobank Format Description XML SEPA DD - RDC (Rabobank Direct Connect) November 2015 Version 2.2 1 Contents SEPA DD Import Format 3 SEPA DD
SEPA CORE DIRECT DEBIT SCHEME CUSTOMER-TO-BANK IMPLEMENTATION GUIDELINES
Doc: EPC130-08 30 November 2012 (Version 7.0 Approved) EPC SEPA CORE DIRECT DEBIT SCHEME CUSTOMER-TO-BANK IMPLEMENTATION GUIDELINES Abstract Document Reference Issue This document sets out the rules for
SEPA CREDIT TRANSFER SCHEME INTER-BANK IMPLEMENTATION GUIDELINES
Doc: EPC115-06 30 November 2012 (Version 7.0 Approved) EPC SEPA CREDIT TRANSFER SCHEME INTER-BANK IMPLEMENTATION GUIDELINES Abstract Document Reference Issue This document sets out the rules for implementing
DESCRIPTION OF SEPA XML FORMAT FOR ING BUSINESSONLINE IMPORT AND EXPORT TEMPLATES
DESCRIPTIN F SEPA XML FRMAT FR ING BUSINESSNLINE IMPRT AND EXPRT TEMPLATES TABLE F CNTENTS Import of orders 3 1. Introduction 3 1.1 Notation 3 1.2 File structure 4 1.3 Batching rules 4 1.4 Differentiation
Accounts and bank transfers
Price List Accounts and bank transfers... 2 Bank cards... 4 Servicing of payment cards... 7 Deposits... 8 Securities... 9 Loans... 11 Leasing... 12 Price List for Au-clients... 13 Price List for non-residents...
SEPA CORE DIRECT DEBIT SCHEME INTER-BANK IMPLEMENTATION GUIDELINES
Doc: EPC114-06 25 November 2014 (Version 8.0 Approved) EPC SEPA CORE DIRECT DEBIT SCHEME INTER-BANK IMPLEMENTATION GUIDELINES Abstract Document Reference Issue This document sets out the rules for implementing
Customer Statement - MT940 with Structured Information To Account Owner
General Information The MT940 customer statement message is an electronic message containing financial statement information for customers concerning their accounts. Danske Bank can send a MT940 either
Bankline internet banking import file layout user guide
Bankline internet banking import file layout user guide Bankline internet banking import file layout user guide 2 Contents 1. Introduction to Bankline import...3 1.1 What is Bankline import?...3 1.2 How
Foreign payment orders
p. 1 Foreign payment orders The Foreign payment orders bank standard deals with the electronic exchange of payment orders in euro or in foreign currencies transmitted by the customer to his bank. For payments
ISO 20022 Message Implementation Guide for Cash Management Reports
ISO 20022 Message Implementation Guide for Cash Management Reports CAMT052 CAMT053 CAMT054 CAMT060 Version: 1.7 Issue date: 16 November 2015 Author: Swedbank Table of Contents 1. Introduction 2. Bank To
Guide for Ruble Payments 02.05.2016
Guide for Ruble Payments 02.05.2016 How to fill in a Foreign Payment order 2/13 Required details of ruble payments 1. The beneficiary's name in Russian written in Latin alphabet according to the transliteration
Format Description. SWIFT MT103 Single Customer Credit Transfer
De Format Description SWIFT MT103 Single Customer Credit Transfer COLOPHON Title Format Description SWIFT MT103 Version, date 1.3, June 2015 On behalf of Contact address Corporate Client Channels Rabobank
QUICK REFERENCE GUIDE. ING Payment Processing Offer in XML
QUICK REFERENCE GUIDE TABLE OF CONTENTS 1. ING PAYMENT PROCESSING TYPES... 3 2. ENCODING... 4 2.1. How to request the different payment processing?... 4 2.2. Standard Payment Processing... 4 2.3. Urgent
499.35 en (pf.ch/dok.pf) 11.2015 PF. EPO manual Electronic payment order via file transfer
499.35 en (pf.ch/dok.pf) 11.2015 PF EPO manual Electronic payment order via file transfer Customer support Customer support for EPO Consulting & Sales Phone +41 848 888 900 (CHF 0.08/min. from a landline)
Format Description SWIFT MT940 Structured
Format Description SWIFT MT940 Structured Rabo Cash Management Colophon Title Format Description SWIFT MT940 Structured Version, date 3.331, November 2014 On behalf of Zakelijke Klantkanalen Contact address
Payments Standards - Clearing and Settlement
UNIFI (ISO 20022) Message Definition Report Payments Standards - Clearing and Settlement Approved by UNIFI Payments SEG on 06 June 2006 Edition July 2006 Table Of Contents Overview... 1 What does this
BEST client format supported by KB (valid from 28th November 2015)
supported by KB (valid from 28th November 2015) 1/19 List of contents: 1 Introduction... 4 1.1 Purpose of this document... 4 1.2 Characteristics of BEST format... 4 2 Formal check of BEST format... 4 2.1
Payments Market Practice Document. ISITC Settlements Working Group
Payments Market Practice Document ISITC Settlements Working Group Publication Date: October, 2012 Author(s): ISITC Settlements Working Group DISCLAIMER This market practice document has been developed
SEPA Direct Debit Unpaid Report File Format
SEPA Direct Debit Unpaid Report File Format PAIN.002.001.03 XML File Structure This document is published by Bank of Ireland, and both it, and its contents, are the property of Bank of Ireland. This document
Format description SEPA DD ISO20022 (for Euro Direct Debits)
Format description SEPA DD ISO20022 (for Euro Direct Debits) Version, date Project 1.4, 24 April 2013 Rabo Cash Management 1 Colophon Title SEPA Direct Debit format description Version, date 1.4, 24 April
Format Description MT940. Rabo Cash Management
Format Description MT940 Rabo Cash Management COLOFON Title Format Description MT940 Version, date 2.4, January 2013 On behalf of Contact address FL-Services Rabobank Nederland, Croeselaan 18, Postbus
SEPA CBI XML generator Documentation
SEPA CBI XML generator Documentation Release 0.1.0 Emanuele Pucciarelli July 06, 2014 Contents 1 Introduction 3 2 Quick start 5 3 Usage 7 4 The IdHolder class 9 5 The Payment class 11 5.1 Adding transactions...........................................
XML Message for SEPA Direct Debit Initiation
XML Message for SEPA Direct Debit Initiation Core and Business-to-Business Implementation Guidelines Version 1.2 Table of Contents 1 Introduction... 4 1.1 SEPA Direct Debit definition... 5 1.2 Message
Changes only affecting customers using SWIFT codewords, Intermediary Institutions, or with other special requirements
Bankline File Import Guide 1. Introduction This document describes the changes effective April 2008 for the Bankline Internet Banking Import File Layout User Guide. In overview, the changes are as follows.
Russian Rouble payment requirements.
Russian Rouble payment requirements. When making payments in Russian Roubles (RUB) there are requirements, set by the Russian Central Bank, to include identifying codes on certain payments An INN code
Notes for foreign currency payments at HSBC
Notes for foreign currency payments at HSBC There are some foreign currencies that require on the part of HSBC specific indications to process payment orders Currently, this applies to the following currencies:
Deutsche Bank Global Transaction Banking. Internet Bankieren. Entering Payments and Collections. www.deutschebank.nl
Deutsche Bank Global Transaction Banking Internet Bankieren Entering Payments and Collections www.deutschebank.nl Internet Bankieren Entering Payments and Collections 2 Entering payments and collections
User Manual Internet Banking Enter and Send Orders
This manual of ABN AMRO Internet Banking describes how to enter payment orders, stock orders, investment orders and how to send your orders to the bank. You can enter a maximum of 45 orders for dispatch.
ELECTRONIC BANKING. RFT MT101 File Format Description Ver. 2009-09-28
ELECTRONIC BANKING RFT MT101 File Format Description Ver. 2009-09-28 CONTENTS: 1. RFT MT101 File Format Description 3 2. Detailed MT101 File Format Description 3 2.1 Key to description of the records 3
The updated list of most used VO codes.
The updated list of most used VO codes. VO code Type of operation 02 FX transactions 02 010 Purchase of RUB currency by non-resident 02 020 Selling of RUB currency by non-resident 10 Settlements for goods,
International ACH Transactions (IAT) File Format Guide
U.S Bank created this IAT file format guide to be used as a supplemental tool to the format listed in the NACHA rules. Organizations can use this to help make changes in their system to prepare for the
Swedbank Business Internet Banking User Manual
Swedbank Business Internet Banking User Manual Content Introduction 1. HOW TO START 1.1 USING INTERNET BANKING 1.2 TERMINATING INTERNET BANKING SESSION 2. INTERNET BANKING SECURITY 2.1 PASSWORD SYSTEM
Electronic foreign currency payments, LUM2
Electronic foreign currency payments, LUM2 Contents 1 Electronic foreign currency payment service... 3 2 Service agreement and testing... 3 2.1 Agreement... 3 2.2 Testing... 4 2.2.1 File transfer and processing...
Coded statement of account (CODA)
12/07/2012 Coded statement of account (CODA) This bank standard (also called CODA) specifies the lay-out for the electronic files, by banks to customers, of the account transactions and the information
TERMS AND CONDITIONS OF PAYMENT ORDER IN FOREIGN EXCHANGE TRANSACTIONS AT PKO BP SA BANK
TERMS AND CONDITIONS OF PAYMENT ORDER IN FOREIGN EXCHANGE TRANSACTIONS AT PKO BP SA BANK TABLE OF CONTENTS SECTION 1 General provisions... 1 I. General rules for payment execution in foreign exchange transactions...
Payments Statistics Return (PSA)
Payments Statistics Return (PSA) Notes on Compilation Incorporating FAQ Version 1.1 4 March 2015 Email: [email protected] Website: http://www.centralbank.ie/ Version Date Comment V1.1 4 March 2015
Swedish Common Interpretation of ISO 20022 Payment Messages. Appendix 1: Common Payment Types in Sweden
Swedish Common Interpretation of ISO 20022 Payment Messages Appendix 1: 2 (27) Version Date Changes 0.1 2013-12-11 Initial version 1.0 2014-02-10 Updates after external review Page 5: Added that BG/PG
Functional specification for Payments Corporate egateway
Functional specification for Payments Corporate egateway 2(53) Page Table of contents 1 Introduction... 5 1.1 Explanation of definitions for EDIFACT & XML ISO20022 6 1.2 Level descriptions for EDIFACT
Hal E-Bank Foreign payments (Format of export/import files)
Hal E-Bank Foreign payments (Format of export/import files) Hal E-Bank Foreign payments: format of export/import files Version: 17.x.x.20 Author: HALCOM d.d., Ljubljana Editor: HALCOM a.d., Beograd, July
How To Use Danske Internet Bank
Short description of services offered to business customers in Danske Internet Bank Field of activity Entry to Danske Internet Bank Accounts Services Agreements Security elements Account balance Account
User's manual for OTPdirekt Internet Banking. v.1.0
User's manual for OTPdirekt Internet Banking v.1.0 1 Contents General... 4 Log in... 4 Logging out... 4 Home page... 5 Accounts... 5 Accounts - Overview of movements... 6 Accounts - OTPdirekt transactions...
SEPA Direct Debit Initiation Customer-to-Bank Implementation Guidelines for the Netherlands
SEPA Direct Debit Initiation Customer-to-Bank Implementation Guidelines for the Netherlands CORE and Business-to-Business Implementation Guidelines Disclaimer These guidelines may be subject to changes.
Foreign Payment Operations in Direct Banking of UniCredit Bank Czech Republic and Slovakia, a.s.
Foreign Payment Operations in Direct Banking of UniCredit Bank Czech Republic and Slovakia, a.s. BusinessNet User Handbook April 2015 2 3 INTRODUCTION Dear Client Foreign payment operations have developed
SEPA formats - an introduction to XML. version September 2013. www.ing.be/sepa
Financial Supply Chain SEPA SEPA formats - an introduction to XML version September 2013 www.ing.be/sepa INTRODUCTION 1 INTRODUCTION TO XML 2 What is XML? 2 What is a root element? 2 What are the specifications
SEPA Credit Transfer Customer-to-Bank Implementation Guidelines for the Netherlands
SEPA Credit Transfer Customer-to-Bank Implementation Guidelines for the Netherlands Disclaimer These guidelines may be subject to changes. Utmost care has been taken to ensure the information in this publication
1.1. Overview... 5 1.2. Direct credits... 6 1.3. Direct debits... 9 1.4. Nab direct credits... 12
1.1. Overview... 5 1.2. Direct credits... 6 1.3. Direct debits... 9 1.4. Nab direct credits... 12 2.1. Overview... 16 2.2. Credit card transaction... 17 2.3. Credit card response... 20 3.1. Overview...
File format DETAILS RECORD TYPES ABBREVIATIONS (LEGEND) GENERAL REMARKS. Welcome to
Consolidated electronic payment order format for national payments in hrk, national payments in foreign currency, international payments in hrk or foreign currency and personal income payments 1 Applied
Format description of MT103 (Multicash PLA) foreign payment file.
Format description of MT103 (Multicash PLA) foreign payment file. 1 General information about MT103 file This document explains formats of MT103 file - used to import International / Foreign Currency Order
How To Create A Credit Card From A Creditcard In A Microsoft Web Server On A Microsql Web Server
Appendix to Danish Message Implementation Guideline for Common Global Implementation (CGI) Customer Credit Transfer Initiation and Danish Implementation Guideline for CGI Customer Payment Status Report
Internet Banking for Business
INTERNET BANKING FOR BUSINESS Information you need to know about importing transaction files into Internet Banking for Business For more info bnz.co.nz Internet Banking for Business. This guide provides
ANZ TRANSACTIVE FILE FORMATS WEB ONLY 07.2013. Page 1 of 118
ANZ TRANSACTIVE FILE FORMATS WEB ONLY 07.2013 Page 1 of 118 ANZ Transactive and ANZ Transactive - Mobile are provided by Australia and New Zealand Banking Group Limited (ACN 005 357 522). References to
OP's C2B SERVICES Pain 03. Payment Transfer Products
OP's C2B SERVICES Pain 03 Payment Transfer Products Customer Guidelines March 2015 2/104 Version Key Changes Changed section November 2012 added money orders 13 C2B money orders July 2013 updated payment
SEPA. Changes in the Payment System Implementation of the European SEPA Regulations for Kuna and Euro Payments
SEPA Changes in the Payment System Implementation of the European SEPA Regulations for Kuna and Euro Payments SEPA The Single Euro Payments Area (SEPA) stands for a European Union (EU) payments integration
Form Payments statistics (formerly form-9006)
Form Payments statistics (formerly form-9006) General The report contains data on payments, specifically payments between consumers, businesses and the government. As of July 2014, this report implements
Implementation of ISO 20022: starter kit for software partners
Insert images: Swiss Post menu > image > insert image. For more images go to www.brandingnet.ch Technical details Full screen image size W 25.4 cm x H 19.05 cm equals W 1500 pixels x H 1125 pixels Resolution
TERMS AND CONDITIONS APPLICABLE TO CREDIT INSTITUTIONS
ERSTE BANK HUNGARY ZRT TERMS AND CONDITIONS APPLICABLE TO CREDIT INSTITUTIONS Effective from: 01 September 2014 1. General Provisions 1.1. These Terms and Conditions (hereinafter TC ) apply to all correspondent
More information on completing payment details
More information on completing payment details Agreement number [applicable to Transfer from account abroad] Enter reference number for agreed rate or forward rate. Amount Enter the amount, and specify
MT 103+ Single Customer Credit Transfer
MT 103+ Single Customer Credit Transfer The MT 103+ is a General Use message, ie, no registration in a Message User Group is necessary to send and receive this message. It allows the exchange of single
Cash Management Balance Reporting Specifications Version 2. Technical Reference Manual
Cash Management Balance Reporting Specifications Version 2 Technical Reference Manual 10/2005 Printed in the United States of America Copyright 2005 by BAI, Chicago, Illinois All rights reserved. No part
SEPA DIRECT DEBIT SCHEME IMPLEMENTATION GUIDELINES
Doc: EPC114-06 19 June 2007 (Version 2.3 ) OITS SG SEPA DIRECT DEBIT SCHEME IMPLEMENTATION GUIDELINES Abstract Document Reference Issue This document sets out the SEPA rules for implementing the direct
CHARGES CATALOGUE. For Individuals and Small Companies:
The Charges Catalogue includes the usual charges that are currently valid as well as upcoming charges with their implementation date. The Charges Catalogue is reviewed at fixed intervals and is being also
LECTURE No.9 INSTRUMENTS OF PAYMENT
LECTURE No.9 INSTRUMENTS OF PAYMENT Cash and cash instruments The cashier s work consists in receiving cash and cash instruments such as cheques and other instruments ( documents of title to cash ) in
Collection Information Statement for Wage Earners and Self-Employed Individuals
Georgia Department of Revenue Collection Information Statement for Wage Earners and SelfEmployed Individuals Form CD14C (June 2012) Use this form if you are An individual who owes income tax on a Form
Service description. Corporate Access Payables
Service description Corporate Access Payables Table of contents Page 2 of 12 1 INTRODUCTION... 3 2 STRUCTURE OF DOCUMENTATION... 4 3 AGREEMENT SET-UP... 4 4 AVAILABLE MESSAGE TYPES... 5 5 OFFERED PAYMENT
Switching your Business Current Accounts
Switching your Business Current Accounts Summary of the Key Features of the Account Switching Code for Business customers Bank of Ireland ("New Bank") can facilitate all the steps required in order to
Rien que pour vos flux :
Rien que pour vos flux : La payment factory et les comptes virtuels au service des transferts pour compte de From SEPA compliance to benefits COBO Payment On Behalf Of POBO SEPA benefits Central Payment
Health Insurance Companies Tab. Monthly cash inflows and outflows of public health insurance companies
Health Insurance Companies Tab. Monthly cash inflows and outflows of public health insurance companies Coverage: Health insurance companies operating in the field of public health insurance, which are
2 P a g e. V. Content of order-receipt Art.18. An order-receipt submitted to the Bank shall contain the following details:
General Terms and Conditions of TEXIM BANK AD To Framework Agreement for Opening and Maintenance of Bank Payment Accounts and Execution of Payment Transactions These General Terms and Conditions shall
REPORTING INSTRUCTIONS FOR INVESTMENT FUNDS
REPORTING INSTRUCTIONS FOR INVESTMENT FUNDS 1. Reporting policies & procedures 1.1 The Excel file Investment Funds Returns (FORM STAT 001) - contains three sheets (Assets, Liabilities and Memorandum Items).
SWIFT MT940 MT942 formats for exporting data from OfficeNet Direct
SWIFT MT940 MT942 formats for exporting data from OfficeNet Direct January 2008 2008 All rights reserved. With the exception of the conditions specified in or based on the 1912 Copyright Act, no part of
Collection Information Statement for Wage Earners and Self-Employed Individuals
Form 433-A (Rev. December 2012) Department of the Treasury Internal Revenue Service Collection Information Statement for Wage Earners and Self-Employed Individuals Wage Earners Complete Sections 1, 2,
Make payments. Bankline support guides: In this guide. How to make a standard domestic payment. Did you know? Page 1
Bankline support guides: Make payments In this guide Learn how to make standard domestic payments and CHAPS payments. Learn how to transfer money between your accounts. Learn how to make international
