camt Debit Notification BankToCustomerDebitCreditNotificationV02

Transcription

1 orporate Access Payables Message Implementation Guidelines camt Debit Notification BankToustomerDebitreditNotificationV02 These Message Implementation Guidelines only include a description of Debit entries. MIG version: 1.3 : eference to rouble (UB) payments to be launched mid-november 2017 eference to Finland expected, as previously announced, to be launched during November 2017, with full customer access in Q1 2018

2 amt Debit Notification orporate Access Payables version of 17 Table of contents 1. Introduction About orporate Access Payables Bank Transaction odes usage of XML format Document references Guidelines Appendix 1 Bank Transaction odes Debit entries...16

3 amt Debit Notification orporate Access Payables version of Introduction These Message Implementation Guidelines (MIG) were prepared on behalf of Group (hereinafter ). The purpose of this documentation is to define how information in a debit advice message is structured for the exchange between and the message receiver. These Message Implementation Guidelines comply with the international definitions for content and use of an camt BankToustomerDebitreditNotification and ommon Global Implementation (GI) recommendations, which are available at: GI link 2. About orporate Access Payables orporate Access Payables is s file-based payment solution. The service will enable s customers to execute harmonised and straightforward ordinary commercial (incl. SEPA) payments as well as salaries, pension, urgent and cross-border/cross-currency payments from accounts in all the countries in the Nordic region. In return, the customer will receive status reports and debit advice. Financial, commercial same-day-value and cash-pool payments will be included in a later release. This release (v. 1.3), which is the latest version for all included countries, i.e. Denmark, Finland, Norway and Sweden, also includes the possibility for customers to perform cancellation of payments, sent in pain , by use of Message type camt (ustomerpaymentancellationequest). will as a response to Message camt send Message types pain and camt (i.e. esolutionofinvestigation). Note: This document may be subject for future changes and will in those cases be duly informed by. The Bank-to-ustomer Debit Notification message is sent by to an account owner or to a party authorised by the account owner to receive the message. It can be used to inform the account owner, or authorised party, of single or multiple debit entries reported to the account. Only transactions sent to orporate Access Payables in pain will be reported back in the camt For further detailed information about how creates the Bank-to-ustomer Debit Notification, the service and its offering, definition of parties involved, as well as technical information to support customer s implementation, will be found in orporate Access Payables Service description r guide & Message flow, which can be found on: nordea.com/corporateaccess. 3. Bank Transaction odes Bank Transaction odes are used to define which types of transactions are reported in the notification. uses the standard codes according to. Appendix 1 provides further details.

4 amt Debit Notification orporate Access Payables version of usage of XML format The term message is used for one XML schema occurrence, which is a combination of blocks called Group Header, Notification, Entry and TransactionDetails information. One file will only contain one Message. A message sent by can contain Notifications for several Debtors/accounts as agreed under the orporate ash Management agreement with. Each Notification will include one or more Entry s whereas, dependent on booking option chosen by Debtor/ustomer, each Entry will consist of one or more TransactionDetails. All elements or tags defined as Mandatory by for camt are included in s orporate Access Payables MIG. This also includes elements or tags that are optional or conditional, depending on specific criteria, as set by the service (or local country infrastructure). Elements or tags not used by the service are not included in this MIG, even if they are included in the Message Definition eport or in the GI Implementation Guide for BankToustomerDebitredit Notification. This is to enable a smooth introduction of the service for potential users. The following is a description of used fields and columns in the MIG: No = eference number that refers to the related description in the Message Definition eport sequence = Informs about which level a specific field is placed within the XML structure Or = will provide one or the other field, but not both Message Item = efers to the actual tag name in XML, which is also stated under the column XML Tag Name. This can be a Message element (a.k.a. a field in a traditional sense), or a Message omponent (i.e. a group of information consisting of several elements). Each message element is stated with the element type it comprises (stated under column Type). XML Tag = Specific code referring to an XML element, and will be part of the XML Schema for the identification of an XML element. The Tag Name will be stated at the beginning of a string which is to include the required information (i.e. <Dbtr>) and will end the string with the same Tag Name, starting with a slash (i.e. </Dbtr>). Multiplicity = Informs how many times an element can or must be used, as defined by One occurrence (required) 1..n One or several occurrences (value for n represents total number of occurrences) 1..3 Minimum one occurrence must be used and maximum 3 occurrences can be used. Note: True value of n represents unlimited number of occurrences None or one occurrence to be used (optional) 0..n None or several occurrences can be used (value for n represents total number of occurrences) Note: True value of n represents unlimited number of occurrences. Type = States the value to be transferred in the actual XML element. There are a total of seven different Data Type representations that can be used in a BankToustomerDebitreditNotification : Identifier, ode, Text, ate, Time, Amount & Indicator. See examples below:

