AX 2012 R3 SEPA (ISO XML) Credit transfer and direct debit payments Date: March 3 rd, 2015

Transcription

1 Contents Introduction... 2 Setup Credit Transfer... 3 Export the xml stylesheet for the payment format from AOT... 3 Setup a batch job to generate SEPA files... 4 Setup Outbound ports for electronic payments... 5 Add Truncate to the Outbound port... 7 Setup a bank account for the legal entity (DEMF) Set up vendors and vendor bank accounts for SEPA credit transfers Create and export payments using SEPA payment format Setup outbound folder destination for additional company Setup Outbound ports for electronic payments for company FRSI Add Truncate to the Outbound port Setup a bank account for the legal entity (FRSI) Set up vendors and vendor bank accounts for SEPA credit transfers Create and export payments using SEPA payment format Setup SEPA Direct Debit Export the xml style sheets for the payment format from AOT Setup a batch job to generate SEPA files Setup Outbound ports for electronic payments Add a Truncate to the Outbound port Setup a bank account for the legal entity (DEMF) Setup SEPA Direct mandates in Accounts receivable parameters Setup a Method of payment for SEPA direct debit Setup customer record with direct debit mandate information and customer bank account Differences between SEPA Core and B2B Schemes Create a free text invoice for direct debit mandate customer Create the payment and generate a SEPA direct debit file Setup Outbound ports for electronic payments Add a Truncate to the Outbound port Setup a bank account for the legal entity (FRSI)... 44

2 Setup SEPA Direct mandates in Accounts receivable parameters Setup a Method of payment for SEPA direct debit Setup customer record with direct debit mandate information and customer bank account Create a free text invoice for direct debit mandate customer Create the payment and generate a SEPA direct debit file Additional information Releases for AX 2012 R3 SEPA Credit Transfer and SEPA Direct Debit References Validation tools Introduction The Single Euro Payments Area (SEPA) is an initiative by the European Commission in which all electronic payments are considered domestic, regardless of the country/region where the individual, business, or organization, and the bank are located. Within this area, there is no difference between national and cross-border payments. The SEPA includes the 27 European Union (EU) member states, plus Iceland, Liechtenstein, Norway, Switzerland, and Monaco. The SEPA helps form a single market for payment transactions within the European Economic Area (EEA). Ultimately, the SEPA is expected to reduce the number of payment formats that banks, businesses, and individuals must work with. The European Commission established the legal foundation for SEPA payments through the Payment Services Directive (PSD). The European Payments Council (EPC) supports the SEPA by: Setting standards for SEPA electronic payments by using the ISO Universal financial industry message scheme XML format. Setting rules and guidelines for handling euro payments. The EPC, which consists of European banks, develops the commercial and technical frameworks for the SEPA payment instruments. The EPC is committed to delivering three pan-european payment instruments: For credit transfers SCT SEPA Credit Transfer supported in Microsoft Dynamics AX 2009 SP1, Microsoft Dynamics AX 2012 and Microsoft Dynamics AX 2012 R2 - R3. For direct debits SDD SEPA Direct Debit supported in Microsoft Dynamics AX 2009 SP1, Microsoft Dynamics AX 2012 and Microsoft Dynamics AX 2012 R2 - R3. For cards SEPA Cards Framework is not supported by Microsoft Dynamics AX

3 Setup Credit Transfer The following steps are needed to setup SEPA credit transfer. This documentation is based on Contoso Demo data (DEMF) with a legal entity located in Germany Export the xml stylesheet for the payment format from AOT 1. Create a folder in which the XLST will be export and saved. The folder might be named C:\SEPA 2. Open AOT by clicking CTRL+D 3. Expand the resources node, select VendPayments_SEPACreditTransfer_03_xsl. Right click and Open Click Export and save the file to C:\SEPA

4 Setup a batch job to generate SEPA files 4. Go to System administration/inquiries/batch jobs/batch jobs 5. Ctrl+N to create a new batch job 6. Enter a Job description = Generate SEPA Payments and save the batch job 7. Click View task and create two new tasks 8. Task 1: Company accounts = CEE > Class name = AIFGatewaySendService 9. Task 2: Company accounts = CEE > Class name = AIFOutboundProcessingService Close the Batch tasks form 9. In the Batch job form select the previous created Batch job and click Recurrence 10. Enter Recurring pattern e.g. Minutes and Count:1

