Skip to content
AutaxoAutaxo

Vehicle Data in E-Invoices: What Changes from 2027 and What VINvoice Proposes

17 min read E-Invoicing VINvoice Invoicing Vehicle Data ZUGFeRD Digitalization
Leonard Niehaus : Co-founder & CTO, Autaxo
Julian Alessio Goßen : Co-founder, Autaxo

In brief

VINvoice is an open, vendor-neutral and voluntary convention for vehicle data in EN 16931 e-invoices. The VIN goes into the invoice line object identifier (BT-128); other characteristics such as first registration or mileage go into named item attributes (BG-32). As of November 2026, VINvoice is a draft for review.

On this page (12 sections)

From 2027, invoices from domestic business partners will arrive as e-invoices more often: both the invoice for a vehicle you buy from another dealer and the invoice for workshop work, reconditioning or transport. Your software can take amounts and tax rates from the structured file. But the e-invoice has no field of its own for the vehicle. Without a shared rule, details such as first registration or mileage end up in free text or in freely named attributes, where software cannot reliably find them.

VINvoice proposes where these details go in an e-invoice and what they are called, without introducing a new format.

Disclosure up front: This article is published by Autaxo GmbH. The company sponsors VINvoice and implements the convention in its software. The article is an explanation with sources, not a neutral assessment. VINvoice is voluntary and still a draft for review.

What Changes for Your Incoming Invoices from 2027?

For transactions from 2027, domestic businesses with total prior-year revenue of more than €800,000 must generally issue their invoices to other domestic businesses as e-invoices.

Under section 14(1) sentence 3 of the German VAT Act (UStG), an e-invoice is an invoice that is issued, transmitted and received in a structured electronic format and enables electronic processing, such as XRechnung or ZUGFeRD/Factur-X, except in the MINIMUM and BASIC WL profiles. A simple PDF without embedded data is not an e-invoice. Section 27(38) UStG governs when paper or a simple PDF is still permitted:

Transactions inPaper or simple PDF still permitted?
2025 and 2026Yes, until December 31, 2026, for all issuers; a PDF only with the recipient’s consent (no. 1).
2027Only until December 31, 2027, and only if the issuer’s total revenue in 2026 did not exceed €800,000; a PDF still only with the recipient’s consent (no. 2). Regardless of revenue, EDI remains possible with the recipient’s consent until December 31, 2027 (no. 3).
From 2028No transitional rule remains in section 27(38) UStG.

What matters is the issuer’s revenue, not yours. Even as a small business, you will therefore receive more e-invoices from larger domestic partners from 2027. You do not need to consent to an e-invoice, even from a smaller issuer (section 14(1) sentence 5 UStG): the obligation under section 14(2) sentence 2 no. 1 UStG does not depend on revenue, and section 27(38) UStG only allows paper or, with your consent, a simple PDF as a transitional alternative. Under the wording of the law, smaller issuers will also be included from 2028. The same timeline applies to your own invoices to domestic business customers; then your own total revenue in 2026 is what counts. Our article E-invoicing in the automotive trade explains the exceptions.

Why Does an E-Invoice Have No Dedicated Field for Vehicle Data?

Because EN 16931, the European data model behind XRechnung, ZUGFeRD/Factur-X and Peppol invoices, has no dedicated field for vehicle data.

For the VIN, the invoice line object identifier (BT-128) provides a structured place. All other vehicle details end up in free text or in item attributes (BG-32) whose names nobody has defined. The recipient’s software then has to guess: Which date is the first registration, which number is the mileage, and does the line describe the purchased vehicle or only a repair to it?

In day-to-day work, this can mean: the invoice arrives in structured form, yet you still type in the vehicle details and assign the workshop invoice by hand.

What Is VINvoice?

VINvoice is an open, vendor-neutral convention for vehicle data in EN 16931 e-invoices, not a separate invoice format. It proposes uniform rules for fields that already exist:

  • VIN: in the invoice line object identifier, marked as a vehicle identification number, and additionally as a separate row that every e-invoice viewer displays.
  • Other characteristics: one item attribute each, with a readable label and a fixed key in square brackets. People read the label; software reads the key.
  • Values: dates as 2022-03-18, mileage as 48200 without a thousands separator, values from the convention’s lists as lowercase codes such as used.
  • Marker and role: One row marks the vehicle line, and a second row states its role: supply, trade-in, service on the vehicle (such as repairs, parts or testing), rental, leasing, agency, transport or other.

Excerpt from a vehicle line: one dealer sells a used car to another dealer under the margin scheme. The values come from VINvoice’s fictitious test invoices. The table shows the registry’s English labels; the German test invoice uses the German ones:

Item attribute name (BT-160)Value (BT-161)
VINvoice specification [vehicle.specificationId]vehicle/1.0
Vehicle role [vehicle.roleCode]supply
Vehicle identification number (VIN) [vehicle.vin]TSTVEH016N0000001
Date of first registration [vehicle.firstRegistrationDate]2022-03-18
Odometer reading (km) [vehicle.odometerReadingKm]48200
Margin scheme [vehicle.marginSchemeIndicator]true

There is a reason for the last row: EN 16931 does not yet have a VAT category of its own for the margin scheme. According to the VINvoice specification, margin scheme lines for domestic supplies and supplies to other EU member states therefore use the “exempt” category (E), with an exemption reason as text. The “Margin scheme” row is meant to show receiving software that this is not a genuine VAT exemption. It does not replace the statement required under section 14a(6) UStG, which for used vehicles is usually “Gebrauchtgegenstände/Sonderregelung” (second-hand goods/special scheme). That statement still belongs on the invoice, in the e-invoice as a note. The Invoice Text Generator provides suitable wording.

Summary for Software Vendors and Tax Advisors

  • VIN: BT-128 with the scheme AKG from UNTDID 1153 and the document type 130, plus the row vehicle.vin with the same value.
  • Characteristics: one item attribute (BG-32) per characteristic, name Label [key] in BT-160, value in BT-161. Dates in ISO 8601, numbers without group separators, tokens from the registry’s lists in lowercase.
  • Marker and role: exactly one row vehicle.specificationId = vehicle/1.0 per vehicle line, instead of a specification identifier in BT-24, plus the role row vehicle.roleCode.
  • Workshop invoices: the rows on a reference line with the value 0.00, and the VIN in BT-128 of every further line for the same vehicle.
  • Tax-relevant keys, always with a label: vehicle.odometerReadingKm, vehicle.odometerReadingMi, vehicle.newMeansOfTransportIndicator, vehicle.firstEntryIntoServiceDate and vehicle.marginSchemeIndicator. The specification refers to Article 2(2)(b), Article 138 and Articles 311 to 325 of the EU VAT Directive as well as sections 1b, 6a, 14a(4) and 25a UStG, and calls these encodings provisional until a tax advisor has confirmed them in writing.
  • Status: registry vehicle/1.0-draft of October 24, 2026, with 48 keys; 19 test invoices in CII and UBL; and a reference checker at vinvoice.org.

Is VINvoice Mandatory?

No. VINvoice is a voluntary convention, not a law and not a standard. For e-invoices, the German VAT Act requires a structured format that complies with the European standard on electronic invoicing, or an agreed format that is interoperable with it (section 14(1) sentence 6 UStG). It does not specify where vehicle data goes within that format. CEN, FeRD, KoSIT, OpenPeppol and public authorities have neither published nor endorsed VINvoice. The statutory invoice particulars remain mandatory.

Does an E-Invoice with VINvoice Rows Remain Valid?

Yes. VINvoice only uses fields that EN 16931 already provides, and adds neither an XML element nor a specification identifier of its own. According to the specification, the invoice therefore remains a valid EN 16931 e-invoice in every syntax and every national profile. Software without VINvoice support displays the rows as ordinary item attributes. Tax-relevant details such as mileage or the margin scheme always carry a readable label. Under the specification’s reading rules, deviations from VINvoice never make an invoice invalid.

What Does Autaxo Already Implement?

Starting with version 9.5, released on October 29, 2026, Autaxo writes VINvoice rows into the e-invoices for your vehicle sales and reads them from incoming e-invoices.

When Writing: Your Sales Invoices

Sales invoices that Autaxo generates contain an e-invoice in ZUGFeRD format (Factur-X, EN 16931 profile), even for private customers. If a detail required for this is missing, such as your customer’s address, Autaxo points this out before you finalize. For the vehicle sold, Autaxo writes the marker, the role “supply”, the VIN, make and model. First registration, condition (new or used) and mileage are added if they are recorded on the vehicle, and for sales under the margin scheme (section 25a UStG), so is the “Margin scheme” row. The VIN also appears in the object identifier, and the usual line text remains. If a vehicle detail is missing or a value does not comply with the convention’s rules, Autaxo omits only that row.

A reversal of the vehicle sale repeats the rows; ancillary lines such as delivery get none. Workshop, cost and commission invoices that you issue carry vehicle rows only if you link the vehicle to the invoice yourself before finalizing. Each linked vehicle then appears in a line of its own without an amount, with VIN, make, model and first registration; totals and tax stay the same.

