Changes for importing ISO20022 camt.054 into customer payment journal are available in Microsoft Dynamics AX

This hotfix will introduce the feature that allows to import incoming customer payments into customer payment journal from ISO20022 camt.054 credit advice file in Microsoft Dynamics AX 2012 R3, Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012, and Microsoft Dynamics AX 2009 SP1.

More Information

The changes in the hotfix enable the changes for importing incoming customer payments into customer payment journal from ISO20022 camt.054 credit advice file in Microsoft Dynamics AX.

Setup

  1. Set up Method of payment in Account receivable > Setup > Payment > Methods of payment:

    1. Choose ISO20022 camt.054.001.02 in the Import format field;

    2. Choose bank account in the Payment account field.

  2. Set up customer record in Account receivable > Customers > All customers: Name, Organization number.

    If ESR payments will be imported which contain ISR reference (applicable for legal entities in Switzerland), set up length of customer code used in ISR reference for automatic identification of customer (field “Customer payments, account lengths”). Also make sure that Customer number and invoice number (number sequences) contain only digits and no other characters. Also, invoice number must not have leading zeros.

  3. Press Bank accounts in customer record and set up customer bank account record: IBAN or Bank account number, SWIFT or Routing number.

  4. Set up legal entity bank accounts in Cash and bank management > Bank accounts:

    1. IBAN or Bank account number, SWIFT or Routing number, Currency, Address.

    2. If you are going to use Advanced bank reconciliation, activate parameter Advanced bank reconciliation in Reconciliation fast tab.

      If you are going to reconcile unposted imported payments, activate also parameter Use bank statements as confirmation of electronic payments.

    3. If you are going to import ESR payments (applicable for banks in Switzerland), set up the following data:

      ESR: This is a unique contract number you get as a participant of the ESR system.
      BESER ID: This is a unique identifier for your bank in the ESR system. It must be filled for bank account and has normally 6 digits.

  5. (Optionally) Set upmapping between bank transaction codes in file and bank transaction type in system.

    1. Open Cash and bank management > Setup > Bank reconciliation > Transaction code mapping;

    2. Choose Bank account in the left side;

    3. Create new line in the right side, enter Statement transaction code, and choose respective bank transaction type.

    Tip! If you set up mapping for Domain codes, in the Statement transaction code, fill concatenated values from 3 levels: DomainFamilySubfamily, example: PMNTRCDTDMCT (Payments > Received credit transfer > Domestic credit transfer).

  6. If file contains transaction charges which you decide to post along with posting of incoming payment:

    1. Set up Payment fee in Accounts receivable > Setup > Payment > Payment fee. In the field Charge choose "Ledger" so that fee amount is charged to the dedicated GL account.

    2. Associate Payment fee ID to Method of payment and bank account in the Payment fee setup form (press Payment fee setup button on Methods of payment form).

Import customer payments

  1. Open Customer payment journal, go to Lines.

  2. Press Functions > Import payments.

  3. In the dialog, choose Method of payment for which transactions will be imported, press OK.

  4. In the Import payments dialog, you can set up the following parameters and press OK:

    1. Choose Bank account (if it wasn't defaulted from the Method of payment). If Bank account left blank, notifications for all bank accounts from file will be imported.

    2. Choose File name which is used in import.

    3. Activate Import incorrect records, if you want to import records where customer was not found in the system. Customer account will be left blank in such lines.

    4. Activate Print control report, if Control report should be printed.

    5. Activate Settle transactions if imported customer payments will need to be settled with invoices found in the system.

      Invoices are searched only when Structured remittance information is provided in file (either structured creditor reference or structured referred documents).

    6. Activate Import direct debit transactions if incoming direct debits need to be imported in the journal.

      This option should be chosen only when direct debits were not initiated from the system.

  5. Review generated payment lines, in status Received. Prepare lines for posting or reconciliation.

    If you change the line amount (this is not advised), imported Fee amounts will be recalculated based on setting in Payment fee setup.

  6. If you are going to import account statement and reconcile unposted payments via Advanced bank reconciliation, choose all payment lines and press Payment status > Sent.

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:

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+ContactsCustomers

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.


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

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.

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
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

Thank you for your feedback!

Thank you for your feedback! It sounds like it might be helpful to connect you to one of our Office support agents.

×