Drop your XML file or your hybrid PDF: Lekteo lays the invoice out in plain language, checks it against the European EN 16931 standard and tells you what is wrong. No account, and your file never leaves your browser.
Loading the reader…
A file arrives by email or through your platform. It is called INV-2026-0847.xml, or it is a hybrid PDF that shows almost nothing. You double-click, and you get a wall of tags.
You did nothing wrong. An electronic invoice is not a document made for human eyes: it is a data file, meant to be picked up automatically by accounting software. The tags you are looking at are the invoice.
What you are missing is simply the tool that puts that data back into shape. If your file is a bare .xml, the page on opening an XML invoice covers that case. And if you are wondering why these files started arriving, the page on who must comply, and when explains it.
.xml and .pdf.Nothing to create, nothing to install, no address to leave behind. You do not need to know which format you are holding either: it is recognised as the file is read. The comparison of the three formats will tell you which one you received.
An invoice laid back out, in the order you normally read one:
Every piece of information also carries its standard identifier — BT-1 for the invoice number, BT-9 for the due date. Those codes come from the European EN 16931 standard, and they earn their keep the day you have to point a third party at one precise field.
EN 16931 is the European standard that defines what an invoice must contain: the information it carries, named BT-xx, and the consistency rules it must satisfy, numbered BR-xx. Lekteo checks those rules and explains every finding in plain language.
It will flag, for instance, a VAT amount that does not match its taxable base, a total that does not add up, a mandatory field that is missing, an IBAN whose check digits fail, or a due date that falls before the issue date. Each finding states what is wrong using the real figures from your file, why the rule exists, and where to look in the invoice.
A finding is not accounting advice. Lekteo tells you what the standard says; whether you pay or dispute remains your call.
An invoice contains your turnover, your customers’ names, your commercial terms, and often your bank details. That is not data you hand to an unknown service just to see a table.
Lekteo runs entirely in your browser, in local JavaScript. The file is opened on your machine and transmitted nowhere: no upload, no account, no database. You can verify it: cut your connection once the page has loaded, and reading still works.
Once the invoice is displayed you can export it as JSON or CSV to pick it up in a spreadsheet or in your bookkeeping tool. The export, too, is produced on your own computer.
No. There is no account, no email address to hand over and no software to install. You open the page, you drop the file, you read it.
Technically yes, and the result is almost always unusable. Excel proposes a column layout that resembles no invoice, and Word shows the source code as it is. Neither knows the structure of an electronic invoice: nothing tells them which tag holds the amount due.
No. The format is identified as the file is read, from its first tag. You have nothing to choose before dropping it, and both the format and the declared profile are shown at the top of the invoice afterwards.
No. It is sent to no server and stored nowhere. Processing happens in the open tab; closing it ends everything. Your file stays on your machine, untouched.
Start by reading the finding: it gives the expected amount and the declared amount. If the gap is real, ask for a corrected invoice or a credit note before paying. Lekteo reports a discrepancy; it does not decide for you.