Finance & taxesJune 21, 20268 min read

GoBD for solo professionals: what matters in 2026

What GoBD, §14 UStG, e-invoicing, and retention periods really mean in daily work in 2026 - without tax jargon or panic.

What this article clarifies
  • GoBD is not just a large-company topic. It is everyday hygiene for digital receipts and invoices.
  • The key questions are simple: complete, ordered, traceable, timely, and protected against silent changes?
  • The earlier receipts, invoices, and projects are connected, the less end-of-month reconstruction remains.
1,088 Word count8 min Read time08 Sections
Cover image for the Klausi blog post "GoBD for solo professionals: what matters in 2026"

Summary

For many self-employed people, GoBD sounds like something that only matters once a tax audit appears. In reality it starts much earlier: with receipts, invoices, corrections, exports, and whether you can still explain a transaction months later. This refresh explains the rules in practical terms, clarifies the 8/10/6-year periods, and shows which routines actually help in daily work.

Why GoBD matters for solo professionals

Many self-employed people only meet GoBD when a tax advisor asks for exports or when an audit is announced. At that point everything suddenly feels complicated. In reality the core question is practical: can a third party later understand what happened, which receipt belongs to it, and whether something was silently changed afterwards?

That is why the topic is not limited to larger companies. Anyone who writes invoices, photographs receipts, documents payments, or stores business data digitally is already building an auditable process - whether intentionally or not.

For solo professionals this matters because bookkeeping often runs beside client work, projects, and appointments. The more fragmented that workflow is, the more expensive later reconstruction becomes.

The practical core: complete, ordered, traceable

For daily work, reduce GoBD to a few guiding questions: is the transaction fully captured, is the client or project clear, is the document readable, are changes documented, and can the data be exported cleanly when needed?

Protected against silent changes does not mean corrections are forbidden. It means corrections must remain visible. A quietly overwritten PDF or spreadsheet is weaker than a workflow with status, history, and clear correction logic.

Timely capture matters just as much. If receipts are gathered weeks later, traceability is already getting weaker.

  • Capture receipts as close as possible to the moment they arrive.
  • Keep invoice numbers sequential and unique.
  • Connect project, client, amount, date, and category.
  • Document corrections instead of overwriting old states.

§14 UStG: what makes an invoice clean

§14 UStG defines which details make an invoice legally usable for German VAT purposes. For solo professionals, the important parts are typically a unique invoice number, invoice date, service date, service description, customer data, amount, tax amount, and where applicable tax number or VAT ID.

The most common problem is not visual design. It is a broken system: duplicate invoice numbers, unclear service periods, missing mandatory fields, or an archive where invoice, payment, and project no longer belong together.

If invoices are derived from tracked services and work, this risk drops significantly. That is why GoBD, invoice logic, and time tracking for self-employed people are more closely connected than many people assume.

Retention in 2026: 8 years, 10 years, 6 years

From 2025 onward, invoices and booking receipts are generally subject to an 8-year retention period. In daily life this covers many documents self-employed people touch constantly: incoming invoices, outgoing invoices, and common bookkeeping receipts.

Alongside that, 10 years still apply to certain core accounting records such as books, inventories, annual statements, and comparable organisational documents. Commercial and business correspondence is usually kept for 6 years.

The practical outcome is simple: not everything has the same retention period. Good software therefore does not only store documents for a long time. It structures them so type and context remain clear later.

  • Invoices and booking receipts: generally 8 years.
  • Books, records, and annual statement documents: usually 10 years.
  • Business correspondence: usually 6 years.

Why e-invoices make structured data more important

E-invoicing makes one thing clearer: bookkeeping is not only about pretty PDFs. Over time, the important question becomes whether tax-relevant data remains structured, readable, and exportable.

Formats such as ZUGFeRD illustrate this well: the human-readable layer helps in daily work, but the structured layer matters for processing and audits. Both need to match. If tax-relevant additions only live in the PDF, those still need to be retained cleanly.

For solo professionals this does not mean memorising every technical format. It means using a system that carries data reliably instead of only displaying it nicely.

When general bookkeeping advice is no longer enough

Many bookkeeping articles stay at the level of deadlines and accounting logic. In practice, GoBD often fails somewhere else: at the media breaks. Receipts live in inboxes, invoices live in another tool, and project evidence sits somewhere in between.

If you want to improve the overall workflow, the next useful read is either bookkeeping for self-employed people or bookkeeping software for self-employed people 2026. Both help with the decision of when a single-purpose tool is enough and when a connected workflow saves real time.

GoBD becomes easier as soon as your system demands less reconstruction.

How Klausi helps

Klausi does not replace tax advice. The benefit is different: receipts, invoices, time, and projects should be captured in a way that removes end-of-month searching and reconstruction.

Finances, receipts, invoices, and project context sit inside one workflow. The AI assistant helps prepare and classify, but responsibility and control stay with you. For audits, that mainly means calmer data, EU hosting, and fewer scattered files.

See finances in Klausi - and check whether your current workflow already keeps receipts, invoices, and project context together without manual reconstruction.

A short checklist for everyday work

If you only spend five minutes a week on structure, check these points. They do not solve every edge case, but they reduce the risk of having to rebuild everything from memory later.

  • Are all incoming and outgoing invoices stored in one place?
  • Are invoice numbers sequential and unique?
  • Are receipts connected to project, client, or trip?
  • Can changes or corrections be traced?
  • Are exports for tax advisors or audits prepared?
  • Is it clear which documents must be kept for 8, 10, or 6 years?

Do self-employed people need to consider GoBD?

As soon as tax-relevant documents are created or stored digitally, GoBD becomes practically relevant. How far obligations go depends on the individual setup, but receipts, invoices, and records should always stay traceable and changes should be documented.

Do invoices still need to be kept for 10 years in 2026?

Invoices and booking receipts are generally subject to an 8-year retention period from 2025. Books, records, inventories, annual statements, and comparable core accounting documents remain at 10 years under §147 AO.

What is the most common GoBD mistake in daily work?

Usually not theory, but broken workflows: receipts are spread across inboxes and phones, invoice numbers are inconsistent, corrections overwrite previous states, and nobody can explain months later what happened when.

Does Klausi replace tax advice?

No. Klausi helps with structure, capture, and preparation. For individual tax, legal, or sector-specific questions, consult qualified professional advice.

Relevant product pages

These product pages match the article

If you want to continue the topic inside the product, start with the most relevant Klausi pages here.

Product

Finance

Income, expenses, receipts, and invoices — GoBD-compliant, with travel expenses and forecast.

Read more
Product

AI assistant

Day plans, receipt detection, and answers from your numbers — optional and GDPR-compliant.

Read more

Liefern statt verwalten.

Klausi verbindet Aufgaben, Zeit, Projekte und Finanzen - damit dein Arbeitstag am Ende nicht rekonstruiert werden muss.