Reseller story · Eventify
Peppol invoices ship with every ticket sold.
Eventify built their own ticketing platform from the ground up. As Peppol rolled out across Europe, they wired e-invoice.be's API straight into the checkout. Any buyer who wants a Peppol invoice gets one. No ERP detour. No PDF in anyone's spam folder.
The platform
Registration, ticketing, networking, badges. Now Peppol.
Eventify runs the full event lifecycle for thousands of event managers worldwide. In-person, hybrid, virtual. The Peppol invoice option now sits inside the same checkout the buyer is already in.
- 5,000+
- event managers run Eventify
- 40+
- countries with live events on the platform
- 99%
- positive reviews on G2
Source: eventify.io.
Three moving parts. One checkout.
Eventify hosts thousands of events. Each one is run by a different organiser with their own VAT number and accounting setup. The integration is built around that fact.
Multi-tenant by design
One organisation key for Eventify. A scoped API key for every event organiser on the platform. Invoices go out under the organiser's name and VAT number, not Eventify's.
Verified Peppol delivery
Every invoice comes back with a signed receipt from the buyer's access point. Eventify sees real delivery status, not 'did the PDF land in their inbox' guesswork. No silent failures, no support tickets asking where the invoice went.
Credit notes when events cancel
If a show is called off the week before, the refund needs a credit note. Same JSON payload as the invoice, with the document type flipped. Both documents flow over Peppol.
Eventify could have built an access point. They chose not to.
The numbers Eventify ran on becoming a Peppol Access Point themselves versus partnering with e-invoice.be. The same numbers apply to any SaaS that bills on behalf of its customers.
- 01
OpenPeppol membership and access point certification
Build it yourself
Required. Several months of conformance testing and a signed Transport Infrastructure Agreement.
Partner with e-invoice.be
Already done. You inherit our certification.
- 02
BIS Billing 3.0 and EN 16931 spec maintenance
Build it yourself
Your team tracks every CEN and Peppol release, ships schema updates, runs validation.
Partner with e-invoice.be
Our problem. The API stays at the current BIS.
- 03
Time to first compliant invoice in production
Build it yourself
Nine to twelve months realistic, longer if you have not shipped XML at scale before.
Partner with e-invoice.be
Days. One API key, one POST, one Peppol receipt back.
- 04
Multi-tenant invoicing on behalf of your customers
Build it yourself
Build the tenant model, the scoped keys, the audit trail, the per-tenant Peppol registration flow.
Partner with e-invoice.be
Built in. One organisation key for you, scoped keys per tenant.
- 05
Network monitoring and 24/7 uptime
Build it yourself
Your on-call rotation answers when an SMP lookup fails at 3am.
Partner with e-invoice.be
Ours does.
- 06
Cost model
Build it yourself
Engineering headcount, certification fees, OpenPeppol annual fee, ongoing compliance.
Partner with e-invoice.be
Pay per document. No setup fee. Cancel anytime.
- 07
Liability for non-compliant invoices
Build it yourself
Yours.
Partner with e-invoice.be
Shared. We are the certified access point on the wire.
How it runs in production
One API call per ticket. One more when an event cancels.
- 01
Buyer picks Peppol invoice at checkout
Any buyer with a Peppol ID can ask for a structured invoice instead of a PDF. They drop in their company VAT number and Peppol address at checkout.
- 02
Eventify calls the API under the tenant key
The ticketing checkout fires a single API call to e-invoice.be using the organiser's scoped tenant key. The document is created and signed on the organiser's behalf.
- 03
e-invoice.be ships the invoice over Peppol
As a certified Peppol Access Point, e-invoice.be hands the structured invoice to the buyer's access point. The buyer's accounting software receives it directly.
- 04
Cancellation? A credit note travels the same path
If the event is called off, Eventify's refund flow fires a second API call with document type set to credit note. The two documents net out cleanly on the buyer's side.
“Our organisers needed Peppol invoices the day buyers started asking. Becoming an access point ourselves was never on the table. e-invoice.be gave us a clean multi-tenant API, and it pays for itself on every ticket where a buyer asks for one.”
Hussain FakhruddinFounder & CEO, EventifyReseller FAQ
Questions every platform asks before they wire us in.
Can my platform issue Peppol invoices on behalf of my customers?
Yes. The reseller API is multi-tenant by design. You hold one organisation key. Each of your customers gets a scoped tenant key. Invoices ship under the tenant's name and VAT number, not yours, and the tenant remains the legal sender of record.
What is multi-tenant scoping in practice?
One organisation key authenticates your platform. A scoped tenant key identifies the customer the invoice belongs to. Every API call carries the tenant key, so the document is signed and delivered on that tenant's behalf. The audit trail keeps the two separate.
Do we need to become a Peppol Access Point ourselves?
No. e-invoice.be is a certified Peppol Access Point. Your platform uses our API. Our certification carries the document. You skip OpenPeppol membership, conformance testing, and the ongoing BIS spec work.
What happens when a buyer is not yet on the Peppol network?
The API returns a clear status and you fall back to a PDF or email delivery for that buyer. Once the buyer registers their Peppol ID, subsequent invoices go over Peppol with no change on your side.
How do credit notes for cancellations and refunds work?
Same JSON payload as the invoice, with the document type set to CREDIT_NOTE and a reference to the original invoice ID. The credit note travels the same Peppol path and nets out cleanly in the buyer's accounting software.
Who owns the relationship with the Peppol authority, you or us?
e-invoice.be is the access point of record on the wire. Your customer is the legal sender of the invoice, registered on Peppol under their own VAT number. You sit in the middle as the platform issuing the document on their behalf.
Is there a setup fee for the reseller program?
No setup fee. No monthly minimum. Pay per document sent or received. You can leave whenever you want.
What does a typical reseller onboarding look like?
Typically one week. After you sign the reseller agreement we issue both a development and a production API key. Your team integrates against the development key, flips to production when you are ready to go live, and starts issuing tenant keys per customer from there.
Got a platform that issues invoices?
If your software bills on behalf of other companies, whether you sell tickets, run a marketplace, manage rentals, or invoice for clients, the same reseller arrangement is open to you. No setup fee. Pay per document. Leave whenever.
Further reading: Peppol invoicing for events, written by the Eventify team.