How to Invoice a German GmbH Compliantly

Start here and avoid the two invoice failures that cost freelancers money#

If you want a Rechnung that gets paid without back-and-forth, treat first-pass accuracy as a cash flow task, not admin cleanup. Two failures are common and expensive: sending a duplicate or conflicting invoice, and invoicing while scope or acceptance is still disputed.

Before you start#

Step 1. Set the standard for this article. This guide is for freelancers doing B2B service work. The goal is practical, not academic. You should be able to send an invoice that is clear enough to pass AP review and documented well enough to answer follow-up questions.

That scope matters. Public summaries help, but they do not settle every edge case. When key billing details are not clear from your facts, the conservative move is to stop, verify, and issue once rather than fix it later after the client has already logged or paid the wrong version.

Step 2. Prevent the first expensive failure: duplicate invoicing. Duplicate invoicing is not a minor clerical slip. It is a direct time-and-money risk, and it often starts with weak checks and version control. For freelancers, it tends to show up in three avoidable ways: you resend an edited PDF without a clean status trail, you issue a replacement invoice without clearly withdrawing the first one, or you bill the same milestone twice because your email, contract, and invoice records do not match.

Your first checkpoint is basic: one final invoice file, one invoice number, one send channel, and one timestamped record of what was sent. If you revise anything after sending, mark the old version as withdrawn in your records before the new one leaves your outbox. If you cannot prove which version is current, payment can get delayed.

Step 3. Prevent the second failure: invoice disputes that should have been resolved earlier. Ignored invoice disputes cost time and money too. If the buyer thinks the service description, dates, amount, or acceptance status does not match the deal, the invoice can become the point where a contract argument starts.

Do not send first and explain later. Before you bill, make sure you can point to the evidence pack behind the invoice:

• the signed scope or statement of work
• the accepted deliverable or milestone approval
• the agreed fee and currency
• the exact legal entity name of the buyer you are billing

That frames the rest of this guide. You will leave with a fill-ready invoice structure, a practical tax-decision path, dispute-control wording that helps prevent avoidable fights, and a copy-paste pre-send checklist. If you need deeper field-by-field drafting help, use How to Write a Legally Compliant Invoice in Germany alongside this guide. If you want a deeper dive, read Germany Freelance Visa: A Step-by-Step Application Guide.

What to prepare before you draft the invoice#

Before you draft, line up four things: proof the invoice is due, exact party and tax identifiers, your tax treatment lane, and one clean audit trail.

Step 1. Build the evidence pack. Collect the records that support issuing the invoice: signed scope or SOW, acceptance of the deliverable or milestone, and the agreed fee and currency. Verify the buyer's legal contract name exactly, including German GmbH where applicable.

Step 2. Confirm the identity fields exactly as you will print them. Lock the seller and buyer details before you write line items. Include your business details, the client's billing details, and any shared Umsatzsteuer-ID or other tax identifier, and keep wording consistent across your records.

Step 3. Choose the tax lane before you write. Decide whether you are issuing a standard B2B invoice, a Kleinunternehmer case under § 19 UStG, or an edge case for tax-advisor review. If you are unsure whether the supply is taxable in Germany, pause and verify before issuing.

Step 4. Set up one audit trail. Use one system of record for the final PDF, supporting documents, invoice number log, send timestamp, and payment status. An invoice is both a payment request and a business record, so your file history should make version status clear. This pairs well with our guide on A Guide to the German 'Künstlersozialkasse' (KSK) for Freelance Artists.

Build the invoice fields a German GmbH AP team expects#

Use one consistent invoice structure each time: include all required content, then add payment-routing details that make processing easier.

German rules require complete seller and recipient name/address details, an issue date, a uniquely assigned consecutive invoice number, and the service or delivery date. Your amount block should clearly show net amount, tax amount, and total, plus the applicable tax rate or exemption note. German law does not require a fixed visual layout, so keep yours stable and easy for your client's AP team to scan.

Step 1. Arrange the fields in one consistent order#

A practical default order is: seller identity, buyer identity, invoice number, issue date, service period/date, service description, net/tax/total block, then payment terms.

For service work, state the service date or period explicitly. If your contract says "Strategy retainer for February 2026," print that period on the invoice instead of relying on the issue date alone.

Step 2. Verify the highest-risk fields before sending#

Run these checks before you send:

1. Legal-name match: buyer name and address match the contract party exactly, including the GmbH suffix where applicable.
2. Math tie-out: line items, subtotal, tax, and total reconcile after any edits.
3. Deliverable wording: line items map to the agreed milestone, period, or accepted output in your scope documents.

Step 3. Add payment-routing details to reduce avoidable back-and-forth#

Payment instructions are not the same as legal minimums, but they help AP route and settle invoices. Include due date, bank details, transfer reference, and a remittance contact. Federal e-invoicing guidance also maps payment terms and bank details into structured processing fields, which is a strong operational signal to include them clearly.

Do not apply simplified small-amount invoice treatment unless the total invoice is at or below 250 Euro. You might also find this useful: A Deep Dive into the German Trade Tax ('Gewerbesteuer') for Freelancers.

Decide VAT treatment before you send#