5 Click OK 11. Back to the Batch job form go to Functions/Change status and Select: Waiting Close the Batch job form Setup Outbound ports for electronic payments 12. Go to System administration/setup/services and Application Integration Framework/ Electronic payment services 13. Open the form Outbound ports for electronic payments 14. Select the automatically generated port SEPACreditTransfer Please note: If you are planning to setup SEPA for multiple companies rename the payment to add the company. The payment format name cannot include any blanks and keep in mind to setup the correct path for the outbound folder and the XSLT.

6 15. Specify the location of the XSLT file SEPAVend.xsl and the location for the outbound folder DEMFCreditTransfer 16. Go to button Create ports to create the Outbound port

7 Add Truncate to the Outbound port 17. Export the stylesheet for truncate from AOT 18. Open AOT by clicking CTRL+Shift+W 19. Expand the resources node, select VendPayments_SEPATruncateTagsAndBOM.xslt Right click and Open Click Export and save the file to C:\SEPA

8 20. Go to System administration/setup/services and Application Integration Framework/ Outbound ports 21. Select Port name DEMFSEPACreditTransfer 22. Go to Fast Tab Processing options and enable check Transform all responses 23. Click button Outbound transforms 24. On the new form, click on button Manage transforms 25. Ctrl+N and enter a Name (Truncate SEPA CT), Description: Truncate, Type: XSL 26. Click button Load and select the exported file SEPATruncateTags.xsl

9 Close 27. Select the created Transform Truncate SEPA CT Close the form

10 Setup a bank account for the legal entity (DEMF) 28. Go to Cash and bank management/bank accounts 29. Create a bank account used for SEPA Credit transfer payments (DEMF OPER) 30. Go to Fast Tab Additional identification and enter SWIFT code and IBAN SWIFT: SSKMDEMMXXX IBAN: DE Set up vendors and vendor bank accounts for SEPA credit transfers 31. Go to Accounts payable/common/vendors/all vendors 32. Select or create a vendor 33. Go to FastTab Purchasing demographics and verify Currency=EUR 34. Go to FastTab Payment 35. Clear Method of payment 36. Go to field Bank account 37. Create a Bank account for the vendor (e.g. NL BANK) 38. Within FastTab General enter SWIFT code and IBAN SWIFT code: ABNANL2A IBAN: NL18ABNA

11 Close 39. Select the created bank account for field bank account within the vendor payment FastTab

12 Create and export payments using SEPA payment format 40. Go to Accounts payable/journals/payment/payment journal 41. Ctrl+N to create a new journal and click Lines 42. Enter data in required fields Date > Account = SEPA Vendor > Debit: 1.000,00 Offset account type: Bank Offset account: DEMF OPER Payment status: set to None 43. Go to Functions>Generate payments 44. Within the Generate payments form enable Export payment using service 45. Payment format = Select SEPACreditTransfer 46. Select the legal entities bank account used for SEPA payments (DEMF OPER) 47. Enable Show format dialog checkbox Click ok

13 48. Payment processing data form will open 49. Fill all necessary values 50. If needed enter an individual file name for later identification of the payment file 51. Mark checkbox for payment reports if needed 52. Click OK and OK to create the payment file

14 Note: Information if Structured/Unstructured Structured: Belgium - Structured remittance information is based on the Invoice field for the settled invoice. The first 10 numeric characters are used, plus a check sum based on MODULO 97. For example, if the invoice is A1234B567C89012, the first 10 numeric characters are ROUND ( /97) = * 97 = = 02 Structured message: = Finland - For structured remittance information: For Finnish vendors, the Finnish reference number information is used (Payment ID field on the Payment tab in the Journal voucher form for the payment journal). For foreign vendors, the vendor s invoice number is used (Invoice field in the Journal voucher form for the invoice). For the Message and Payment identification fields in the payment file, the journal number of the vendor payment journal is used. Unstructured: Austria, France, Germany, Italy, Spain and Netherlands Batch booking true/false Batch booking tag is needed by the bank, which is processing the SEPA XML file. If batch booking = true, the bank will summarize all the transaction into one sum, which is displayed on the bank account statement. If batch booking = false, all transactions will be displayed within single lines, as they are displayed in the xml file. Variant Variant 003 is used in Germany ONLY, in all other countries the variant 02 is used, as well this field can remain blank.

15 53. Review the reports generated In case an invoice has been settled during the payment generation the payment advice includes this information

16 54. Go to the folder where the SEPA files should be stored

