-
Our e-invoice checker failed every Peppol self-billing invoice. Now it uses the right rules
Peppol self-billing invoices name peppol.eu, so our checker ran the Billing rules on them and rejected all nine of OpenPeppol's examples. Here is the fix.
-
A date with a timezone hid a no-break space from our e-invoice checker
We checked which invoice values our checker treats as dates or numbers against Saxon. Dates like 2024-01-31+01:00 were missed, and 30 February was taken.
-
Forty comments could freeze our e-invoice checker
A one-line regex that spotted France's e-reporting files backtracked 2^n ways on n XML comments. How we found it, the fix, and why CI missed it.
-
Peppol BIS 3.1.0 rejects files from 24 February: check yours against it now
Our free e-invoice checker now runs Peppol BIS 3.1.0 before it is in force and marks each new finding. Five of OpenPeppol's own 3.0.22 examples fail it.
-
A Dutch VAT number with a space in it: what our e-invoice checker let through
Peppol warns on NL 123456782 B01. Our checker passed it, and never read the tax representative's VAT number. We measured both gaps against Peppol's own rule.
-
A Belgian Peppol address with a typo passed our preflight 1,769 times in 2,669
Our electronic-address check counted digits; OpenPeppol checks the mod-97 pair. Measured against Peppol's own rules: 13,645 misses before, 0 after.
-
Our e-invoice checker called 91% of valid new Dutch sole-trader VAT numbers typos
Since 2020 Dutch sole traders get VAT numbers checked with mod 97, not the elfproef. Our checker used only the elfproef; now 0 of 60,000 differ from stdnum.
-
Eighteen Oman e-invoice rules that never ran, and the variable name behind it
A cross-check against Saxon found that 18 of Oman's PINT rules were skipped on every file because one variable name collided. All of them run now.
-
An invisible space after an invoice total, and why our checker missed it
A no-break space after an e-invoice amount passed all our built-in checks while Saxon validators reject the file. INV-065 now names the field.
-
An invisible space in an Italian, Polish or Hungarian e-invoice amount, now caught
A no-break space after an amount passed our FatturaPA, KSeF, Facturae, NAV and ISDOC checks while XML schema validators refuse it. Now every reader names it.
-
A no-break space the browser ignored and Saxon did not
Our in-browser e-invoice rules read U+00A0 as whitespace; Saxon does not. On 688 test invoices we disagreed 161 times. Now 0, checked against SaxonC-HE.
-
Peppol checks party ids inside UBL invoice lines too, so now we do
Peppol's id rules name no parent, so a line's delivery party GLN can bounce a UBL invoice. Our checker missed 711 of 9,490 such files; now it misses none.
-
Every one of FNFE's extended example invoices failed our checker. Now they pass, for the right reason
E-Invoice Preflight now runs FNFE's EXTENDED-CTC-FR and Factur-X 1.09.2 EXTENDED rules on extended invoices: 175 of 175 runs match Saxon.
-
France's BR-FR e-invoice error codes, all 384 messages in English
FNFE-MPE publishes France's BR-FR rule messages in French only. E-invoice Preflight now reports all 384 in English, with the French kept beside each one.
-
France's e-reporting file (Flux 10): what the official controls miss
E-Invoice Preflight now reads France's Flux 10 e-reporting file and runs the PPF's controls offline. A 20% VAT line with 0.00 VAT passes all 150 of them.
-
France's BR-FR e-invoice rules now run in the browser, checked against FNFE's own XSLT
E-Invoice Preflight now runs FNFE-MPE's BR-FR Schematron 1.4.0.04 locally. It matched Saxon on 264 of 264 runs, after three fixes to how it reads Schematron.
-
France's e-invoice rules against Saxon, and a hidden space in Flux 10
France's BR-FR, extended, CDAR and Flux 10 rules, in the browser and on Saxon over 1,784 test copies: no rule ids differed. One Flux 10 gap is fixed.
-
Checking France's invoice status messages (CDAR) against FNFE's own rules
E-Invoice Preflight now reads France's CDAR status messages, compares them with the invoice and runs FNFE's BR-FR-CDV rules: 780 of 780 runs match Saxon.
-
A GTIN filed under Peppol's GLN scheme gets the GLN check: 581 test files our checker passed
In a CII invoice, an item's GlobalID under scheme 0088 meets Peppol's GLN rule, so a mistyped digit bounces the file. Our checker now reads line ids too.
-
One invisible character, two XPath engines: Dutch VAT numbers and Peppol's R056-2
A valid Dutch VAT number written with B drew a false blocking error; a trailing no-break space slipped past. 3,149 disagreements with Peppol to 0.
-
Peppol checks a Belgian KBO number in three places. The preflight checked one
INV-062 and INV-063 apply OpenPeppol's id rules to party identifiers and legal registration numbers, with 0 disagreements on 18,794 whole UBL and CII files.
-
Peppol checks the payee's ids too: 3,311 of 9,596 test files our checker passed would have bounced
OpenPeppol's id rules match a payee's and a tax representative's ids, not only the seller's. Our checker now reads them: 0 disagreements on 18,790 files.
-
Peppol only warns about a bad Italian or Dutch address. The preflight now does too
Seven warning-level PEPPOL-COMMON rules now run as a non-blocking INV-061 warning, with 0 disagreements against Peppol's own XQuery on 23,999 drawn ids.
-
Romania, Portugal, Croatia and the Netherlands: our e-invoice rules against Saxon
Four national e-invoice rule sets, run in the browser and on Saxon over 5,556 test copies: no rule ids differed. The one mismatch was in our test script.
-
Six of France's 43 invoice-status rules cannot fire
A French invoice status with no invoice number passes all 43 BR-FR-CDV rules on Saxon and on our engine. Why six rules are dead, and what we check instead.
-
Our e-invoice CLI skipped a check the web page ran: 24 of 34 files read differently
The Python CLI read party ids only from JSON, so Peppol's id format rule never fired on XML. A two-reader diff found 24 of 34 files apart; now 0.
-
Rio's Nota Carioca service codes: 998 codes, five acts, one check
Rio de Janeiro's NFS-e takes a six-digit service code from a table changed by four acts since 2018. We read them all and now check the code offline.
-
Slovakia's 2027 e-invoice mandate, read from the Act instead of vendor blogs
We read Slovakia's Act 385/2025 on slov-lex.sk. 1 January 2027 is a transitional rule; the general e-invoice rule waits until 2030. A Slovak check ships.
-
The Facturae signature policy hash belongs to a PDF revision from 2008
Every Facturae signer writes the same policy hash, and the PDF served today does not match it. The 2008 revision inside the file does.
-
Three false errors on Canary Islands invoices, found in the AEAT's own rule text
Our VERI*FACTU checker rejected valid IGIC records three ways. The AEAT's validation document showed why; all three are fixed, and two new checks added.
-
A Hungarian cancellation has to add up to zero: checking NAV corrections against their invoice
NAV checks a correction or cancellation against the invoice it refers to. Drop both into the checker and it now runs those checks offline.
-
Brazil's ISS has a legal floor and ceiling. Our NFS-e checker now reads them
Brazil's ISS rate must sit between 2% and 5%, with three exceptions. We added the check to ABRASF and national NFS-e and ran it on 489 public files.
-
Checking a Spanish Facturae file before FACe sees it
Our free checker now reads Spain's Facturae 3.2.1 and 3.2.2 offline: the official XSD plus its totals formulas, matched against xmllint on 1,000 files.
-
What SdI said, checked against the file it said it about
Our checker now reads SdI receipts, explains each rejection code in English and checks it against the invoice. Tried on 33 public receipts.
-
Why FACe says "firma no válida": checking a Facturae signature before you send it
Our free checker now verifies the XAdES-EPES signature on a Spanish Facturae file in the browser, and agreed with signxml on all 180 signed and broken files.
-
Will NAV accept it? Checking a Hungarian Online Számla report before it goes
Our free checker now reads Hungary's NAV Online Számla 3.0 report offline. On NAV's own 30 samples it found five faults in the samples themselves.
-
How the VAT on a Polish advance invoice is split, from the Ministry's own examples
FA(3) advance and settlement invoices split the payment across VAT rates by gross share. We now check it; the Ministry's 26 examples found six of our bugs.
-
NAV's own sample invoice gets a warning: a 2019 that never moved
We read the header and line warnings in NAV's Annex I one by one. 23 can be checked from the file, and one catches a slip in NAV's own sample.
-
The missing schema: checking NAV Online Számla files against the XSD NAV doesn't ship
Our Hungarian NAV checker now runs NAV's schema first, namespaces included. On 5,776 broken copies of NAV's samples it agrees with xmllint on all.
-
Hungary's product fee, checked on the invoice report, and the scripts phones were downloading
Our NAV Online Számla checker now checks product fee (termékdíj) totals against NAV's 13 warnings, and the offline download got 370 KB lighter.
-
Is NAV's 13-month delivery warning still alive? Its own spec says both
Annex I of NAV's Online Számla 3.0 spec lists warning 313 as live; the same PDF's change log says it was deprecated in 3.11. What our checker now says.
-
We checked a Hungarian invoice for five things NAV never checks
NAV's Annex I, read warning by warning: five checks NAV never makes, six renamed codes, a euro tolerance 100 times too loose, 21 missing warnings.
-
Rio de Janeiro's ISS rates on an NFS-e: 2% and 5% are always legal, 2.9% never is
Our NFS-e checker now reads Rio de Janeiro's own ISS rates (Lei 691/1984 art. 33). Its list is shifted against LC 116 the same way São Paulo's is.
-
São Paulo numbers its ISS service list differently from LC 116. Our NFS-e checker now knows
São Paulo taxes software at 2.9%, not 5%, and its service list is shifted against LC 116. Our NFS-e check now reads the city's rates and the shift.
-
Verifactu error codes: the AEAT's 247, mapped to checks you can run before sending
The AEAT publishes 247 Verifactu error codes. We mapped 113 of the record codes to offline checks, read the AEAT's reply, and found library copies out of date.
-
Which VAT rates does Verifactu accept? The AEAT's list, and the surcharge list beside it
On an S1 line the AEAT accepts only 0, 2, 4, 5, 7.5, 10 and 21% VAT, and eight surcharge rates. A free checker now rejects anything else before you send.
-
A Verifactu fingerprint hashes the amount as written: 15, not 15.00. A free checker names the slip
Spain's Verifactu records chain SHA-256 fingerprints. Our free checker recomputes each one, follows the chain, and names the slip when a hash is wrong.
-
Verifactu rejects 5% VAT after September 2024 and GB VAT numbers after Brexit. A free checker catches both
27 more of the AEAT's Verifactu rejection codes, from VAT rates out of date to GB numbers after Brexit, now caught before sending by a free checker.
-
A Bottle Deposit on a Croatian E-Invoice Is Exempt in One Layer and Out of Scope in the Other
Croatia's eRačun writes a bottle deposit as exempt for EN 16931 and out of scope in the HR extension. The free creator now writes both layers.
-
A Factur-X PDF that veraPDF passes, written with no dependencies
The free e-invoice creator now writes Factur-X / ZUGFeRD PDFs, a printed page with the CII XML inside, as PDF/A-3b. veraPDF passes all 8 test files.