Autaxo automatically checks its sample invoices with VINvoice rows against the Factur-X schema, the EN 16931 validation rules and the VINvoice checker. You can find more on invoicing under Invoicing and e-invoices.

When Reading: Your Incoming Invoices

When you upload an e-invoice, Autaxo recognizes it as an XML file (ZUGFeRD/Factur-X, XRechnung, Peppol BIS) or as a PDF with an embedded XML file. Autaxo reads such a PDF, for example ZUGFeRD or Factur-X, in the same way when it arrives in Autaxo by email.

If the lines relating to a vehicle carry VINvoice rows, or if the VIN is in the object identifier, marked as a vehicle identification number, Autaxo reads the invoice without AI. Autaxo takes the VIN, make, model, first registration and mileage from the VINvoice rows, along with the line text; a flagged margin scheme becomes the tax case in the draft. Autaxo treats only lines with the role “supply” as the purchase of the vehicle itself. If the role row is missing, for example when only the object identifier states the VIN, a line with an amount generally counts as a supply. Autaxo does not currently import the vehicle configuration, condition, power, color, fuel or the characteristics for new vehicles.

If the VIN appears only in the line text, an AI model reads the text of exactly these lines and decides whether they concern the vehicle itself or a service performed on it. If the VIN is in none of these places, that is, neither in VINvoice rows nor marked in the object identifier nor in the line text, Autaxo does not recognize a vehicle line. This also applies if the VIN is in a freely named attribute such as “Fahrgestellnummer” (chassis number). A vehicle purchase then arrives as an ordinary line. For a ZUGFeRD PDF without lines (the MINIMUM and BASIC WL profiles), AI receipt recognition reads the details from the visible PDF.

Automatic assignment only happens when the VIN matches exactly. Autaxo links a purchase to a vehicle if exactly one existing, non-archived vehicle that has not yet been purchased carries this VIN. If there is no match and the VIN is valid, Autaxo creates the vehicle when you finalize. If there is a possible match, such as a vehicle with this VIN that has already been purchased or sold, or if a valid VIN is missing, you decide before finalizing. A workshop or cost invoice goes to the vehicle’s costs if exactly one non-archived vehicle carries the VIN. Without a match, Autaxo does not assign it to any vehicle and does not create one either. You can then assign it yourself in the draft, or upload it directly in the vehicle’s “Costs & invoices” tab. You always review and finalize the draft yourself.

What Autaxo Does Not Currently Write

  • New vehicles: no “New means of transport” or “First entry into service” rows. More on this in the section on supplies of new vehicles to other EU member states.
  • Other characteristics: Of the draft’s 48 keys, Autaxo uses nine. Characteristics not written as rows include vehicle configuration, power, engine capacity, color, fuel, registration number, the German HSN/TSN key numbers and the odometer reading in miles. Color and power, if recorded, appear only in the line text.

What Decides Whether VINvoice Helps You with Incoming Invoices?

On the sender: VINvoice only helps you with incoming invoices if the sender’s software writes the rows.

Sales invoices from Autaxo do. An example: you buy a vehicle under the margin scheme from a dealer who invoices with Autaxo and upload their e-invoice to Autaxo. Autaxo then transfers the VIN, make, model and the tax case into the draft without AI, and the first registration and mileage too if the seller recorded them. You do not have to type any of it; you do still review and finalize.

Whether the software your other suppliers use writes VINvoice is up to its vendors. Ask instead of assuming it does.

What Applies When You Supply New Vehicles to Other EU Member States?

If you supply a new vehicle to another EU member state, the invoice must contain the characteristics under section 1b(2) and (3) UStG, and EN 16931 has no field of its own for them.

Section 14a(4) sentence 1 UStG states, in translation: “An invoice for the intra-Community supply of a new vehicle must also contain the characteristics referred to in section 1b(2) and (3).” For land vehicles, the following applies:

  • A vehicle is a motorized land vehicle with an engine capacity of more than 48 cubic centimeters or a power output of more than 7.2 kilowatts (section 1b(2) UStG).
  • It is new if it has traveled no more than 6,000 kilometers or if, at the time of acquisition, its first entry into service was no more than six months earlier (section 1b(3) UStG).

Either criterion is enough: a three-year-old car with 5,000 kilometers is just as new as a demonstration car with 9,000 kilometers whose first entry into service was four months before the acquisition. Section 14a(4) does not itself specify which of these details belong on the invoice or in what form. The invoice must be issued by the 15th day of the following month (section 14a(3) UStG). The law generally does not require an e-invoice here, because the domestic obligation presupposes that both businesses are established in Germany (section 14(2) sentence 2 no. 1 UStG). If you issue an e-invoice anyway, it has no field of its own for these characteristics either.

