Tax guide · E-invoicing and transmission

E-invoice formats and transmission channels

Format, profile and transport channel are separate decisions. A syntactically valid XML file may still fail if the recipient profile, mandatory data or network rules do not match.

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 supplier has UBL but the buyer requires Peppol BIS or a national profile. Dynafis checks mapping and target requirements.

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.