DMS & ERP: Digital, GoBD-Compliant Archiving

In short: a DMS inside your ERP firmly ties every document to its posting and stores it unalterably – turning a stack of paper into a GoBD-compliant, always searchable archive. The document management system (DMS) handles three jobs here: capturing documents (by scan or as an e-invoice), linking them to the business transaction, and retaining them audit-proof over the statutory period. What matters is not just that your system stores documents, but how: unalterably, traceably and machine-findable. This article walks you through the full path from incoming document to retention period – and what to look for when choosing a system.

Why a DMS in the ERP is more than a file-storage folder

Many companies scan documents and drop the PDFs into folder structures on a drive. That is digitization, but not proper archiving. The difference lies in context: a DMS integrated into the ERP connects the document with the structured data – journal entry, supplier, order, payment. A folder full of PDFs does not.

This integration delivers three tangible advantages:

• Traceability: From the journal entry you jump straight to the original document – and back again. That is exactly what the GoBD require.
• Immutability: The document sits write-protected in the archive, not on a drive where anyone can overwrite or delete it.
• Findability: Full-text and metadata search locates a document in seconds instead of digging through folder trees.

A plain file system reliably meets none of these requirements. That is why an integrated DMS – whether as an ERP module or a connected third-party system – is practically mandatory for digital document processing.

Document capture: keep scan and e-invoice apart

Every archiving process starts with capture. There are two fundamentally different paths here that you should not confuse.

Scanning and reading paper documents

Classic paper documents – incoming invoices, delivery notes, receipts – are scanned and evaluated via text recognition (OCR). A good DMS reads the document number, date, amount and supplier automatically and suggests the matching posting. Important: the scanned document must then be stored unalterably. In many cases, mere digitization allows the destruction of the paper original – but only if the scan process is cleanly described in your process documentation.

Processing e-invoices as structured data

The e-invoice is neither a scan nor a PDF, but a structured data set in a format compliant with EN 16931 – such as XRechnung or ZUGFeRD. It must be archived in its original format; a printout or PDF copy does not replace the XML data set. This is a common mistake: anyone who files an e-invoice only as a PDF has lost the original document subject to retention. Your ERP should read in the structured data set, take the posting data directly from it, and store the original audit-proof.

For the e-invoice, Germany applies a clear phasing that you should know:

So the receipt obligation already applies – your system must be able to accept and archive e-invoices in EN 16931 format, regardless of when you yourself have to start issuing them.

Linking document and posting

The core of GoBD compliance is the seamless connection between document and posting. An expert third party – a tax auditor, for instance – must be able to trace every business transaction from the document to the posting and back again. This is called the document function.

In practice this means: every posting in the general ledger carries a reference to the corresponding document in the DMS, and every document shows which journal entry processed it. If something changes – a correction via cancellation, say – the original context is preserved. This firm link is the difference between an orderly archive and a loose collection of files.

When choosing a system, make sure the link is created automatically during posting and does not have to be maintained manually. Manual assignment is error-prone and quickly tears gaps at high document volumes – and every gap is a potential ground for objection.

Audit-proof archiving: unalterable and traceable

Audit-proof archiving means that a document, once archived, can no longer be changed or deleted unnoticed. It is the technical answer to the GoBD principle of immutability.

What your system must deliver technically

• Write-protected storage: The document sits in its original format, non-overwritable. Corrections create a new version, the original is preserved.
• Versioning: Every edit is stored as its own version, and the complete history is traceable.
• Audit trail: A seamless audit trail logs who captured, linked or changed which document and when – with user and timestamp.
• Permissions model: A clean system of roles and permissions controls who may archive, approve or delete.

Backup and reproducibility

Audit-proof archiving does not end with storage. The documents must remain legible and reproducible over the entire period. A regular, tested backup including proven restoration is mandatory – as is a concept for how you transfer documents without loss during a system change or data migration. An archive that is no longer legible after ten years does not serve its purpose.

Setting retention periods correctly

The retention obligation varies by document type. What matters is the current reform under the Fourth Bureaucracy Relief Act (BEG IV), which shortened the period for accounting documents.

The shortened 8-year period applies to accounting documents whose regular 10-year period had not yet expired on 31.12.2024. Your DMS should calculate the period automatically per document type and release documents for deletion only after expiry – ideally via a documented deletion concept that also accounts for GDPR requirements. When in doubt, your tax advisor classifies the individual case; the longer period always trumps the shorter one.

Search, access and audit

An archive is only as good as its findability. During a tax audit under § 147 AO, your system must serve data access in all its variants – the framework originating from the GDPdU lives on in the GoBD:

• Z1 – direct access: The auditor works read-only directly in the system. You need an auditor account with read-only rights.
• Z2 – indirect access: Your team runs evaluations as specified by the auditor.
• Z3 – handover on data medium: You export the tax-relevant data and documents in an analyzable format.

For everyday work, fast full-text and metadata search matters most: document number, supplier, amount, date or order as a search criterion. Anyone who finds a document in seconds instead of searching through folders saves more time in daily operations than most expect when choosing a system. Also check whether the interface to your tax advisor – the DATEV export, for instance – hands over documents and postings together.

Process documentation: the mandatory part almost everyone forgets

The best DMS technology is useless without a description of how you use it. The process documentation is explicitly required by the GoBD and the point at which most SMEs fail. It describes traceably how documents are created, captured, linked, archived and deleted after the period expires.

For digital document archiving, it must include at least:

• Scan process: Who scans when, how is it checked, when may the paper be destroyed (replacement scanning)?
• E-invoice processing: How are structured documents read in and stored in their original format?
• Archive and deletion rules: Periods per document type, permissions, deletion concept.
• Operation and backup: Backup, access protection, versioning, contingency plan.

What matters is versioning the documentation itself: if a process changes, it must be traceable which version applied when. During implementation, a structured ERP consulting engagement helps by building these requirements in from the start instead of retrofitting them expensively later – along with a clean integration between DMS, accounting and the tax-advisor interface.

Conclusion

A DMS in the ERP turns documents into an orderly, audit-proof and searchable data set rather than PDFs in a folder. Four things are decisive: structured capture (scan and e-invoice in the original format), a firm link between document and posting, unalterable archiving with an audit trail, and correctly set retention periods. Without a versioned process documentation, however, the whole thing remains piecemeal. Which systems cover these requirements is something you research in the ERP directory and the comparison. And for all detailed tax-law questions the rule holds: coordinate with your tax advisor before the audit arrives.