ZUGFeRD / Factur-X
A normal-looking PDF with the invoice data embedded as XML. Tailride finds the XML and uses it instead of reading the page.
More and more suppliers send electronic invoices: a PDF with hidden XML inside (ZUGFeRD, Factur-X), a plain XML file (XRechnung, Peppol), or a signed Italian FatturaPA. Tailride recognises them, reads the structured data directly — no OCR guesswork — and turns XML-only invoices into a readable PDF for you.
Since 2025 every business in Germany must be able to receive e-invoices, France and Belgium are phasing them in, Italy has required FatturaPA for years and Spain uses Facturae with the public sector. If your suppliers send them, your invoice tool has to understand them — not just look at the picture.
A normal-looking PDF with the invoice data embedded as XML. Tailride finds the XML and uses it instead of reading the page.
The German public-sector standard, delivered as pure XML in either of its two syntaxes. Both are read.
The European exchange format used across the Peppol network and by many invoicing tools. Credit notes included.
Italy's mandatory e-invoice format, including the digitally signed .p7m envelope, which Tailride unwraps for you.
The Spanish structured format used with public bodies and a growing number of companies.
An XML-only invoice gets a clean, human-readable PDF generated from its data, so you can preview, share and archive it like any other invoice.
Nothing to configure — e-invoices flow through the same sources as everything else.
By email, from a supplier portal, through the desktop app's Proton Mail or folder sources, or as a manual upload.
Embedded XML, a standalone XML file or a signed envelope is detected before any reading starts. The desktop app already spots embedded XML during its local check.
Supplier, dates, totals, tax rates, payment terms and every line item come straight from the structured data — exact, no OCR.
The result goes through the same account coding, VAT handling and export to Xero, QuickBooks, sevDesk, Lexware Office, e-conomic, Odoo, Sage and the rest.
Net, VAT and gross per rate, line by line, taken from the document's own data. Reverse-charge and tax notes are carried through.
A PDF that arrives twice — once with XML, once as a plain scan — is recognised as the same invoice.
E-invoices sit next to scanned receipts and email invoices in one list, with the same coding rules and exports.
Fields that don't exist on paper — buyer references, order numbers, payment details — are kept with the document.
You often can't tell from the PDF — a ZUGFeRD or Factur-X invoice looks like any other. Tailride checks every incoming file for embedded XML and marks the ones it finds. Pure XML files and .p7m files are always e-invoices.
No. E-invoice reading is on for every account and every source. If the data is there, Tailride uses it.
The XML is the legally binding part of a hybrid invoice, so Tailride uses the XML. You can always open the PDF next to the extracted data to compare.
Not yet. Tailride reads Peppol-format (UBL) invoices you receive by email or download, but does not act as your Peppol access point today.
It recognises embedded XML during its local check, so a hybrid PDF from Proton Mail or a watched folder is always treated as an invoice and sent on. The reading itself happens in Tailride.
All the integrations Tailride supports: Xero, QuickBooks, sevDesk, Lexware Office, e-conomic, Odoo, Sage, FreeAgent, Holded, Business Central, plus Google Drive, OneDrive and Google Sheets.
Keep reading
E-invoices arrive through the same sources as everything else — and get the same coding and export.
Connect your inbox or install the desktop app — e-invoices are handled from the first one.