5 amt Debit Notification orporate Access Payables version of 17 Data Type Type Example Identifier PartyId SALES OMPANY PATY ode PaymentMethod3ode 2.2 TF = redit Transfer Text Max35Text 2.1 AA22BB11 ate ate Time Time T05:32:31Z Amount DecimalNumber Indicator Indicator 2.3 true = Batch booking requested = This column states the classification uses for each tag/element in this MIG uses the classification 1..n as mandatory and 0..n for optional usage. uses a slightly more gradient classification, such as: Attribute ode Terminology Definition equired Mandatory by or equired by GI. XO exlusive Or Select either field, but not both onditional Dependent upon certain conditions or optional to use by comment = Informs of special rules or usage for each element. If no comments exist, then standard usage according to applies. The files sent by will be in UTF-8 format. For information/description about technical issues such as security, retransmissions, or duplicates, please see Service description for orporate Access FileTransfer & orporate Access Payables at nordea.com/corporateaccess More information on definitions on camt is available on the website: Link 5. Document references This chapter contains references to documents relevant for this MIG: Message Definition eport, Edition December 2009 ( Link ) camt , BankToustomerDebitreditNotificationV02

6 amt Debit Notification orporate Access Payables version of Guidelines comment - Bank To ustomer Debit Notification V02 <BkTostmrDbtdtNtfctn> Message root, identifying message type GroupHeader <GrpHdr> [1..1] GroupHeader MessageIdentification <MsgId> [1..1] Max35Text Identification created by and will be unique for min. 90 calendar days reationtime <redttm> [1..1] Time and time at which the message was created. applies UT or local time. Example: T05:32:31Z Messageecipient <Msgcpt> [0..1] PartyIdentification32 This item identifies the recipient(s), as agreed with. Only identifications registered by will be provided Identification <Id> [0..1] Party6hoice OrganisationIdentification <OrgId> [1..1] OrganisationIdentification {Or BIOrBEI <BIOrBEI> [0..1] AnyBIIdentifier XO Identification as used by receipient in sent pain to Or} Other <Othr> [0..n] GenericOrganisationIdentification1 XO Identification <Id> [1..1] Max35Text ustomer identification as agreed with (or assigned by). If BIOrBEI not used to identify recipient then Other Identification as assigned by will be used with code UST. ode BANK will always be present (i.e. sender) with value NDEAPOD, indicating that the file is sent from s production environment SchemeName <SchmeNm> [0..1] OrganisationIdentificationSchemeName1hoice ode <d> [1..1] ExternalOrganisationIdentification1ode d codes: BANK BankPartyIdentification () UST ustomer number AdditionalInformation <AddtlInf> [0..1] Max500Text d code: /DEBT/ Notification with Debit entries ONLY Notification <Ntfctn> [1..n] AccountNotification2 Each notification contains one account.

7 amt Debit Notification orporate Access Payables version of 17 comment Identification <Id> [1..1] Max35Text Unique identification, as assigned by the account servicer, to unambiguously identify the account notification. Unique at for min. 90 calendar days. Note: will use date/time (i.e. YYYYMMDDHHMMSS), currency and last four (4 digits) of the reported account reationtime <redttm> [1..1] Time and time at which the notification was created. Expressed using UT designator [Z] with or without offset. Example: T05:32:31Z Account <Acct> [1..1] ashaccount20 ustomers can choose to have the account number reported as IBAN or BBAN Identification <Id> [1..1] AccountIdentification4hoice {Or IBAN <IBAN> [1..1] IBAN2007Identifier XO Finland: Only IBAN available Or} Other <Othr> [1..1] GenericAccountIdentification1 XO Identification <Id> [1..1] Max34Text SchemeName <SchmeNm> [0..1] AccountSchemeName1hoic e ode <d> [1..1] ExternalAccountIdentification1ode urrency <cy> [0..1] ActiveOrHistoricurrencyode Servicer <Svcr> [0..1] BranchAndFinancialInstitutionIdentification4 d code: BBAN FinancialInstitutionIdentification <FinInstnId> [1..1] FinancialInstitutionIdentification {Or BI <BI> [0..1] BIIdentifier XO Bank Denmark = NDEADKKK Bank Finland = NDEAFIHH Bank Norway = NDEANOKK Bank Sweden = NDEASESS Or} learingsystemmemberidentification <lrsysmmbid> [0..1] learingsystemmemberidentification learingsystemidentification <lrsysid> [0..1] learingsystemidentification2hoice ode <d> [1..1] ExternallearingSystemIdentification1ode XO Only used for Sweden. Will be used if learingsystemidentification used by Debtor in pain d code: SESBA Swedish Bankers Association

