Universal EU e-Invoicing, ViDA & Peppol BIS 3.0
Deterministic EU e-Invoicing Validator, German XRechnung, Italian SDI & ViDA DRR Engine
This vertical exposes a dedicated Model Context Protocol (MCP) Streamable HTTP endpoint featuring 4 mathematically deterministic compliance tools. Specifically engineered for autonomous AI agents, enterprise ERPs, and compliance pipelines to ensure exact statutory verification without probabilistic hallucination.
Quick AI Agent Setup (Cursor / Claude Desktop / n8n)
https://peppol-mcp.novapixel.it/{
"mcpServers": {
"lexgrid-einvoice-vida": {
"url": "https://peppol-mcp.novapixel.it/"
}
}
}
{
"mcpServers": {
"lexgrid-einvoice-vida": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://peppol-mcp.novapixel.it/"]
}
}
}
01. Statutory Architecture & Mathematical Precision
Cross-border European B2B trade is transitioning to mandatory electronic invoicing governed by the EU ViDA (VAT in the Digital Age) Directive, CEN/EN 16931 semantic standards, and Peppol BIS Billing 3.0. In addition, national implementations such as German XRechnung 3.0 / ZUGFeRD 2.2 and Italian SDI FatturaPA impose rigid syntax, routing, and tax calculations. LexGrid provides deterministic mathematical and schema validation without LLM hallucination.
Unlike probabilistic LLM inference which may hallucinate tax percentages, distort statutory thresholds, or produce subtle rounding discrepancies, this engine isolates all math, validation logic, and regulatory constraints into pure, auditable TypeScript routines operating with exact precision (via decimal.js and official XSD/XML schemas).
02. Included Deterministic Tools
universal_peppol_bis3_validator
CEN/EN 16931 & Peppol BIS Billing 3.0Universal CEN/EN 16931 semantic data model and OpenPeppol UBL 2.1 Schematron rules validator with decimal.js tax recalculation.
Statutory Anchor: CEN/EN 16931 & Peppol BIS Billing 3.0
xrechnung_zugferd_cross_compiler
KoSIT XRechnung 3.0 & WachstumschancengesetzCompiles and validates German XRechnung 3.0 and hybrid PDF/A-3 ZUGFeRD 2.2 e-invoices, verifying Leitweg-ID codes and German B2B mandates.
Statutory Anchor: KoSIT XRechnung 3.0 & Wachstumschancengesetz
vida_cross_border_digital_reporter
Riforma ViDA & Artt. 218-222 Dir. 2006/112/CEAudits cross-border B2B intra-community transactions under the EU VAT in the Digital Age (ViDA) Directive, verifying the 2-day issuance window and MTIC fraud risk.
Statutory Anchor: Riforma ViDA & Artt. 218-222 Dir. 2006/112/CE
fatturapa_sdi_sanitizer
Specifiche Tecniche SDI v1.2.2 & D.P.R. 633/72Validates and sanitizes Italian FatturaPA XML payloads (FPR12 B2B / FPA12 PA), verifying 7-char SDI recipient codes, Natura IVA codes, Split Payment deductions, and stamp duty.
Statutory Anchor: Specifiche Tecniche SDI v1.2.2 & D.P.R. 633/72
vat_triangulation_audit
Art. 141 Dir. 2006/112/CE & Art. 40 D.L. 331/93Audits simplified triangular trade transactions under Article 141 of Council Directive 2006/112/EC, generating mandatory invoice notations and verifying Intrastat obligations.
Statutory Anchor: Art. 141 Dir. 2006/112/CE & Art. 40 D.L. 331/93
03. Enterprise & AI Agent Workflows
Universal Peppol BIS 3.0 Pre-Flight Validation
Validates invoice payloads against CEN/EN 16931 rules and OpenPeppol UBL 2.1 Schematron rules, computing decimal tax subtotals and payable amounts before transmission to Peppol Access Points.
German B2G & B2B Mandate Cross-Compilation
Compiles and verifies XRechnung 3.0 and hybrid PDF/A-3 ZUGFeRD 2.2 profiles, checking mandatory Leitweg-ID codes and German Wachstumschancengesetz mandates.
ViDA Real-Time Digital Reporting & Triangular VAT
Audits compliance with the 2-business-day issuance window under ViDA Digital Reporting Requirements (DRR) and verifies Article 141 triangular transaction reverse-charge clauses.
04. Live Payload Specification (Tool: universal_peppol_bis3_validator)
JSON-RPC / REST 200 OK
{
"invoiceNumber": "INV-2025-001",
"issueDateIso": "2025-03-15",
"senderVatId": "IT01234567890",
"senderEndpointId": "0201:IT01234567890",
"receiverVatId": "DE123456789",
"receiverEndpointId": "0201:DE123456789",
"buyerReferenceOrOrderNumber": "PO-998877",
"invoiceLines": [
{
"lineNumber": 1,
"itemName": "Cloud Consulting Services",
"quantity": 10,
"unitPriceEur": 150,
"vatRatePercent": 0
}
]
}
{
"status": "success",
"deterministic_execution": true,
"suite": "einvoice-vida",
"tool": "universal_peppol_bis3_validator",
"data": {
"invoiceNumber": "INV-2025-001",
"isCenEn16931Compliant": true,
"isPeppolBis3Compliant": true,
"validationStatus": "PASSED",
"financialTotals": {
"lineExtensionAmountTotalEur": 1500,
"payableAmountEur": 1500
}
}
}
05. Regulatory Framework & Statutory Basis
All algorithms operate under official formulas enacted by statutory regulations, without approximations or probabilistic inferences:
- ⚖️ Proposta di Direttiva ViDA (VAT in the Digital Age) & Accordo ECOFIN
- ⚖️ Direttiva 2014/55/UE sulla fatturazione elettronica negli appalti pubblici
- ⚖️ Standard CEN/EN 16931 & OpenPeppol BIS Billing 3.0 (UBL 2.1)
- ⚖️ Specifiche Tecniche SDI FatturaPA v1.2.2 (Agenzia delle Entrate)
- ⚖️ Standard KoSIT XRechnung 3.0 & ZUGFeRD 2.2 / Factur-X (Germania)
- ⚖️ Art. 141 Direttiva 2006/112/CE (Triangolazioni comunitarie semplificate)
06. Frequently Asked Questions & Regulatory Details
What is the timeline for the EU ViDA (VAT in the Digital Age) e-invoicing mandate? ↓
Under the ECOFIN ViDA agreement, Member States can mandate domestic B2B e-invoicing immediately without prior Commission derogations. Real-Time Digital Reporting Requirements (DRR) for intra-Community supplies become mandatory across the EU by 2030.
How does LexGrid validate German Leitweg-ID routing codes? ↓
The engine verifies format compliance against KoSIT specifications (Grob-ID, Fein-ID, and Prüfziffer) ensuring invoices destined for German federal, state, and municipal authorities pass statutory acceptance gates.
What are the statutory requirements for triangular VAT transactions under Art. 141? ↓
The three parties must be registered for VAT in three distinct EU Member States, goods must be transported directly from Member State A to Member State C, and the intermediary invoice must include explicit statutory reverse-charge notation.