This article applies to Microsoft Dynamics AX for all regions.
A country-specific update is available for SEPA Credit Transfer ISO20022 (pain.001.001.03) and SEPA Direct Debit Initiation message ISO20022 (pain.008.001.02) for France, Germany, Spain and generic formats in Microsoft Dynamics AX 2009 Service Pack 1 (SP1), Microsoft Dynamics AX 2012 and Microsoft Dynamics AX 2012 R2.
The Single Euro Payments Area (SEPA) is an area that is set up by the European Commission. In the SEPA, 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, national and cross-border payments have no difference. The SEPA includes the 27 European Union (EU) member states, plus Iceland, Liechtenstein, Norway, Switzerland and Monaco. 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 people 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 by using the ISO 20022 universal financial industry message scheme XML format.
Setting rules and guidelines for the handling of euro payments.
A SEPA Direct Debit enables a creditor to collect funds from a customer’s bank account, if a signed mandate is granted by the customer to the creditor. The customer signs a mandate authorizing the creditor to collect a payment and instructing the customer’s bank to pay the collection. SEPA Direct Debits create, for the first time, a payment instrument that can be used for both national and cross-border euro direct debits throughout the 32 SEPA countries/regions.
As of February 1, 2014, SEPA Credit Transfer and SEPA Direct Debits will be mandatory for this kind of transaction within the euro area. There are two schemes available for SEPA Direct Debit: the SEPA Core Direct Debit Scheme and the SEPA Business to Business Direct Debit Scheme.
For more information about the current and planned functionality for Microsoft Dynamics AX that supports the SEPA direct debit (ISO 20022 XML) payment format, download the white paper from the following Microsoft website:
Microsoft Dynamics AX 2009 users should already have their method of payment setup in the following location to use the SEPA Direct Debit export format:
Account Receivable/Setup/Methods of payment/File format tab/Setup buttonMicrosoft Dynamics AX 2012 and Microsoft Dynamics AX 2012 R2 users should already have their outbound port configured. For more information about how to configure the outbound port, go to the following Microsoft website:
Walkthrough: Configuring an outbound integration port for payments [AX 2012]If outbound port was already previously configured for Direct Debit, in that case, it needs to reselect "Export service operations" in Service contract customizations part and then enable all Data Policies.
Mandates can be entered and maintained at the customer level. Reports can be generated to be sent to the customer for signing.
A method of payment can be marked to indicate that any transactions that use the method of payment have a valid mandate entered by selecting the Mandate required check box. In addition, any method of payment where the user has selected the Mandate required check box will want to have the Period dropdown field set to Invoice, which creates a separate payment for each invoice. This avoids issues in which customers use different mandates for different banks.
Transactions where a method of payment is not specified will use default method of payment and default mandate from the customer. The sales order and free text invoice let the user specify the mandate to be used.
During the payment proposal, users can select invoices to be paid by Mandate scheme and Payment type by adding the Customer direct debit mandate table to the proposal selection query.
Upon printing of invoices that use the method of payment with the Mandate required check box selected, a section will be printed on the invoice to indicate the specifics of the direct debit.
Creditor Scheme Identification ID (the Direct Debit ID field) has to be registered according to the Creditor Scheme Identification Rule. For more information about the Creditor Scheme Identification Rule, click to view the Creditor Identifier Overview document:
Creditor Identifier OverviewThe dialog box for the file generation for DD contains the following parameters:
Format, the format of message: Strd or Ustrd. For Germany is always Unstrd.
Country, the country.
Issuer, the issuer of the creditor reference. This parameter is not required. In this case, it is defaulted with BBA for Belgium, CUR for the Netherlands and ISO for other countries. It affects the calculation of the creditor reference.
There are following changes and correction that were done for generic, BE and NL country format for Microsoft Dynamics AX 2009 SP1, Microsoft Dynamics AX 2012 and Microsoft Dynamics AX 2012 R2:
Messages in CustOutPaymRecord_SEPA (Direct Debit) were corrected by using the term "customer" instead of "vendor.".
Removed transaction amount limit validation for credit transfer.
Belgium features - SEPA credit trans and payment id:
User can set "Payment id" on invoice/payment journal in Visual format of Belgian structured communication standard.
Visual format will be converted to electornic format in XML file. This is according to Additional Optional Service 1 (AOS1) applied in Belgium to SEPA Credit Transfer (SCT) and SEPA Direct Debit (SDD)
"Visual representation" - It is what user enteror see in Microsoft Dynamics AX (with +++ *** and /, for example, +++2211/6850/4472+++ )
"Electronic format" – It is what is inserted into XML file (just digits, for example, 221168504472)
In that case, if Payment ID will be specified and will be in format like "+++something+++" or "***something***", and additionally Format = Strd (Structured for Microsoft Dynamics AX 2009) is selected, XML file is generated with STRD message.
If user who generates file for Belgium did specify Payment ID but still that payment id format is not in Visual format of Belgian structured communication standard, in XML file it will be inserted as Unstructured.
In all other cases, it will be inserted as Unstructured message.
A supported hotfix is available from Microsoft. There is a "Hotfix download available" section at the top of this Knowledge Base article. If you are encountering an issue downloading, installing this hotfix, or have other technical support questions, contact your partner or, if enrolled in a support plan directly with Microsoft, you can contact technical support for Microsoft Dynamics and create a new support request. To do this, visit the following Microsoft website:
https://mbs.microsoft.com/support/newstart.aspx You can also contact technical support for Microsoft Dynamics by phone using these links for country specific phone numbers. To do this, visit one of the following Microsoft websites:
https://mbs.microsoft.com/customersource/support/information/SupportInformation/global_support_contacts_eng.htmIn special cases, charges that are ordinarily incurred for support calls may be canceled if a Technical Support Professional for Microsoft Dynamics and related products determines that a specific update will resolve your problem. The usual support costs will apply to any additional support questions and issues that do not qualify for the specific update in question.
If you have customizations for one or more of the methods or the tables that are affected by this hotfix, you must follow these steps:
Review the changes that are documented in the .xpo file.
Apply these changes in a test environment before you apply the hotfix in a production environment.
For more information about how to install this hotfix, click the following article number to view the article in the Microsoft Knowledge Base:
893082 How to install a Microsoft Dynamics AX hotfix
You must have one of the following products installed to apply this update:
Microsoft Dynamics AX 2012 R2
Microsoft Dynamics AX 2012
Microsoft Dynamics AX 2009 SP1
You must restart the Application Object Server (AOS) service after you apply this update.
The global version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.