8 amt Debit Notification orporate Access Payables version of 17 comment MemberIdentification <MmbId> [1..1] Max35Text Valid branch number 9960 for Plusgiro PostalAddress <PstlAdr> [0..1] PostalAddress ountry <try> [0..1] ountryode d codes: DK = Denmark FI = Finland NO = Norway SE = Sweden Entry <Ntry> [0..n] eportentry2 Set of elements used to specify an entry in the notification Entryeference <Ntryef> [0..1] Max35Text Increased by one (1) for each entry Amount <Amtcy="AAA"> [1..1] ActiveOrHistoricurrencyAndAmount reditdebitindicator <dtdbtind> [1..1] reditdebitode d code: DBIT Debit Posted amount in the currency of the account reported and is the total of one or many entry details. Note: This amount can be zero for Norway and Sweden Status <Sts> [1..1] EntryStatus2ode d code: BOOK Booked Booking <BookgDt> [0..1] AndTimehoice Booking date will always be present <Dt> [1..1] Value <ValDt> [0..1] AndTimehoice Value date will always be present <Dt> [1..1] AccountServicereference <AcctSvcref> [0..1] Max35Text : Not used. See also under Transaction Detail level BankTransactionode <BkTxd> [1..1] BankTransactionode- Transaction odes are used (see Appendix 1). Structure Domain <Domn> [0..1] BankTransactionode- Transaction odes are used (see Appendix 1). Structure ode <d> [1..1] ExternalBankTransactionDomain1ode Family <Fmly> [1..1] BankTransactionode- Transaction odes are used (see Appendix 1). Structure ode <d> [1..1] ExternalBankTransactionFamily1ode SubFamilyode <SubFmlyd> [1..1] ExternalBankTransactionSub- Family1ode EntryDetails <NtryDtls> [0..n] EntryDetails1 Set of elements used to provide details on the entry TransactionDetails <TxDtls> [0..n] EntryTransaction2 Set of elements used to provide information on the underlying transaction(s).

9 amt Debit Notification orporate Access Payables version of eferences <efs> [0..1] Transactioneferences2 comment MessageIdentification <MsgId> [0..1] Max35Text MessageIdentification as sent in pain AccountServicereference <AcctSvcref> [0..1] Max35Text Denmark: Will be reported when available. Finland, Norway & Sweden: Will always be present PaymentInformationIdentification <PmtInfId> [0..1] Max35Text PaymentInformationIdentification as sent in pain InstructionIdentification <InstrId> [0..1] Max35Text InstructionIdentification will be present if sent by customer in pain EndToEndIdentification <EndToEndId> [0..1] Max35Text Will always be present as sent by customer in pain AmountDetails <AmtDtls> [0..1] AmountAndurrencyExchange InstructedAmount <InstdAmt> [0..1] AmountAndurrencyExchangeDetails Amount <Amtcy="AAA"> [1..1] ActiveOrHistoricurrencyAndAmount TransactionAmount <TxAmt> [0..1] AmountAndurrencyExchangeDetails Amount <Amtcy="AAA"> [1..1] ActiveOrHistoricurrencyAndAmount urrencyexchange <cyxchg> [0..1] urrencyexchange5 Will always be reported as received by customer in pain Will always be present. Norway & Sweden: Zero amount is possible i.e. digit "0" may occur Sourceurrency <Srccy> [1..1] ActiveOrHistoricurrencyode Targeturrency <Trgtcy> [0..1] ActiveOrHistoricurrencyode Exchangeate <Xchgate> [1..1] BaseOneate Exchange rate will be stated with maximum 11 digits including 6 decimals. will currently present currency exchange rate as expressed by the local country, i.e. against currency base de-nominations "1" or "100". For further information about used currency base denominations and exchange rates, please see ountry Appendix, chapter ontractidentification <trctid> [0..1] Max35Text Norway & Sweden: Not used ountervalueamount <ntrvalamt> [0..1] AmountAndurrencyExchangeDetails Amount <Amtcy="AAA"> [1..1] ActiveOrHistoricurrencyAndAmount BankTransactionode <BkTxd> [0..1] BankTransactionode- Structure4 Will only be present when Equivalent amount used by customer in pain Transaction odes are used (see Appendix 1).

