E-invoicing compliance platform

The situation

An incoming national e-invoicing reform meant every business above a certain size would soon be required to exchange invoices through approved platforms, in structured, machine-readable formats rather than PDFs. That requirement doesn't just change a file type — it changes what "correct" means for an invoice, down to which fields are mandatory and how they're encoded.

The product needed backend services that could generate, validate, and transmit invoices in the formats the reform actually requires — Factur-X and UBL — and do it reliably enough to sit inside another company's compliance obligations.

The approach

The work centered on a Spring Boot backend that treats format compliance as a first-class concern rather than an afterthought: structured invoice data validated against the Factur-X and UBL schemas before it ever reaches the approved-platform integration layer, with clear REST endpoints for the rest of the product to build against.

Because the reform's requirements were still being finalized while the platform was being built, the services were designed to be adjusted as the specification firmed up — versioned formats and validation rules, not logic hard-wired to a single moment-in-time reading of the standard.

The outcome

A backend that generates and validates compliant e-invoices ahead of the reform taking effect, built so the product team could keep shipping the rest of the platform without becoming compliance specialists themselves.