Skip to main content

Sending your invoices information from Ezus to your certified platform

As part of the electronic invoicing reform, your B2B invoices must be issued and received in a structured format (Factur-X, UBL or CII): a simple PDF sent by email is no longer enough.

💡 Depending on the country, electronic invoices are transmitted either through a central government portal or via certified e-invoicing service providers (often referred to as accredited platforms, PACs in Latin America, or Peppol Access Points in Europe).

This generic article explains how to transmit the billing information generated in Ezus to your certified e-invoicing service providers.

To learn more about the reform, we invite you to read our article ✍️ E-invoicing: Ezus prepares for new European requirements.

Ezus's role

⚠️ Ezus is not a certified platform.

Our role is to prepare your invoices (sales and purchases) with the right level of information and to make it easier to integrate them into your accounting ecosystem.

Once your invoices are generated in Ezus, you transmit their information to your your accounting system (for example Sage), which then takes over compliance (regulatory format), transmission and e-reporting.

⚠️ Be careful not to confuse "accounting tool" and "certified platform."

  • Some software (Pennylane, Sage, Cegid, Sellsy, Tiime, Qonto/Regate…) is both a management tool and a compliant platform

  • Others (EBP, Evoliz, Freebe…) are billing software that achieves full electronic invoicing compliance by integrating via a certified partner platform

Always check the status of your tool on your tax authority’s official list before relying on it for compliance purposes.

How to automate the transmission of your sales invoices from Ezus?

  • via Zapier: no code, recommended for most users

  • via API: for technical profiles and custom integrations.

💡 The Ezus API is available exclusively to customers who have subscribed to a Premium or Enterprise plan.

Prerequisites

Before you begin, make sure you have:

  • Your Ezus API credentials: go to Settings > Developers from https://pro.ezus.io/settings. The Ezus API expects two headers:

    • x-api-key: your API key

    • Authorization: Bearer <token>: your token

  • An active account on your certified platform (Pennylane, Sage…), with the necessary access to its connector or its API.

⚠️ Your API key and your token are sensitive data: keep them safe and never share them.

Option 1: integration via Zapier (no code)

Zapier is an automation tool that connects your Ezus account to thousands of other applications, with no development. For more information, feel free to read our article ✍️ Use the Zapier x Ezus integration.

Here are the concrete steps to follow:

  1. Connect Ezus to Zapier using your API credentials.

  2. Choose the Ezus trigger that starts the automation.

  3. Choose the action on the certified platform side: creating or importing the invoice into your PA.

  4. Map the fields between Ezus and your certified platform: amount excl. VAT, amount incl. VAT, VAT, customer, project, invoice number, dates…

  5. Test the Zap with a real invoice, then activate it.

For any issue related to Zapier, contact Zapier support directly.

Option 2: integration via the Ezus API

If you want to go further, the Ezus API lets you build a custom integration between Ezus and your certified platform. Before you start, feel free to read our article ✍️ How to use the Ezus API.

Find our documentation at api.ezus.io.

💡 Not to be confused with the API base URL, which is api.ezus.app.

The API distinguishes two routes depending on the invoice type:

  • Sales invoices (customers): GET https://api.ezus.app/invoices

  • Purchase invoices (suppliers): GET https://api.ezus.app/invoices-supplier

Here are the concrete steps to follow:

1. Retrieve your invoices from Ezus via the corresponding route (sales and/or purchases).

2. Retrieve the information to be transmitted, for instance:

The returned list is paginated (50 per page): to display the next 50 items in the list, call the route using the next_token query parameter.

3. Send this data to your certified platform's API.

💡 Specific to sales invoices: the /invoices route exposes the is_einvoice_ready field (boolean), which indicates that an invoice is ready for electronic invoicing, and accepts the ?stage=completed filter.

Neither of these two elements exists on the purchases route /invoices-supplier.

Set the synchronization frequency according to your needs:

  • Real time: with each new invoice

  • Scheduled: every hour or every day

  • Triggered: on a specific event

Points to watch

  • Compliance (regulatory formats, transmission, e-reporting) is handled by your certified platform, not by Ezus.

  • Filter the invoices to transmit: on the sales side, rely on stage=completed and/or is_einvoice_ready so you don't send drafts to your certified platform. On the purchases side, since this filtering isn't available, plan your own selection logic.

  • Check the mapping of VAT and the amounts excl./incl. VAT to avoid any accounting discrepancy.

  • Plan a safeguard against duplicates, especially with a scheduled Zap.

  • A valid connection / key is required on both sides (Ezus and the certified platform).

  • Don't forget the purchases side: the receiving obligation also concerns your supplier invoices, hence the dedicated /invoices-supplier route.

Did this answer your question?