Jupiter ERP

E-invoicing rules for founders

Author: Jupiter ERP editorial teamLast updated:
Desk by a window with a laptop, a closed folder, and a coffee cup

In short

Since 2025 an e-invoice is a structured file, not a plain PDF. Receiving and issuing follow different deadlines. Small businesses have special issuing rules under § 34a UStDV. This page follows § 14, § 27 (38) UStG, and the finance ministry FAQ. It is orientation, not advice on your case.

What counts as an e-invoice since 2025? Link to this section

Under § 14 (1) UStG, an electronic invoice is issued, sent, and received in a structured electronic format that can be processed electronically. The format must follow the European standard EN 16931 or an interoperable format the parties agree. A PDF without that data is an other invoice.

ZUGFeRD is a hybrid: a PDF people can open, plus embedded XML machines can parse. XRechnung is typically a pure XML package used heavily in public procurement. Jupiter ERP generates ZUGFeRD 2.x with the EN 16931 profile inside the invoice PDF, provides XRechnung 3.0 as a download for public authorities, and reads inbound XRechnung files as expense receipts.

Content rules under § 14 (4) UStG or § 34a UStDV still apply. Structure does not fix a missing tax number. Mandatory field overviews from the chambers of commerce help you check the human-readable side; FeRD documents describe the ZUGFeRD profiles on the technical side.

Do I already have to receive e-invoices? Link to this section

There is no transition period for receiving. Domestic businesses must be able to receive an e-invoice from 1 January 2025, including small businesses. The finance ministry FAQ says an email inbox is already enough. The FAQ does not provide exceptions for receiving.

'Able to receive' does not mean you must book every file automatically. It means a supplier can send a structured invoice and you can take delivery. Many founders start with email plus a viewer. Filing e-invoices as expense receipts inside Jupiter ERP starts at Business. The public e-invoice viewer on the website works without an account when you only need to read a file.

Plan a folder or inbox rule early. Lost attachments are still lost, structured or not. If your advisor collects receipts, agree how structured files reach the firm: forward, export, or DATEV later on a paid plan.

From when do I have to issue e-invoices myself? Link to this section

Until 31 December 2026 every issuer may still send an other invoice for supplies performed by then (§ 27 (38) no. 1 UStG). Paper does not need consent. Another electronic format, such as a PDF without structured data, needs the recipient's consent.

Until 31 December 2027 that continues if prior-year turnover under § 19 (2) UStG was not more than €800,000 (§ 27 (38) no. 2 UStG). Above that, the issuing duty starts in 2027. From 2028 the transition ends for the remaining issuers. An EDI process that is not itself an e-invoice may still run until the end of 2027 under the conditions in the statute.

These dates move with legislation and ministry guidance. Re-check the linked FAQ and UStG text before you promise a customer a format for a future year. Software defaults help you issue structured PDFs early; they do not decide which statutory deadline binds your entity.

PhaseIssuing (typical domestic B2B)Receiving
From 1 Jan 2025Other invoices still widely allowedStructured receive required
Through 2026Other invoices allowed for all issuers (conditions in § 27 (38))Still required
2027Other invoices if prior-year turnover ≤ €800,000; else e-invoiceStill required
From 2028General issuing transition ends; see small-business nuance belowStill required

Continue reading

What is different for small businesses (Kleinunternehmer)? Link to this section

An invoice for supplies that are exempt under § 19 (1) UStG may always be sent as an other invoice under § 34a sentence 4 UStDV, including after 2028. That is the core nuance founders miss: receiving is already mandatory; issuing a structured e-invoice for § 19 supplies is not forced by that sentence in the same way as for regular taxable supplies.

Small businesses must still receive e-invoices. If someone switches to regular taxation, the issuing duty applies from then, subject to the other conditions and transition rules. A customer can still ask for a structured invoice when the statute does not yet require it. Refusing without a conversation can delay payment even when the law still allows an other invoice.

