It is possible to import sales invoices into Netvisor in Finvoice XML format using Data import tool. Data import is available for all companies and the user importing invoices has to have editing authorization for "Perustietojen hallinta" and "Perustietojen tuonti" in Accouting function specific rights. Data import can be found in Netvisor UI: Company menu > Data import and export > Data import.
To be able to import sales invoices you need invoice material in Finvoice standard. The oldest supported version of Finvoice is 1.2 but newer versions can also be used.
The Web Service Interface has to be activated in order to import sales invoices. You can activate Web Service Interface in Company menu > Rights of interface resources by typing "Netvisor laskutietojen tuonti (Finvoice)" in the search bar. Select the right integration and enable all resources.
The person importing sales invoices must create API identifiers in Company menu > API and identifiers > click "Create new API identifier".
Importing sales invoices in Finvoice format is included in all service packages.
Finvoice import requires the following resources in order for it to work correctly:
| Resource | Description |
| Customer.nv | Importing customer details |
| Customerlist.nv | Retreiving customer list |
| Product.nv | Importing product details |
| Productlist.nv | Retreiving product list |
| Salesinvoice.nv | Importing sales invoice / sales order |
Finvoice import details
The table below shows fields taken from the Finvoice material and what field is uses in Netvisor. Secondary information is used if primary information is not given in the Finvoice material.
| Finvoice field, primary | Finvoice field, secondary | Field in Netvisor | Description |
| Invoice | |||
| SellerOrganisationTaxCode | SellerPartyIdentifier | Customer's Business ID | Customer's Business ID when creating new customer. NOTE! The Business ID should be valid Finnish Business ID. If you wish to use foreign VAT identifier it is not taken from the Finvoice material. Foreign VAT identifiers have to be added manually to customer details |
| DeliveryDate | Delivery date | ||
| InvoiceNumber | Invoice number | ||
| InvoiceDate | Invoice date | ||
| EpiRemittanceInfoIdentifier | EpiReference | Reference number | |
| InvoiceDueDate | Payment term days | Payment term is formed by subtracting InvoiceDate from InvoiceDueDate | |
| CashDiscountDate | Cash discount days for the payment term | ||
| CashDiscountPercent | Cash discount percent | ||
| DeliveryMethodText | Delivery method | ||
| DeliveryTermsText | Delivery term | ||
| InvoiceFreeText | Free text before invoicelines | ||
| SellerReferenceIdentifier | Our reference | ||
| BuyerReferenceIdentifier | Your reference | ||
| OrderIdentifier | Order number | Order number is shown in sales invoice Additional information | |
| SellerContactPersonName | Seller name | ||
| InvoiceTotalVatIncludedAmount | Currency | Currency code is taken from the message attribute | |
| Attribute: AmountCurrencyIdentifier | |||
| Invoicing information to the invoice | |||
| InvoiceRecipientOrganisationName | BuyerOrganisationName | Customer name | |
| InvoiceRecipientOrganisationName | Extension for name | The second occurrence of the element is the extension for name | |
| InvoiceRecipientPartyIdentifier | BuyerPartyIdentifier | Customer code | |
| InvoiceRecipientStreetName | BuyerStreetName | Customer address | |
| InvoiceRecipientPostCodeIdentifier | BuyerPostCodeIdentifier | Customer post number | |
| InvoiceRecipientTownName | BuyerTownName | Customer city | |
| CountryCode | CountryCode | Customer country code ISO3166 standard | |
| Delivery information to the invoice | |||
| DeliveryOrganisationName | Delivery name | ||
| DeliveryStreetName | Delivery address | ||
| DeliveryPostCodeIdentifier | Delivery country code | ||
| DeliveryTownName | Delivery city | ||
| CountryCode | Delivery country code ISO3166 standard | ||
Customere details to the customer card (if not exist) | |||
| InvoiceRecipientPhoneNumberIdentifier | BuyerPhoneNumberIdentifier | Phone number | |
| InvoiceRecipientEmailaddressIdentifier | BuyerEmailaddressIdentifier | ||
| InvoiceRecipientEmailaddressIdentifier | BuyerEmailaddressIdentifier | Email invoicing address | |
| ToIdentifier | E-invoice address | ||
| ToIntermediator | E-invoice operator | ||
| Invoice row | |||
| ArticleIdentifier | Product code | Product code when createing a new product or targeting to an existing product | |
| ArticleName | Product name | ||
| RowAmount | Product unit price | Calculated on the basis of line sum, delivered quantity and discount | |
| RowDiscountPercent | Discount percent | ||
| DeliveredQuantity | Product quantity | ||
| RowVatRatePercent | VAT-percent | ||
| RowNormalProposedAccountIdentifier | Accounting suggestion | ||
| RowFreeText | Row free text | ||
| RowIdentifier | Order number | ||
Dimensions of the invoice row's | |||
| RowDefinitionHeaderText | Dimension header | ||
| RowDefinitionValue | Dimension item | ||
| Product details to the product card (if not exist) | |||
| ArticleIdentifier | Product code | ||
| ArticleName | Product name | ||
| RowAmount | Product unit price | Calculated on the basis of line sum, delivered quantity and discount | |
| RowDiscountPercent | - | ||
| DeliveredQuantity | - | ||
| Attribute: QuantityUnitCode | Unit | ||
| RowVatRatePercent | VAT-percent | ||
| Comment row | |||
| RowFreeText | Comment row | Element must be the only element in the InvoiceRow |
To be able to import scandinavian letters (å, ä, ö) the material needs to be encoded in ISO/IEC 8859-15 form.
It is also possible to import dimension headers and dimension items in fields RowDefinitionHeaderText and RowDefinitionValue.
If customer doesn't exist in Netvisor before import, the e-invoice details and e-mail invoicing address are imported to Netvisor if this information is found in the finvoice file. And if customer is already in Netvisor, the e-invoice details/e-mail invoicing address are not updated from the finvoice file. E-invoice details/email invoicing address should be manually saved to customer details in Netvisor or imported using Customer import.
One Finvoice file can include multiple invoices. This way there is no need to import invoices one at a time.
Phases of Finvoice import
- Open Company menu and choose "Data import"
- Choose "Lasku/suoritus XML" (see picture below, step 1) and press "Selaa" (2)
- Find the right Finvoice file and press ""Submit data" -button (3). This starts the Finvoice import.
If there are no errors in the import, Netvisor will show a specification of imported data and links to formed material.
Finvoice import establishes customers and products used in the import if customers or products do not exist in Netvisor before import. Please note that customer's e-invoice details or e-mail invoicing addresses are not imported. If customers and products used in the import exist in Netvisor, the imported customers and products are targeted to existing ones.
If the imported material contains errors an error message is shown. The message tells why the material cannot be imported into Netvisor. If the material includes more than one invoice the invoices in right form are imported. There is an editor window below the error message but the material cannot be edited in that window. All changes to the invoice material must be done in the original file. After correcting the material the invoices can be imported again. Please do not edit the imported invoices in Netvisor after the import.
Did you find it helpful? Yes No
Send feedback