SEPACreditTransferPayments Ax5 WP
SEPACreditTransferPayments Ax5 WP
SEPACreditTransferPayments Ax5 WP
Table of Contents
Executive summary ..................................................................................... 3
SEPA credit transfer overview ................................................................................................. 3 SEPA credit transfers in Microsoft Dynamics AX ........................................................................ 3
Installation ................................................................................................. 4
Install the .xpo and label files ................................................................................................. 4 Verify that the SEPA export file formats are installed ................................................................. 4
Setup .......................................................................................................... 5
Set up SEPA countries/regions as members of the European Economic Area................................. 5 Set up a method of payment for SEPA credit transfers ............................................................... 5 Set up company information .................................................................................................. 6 Set up company bank accounts for SEPA credit transfers ........................................................... 6 Set up vendors and vendor bank accounts for SEPA credit transfers ............................................ 6 Belgium only: Set up Isabel electronic banking parameters ........................................................ 7
Transactions ............................................................................................... 8
Create and post invoices ........................................................................................................ 8 Create and export payments using a SEPA payment format ....................................................... 8 Country/region-specific information........................................................................................10 Send the credit transfer file to the bank ..................................................................................11
References ................................................................................................ 11
Executive summary
The Single Euro Payments Area (SEPA) is an area set up by the European Commission in which all electronic payments are considered domestic, regardless of the country/region in which the individual, business or organization, and bank are located. Within this area, there is to be no difference between national and cross-border payments. The SEPA includes the 27 European Union (EU) member states, plus Iceland, Liechtenstein, Norway, and Switzerland. The SEPA helps to 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 the standards for SEPA electronic payments using the ISO 20022 Universal financial industry message scheme XML format. Setting rules and guidelines regarding the handling of euro payments.
The EPC, which consists of European banks, develops the commercial and technical frameworks for SEPA payment instruments. Three types of SEPA payments are planned: Credit transfers (supported in Microsoft Dynamics AX 4.0 SP2 and AX 2009 SP1) Direct debits (future) Cards (future)
This white paper describes the SEPA credit transfer payment formats that are available for Microsoft Dynamics AX and how to install, set up, and use them.
Installation
The SEPA credit transfer payment format is available for the following versions: Microsoft Dynamics AX 4.0 SP2 Microsoft Dynamics AX 2009 SP1
5. Select the nine SEPA ISO20022 CredTrans file formats, and then click the < button. 6. Close the File formats for methods of payment and the Methods of payment forms.
Setup
Before you can create SEPA export files, you must specify information in Microsoft Dynamics AX.
4. Repeat steps 2 and 3 for the following countries/regions. European Union, Euro zone countries/regions Austria, Belgium, Cyprus, France, Finland, Germany, Greece, Ireland, Italy, Luxembourg, Malta, Netherlands, Portugal, Slovenia, and Spain European Union, non-Euro zone countries/regions Bulgaria, Czech Republic, Denmark, Estonia, Great Britain, Hungary, Latvia, Lithuania, Poland, Romania, Slovakia, and Sweden European Economic Area zone countries/regions Iceland, Liechtenstein, Norway, Switzerland 5. Close the form.
1. Click Accounts payable > Setup > Payment > Methods of payment. 2. On the Overview tab, press CTRL+N to create a new line. Enter an appropriate identifier, such as SEPA credit transfer, in the Method of payment field. 3. Enter other information, as needed, for the method of payment. 4. Click the File formats tab. In the Export format field, select SEPA ISO20022 CredTrans. If the country/region where your bank is located has special requirements, select the export format for your country/region. Note: If the field list is empty, click Setup and select from the available formats. 5. Repeat steps 2 through 4 for additional banks, if necessary. For example, suppose that you do business with vendors in all EU countries and have one bank account in Germany and another in Finland. You will pay some vendors from the account in Germany and others from the account in Finland. You must set up two methods of payment: One that uses the SEPA ISO20022 CredTrans DE export format and another that uses the SEPA ISO20022 CredTrans FI export format. 6. Close the form.
Set up vendors and vendor bank accounts for SEPA credit transfers
SEPA payments require that IBAN and BIC (SWIFT) codes are provided for the vendor bank account. Also, SEPA payments must be in euros. Enter the bank account information and currency information for your vendors.
1. Click Accounts payable > Common Forms > Vendor Details. 2. On the Overview tab, select a vendor that you will submit SEPA credit transfers for. 3. Verify that the currency code for the vendor is EUR. 4. Click Setup > Bank accounts. 5. In the Vendor bank accounts form, on the Overview tab, select a bank account. 6. On the General tab, enter information in the SWIFT code and IBAN fields. 7. Click the Address tab. 8. Enter the address information, including the street name, ZIP/Postal Code, and country/region. It is important to specify the country/region where the bank is located. 9. Close the Vendor bank accounts form to save your changes. 10. In the Vendors form, click the Payment tab. 11. Optional: Select a method of payment that uses one of the SEPA ISO20022 CredTrans export formats. This method of payment is used as the default entry when creating transactions for the vendor. 12. Select the vendor bank account in the Bank account field. 13. Repeat steps 2 through 12 for all vendors for which you will submit SEPA credit transfers. 14. Close the Vendors form.
Transactions
You use the SEPA credit transfer payment format the same way that you use any other payment format in Microsoft Dynamics AX.
13. Select a method of payment that uses one of the SEPA ISO20022 CredTrans export file formats, and then select the bank account from which the payment is drawn. 14. Click Dialog.
15. In the Dialog form, enter information for the export file. Refer to the following table for information about each field. Field
Processing date Remittance information
Description
Enter the date when the bank should process the payments. Select the format for remittance information, depending on the requirements of your country/region or bank. Structured Select this option if one payment line is settled with one invoice. This option is not available for the country/region-specific export formats for Austria, France, Germany, or The Netherlands. Unstructured Select this option if payment is settled with multiple invoices. The invoice numbers for the settled invoices are concatenated and used as the remittance information. In compliance with SEPA guidelines, unstructured remittance information is limited to 140 characters.
Amount limit
Enter the SEPA payment amount limit for your country/region, if required. If you enter an amount, each payment in the journal is below this limit is verified. Note: If a payment exceeds the amount limit, additional information must be submitted to the central bank. Payment amounts that exceed the payment amount limit are not supported in this release.
Enter or select the file name for the SEPA XML file. Use the file extension .XML. Select this check box to print a report that contains the payment information. You can specify report options by clicking the Control report button.
16. Click OK. 17. In the Generate payments form, click OK to create the payment file. 18. Close the Journal voucher and Journal forms.
Country/region-specific information
Refer to the following table for information about the country/region-specific formats. Country/region
Austria Belgium
Export format
SEPA ISO20022 CredTrans AT SEPA ISO20022 CredTrans BE
Table Heading
Only unstructured remittance information is supported. 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 12345567890. ROUND(1234567890/97) = 12727504 12727504 * 97 = 1234567888 1234567890 - 1234567888 = 02 Structured message: 1234567890 + 02 = 123456789002 Microsoft Dynamics AX 2009 only: If you are using Isabel electronic banking software, the File name location in the Dialog form must be the same as the location specified in the Upload folder in the IBS parameters form. When the payment generation process is complete, a record is created in the IBS transactions form.
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 vendors 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. France SEPA ISO20022 CredTrans FR Only unstructured remittance information is supported. A SEPA payment cannot be processed in either of the following situations: The payment amount is greater than the Amount limit field in the payment format dialog and the destination bank is not located in France. The payment amount is greater than the Amount limit field in the payment format dialog, the destination bank is not located in France, and the payment beneficiary is nonresident in France.
SEPA ISO20022 CredTrans DE SEPA ISO20022 CredTrans IT SEPA ISO20022 CredTrans ES SEPA ISO20022 CredTrans NL
Only unstructured remittance information is supported. No additional information is required. No additional information is required. Only unstructured remittance information is supported.
10
References
European Payments Council (EPC) http://www.europeanpaymentscouncil.eu/ EPC SEPA Credit Transfer Scheme Customer-to-Bank Implementation Guidelines http://www.europeanpaymentscouncil.eu/documents/EPC13208%20C2B%20CTIG%20V3.2%20Approved.pdf Directive on Payment Services (PSD) http://ec.europa.eu/internal_market/payments/framework/index_en.htm European Central Bank http://www.ecb.int/paym/sepa/html/index.en.html European Commission http://ec.europa.eu/internal_market/payments/sepa/index_en.htm
11
Microsoft Dynamics is a line of integrated, adaptable business management solutions that enables you and your people to make business decisions with greater confidence. Microsoft Dynamics works like and with familiar Microsoft software, automating and streamlining financial, customer relationship and supply chain processes in a way that helps you drive business success. U.S. and Canada Toll Free 1-888-477-7989 Worldwide +1-701-281-6500 www.microsoft.com/dynamics
The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the date of publication. Because Microsoft must respond to changing market conditions, this document should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information presented after the date of publication. This document is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED, OR STATUTORY, AS TO THE INFORMATION IN THIS DOCUMENT. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation. Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property. 2009 Microsoft Corporation. All rights reserved. Microsoft,Dynamics and Dynamics Logo, FRx, Microsoft Dynamics, SharePoint, Visual Basic, Visual Studio, Windows, and Windows Microsoft the Microsoft the Microsoft Dynamics Logo are trademarks of the Microsoft group of companies. Server are either registered trademarks or trademarks of Microsoft Corporation, FRx Software Corporation, or Microsoft Business All other trademarks are property of their respective owners. Solutions ApS in the United States and/or other countries. Microsoft Business Solutions ApS and FRx Software Corporation are subsidiaries of Microsoft Corporation.
12