This article applies to Microsoft Dynamics AX for the Swiss (ch) region.

The SEPA direct debit (DD) export payments are designed in Microsoft Dynamics AX 2012 R3, Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012, and Microsoft Dynamic AX 2009 SP1 through the Application Integration Framework (AIF). More details about processing SEPA DD and mandates functionality could be found in TechNet Article

To generate the country/region specific version of the direct debit file, in the Payment processing data form, in the Country field, for Switzerland type "CH".

You may use this format if you need to generate SEPA direct debit (euro payment from country in SEPA zone).More information can be found in SEPA DD Whitepaper

The following Swiss specific rules were implemented in the Swiss SEPA DD file compared to SEPA DD generic filling rules:





Schema location is

Organization name



Company name field length exported to 70 symbols

Organization identification



Value from Company information > Tax registration number is exported in tag <Id> if present

Organization postal address


Not present in the schema

Control sum


Not calculated and not present in the schema

Debtor account identification


If IBAN value is not present in Company bank account, then the value from Bank account number field is exported to <Othr> tag (which should contain Postal account number).

Creditor account identification


If IBAN value is not present in Customer bank account, then the value from Bank account number field is exported to <Othr> tag (which should contain Postal account number).

Validation of mandatory filling of customer IBAN is not present.

Amendment information details


If organization bank account SWIFT is changed, the tag <AmdmntInfDtls> is not exported (not present in the schema)

Amendment information details > Original creditor schema identification

<AmdmntInfDtls>\<OrgnlCdtrSchmeId>\ <Id>\<PrvtId>\<Othr>

If Direct debit ID is changed in customer bank account, additional tag <SchmeNm>\<Prtry> with value “SEPA” is present in the schema.

Amendment indicator, Amendment information details



If customer bank account SWIFT changed, <AmdmntInd> and <AmdmntInfDtls> exported only for records with sequence type <SeqTp> = FRST.

But anyway tag <OrgnlDbtrAgt>\<FinInstnId>\<BIC> is not exported for CH, only value “SMNDA” at <Othr>\<Id> is present.

Original debtor agent


If customer bank account SWIFT changed, tag <OrgnlDbtrAgt> and its content exported only for Sequence Type FRST.

Instruction identification


First 35 symbols of journal line Voucher ID is exported

Following fix was made for all countries:

If mandate changes exist, previous values of initialized assigned with old values of Company name, IBAN, Direct debit Id, SWIFT, customer SWIFT or customer IBAN, but if some of these values did not change they are assigned with current values. Previously they remained blank in this case. This allows to avoid exporting tags with empty values because conditions like bankAccountSwift != previousBankAccountSwift (which can be blank) were met.


This hotfix will enable this feature.

Hotfix information

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: 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:

Partners 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.

Installation information

If you have customizations for one or more of the methods or the tables that are affected by this hotfix, you must 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 hotfix:

  • Microsoft Dynamics AX 2012 R3

  • Microsoft Dynamics AX 2012 R2

  • Microsoft Dynamics AX 2012

  • Microsoft Dynamics AX 2009 SP1

Restart requirement

You must restart the Application Object Server (AOS) service after you apply the hotfix.

File information

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.

Need more help?

Expand your skills


Get new features first


Was this information helpful?

What affected your experience?

Thank you for your feedback!