Bewirtungsbeleg in English: Germany's Business Meal Receipt

A Bewirtungsbeleg is the supporting record for a business meal in Germany. If you are searching for Bewirtungsbeleg in English, the useful answer is this: it is the document that turns a restaurant meal into a tax-defensible business expense by recording the place, date, participants, business occasion, and amount. German tax guidance limits the income-tax deduction for appropriate, documented business entertainment costs to 70%, and current BMF guidance on restaurant entertainment records requires timely written details for place, date, participants, occasion, and amount.

That is why the restaurant receipt on its own is usually not enough. The receipt proves that food or drinks were purchased, but it does not normally show who attended, why the meal happened, or why the expense was business-related rather than private. The Bewirtungsbeleg adds that missing business context so the cost can be booked correctly and defended later if someone reviews it.

A valid business entertainment record in Germany usually has two parts. First, the restaurant issues the invoice or till receipt with the transaction details. Second, the host adds the tax-relevant information, either on the receipt itself or on a separate supporting form attached to it. In practice, a Bewirtungsbeleg is this two-part proof: the restaurant invoice plus the host's business explanation.

You need a Bewirtungsbeleg when you have a meal receipt in hand and want that expense to hold up in German bookkeeping, expense review, and a later tax check.

The Fields a Valid Bewirtungsbeleg Must Contain

Once you know the receipt alone is not enough, the next question is what finance actually expects to see. The format can vary. What matters is whether the required information is complete, readable, and attached to the restaurant receipt.

Common German field	Plain-English meaning	Usually comes from	What finance needs to see
Name, Anschrift des Restaurants / Bewirtungsbetrieb	Restaurant name and address	Restaurant receipt	The full venue details, so the supplier and place of the meal are identifiable.
Rechnungsdatum / Ausstellungsdatum	Invoice issue date	Restaurant receipt	The date the receipt was issued.
Leistungsdatum / Tag der Bewirtung	Date of service, meaning the actual meal date	Restaurant receipt	The date the meal took place, if different from the invoice date.
Bewirtender / Gastgeber / Leistungsempfaenger	Host or claiming person	Usually added by the host, sometimes printed on the invoice	The full name of the employee, freelancer, or business owner responsible for the meal.
Teilnehmer / bewirtete Personen	Participants	Host supporting record	The names of the guests and enough business context to identify them. Example: Anna Smith, Procurement Manager, ABC GmbH; John Lee, Sales Director, XYZ Ltd; host: Max Mueller.
Anlass der Bewirtung	Business occasion or purpose	Host supporting record	A specific business reason, not a generic label. Good entries: Quarterly pricing review for ABC GmbH supply contract renewal or Kickoff meeting for payroll migration project. Weak entries: business dinner, meeting, networking, discussion.
Verzehrte Speisen und Getraenke / Leistungsbeschreibung	Itemized food and drinks	Restaurant receipt	An itemized description of what was consumed. Finance wants more than a bare lump sum.
Trinkgeld	Tip	Usually added at payment, sometimes printed on receipt	A separately visible tip amount if it was not already included on the receipt.
Gesamtbetrag / Summe / Brutto	Total amount	Restaurant receipt, plus host note if tip was added separately	The final amount paid, with the receipt total and any added tip still understandable.
Unterschrift / Datum / Genehmigung	Signature, date, or approval	Host supporting record or digital workflow	The host-created Eigenbeleg should be signed; in a digital workflow, the signature or approval timing should be recorded and kept with the receipt.

Two fields usually decide whether the record looks solid or weak:

• Participants: Write real names whenever possible, not just client, supplier, or prospect.
• Occasion: Tie the meal to an identifiable project, negotiation, review, proposal, or transaction so a finance reviewer can understand the business reason without asking follow-up questions.

If you're filling one out now, a compact example would look like this:

• Participants: Anna Smith, Procurement Manager, ABC GmbH; John Lee, Sales Director, XYZ Ltd; host: Max Mueller
• Occasion: Lunch to review 2026 supply contract renewal and pricing terms
• Tip: Add it separately if the receipt did not capture it clearly
• Still add beyond the restaurant receipt: the host identity, participant names, business purpose, and any handwritten tip or approval detail

An English Bewirtungsbeleg template is useful only if it captures the same German tax fields while letting the user map them to the labels on the restaurant receipt. The form itself is not what makes the expense defensible; the completed record has to separate receipt data from host-added data and keep both parts attached as one audit-ready German business meal receipt.

Before you submit the expense, ask these yes-or-no questions:

• Does the purpose describe the concrete business matter, not just "meeting" or "discussion"?
• Are all relevant participants named clearly enough to identify the business relationship?
• Is your role as host or company representative obvious?
• Does the restaurant receipt remain linked to the supplementary record?
• Is the receipt sufficiently itemized, rather than just showing a payment total?
• Were the details recorded at the time, instead of guessed afterward?

If any answer is no, fix the file before it enters your accounting workflow. For a broader standard on German tax-audit record requirements, use the same principle here: the file should make sense to someone who was not present at the meal.

---

How the 70% Rule, VAT, and the EUR 250 Threshold Work

