E-mail
[email protected]Evidence
Tested in the official test environments. The files are here.
Instead of logos, the work itself: invoices generated from ERP-style data, checked against the official rule sets and sent through the countries' own test environments in September 2026.
- Route
- KSeF 2.0 (test)
- Format
- FA(3)
- Posted
- 26.09.2026
- Receipt
- UPO received
Real receipts from official test environments, 26 and 27 September 2026. Sample data, fictitious companies.
Validation evidence
Official rule sets · run 27.09.2026
- 27.09.2026Peppol BIS 3.0 · BE, DE, FR, PLUBL 2.1 schema · CEN EN 16931 · Peppol BIS Billing 3.0.204 of 4 pass
- 27.09.2026Peppol · access pointBelgian invoice sent through a certified access-point sandbox (test mode)Validator: 0 issuesAccepted · sent
- 26.09.2026Poland · KSeF FA(3)FA(3) schema 1-0E · submitted to the KSeF 2.0 test environmentKSeF number issued
- 27.09.2026Romania · RO e-FacturaCIUS-RO 1.0.9 locally · ANAF public validation serviceANAF: ok
- 27.09.2026Rejection test10 local defects · live defects at ANAF, KSeF and a Peppol access pointBR-RO-100 · KSeF 440 · BR-CO-16All rejected
- 27.09.2026Correction test26 defects against the Peppol, XRechnung, CII, CIUS-RO and FA(3) rules, each corrected and checked again26 of 26 fixed
Sample data. Companies, VAT IDs and IBANs are fictitious. Network transmission is tested per route in the pilot sandbox.
A readable PDF on top. A compliant e-invoice inside.
Every invoice we produce carries the EU mandatory fields, the right wording for reverse charge and exemptions, a SEPA payment code and the structured XML the network needs.
- EN 16931 · Peppol BIS 3.0 Structured UBL XML, attached to the PDF and sent over 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 A SEPA QR code with the amount and reference filled in.
Your brand We can apply your logo, colours, payment details and approved layout, or your ERP partner’s, while keeping required fields and structured data intact.
What the test environments answered
| Environment | What we sent | What came back |
|---|---|---|
| KSeF 2.0 TEST, Poland | An FA(3) invoice, then the same invoice again | A KSeF number and UPO; the second copy rejected as a duplicate (440) |
| ANAF validation service, Romania | A CIUS-RO invoice and a credit note, then planted defects | State ok for both; BR-RO-100 and a wrong CUI rejected |
| Peppol access-point sandbox, Belgium | A Peppol BIS invoice and a credit note | 0 validator issues and sent; a BR-CO-16 defect refused |
| French platform sandbox (SUPER PDP) | UBL France, CII France and Factur-X invoices | Deposited and received (200, 202); a BR-CO-16 copy rejected (213) |
| KoSIT, veraPDF and Mustang, Germany | XRechnung and ZUGFeRD invoices and credit notes | Accepted with 0 messages; PDF/A-3B valid |
Rejections, as the systems returned them
Four rejections from our tests, word for word. Finding these before anyone else does is the job.
- RReturned 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).
- RReturned 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.
- RReturned invoiceKSeF 2.0 test environment · 27.09.2026
- Rule
- KSeF 430
- Cause
- Byte-order mark at the start of the file
As returned
Błąd weryfikacji pliku faktury. Wykryto BOM w pliku.
- RReturned invoiceKSeF 2.0 test environment · 27.09.2026
- Rule
- KSeF 440
- Cause
- Duplicate: already accepted in an earlier session
As returned
Duplikat faktury. Faktura o numerze KSeF: 3986650091-20260927-86E6E5800000-AA została już prawidłowo przesłana do systemu…
What this evidence is, and what it is not
- Test environments and sandboxes, not production traffic
- Fictitious companies, VAT IDs and IBANs
- Client work is shown only with the client's consent
Want to see a route run with your own data?
Bring one case. The first valid test invoice is the proof that matters.
- Your ERP and version
- The first country route and legal entity
- A representative invoice and where the credentials stand
30-minute call
Choose a time