How to Write a Legally Compliant Invoice in Germany

Send a German invoice that is compliant and payment-safe on the first try#

The goal is simple: send a Rechnung that meets German requirements and is easy to review and pay. Use the same order every time: legal minimum fields first, payment terms second, pre-send risk checks third. Treat it as a defensive sequence, not a design template or a complete legal checklist for every case.

1. Step 1: Lock legal minimum fields first.

Include core compliance fields upfront, especially a unique invoice number and an invoice issue date. Keep sender, recipient, and tax details consistent and easy to verify across invoices. For cross-border work, invoice under your home-country rules while still meeting EU and German requirements.

1. Step 2: Add payment terms that are clear and executable.

State due date, payment terms, and payment instructions in plain language.

1. Step 3: Run a separate pre-send risk check.

Before sending, verify completeness and consistency across the invoice. Confirm the document is both compliant and operationally clear, then keep support records tied to the same invoice number.

If you skip this order, non-compliance risk rises and issues can surface after submission, including delays, penalties, or tax complications. Keep the sequence strict even for smaller invoice values so your quality level does not drift from one cycle to the next.

Timing also matters. B2G e-invoicing has been mandatory since November 27, 2020, and businesses have had to be able to receive B2B e-invoices since January 1, 2025. Issuing obligations tighten in stages, including a 2027 threshold for businesses above EUR 800,000, with broader issuing requirements by 2028.

What to prepare before you draft the Rechnung#

Preparation is the main control point. When your inputs are complete, drafting is faster and lower risk. A Rechnung is both a business record and a payment request, so inconsistent details can create avoidable delays.

If the supply is taxable in Germany, German invoicing rules apply. There is no single required template, so complete and consistent information matters more than layout.

Before you draft the first line item, gather the contract, any purchase order instructions, and your prior accepted invoice for the same client when available. That quick comparison often catches naming drift, account-detail drift, and date-label drift before they turn into revision work.

1. Step 1: Assemble your legal identity set.

Put your full legal name, business address, and relevant tax/VAT identifiers in one source note. Keep this block consistent with your contract and prior accepted invoices. If details changed recently, update your source note first and only then start drafting.

1. Step 2: Confirm client billing inputs before drafting line items.

Collect the invoice recipient legal name, billing address, and purchase order only when required. Check those details against the contract counterparty and billing instructions. If the contract and billing portal show different recipient wording, resolve that mismatch before you issue anything.

1. Step 3: Prepare service support for the billed period.

Gather scope notes, delivery proof, and agreed rate basis for each planned line item. Keep records organized so each amount and service period is easy to defend if questioned. A simple folder split by invoice number and service period is enough as long as it is consistent.

1. Step 4: Lock numbering and filing before first draft.

Set a sequential invoice-number method and define where final invoices and support records are stored. Treat invoice issue date and service date or service period as separate checklist fields, and confirm the next invoice number is unique and retrievable. Do this before draft creation, not at send time, so you are not assigning numbers under pressure.

Step 1 Lock party identities and tax identifiers#

Lock legal names, addresses, and the tax identifier you plan to use before you draft amounts. That alone can reduce avoidable review issues.

1. Use exact legal names and addresses for both parties.

Use your registered business details for the sender and contract counterparty details for the recipient. Do not replace legal entity names with team names, nicknames, or brand labels.

1. Use the tax identifier you have confirmed for this invoice case, and keep that choice consistent.

Germany uses multiple tax numbers (Steuernummer, USt-IdNr, W-IdNr), so choose the identifier you have confirmed for the case and repeat that pattern for similar invoices. If you are unsure which identifier applies, pause and confirm before issuing.

1. Run a pre-send AP checkpoint.

Confirm the recipient legal entity, billing address format, and any purchase order reference in the client instructions are consistent with the contract and billing details.

1. Treat entity mismatch as a high-risk issue.

If the invoice recipient does not match the contract counterparty, correct it before sending so processing is less likely to be delayed.

A practical check is to read the sender and recipient blocks out loud against the contract header and billing instructions. If either one sounds different, stop and fix it. Identity mismatches are usually easier to correct before send than after routing starts.

Step 2 Define service scope and date logic so disputes fail early#

Disputes often start with unclear timing or vague scope. Make the service date or service period and line-item scope explicit so reviewers can confirm what was delivered and when.

1. Separate dates and label them clearly.

Show the invoice issue date and the service date or service period as distinct fields where relevant. Avoid a single generic date field.

1. Use one clear service period for bundled monthly work.

