06 / EU B2B E-INVOICING / PEPPOL
MYFILETRACKER
ROLELead EngineerTYPEDirect ContractYEAR2025
INVOICE
→VALIDATE
→DOCUMENT
→PEPPOL
→DELIVERY
01 / CONTEXT
A prototype taken into a Peppol-compliant B2B invoicing platform with structured document validation, auditable state transitions and organisation-level isolation.
The client arrived with a prototype that had never been tested against a real document. The production system had to accept invoices, validate them against the Peppol standard and preserve a traceable history of every state change.
02 / THE HARD PART
Compliance software has almost no tolerance for being nearly correct. Validation therefore had to become part of the product's core data flow rather than an edge check performed after a document had already moved through the system.
03 / WHAT SHIPPED
Structured invoice parsing
Peppol-oriented validation
Per-document status history
Audit-friendly state transitions
Organisation-level data isolation
Firebase-backed document storage and authentication
04 / STACK
Next.jsReactTypeScriptNode.jsFirebase
NEXT / 07