EN
Language
Bring your case
Bring your case

Official deadlines checked 06.10.2026

Your ERP.Your invoices.Our integration.

E-⁠invoicing for businesses that run an ERP, and for the ERP partners who serve them. One source system and one country route: EUR 3,600 direct, or EUR 3,000 through an ERP partner. We target the first valid test invoice within two working days after the technical readiness package is complete.

Bring us one caseSee the standard scope
  • Rail-neutral delivery
  • Direct, or through your ERP partner
R
ANAF · validation service27.09.2026 · stare: ok
R
Peppol · access point27.09.2026 · Sent
R
Registered · KSeF 2.0Test environment
KSeF number7443889269-20260926-9AC1F4000000-9D
Route
KSeF 2.0 (test)
Format
FA(3)
Posted
26.09.2026
Receipt
UPO received

Receipts from official test environments, 26 and 27 September 2026. Sample data, fictitious companies.

Scroll for more

Routes we have tested in official test environments

On request, not tested yet: Croatia, Greece, Italy and Slovakia

Countries

Where the rules apply, and how invoices travel.

The rules cover VAT-registered businesses in every industry. Where there is a phase-in, it goes by company size or turnover.

We integrate through the appropriate certified Peppol access point, French approved platform or local provider, and may use a public government API where the country supports direct integration. The route is named in the scope.

  1. 01.01.2019
    ItalySee the Italy integration
    Domestic B2B invoices are transmitted through the national SdI system.SdI · FatturaPA
    In force
  2. 01.07.2024
    RomaniaSee the Romania integration
    Domestic B2B invoices are transmitted through the national RO e-⁠Factura system.RO e-⁠Factura · RO_CIUS
    In force
  3. 01.01.2026
    BelgiumSee the Belgium integration
    All VAT-registered businesses exchange structured invoices.Peppol · Peppol BIS 3.0
    In force
  4. 01.01.2026
    CroatiaSee the Croatia integration
    Domestic B2B invoices go through Fiskalizacija 2.0, with data reported to the tax authority.Fiskalizacija 2.0 · EN 16931
    In force
  5. 01.04.2026
    PolandSee the Poland integration
    Invoices clear through the national KSeF platform. Required for every business since 01.04.2026, except sales up to PLN 10,000 a month, which may stay outside until 31.12.2026.KSeF 2.0 · FA(3)
    In force
  6. 01.09.2026
    FranceSee the France integration
    Everyone receives now. Large and mid-size firms issue now, SMEs from 01.09.2027.Approved platforms · Factur-X, UBL, CII
    In force
  7. 02.03.2026
    GreeceSee the Greece integration
    Businesses above EUR 1 million revenue issue through myDATA providers since 02.03.2026. All others start on 02.11.2026, with a phase-in until 31.01.2027.myDATA · Provider schema
    In force
  8. 01.01.2027
    GermanySee the Germany integration
    Firms over EUR 800k turnover must issue. Everyone else from 01.01.2028.Agreed channel · XRechnung, ZUGFeRD
    Next
  9. 01.01.2027
    SlovakiaSee the Slovakia integration
    B2B e-⁠invoicing starts, with tax-data reporting.Providers + reporting · EN 16931
    Next
  10. 2028–2030
    Latvia, Slovenia, Ireland, EU (ViDA)
    Enacted or announced. EU-wide rules for cross-border B2B from 01.07.2030.EN 16931
    Later

Checked against official sources on 27.09.2026. Dates change. Ask us for the current position in your country.

All countries

E-⁠invoice flow

How an e-⁠invoice travels

Your ERP's invoice is converted, checked and sent over the country's network, and a receipt comes back. In Poland, KSeF must accept each invoice and give it a number.

  1. 01

    Your ERP

    Creates the invoice as it does today.

  2. 02

    Mapping

    Each field goes into the format the country requires.

    • EN 16931
    • FA(3)
    • XRechnung
    • Factur-X
    • CIUS-RO
  3. 03

    Validation

    The file is checked against the official rules before it is sent.

    • XSD
    • Schematron
  4. 04

    Sending

    It travels over the country's own route.

    • Peppol
    • KSeF 2.0
    • Plateformes Agréées
    • RO e-Factura
  5. 05

    Receipt

    Status, ID and any rejection come back to your system.

Common problems

Most e-⁠invoicing projects fail after the software is switched on.

The network is the easy part. The trouble sits between your ERP and the network, and it keeps coming back every month.

Your ERP export doesn't match the standard(01)

Fields are missing, codes don't line up and tax breakdowns are off. The invoice is valid in your ERP and invalid everywhere else.

Fixed by mapping to EN 16931
Every country adds its own rules(02)

XRechnung, FA(3), Factur-X and Peppol BIS each check different things. One format does not pass everywhere.

Fixed by country validation
Every country, its own connection(03)

