14+
Countries supported
48h
New country onboarding
100%
Regulatory coverage
1
Single integration point
The Multi-Country Challenge
Picture this: your enterprise runs SAP S/4HANA or Oracle NetSuite across 14 countries. Finance teams in Munich, Madrid, and Riyadh all process invoices through the same ERP instance. But here's the problem — every single country has a different e-invoicing mandate.
Germany requires XRechnung in UBL 2.1 format via Peppol. France is rolling out Factur-X through certified PDPs. Spain demands real-time reporting through Verifactu/SII. Italy has its own Sistema di Interscambio with FatturaPA XML. Saudi Arabia enforces ZATCA Phase 2 pre-clearance with cryptographic stamping. And that's just five of the fourteen.
14 separate connectors
One for each country's tax authority or network
14 different schemas
UBL, CII, FatturaPA, KSeF FA(2), ZATCA XML…
42+ format updates/year
Schema versions change 3× per year per country
€400K+ annual cost
Maintaining bespoke integrations per jurisdiction
The traditional approach? Build or buy a connector for each country. Hire local compliance consultants. Maintain 14 different XML schemas. Pray that when Poland updates KSeF from Phase 1 to Phase 2, someone on your team notices before the deadline. It's unsustainable, expensive, and risky.
Country Requirements Matrix
Every country in your ERP footprint has distinct requirements across five dimensions: invoice format, delivery network, clearance model, XML schema, and validation rules. Here's a snapshot of the complexity your finance team faces:
Germany — XRechnung
Germany mandates XRechnung for all B2G invoices, using UBL 2.1 delivered via Peppol. The Leitweg-ID routing scheme, unique to Germany, must be embedded in the invoice XML. Version 3.0 adds new business rules that reject invoices missing payment terms metadata.
France — Factur-X / PPF
France's Continuous Transaction Controls (CTC) mandate requires all B2B invoices to pass through certified Plateformes de Dématérialisation Partenaires (PDPs) by 2026. Factur-X combines a PDF/A-3 visual layer with embedded CII XML — a hybrid format no other country uses.
Spain — Verifactu / SII
Spain's Suministro Inmediato de Información (SII) requires real-time invoice reporting within 4 days. The upcoming Verifactu system adds anti-fraud controls with chained hash sequences — each invoice cryptographically references the previous one.
Italy — SdI / FatturaPA
Italy pioneered mandatory B2B e-invoicing in the EU. Every invoice must be cleared by the Sistema di Interscambio before it reaches the buyer. FatturaPA 1.2 schema is unique to Italy — not UBL, not CII — with 400+ validation rules.
Saudi Arabia — ZATCA Phase 2
ZATCA Phase 2 (Integration Phase) requires real-time clearance with cryptographic stamping. Every invoice gets a UUID, QR code with digital signature, and XML must conform to UBL 2.1 with ZATCA-specific extensions. Non-compliance blocks the invoice entirely.
Poland — KSeF
Poland's Krajowy System e-Faktur (KSeF) is a centralized government platform. All B2B invoices must be submitted and receive a KSeF reference number before they're legally valid. The FA(2) schema is Poland-specific with mandatory structured line items.
UAE — FTA E-Invoicing
The UAE Federal Tax Authority is implementing mandatory e-invoicing with Peppol as the underlying framework. Invoices must include TRN (Tax Registration Number) validation and comply with UAE-specific business rules layered on top of Peppol BIS 3.0.
Add Romania (eFactura via SPV), Belgium (Peppol B2B mandate from 2026), Portugal (CIUS-PT on top of Peppol), Netherlands (SI-UBL 2.0), Greece (myDATA real-time reporting), Sweden (Peppol BIS Billing 3.0), and Norway (EHF format) — and you have 14 completely different compliance landscapes that your single ERP must navigate.
InvoStaq's Unified Approach
Instead of building 14 separate integrations, InvoStaq provides a single API endpoint that normalizes every country's requirements behind one consistent interface. Your ERP sends one standardized payload — InvoStaq handles the rest.
Format Normalization
Send UBL, CII, or even flat JSON. InvoStaq converts to whichever format each country demands — XRechnung, Factur-X, FatturaPA, ZATCA XML, KSeF FA(2), or Peppol BIS.
Schema Mapping Engine
Every country has unique required fields. InvoStaq's mapping engine automatically enriches your invoice data with country-specific metadata — Leitweg-IDs for Germany, CUF codes for Spain, UUID stamps for Saudi.
Network Routing
InvoStaq routes each invoice to the correct network automatically. Peppol for Germany and Belgium, SdI for Italy, KSeF for Poland, FATOORA for Saudi, PPF for France — zero manual configuration.
Clearance Orchestration
Pre-clearance countries (Italy, Saudi, Poland) require submission before the buyer sees the invoice. Post-audit countries (Germany, Belgium) allow direct delivery. InvoStaq handles both models transparently.
Validation Rules Engine
Each country has hundreds of validation rules. InvoStaq maintains 2,800+ rules across all 14 jurisdictions, updated automatically when tax authorities publish new requirements.
Crypto & Signing
ZATCA requires digital signatures and QR codes. Italy requires SdI-issued identifiers. Spain's Verifactu uses hash chains. InvoStaq handles all cryptographic requirements per country.
POST /api/v1/invoices/submit
Authorization: Bearer YOUR_API_KEY
Content-Type: application/json
{
"invoice": "<base64-encoded-ubl-xml>",
"source_country": "DE",
"destination_country": "IT",
"format": "auto-detect",
"routing": "automatic"
}
// InvoStaq automatically:
// 1. Detects the source format (UBL 2.1)
// 2. Validates against German XRechnung rules
// 3. Converts to Italian FatturaPA 1.2 schema
// 4. Submits to SdI for pre-clearance
// 5. Returns clearance status + SdI identifier
// Response
{
"status": "cleared",
"country": "IT",
"format_used": "FatturaPA_1.2",
"network": "SdI",
"clearance_id": "IT01-2026-0000142857",
"processing_time": "1.2s",
"validations_passed": 412
}The beauty of this approach is that your ERP team writes one integration — a single REST API call. InvoStaq's compliance engine determines the correct format, schema, network, and clearance model based on the invoice's jurisdiction. When Belgium activates its Peppol B2B mandate or France transitions to mandatory CTC, your integration doesn't change. InvoStaq updates its rules engine, and your invoices keep flowing.
Implementation Strategy
Rolling out multi-country compliance doesn't require a big-bang migration. InvoStaq's phased approach lets you go live country-by-country while maintaining a single integration architecture:
We audit your ERP's invoice data structure and map every field to the target country schemas. This reveals gaps — missing Leitweg-IDs for Germany, missing TRN fields for UAE, missing CUF sequences for Spain. We generate a field-mapping matrix for all 14 countries.
InvoStaq's rules engine is configured with your specific business context — your VAT registration numbers per country, your Peppol participant IDs, your ZATCA Organization Unit identifier, your Italian codice destinatario. Each country's validation profile is tailored to your entity structure.
Your ERP team implements one API connector to InvoStaq. Whether it's an SAP RFC/BAPI call, an Oracle Integration Cloud flow, or a direct REST endpoint — you build it once. We provide SDKs for ABAP (SAP), PL/SQL (Oracle), C# (Dynamics), and Python (Odoo).
Every country has a test environment. We run your actual invoice data through InvoStaq's sandbox, covering all 14 jurisdictions. You see exactly how each invoice transforms, validates, and routes — before a single live invoice is sent.
We activate countries in waves — typically starting with Peppol markets (Germany, Belgium, Netherlands) in wave one, then SdI/KSeF markets (Italy, Poland) in wave two, then ZATCA markets (Saudi, UAE) in wave three. Full dashboard monitoring with per-country compliance metrics from day one.
Once your single API integration is live, adding a new country takes 48 hours — not months. When your business expands to Greece, Norway, or Portugal, InvoStaq activates the country's compliance profile on your account. No new code, no new connectors, no new schemas to manage. Your existing API call handles it automatically.
Future-Proofing Your Compliance
Tax mandates don't stand still. The EU ViDA directive will harmonize cross-border e-invoicing across all member states by 2030. France's CTC mandate expands to all businesses by 2027. Poland's KSeF delayed but confirmed mandatory. New countries — Turkey, India, Malaysia — are announcing mandates every quarter. If you built 14 individual integrations, every one of these changes is a new project.
Auto-Updated Rules
When Germany publishes XRechnung 4.0 or ZATCA adds new validation fields, InvoStaq updates its rules engine automatically. Your integration stays the same — zero code changes on your side.
New Mandate Coverage
InvoStaq's compliance team monitors every tax authority in real-time. New mandates are supported before their enforcement date. You get email alerts and dashboard notifications for upcoming changes.
ViDA-Ready Architecture
The EU's VAT in the Digital Age directive will require real-time digital reporting across all member states. InvoStaq's architecture is already built for this — the transition will be seamless for existing customers.
The difference between managing compliance reactively and proactively is the difference between scrambling before every deadline and knowing that your system is already compliant. InvoStaq transforms multi-country e-invoicing from a recurring crisis into a solved problem.
Your CFO shouldn't be worrying about XML schema versions. Your IT team shouldn't be maintaining 14 separate connectors. Your compliance officers shouldn't be manually tracking mandate deadlines across a dozen jurisdictions. InvoStaq consolidates all of this into a single, managed service that scales with your business — whether you operate in 14 countries today or 40 tomorrow.
One Integration, Every Country
Stop building per-country connectors. InvoStaq gives you a single API that covers 14+ jurisdictions with 100% regulatory compliance — and adds new countries in 48 hours.