Next to the table, a consistency check compares the two halves of the file: the invoice number and the grand total (GrandTotalAmount) from the XML are looked for in the text of the PDF pages, in the usual number formats (1190.00, 1,190.00, 1.190,00), and either one that cannot be found is flagged as a mismatch for you to check. The header shows what kind of e-invoice it is, its version and conformance level from the XMP metadata, the attachment’s relationship to the PDF (Data, Alternative or Source) and the PDF/A part the file declares, and Download the XML saves the attached file to your device. Bindery reads and preserves e-invoices; it does not validate the invoice against the full EN 16931 schematron, so a file that reads cleanly here can still be rejected by a receiver’s validator. Everything runs in your browser: the invoice is never uploaded.
How it works
- Drop the PDF on this page — it opens in Upload-ready on your device
- Read the invoice table and the consistency check: the XML’s invoice number and grand total, looked for on the visible pages
- Download the XML if your accounting software or your accountant needs it
Questions people ask
Which invoices can it read?
PDFs with an attached file named factur-x.xml (Factur-X, and ZUGFeRD from version 2.1), zugferd-invoice.xml (ZUGFeRD 2.0, and ZUGFeRD-invoice.xml in 1.0) or xrechnung.xml (ZUGFeRD’s XRECHNUNG profile) in the document’s embedded files. The table is read from the CII (UN/CEFACT Cross Industry Invoice) syntax those files use, including the older CrossIndustryDocument schema of ZUGFeRD 1.0; an xrechnung.xml written in UBL syntax is found and can be downloaded but is not shown as a table. A PDF without such an attachment is an ordinary PDF invoice, with no XML to read.
What does the consistency check compare?
Two values: the invoice number and the grand total (GrandTotalAmount) from the XML, looked for in the text of the PDF pages in the usual number formats (1190.00, 1,190.00, 1.190,00). If either cannot be found, the check flags a mismatch: the page a person reads and the XML the software books may not describe the same invoice, and the XML is the one that counts. It does not compare every line, rate or date, and when a prepayment makes the amount due differ from the grand total, it still looks for the grand total. It can only search text the PDF contains — a scanned page without a text layer gives it nothing to find.
Does Bindery validate the e-invoice?
No. Bindery does not validate the invoice against the full EN 16931 schematron or the Factur-X, ZUGFeRD and XRechnung business rules. It reads the XML, shows it as a table, looks for two of its values on the pages and, in the tools that rewrite PDFs, preserves it. For a formal verdict, use the validator of your receiver or of the platform you send through. Reading happens in your browser tab; Bindery has no server that receives documents.
What happens if I compress or merge the invoice afterwards?
Compress, Merge, Flatten, Watermark, Organize, Upload-ready’s fix and Leak Check’s Sanitize warn first that the file is an e-invoice whose attached XML is the legal invoice, and offer to continue and keep the XML, or cancel; when merging, only the first document’s XML can be kept, and the warning says so. Other tools that write a new PDF — Split, Extract pages, Delete pages, Mix, Unstack, Remove metadata and PDF to PDF/A among them — do not check for an e-invoice and can drop the XML, so keep the original.