If work is billed monthly, state one period and keep line items consistent with it. Tie each line item to a deliverable or workstream so scope is easy to validate.

1. Prefer specific line-item descriptions over vague labels.

Replace broad text like consulting services with concrete descriptions of work delivered. This is especially helpful when cross-border reviews involve multiple entities with separate tax, banking, and vendor operations.

1. Run a traceability check before issuing.

For each line item, confirm it maps to agreed scope, a milestone note, or an accepted deliverable. If you cannot trace a line quickly, rewrite it before sending.

For one-off work, a single service date can be enough. For bundled work, a service period is often clearer. Use whichever makes the delivery window obvious to someone who did not work on the project, then keep that wording consistent across the invoice.

Step 3 Build amounts that reconcile on first review#

If totals cannot be reproduced from line items, approval can slow down. Build the math so a reviewer can recalculate it in one pass.

1. Structure each line item so it can be recalculated.

Show quantity or scope unit, unit basis, and line subtotal. For fixed-fee work, label the basis in plain language so reviewers can map it to agreed terms.

1. Make the totals block mirror the line math.

Present net amount, VAT amount, and gross amount in one summary block. Run this control before issuing: line-item subtotals = net amount, and net amount + VAT amount = gross amount.

1. State VAT treatment explicitly.

If Value Added Tax (VAT) applies, show VAT amount clearly. If VAT does not apply, make that status explicit instead of leaving the VAT field blank.

1. Run a reconciliation check before sending.

Where commercial records exist, compare what you bill to what was ordered, received, and paid so you catch mismatches early. In self-billing cases, keep VAT details explicit because the customer issues the invoice on behalf of the supplier.

If totals are correct but labels are unclear, review can still stall. Keep line labels and totals labels aligned so the reviewer can map each subtotal to the summary block without guessing.

Step 4 Set payment terms that protect cash flow without slowing approval#

Set payment terms so AP can execute quickly, then define late-payment follow-up in advance.

1. State terms, due date, and payment details together in plain language.

Use consistent labels such as due date, account holder, and payment reference so payment can be executed with less back-and-forth.

1. Match wording strength to approval risk.

Use clear, neutral language that matches your agreement so AP can review and process the invoice without extra interpretation.

1. Add one clear escalation clause for late payment.

Document the sequence: reminder, request for remittance date, and escalation to the agreed finance contact.

1. Keep execution records tied to the invoice number.

If you use payment links, keep them clearly tied to the invoice and keep confirmation records mapped to the exact invoice number. If self-billing applies, confirm a written agreement and current tax details, and update the agreement if VAT numbers change.

Payment wording should be easy to execute, not dramatic. Keeping due date, account data, and payment reference in one place can reduce avoidable delays.

Germany's move to structured e-invoicing is stated to begin on 1 January 2025. Structured e-invoices (such as XML or EDI) can reduce manual errors and speed invoice processing, so keep due date, amount, and payment reference consistent across every version you send.

What changes when you invoice a cross-border client#

For cross-border invoices, keep the same German compliance approach and adapt what changes by case: VAT wording, electronic format, and recipient details.

A common risk in international cases is small differences across the contract, invoice, PO, and remittance details. Those gaps can trigger manual checks, so tighten the joins before you send.

Step 1 Lock the commercial reference set before issue#

Before sending, lock the commercial reference set: purchase order when required, payment terms, and bank account details. Keep these details consistent across contract, invoice, and remittance instructions so the client can route payment with less rework.

If a purchase order is required, make sure the PO on the invoice matches the client legal entity and billing record. Use agreed payment-term wording and a stable bank-detail format for that entity.

If the client has multiple legal entities, confirm the exact billed entity each cycle instead of assuming it is unchanged from the last invoice. That check can reduce rejected invoices with otherwise correct amounts.

Step 2 Adapt VAT and e-invoice handling by transaction case#

Use EU VAT invoicing rules as the baseline, then tailor by transaction context. VAT obligations can differ by where you sell and whether the transaction is for goods or services, so avoid copying wording from another client without checking fit.

For most B2B supplies, an invoice is required. Electronic invoices are equivalent to paper invoices. Businesses may issue electronic invoices when the recipient accepts them. In the cited Germany timeline, B2B e-invoicing implementation starts on January 1, 2025 and is mandatory for all B2B transactions by January 1, 2028. In Germany B2G, e-invoicing has been mandatory since April 18, 2020, and the cited guidance notes Peppol accessibility. If VAT treatment is still unclear, review your tax notes before issuing.

