fiskaly E-INVOICING

Introduction

fiskaly E-INVOICING is a cloud-based electronic invoicing solution that enables POS providers, ERP system vendors, and businesses to create, validate, send, and receive electronically structured invoices in compliance with the European Norm EN 16931. The service leverages the Peppol network for the transmission and receipt of e-invoices and ensures that all outgoing invoices are fully compliant before delivery. It is accessed via a RESTful API and managed through the fiskaly HUB. The service is currently available in Belgium, with additional European markets planned.

Service Description

fiskaly delivers the fiskaly E-INVOICING service to the CUSTOMER, enabling the following:

E-invoice creation: Based on the invoice data submitted by the CUSTOMER, the service generates electronically structured e-invoices that comply with the format requirements of EN 16931 (European Norm).
E-invoice transmission via Peppol: E-invoices can be sent to recipients via the Peppol network.
Pre-send validation: Before an e-invoice is transmitted, the service performs a validation of its format and structure, ensuring that no e-invoices are sent that do not comply with EN 16931.
E-invoice reception: The CUSTOMER can receive national and international e-invoices via the Peppol network.

Market availability: The above services are currently available in Belgium (additional countries coming soon).

Coming soon (planned features):

Optional: Sending the structured e-invoice via email (e.g., if the recipient does not have a Peppol ID).
Optional: Generation of an additional human-readable PDF version of the invoice.

Optionally available (connected service):

fiskaly SAFE integration: Automatic archiving of sent and received e-invoices via fiskaly SAFE (subject to separate pricing).

📘Note

fiskaly’s scope of services does not include: integration into recording systems; development of individual solutions or adaptations; training services; provision of internal documentation (except public integration instructions and API descriptions via workspace.fiskaly.com); data transfer services between the API and the END CUSTOMER’s IT systems; storage of data beyond the three (3) month period; support and assistance services not expressly specified in the contract; or other products of fiskaly.

Functionalities

Structured e-invoice creation: Generation of electronically structured e-invoices compliant with EN 16931, based on invoice data submitted by the CUSTOMER via the API.
Format and structure validation: Automated pre-send validation against EN 16931 requirements, aiming to prevent non-compliant invoices from being transmitted.
Peppol transmission: Sending of validated e-invoices to recipients via the Peppol network.
Peppol reception: Receipt of national and international e-invoices via the Peppol network.
API-first architecture: RESTful API for seamless integration into POS, ERP, or other invoicing systems.
Management via fiskaly HUB: Administration and configuration through the HUB.
Multi-market support: Currently available in Belgium; additional European markets planned.

System Requirements

A valid contractual relationship with fiskaly permitting use of the service.
An internet connection for integration and operation.
Integration of the fiskaly E-INVOICING API into the CUSTOMER’s POS, ERP, or invoicing system.
A system capable of providing the necessary invoice data in the format and schema specified by fiskaly via the API.
Access to the fiskaly HUB for administration and configuration.
Per registered taxpayer entity an uploaded proof of ownership document for verification of the taxpayer’s legal existence and registration status.

Maintenance and Support

fiskaly is committed to maintaining and updating the E-INVOICING service. fiskaly undertakes to maintain and update the Service with a view to supporting its security, availability, and ongoing alignment with applicable technical and reporting requirements; however, the Customer remains responsible for implementing required updates, migrations, and integration changes on its side. The service is versioned according to semantic versioning; significant changes resulting in new major releases will be documented. Maintenance activities may result in the temporary outage of the service. As far as possible, these activities shall be announced at least two (2) weeks in advance; emergency maintenance activities may deviate from this. fiskaly provides assistance to customers via the fiskaly support portal (support.fiskaly.com).

Testing

fiskaly provides a TEST environment for the E-INVOICING service. The TEST environment allows the CUSTOMER to validate its integration and e-invoice workflows before going live. fiskaly is not responsible if real data is provided in the TEST environment.

Service Limitations

The service currently supports Belgium; additional country availability will be communicated as it becomes available.
The completeness and correctness of the invoice data submitted by the CUSTOMER remain the CUSTOMER’s sole responsibility.
The validation performed by the service covers format and structure compliance with EN 16931; it does not verify the substantive tax correctness, legal classification, or business accuracy of the invoice content.
Transmission via Peppol requires the recipient to have a valid Peppol ID; alternative delivery methods (e.g., email) are planned but not yet available.
Changes in applicable laws, regulations, or Peppol network requirements may result in changes to the service.

Customer Obligations

Responsible for integrating the E-INVOICING API into the POS, ERP, or invoicing system.
Per registered taxpayer entity an uploaded proof of ownership document for verification of the taxpayer’s legal existence and the VAT identification number through the EU VIES system or an equivalent authoritative registry.
Customer shall fully comply with the applicable Peppol Authority Specific Requirements or equivalent jurisdiction-specific requirements applicable to that Sub-Merchant.
Customer shall maintain records of all KYC/KYB checks performed and shall make such records available to Provider upon request.
Customer shall perform ongoing monitoring of Sub-Merchant status, including periodic re-validation of VAT registration, and shall notify Provider without undue delay of any material change in a Sub-Merchant’s legal status, ownership, or VAT registration.
Customer warrants that it shall not permit any Sub-Merchant to access or use the Provider services unless and until the KYC/KYB due diligence described in this Section 2.5 has been satisfactorily completed.
Must provide complete, accurate, and timely invoice data in the format and schema specified by fiskaly via the API.
Must stay updated and implement required new releases and integration changes as communicated by fiskaly.
Must ensure that the invoice data submitted complies with applicable legal and tax requirements; the service validates format and structure but not substantive content.
Must manage the activation, configuration, and use of the service via the fiskaly HUB.

Version: v.1 | Last updated: 2026/03/24

Was this page helpful?