Stop Invoice Rejections Before They Leave Your ERP

A controlled compliance safety layer for EU e-invoicing pipelines.

Built for ERP vendors and integrators shipping cross-border invoices.

Validate. Safely remediate. Revalidate via KoSIT. Generate audit evidence. Automatically.

Safe remediation policy: amounts, VAT totals and IBANs are blocked by design.

Every remediation is logged. Every invoice is revalidated before release.

1,300+

Validation Rules

2026.02

Rule Set Version

Feb 2026

Last Updated

99.9%

Uptime

Validation is not the problem. Pipeline drift is.

Invoice validation fails in production — not in documentation.

Real pipelines break because:

  • ERP template drift across customers
  • CIUS fragmentation per country
  • Strict validator rejections on structural edge cases
  • Missing business data requires controlled input
  • Rejections create payment delays and support tickets

Validation tools show errors.

They don't stabilize pipelines.

Built for Teams Shipping Invoice Pipelines

ERP Vendors

Your export templates work until they don't. When a customer's invoices start getting rejected in production, the support tickets land on your desk. Invoice Navigator catches structural drift before submission — across all your customers, all their countries.

REST API, no SDK required

Integrators

Mandate go-lives are deadline-driven and country-specific. Your pipeline needs to validate against the right CIUS, remediate what's safe, and flag what's missing — without you maintaining rule sets per jurisdiction.

Sandbox available for integration testing

Accounting Firms

Multi-client invoice batches from different ERPs, different formats, different countries. One API call validates and remediates the batch. Evidence packs per invoice for audit.

Bulk upload endpoint available

Designed for pipelines. Not manual uploads. Typical setup time: less than one sprint.

A Compliance Gate Between Your ERP and Delivery

Invoice Navigator sits between your exporter and submission.

ERP ExportInvoice NavigatorCompliant InvoiceDelivery
  • Classifies validation findings
  • Safely remediates structural compliance issues
  • Requires explicit input for business-critical data
  • Blocks financial fields from modification
  • Revalidates before release
  • Generates a structured evidence pack

Designed for Safety, Not Convenience

01

Safe Auto-Remediation

Structural corrections where commercial meaning is unchanged. Namespace repair, encoding fixes, disallowed element removal.

02

Input-Required Workflow

Missing business data triggers explicit input — never assumptions. Missing buyer endpoint ID, missing payment means code.

03

Financial Field Blocking

Amounts, VAT totals, IBANs are never modified. Hardcoded, not configurable.

04

Revalidation Loop

Every remediated invoice is validated again before being released downstream. Via KoSIT, the official German validation framework.

Every action is logged.

Every invoice receives a structured evidence pack.

No guessing.
No silent mutations.
No financial edits.
Just controlled remediation and proof.

This is compliance infrastructure — not formatting.

What It Replaces

Hiring a compliance engineer to maintain rule sets and fix edge cases typically costs €60–80K/year in most EU markets. A part-time contractor runs €2–3K/month.

The Pro plan handles it at €499/month. For your entire pipeline.

See the Safety Layer in Action

Three scenarios. User-triggered. Every state transition is explicit.

Compliance Engine
1
<Invoice xmlns="urn:oasis:names:...ubl:2">
2
<CustomizationID>urn:cen.eu:en16931:2017</CustomizationID>
3
<ProfileID>urn:fdc:peppol.eu:2017:poacc:billing:01:1.0</ProfileID>
4
<ID>INV-2026-0847</ID>
5
<IssueDate>2026-02-19</IssueDate>
6
<InvoiceTypeCode>380</InvoiceTypeCode>
7
<Note>Project delivery Q1</Note>
8
<MandateTypeCode>B2B</MandateTypeCode>UBL-CR-435
9
<AccountingSupplierParty>
10
<Party>
11
<EndpointID schemeID="0088">4398823</EndpointID>
12
<PartyName>
13
<Name>Müller GmbH</Name>
14
<PayableAmount currencyID="EUR">12,450.00</PayableAmount>
15
<TaxAmount currencyID="EUR">2,365.50</TaxAmount>

Findings

UBL-CR-435FATALAUTO-FIX

UBL 2.1 Cross-Industry

Disallowed element MandateTypeCode

Validation: FAILED1 issue found

Best experienced on desktop for the full interactive console.

Scenario

What Happens in Production

An ERP vendor exports 3,000 invoices per month across DE, BE, NL, and FR.

Their export templates work for most invoices. The rest fail: missing CustomizationID after a template update, decimal precision mismatches on French invoices, disallowed elements left over from an old Peppol profile.

Without a compliance gate, those invoices get rejected at the access point. Each rejection creates a support ticket, a payment delay, and an unhappy customer.

With Invoice Navigator in the pipeline:

  • Most are auto-remediated (structural fixes, no financial data touched)
  • Some trigger input-required workflows (missing buyer endpoints, payment means)
  • A handful are blocked (financial field discrepancies that need human review)
  • Every invoice gets an evidence pack for audit

The rejection rate typically drops from double digits to under 2%. No new hires. No compliance contractors. One API endpoint.

One Endpoint. Full Pipeline.

POST /v2/validate-and-fix

RequestJSON
1{
2 "xml": "<?xml version=\"1.0\"...>",
3 "fileName": "INV-2026-0847.xml",
4 "remediation_policy": "safe",
5 "generate_evidence_pack": true
6}
ResponseJSON
1{
2 "validationRef": "val_8f2a3b",
3 "originalValid": false,
4 "fixedValid": true,
5 "engine": "hybrid",
6 "fixesApplied": 1,
7 "fixSummary": { "autoFixable": 1, "needsInput": 0, "blocked": 0 },
8 "evidencePackUrl": "/api/v1/evidence-pack/ep_...",
9 "_links": { "self": "/api/v2/validate-and-fix" }
10}

No hidden transformations. No silent rewrites.

View API Documentation

Not a Validator

What validators do

What Invoice Navigator does

Show you a list of errors

Classify, remediate, revalidate, and prove compliance

Stop at "invalid"

Fix what's safe, ask for what's missing, block what's financial

Return a report

Return a remediated invoice + structured evidence pack

Run manually or via CLI

Run in your pipeline via a single REST endpoint

See the full breakdown on the comparison page

Priced for Production Pipelines

Starter

249/mo

Up to 1,000 invoices/mo

1,000 invoices/mo · 30-day retention · Email support

Most Popular

Pro

499/mo

Up to 5,000 invoices/mo

5,000 invoices/mo · Batch processing · 90-day retention · Rule alerts

Scale

999/mo

Up to 25,000 invoices/mo

25,000 invoices/mo · 1-year retention · Dedicated support · SLA targets

Rule Version TrackingEvidence Pack Per InvoiceFinancial Field Protection
  • Versioned rule sets with update tracking
  • Revalidation via KoSIT for German CIUS; equivalent validation for other jurisdictions
  • Structured evidence pack per invoice
  • Clear remediation boundaries
  • Public status page

Start with 100 free invoices — full engine access, no credit card.
Integrates with your pipeline in under one sprint.

Ready to Harden Your Pipeline?

Deploy the Safety Layer and stop rejections before they reach your customers or platforms.