10 amt Debit Notification orporate Access Payables version of Domain <Domn> [0..1] BankTransactionode- Structure ode <d> [1..1] ExternalBankTransactionDomain1ode Family <Fmly> [1..1] BankTransactionode- Structure ode <d> [1..1] ExternalBankTransactionFamily1ode SubFamilyode <SubFmlyd> [1..1] ExternalBankTransactionSub- Family1ode comment Transaction odes are used (see Appendix 1). Transaction odes are used (see Appendix 1) harges <hrgs> [0..n] hargesinformation6 harges will only be reported for Denmark, if available, as information for customer and will not be included in the Entry or EntryDetail amount(s) Amount <Amtcy="AAA"> [1..1] ActiveOrHistoricurrencyAndAmount Bearer <Br> [0..1] hargebearertype1ode d codes: DEBT BorneByDebtor SHA Shared SLEV Following Service Level. (Only for SEPA payments) elatedparties <ltdpties> [0..1] TransactionParty2 Note: For SEPA payments will report SLEV as used charge code UltimateDebtor <UltmtDbtr> [0..1] PartyIdentification32 Will be returned by, if used by customer in pain Name <Nm> [0..1] Max140Text PostalAddress <PstlAdr> [0..1] PostalAddress StreetName <StrtNm> [0..1] Max70Text BuildingNumber included in StreetName Postode <Pstd> [0..1] Max16Text TownName <TwnNm> [0..1] Max35Text ountry <try> [0..1] ountryode AddressLine <AdrLine> [0..7] Max70Text Identification <Id> [0..1] Party6hoice OrganisationIdentification <OrgId> [1..1] OrganisationIdentification Other <Othr> [0..n] GenericOrganisationIdentification Identification <Id> [1..1] Max35Text

11 amt Debit Notification orporate Access Payables version of SchemeName <SchmeNm> [0..1] OrganisationIdentificationSchemeName1hoice ode <d> [1..1] ExternalOrganisationIdentification1ode reditor <dtr> [0..1] PartyIdentification Name <Nm> [0..1] Max140Text d code: UST ustomernumber comment PostalAddress <PstlAdr> [0..1] PostalAddress StreetName <StrtNm> [0..1] Max70Text BuildingNumber included in StreetName Postode <Pstd> [0..1] Max16Text TownName <TwnNm> [0..1] Max35Text ountry <try> [0..1] ountryode AddressLine <AdrLine> [0..7] Max70Text Identification <Id> [0..1] Party6hoice {Or OrganisationIdentification <OrgId> [1..1] OrganisationIdentification4 XO Other <Othr> [0..n] GenericOrganisationIdentification Identification <Id> [1..1] Max35Text Will be present as sent in pain SchemeName <SchmeNm> [0..1] OrganisationIdentificationSchemeName1hoice ode <d> [1..1] ExternalOrganisationIdentification1ode d codes: UST ustomernumber TXID TaxIdentificationNumber Or} PrivateIdentification <PrvtId> [1..1] PersonIdentification5 XO : TXID used for UB payments towards ussia Denmark: TXID used for V no. as Id Other <Othr> [0..n] GenericPersonIdentification Identification <Id> [1..1] Max35Text Will be present as sent in pain SchemeName <SchmeNm> [0..1] PersonIdentificationSchemeName1hoice

