According to Directive 2014/55/EU, all European Union (EU) countries are moving toward electronic (paperless) invoicing.
This release enables electronic invoicing in Microsoft Dynamics 365 Finance for Finland-specific format "Finvoice" version 3.0.
The format realizes all the mandatory and some basic optional elements of the structure. This format can be used as is or considered as the base for further customization.
The update consists of 2 parts:
Application changes included into Microsoft Dynamics 365 Finance starting from Monthly Update 10.0.13;
Changes included into Electronic reporting configurations.
Please do the following steps to complete electronic invoicing enabling.
Electronic reporting (ER) settings
Import the following or higher version of the ER configurations from LCS library:
Invoice model mapping.version.219.150
Sales invoice (FI).version.219.20
Project invoice (FI).version.219.6
For more information how to import Electronic Reporting configurations, see Download Electronic reporting configurations from Lifecycle Services.
Make the references to the imported ER formats configurations in Electronic documents tab of Accounts receivable parameters:
Registration IDs settings
Create (if not exists) a new Registration type with a specific Registration category “Enterprise ID (COID)”:
Enter Registration IDs of this type for the Legal entity and Customers.
These Registration IDs will be then used as Seller’s and Buyer’s parties identifiers.
Electronic document properties configuration
In Accounts receivable > Setup > Electronic document property types enter 2 new Types with exact names “Identifier” and “Intermediator”:
These types will be used to populate “MessageTransmissionDetails” for Sender and
In Organization administration > Organizations > Legal entities > Electronic document properties enter
the values for the above types for the Legal Entity:
These values will be used as Sender details.
In Accounts receivable > All customers > Electronic document properties enter the values for the defined types for Customers:
These values will be used as Receiver details.
In customer master data enable generation of electronic invoices for required customers by turning on eInvoice parameter.
Another parameter eInvoice attachment controls whether to include a PDF copy of a printable invoice in the electronic invoice as attachment.
Define Customer’s Tax exempt number:
Add customer’s contact with a phone number or an email defined and select it as a Primary contact in Sales demographics tab:
Units of measure configuration
In Organization administration > Setup > Units > Units > External codes define the values of External codes for all involved units.
The external codes will be used as international trade units of measure codes recommended by United Nations Economic Commission for Europe (UNECE).
Tax codes configuration
In Tax > Indirect taxes> Sales tax > Sales tax codes, in Sales tax code tab define the values of External codes according to UN/CEFACT standard for all used sales tax codes.
Methods of payments configuration
While generating electronic invoices, internal codes used for the methods of payments must be replaced with payment means codes according to UN/CEFACT standards. Application specific parameters must be configured to enable such replacement.
Application specific parameters setup
From LCS > Shared asset library > Data packages, download Finvoice_payment_methods_ASP.zip package with the following files with the examples of Application specific parameters setup for Sales invoice (FI) and Project invoice (FI) formats respectively:
Payment_methods_ASP_Sales invoice (FI).219.20.xml;
Payment_methods_ASP_Project invoice (FI).219.6.xml.
In Electronic reporting workspace, for Sales invoice (FI) format, open Application specific parameters > Setup:
Import application specific parameters for Sales invoice from the downloaded data package. Override the existing settings:
After import, In Conditions section, in Name column add/change Methods of payment codes used in the system and associate them with standardised payment means codes in Lookup result column.
Once completed, change the state from In progress to Completed.
: two lines for with *Blank* and *Not blank* values in Name column must present in Application specific parameters setup and be the last two lines.
Repeat the same application parameters setup for Project invoice (FI) format.
These application parameters are specific for each Legal Entity.
Invoice types configuration
The following types of invoice documents are supported and will be populated automatically:
INV01 - Invoice;
INV02 - Credit note.
If a required invoice type is not covered by the values from the list then it can be manually adjusted in the invoice journals.
To activate the possibility of manual adjustment the following setup has to be done.
Electronic document property definition
In Accounts receivable > Setup > Electronic document property types, add a new property type DocumentType (exactly as written here) applicable to Customer invoice journal and Project invoice.
Invoice document type registration
In Accounts receivable > Inquiries and reports > Invoices > Invoice journal, open Electronic document properties for a selected invoice.
In the next form enter a required Invoice type:
This invoice type value will override automatically created codes.
Similarly for Project invoices, Invoice types can be adjusted in Project management and accounting > Project invoices > Project invoices > Electronic document properties.
Export of Customer of e-invoices
Sending of e-invoices
When an invoice is posted you can generate an electronic invoice by clicking Send > Original button:
Inquiring of e-invoices
The XML file with a generated electronic invoice can be then found in Electronic reporting jobs in Organization administration. To see the file click Show files button for the relevant job:
Then click Open button to download the file with the electronic invoice:
Sending to ER destinations
Alternatively, it is possible to setup Electronic reporting destinations for the e-invoice formats. In this case the output XML files with electronic invoices will be send to the defined destinations, Sharepoint folders, for example, right after posting of an invoice. It is necessary to turn on Print invoice parameter when posting and print to screen, if no paper copy is required.
For more details about ER reporting destinations, please refer to: Electronic reporting (ER) destinations.
At the moment SHA1 algorithm for attachments checksum calculation is not implemented. As result, the related XML element AttachmentSecureHash will be generated as empty.