Keep your VAT statement, totals block, and any structured payload aligned. If those versions conflict, AP may pause payment while tax details are rechecked.

Step 3 Run a pre-send international checkpoint#

Use a short pre-send check for international cases:

• Confirm the recipient legal entity matches the contracting party and billing record.
• State a clear service period.
• Keep tax identifier usage consistent for the case (tax ID or VAT registration number as required).
• Verify PO, payment terms, and bank account details match across invoice and payment instructions.
• Confirm the recipient accepts the electronic format you plan to send.

If legal entity or tax identifier details conflict, pause and correct before issuing.

A simple decision rule helps: if two documents disagree on entity, tax identifier, or payment details, the invoice is not ready. Fix the mismatch first, then send once.

Contract terms your invoice should align with before you send#

Before sending, run one consistency check: the invoice should match the signed agreement and your support records so approval is not delayed by avoidable mismatches.

This section is about defensibility, not legal theory. When the invoice text and your support records point in the same direction, disputes are easier to contain and faster to resolve.

Step 1 Align timing and handoff details#

For progress invoicing, make sure each billed line item uses a clear service date or service period. Keep invoice issue date separate from service timing so reviewers can verify what was delivered, when, and when it was billed.

When handoff spans multiple dates, keep the billing period wording consistent across related line items. Mixed date language in the same invoice creates avoidable questions.

Step 2 Keep scope wording factual#

Keep invoice descriptions focused on delivered work and avoid broad promises. Short, factual line items are easier to approve and harder to misread.

Use delivery language that maps to work already completed. If a description reads like marketing copy, rewrite it as a concrete service statement.

Step 3 Verify reimbursables with proof#

For reimbursable or third-party costs, keep approval evidence and underlying documents with the invoice record before billing. The same time-and-proof discipline used in progress invoicing helps prevent disputes on pass-through charges.

If a reimbursable line is challenged, you should be able to produce the approval evidence and underlying document quickly. Slow evidence retrieval can delay payment even when the charge is valid.

Step 4 Keep dispute-ready records and valid format#

Keep one clean record package: invoice number, invoice issue date, service date or service period, and line-item approvals. Also confirm that the sent format is tracked. In Germany's B2B e-invoicing rollout, businesses must be able to receive structured e-invoices from January 1, 2025, with full B2B issuance required by 2028. Valid e-invoices are structured EN 16931 formats such as XRechnung or ZUGFeRD, not simple PDF or Word files.

A dispute-ready package should be easy for a third party to read without extra explanation. That is the standard that keeps follow-up predictable when a payment is questioned.

Step 5 Run a pre-send compliance and risk check#

Use a two-pass review before sending: legal completeness first, payment operability second. If either pass fails, pause and fix it before release.

1. Required fields check (legal completeness). Confirm core invoice fields are present and clear (for example: invoice number, issue date, service date or service period, recipient details, tax identifier, and VAT treatment). Verify consistency across your Rechnung and any structured version, and check against your current Germany VAT invoicing requirements.

2. Payment execution check (operability). Confirm due date, payment terms, bank account details, and purchase order alignment. Make sure these details do not conflict across sections.

3. Evidence check (defensibility). Ensure each line item maps to proof of work and approved scope, then archive that evidence with the final Rechnung PDF and any structured e-invoice payload you use.

4. Control check (records and totals). Verify invoice number sequencing is intact in your records, and reconcile totals from line items through gross amount before send.

Run legal completeness and payment operability as separate passes on purpose. The first pass asks whether the invoice meets your current invoicing requirements. The second asks whether AP can execute payment without clarification. Combining both into one quick read often misses one side.

This check matters more as e-invoicing obligations evolve. The stated ViDA timeline says adoption on March 11, 2025, with entry into force in April 2025. It also states cross-border B2B e-invoicing mandatory from July 1, 2030, and legacy national alignment by January 1, 2035. In Germany, keep this process compatible with structured formats such as XRechnung. Related: A Deep Dive into Germany's Tax System for Freelancers.

Common invoice failures and how to recover without creating a bigger mess#

When an invoice fails, recover in a controlled, traceable way: fix the specific error, link the correction to the original, and keep both records clean. Move quickly, but do not send partial fixes.

One AP benchmark reports that 86% of teams still rely on manual invoice processing, which means small inconsistencies may stall routing in manual workflows. Poor handling can also lead to late payment penalties and reputational damage. In electronic submission contexts such as FACE, sending errors can also affect financial management and commercial relationships.

