Tax guide · E-invoicing and transmission

Receiving e-invoices: obligations and readiness

The obligation to receive can start earlier or apply more broadly than the obligation to issue. Readiness means accepting, validating, routing and retaining structured invoice data, not merely opening an email attachment.

01

What to verify

  • Invoice date, transaction type and company criteria

  • Receiving, issuing, transmission and reporting as separate duties

  • Structured format, profile, platform and transitional rule

02

Practical workflow

  1. 1

    Capture the decisive facts and select the correct jurisdiction and date.

  2. 2

    Resolve the time-valid rule and record its source, version and open questions.

  3. 3

    Align invoice, accounting, reporting and evidence; route uncertainty to review.

03

Worked example

A small company receives its first structured invoice. It tests the channel, rendering, validation, approval and compliant retention.

Check e-invoicing obligations →

04

Common mistakes

  • !

    Treating a PDF as a structured e-invoice

  • !

    Checking one headline deadline instead of separate duties

  • !

    Validating syntax without business and tax validation

05

Invoice and accounting impact

The result should be represented consistently in the invoice, structured data, accounting, reporting and evidence. If a decisive fact changes, the decision is recalculated and the previous version remains in the audit trail.

06

Legal basis and official sources

The page links to official primary sources. The actual decision is made by the versioned Dynafis rule set.