Tinklaraštis
    Standards12.2.2026

    EN 16931 ja rakenteinen laskudata: mitä se tarkoittaa kirjanpidolle

    EN 16931 on EU:n standardi verkkolaskun rakenteiselle datalle. Käymme läpi, mitä standardi tarkoittaa kirjanpidon kannalta ja miten pienyritys hyötyy rakenteisesta datasta.

    EN 16931 is an EU standard for structured data in e-invoices. It defines what information an electronic invoice must contain. In this article, we will go through what the standard means for accounting and how a small business benefits from structured data.

    Structured data vs. PDF – why does it matter?

    A PDF invoice is a human-readable image. A structured invoice (e.g. Finvoice, Peppol BIS) is machine-readable data. The difference is significant for accounting:

    OminaisuusPDF-laskuRakenteinen lasku
    TiliöintiManuaalinen tai OCR (virhealtis)Automaattinen sääntöjen perusteella
    ALV-käsittelyTarkistettava käsinALV-koodit mukana datassa
    ArkistointiErillinen tallennusIntegroituu suoraan kirjanpitoon
    HakeminenHankalaHelppo (hakukentät)
    VirheetYleisiä (näppäilyvirheet)Harvinaisia (data siirtyy suoraan)

    The purpose of the EN 16931 standard

    EN 16931 is a European standard that defines the minimum content of an e-invoice. It emerged from EU Directive 2014/55/EU and is mandatory for public sector invoicing.

    The standard defines, for example:

    • Mandatory data fields (seller, buyer, invoice amount, VAT breakdown)
    • Structure of invoice lines
    • VAT categories and codes
    • Presentation of payment terms
    • Handling of attachments

    Skaityti daugiau about e-invoicing legislation in our e-invoicing article.

    Benefits in accounting

    When invoice data is in a structured format, accounting benefits significantly:

    • Automatic accounting entry: the system can allocate the invoice line to the correct accounting account
    • VAT calculation becomes automated: VAT codes are transferred directly from the invoice data
    • Reconciliation speeds up: payments are automatically allocated to invoices
    • Reporting improves: reports can be generated directly from structured data
    • Reduction of errors: no manual data entry

    Preparation in a small business

    1. Ensure that your invoicing software produces EN 16931-compliant e-invoices
    2. Implement financial management software that can receive and account for structured invoices (e.g., Eemel Accounting)
    3. Request e-invoices from your suppliers instead of PDF invoices
    4. Activate automatic accounting entries and VAT rules
    5. Utilize structured data in reporting

    Skaityti daugiau about the impact of GDPR on financial management in our GDPR article.

    Practical example: construction company and purchase invoice processing

    A small construction company previously received purchase invoices as PDFs via email. The accountant manually entered each invoice into the accounting system. Typically, processing time was 5–10 minutes per invoice.

    Transitioning to receiving structured e-invoices in Eemel Accounting:

    • Purchase invoices arrive directly in the software as structured data
    • Automatic accounting entry allocates the invoice to the correct account
    • Processing time dropped from 5 minutes to less than 1 minute per invoice
    • Monthly invoice processing collectively sped up by approximately 4 hours

    Try it in practice

    Eemel Accounting automatically receives and accounts for structured e-invoices. Accounting becomes more efficient.

    Start for free

    Frequently asked questions

    Is EN 16931 mandatory for small businesses?

    Yes, for invoicing in the public sector. For the private sector, it is a strong recommendation and practically the standard for e-invoicing.

    Does Eemel Accounting support the EN 16931 standard?

    Yes. Eemel supports Finvoice and Peppol BIS formats, which are EN 16931-compliant.

    How does structured data reduce errors?

    Data is transferred directly from one system to another without manual input. Data entry errors and incorrect accounting entries are significantly reduced.

    Can PDF invoices be converted into structured ones?

    OCR technology can read PDF invoices, but the result is prone to errors. A better solution is to ask suppliers for e-invoices directly.

    How does ViDA relate to EN 16931?

    ViDA (VAT in the Digital Age) requires structured invoice data. EN 16931 is the standard on which ViDA's requirements are based.

    This article is general in nature and does not constitute legal advice.

    Už Eemel stovi Epic Invoicing Oy | Įmonės kodas: 2571844-9 | PVM kodas: FI25718449

    Visiškai Suomijos nuosavybė | Buveinė: Tampere, Suomija