Ways to e-invoice from Stripe: Marketplace apps, APIs and DIY compared

By evoicely · Last checked 21 October 2026

Stripe doesn't create e-invoices itself, so you add something: a Stripe App Marketplace app, an outside service fed by Stripe's webhooks, your own code, or a different billing platform. Which one fits depends mostly on two things: which countries your business customers are in (Germany needs XRechnung or ZUGFeRD, Belgium needs Peppol, France needs a plateforme agréée), and whether you want the files delivered for you or just generated. This page compares the routes and the tools we found, with what each vendor's own page said on the day we checked.

evoicely is one of these tools, so we're not neutral. We've kept to facts the vendors publish themselves, linked each one, and listed what we don't do. If something here is out of date, tell us and we'll correct it.

What Stripe says it does

Stripe's documentation says Stripe Invoicing "creates invoice records and exposes invoice data through our API and webhooks, but doesn't generate or transmit legally compliant e-invoice files on its own", and that it "relies on specialized third-party providers to handle generation, validation, and delivery". It names Billit as its "preferred e-invoicing partner" and points to the other providers in the Stripe App Marketplace. (Stripe docs: E-invoicing) For the background, see Does Stripe support e-invoicing?

The short version

• Customers only in Germany: you need ZUGFeRD in the EN 16931 profile (or higher), or XRechnung, emailed to your customer. Several German apps and services do this; check that credit notes are covered and which profile you get.
• Customers only in Belgium: you need Peppol BIS Billing 3.0 sent over the Peppol network, and each customer's Peppol ID. Pay-per-send Peppol apps are the cheapest start; check what happens to customers without a Peppol ID.
• Germany and Belgium: few tools cover both, so compare those first.
• France, or many countries at once: you need a provider connected to a French plateforme agréée (PA), or a multi-country platform. These tend to cost more.
• You only want the XML and will deliver it yourself: a conversion API or an open-source library is enough.

What to compare

• Formats and profile. In Germany, ZUGFeRD MINIMUM and BASIC WL don't count as e-invoices. A page that says "ZUGFeRD" without a profile leaves that open (see ZUGFeRD profiles explained).
• Delivery. Does it email the file or send it over Peppol, or does it only hand the file back to you?
• Credit notes. A correction of an e-invoice should be an e-invoice too.
• Payments without an invoice. Checkout and Payment Links sales have no Stripe invoice unless you switch invoice creation on.
• Buyer identifiers. Stripe has no field for a Peppol ID or a Leitweg-ID. Where does the tool get them, and what does it do when one is missing (Peppol IDs in Stripe)?
• Validation. Which rules does it check against (KoSIT for XRechnung and ZUGFeRD, the Peppol BIS 3.0 schematrons), and can you see the result?
• Pricing model. Per send, per month or per pack, and whether prices include VAT.

Stripe App Marketplace apps

These install from the Stripe App Marketplace and read your invoices from Stripe. Listed in no particular order; facts and prices as each vendor's own page stated them on 21 October 2026.

The Marketplace also has single-country apps, for example A-Cube for Italy. They're left out here because they don't cover Germany, Belgium or France.

Services that connect outside the Marketplace

These connect with Stripe Connect, a restricted API key or a webhook, or work from files you send them.

Build it yourself

If you'd rather own the pipeline, Stripe documents the flow: listen for invoice events (Stripe suggests invoice.created, because finalized invoices can't be edited), fetch the invoice, map it to the format and send it through a provider. Two well-known open-source libraries help with the file itself:

• Mustang (Java, Apache-2.0): reads, writes and validates ZUGFeRD/Factur-X and CII XRechnung.
• factur-x by Akretion (Python, BSD 3-Clause): embeds the XML in a PDF to make a Factur-X/ZUGFeRD file, extracts it again, and checks it against the XSD and schematron.

The libraries don't map Stripe's discounts, taxes and rounding onto the EN 16931 rules, deliver over Peppol or archive anything. That's the bulk of the work.

Move invoicing off Stripe

Some billing platforms include e-invoicing. Chargebee, for example, says it supports e-invoicing "across 20+ countries" (Chargebee). Switching means migrating subscriptions, payment methods and customer data, so it usually makes sense only if you were going to move anyway.

What evoicely does and doesn't do

• Does: converts every finalized Stripe invoice and credit note to ZUGFeRD (EN 16931) or XRechnung for German customers and Peppol BIS 3.0 for Belgian ones, checks each file with the official validators and gives you the report.
• Doesn't, yet: France (evoicely is not a plateforme agréée; delivery through one is planned), other countries, or a Stripe App Marketplace listing.
• Doesn't ever: give tax advice or guarantee that an invoice is compliant.

Try it free on 10 e-invoices a month, or check a file you already have with the free validator.

For the deadlines that make this necessary, see EU e-invoicing deadlines by country.

Vendor details come from each vendor's public pages as of the date above. Features and prices change, so check the vendor's site before you decide. This is general information, not legal or tax advice.