This guide explains how to import Finvoice-formatted invoice material into Netvisor.

CONTENT

​

Finvoice invoice material can be imported into Netvisor from other systems in XML format. The only allowed file format for import is XML, and the Finvoice content must match the documentation described in this guide. The "Data import" function is used to transfer invoice data. The imported invoices must be sales invoices; importing purchase invoices is not possible. The function is available for all companies, and the user must have editing rights in Accounting function-specific rights for "Basic data management" and "Basic data import". You can find the Data import function in the Netvisor UI: Company menu > Data import and export > Data import.

To import invoice material, you need invoice material that complies with the Finvoice standard. The oldest supported version of Finvoice is 1.2, but newer Finvoice material versions can also be used.

​

​

The following steps must be completed in Netvisor for the import:

Using the Netvisor invoice import function is included in all packages.

Importing invoice data (Finvoice) requires the following resources:

​

The correspondence table below shows the information taken from the Finvoice material and the field in Netvisor where the information is targeted. Secondary information is used if a primary value has not been given in the invoice material. Example materials can be found at the end of the guide, and an Excel-format correspondence table can be downloaded here.

To have Scandinavian letters (å, ä, ö) displayed correctly, the material must be in ISO/IEC 8859-15 encoded form. Special characters must be given in the material as XML entities according to the Finance Finland Finvoice 3.0 implementation guideline. See the table below.

For example, the company name TILI & Tiliöinti Oy must be given in the XML material as TILI & Tiliöinti Oy.

With Finvoice-formatted invoice material it is also possible to import cost object headers and cost objects from fields RowDefinitionHeaderText and RowDefinitionValue. If you want to prevent the import of cost object headers and cost objects, please contact Netvisor customer service.

If a customer is created during the import, both the e-invoice address details and the email invoicing address are read from the invoice material to the customer card, if they are found in the material. If the customer is already found in Netvisor before the import (i.e., the customer code given in the material is found in Netvisor), the e-invoicing data/email invoicing address must be manually updated to the customer card or imported to the customer register using Customer details import. If you want invoices to be allocated in the future to a customer card found in Netvisor, the Netvisor customer code must be given in the material (InvoiceRecipientPartyIdentifier or BuyerPartyIdentifier).

*If a product is not found by product code (ArticleName) nor by product name (ArticleName), the product is created in Netvisor according to the invoice material data. If the product is already found in Netvisor, the data is not updated from the invoice material to the Netvisor product.

The product unit price is calculated based on the row sum, delivered quantity, and possible discount.

The invoice total is calculated based on invoice rows.

One transfer file can contain multiple invoices. This way, invoices do not need to be imported one at a time.

​

​

​

If there are no errors in the import, after the import a specification of imported data and links to formed materials are presented.

The invoice import also automatically establishes in Netvisor the customer used on the invoice and the products used, if they are not already found. Please note that the customer's e-invoicing data is not saved to the customer card at this point. If the customer and products used on the invoice are found in Netvisor, the data is targeted to the existing customer and products.

If there are errors in the imported material, an error message is displayed explaining why the material cannot be imported into the system. Below the error message, an editor window is displayed, but the user cannot make changes to the imported material through this window; changes must be made to the original Finvoice material. After correction, the material can be imported again. If the material contains multiple invoices, the invoices in the correct format are imported directly. Please do not edit the imported invoices in the UI after the import.

Error message "INVALID_DATA :: Tiedon muoto virheellinen:. XML-sanoman validointi epäonnistui: Could not validate xml: The element 'invoicelines' has incomplete content. List of possible elements expected: 'invoiceline'." indicates that there are deficiencies in the invoice rows or the fields do not match the fields described in this guide. Most commonly, the problem is that the material has "InvoicedQuantity" when it should be "DeliveredQuantity".

​

The examples below show the minimum information that the Finvoice material must have in order to import a sales invoice, as well as the maximum information that can be read from the material. In addition to these, the Finvoice material may have other information according to the Finvoice standard, but it is not read into Netvisor.

​

​

Keywords: Invoice material, Finvoice, Netvisor, XML, Sales invoice, Software interface service, Import

​

This article has been translated using an AI-based translation tool. The contents or wording of these instructions may differ from those in other instructions or in the software.