12 amt Debit Notification orporate Access Payables version of ode <d> [1..1] ExternalPersonIdentification1ode comment d code: SOSE SocialSecurityNumber TXID TaxIdentificationNumber Other <Othr> [0..1] Text reditoraccount <dtracct> [0..1] ashaccount16 : TXID used for UB payments towards ussia Denmark: SOSE used for P no. as Id Identification <Id> [1..1] AccountIdentification4hoice {Or IBAN <IBAN> [1..1] IBAN2007Identifier XO Or} Other <Othr> [1..1] GenericAccountIdentification1 XO Identification <Id> [1..1] Max34Text SchemeName <SchmeNm> [0..1] AccountSchemeName1hoic e {{Or ode <d> [1..1] ExternalAccountIdentification1ode XO d code: BBAN Or}} Proprietary <Prtry> [1..1] Max35Text XO d codes: BGN BankGiro Number O Nets reditor Number Ultimatereditor <Ultmtdtr> [0..1] PartyIdentification32 Will be returned by, if used by customer in pain Name <Nm> [0..1] Max140Text Identification <Id> [0..1] Party6hoice {Or OrganisationIdentification <OrgId> [1..1] OrganisationIdentification4 XO Other <Othr> [0..n] GenericOrganisationIdentification Identification <Id> [1..1] Max35Text SchemeName <SchmeNm> [0..1] OrganisationIdentificationSchemeName1hoice ode <d> [1..1] ExternalOrganisationIdentification1ode Or} PrivateIdentification <PrvtId> [1..1] PersonIdentification5 XO d code: UST ustomernumber

13 amt Debit Notification orporate Access Payables version of Other <Othr> [0..n] GenericPersonIdentification1 comment Identification <Id> [1..1] Max35Text SchemeName <SchmeNm> [0..1] PersonIdentificationSchemeName1hoice ode <d> [1..1] ExternalPersonIdentification1ode elatedagents <ltdagts> [0..1] TransactionAgents2 d code: SOSE SocialSecurityNumber DebtorAgent <DbtrAgt> [0..1] BranchAndFinancialInstitutionIdentification FinancialInstitutionIdentification <FinInstnId> [1..1] FinancialInstitutionIdentification BI <BI> [0..1] BIIdentifier Bank Denmark = NDEADKKK Bank Finland = NDEAFIHH Bank Norway = NDEANOKK Bank Sweden = NDEASESS reditoragent <dtragt> [0..1] BranchAndFinancialInstitutionIdentification4 Only used for International (cross-border/cross-currency) payments, but not for International cheques FinancialInstitutionIdentification <FinInstnId> [1..1] FinancialInstitutionIdentification BI <BI> [0..1] BIIdentifier Will be reported if received from local clearing system learingsystemmemberidentification <lrsysmmbid> [0..1] learingsystemmemberidentification learingsystemidentification <lrsysid> [0..1] learingsystemidentification2hoice ode <d> [1..1] ExternallearingSystemIdentification1ode Will be reported if MemberIdentification received from local clearing system and will then be returned as used by customer in pain MemberIdentification <MmbId> [1..1] Max35Text Will be reported if received from local clearing system Name <Nm> [0..1] Max140Text Will be reported if received from local clearing system, otherwise returned as used by customer in pain PostalAddress <PstlAdr> [0..1] PostalAddress ountry <try> [0..1] ountryode Will be reported if received from local clearing system IntermediaryAgent1 <IntrmyAgt1> [0..1] BranchAndFinancialInstitutionIdentification4 Will only be reported for Intercompany payments, if used by customer in pain , and Intermediary Agent outside Group. Denmark & Sweden: Not used

14 amt Debit Notification orporate Access Payables version of FinancialInstitutionIdentification <FinInstnId> [1..1] FinancialInstitutionIdentification BI <BI> [0..1] BIIdentifier comment Purpose <Purp> [0..1] Purpose2hoice Will only be reported if used by customer in pain {Or ode <d> [1..1] ExternalPurpose1ode XO Will only be reported for SEPA payments, if used by customer in pain Or} Proprietary <Prtry> [1..1] Max35Text XO Will only be reported for domestic payments, if used by customer in pain emittanceinformation <mtinf> [0..1] emittanceinformation Unstructured <Ustrd> [0..n] Max140Text Structured <Strd> [0..n] StructuredemittanceInformation eferreddocumentinformation <frddocinf> [0..n] eferreddocumentinformation Type <Tp> [0..1] eferreddocumenttype odeorproprietary <dorprtry> [1..1] eferred- DocumentType1hoice ode <d> [1..1] DocumentType5ode d codes: INV ommercial Invoice EN reditnote Number <Nb> [0..1] Max35Text Willl be reported if present elated <ltddt> [0..1] Willl be reported if present eferreddocumentamount <frddocamt> [0..1] emittanceamount1 Will always be present reditnoteamount <dtnoteamtcy="aaa"> [0..1] ActiveOrHistoricurrencyAndAmount emittedamount <mtdamtcy="aaa"> [0..1] ActiveOrHistoricurrencyAndAmount reditoreferenceinformation <dtrefinf> [0..1] reditoreferenceinformation Type <Tp> [0..1] reditoreferencetype2 Will be reported together with code EN Will be reported together with code INV If reditor eference used by customer in pain , it will always be reported back with code SO in camt.054 Debit Notification, this irrespectively if local clearing might have processed the payment as a nonstructured reference payment towards beneificiary odeorproprietary <dorprtry> [1..1] reditoreferencetype1hoice ode <d> [1..1] DocumentType3ode d code: SO Structuredommunicationeference

