Putting airport transfers on the company account: invoices done right
An assistant in Frankfurt books a transfer for a visiting client from Zurich. The client never sees an invoice, never touches a payment app, and flies home without thinking about it again. Three weeks later, finance is trying to match a stray receipt to a cost centre nobody remembers assigning. This is the unglamorous half of transfers on the company account: not the ride itself, but the paperwork trail behind it — who books, who pays, and what the invoice needs to say so the accounting team doesn’t have to chase it down later. For office managers, travel coordinators and finance teams who arrange Frankfurt Airport transfers for colleagues and guests, the mechanics matter more than the legroom.
Three booking patterns, one paper trail
In practice, company transfer bookings tend to fall into one of three patterns. The self-booker pays privately and files the receipt through expense software afterwards — simple, but it multiplies the number of invoices finance has to process one by one. The company account is the opposite: payment is set up centrally with the transfer provider, and individual rides are confirmed rather than paid for each time. Third-party booking covers guests — a client, a candidate, a visiting auditor — where the person in the car never sees a bill because it’s billed straight to the host company. All three break down at the same point: without a flight number, the correct invoice recipient, and a traceable cost-centre reference at the time of booking, a five-minute reservation turns into a week of email follow-ups. Anyone booking regularly on behalf of others should confirm upfront whether their organisation already runs a standing account with the transfer provider or settles every ride individually — that answer determines what information the booking form actually needs.
What a proper German VAT invoice must show
For input VAT recovery in Germany, form matters more than intent. A full invoice under §14 UStG (the German VAT Act) needs: the complete name and address of both the supplying business and the invoice recipient, the supplier’s tax number or VAT ID, the issue date, a sequential invoice number, the quantity and nature of the service (for a transfer: route, date, and ideally the flight number as proof of service), the date the service was performed, the net amount broken down by tax rate, and the applicable VAT rate and amount. Miss one line item and a tax office can, in principle, disallow the input VAT deduction — a familiar problem with handwritten taxi receipts that show only a date and a total. For any finance team handling transfers regularly, invoice discipline becomes part of choosing a provider: does a complete invoice with every required field arrive automatically, or does someone have to request it after the fact?
Small-value invoices, full invoices, and the e-invoicing shift
Not every transfer needs the full list. Under §33 UStDV, a simplified small-value invoice is sufficient up to a gross amount of 250 euros, with far fewer mandatory fields. Most short Frankfurt-area hops fall under that simplification; longer routes or larger group vehicles usually don’t.
| Feature | Small-value invoice (up to €250 gross) | Full invoice (above €250 gross) |
|---|---|---|
| Legal basis | §33 UStDV | §14 UStG |
| Recipient name/address | not required | required |
| Sequential invoice number | not required | required |
| Tax rate vs. tax amount | tax rate alone is enough | rate and amount shown separately |
| Date of service | required | required |
Delivery itself is changing in parallel. Since 1 January 2025, every business in Germany has been required to be able to receive electronic invoices in structured format. On the sending side, a transition period still applies: paper and PDF invoices for domestic B2B transactions from 2025 and 2026 remain valid without the recipient’s consent through the end of 2026, and PDF invoices beyond that require explicit consent. From 2027, mandatory e-invoicing phases in for larger businesses; from 2028, it applies to essentially all domestic B2B invoices. Companies running transfers through a standing account should ask their provider when structured e-invoices become available — the rollout is staged, not a single cutover date.
Collective invoicing and cost-centre tagging
For organisations with recurring transfer needs — client meetings, candidate interviews, standing roadshow bookings — a single collective invoice almost always beats a stack of individual receipts. Every ride in a given month runs against a company account, and at month’s end one invoice lists every leg, ideally with reference fields for cost centre, project code or department tag already attached. That does more than lighten the accounting workload: it makes internal allocation cleaner, because nobody has to guess in arrears whether a ride belonged to Client A or an internal conference. The practical detail that matters: the cost-centre reference has to be entered at the time of booking, not reconstructed later during invoice review — after the fact, it’s rarely possible to pin down with confidence.
Where transfers sit in a travel policy
Many corporate travel policies separate “taxi/public transport” from “chauffeured car service” without making the line especially clear to the traveller booking it. A pre-booked, fixed-price airport transfer usually sits in the same policy bracket as a taxi, but unlike a street taxi it can be budgeted and approved before the trip starts — useful for organisations that require pre-trip cost sign-off. For days built around several stops rather than one pickup — investor meetings, plant visits across the Rhine-Main region — some policies carve out separate rules for hourly bookings; the cost logic behind all-day chauffeur bookings works differently from a single point-to-point fare and is worth checking against the policy text directly. Anyone booking on behalf of a guest should also confirm whether the invoice is meant to land on the host company or the guest personally — with a standing chauffeur-driven Frankfurt account, that routing can be set once at booking time so nobody’s personal card gets charged and then has to be reimbursed.
Per diems and transfer costs are two separate lines
A recurring mix-up in expense reports: the transfer gets folded into the meal allowance line, even though the two run on entirely separate legal footing. Germany’s domestic per diem for business travel (Verpflegungsmehraufwand) is unchanged at 28 euros for a full 24-hour day away, and 14 euros for more than eight hours away as well as for the arrival and departure days of a multi-day trip — it covers meals, not transport. The airport transfer is its own line item, booked and receipted as a travel/transport cost, independent of whether a per diem is also claimed for the same day. Combining both into a single expense-report line tends to invite questions in an audit; keeping fare and per diem separate from the start, even when they belong to the same trip, holds up better.
For the next trip, it’s usually simpler to get a fixed price in advance and attach the invoice recipient and cost-centre reference at booking time, rather than sorting it out after the ride.
Frequently asked questions
Does a simple receipt cover input VAT recovery on a transfer?
A simplified small-value invoice under §33 UStDV is sufficient only up to a gross amount of 250 euros. Above that threshold, a full invoice with every field required under §14 UStG is necessary, or the input VAT deduction can be disallowed on review.
Can the invoice go directly to the company instead of the traveller?
That’s the standard setup with a company account: the business name and address are entered as the invoice recipient at the time of booking, regardless of who actually rides in the car. The same applies when booking for a client or candidate who never handles payment personally.
Will transfer invoices have to be e-invoices soon?
Businesses in Germany have already been required to be able to receive structured electronic invoices since the start of 2025. A transition period for sending paper or PDF invoices runs through the end of 2026, mandatory e-invoicing phases in from 2027 based on company size, and applies to essentially all domestic B2B invoices from 2028.
Can a cost centre be added to an invoice after it’s already been issued?
A cost-centre or project reference is best entered at the time of booking, since it typically becomes part of the service description on the invoice itself. Changing it after an invoice has already been issued usually requires a formal correction rather than a simple edit.
What happens when several colleagues share the same transfer?
Shared rides can usually be booked against one shared cost centre or project code rather than a single traveller’s name. It’s more reliable to set that up at booking time than to split an already-issued invoice retroactively.