Peppol, KSeF, the French platforms, SdI and myDATA each need their own route. Most teams end up with one supplier per country.

Fixed by one integration
Rejections pile up where nobody looks(04)

A rejected invoice is an unpaid invoice. Without someone watching, they sit in a portal until a customer calls about it.

Fixed by monthly care
R
Returned invoicePeppol validation, test mode · 27.09.2026
Rule
BR-CO-16
Cause
Amount due does not add up

As returned[BR-CO-16]-Amount due for payment (BT-115) = Invoice total amount with VAT (BT-112) -Paid amount (BT-113) +Rounding amount (BT-114).

R
Returned invoiceXRechnung validator (KoSIT) · 27.09.2026
Rule
BR-DE-15
Cause
Buyer reference (BT-⁠10) missing

As returned[BR-DE-15] Das Element "Buyer reference" (BT-10) muss übermittelt werden.

R
Returned invoiceKSeF 2.0 test environment · 27.09.2026
Rule
KSeF 430
Cause
Byte-order mark at the start of the file

As returnedBłąd weryfikacji pliku faktury. Wykryto BOM w pliku.

R
Returned invoiceKSeF 2.0 test environment · 27.09.2026
Rule
KSeF 440
Cause
Duplicate: already accepted in an earlier session

As returnedDuplikat faktury. Faktura o numerze KSeF: 3986650091-20260927-86E6E5800000-AA została już prawidłowo przesłana do systemu…

Two ways to buy

Buy from us directly, or through your ERP partner.

Same scope and same evidence, with a two-day test target on the routes we have tested.

Pricing

A standard scope, priced before work starts.

One legal entity, one source system, one country route and one outbound invoice family.

Standard unitfixed price

EUR 3,600direct, per case

EUR 3,000 through an ERP partner (wholesale)

Bring us one case

What's included

  • Mapping Your ERP's invoice export, turned into the EU standard format (EN 16931), field by field.
  • Validation The mapped invoice is checked against the applicable format and country rules before test submission.Included in scope
  • Sending Invoices go out through Peppol, KSeF, a French approved platform or the national system each country uses, and the status comes back by webhook or API.
  • Valid test milestone We target the first valid test invoice within two working days of the complete ready package.Readiness-gated target
  • Rejection handoff Status and rejection messages come back by webhook or through the API, with optional ongoing care.First month of rejection care free
  • Rule changes Mandates move. When a country changes its rules or dates, we update your setup and tell you what it means.
Rejection careFirst month free

EUR 599per monthdirect, per case

EUR 499 per month through an ERP partner (wholesale)

Talk through your setup
  • Every rejection tracked to a fix
  • Root cause fixed in the mapping, not just the invoice
  • A monthly report you can hand to finance

Quoted separately

  • Extra entities and countries
  • Inbound flows
  • Reporting and archive
  • ERP user-interface work
  • Platform and licence fees
Check one case

Network fees for access points and platforms are passed through at cost and named in the scope.

How it works

From your ERP export to an accepted invoice.

The clock starts after readiness: representative data, working source access, issued test credentials or certificates, and a technical owner on your side. Production timing can still depend on platform onboarding, authorisation and UAT.

  1. Scope

    Your ERP, countries and volumes, in one call.

    01/06

  2. Map

    Your export matched to EN 16931.

    02/06

  3. Validate

    Checked against each country's rules.

    03/06

  4. Test

    Test invoices in the network's test environment.

    04/06

  5. Go live

    First live invoices sent and confirmed.

    05/06

  6. Monitor

    Rejections fixed, a report every month.

    06/06

How it works

Evidence

Validation evidence

Official rule sets · runs from 26.09.2026 to 04.10.2026

  1. 27.09.2026
    Peppol BIS 3.0 · BE, DE, FR, PLUBL 2.1 schema · CEN EN 16931 · Peppol BIS Billing 3.0.20
    XML
    4 of 4 pass
  2. 27.09.2026
    Peppol · access pointBelgian invoice sent through a certified access-point sandbox (test mode)
    Validator: 0 issues
    Accepted · sent
  3. 26.09.2026
    Poland · KSeF FA(3)FA(3) schema 1-⁠0E · submitted to the KSeF 2.0 test environment
    FA(3) XML · UPO
    KSeF number issued
  4. 27.09.2026
    Romania · RO e-⁠FacturaCIUS-⁠RO 1.0.9 locally · ANAF public validation service
    PDF · XML
    ANAF: ok
  5. 27.09.2026
    Rejection test10 local defects · live defects at ANAF, KSeF and a Peppol access point
    BR-⁠RO-⁠100 · KSeF 440 · BR-⁠CO-⁠16
    All rejected
  6. 27.09.2026
    Correction test26 defects against the Peppol, XRechnung, CII, CIUS-⁠RO and FA(3) rules, each corrected and checked again
    Report
    26 of 26 fixed
  7. 04.10.2026
    Full run · all routes34 scenarios: Peppol, France, Poland, Romania, Germany, lookups and ERP connectors
    Summary
    34 of 34 passed

