Europe: Importing transaction level into Bank statement in ISO20022 camt.053 format

This feature introduces additional capabilities in Advanced bank reconciliation feature for importing bank statement and matching bank statement lines to bank documents.

Refer to the following documentation to get more details on Advanced bank reconciliation feature:

• Advanced bank reconciliation overview

• Configure advanced bank reconciliation

• Set up the advanced bank reconciliation import

• Reconcile bank statements using advanced bank reconciliation

• Set up bank reconciliation matching rules

  Import of ISO20022 camt.053 statement from the Entry (C-Level) is supported via XSLT transformation files, more information can be found in the documentation referred above.

  This feature introduces additional possibility to import ISO20022 camt.053 statement from the Transaction (D-Level). This is supported through Electronic reporting configurations.

High level structure of camt.053 XML file is present below for your reference:

A-Level: Group header

  B-Level: Account Statement

    C-Level: Statement Entry

      D-Level: Transaction details

ER configurations are created based on ISO20022 message definition report and considering Common global implementation guidelines (CGI).

No country or bank specifics are considered in this feature release.

Electronic reporting configurations can be easily updated by user when any country or bank specifics need to be considered.

This feature also introduces additional capability for importing ISO20022 references.

The following changes are done in XSLT file of ISO2002XML_to_Reconciliation_xslt (importing from Entry D-Level):

Transformation file was updated to be able to import:

• Creditor reference information;

• Account servicer reference information;

• Instructed amounts;

• Proprietary bank transaction codes when Domain bank codes are empty.

This XSLT file can be used when there is no more than 1 transaction level line under each entry level line. This XSLT transformation file ensures import of bank statement line from Entry level of camt.053 file.

New Electronic reporting configurations were added to be able to import bank statement lines from Transaction details level:

This can be used when there are more than 1 transaction level line under each entry level line. ISO20022 camt.053 configuration ensures import of bank statement line from Transaction level of camt.053 file.

Consult with your bank to get more details on your camt.053 file to choose an appropriate approach for import.

With this feature, user has now additional possibilities to set up automatic matching rules in advanced bank reconciliation feature, by using imported ISO20022-specific references when using full ISO20022 cycle, including:

• Export payments in ISO20022 pain.001 credit transfer, ISO20022 pain.008 direct debit formats.

• Import payments into customer payment journal in ISO20022 camt.054 format.

• Import return files into vendor payment transfer journal in ISO20022 pain.002 and camt.054 formats.

• Import bank statements via advanced bank reconciliation.

  Several ISO20022-specific references can now be used for matching between imported bank statement line and payment document.

  - New field End to End ID is added to Bank documents list (generated payments) which is filled with <Voucher_RecID> – similar way as EndToEndID is filled in ISO20022 credit transfer generate payment file.

  - New field Payment ID is added to Bank documents list (generated payments) which is taken from the Payment ID field on the payment journal line.

  - New field Creditor Reference Information is added to Bank statement line. Structured creditor reference from camt.053 file is imported into this new field from camt.053 file.

  The following table shows some ISO20022 references and their flow through payment messages:

Go to Cash and bank management > Setup > Advanced bank reconciliation > Bank statement format.

Create bank statement format (for example, ISO20022_trans). Activate the Generic electronic reporting field. Choose ER configuration in the Import format configuration field.

Set up additional rules to match bank statement line and bank document line using ISO-20022 specific references in the form of Cash and bank management > Setup > Advanced bank reconciliation > Reconciliation matching rules.

The End to End ID field value in bank document line is equal to the Description field value of Statement (EndtoEndID value from camt.053 file is imported into Description field of Bank statement line). This matching rule can be set up for both Issued credit transfers/direct debits (initiated via vendor and customer payment journal) and Received credit transfers (imported via camt.054 feature into customer payment journal):

The Creditor Reference Information field value from bank statement line to Payment ID from bank documents (filled with Structured creditor reference in camt.054 import). This matching rule can be applied for issued credit transfers for example (PMNT-ICDT bank transaction code).

The Payment reference field value in bank document line is equal to the Text field value of bank statement (AccountServicerReference field value from camt.053 file is imported into the Text field of Bank statement line). This matching rule can be applied for received credit transfers for example (PMNT-RCDT bank transaction code).

Note For received credit transfers, imported into a customer payment journal through camt.054 feature, user needs to change Status of payment journal line from Received to Sent to be able to match it via Advanced bank reconciliation.

Import statement in the form of Cash and bank management > Bank statement reconciliation > Bank statements.

Reconcile statement in the form of Cash and bank management > Bank statement reconciliation > Bank reconciliation.

Find more details in article Reconcile bank statements using advanced bank reconciliation.

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

• Download update for Microsoft Dynamics 365

Note You can refer to the above link and download the related hotfix.

Prerequisites

You must have the following product and hotfixes installed to apply this hotfix:

• Microsoft Dynamics 365
• KB4054478
• KB4039961

You may need to run Organization administration \ Electronic reporting \ Rebuild table references function before you start using this feature.

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.