17 Setup outbound folder destination for additional company 1. Create a new file folder whereas the payment files are generate to in case of additional company using SEPA Setup Outbound ports for electronic payments for company FRSI 2. Go to System administration/setup/services and Application Integration Framework/ Electronic payment services 3. Open the form Outbound ports for electronic payments 4. Select the automatically generated port SEPACreditTransfer and rename it 5. Specify the location of the XSLT file SEPAVend.xsl and the location for the outbound folder C:\SEPA\FRSICreditTransfer 6. Go to button Create ports to create the Outbound port

18 Add Truncate to the Outbound port 7. Go to System administration/setup/services and Application Integration Framework/ Outbound ports 8. Select Port name FRSISEPACreditTransfer 9. Go to Fast Tab Processing options and enable check Transform all response 10. Click button Outbound transforms 11. Select the created Transform Truncate SEPA CT Close the form

19 Setup a bank account for the legal entity (FRSI) 12. Go to Cash and bank management/bank accounts 13. Create a bank account used for SEPA Credit transfer payments (FRSI OPER) 14. Go to Fast Tab Additional identification and enter SWIFT code and IBAN SWIFT: ABCOFRPP IBAN: FR Set up vendors and vendor bank accounts for SEPA credit transfers 15. Go to Accounts payable/common/vendors/all vendors 16. Select or create a vendor 17. Go to FastTab Purchasing demographics and verify Currency=EUR 18. Go to FastTab Payment 19. Clear Method of payment 20. Go to field Bank account 21. Create a Bank account for the vendor (e.g. NL BANK) 22. Within FastTab General enter SWIFT code and IBAN SWIFT code: ABNANL2A IBAN: NL18ABNA

20 Close 23. Select the created bank account for field bank account within the vendor payment FastTab

21 Create and export payments using SEPA payment format 24. Go to Accounts payable/journals/payment/payment journal 25. Ctrl+N to create a new journal and click Lines 26. Enter data in required fields Date > Account = SEPA Vendor > Debit: 2.000,00 Offset account type: Bank Offset account: FRSI OPER Payment status: set to None 27. Go to Functions>Generate payments 28. Within the Generate payments form enable Export payment using service 29. Payment format = Select FRSISEPACreditTransfer 30. Select the legal entities bank account used for SEPA payments (FRSI OPER) 31. Enable Show format dialog checkbox Click ok

22 32. Payment processing data form will open 33. Fill all necessary values 34. If needed enter an individual file name for later identification of the payment file 35. Mark checkbox for payment reports if needed 36. Go to the folder where the SEPA files should be stored

23

24 Setup SEPA Direct Debit The following steps are needed to setup SEPA direct debit. This document is based on Contoso Demo data (DEMF) with a legal entity located in Germany Export the xml style sheets for the payment format from AOT 1. Create a folder in which the XLST will be export and saved. The folder might be named C:\SEPA 2. Open AOT by clicking CTRL+D 3. Expand the resources node, select CustPayments_SEPADirectDebit_02_xslt. Right click and Open Click Export and save the file to C:\SEPA

25 Setup a batch job to generate SEPA files Follow the steps if SEPA setup in other environments than the above, otherwise the batch jobs from CT are used. 4. Go to System administration/inquiries/batch jobs/batch jobs 5. Ctrl+N to create a new batch job 6. Enter a Job description = Generate SEPA Payments and save the batch job 7. Click View task and create two new tasks 8. Task 1: Company accounts = CEE > Class name = AIFGatewaySendService 9. Task 2: Company accounts = CEE > Class name = AIFOutboundProcessingService Close the Batch tasks form 10. In the Batch job form select the previous created Batch job and click Recurrence 11. Enter Recurring pattern e.g. Minutes and Count:1 Click OK

26 12. Back to the Batch job form go to Functions/Change status and Select: Waiting Close the Batch job form Setup Outbound ports for electronic payments 13. Go to System administration/setup/services and Application Integration Framework/ Electronic payment services 14. Open up the form Outbound ports for electronic payments 15. Select the automatically generated port SEPADirectDebit Please note: If you are planning to setup SEPA for multiple companies rename the payment to add the company. The payment format name cannot include any blanks and keep in mind to setup the correct path for the outbound folder and the XSLT. 16. Specify the location of the XSLT file SEPACust.xsl and the location for the outbound folder DEMFDirectDebit 17. Go to button Create ports to create the Outbound port

27 Add a Truncate to the Outbound port 18. Go to System administration/setup/services and Application Integration Framework/ Outbound ports 19. Select Port name: DEMFSEPADirectDebit 20. Go to FastTab Processing options and enable check Transform all responses 21. Click button Outbound transforms 22. Select the created Transform Truncate SEPA CT Close the form

