Finvoice validation

Structure and content validation at once

Finvoice validation with ease

Check whether your Finvoice message (3.0/2.01/2.0/1.3/1.2) complies with general structure, format and content requirements.

Quick test generates an overview of errors in Finvoice message.
Order Finvoice test package to get a detailed test report of all errors.
Finvoice 3.0

Finvoice test package

  • Finvoice versions 3.0/2.01/2.0/1.3/1.2 Covers commercial invoices and credit notes, likewise, direct payments using Finvoice 2.01-3.0.
  • validation with(out) SOAP envelope
  • schema validation
  • over 100 content checks
  • basic validation for SOAP envelope
  • basic validation for attachments
  • unlimited number of tests Finvoice 3.0 validation
    General invoices: 130 business rules
    EN16931 invoices: 200 business rules
    Public procurement: 60 additional rules

Finvoice test report example
Finvoice examples Finvoice testaus this page in Finnish

Finvoice is the de-facto XML standard for electronic invoicing in Finland. Finvoice messages usually pass structure validation (schema validation) but content issues prevent fully automated processing. Once EU directive 2014/55 is applied, receivers are allowed to reject invoices with incomplete content.

Efficiency via test automation

Truugo provides an easy solution to validate messages efficiently and accurately as a self-service. Test automation saves a substantial amount of time and detailed validation helps you to sleep better at night.

Easy quality assurance for Finvoice messages

Our Finvoice validators contain over 100 content checks, in addition to traditional structure validation. This covers checks related to data repetition, data format, allowed codes but especially to logical interdependencies.

Truugo generates a test report which contains a sensible description and a reference to an invalid message element for each error. Thus both IT developer and business expert will receive a sensible feedback for resolving those issues.

Checks are based on Finvoice's message implementation guideline (defined by Federation of Finnish Financial Services), general invoice requirements and semantic model (EN16931).

You can also setup customized XML validator and provide it as a self-service for your supplier network.