#Scribo vs Stripe Invoicing
Stripe Invoicing is a pay-per-paid-invoice layer on top of Stripe payments that outputs PDFs, not EN 16931 XML; Scribo is free and emits compliant XRechnung and ZUGFeRD — so many teams keep Stripe for collecting payment and add Scribo for the compliant file. They solve different halves of the same workflow.
Factual comparison only — not tax or legal advice. Competitor details are as of June 2026; check stripe.com/invoicing for current pricing and features.
#At a glance
| Scribo | Stripe Invoicing | |
|---|---|---|
| Price | Free, no per-invoice fee (fair-use limits) | No monthly fee; a percentage per paid invoice, plus payment-processing fees |
| Collects payment | No | Yes (its core purpose) |
| EN 16931 formats (XRechnung, ZUGFeRD) | Yes (live) | Not natively (PDF output) |
| US plain PDF | Yes | Yes |
| Validated at generate time | Yes (Invopop EN 16931 validator) | — |
| Public HTTP API | Yes (/api/v1) |
Yes (extensive) |
| First-party agent surface | Yes (MCP, CLI, skill) | Yes (MCP / agent tools, payment-oriented) |
| Operator | Causa Prima Germany GmbH | Stripe, Inc. |
#When Stripe Invoicing is the better fit
If your priority is getting paid — sending an invoice with a "pay now" card link and collecting the money — Stripe Invoicing is purpose-built for that, with deep payment tooling. For many US and online businesses with no EU structured-invoice requirement, a Stripe PDF is all they need.
#When Scribo is the better fit
If you need an EN 16931-compliant structured invoice that Stripe doesn't produce — for a German or EU buyer who requires XRechnung or ZUGFeRD — Scribo generates and validates it for free. It's also the fit for agent-driven generation: via the hosted MCP server, CLI, or skill, a billing agent can produce the compliant document directly.
#Use them together
These aren't mutually exclusive. A common pattern: Stripe for the payment rails, Scribo for the compliant document. You collect payment through Stripe and generate the EN 16931 invoice through Scribo, free.
#The honest limits of each
- Scribo generates the compliant invoice file only — it does not collect payment or keep books.
- Stripe Invoicing does not natively produce EN 16931 structured invoices, and charges a percentage of each paid invoice.
#Frequently asked questions
Does Stripe Invoicing produce XRechnung or ZUGFeRD? Stripe Invoicing produces PDF invoices and is built around collecting payment; it does not natively generate EN 16931 structured formats like XRechnung or ZUGFeRD. Scribo generates those compliant formats. Many teams keep Stripe for payments and use Scribo for the compliant file.
Is Scribo cheaper than Stripe Invoicing? Scribo is free with no per-invoice fee. Stripe Invoicing charges a percentage of each paid invoice on top of payment-processing fees. But they do different things — Stripe collects the payment; Scribo does not. The cost comparison only matters where you need the compliant document, not payment collection.
Can my Claude or MCP agent create a compliant invoice instead of a Stripe PDF? Yes. Scribo exposes a hosted MCP server, a CLI, and a Claude/Codex skill, so an AI assistant or billing agent can generate a validated EN 16931 invoice directly. Stripe also offers agent/MCP access, but for payment and billing operations rather than EN 16931 e-invoice generation.
Does Scribo collect payment? No. Scribo only generates the compliant invoice file. It does not process card payments or collect money — that is what a payment platform like Stripe is for. The two are complementary.
See also: What is EN 16931? · What is XRechnung? · Best free e-invoicing tools · Scribo compliance posture. Competitor facts as of June 2026 — verify on the vendor's site.