Sample data. Companies, VAT IDs and IBANs are fictitious. Tested in official test environments and sandboxes, October 2026.

A readable PDF on top. A compliant e-⁠invoice inside.

Our sample PDFs carry the EU mandatory fields, the right wording for reverse charge and exemptions, a SEPA payment code and the structured XML the network needs.

  • Sample invoice: Belgium to Germany, reverse charge
    Belgium → Germanyreverse charge · ENPDF · XML
  • Sample invoice: German domestic, 19% VAT
    Germanydomestic VAT · DEPDF
  • Sample invoice: French services invoice
    Franceservices · FRPDF · XML
  • Sample invoice: Polish domestic invoice
    Polanddomestic VAT · PLPDF · XML
  • EN 16931 · Peppol BIS 3.0 Structured UBL XML next to the PDF, ready for the network.
  • Art. 226 checked Each invoice is checked for the fields the VAT Directive requires, plus country rules for DE, FR, PL, BE and RO.
  • Local language Labels and legal wording in English, German, French or Polish.
  • Pay by scan, on request A SEPA QR code with the amount and reference filled in.

Your brand, on request We can apply your logo, colours, payment details and approved layout, or your ERP partner’s, while keeping required fields and structured data intact.

See the evidence

ERP systems

Same process. Shaped around the ERP you already run.

ERP8

Countries9

For partners

Your clients need e-⁠invoicing. Add delivery capacity without losing the account.

Bring one real client case. Keep the relationship and set the retail price.

You own ERP configuration and client communication. We own the agreed mapping, country validation, route integration, returned status and handover. Delivery can be under your brand.

Bring us one case

  • White-label or referral

    Your name stays on the relationship. Choose the model per client.

  • EUR 3,000 wholesale

    For the standard one-entity, one-source, one-country outbound scope. Businesses buying directly pay EUR 3,600.

  • You choose the margin

    Add your ERP work, discovery and account margin. We do not cap your client price.

  • No new platform to resell

    We rent the networks. You don't carry another licence.

Rejection care

An invoice that fails on day one costs you money on day thirty.

Networks send rejections back as codes, not explanations. We read them, correct the invoice, send it again and log the cause, so the same error doesn't repeat next month.

See the standard scope
R
Returned invoiceSpecimen from the rejection test, 27.09.2026
Returned by
Peppol access point, test mode
Rule
BR-CO-16
Cause
Amount due does not add up
Owner
Mapping

The part that matters after the invoice is sent.

  • Written scope

    ERP, countries, formats and price, agreed in writing first.

  • Licensed networks

    We route through certified Peppol and platform providers.

  • Tested before live

    Test invoices through test environments before go-live.

  • Monthly report

    Sent, accepted, rejected and fixed, in one page.

FAQ

The questions we get on almost every call.

Do we need to change our ERP?
No. We work from the invoice data your ERP already exports and connect it to the networks each country requires.
Are you a Peppol access point or an approved platform?
No. We integrate through the appropriate certified Peppol access point, French approved platform or local provider, and may use a public government API where the country supports direct integration. The route is named in the scope.
What does it cost?
EUR 3,600 when you buy directly, or EUR 3,000 wholesale through an ERP partner, for one legal entity, one source system, one country route and one outbound invoice family. Extra entities, countries, inbound flows, reporting, archive or ERP UI work are quoted separately, and network fees are passed through at cost.
Does the two-day target mean production go-live in two days?
It means the first valid test invoice within two working days after representative data, working access, test credentials or certificates and a technical owner on your side are ready. Production may still depend on platform onboarding, taxpayer authorisation and UAT.
We already have an e-⁠invoicing app in our ERP. Do we still need you?
Maybe not for sending. Apps generate the format, but someone still has to fix the mapping gaps and the rejections. That part is what we sell.
Can you work under our brand?
Yes. ERP partners can use us white-label or refer clients to us. We can also apply the partner's or end client's approved branding to the human-readable PDF. The structured invoice and required legal fields remain governed by the country format.
Can a business work with you directly?
Yes. We work with businesses directly and through ERP partners, always B2B. If a partner already runs your ERP, they can bring us in behind them. If not, your own IT team works with us on the ERP side.

All questions

Contact

Thirty minutes to test whether it fits the standard scope.

Bring one case. It helps to have:

  • Your ERP and version
  • The first country route and legal entity
  • An anonymised sample invoice and where the credentials stand

30-minute call

Choose a time

Choose a time

The calendar is provided by Cal.com. Loading it shares your IP address with Cal.com and may set cookies there.

or open it on cal.com