For this case, VINvoice provides the “New means of transport” row, plus power or engine capacity and the mileage or the first entry into service. In VINvoice, the first entry into service is a characteristic of its own, separate from the first registration. The law, too, refers to the first entry into service, not to the first registration. The two dates can differ, for example if a vehicle was used before it was registered. Clarify with your tax advisor whether, in your case, the first registration is sufficient as the information on the first entry into service.

Autaxo does not write the “New means of transport” and “First entry into service” rows today. If you sell a new vehicle to a business with a VAT ID in another EU member state, the rows on these characteristics contain only the first registration and the mileage, each only if it is recorded on the vehicle. Power, if recorded, appears only in the line text.

What Can You Do Now?

Ask your business partners about e-invoices and the VIN, maintain your vehicle data and clarify special cases with your tax advisor.

  1. Clarify your own obligation: Check with your tax advisor whether your total revenue in 2026 exceeds €800,000 and you therefore already have to issue e-invoices for transactions from 2027.
  2. Ask your partners: Find out from dealers, workshops, reconditioners and transport companies when they will start sending you e-invoices.
  3. Request the VIN: Ask them to include the VIN in every invoice relating to a vehicle, ideally following VINvoice.
  4. Maintain your vehicle data: Record the VIN, first registration, condition and mileage in full. Autaxo only assigns automatically when the VIN matches exactly. First registration, condition and mileage only appear in the rows of your sales invoices if they are recorded.
  5. Link the vehicle: For workshop, cost and commission invoices that you issue, link the vehicle in the draft under “Cost allocation” so that the VIN appears in the e-invoice.
  6. Coordinate EU supplies of new vehicles: Clarify with your tax advisor how you state the characteristics under section 1b UStG, especially the first entry into service.
  7. Check the file: The E-Invoice Checker checks XRechnung and ZUGFeRD files technically, but does not check the vehicle rows separately.

What Is the Status of the Initiative?

As of November 3, 2026, VINvoice is a draft for review; version 1.0 is still pending.

  • Changes: Keys, labels and values may still change until version 1.0. Autaxo works with the draft of October 24, 2026, and will have to update its implementation for version 1.0. We will update this article for version 1.0.
  • Have your say: Comments and suggestions are welcome, especially from tax advisory practice on the provisional tax encodings. New characteristics and corrections go through the public GitHub repository; each term page in the vocabulary links directly to a form for proposing a change. The governance page describes the process.
  • Licenses: specification text CC BY 4.0, registry data CC0 1.0, code such as the reference checker Apache 2.0. There are no fees for membership, licensing or certification.
  • Neutrality: Autaxo GmbH sponsors VINvoice, but under the neutrality charter it holds at most one seat among the editors and has no veto. Within twelve months after version 1.0, the repository, domain and name are to pass to a neutral steward.
  • Mustangproject: The open-source project Mustangproject, a Java library for ZUGFeRD, Factur-X and XRechnung, links to VINvoice on its ZUGFeRD page under “Industry recommendations”. This is a reference, not a statement about support in the library.

VINvoice contact: For all questions and enquiries about VINvoice, contact Leonard Niehaus, co-founder and CTO of Autaxo, at Leonard@autaxo.de.

Sources and Suggested Citation

Suggested citation: Niehaus, Leonard; Goßen, Julian Alessio: Vehicle Data in E-Invoices: What Changes from 2027 and What VINvoice Proposes. Autaxo GmbH, 2026. https://autaxo.de/en/blog/vehicle-data-e-invoice-vinvoice/

Note: This article provides general information and does not replace individual tax advice.

About the author Leonard Niehaus, co-founder and CTO of Autaxo

Leonard Niehaus

Co-Founder & CTO

Leonard Niehaus is co-founder and CTO of Autaxo. He leads technical implementation, focusing on software architecture, cloud infrastructure, scaling and security by design. He is the contact at Autaxo for enquiries about the open VINvoice convention.

Leonard is a co-founder and CTO of Autaxo. Autaxo publishes this blog, provides software for vehicle dealers and sponsors the open VINvoice initiative.

About the author Julian Alessio Goßen, co-founder and CEO of Autaxo

Julian Alessio Goßen

Bachelor of Taxation · Founder & CEO

Julian Alessio Goßen gained his first experience in the software industry in the DACH region from 2017 to 2019. Today, he combines experience in tax practice with developing Autaxo. His focus is tax logic and traceable processes in the motor trade, particularly the German §25a margin scheme, EU/export transactions and GoBD record keeping.

Julian is a co-founder and CEO of Autaxo. Autaxo publishes this blog and provides software for vehicle dealers.