28 Setup a bank account for the legal entity (DEMF) 23. Go to Cash and bank management/bank accounts 24. Create a bank account used for SEPA Credit transfer payments (DEMF OPER) 25. Go to FastTab Additional identification and enter SWIFT code and IBAN SWIFT: SSKMDEMMXXX IBAN: DE Direct debit ID: Enter an identifier of the companies bank (Test ID) Setup SEPA Direct mandates in Accounts receivable parameters 26. Go to Accounts receivable>setup>accounts receivable parameters 27. Select area Direct Debit 28. Enter required days

29 Note (depending on the bank and country): Pre-notification: o Days required for the first pre-notification = 14 o Days required for recurring pre-notification The creditor has to send pre-notifications for each direct debit at least 14 days prior to the due date. Pre-notifications have to include at least: Amount Due date Creditor ID Mandate ID Bank submission: o Days required for the first core bank schema submission = 5 The number of days prior to the first submission must be at least 5 working days before due date and not earlier than 14 calendar days to be received by the customers bank. o Days required for recurring core scheme bank submissions = 2 The number of days prior to the recurring submission must be at least 2 working days before due date and not earlier than 14 calendar days to be received by the customers bank. o Days required for the first B2B bank submission = 1 o Days required for recurring B2B bank submission = 1 o Days required for the first COR1 bank submission = 1 o Days required for recurring COR1 bank submission = 1 The number of days prior to the first and recurring submission must be at least 1 working day before due date and not earlier than 14 calendar days to be received by the customers bank. Expiration: o Months between usage and expiration The mandate is valid up to the termination by the customer. It loses its validity, if more than 36 months have passed since the last valid direct debit

30 Setup a Method of payment for SEPA direct debit 29. Go to Accounts receivable/setup/payment/method of payment 30. Ctrl+N to create an new method of payment 31. Enter: Method of payment: SEPA DD Period: Invoice Description: SEPA DirectDebit Payment type: Electronic payment 32. Go to FastTab General and enter: Require mandate: YES Account type: BANK Payment account: DEMF OPER 33. Go to FastTab Payment attributes 34. Mark Third-party bank

31 Setup customer record with direct debit mandate information and customer bank account 35. Go to Accounts receivable/common/customers/all customers 36. Select a Customer or create a new one (e.g. SEPA Customer NL) 37. Go to FastTab Addresses and enter an address within the EU (e.g. NLD) 38. Go to FastTab Payment defaults 39. Enter Method of payment: SEPA DD Bank account: right click/view details, enter - Bank account: NL Bank - Name: NL Bank - Currency = EUR Tab General: - Swift Code = ABNANL2A - IBAN = NL18ABNA

32 Close the Customer bank account form and select Bank account for the Bank account field 40. Go to FastTab DirectDebit mandates 41. Click Add and enter - Bank account: NL Bank - Signature date: 1/1/ Expected numbers of payments: Usage count: This field is set to 0 for new mandates and will update automatically with each invoice payment

33 Click ok

34 CORE/COR1 vs. B2B Many legacy direct debit schemes were pretty efficient and allowed creditors to collect according to various business requirements. Some legacy schemes allowed collections to be submitted to the bank / clearing 1 day prior to the collection date. This has now changed under SEPA direct debit CORE processing where the requirement is for collection instructions to be submitted 2 days prior to the due date (for recurring collections). 1. Recognizing this in the CORE scheme, the EPC updated the SEPA Direct Debit rulebook which created a local instrument COR1 handling a shorter processing cycle of Due Date-1 day. This allowed the creditor to submit the collection file 1 day before collection date 2. COR1 SEPA direct debit collections is a purely optional scheme, and it is up to the bank if they wish to support COR1 3. So far only Austria, Germany and Spain support COR1 processing 4. Given that existing / legacy collection scheme facilitates submitting the direct debit file one day prior to the due date, it is likely that the COR1 scheme will prevail in Austria, Germany, Spain, and CORE will be used for cross border euro currency collections 5. Aside from being able to submit the first (FRST) and recurring (RCUR) collections 1 day prior to the due date, all other aspects of COR1 SEPA direct debit collections align with the CORE scheme 6. To collect using COR1 you must explicitly refer to the COR1 SEPA direct debit scheme within the XML Payment Information tag as follows: <PmtTpInf> <SvcLvl> <Cd>SEPA</Cd> </SvcLvl> <LclInstrm> <Cd>COR1</Cd> </LclInstrm> There are two SEPA Direct Debit schemes: Core/COR1 and B2B. In below table are some of the key differences to be aware of.

