GoBD and invoices: what a traceable process has to deliver
GoBD (the German rules for proper digital bookkeeping) is not a seal a piece of software can carry. The principles describe how digital bookkeeping and record retention stay in proper order – and that is decided by how the program, its settings and your own process work together. Here is what matters for invoices specifically.
Traceability instead of file chaos
An invoice should stay traceable from creation to payment. That includes client master data, estimate, invoice, sending, payment and, where applicable, the dunning letter. Individual PDFs in different folders do not automatically provide this link.
An activity history and stable document IDs help explain changes. At the same time, it has to be clear who had access and which version was sent. For small teams, a simple process used consistently is better than a theoretically perfect system nobody maintains.
Immutability after sending
A finalized document should not be quietly overwritten. If an invoice has to be corrected in substance, the original transaction should be preserved and the correction should reference it traceably. That also applies to line items, amounts and numbers.
Immutability is not the same as infallibility. Mistakes happen. What matters is that the correction is documented and the old state can still be explained.
- Keep the sent version unchanged
- Document corrections as separate transactions
- Log access and activity traceably
- Check backups regularly
Completeness and availability
An invoice must not exist only as a nice-looking rendering when additional structured data is relevant for processing. Store the original files and the related records so that they stay readable and findable throughout the retention period.
Backups have to be more than a button that produces a ZIP file at some point. Check restoration, permissions and completeness regularly. A backup that has never been tested is an assumption, not a reliable safeguard.
What Sumaro can support
Sumaro can map document relationships, number sequences, statuses, activities, finalized invoices and exports in one workflow. That reduces breaks between tools and formats and makes preparing for your tax advisor easier.
Whether your overall process meets the requirements also depends on master data maintenance, access rights, sending, retention and internal rules. That is why Sumaro speaks of support rather than claiming an unproven certification.
A documented process instead of a buzzword
A GoBD-ready routine starts with a process description that you actually follow. Write down how an estimate is created, an invoice finalized, proof of sending saved, a payment matched and a correction made. The description doesn’t have to be long. But it should clarify which source is authoritative and who reviews an exception.
In a one-person business you are often responsible for every step. That is exactly when a fixed order pays off: check the data, finalize the document, file the original, reconcile the payment and only then prepare a dunning letter. A routine like this makes the work reproducible and makes the handover to your tax advisor easier.
- Record the process and responsibilities in writing
- Clearly distinguish original and correction
- Don’t hide exceptions behind standard automation
Organize retention concretely
Decide where original files, structured e-invoices, attachments and proof of sending are stored. An export should make the case understandable even if there is no access to the application later. Check file formats, readability, permissions and restoring from a backup at regular intervals.
A retention solution is no license to collect without limit. Deletion and blocking concepts have to fit statutory obligations, data protection and your actual business process. If in doubt, have the retention periods clarified by a professional. Sumaro can structure and export, but responsibility for the overall process remains with the business.
Sources and context
Legal and tax rules can change. What counts are the current primary sources and your professional advice.
Put this into practice on your very next job.
Test Sumaro with a real client case and take it from estimate or invoice through to payment. Free for 30 days, no contract.