ISO20022 is an international standard designed to streamline global business communication that you can generate and import ISO20022 payment format file in Microsoft Dynamics 365 Finance and Operations:

File type	Name	Description	Nb-NO	Direction	GER Config
Pian.001	CustomerCreditTransfer	Vendor payment file	Utbetalingsfil	Outbound	ISO20022 Credit transfer (NO)
Pain.002	CustomerPaymentStatus	Payment status log/report – Technical validation Reception return file (Group Header, Payment information level, Credit transaction level)	Mottaksretur	Inbound	ISO20022 pain.002
Pain.008	CustomerDirectDebit	Customer direct debit	Direct Debit	Outbound	ISO20022 Direct debit
Camt054D	BankToCustomerDebitCredit	Settlement return – Debit notification for vendors’ confirmed payments	Avregningsretur	Inbound	ISO20022 Camt.054
Camt054C	BankToCustomerDebitCredit	Settlement return – Credit notification for customers’ confirmed payments	Innbetalingsfil	Inbound	ISO20022 Camt.054
Camt053	BankToCustomerStatement	Bank account statement for reconciliation	Bankkontoutdrag	Inbound	Camt.053 Format

These standard configurations are ready to use and can be imported in to D365FO via Microsoft repositories. To import the configurations, navigate to organization administration > Workspaces > Electronics reporting:

Choose ‘Microsoft’ and click on ‘Repositories’:

Choose ‘Global’ and click on “Open” to access to the repositories.

Search for the configurations and click on “Import” to install them. Following configuration can be searched:

• ISO20022 Credit transfer
• ISO20022 Direct debit
• ISO20022 pain.002
• ISO20022 Camt.054
• Camt.053 Format

Example: Camt.053 Format

Notes:

• While importing the configurations, model mapping and data model will be imported automatically. For example, once you import “ISO20022 Camt.054, ‘Payment model mapping to destination ISO20022’ (model mapping) and ‘Payment model’ will be imported.

• Some configurations are built and applicable for specific product update. It means that you need to have same or newer product update version as prerequisite to import the configuration.

• There are some standard configurations specific for each country and based on their specifications. For example, ‘ISO20022 Credit transfer’ and ‘ISO20022 Direct debit’.

• Each configuration has KB/ID number in Microsoft repositories. This number can be searched on LCS > Project > Issue search to better understand the fix/development for the configuration.

• If you need to create a custom version of standard configuration to satisfy bank specification, you can create a derived version and modify the format designer or mapping model.

In the ISO20022 blog series (ISO20022 – DynFOTech), I have tried to clarify how you can start applying ISO20022 format to generate and import payment file.

Part 1 – Introduction ISO20022 Payment in D365FO for Norway – Part 1 (Intro) – DynFOTech

Part 2 – Configurations ISO20022 Payment in D365FO for Norway – Part 2 (Config) – DynFOTech

Part 3 – Company setup ISO20022 Payment in D365FO for Norway – Part 3 (Company setup) – DynFOTech

Part 4 – Vendor and vendor bank setup ISO20022 Payment in D365FO for Norway – Part 4 (Vendor and Vendor bank setup) – DynFOTech

Part 5 – Generate Pain.001 file ISO20022 Payment in D365FO for Norway – Part 5 (Generate Pain.001 file) – DynFOTech

Part 6 – Import Pain.002 file ISO20022 Payment in D365FO for Norway – Part 6 (Import Pain.002 file) – DynFOTech

Part 7 – Import Camt054D file ISO20022 Payment in D365FO for Norway – Part 7 (Import Camt.054D file) – DynFOTech

Part 8 – Import Camt054C file ISO20022 Payment in D365FO for Norway – Part 8 (Import Camt.054C file) – DynFOTech

Part 9 – Import Camt053 file ISO20022 Payment in D365FO for Norway – Part 9 (Import Camt.053 file) – DynFOTech

Part 10 – Summary

I hope that you find the post instructive and will add value for your daily work as professional to better apply standard functions in D365FO. Please don’t hesitate to re questions to send related questions or feedback via using “Leave a Reply”.