35 Differences between SEPA Core and B2B Schemes Column1 CORE/COR1 SDD B2B SDD Bank Participation Mandatory Optional -> Your customer must ensure their bank is aware that you will debit the customer under the B2B scheme. Not all banks are enrolled, and if your customer fails to notify their bank, your B2B SDD will be rejected Usage With Consumers and Companies With Companies only Refund Right -> 8 weeks after debit -> 13 months after debit (in case of missing mandate) -> No refund right after debit Process Submission Deadlines File format Reachable customers 1. Creditor sends Mandate to Debtor 2. Debtor sends signed Mandate to Creditor 3. Creditor captures Mandate data 4. Creditor stores Mandate 1. D 14 CD: Customer prenotification of amount and due date (unless other timeframe is agreed) 2. D 5 BD: Submission of first and one-off SDD 3. D 2 BD: Submission of subsequent SDD XML -> <Cd>CORE</Cd> or <Cd>COR1</Cd> SEPA DD CORE/COR1 can be used for B2B and B2C 1. Creditor sends 2 Mandate copies to Debtor 2. Debtor: i. Sends signed Mandate to Creditor ii. Sends signed Mandate to their bank to authorize account for B2B collections 3. Creditor captures Mandate data 4. Creditor stores Mandate 1. D 14 CD: Customer pre-notification of amount and due date (unless other timeframe is agreed) 2. D 1 BD: Submission of first, one-off and subsequent SDD XML -> <Cd>B2B</Cd> SEPA DD B2B can be used for B2B area only. It is not allowed to use this scheme for private end users.

36 Create a free text invoice for direct debit mandate customer 42. Go to Accounts receivable/common/free text invoices/all free text invoices 43. Crtl+N to create a new free text invoice 44. Select customer account: SEPA Customer NL and enter: Date: 3/4/2015 Description: Test Main account: Unit price: 1.000,00 Amount: 1.000, Click Post and post the invoice 46. Within the Post free text invoice form mark Posting and Print invoice

37 47. SEPA Notification Header should be printed on the invoice Create the payment and generate a SEPA direct debit file 48. Go to Accounts receivable/journals/payments/payment journal 49. Ctrl+N to create a new journal 50. Click Lines 51. Within the journal voucher enter: Date: 3/4/2015 Account: SEPA Customer NL Offset account type: Bank Offset account: DEMF OPER Payment status: None 52. Go to Functions >Settlement 53. Select an invoice for the payment

38 54. Close the Settle open transaction form 55. Back to the journal go to Functions > Generate payments 56. In the Generate payment form select: Payment method> Method of payment: SEPA DD Export payment using service > Payment format: DEMFSEPADirectDebit Bank account: DEMF OPER Show format dialog: YES Click OK 57. Within the payment processing data form enter (for Germany) Format: Ustrd Country: DE Issuer: ISO Variant: 003 Batch booking: false

39 58. Go back to the journal 59. Payment status changed to Sent and the SEPA direct debit files has been created 60. Payment reports appear if checkbox marked in 10)

40

41 61. Go to the folder where the SEPA file should be stored

42 Setup Outbound ports for electronic payments 62. Go to System administration/setup/services and Application Integration Framework/ Electronic payment services 63. Open up the form Outbound ports for electronic payments 64. Select the automatically generated port SEPADirectDebit Please note: If you are planning to setup SEPA for multiple companies rename the payment to add the company. The payment format name cannot include any blanks and keep in mind to setup the correct path for the outbound folder and the XSLT. 65. Specify the location of the XSLT file SEPACust.xsl and the location for the outbound folder FRSIDirectDebit 66. Go to button Create ports to create the Outbound port

43 Add a Truncate to the Outbound port 67. Go to System administration/setup/services and Application Integration Framework/ Outbound ports 68. Select Port name: FRSISEPADirectDebit 69. Go to FastTab Processing options and enable check Transform all responses 70. Click button Outbound transforms 71. Select the created Transform Truncate SEPA CT Close the form