Decide your VAT treatment before you calculate totals, then keep every tax field consistent with that choice. If you are using Kleinunternehmer treatment, do not show or charge Umsatzsteuer and include the § 19 UStG note. Otherwise, use your normal VAT setup and keep the tax block aligned end to end.

Step 1. Choose the tax basis before you build the amount block#

Set the tax basis first, because tax contradictions are harder to fix than wording issues.

For a Kleinunternehmer invoice, use: "Gemäß § 19 Abs. 1 UStG wird Umsatzsteuer nicht berechnet." If you use that basis, your tax rate field, tax amount field, and total must all match it. Do not show VAT in one field and try to override it with a note elsewhere.

Before sending, run one manual check on just the money section and tax note:

• If using § 19 UStG: net and total should match, no VAT amount shown, and the § 19 wording included.
• If using your normal VAT setup: rate, tax amount, and total should reconcile consistently across the invoice.

If your template predates 1. Januar 2025, review any old Kleinunternehmer wording before reuse, because § 19 UStG was revised with effect from 1 January 2025.

Step 2. Avoid the error that can still create tax exposure#

If you show tax when you should not, that shown amount can still be owed under § 14c Abs. 1 UStG (unrichtiger Steuerausweis).

If you are in the Kleinunternehmer lane, treat visible tax fields as high-risk until checked. Common failure patterns are reused templates, software defaults, or manual edits that leave a tax line behind.

If you are not using Kleinunternehmer treatment, present your normal VAT setup clearly and consistently. Do not guess when a special case is not confirmed.

Step 3. Pause when cross-border place of supply is not obvious#

For B2B services, § 3a UStG gives a general starting rule: place of supply is where the business customer operates. But EU VAT place-of-taxation rules vary by transaction type and include exceptions.

Use that as your decision rule: if cross-border treatment is not clearly confirmed, pause before issuing. Verify the service type, service description, and customer location, then confirm treatment with your accountant or tax advisor before finalizing the invoice. Correcting after payment is usually slower than verifying first. For a step-by-step walkthrough, see How to Get a German Tax ID as a Freelancer Without Mix-Ups.

Add contract protections that stop scope and payment fights early#

Anchor each invoice to signed terms before you send it. If acceptance triggers, milestone names, or extra-work approval rules are still informal, pause billing until they are written into the Agreement.

Step 1. Match invoice lines to the signed Agreement#

In the cited MSA structure, the Agreement can include the MSA plus referenced WOs, SOWs, amendments, and supplements. Reflect that structure on the invoice, or in your sending note, by naming the controlling MSA and the exact WO/SOW version being billed.

Keep wording aligned with the signed text:

• Use the same milestone and acceptance language as the contract.
• Bill extra work only through the written change path required in the signed terms.
• Treat written acknowledgment or confirmation as the control point for scope and effect.

Before sending, check each billable line against the signed document titles and trigger language.

Step 2. Put termination billing logic in writing before the relationship turns#

Do not let the final invoice create new rules. If termination is in play, make sure the contract terms already state what is billable at termination, what written support is required, and how final payment timing is handled, then have the invoice point back to those terms.

Attach the records your signed terms rely on, such as written acceptance or written scope-change approvals. If those written hooks are missing, pause and fix the paperwork before issuing a final invoice.

Step 3. Keep invoice disputes from reopening bigger risk arguments#

If your MSA includes Limitation of Liability and Indemnification, keep the invoice tied to the governing Agreement or SOW so the invoice is not treated as a new risk negotiation. You do not need to restate those clauses on the Rechnung; you do need a clear cross-reference trail.

Use written assent for any late language changes. The cited terms treat assent as concrete actions (for example, signing or clicking accept), and they reject deviating buyer terms unless explicitly agreed in writing. Verbal approval is a payment-delay risk. Related reading: Freiberufler vs Gewerbetreibender for German Freelancers.

Lock enforcement terms before the first invoice#

Before you send the next invoice, make sure one signed document set clearly controls how disputes are handled. Do not assume email history will carry enforcement if a payment issue starts.

Step 1. Confirm the enforcement clause in the signed contract#

Work from the controlling documents, not inbox fragments: MSA, SOW, order confirmation, and any addendum or amendment the contract treats as controlling. Your checkpoint: both sides accepted one written set of terms that governs dispute handling, notice mechanics, and which terms control. If the buyer sent separate terms, treat them as non-binding unless they were expressly agreed in writing.

Step 2. Mirror the agreed dispute path in your invoice terms#

If your signed agreement already includes dispute-handling steps or timing, mirror that wording in the invoice note or footer. Keep it short and consistent with the contract language. The goal is alignment, not new rights: your invoice should point back to the same order or contract terms that already govern billing and notices.

Step 3. Issue a short addendum if the clause is missing#

If the enforcement path is not clear in signed terms, use a short addendum before the next invoice. Do not rely on informal "agreed by email" unless your contract explicitly allows that amendment method. Use a brief signed addendum so both sides are working from the same written process. We covered related documentation discipline in A Guide to the German 'Impressum' requirement for websites.

Send, track, and reconcile without losing traceability#

