01
PDF
PDF workflows stop being enough
Customers increasingly expect structured invoice data, business references, validation results, and machine-readable status.
Germany-first XRechnung workflow for billing platforms
Keep your billing system. Add compliant invoice workflows.
Send the invoice JSON you already produce. InvoiceBridge validates Germany XRechnung requirements, generates structured UBL XML, runs official validation when configured, and keeps invoice-level status and audit evidence without forcing a billing rebuild.
XRechnung UBL export
Official validator evidence
Audit trail by invoice
No ERP migration
customer_invoice.json
validation passed
POST /v1/invoices/transform -> existing invoice JSON received -> Germany profile selected -> VAT IDs, totals, and buyer reference checked -> XRechnung UBL generated -> status and audit evidence stored RESULT workflow_ready document_url /v1/invoices/inv_123/document document_sha256 9b1f...e7c4 POST /v1/invoices/inv_123/official-validate RESULT validator_passed AUDIT invoice_received validation_passed transformed official_validation_passed
The problem
Germany e-invoicing is becoming billing product work.
The hard part is not creating another invoice. It is proving the invoice data is valid, generating the right structured file, and showing finance what happened after the invoice left billing.
02
PAY
Rejected invoices slow cash collection
Bad VAT IDs, missing buyer references, wrong tax totals, and unsupported formats become payment delays and support tickets.
03
EU
Germany is the first workflow to prove
Start with XRechnung validation and evidence, then reuse the same API boundary for other country workflows later.
The solution
One API between your invoice JSON and XRechnung evidence.
Send existing invoice JSON from your ERP, accounting system, billing platform, or marketplace. InvoiceBridge validates the Germany workflow, generates XRechnung UBL, records validator evidence, and keeps status and audit history around it.
01
API
Connect the invoice data you already produce
Keep the ERP, accounting system, billing platform, or marketplace workflow your customers already use.
02
CHK
Catch mandate-specific issues before send
Validate VAT IDs, buyer reference, invoice totals, tax totals, currency, and Germany profile requirements before they hit a customer.
03
LOG
Give finance an answer when they ask
Track each invoice from received to validated, transformed, validator-checked, submitted or recorded, with status and audit evidence attached.
Country workflows
Start with Germany. Keep the country model extensible.
The first credible paid workflow is Germany XRechnung validation and evidence. Other country cards show how the same API boundary expands without turning the billing system into a compliance rewrite.
Usable only when official validation passes
Germany EN 16931 e-invoices
The pain
Germany creates receiving-readiness and mixed-format pressure. Sellers need to know whether an invoice is actually structured and valid, not merely a PDF attachment.
What InvoiceBridge gives you
InvoiceBridge turns existing invoice JSON into XRechnung 3.0 UBL, supports local KoSIT validation, records customer-managed delivery status, and keeps audit evidence for each invoice.
- Mandate check endpoint for Germany B2B
- German VAT ID checksum and VAT-rate validation
- XRechnung 3.0 UBL transformation
- Official validator result storage and audit trail
Snapshot as of May 19, 2026. Country rules need legal review before production. Germany is usable only when official XRechnung validation passes. Legal production support for Belgium, Poland, Romania, and Spain is coming soon. France and Italy are roadmap cards only.
Business outcomes
Built for teams that cannot afford country-by-country rewrites.
01
ERP and accounting SaaS
Add country-specific e-invoicing workflows without forcing customers to abandon the billing screens and invoice data model they already use.
02
Billing platforms
Catch bad totals, VAT IDs, routing fields, and missing mandate data before they become failed sends, customer tickets, or delayed payments.
03
B2B marketplaces
Give sellers one integration path while you prepare country workflows behind the scenes for buyers, authorities, and network requirements.
04
Cross-border finance teams
Answer what happened to an invoice with status, transformed document links, provider references, and chronological audit events.
05
Product and engineering leaders
Centralize mandate checks, validation, transformation, and evidence instead of scattering country logic through billing code.
06
Compliance and support teams
Separate what is usable now, what is coming soon, and what requires official validation so customer conversations stay clear.
07
Infrastructure owners
Use idempotency, request IDs, API-key access, regional metadata, and audit persistence to make invoice workflows operable.
08
Future provider integrations
Keep the same API contract while access-point, government-platform, signing, and webhook integrations are added behind provider boundaries.
Infrastructure
Credible under the hood, simple at the edge.
The sales promise is simple: send invoice JSON and get a compliance workflow back. The implementation still has the platform basics technical buyers expect: API contracts, persistence, idempotency, audit events, OpenAPI docs, and multi-region metadata.
DATA MODEL
Invoice
InvoiceSubmission
ValidationResult
AuditEvent
CountryProfile
MULTI-REGION CONTRACT
GET /health/ready
GET /v1/regions
GET /v1/tenants/{id}/region-decision
X-Deployment-Region
tenant_id + processing_region on records
SECURITY NOTES
X-API-Key required on /v1
VAT IDs masked in logs
Payload size checks
No secrets in code
Pricing
Pay for the workflow, not a billing-system rebuild.
Start by proving the Germany workflow locally. Move into a paid pilot when you want help mapping real invoice payloads, storing validation evidence, and preparing a production rollout. Pilot access is manual while hosted billing and usage metering are coming soon.
Evaluate
$0 /month
For teams proving the workflow with real invoice examples.
- Local/demo use
- Germany sample workflow
- Validation, transform, official-validator hook
- Status and audit trail
- OpenAPI docs
First paid offer
Germany Pilot
$1.5k+ /month
For teams validating real Germany invoice payloads before a production rollout.
- Germany XRechnung workflow support
- Real invoice payload mapping review
- Official validator evidence retention
- Tenant API key, audit trail, and document hashes
- Implementation support
Platform
Custom
For ERP, marketplace, and multi-country platforms that need custom rollout planning.
- Custom volume
- Provider integration planning
- Additional country profiles
- Security review
- SLA planning
Compare
Plan details, side by side.
| Feature | Evaluate | Germany Pilot | Platform |
|---|---|---|---|
| Monthly invoice workflows | Demo/local | Pilot-scoped | Custom |
| Germany XRechnung workflow | Validation-gated | Validation-gated with support | Custom review |
| Official validator result storage | Yes | Yes | Yes |
| Belgium, Poland, Romania, Spain | Coming soon | Roadmap planning | Custom official work |
| Structured transforms | Yes | Yes | Yes |
| Mock provider outcomes | Yes | Yes | Yes |
| Tenant-scoped API keys | Yes | Yes | Custom account model |
| Audit trail | Yes | Yes | Yes |
| Archive/redact invoice data | Yes | Yes | Policy-based retention |
| Webhook delivery | No | Planned | Custom |
| Real provider integrations | No | Planned after pilot | Custom integration |
| Support | Docs | Implementation support | Custom |
FAQ
Common questions.
Is this production-certified?
No. Germany is usable only after official XRechnung validation passes for the generated document. Legal production support for the other implemented countries is coming soon.
Who is this for?
ERP systems, accounting SaaS, billing platforms, and B2B marketplaces that already produce invoice data and need a Germany-first compliance workflow layer.
Why not just generate PDFs?
PDFs do not solve routing, buyer identifiers, country-specific validation, structured exchange, status tracking, or audit evidence.
Can customers keep their current system?
Yes. The product is designed to sit between existing invoice JSON and country workflows, so billing teams do not have to start with a replacement project.
Does this store invoice data?
Yes. The API stores invoice payloads, transformed XML, validation results, and audit events. Tenant API keys scope access, and invoices can be archived with payload/XML redaction while preserving audit hashes.
What makes this different from a script?
The value is the repeatable workflow around validation, idempotency, status, document hashes, and audit evidence, not just XML generation.
Prove the Germany workflow before rebuilding billing.
Use your existing invoice JSON to validate XRechnung requirements, produce structured XML, run official validation, and keep audit evidence.