In Jupiter ERP you set the small-business treatment in first steps. Lines start at 0% VAT with the § 19 note. E-invoicing can stay on so the PDF carries ZUGFeRD anyway. That is often the simplest customer experience during the transition: one PDF that works for humans and machines, without claiming you must issue structure before your deadline.

How does Jupiter ERP handle e-invoices on Free and during the trial? Link to this section

Setup turns the e-invoice on by default. The PDF then contains ZUGFeRD 2.x with the EN 16931 profile, including on Free. New accounts start with a 14-day trial of the full product, no credit card, and no automatic charge. After the trial, Free stays at €0: 1 user, 10 contacts, 5 documents per month (invoices only), 100 MB, templates, tasks, and time tracking.

You can read received files in the e-invoice viewer without an account. Filing them as expense receipts in the panel starts at Business. DATEV export also starts at Business. Dunning starts at Enterprise. Do not expect Free to be a full accounting suite; expect it to issue invoice PDFs with optional ZUGFeRD.

For many private B2B customers, ZUGFeRD hybrid PDFs are the practical default during and after the transition. Inbound XRechnung files can be read in the viewer and filed as expense receipts from Business upward.

  • Default: ZUGFeRD 2.x (EN 16931) embedded in the invoice PDF
  • Available on Free and during the 14-day trial
  • Public e-invoice viewer without login
  • Expense booking of incoming e-invoices from Business

Does the duty cover invoices to private customers? Link to this section

The e-invoice duty covers supplies between domestic businesses. Invoices to consumers are outside it, according to the finance ministry FAQ. You can still send a clear PDF, and you can still enable ZUGFeRD if your process is simpler with one setting for all invoices.

Foreign supplies and special regimes need separate checks with your advisor. This page stays with the domestic founder case: receive structure now, issue on the staged timeline, watch the small-business issuing nuance, and use a hybrid PDF when your software supports it.

Rules can change. Prefer the statute and the ministry FAQ over blog posts when something material is at stake. The sources on this article point to those primary references and to the FeRD ZUGFeRD specification.

Common questions

Related articles

E-invoice software: formats, deadlines, Jupiter ERP

E-invoice software must create or process structured EN 16931 data, not only send PDFs. Jupiter ERP issues outbound ZUGFeRD 2.x with the EN 16931 profile embedded in invoice PDFs, and XRechnung 3.0 as a download for public authorities. Inbound, Jupiter ERP reads ZUGFeRD and XRechnung as expense receipts. Receiving has been mandatory since 2025; issuing follows transition rules through 2026, 2027, and 2028. This guide explains formats, deadlines, and the Jupiter ERP workflow. It is orientation, not advice on your case.

Learn more

XRechnung: format, vs ZUGFeRD, Jupiter ERP

In Germany, XRechnung is the EN 16931 XML invoice for public authorities. Jupiter ERP provides XRechnung 3.0 (CII) as a download for invoices and credit notes, and creates ZUGFeRD 2.x in the PDF for other B2B invoices. Inbound XRechnung files are read as expense receipts. This article explains the difference and the download. It is orientation, not tax advice.

Learn more

E-invoicing and ZUGFeRD in Jupiter ERP

In Germany, a B2B e-invoice (E-Rechnung) is a structured, machine-readable dataset, typically XML under EN 16931. Jupiter ERP embeds ZUGFeRD 2.x with that profile in invoice and credit note PDFs. A plain PDF without structure is usually not enough. This page is orientation, not advice on your case.

Learn more

Small-business scheme (§19 UStG) in bookkeeping

Under Germany’s small-business VAT scheme (Kleinunternehmer, §19 UStG) you generally charge no VAT and may not deduct input VAT. Expenses and reports are treated gross. Jupiter ERP applies the taxation type to invoices, EÜR views, and depreciation once you set it in accounting settings.

Learn more

ZUGFeRD in the PDF, including on Free, is summarised with the plan limits 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
E-invoicing rules for founders · Jupiter ERP