44 Setup a bank account for the legal entity (FRSI) 72. Go to Cash and bank management/bank accounts 73. Create a bank account used for SEPA Credit transfer payments (FRSI OPER) 74. Go to FastTab Additional identification and enter SWIFT code and IBAN SWIFT: ABCOFRPP IBAN: FR Direct debit ID: Enter an identifier of the companies bank (Test ID) Setup SEPA Direct mandates in Accounts receivable parameters 75. Go to Accounts receivable>setup>accounts receivable parameters 76. Select area Direct Debit 77. Enter required days

45 Setup a Method of payment for SEPA direct debit 78. Go to Accounts receivable/setup/payment/method of payment 79. Ctrl+N to create an new method of payment 80. Enter: Method of payment: SEPA Period: Invoice Description: SEPA Payment type: Electronic payment 81. Go to FastTab General and enter: Require mandate: YES Account type: BANK Payment account: FRSI OPER 82. Go to FastTab Payment attributes 83. Mark Third-party bank

46 Setup customer record with direct debit mandate information and customer bank account 84. Go to Accounts receivable/common/customers/all customers 85. Select a Customer or create a new one (e.g. SEPA Customer NL) 86. Go to FastTab Addresses and enter an address within the EU (e.g. NLD) 87. Go to FastTab Payment defaults 88. Enter Method of payment: SEPA Bank account: right click/view details, enter - Bank account: NL Bank - Name: NL Bank - Currency = EUR Tab General: - Swift Code = ABNANL2A - IBAN = NL18ABNA

47 Close the Customer bank account form and select Bank account for the Bank account field

48 89. Go to FastTab DirectDebit mandates 90. Click Add and enter - Bank account: NL Bank - Signature date: 1/1/ Expected numbers of payments: Usage count: This field is set to 0 for new mandates and will update automatically with each invoice payment Click ok

49 Create a free text invoice for direct debit mandate customer 91. Go to Accounts receivable/common/free text invoices/all free text invoices 92. Crtl+N to create a new free text invoice 93. Select customer account: SEPA NL Customer and enter: Date: 3/4/2015 Main account: Unit price: 1.000,00 Amount: 1.000, Click Post and post the invoice 95. Within the Post free text invoice form mark Posting and Print invoice 96. SEPA Notification Header should be printed on the invoice

50 Create the payment and generate a SEPA direct debit file 97. Go to Accounts receivable/journals/payments/payment journal 98. Ctrl+N to create a new journal 99. Click Lines 100. Within the journal voucher enter: Date: 3/4/2015 Account: SEPA Customer NL Offset account type: Bank Offset account: DEMF OPER Payment status: None 101. Go to Functions >Settlement 102. Select an invoice for the payment

51 103. Close the Settle open transaction form 104. Back to the journal go to Functions > Generate payments 105. In the Generate payment form select: Payment method> Method of payment: SEPA Export payment using service > Payment format: FRSISEPADirectDebit Bank account: FRSI OPER Show format dialog: YES Click OK 106. Within the payment processing data form enter (for Germany) Format: Ustrd Country: DE Issuer: ISO Variant: 003 Batch booking: false

52 107. Go back to the journal 108. Payment status changed to Sent and the SEPA direct debit files has been created

53 109. Go to the folder where the SEPA file should be stored

54 Additional information Releases for AX 2012 R3 SEPA Credit Transfer and SEPA Direct Debit KB The "Attending note" and "Payment advice" reports that exist for other payment methods should also be available for the SEPA Credit Transfer and SEPA Direct Debit payment method. To comply with this, a new update is available in Microsoft Dynamics AX 2012 R3 for all supported countries: Austria, Belgium, Germany, Spain, Finland, France, Italy, Netherlands and generic format. KB New possibility to define outbound ports for SEPA electronic payments differently than currently SEPA Credit Transfer for SEPA Credit Transfer and SEPA Direct Debit for SEPA Direct Debit. You can define other names for SEPA electronic ports. KB Generic ISO20022 Credit Transfer format is available for Austria for non-sepa payments in Microsoft Dynamics AX KB SEPA CT AT Truncate and BOM Resource causes invalid xml file in case of Umlaut KB Batch processing is implemented for SEPA payments to improve performance in Microsoft Dynamics AX 2012 or Microsoft Dynamics AX 2012 R3. During running the generate payment function for create an export file, there is a possibility to fill check box "Batch processing" to create a file as part of batch processing. KB "Custom-Exception:SEPA Customer:: The Payment is not fully settled" error when generating a SEPADirectDebit file KB You cannot select the print destination in the payment processing data form when using SEPADirectDebit to export payment reports. References European Payments Council (EPC) - Validation tools ISO20022: oj=61&lang=en Austria:

55 ING bank different countries: