What is e-invoicing?
Section titled “What is e-invoicing?”E-invoicing is the creation, transmission, and receipt of invoice data in a structured electronic format (XML, not PDF) that allows automated validation and processing by software systems. It replaces manual PDF- or paper-based invoicing with electronic invoicing.
fiskaly’s E-INVOICE product handles format generation, validation, transmission to national platforms, and, in Italy, long-term archival — so you do not need to implement country-specific formats and submission protocols yourself.
E-INVOICE covers B2B e-invoicing, and in Italy also invoices issued to consumers. SIGN covers transaction signing at the POS. They are independent products. You may need one, the other, or both depending on your business.
How it works
Section titled “How it works”The integration follows the same pattern across all countries:
- Authenticate —
POST /authwith your API credentials (same as SIGN) - Create an e-invoice — Submit the e-invoice data with country-specific payload fields
- fiskaly validates — Schema and business rule validation before submission
- fiskaly transmits — Delivery to the national platform (Peppol, SDI, PPF, KSeF)
- Track status — Retrieve delivery and acceptance status
Invoice content and layout
Section titled “Invoice content and layout”E-INVOICE has no layout editor. The invoice content follows the EN 16931 data model and is built entirely from the data you send in the API request, so there is no template, logo or design to configure.
You can retrieve the generated invoice file through the API at any time.
European regulatory context
Section titled “European regulatory context”E-invoicing requirements across Europe are driven by the EN 16931 standard — a common semantic data model for invoices. Each country adds its own:
- Format — XRechnung, Factur-X, FatturaPA, etc.
- Transmission network — Peppol, SDI, PPF, KSeF
- Mandate timeline — when B2B e-invoicing becomes mandatory
- Archival rules — how long invoices must be stored
fiskaly abstracts these differences behind a single API. Your integration work on the first country carries forward to every subsequent market.
The Integration Guide covers the shared API surface. Country-specific requirements are added on top of the base schema — early integration work is not wasted.