E-invoicing
PDF invoice or structured E-Rechnung? Be clear about the difference.
A PDF is a human-readable document. A structured e-invoice is machine-readable and must be generated and validated against the applicable technical standard. InvoiceFlow does not blur that line.
PDF invoice
Seller-branded A4 invoice with InvoiceFlow numbering, immutable snapshots and downloadable PDF. A PDF alone is not a structured E-Rechnung.
Structured XML
The architecture is prepared around EN 16931, but official schema and business-rule validation is not implemented. InvoiceFlow does not generate or claim a compliant XRechnung file yet.
Hybrid PDF + XML
A hybrid document is only valid when the embedded XML is generated and validated correctly. InvoiceFlow does not currently produce a ZUGFeRD file or label a plain PDF as ZUGFeRD.
What InvoiceFlow does today
Generates seller-issued PDF invoices, stores them with a SHA-256 hash and supports downloadable archives.
Maintains a structured invoice domain with tax categories, snapshots and eligibility rules.
Keeps PDF and structured e-invoice concepts separate in the data model and UI.
Does not claim German tax compliance or a legally validated format.
InvoiceFlow
Need structured e-invoicing as part of your workflow?
Tell us about your business and the formats you need. We do not sell unimplemented compliance.