Bank statement and payment reconciliation for the EU
This topic provides an overview of the functionality that you can use to reconcile payment information from banks in formats that are used by European countries.
In Microsoft Dynamics 365 for Finance and Operations, Enterprise edition, you can import transactions from banks and settle these transactions against existing transactions. In Europe, you can do this for the following scenarios:
- Importing bank statements
- Importing payments
- Importing return files
A bank statement or account statement is a summary of financial transactions that have occurred over a given period on a bank account held by a company with a financial institution. In Finance and Operations you can import a bank statement. It is important to settle imported transactions with existing transactions as well as verify the opening and ending balance of the bank accounts. The following list includes the supported European formats.
- Advanced bank reconciliation European file formats. For more information, see Advanced bank reconciliation overview.
- ISO 20022 camt.053 bank statement message file format.
- CODA bank statement file format. For more information, see CODA bank statement.
Customer and vendor payments import and return messages
In addition to a bank statement, banks can provide specific messages, containing information about customer and vendor payments, which can be imported into Finance and Operations and reconciled with customer and vendor transactions. When a company needs to receive information about incoming customer payments transactions from the bank, the import formats can be used. For companies that use direct debit and credit transfer, the return messages can be received to update the status of payments that were previously exported. The difference between import formats and return formats is that returns are targeted mostly to update already created payment journal lines (they can be created when direct debit or credit transfer were initiated) instead of creating new lines. Some complex import formats can also include return scenarios. The following example shows how this division should be implemented.
- ISO 20022 camt.054 bank notification message
- Nets import format - Complex feature for Norwegian payment formats
- ESR customer payments import
- Import payment formats for Sweden - BankGirot Max and BankGirot OCR formats
- ISO 20022 pain.002 payment status report
- (DNK) BetalingsserviceBasis-returformat – Return format for customer Betalingsservice export format
- Import payment formats for Sweden - Bankgirot Autogiro returns
- (SWE) BankGirot return – Vendor payments return format, which corresponds to Bankgirot export format