For a typical business meal with external participants, German income tax and VAT do not follow the same logic. That is the part many readers mix up first.

Under Section 4(5) EStG, a documented and appropriate business meal is generally 70% deductible as a business expense, while 30% is non-deductible. That means your German business meal tax deduction is limited even when the meal was genuinely business-related. If the cost is excessive, private in nature, or poorly documented, the tax office can challenge more than just the 30% portion.

A practical way to think about the 70% entertainment expense deduction Germany is:

• Income tax side: 70% of the qualifying net entertainment expense reduces taxable profit.
• Income tax side: 30% stays non-deductible.
• Documentation condition: the meal must be business-related, reasonable in amount, and backed by a proper business entertainment receipt Germany file, meaning the restaurant invoice plus the supporting Bewirtungsbeleg details.

VAT is a separate question. Under Section 15 UStG, input VAT, called Vorsteuerabzug, can still be reclaimable on the full qualifying amount if the invoice meets VAT rules and the expense belongs to the business. That means you should not assume the VAT is also limited to 70%. The income-tax restriction and the VAT deduction are separate systems.

A simplified example helps. If a restaurant bill is EUR 119, made up of EUR 100 net and EUR 19 VAT, the result can look like this when the expense qualifies and the VAT is claimable:

• EUR 70 as deductible business expense for income tax
• EUR 30 as non-deductible for income tax
• EUR 19 as reclaimable input VAT

That split is why finance teams usually review both the purpose statement and the invoice quality, not just the total.

The next practical checkpoint is whether the restaurant bill qualifies as a Kleinbetragsrechnung, meaning a small-value invoice. The current threshold is EUR 250. Up to that amount, simplified invoice rules can apply. Above EUR 250, treat the restaurant document more like a formal German VAT invoice and expect details such as:

• the restaurant's tax number or VAT ID
• a unique invoice number
• the name and address of the recipient, meaning the entertaining taxpayer or business
• the service date, if it is not already clear from the invoice date
• a clearer breakdown of net amount, VAT amount, and gross total

For English-speaking readers, the practical rule is simple: if the restaurant bill crosses EUR 250, do not rely on a basic till receipt alone. Ask for a proper invoice made out to your business, then attach it to the Bewirtungsbeleg.

One important edge case is staff-only hospitality. Meals only for your own employees are not the standard external business-entertainment scenario, so they should not automatically be treated as the ordinary 70/30 case. If the meal is only for your own staff, the expense is generally treated as an internal business cost rather than external entertainment, which is why the 70% cap does not apply in the same way. The practical takeaway is simple: use the ordinary Bewirtungsbeleg logic for meals with external business contacts, and classify staff-only meals separately in your expense process.

How to Store the Receipt and Supporting Record for GoBD

For GoBD purposes, a Bewirtungsbeleg is not just the restaurant slip. The merchant receipt and the supplementary business-meal record belong together as one record, whether you scanned both from paper or created part of the file digitally. Digitization is risky when the receipt is captured but the host-added context sits in a separate email, page, or expense comment. Store the restaurant invoice and the Bewirtungsbeleg details as one retrievable record.

A practical GoBD receipt retention Germany workflow looks like this:

1. Capture the original restaurant receipt immediately, before thermal paper fades or the slip is lost.
2. Add the supplementary Bewirtungsbeleg details promptly, especially participants, business purpose, date, place, and host information.
3. Store both parts together in the same expense or document record, either as one combined PDF or as linked files that are always retrieved together.
4. Check that the final stored version is complete and legible, including handwritten additions.
5. Make sure the system can find the record later by supplier, date, amount, employee, or expense claim number.

The standard is straightforward: completeness, legibility, and retrievability. A later reviewer should be able to open one record and see the merchant receipt plus the supporting explanation without hunting through separate folders. That is why many teams align their process with GoBD digital record-keeping rules, then make the Bewirtungsbeleg part of the same indexed finance record rather than a loose attachment.

If you use OCR or automated document capture, do not assume the important context is fully preserved just because the receipt total was read correctly. The risky fields on a Bewirtungsbeleg are often the human-entered ones, such as who attended and why the meal had a business purpose. This is exactly where receipt OCR accuracy and field-capture challenges become relevant. The operational risk is usually missing context, not missing the gross amount.

A clean finance-operations split looks like this:

• Merchant-captured fields: restaurant name, meal date, itemized food and drinks, subtotal, VAT, total, and any tip that is printed on the receipt
• Host-added fields: participants, business purpose, host identity, and any tip or approval detail that was added after payment
• Control step: store both parts together so anyone retrieving the file sees the merchant-side data and the human-entered justification in one record

If the original receipt is missing, an Eigenbeleg can serve as a fallback concept in German bookkeeping, but that is not the normal route for a restaurant entertainment expense. For a Bewirtungsbeleg, you should treat the original restaurant receipt as the primary evidence and the supplementary record as the explanation that makes it tax-defensible.

A useful final test is this: if a third party could look at your stored file and reconstruct who was entertained, why, when, where, and for how much, you are close to an audit-ready standard.