Because "What's the lawin', lass?" „Zahlen bitte!" « L'addition, s'il vous plaît ! » «Il conto, per favore!» «¿La cuenta, por favor?» «A conta, se faz favor!» „Poproszę rachunek!" "Notan, tack!" "De rekening, alstublieft!" «Τον λογαριασμό, παρακαλώ!» «Рахунок, будь ласка!» «Regningen, takk!» "Saisinko laskun?" „Fizetnék!" „Kontua, mesedez!" „Račun, molim!" "Hesap lütfen!" "Må jeg bede om regningen?" „Chönnti zahle?" "Could I get the bill?" should be an API call!
The
E-Invoicing Engine
ZUGFeRD & Factur-X API. JSON in, valid PDF/A-3 out.
Quick Start
Copy, paste, run. Working invoice in 30 seconds.
Demo API Key (included in the command below)
env_sandbox_demo_public
Unlimited sandbox usage. Watermarked PDFs. No account needed.
Copy & run — works out of the box, no signup required
Nine EU formats from one JSON payload. Nothing stored on our side.
Ready for the e-invoicing mandate
thelawin.dev generates electronic invoices per EN 16931. ZUGFeRD, XRechnung, Factur-X, Peppol and more from a single JSON input.
More on the e-invoicing mandate2025
Receive e-invoices
Mandatory for all businesses
2027
Send e-invoices (B2B)
Large enterprises >800k EUR
2028
Mandatory for all
No exceptions
Try it Right Now
Edit the fields below and generate a real ZUGFeRD 2.4 PDF. Uses sandbox mode.
Official Client Libraries
Type-safe SDKs for 8 languages. Fluent builder API, /retrieve support, 388 tests.
Ruby on RubyGems. All others install from GitHub.
All SDKs open source on GitHub. Missing your language? Let us know →
Simple Pricing
Free sandbox for testing. Upgrade when you're ready.
1 credit = 1× /generate or /retrieve. /validate is free.
Sandbox
For development & testing
€0 /forever
- 0 credits included
- All formats & profiles
- "SANDBOX" watermark
Need production invoices?
€4.90 / 100 credits (no watermark)
Recommended
Starter
For small businesses
- 500 credits / month
- No watermark
- Priority email support
Every plan includes full API access and all output formats.
Need more volume?
Let's talk.
Frequently Asked Questions
Common questions about thelawin.dev
What is thelawin.dev?
thelawin.dev is a Micro SaaS for EU-compliant e-invoicing. Send JSON via REST API, get a valid PDF/A-3 with embedded XML back.
Do you have a service or library somewhere in your infrastructure that creates PDF invoices from your data but isn't ready for EN 16931? thelawin.dev is your drop-in replacement.
Why do I need e-invoicing?
The EU mandates electronic invoicing for B2G (business-to-government) and increasingly B2B transactions. Germany: B2G since 2020, B2B receiving from Jan 2025, issuing from 2027. France: Sept 2026/2027. Italy: since 2019.
Think of the XML attachment as a "digital package insert" for your invoice: machine-readable, legally compliant, and required for doing business in the EU.
Who is this for?
Anyone who generates invoices programmatically:
- Enterprises – replace complex on-premise PDF libraries
- SaaS providers – add compliant invoicing to your platform
- Freelance developers – simple API, no infrastructure to maintain
- AI agents – native MCP support for Claude and other LLMs
The Micro SaaS approach means pay only for what you use, from 0 to 2,000+ credits per month.
How do you handle my invoice data?
We don't store it. Ever. thelawin.dev is truly stateless:
- Your invoice data is processed entirely in RAM
- PDF is generated and returned immediately as Base64
- Nothing is written to disk, no database storage
- Only usage counters (no content) are logged for billing
Billing via Paddle.com (Merchant of Record) handles EU VAT so we never touch payment data.
Which formats do you support?
9 EU-compliant formats from a single JSON input:
*ZUGFeRD 2.4 – Germany B2B
*Factur-X 1.0.8 – France
*XRechnung 3.0.2 – Germany B2G
*Peppol BIS 3.0 – EU cross-border
*FatturaPA – Italy SDI
*UBL 2.1 – OASIS standard
*CII – UN/CEFACT
*Plain PDF – non-EU regions
Use "format": "auto" and we'll pick the right one based on the country codes.
How easy is the integration?
One POST request. That's it.
- Test client built into this website – try before you code
- 8 official SDKs – TypeScript, Python, Ruby, Kotlin, Java, Swift, Dart, C#
- Install:
gem install thelawin(Ruby on RubyGems), all others via GitHub - OpenTelemetry support for monitoring and tracing
- MCP server for AI agent integration
- Discord – join the developer community for questions and support
Most people have it running within an hour.
Can I try it for free?
Yes, forever. The Sandbox plan is free for testing and integration.
- Full API access to all 9 formats
/validateis always free (no credits consumed)- Demo key for unlimited watermarked PDFs
- Buy credit packs (€4.90 / 100 credits) for production PDFs without watermark
- Or upgrade to Starter/Pro for monthly credits
Why "thelawin"?
"Lawin" is Scots for "the bill" or "the tab", as in "What's the lawin', lass?" It's our way of saying: asking for the bill should be as simple as an API call.
When does the e-invoicing mandate apply in Germany?
E-Rechnungspflicht timeline:
- Jan 2025: all German businesses must be able to receive e-invoices
- Jan 2027: large businesses must send e-invoices (B2B)
- Jan 2028: all businesses must send e-invoices
thelawin.dev supports both ZUGFeRD (B2B) and XRechnung (B2G), so you stay compliant either way.
Is thelawin.dev KoSIT compliant?
Yes. Every XRechnung invoice generated by thelawin.dev is validated against the official KoSIT Schematron rules (Koordinierungsstelle für IT-Standards).
That's the check German government portals like ZRE (Zentrale Rechnungseingangsplattform) and OZG-RE run on submitted invoices, so a KoSIT pass here usually means acceptance there.
Does thelawin.dev support Chorus Pro (France)?
Yes. We generate Factur-X 1.0.8 invoices that are fully compatible with the French B2G portal Chorus Pro.
Heads-up: France introduces mandatory e-invoicing (facturation électronique) in September 2026 for large enterprises, with full B2B coverage by 2027.
thelawin.dev generates PDF/A-3 with embedded CII XML, meeting all Factur-X EN 16931 profile requirements.
Can I create FatturaPA invoices for Italy?
Yes. thelawin.dev supports FatturaPA 1.2.2 with all the required fields for submission to the SDI (Sistema di Interscambio).
We handle the Italian-specific requirements:
- Codice Destinatario – 7-character recipient code
- Codice Fiscale – Italian tax ID
- Partita IVA – VAT number formatting
- PEC – certified email address
Start Building for Free
Sign up, grab a sandbox key, validate for free. Buy credits when you're ready.