15 amt Debit Notification orporate Access Payables version of Issuer <Issr> [0..1] Max35Text d code: comment eference <ef> [0..1] Max35Text : will be reported for international creditor reference.

16 amt Debit Notification orporate Access Payables version of Appendix 1 Bank Transactoin odes Debit entries 1.1 Debit entries text code ountry Domain Family Sub-family Domain Family Subfamily Entry level All - Domestic Payments Issued redit Transfers AH Debit PMNT IDT ADT All - International Payments Issued redit Transfers ross-border redit Transfer PMNT IDT XBT All Non identified Payments Not available Not available PMNT NTAV NTAV Entry Detail level Denmark Payments Issued redit Transfer Domestic redit Transfer PMNT IDT DMT Denmark Payments Issued redit Transfers ross-border redit Transfer PMNT IDT XBT Denmark Payments Issued heques Foreign heque PMNT IHQ XBQ Denmark Payments Issued redit Transfers Payroll/Salary Payment PMNT IDT SALA Denmark Payments Issued ash oncentration Transactions Intra ompany Transfer PMNT IN IT Denmark Payments Issued ash oncentration Transactions ross-border Intra ompany Transfer PMNT IN XIT Denmark Payments Issued redit Transfers Priority redit Transfer PMNT IDT PT Denmark Payments Issued redit Transfers Not available PMNT IDT NTAV Entry Detail level Finland Payments Issued redit Transfer SEPA redit Transfer PMNT IDT EST Finland Payments Issued heques ash Letter PMNT IHQ ASH Finland Payments Issued redit Transfers ross-border redit Transfer PMNT IDT XBT Finland Payments Issued heques Foreign heque PMNT IHQ XBQ Finland Payments Issued redit Transfers Payroll/Salary Payment PMNT IDT SALA Finland Payments Issued ash oncentration Transactions Intra ompany Transfer PMNT IN IT Finland Payments Issued ash oncentration Transactions ross-border Intra ompany Transfer PMNT IN XIT Finland Payments Issued ash oncentration Transactions orporate Own Account Transfer PMNT IN OAT

17 amt Debit Notification orporate Access Payables version of 17 text code ountry Domain Family Sub-family Domain Family Subfamily Finland Payments Issued redit Transfers Priority redit Transfer PMNT IDT PT Finland Payments Issued redit Transfers Not available PMNT IDT NTAV Entry Detail level Norway Payments Issued redit Transfer Domestic redit Transfer PMNT IDT DMT Norway Payments Issued heques ash Letter PMNT IHQ ASH Norway Payments Issued redit Transfers Payroll/Salary Payment PMNT IDT SALA Norway Payments Issued redit Transfers ross-border redit Transfer PMNT IDT XBT Norway Payments Issued ash oncentration Transactions Intra ompany Transfer PMNT IN IT Norway Payments Issued ash oncentration Transactions ross-border Intra ompany Transfer PMNT IN XIT Norway Payments Issued redit Transfers Priority redit Transfer PMNT IDT PT Norway Payments Issued heques Foreign heque PMNT IHQ XBQ Norway Payments Issued redit Transfers Not available PMNT IDT NTAV Entry Detail level Sweden Payments Issued redit Transfer Domestic redit Transfer PMNT IDT DMT Sweden Payments Issued ash oncentration Transactions Intra ompany Transfer PMNT IN IT Sweden Payments Issued redit Transfers ross-border redit Transfer PMNT IDT XBT Sweden Payments Issued ash oncentration Transactions ross-border Intra ompany Transfer PMNT IN XIT Sweden Payments Issued redit Transfers Payroll/Salary Payment PMNT IDT SALA Sweden Payments Issued heques ash Letter PMNT IHQ ASH Sweden Payments Issued heques Foreign heque PMNT IHQ XBQ Sweden Payments Issued redit Transfers Priority redit Transfer PMNT IDT PT Sweden Payments Issued redit Transfers Not available PMNT IDT NTAV