Start with a strict three-step sequence for how to write a german invoice: complete legal fields, set executable payment details, then run a final control check. Your draft should show a unique invoice number, invoice issue date, clear service date or service period, and explicit VAT treatment. Build amounts so line items roll cleanly into net amount, VAT amount, and gross amount. Add due date and bank account details in one block. Before sending, verify party identity, tax identifiers, and record linkage to the same invoice number.
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.
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.
State due date, payment terms, and payment instructions in plain language.
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.
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.
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.
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.
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.
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.
Lock legal names, addresses, and the tax identifier you plan to use before you draft amounts. That alone can reduce avoidable review issues.
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.
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.
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.
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.
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.
Show the invoice issue date and the service date or service period as distinct fields where relevant. Avoid a single generic date field.
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.
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.
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.
If totals cannot be reproduced from line items, approval can slow down. Build the math so a reviewer can recalculate it in one pass.
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.
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.
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.
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.
Set payment terms so AP can execute quickly, then define late-payment follow-up in advance.
Use consistent labels such as due date, account holder, and payment reference so payment can be executed with less back-and-forth.
Use clear, neutral language that matches your agreement so AP can review and process the invoice without extra interpretation.
Document the sequence: reminder, request for remittance date, and escalation to the agreed finance contact.
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.
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.
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.
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.
Use a short pre-send check for international cases:
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.
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.
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.
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.
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.
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.
Use a two-pass review before sending: legal completeness first, payment operability second. If either pass fails, pause and fix it before release.
| Check | Focus | Confirm |
|---|---|---|
| Required fields check | Legal completeness | Invoice number, issue date, service date or service period, recipient details, tax identifier, VAT treatment, and consistency across the Rechnung and any structured version |
| Payment execution check | Operability | Due date, payment terms, bank account details, and purchase order alignment |
| Evidence check | Defensibility | Each line item maps to proof of work and approved scope; archive with the final Rechnung PDF and any structured e-invoice payload |
| Control check | Records and totals | Invoice number sequencing is intact; reconcile totals from line items through gross amount |
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.
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.
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.
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.
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.
| Issue | Fix | Keep with record |
|---|---|---|
| Broken invoice number sequence | Issue a corrected document with clear linkage to the original | Keep both records in the audit trail with a short note on what changed and why |
| Wrong invoice recipient | Reissue with corrected details and tell AP which version is current | Keep the message brief and factual |
| Issue-date and service-period confusion | State invoice issue date and service period separately and clearly; update line-item notes | Use the corrected service-period language consistently across affected lines |
| Wrong VAT treatment | Correct the VAT field and include a plain reason statement on the revised invoice | In the AP note, identify the original invoice number, corrected invoice number, and exact field corrected |
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.
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.
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.
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.
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:
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.
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.
| Timeframe | Requirement | Condition |
|---|---|---|
| 2025 | Move toward structured domestic B2B e-invoices | Format readiness |
| Jan 2025-Dec 2026 | PDF still possible | With recipient agreement |
| From 1 Jan 2027 | Mandatory issuance | Businesses above EUR 800k annual turnover |
| From 1 Jan 2028 | Mandatory issuance | Remaining businesses |
| 8 years | Retain invoices | GoBD-aligned set |
Confirm supplier and customer legal names and full addresses, and include your Steuernummer or USt-IdNr. as applicable.
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.
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.
Make due date and bank details visible in one block, and confirm they are consistent across the final invoice version.
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.
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.
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.
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.
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.
A compliant German invoice should clearly identify the seller, the client, and the delivered service or product. Include core details, including a unique consecutive invoice number and clear payment information, so the invoice functions as both a payment request and tax evidence. Keep the e-invoicing timeline in view: domestic B2B businesses must be able to receive electronic invoices from January 1, 2025, with issuing obligations tightening in 2027 for businesses above EUR 800,000 turnover and expanding in 2028. A practical check is whether a reviewer can confirm identity, delivery scope, and payment data without opening another document.
The grounding here does not establish that both are always required in every invoice scenario. Make billing and service timing explicit on the invoice, and label dates clearly so billing and delivery are not confused.
The grounding here does not provide a strict legal rule for this choice. Use the format that makes the billed timeframe clear and unambiguous to the client and reviewer.
State VAT treatment clearly on the invoice. If you are using the small-scale entrepreneur VAT exemption, state that plainly instead of leaving VAT status unclear. Detailed VAT-field requirements vary by invoice type and are not fully covered here.
Invoice numbers are expected to be unique and consecutive, so a break in sequence can raise compliance concerns. Non-compliance is associated with delays, penalties, and tax complications. If you issue a correction, keep records consistent and clearly traceable.
At minimum, make the invoice a clear payment request by stating what is owed and the payment terms in one visible place. Keep wording clear and unambiguous so processing is straightforward.
This grounding does not define an exact first-step statutory correction workflow. Prioritize correcting inaccuracies that affect payment clarity or tax handling, and keep records consistent. Invoices are used for payment enforcement, dispute handling, and tax evidence, so corrections should preserve a clear trail.
Avery writes for operators who care about clean books: reconciliation habits, payout workflows, and the systems that prevent month-end chaos when money crosses borders.
Priya specializes in international contract law for independent contractors. She ensures that the legal advice provided is accurate, actionable, and up-to-date with current regulations.
Educational content only. Not legal, tax, or financial advice.
Choose your track before you collect documents. That first decision determines what your file needs to prove and which label should appear everywhere: `Freiberufler` for liberal-profession services, or `Selbständiger/Gewerbetreibender` for business and trade activity.
Set your German tax position first, then register and file. If you are a globally mobile consultant, a lower-risk approach is a clear decision order, not a tax shortcut.
The real problem is a two-system conflict. U.S. tax treatment can punish the wrong fund choice, while local product-access constraints can block the funds you want to buy in the first place. For **us expat ucits etfs**, the practical question is not "Which product is best?" It is "What can I access, report, and keep doing every year without guessing?" Use this four-part filter before any trade: