Skip to main content
Regulatory compliance

E-invoicing without rebuilding your software

EN 16931, Peppol, Facturae, Verifactu. We adapt the system you already use so it can issue, receive and archive legally valid electronic invoices, integrated with your ERP and with full traceability for every document.

Mandatory e-invoicing is not about emailing a PDF: it requires issuing a structured document — UBL or CII under the European EN 16931 standard, Facturae in Spain — signed or registered so its integrity can be proven, transmitted through an accepted channel and retained for the period the regulation sets. Several pieces coexist. Across Europe, the Peppol network and the ViDA package push towards cross-border digital reporting; in Spain, the Verifactu system and the requirements on invoicing software sit alongside the extension of e-invoicing to business-to-business transactions; and in transport, the electronic consignment note (e-CMR) follows the same path of mandatory document digitisation. Application deadlines have been postponed more than once, so it is worth confirming the current calendar for your case before planning. What does not change is the underlying technical work, and that is where we come in: adapting the software you already run — your ERP, your e-commerce or your management application — so it generates, validates, transmits and archives the right documents without forcing your team onto a different tool.

What we do

Technical adaptation to compliance

We work on your current system. The goal is to comply without breaking the processes that already work.

Structured issuing

Invoice generation in UBL, CII or Facturae conforming to EN 16931, with syntactic and semantic validation done before sending rather than after a rejection comes back.

Registry and integrity

Invoicing records with chained entries, digital fingerprint and electronic signature, so that any later alteration is detectable and demonstrable in an audit.

Transmission and channels

Delivery through the channels accepted for each recipient: the Peppol network for European transactions, public sector platforms and direct business-to-business exchange.

Reception and matching

Automatic capture of incoming invoices, format validation, data extraction and matching against purchase orders and delivery notes so approval stops being manual.

Archiving and traceability

Retention with integrity guarantees for the required period, searchable by any field and with an auditable log of who did what to each document and when.

ERP integration

Connectors for Oracle, SAP, Dynamics 365, Odoo, Holded or A3ERP, and for custom builds. E-invoicing leans on your master data instead of duplicating it.

Regulatory framework

The pieces that have to fit together

A technical map, not tax advice. Deadlines have shifted several times: always confirm the current calendar with your advisor before planning the project.

EN 16931 and Peppol

The European semantic standard and the exchange network that carries it. This is where cross-border interoperability is decided and where the ViDA package is pushing.

Verifactu and invoicing systems

Spanish requirements on invoice-issuing software: chained, unalterable records, digital fingerprint, event logging and, under Verifactu, submission of records to the tax authority.

B2B e-invoicing

The extension of electronic invoicing to transactions between companies and professionals, including the obligation to report the payment status of each invoice received.

e-CMR and transport documents

The electronic consignment note and the European framework for electronic freight transport information: the same principles of integrity, traceability and interoperability applied to logistics.

Is your current software ready?

Free consultation →
Process

From audit to compliance

Situation audit

We review how invoices are issued today, with which systems, in what formats and what gets retained. The output is a concrete list of technical gaps against what is required.

01

Adaptation design

We decide what is solved inside the current system, what needs a new layer and what is better delegated to a certified provider, with an estimate and risks per option.

02

Development and validation

Implementation tested against real cases: credit notes, corrections, intra-community transactions, exemptions and every scenario that tends to break validation.

03

Rollout and support

Go-live with a parallel-running period, training for the finance team and ongoing maintenance as formats and deadlines change.

04
Formats and technologies

What we work with

EN 16931UBL 2.1UN/CEFACT CIIPeppol BISFacturaeVerifactuFACeXAdESe-CMRREST APIXML SchemaNode.jsPythonPostgreSQLOracleSAPOdooHolded
FAQ

Frequently asked questions

Do I have to change ERP to comply?
Almost never. In most cases it is enough to adapt the invoicing module or add a layer that generates, registers and transmits the documents from the data your ERP already holds. Replacing a system because of a regulatory obligation is usually the most expensive and riskiest option; it only makes sense if the current software was already at the end of its life for other reasons.
Are you tax advisors?
No. We are the technical team that implements. The interpretation of the rules and the calendar that applies to you are set by your tax advisor, and we work with them: they hand us the requirements and we make sure the software meets them and can prove it. Nothing published here is tax or legal advice.
What if we operate in several countries?
That is the most common scenario in mid-sized and large companies, and also the trickiest: each country has its own format, platform and calendar. We design the solution with a common core based on EN 16931 and per-country adapters, so adding a new market means configuring an adapter rather than rebuilding the system.
How long does an adaptation project take?
A scoped adaptation on a tidy system usually takes six to twelve weeks from audit to production. Projects spanning several legal entities, several countries or a heavily customised ERP run to several months. The standing recommendation: start with the audit early, because what stretches these projects is almost never the development but discovering the unusual invoicing cases too late.
Let's start

Find out what you are missing

Tell us which system you invoice with today and which countries you operate in. We come back with the list of technical gaps and an effort estimate.

E-Invoicing and Compliance Software

Tell us your challenge. We'll propose a solution.

No commitment. Within 24 hours, you'll receive a proposal with scope, timeline and budget. No fine print.

Book a free call →