Jupiter ERP

Required invoice details (§14 UStG)

Author: Jupiter ERP editorial teamLast updated:
Person at a table with a laptop and a notebook in daylight

In short

§ 14 (4) of the German VAT Act lists the details of a regular invoice. Small businesses under § 19 follow the shorter list in § 34a of the VAT Implementing Regulation. This page compares both lists, shows a fictional example, and explains what Jupiter ERP fills from master data. It is orientation, not advice on your case.

Which details does a regular invoice need under § 14 (4) UStG? Link to this section

An invoice must contain the details in § 14 (4) UStG. Special cases, such as the retention note under § 14b or the word 'credit note' when the recipient issues the invoice, apply only in the situations named there. This article covers the everyday B2B or B2C invoice you write yourself as the supplier.

The list is long because each field supports a different check: who supplied what, when, at which tax, under which number. Skipping the sequential number or the tax breakdown is a common reason invoices come back from customers or advisors. Read the statute text on gesetze-im-internet.de when you need the exact wording; IHK overviews summarise the same fields for day-to-day use.

Bank details are not on the statutory list. They are still useful so the customer can pay by SEPA. In Jupiter ERP they come from company master data when you maintain them. Currency, payment terms, and letterhead are commercial choices on top of the legal minimum.

  • Full name and full address of issuer and recipient
  • The issuer's tax number or VAT ID
  • Date of issue
  • A sequential invoice number, assigned once
  • Quantity and kind of goods, or scope and kind of service
  • Date of supply when it differs from the issue date (calendar month is enough under § 31 (4) UStDV)
  • The amount, split by tax rate and exemption, plus agreed reductions not already in the amount
  • Tax rate and tax amount, or, for an exemption, a note that the exemption applies
FieldRegular invoice (§ 14 (4))Small business (§ 34a UStDV)
Names and addressesRequiredRequired
Tax number / VAT ID / small-business IDTax number or VAT IDOne of those identifiers
Issue dateRequiredRequired
Sequential invoice numberRequiredNot on the minimum list
Quantity and kind of supplyRequiredRequired
Supply dateRequired if different from issue dateNot on the minimum list
AmountSplit by tax / exemptionSingle sum
VAT line or exemption noteRate and amount, or exemption note§ 19 exemption note
Bank detailsNot required by statuteNot required by statute

What changes for small businesses under § 34a UStDV? Link to this section

For supplies that are exempt under § 19 (1) UStG, § 34a UStDV requires at least names and addresses, a tax number, VAT ID, or small-business ID, the issue date, quantity and kind of supply, the amount as a single sum, and a note that the small-business exemption applies. A sequential number and the supply date are not on that minimum list. Small businesses do not deduct input VAT.

The example below is fictional. It is not a template to download. The invoice number comes from the number range in Jupiter ERP even though § 34a does not require it. Using a range still helps you and your advisor keep a clear archive.

E-invoice rules interact with small-business status. Receiving structured invoices already applies to domestic businesses, including small businesses. Issuing other invoices for § 19 supplies can remain allowed under § 34a sentence 4 UStDV after the general issuing transition. Details and deadlines belong in the e-invoicing article and the ministry FAQ linked in the sources.

  • Beispiel GmbH, Musterstraße 1, 10115 Berlin
  • Musterkunde AG, Beispielweg 2, 80331 München
  • Tax number: 12/345/67890 (placeholder)
  • Date of issue: 13 October 2026
  • 2 hours of consulting
  • Amount: €180.00
  • Note: The small-business exemption applies to this supply (§ 19 UStG).
  • Invoice number 2026-001, from the number range, beyond the minimum list

What does Jupiter ERP fill in automatically? Link to this section

Company, bank, and tax number come from master data. The invoice number comes from the number range. The tax rate comes from the line, or 0% with the § 19 note when you chose the small-business treatment in first steps. There is a PDF preview before sending. You review content and mandatory fields yourself. Reverse charge and intra-EU supplies belong with your tax advisor.

When e-invoicing is enabled (default in setup), the PDF contains ZUGFeRD 2.x with the EN 16931 profile. Structured fields must match what you typed. A wrong address in master data becomes a wrong address in both the visual PDF and the XML. Preview and, if needed, open the file in the e-invoice viewer before you treat the document as final.

New accounts get a 14-day trial of the full product with no credit card. After that, Free stays at €0 with 5 documents per month (invoices only), 10 contacts, 1 user, and 100 MB. You can write compliant invoices on Free; quotes, DATEV export, and dunning sit on higher plans. Filing incoming e-invoices as expenses starts at Business. The public viewer needs no account.

How do mandatory fields relate to e-invoices? Link to this section

Statutory mandatory fields and the e-invoice format are related but not identical. § 14 and § 34a say what content must appear. EN 16931 and ZUGFeRD say how that content is encoded for machines. A beautiful PDF that omits the tax number still fails the content test. A structured file that maps empty seller VAT fields fails the format test even if the visual page looks fine.

Since 2025, a PDF without structured data is an other invoice, not an e-invoice, under the current reading of § 14 UStG. During transition phases many issuers may still send other invoices for B2B supplies under the conditions in § 27 (38) UStG. Recipients must already be able to receive structured invoices. See the founders e-invoicing article for the 2026, 2027, and 2028 issuing steps.

When e-invoicing is on, Jupiter ERP embeds ZUGFeRD 2.x with the EN 16931 profile in the PDF. Inbound XRechnung files can be read in the viewer and filed as expense receipts from Business upward.

What should you double-check before you hit send? Link to this section

Use this short checklist every time until it becomes muscle memory. It does not replace a legal review of edge cases, but it catches the errors that delay payment.

  • Issuer and recipient show full name and full address
  • Tax number or VAT ID (or small-business ID where applicable) is present
  • Issue date and, if needed, supply date or month are correct
  • Invoice number comes from the range and was not reused
  • Lines describe quantity and kind clearly
  • VAT breakdown or § 19 note matches your tax treatment
  • PDF preview looks right; for e-invoices, structure is enabled
  • Bank details are present if you expect a SEPA transfer

Common questions

How you create a small-business invoice in Jupiter ERP is on the founder page. Invoicing software for founders

Jupiter ERP

Your first invoice in minutes

Start for free: write invoices on the Free plan. Choose plan, term, and add-ons in the app afterwards. Custom adaptations or API integration? Get in touch.

  • 14-day trial
  • No credit card
  • Hosted in Germany
  • GDPR-compliant
Required invoice details (§14 UStG) · Jupiter ERP