Choose the output you actually need.
The current creator produces a printable document and application-owned structured data. It does not yet generate a recognised standards-based e-invoice. A PDF or JSON file alone does not establish standards compliance.
Working outputs
| Output | What it contains | What to expect |
|---|---|---|
| Printable invoice | Seller, buyer, dates, items, amounts, tax breakdown, payment instructions and notes. | Uses your browser print dialog. Save as PDF depends on your browser. No embedded invoice XML. |
| Structured JSON | Versioned application schema, entered fields and recalculated totals in minor units. | Useful for revising or integrating the data. No EN 16931 mapping or formal standards validation. |
| Line items CSV | Invoice reference, item fields, tax categories and per-line amounts. | Useful for spreadsheets. Does not contain the full supplier/customer invoice record. |
| Editable JSON draft | The editable application model, including incomplete entries. | Save your work and import it again. No validated-invoice claim. |
Formats discussed, not implemented
EN 16931, XRechnung, ZUGFeRD, Factur-X and Peppol are relevant when choosing a structured invoicing workflow. They are listed here to explain the product boundary. The creator does not generate or validate them, and does not deliver documents through Peppol.
- EN 16931: formal semantic mapping and business-rule validation are planned.
- XRechnung: an implementation-specific XML adapter and verification are planned.
- ZUGFeRD / Factur-X: embedded XML PDF output and appropriate verification are planned.
- Peppol: supported document profiles and routing integration are planned.
Country context is not a country profile
Germany, France, Belgium, Poland and the other country choices record the context and party addresses. They do not apply national rules, tax rates, mandatory identifiers or submission requirements. There are no country-specific compliance guarantees.
Before sharing an invoice
Confirm your recipient’s required format and the rules applicable to your transaction. Field validation helps review this application’s inputs, but does not replace formal invoice validation.
Create or revise an invoice ↗