Business requirements

Implementation guidelines for ISO20022 Swiss direct debit are published on SIX Interbank Clearing page.

The definitions for Swiss direct debits cover the banks schemes (LSV+/BDD) and the PostFinance scheme (CH-DD direct debit) that are currently still separate and enable the collection of direct debits using the ISO 20022 standard.

Scope of the functionality in this hotfix covers Swiss Direct Debit CH-DD scheme.

Overview

Swiss SEPA direct debit

Swiss specific SEPA direct debit is released through KB 3152803.

ISO20022 Swiss direct debit CHDD in Microsoft Dynamics AX

Swiss direct debit is implemented by using the payment formats functionality in the Account receivable module. The following new payment format is available:

  • Generic ISO20022 Direct Debit CH (CHDD)

You should consider the following information when using this payment format:

  • Swiss direct debit CH-DD allows initiation of domestic direct debits in currencies CHF and EUR and intends to substitute legacy Postfinance txt direct debit format DebitDirect. User should generate separate files for direct debits in different currencies.

  • Schema CH-DD is identified by Service level code "CHDD".

  • Information about direct debit mandates is not present in direct debit file as per the implementation guidelines and thus, mandates functionality is not applicable for Swiss direct debit.

  • Two direct debit procedures are applicable: Customer direct debit contains "DDCOR1", business to business direct debit contains "DDB2B". Exact procedure is identified through the Local instrument. User should generate separate files for direct debits of different procedures.

  • It's assumed that customer bank account is located inside Switzerland. No validation is implemented.

  • No status report pain.002 is implemented in Accounts receivable at this point.

Setup

Before you can create ISO20022 Swiss direct debit, you must set up the legal entity and bank account information in Microsoft Dynamics AX.

Set up legal entity information

Use the Legal entities form to set up legal entity information for ISO20022/SEPA payments.

For the legal entity that initiates the payment and creditor legal entity, set up Name, Address of legal entity (make sure, ISO country code is set up on Country/region of legal entity).

Set up company bank accounts

Use the Bank accounts form to enter the bank account information for your legal entity (Cash and bank management > Common > Bank accounts) to set up the following information:

Field

Description

Company ID on "Additional identification" fast tab.

RS-PID – company identification

Routing number on "General" fast tab.

Constant "09000"

IBAN on "Additional identification" fast tab.

Valid IBAN of bank account

Bank account number of "General" fast tab

Valid Post Office account number

(either IBAN or Bank account number must be present)

Set up customers and customer bank accounts

Use Customer form to set up customer information (Accounts receivables > Common > Customers > All customers).

Set up Name and Address of the customer (make sure, ISO country code is set up on Country/region of customer address).

Use the Customer bank accounts form to set up information about customer bank accounts.

Field

Description

Routing number on "General" fast tab

Constant "09000"

You may also set up Routing number type = "CH".

IBAN on "General" fast tab

Valid IBAN of bank account

Bank account number of "General" fast tab

Valid Post Office account number

(either IBAN or Bank account number must be present)

Set up Method of payment

Use the Methods of payment – customers form to set up the method of payment.

Field

Description

Payment type

Choose "Electronic payment".

File formats \ Export format

Choose

  • Generic ISO20022 direct debit CH (CHDD)

General \ ISO20022 codes \ Service level

Choose default Service level for this method of payment.

Recommended to set up constant "CHDD"

General \ ISO20022 codes \ Local instrument

Choose default Local instrument for this method of payment.

Recommend to set up one of allowed values: either DDCOR1 or DDB2B.

General \ ISO20022 codes \ Category purpose

Choose default Category purpose if applicable.

This hotfix includes a modification to store ESR reference number in the Payment Id field of customer transaction after customer invoice posting.

Activate Payment Id in the Payment attributes tab to generate payment lines by Payment proposal function per Payment Id (transfer ESR reference into the Payment Id field of payment journal line automatically).

Transactions

Create and post invoices to customers in a usual way.

Create and export payments using ISO20022 Swiss Direct Debit payment format in AX

Use the Payment journal form:

  1. Click Accounts receivables > Journals > Payments > Payment journal. Create or select a journal.

    On the General tab in the group ISO20022 codes, fill the default values for the current payment journal: Service level, Local Instrument, Category purpose (if they are not set up in Methods of payment or should be different from those set up in Methods of payments).

    You can further change values for each payment line on the Payment tab, group of fields ISO20022 codes.

    It's recommended to create separate journals for different direct debit procedures (identified by Local Instrument).

  2. Click Lines to open the Journal voucher form for payment journal lines.

  3. Create payment lines by using the Payment proposal function or manually.

  4. For payment line, on the Payment tab, you can review or update fields valuable for payment initiation:

Payment ID – review or enter ID to be used in Unstructured remittance information (Swiss Direct debit CHDD specifics).

Note Enter payment notes to be presented in Unstructured remittance information, if applicable.

Tip Set up Organization administration > Default descriptions for automatic generating Payment notes with information about settled invoices.

  1. Click Functions > Generate payments. In the Method of payment field, select a method of payment with export format Generic ISO20022 direct debit CH (CHDD).

  2. In the Bank account field, select the bank account where the payment is made.

  3. Click Select and set up filter by Currency if the journal contains payment lines for different currencies.

  4. Click Dialog. In the Dialog form, enter information for the export file. The following table provides information about each field.

Field

Description

Processing date

Enter the date when the bank should process the payments.

If the field is blank, the Date from payment journal line will be considered as Requested execution date.

File name

Enter or select the file name for the ISO20022 XML file. Use the file extension .xml. The file name is also displayed on the Attending note report.

Control report

Select this check box to print a report that contains the payment information. You can specify report options by clicking the Control report button.

Attending note

Select this check box to print the Attending note report. You can specify report options by clicking the Attending note button.

Payment advice

Select this check box to print the Payment advice report. You can specify report options by clicking the Payment advice button.

Remittance information

Only Unstructured allowed.

Payment Id, Payment notes or list of settled invoices will be exported as Unstructured remittance information.

Batch booking

Only Unknown allowed.

Batch booking tag will not be present in the file.

Issuer

Only <empty> allowed.

Issuer tag will not be present in the file.

  1. Click OK.

  2. In the Generate payments form, click OK to create the payment file.

Send the direct debit file to the bank

When you generate payments, the payments are saved to the location that you specify in the Dialog form. The next step is to send the .xml file to your bank. This process varies from bank to bank. Follow the instructions from your bank to submit the files to the bank for processing.

Hotfix information

How to obtain the Microsoft Dynamics AX updates files

This update is available for manual download and installation from the Microsoft Download Center.

Prerequisites

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.

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:

Partners

https://mbs.microsoft.com/partnersource/resources/support/supportinformation/Global+Support+Contacts

Customers

https://mbs.microsoft.com/customersource/northamerica/help/help/contactus

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

Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained here in is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use for other considerations.

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

What affected your experience?

Any additional feedback? (Optional)

Thank you for your feedback!

×