Launch partner programme · limited to 3 companies

E-invoicing in your software.
Your brand. No XML.

Embed legally compliant e-invoices (EN 16931, ZUGFeRD/Factur-X) in your SaaS via iframe (fast) or via API (full design control), in your own corporate design, without our brand. Your end customers do not create an account with us; usage is billed to your quota.

EN 16931KoSIT-validated, § 14 of the German VAT Act (UStG)
Art. 28DPA included, hosted in Germany
iframe + APIin your own design, no account
3 placeswith personal support

See it live

This is exactly the form you embed, shown here embedded, pre-themed and with automatic height. Fill it in and create a real ZUGFeRD PDF (demo, nothing is stored).

A dependency that is safeguarded

You rely on us for a core process. That is why safeguards come before everything else.

Legally compliant & validated

PDF/A-3 with embedded XML according to EN 16931, checked against the official KoSIT validator, complete under § 14 UStG, VAT ID verified live via EU VIES.

GDPR & DPA

Data processing agreement under Art. 28 GDPR (DSGVO) included, hosting in Germany, documented deletion policy, data export at any time.

Stable operations

Automatic monitoring with alerting, verified daily backups, fast deployments, adjustments the same day instead of in weeks.

Building e-invoicing yourself takes months and ties up your best developers. We deliver the validated part; you keep your product and your brand.EN 16931 · ZUGFeRD 2.x · Factur-X · XRechnung validation

Three ways to e-invoicing in your own product

If your SaaS needs to issue e-invoices, you realistically have three options. Which one fits depends on how close e-invoicing is to your core business.

Option 1

Build it yourself with a library

Full control, no ongoing third-party costs. In return you carry EN 16931, the German BR-DE rules, PDF/A-3 generation and every format change yourself, permanently. Sensible if e-invoicing is part of your core product.

Option 2

Ready-made portal with a third-party brand

Quick to launch, but your end customers create an account with the provider and see its brand. The break in the user journey stays visible, and the customer relationship is shared.

Option 3

Embed white-label

The option offered here: the form via iframe or API in your design, without our brand, with no account for your end customers. You keep your product and the customer relationship, but hand a core process to a service provider. That is why there is a DPA, hosting in Germany and data export at any time, so the dependency stays contractually manageable.

How to become a launch partner

1 · Call

Initial call

We get to know your product and your use case and work out the integration together.

2 · Co-integration

Supported integration

We support your developers in embedding the iframe and the signed tokens, with a direct line to our team.

3 · Live

Live on your quota

Your end customers create e-invoices in your design; usage is charged to your credit.

What the first 3 partners get

Personal support instead of off-the-shelf plug-and-play, with real safeguards instead of a discount stamp.

Founder terms

Permanently frozen price

Your introductory terms remain in place long term, so you can plan, even if prices rise later.

Direct line

Shared channel with the team

No ticket system: a shared channel, a named contact person, adjustments the same day through our CI.

Safeguarded

DPA, data export, hosting in Germany

Contractually contained risk: data processing under Art. 28 GDPR, export at any time, hosting in Germany.

Included

Supported integration, no setup costs

We integrate the embed together with your developers, including theming, auto-resize and success events. No setup fee for launch partners.

Secure one of the 3 places

Briefly outline your product and we will get back to you personally to arrange an initial call (usually within one business day).

Prefer to write directly? office@fhcp.de

FAQ from SaaS providers

Is there an alternative to building ZUGFeRD yourself?

Yes. Instead of implementing and permanently maintaining EN 16931, the German BR-DE rules and PDF/A-3 generation yourself, you embed the finished form via iframe or integrate the API into your product. The difference from a ready-made portal: it runs in your design, without our brand, and your end customers do not create an account with us.

Will my end customers see that a service provider is behind it?

No. The embedded form carries your corporate design (colours, corner radii, title) and none of our branding. There is no sign-up or login step with us for your end customers, and billing runs through your quota.

What happens to my data if we part ways?

A data processing agreement under Art. 28 GDPR (DSGVO) applies, hosting is in Germany, and you can export the invoices as PDF and XML at any time. The dependency is therefore contractually and technically manageable, which is the decisive point for a core process.

iframe or API: which is better?

The iframe is integrated in hours and comes with the form, validation and PDF generation ready-made. The API gives you full control over the interface but costs development time. Many start with the iframe and switch later; both use the same validated generation in the background.

Can we also check e-invoices with it, not just create them?

Yes, via POST /v1/check. This lets you validate your end customers' incoming invoices against EN 16931, including the check for manipulated bank details.

Log in

Forgot your password?

No account yet? Sign up now

Sign up

B2B offer for businesses and self-employed professionals; a tax number or VAT ID is required.

At least one of the two is required.

Already registered? Log in