Skip to content
Languages
A person reviews printed documents beside an open laptop

Bilingual e-invoice: Check the XML and PDF view

Checking a bilingual e-invoice. Do the XML and PDF view match?

Your customer reads the English PDF view while their accounts team imports the XML. Compare both before sending so that they describe the same invoice.

·

Photo: SHVETS production on Pexels

You export a ZUGFeRD invoice for a customer in Germany. The bilingual view shows 12 November as the date of supply, but the embedded data shows 21 November. A file can pass a technical check and still contain the wrong date. If the two parts of a hybrid e-invoice differ, the structured data takes precedence. Check the exported file itself before you send it.

1. Confirm what your customer will process

Ask their accounts team about the format, delivery channel and any purchase order reference or extra fields. A compliant hybrid e-invoice combines structured data and a PDF view in one file. For an XML-only invoice, open the file in a viewer to check it. If the customer also wants a readable copy, agree on how they will identify the invoice they should post.

A standalone PDF is not an e-invoice under § 14 UStG. Whether it can be used as another type of invoice depends on the transaction and recipient. For certain domestic B2B transactions, § 27(38) UStG allows another type of invoice until the end of 2026. If the issuer's total turnover in the previous year did not exceed €800,000, the transition can also apply to transactions carried out in 2027. Sending another type of electronic invoice under this transition requires the recipient's consent. Check exceptions separately.

2. Keep the required fields and translation in sync

Enter the date of supply, quantities, prices and tax data once in the source invoice. Do not give the translated view another invoice number or different amounts. Translate the field labels and descriptions so both versions cover the same scope. “Wartung des Webshops im November / Online shop maintenance in November” is clearer than two descriptions that give different periods.

In the standard case described here, the structured part must contain the information required for VAT purposes. An attachment can explain details, but it cannot supply required data missing from the structured part. § 14 UStG does not generally require invoices to be written in German. For special mandatory wording such as “Reverse charge”, check that the tax treatment applies and use an accepted term. In German tax proceedings, the tax office can request a translation of foreign-language documents submitted to it under § 87 AO.

3. Check the exported file twice

First use a validator to check the expected format and business rules. It can flag missing fields or inconsistent totals. Then view the structured data and compare it with the order and PDF view. Without the supporting documents a validator cannot tell when you actually supplied the service.

  • Are the supplier, customer and references correct?
  • Do the invoice number, invoice date and date of supply match the order records?
  • Do the description, quantities, currency, tax rate, tax amount and amount due agree?
  • If shown, do the payment terms and details match what you agreed?

4. Correct the source and export again

The order records in the example establish 12 November as the date of supply. Correct the invoice data before sending and export a fresh file. Check it with the validator and viewer. Editing the PDF view alone leaves the wrong date in the XML. If you have already sent the invoice, use the invoice correction process and retain the link to the original.

5. Keep the file you actually sent

Retain the sent original with its structured data. Keep at least the structured part of an e-invoice in its original form. If the visible part contains additional information relevant to tax, it may also need to be retained. Under § 14b UStG, businesses generally retain invoices for eight years from the end of the calendar year of issue. Keep any later translation with a reference to the original.

Checklist before sending

  • Confirm the customer's format, delivery channel and language preference.
  • Check that the structured data has all required fields and clear wording.
  • Validate the actual exported file and open it in a viewer.
  • Compare the data against the order records and readable view.
  • Identify the file to send and keep the sent original for your records.

See the invoice language guide for help choosing German, English or a bilingual view. The checks here apply to e-invoices under German VAT law.

Official sources

Photo: SHVETS production / Pexels · Pexels license

Organise your office digitally

With Motorica you create invoices, quotes and receipts – and keep deadlines in view.

Discover Motorica   Knowledge