Treat recovery as a single correction cycle, not a stream of edits. Multiple partial resends can create version confusion and leave AP unsure which document is current.

Step 1 Repair a broken invoice number sequence#

If an invoice number is missing, duplicated, or out of sequence, issue a corrected document with clear linkage to the original. Keep both records in your audit trail with a short note on what changed and why.

When you send the correction note, name both invoice numbers in the subject line or first sentence. That can make AP routing cleaner and reduce follow-up.

Step 2 Reissue for a wrong invoice recipient#

If recipient legal name or address is wrong, reissue with corrected details and tell AP which version is current. Keep the message brief and factual so the correction is easy to process.

Do not combine this fix with unrelated rewrites. Correct the recipient data, keep the rest stable, and resend one clean version.

Step 3 Resolve issue-date and service-period confusion#

If date fields are unclear, state invoice issue date and service period separately and clearly. Update line-item notes so they match corrected service-period language.

Date corrections should read the same way across all affected lines. Mixed wording after correction can trigger another review loop.

Step 4 Correct VAT treatment and send a concise AP note#

If VAT treatment is wrong, correct the VAT field and include a plain reason statement on the revised invoice. In your AP note, identify original invoice number, corrected invoice number, and the exact field corrected.

Use this resend check before release:

• corrected invoice linked to the original record
• invoice number and issue date verified in your register
• service period wording aligned with line items
• recipient legal details rechecked
• VAT treatment and reason statement visible and consistent

If any point is unclear, pause and fix it before reissuing. One complete correction is usually cleaner than multiple partial resends. After reissue, archive the original, the corrected invoice, and the correction note together so the correction history stays in one package.

Want a quick next step? Try the SOW generator.

Copy and paste final invoice checklist#

Use this as your final pre-send gate: if one item fails, fix it and rerun the full list before sending. Run it in two quick passes: first legal and tax completeness, then payment operability and evidence readiness.

1. Identities and tax IDs are complete.

Confirm supplier and customer legal names and full addresses, and include your Steuernummer or USt-IdNr. as applicable.

1. Core invoice fields are complete.

Verify a unique, sequential invoice number and that all other required invoice details are present. If the invoice is <= EUR 250 gross, only use the small-amount format when that threshold is actually met.

1. Amounts and VAT treatment are complete.

Recheck totals and VAT arithmetic. If VAT-registered, show VAT rate(s) and VAT amount(s); if using Kleinunternehmer treatment, issue without VAT and include the short explanatory note. One missing mandatory detail can invalidate the customer's input tax deduction.

1. Payment details are complete and unambiguous.

Make due date and bank details visible in one block, and confirm they are consistent across the final invoice version.

1. Risk and compliance checks are complete.

Confirm format readiness for the e-invoicing transition timeline (2025 move toward structured domestic B2B e-invoices; Jan 2025-Dec 2026 PDF still possible with recipient agreement; from 1 Jan 2027 mandatory issuance for businesses above EUR 800k annual turnover; from 1 Jan 2028 for remaining businesses), then archive records in a GoBD-aligned set and retain invoices for 8 years.

Keep this checklist next to your draft while editing, then run it once more on the final version you actually send. Many errors happen because the checklist is run on an earlier draft, not on the release copy.

Final takeaway#

For every Rechnung, keep the order strict: complete the legal core, make payment handling clear, then run a final pre-send check. That sequence keeps the invoice usable as both a payment request and a tax record while reducing correction risk.

1. Complete the legal core first. Start with mandatory invoice information under Section 14 of the VAT Act, then verify concrete completeness points: the date goods or services were delivered, plus clear quantity and description for each service line.

2. Treat it as a payment instrument, not admin paperwork. A Rechnung is a time-stamped payment request that creates an account receivable and stores income information for tax and accounting. Keep payment and VAT wording clear and consistent, especially in cross-border cases where VAT compliance is generally more burdensome than domestic compliance.

3. Protect the correction trail. Do not edit an issued invoice in place. If it is wrong, cancel it and issue a corrected invoice. Incorrect invoices can lead to service cancellation and tax-office problems.

Keep two timeline controls in your process: be able to process B2B e-invoices from January 1, 2025, and retain invoices for 8 years as of 2025. If you want one memory line for how to write a German invoice, use this: verify legal completeness, make payment handling unambiguous, and keep a defensible correction trail.

Before your next billing cycle, take one practical step: copy the checklist section into your draft review routine and run it on the exact file you send. Consistent execution is what turns compliance from stress into routine.