ISO20022 files import in Microsoft Dynamics 365 for Operations

Vrijedi za: Dynamics 365 for Operations

Overview


This article describes features which allows to import payment files in Microsoft Dynamics 365 for Operations in following formats: 
  • incoming payments from the ISO20022 camt.054 credit advice file into Customer payment journal 
  • return files in ISO20022 format: pain.002 status return and camt.054 debit advice into AP Payment transfer journal

Camt.054 credit advice import into AR payment journal


This feature allows to import bank notification messages in camt.054.001.002 format into Customer payment journal.

To use this feature, following setup should be completed:

  • Import ER configuration "ISO20022 Camt.054" from the LCS and select it on the customer Method of payment form in the Import format configuration field. For more info, see also wiki article.
  • On the All customers form, set up Name and Organization number for required customers. On the Customer bank account form, set up customer bank account record: IBAN or Bank account number, SWIFT or Routing number.
  • Set up legal entity bank accounts on the Bank accounts form:
    • IBAN or Bank account number, SWIFT or Routing number, Currency, Address.
    • 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.
    • (Optionally) Set up mapping between bank transaction codes in the file and bank transaction type in system on the Transaction code mapping form.
  • If file contains transaction charges which you decide to post along with posting of incoming payment, create payment fee on the customer Payment fee form, and then associate it with the bank account on the Payment fee setup on the Methods of payment form.
  • If ESR payments will be imported which contain ISR reference (applicable for legal entities in Switzerland), additional settings should be entered:
    • Length of customer code used in ISR referencef or 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.
    • ESR, BESR and Routing number for the legal entity Bank account.For more info see also legacy ESR feature, which requires similar settings.
To run the file import, open customer payment journal lines form and click Functions/ Import payments button. On the dialog screen select method of payment which have required settings for ISO20022 camt.054 format. On the opened dialog, specify required parameters and path to the file location. Click OK. File is successfully imported.

Pain.002 status return and camt.054 debit advice import into AP Payment transfer journal


This feature allows to import bank messages in ISO20022 formats: pain.002.001.003 status return messages and camt.054.001.002 debit advice on the Vendor payment transfer form.

To use this feature, following setup should be completed:
  • Import ER configurations "ISO20022 Camt.054" and "ISO20022 pain.002" from the LCS and select it on the vendor Method of payment form in the Return format configuration and Return format secondary configuration fields. It will require to activate Generic electronic Return format for the selected method of payment.
  • Set up mapping of status codes between pain.002 statuses and vendor payment journal statuses on the Return format status mapping form.
Example setup:
 Return statusPayment status 
 RJCTRejected 
 ACCPAccepted 
 ACSPRecieved 
  • Set up pain.002 error codes and descriptions on the Return format error codes form per external ISO20022 Status reason codes.
Example setup:
 Code Name
 AC01 IncorrectAccountNumber
 AC02 InvalidDebtorAccountNumber
 AC03 InvalidCreditorAccountNumber
 AC04 ClosedAccountNumber
 AC05 ClosedDebtorAccountNumber
 AC06 BlockedAccount
 ...... 


  • If camt.054 file contains transaction charges which you decide to post along with posting of incoming payment, create payment fee on the vendor Payment fee form, and then associate it with the bank account on the Payment fee setup on the Methods of payment form.  

To run the file import, open vendor payment transfers form and click Return file - vendor button. On the dialog screen select method of payment which have required settings for ISO20022 files and press OK. Then, select which file format do you plan to import and click OK. On the opened dialog, specify required parameters and path to the file location and click OK.  

If you're importing pain.002 file, then status of vendor payment lines will be updated according to the information in imported file.

If you're importing camt.054 file, then additional parameters should be specified:
  • Fee ID - new Payment fee lines will be created in vendor payment journal line if charges amount is present in camt.054 file.
  • New journal name, New journal description - payment journal parameters where processed payments will be transferred. After transferring, new voucher numbers should be assigned within the new journal. See the Known limitations section for more information.
  • Import direct debit transactions - activate Import direct debit transactions if outgoing direct debits need to be imported to the vendor payment journal.
  • Journal name - define a new journal name for the imported direct debit transactions
  • Settle transactions - activate if imported vendor payments will need to be settled with invoices found in the system.
Imported information can be reviewed on the Payment transfers form. 
In case of any issues in records in the file, they should be imported as is (i.e. with empty vendor account if it is not possible to find one).

Known limitations


In this section, known limitations regarding this functionality are listed. They can be changed within the subsequent hotfix packages.
  1. While importing pain.002 messages, processing logic can be based on 3 status levels in the incoming file: 1 - Group status (<OriginMsgId>), 2 - Payment information status (<PmtinfSts>) and 3 - Transaction status. By design, transaction vouchers and Payment information should be saved in the intermediate tables and used for mapping purposes during the import process. But because of export feature limitations, it cannot be saved, and for levels 2 and 3 payments cannot be updated automatically as expected. When you receive the error message in the infolog, you can find corresponding payment and update it's status manually.
  2. Unable to update currency exchange rate for the payment lines based on the information in the camt.054 file.
  3. Unable to reassign payments to the new payment journal during import for further voucher numbers reassignment because of the framework limitations.
  4. Control report is not included in this fix. You still can review messages on the infolog in case of matching errors. In some scenarios, errors can be found visually on the payment journal form, or while posting the journal.

Prerequisites


You must have one of the following products installed to apply this hotfix:
  • Microsoft Dynamics 365 for Operations.
Following hotfixes are required for this functionality:
3213292
3218206
3217049        

Hotfix information


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:
Customers: 
https://mbs.microsoft.com/customersource/support/information/SupportInformation/global_support_contacts_eng.htm
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.

How to obtain the Microsoft Dynamics AX updates files

For Microsoft Dynamics AX 7.0 & Microsoft Dynamics 365 for Operations, you can go to https://fix.lcs.dynamics.com/issue/results/?q=4010796 for reference.
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.