After you issue the invoice, run one traceable workflow end to end: one final record, one provable send event, and one payment reference you can reconcile.

Step 1. Finalize one authoritative invoice record. Use one issuance channel per Rechnung, and treat the finalized version as the only live document. Do not send drafts from multiple tools or resend edited PDFs under the same number. In Stripe Invoicing, finalization adds an invoice number, locks certain fields, and creates both a hosted payment URL and a PDF link. Your checkpoint: one final document or platform record, one invoice number, one payment reference.

Step 2. Send it with receipt evidence. For disputes, you generally need proof that invoices and reminders were received, and sending an email alone does not prove receipt. Use a send method that leaves a receipt trail, then store the send timestamp, recipient address or portal, and any AP acknowledgment. If a client portal is required, save the submission confirmation with the invoice record.

Step 3. Track status in order. Follow the sequence: confirm receipt, monitor the due-date window, send reminders only after the deadline passes, then escalate only if reminders get no response. If you use Stripe, track against its lifecycle states (draft, open, paid, uncollectible, void). If you do not, mirror the same clear state model internally so "sent," "due," and "in dispute" are never mixed up.

Step 4. Reconcile payment before close-out. When payment arrives, verify three items before closing: that the amount matches, the reference matches, and close-out evidence is stored with the original invoice. If you use a platform, keep status history, payment confirmation, and accounting exports (for example CSV) as audit artifacts. If amount or reference does not match, keep the invoice open internally until the payment is tied to the correct record.

Common rejection points and how to recover fast#

When AP rejects the invoice itself, the fastest fix is a clean correction trail: withdraw or cancel the bad version, then issue one clear replacement that references the earlier record.

Step 1. Fix party-identity errors first. If the buyer name is wrong, stop and correct it before anything else. Full name and address of seller and buyer are core invoice fields, so the wrong German GmbH entity can block booking. Check the legal entity across the contract party, billing instructions or portal profile, and the invoice header before reissuing.

Do not resend an edited PDF under the same invoice ID. Duplicate IDs are a known AP-network rejection trigger. Cancel or withdraw the incorrect invoice, then issue a corrected invoice with a unique number that clearly references the original invoice number and date (for example: "Corrected invoice replacing invoice 2026-014 dated 14.03.2026; prior invoice withdrawn.").

Step 2. Cancel and reissue when VAT/Umsatzsteuer treatment is wrong. If tax text, VAT amount, or totals are wrong, treat it as a substantive error. Use a cancel-and-recreate path with corrected tax treatment and totals, plus a written acknowledgment trail showing which version is valid. The operating check is simple: only one invoice should remain payable.

For structured e-invoices, include the preceding invoice reference in BG-3. Where document typing applies, use BT-3 code 384 for a corrected invoice and BT-3 code 381 for a credit note.

Step 3. Resolve scope disputes with evidence mapping. If a line item is disputed, attach acceptance evidence and map each line item to the agreed deliverable and service period. This usually clears approval faster than broad wording changes because AP can route a concrete package for sign-off.

Step 4. Confirm the buyer's actual e-invoicing requirement before format conversion. For domestic B2B transactions in Germany, electronic invoicing is mandatory from 1 January 2025 (with transition rules), and a compliant e-invoice must be structured and machine-processable. The format must follow EN 16931 or an allowed agreed alternative.

Do not assume every buyer wants the same channel. Confirm the buyer's accepted format and delivery route before producing XRechnung or sending via Peppol. Need the full breakdown? Read A US consultant's guide to invoicing a Swiss 'GmbH'. Want a quick next step for invoicing a German GmbH? Try the SOW generator.

Copy-paste pre-send checklist#

Use this as your final pre-send gate: make the invoice easy for AP to accept, easy to reconcile, and easy to defend later.

• Client legal name matches the contract party.

Check the invoice customer name against the executed agreement or vendor record for the German GmbH, not a brand label or email signature variant.

• Invoice number and dates are clean.

Confirm the invoice number is unique and sequential, and that issue date and service period match delivery. If you use a short small-amount format, keep it to invoices up to €250 gross.

• VAT path is explicit and consistent.

If VAT applies, show VAT rate(s) and VAT amount(s) (unless an exemption applies). If you are under Kleinunternehmer treatment, invoice without VAT and include the § 19 UStG note. Do not mix both approaches on one invoice.

• Payment terms and remittance reference are unambiguous.

Keep terms, due date, and payment reference obvious on the invoice, and use the invoice number as the reference where possible.

• Contract backstops are signed and referenced.

Before billing, make sure Termination, Limitation of Liability, Indemnification, Governing Law, Jurisdiction, and Dispute Resolution are settled in the signed contract set and easy to trace from the invoice.

• Send record, format acceptance, and tracking are logged in one trail.

Save file version, send timestamp, recipient, receipt confirmation, and payment status in one place; retain records for 8 years (entrepreneurs). Also confirm delivery format expectations: from 1 January 2025 businesses are described as needing to receive EN 16931 e-invoices, and during Jan 2025-Dec 2026 PDF remains acceptable only if the recipient agrees.

Want to confirm what's supported for your specific country/program? Talk to Gruv.