Document archiving software for businesses: digital and audit-proof archiving
Document archiving software stores business documents digitally, unalterably and in searchable form, so that they remain complete, legible and available for audits throughout the entire retention period.
With enaio and AWP Consult, you replace filing cabinets, scattered network drives and legacy archive systems with one central digital archive. Invoices, contracts, emails and HR records are stored audit-proof in one place and can be found in seconds, even years later.
- Document class
- Supplier contract
- Received
- by email, 12 Mar 2026
- Format
- PDF/A-3 with XML
- Hash value
SHA-256 7f3a…c91e- Retain until
- 31.12.2036
- Status
- unalterable
Key facts at a glance
Document archiving software is a system that stores completed business documents digitally, unalterably and in searchable form throughout the entire retention period and logs every access.
Electronic archiving is expressly permitted under Section 147(2) of the German Fiscal Code (AO) and Section 257(3) of the German Commercial Code (HGB); however, opening balance sheets and annual financial statements must be retained in the original.
Audit-proof archiving is not a legal term: the benchmark is the German GoBD (principles for proper electronic bookkeeping) issued by the Federal Ministry of Finance and the ten principles of the VOI industry association.
Retention periods run from the end of the calendar year: ten years for books and annual financial statements, generally eight years for accounting vouchers, six years for commercial and business letters.
For long-term formats: PDF/A in accordance with ISO 19005 for documents, the original XML file for e-invoices, and the original format wherever machine evaluability matters.
For scans and the preservation of evidential value, the guidelines TR-03138 (RESISCAN) and TR-03125 (TR-ESOR) of the German Federal Office for Information Security (BSI) set the technical standards.
What is document archiving software?
Document archiving software is a system that retains completed documents over the long term and protects them against tampering: it captures documents from scanning, email, ERP and specialist applications, adds metadata, protects them against alteration, monitors retention periods and makes them retrievable at any time via search and files.
In most companies, the initial reason for electronic archiving is a legal one: the German Fiscal Code (AO), the German Commercial Code (HGB) and the GoBD, the Federal Ministry of Finance's principles for proper bookkeeping and record retention in electronic form, require records relevant under tax and commercial law to remain organised, complete and legible for years. Section 147(2) AO and Section 257(3) HGB expressly permit retention on data carriers, with the exception of opening balance sheets and annual financial statements. Documents received electronically must generally also be retained electronically.
The everyday benefits are at least as great: less space for binders, no searching through basement archives and fast access from any location and device, with the appropriate permissions.
Typical contents of a digital archive
Incoming and outgoing invoices, including e-invoices
Accounting vouchers, bank statements, annual accounts
Contracts and agreements
Business emails and correspondence
Personnel files and payroll records
Delivery notes, consignment notes and customs documents
Technical documentation, test reports and drawings
Do you have a specific question about your case?
In the archive consultation, we review your binders, network drives and legacy systems and outline how a central archive with enaio would be set up at your company.
- Holdings and document types
- Legacy systems and interfaces
- Cloud or on-premises
What requirements must audit-proof archiving software meet?
Audit-proof archiving software must store documents unalterably, completely and in an orderly manner, make them retrievable via full text and metadata, keep them legible in long-term formats, manage retention periods and protect and log every access. Audit-proof is neither a legal term nor a protected seal; it is the sum of these six properties, which must stand up to tax audits, statutory audits and data protection requirements.
Immutability
Archived documents cannot be overwritten or deleted unnoticed. Changes to metadata are versioned, and the original state remains identifiable.
What audit-proof meansCompleteness and order
Every document is captured with a unique identifier and metadata and placed in a clear file structure. Nothing is lost between the incoming mail and the archive.
Full-text search and metadata
Text recognition makes even scanned documents searchable. Metadata such as customer, document number or date lead you straight to the result.
Full text or metadata?Long-term formats
PDF/A for documents, XML for e-invoices and the original format where it is subject to retention requirements. This keeps everything legible even after many years.
Retention periods
Retention periods are defined for each document class and monitored automatically. Documents are deleted only after expiry and with a log entry.
Retention periods 2026Access control and audit trail
Roles and permissions control who sees what. Every access is logged, and auditors receive read-only access.
How does archiving software differ from a DMS?
Archiving software retains completed documents unalterably and over the long term, whereas a document management system (DMS) edits, versions and controls documents in ongoing business via workflows. The two are often equated but solve different tasks. In practice, most companies need both in one system.
| Feature | Archiving software | Document management system (DMS) |
|---|---|---|
| Main task | Retain completed documents securely over the long term | Edit, share and control documents in ongoing business |
| Document status | Final, no longer alterable | In progress, with versions and drafts |
| Changes | Excluded, only metadata is versioned | Desired, with versioning and check-in and check-out |
| Typical functions | Audit-proof storage, retention periods, research, auditor access | Workflows, follow-up reminders, templates, collaboration |
| Time horizon | Years to decades | As long as the process is active |
| Legal focus | GoBD, AO, HGB, retention periods | Processes, responsibilities, data protection |
enaio combines both: documents are edited in the DMS and move automatically into the audit-proof archive once the process is completed, without media breaks and without a second system.
What does digital archiving change in day-to-day business?
Above all, digital archiving changes how you search: anyone who needs a contract, an invoice from three years ago or the correspondence on a complaint case finds it via full text and metadata in seconds rather than hours, from any location and only with the appropriate permissions. The legal obligation is usually the trigger; this benefit is the reason why companies do not want to go back to paper.
At the same time, the archive becomes the foundation for further digitalisation: an incoming invoice workflow, a digital personnel file or contract management access the same files.
Full-text and metadata search across all files, including email attachments and scanned documents.
Access from different locations and devices, via the client, the browser or directly from Microsoft Office.
Scheduled follow-up reminders alert you to notice periods, inspection dates and the end of retention periods.
With subscriptions, you are notified when something changes in a file or process.
Filing shelves and external records storage gradually become unnecessary.
Not sure where to start? We will assess your starting position.
What technology and standards underpin audit-proof archiving?
Audit-proof archiving rests on six building blocks: the principles of the German GoBD (principles for proper electronic bookkeeping) and the VOI, storage technologies such as WORM, hash values and timestamps, long-term formats such as PDF/A, the guidelines TR-ESOR and TR-RESISCAN of the German Federal Office for Information Security (BSI), a concept for email archiving and a clean metadata model. The following sections explain each building block with the relevant references.
01
Audit-proof archiving and the VOI principles
The term audit-proof archiving was coined by the VOI industry association in the 1990s with ten principles that still serve as a reference today. In essence, they require:
The principles largely correspond to those of the German GoBD (principles for proper electronic bookkeeping). There is no legal definition. What this means for tax records is explained on the page on GoBD-compliant DMS.
- proper retention in accordance with legal and internal requirements,
- completeness: no document is lost on its way into the archive or within it,
- archiving at the earliest organisationally possible point,
- conformity with the original and unalterable storage,
- access only for authorised persons,
- retrieval and reproduction within a reasonable time,
- destruction no earlier than the end of the retention period,
- traceable logging of every modifying action,
- auditability of the entire procedure by expert third parties,
- compliance with all principles even during migration and system changes.
02
Storage technologies: WORM, hash values and timestamps
The German GoBD (principles for proper electronic bookkeeping) leave open how immutability is achieved: through hardware, software or organisational measures (para. 110). In practice, archives combine several levels:
- Hardware WORMWrite Once Read Many: data carriers that can be written once and only read thereafter. Historically optical media, rare today.
- Software WORMStorage systems or object storage with a retention lock that technically refuse deletion and overwriting until the end of the retention period.
- Hash valuesA cryptographic fingerprint, such as SHA-256, is stored for each document at the time of archiving. Any subsequent deviation is detected during the verification run.
- TimestampsA timestamp from a trusted authority proves that a hash value existed at a specific point in time. Qualified timestamps are governed by the eIDAS Regulation.
Have checksums verified automatically against the archive holdings at regular intervals and log the result. A hash value that nobody checks only protects you on paper.
03
Long-term formats: PDF/A-1 to PDF/A-4 and XML originals
Under Section 146(5) of the German Fiscal Code (AO), data must be available at all times and promptly legible throughout the retention period. PDF/A is the ISO 19005 series of standards for long-term archiving. Fonts must be embedded, encryption and external references are prohibited, and JavaScript is only permitted in PDF/A-4e.
For e-invoices, the structured XML part is authoritative and is retained in the original. Under para. 135 of the German GoBD (principles for proper electronic bookkeeping), conversion is only permitted if no information is lost and the conversion is documented. Spreadsheets, CAD drawings and ERP exports remain in their original format where evaluability matters.
- PDF/A-1 (2005)Based on PDF 1.4, no transparency and no embedded files. Conformance levels a and b.
- PDF/A-2 (2011)Based on PDF 1.7, permits JPEG2000, transparency and the embedding of PDF/A files. Additional level u for Unicode.
- PDF/A-3 (2012)Like PDF/A-2, but permits embedded files of any format. ZUGFeRD with its embedded XML invoice is based on this.
- PDF/A-4 (2020)Based on PDF 2.0, variants 4f for embedded files and 4e for engineering content.
Validate generated PDF/A files automatically against the standard. A file that is merely called PDF/A is not necessarily one.
04
BSI TR-ESOR and TR-RESISCAN
The Technical Guideline BSI TR-03125 (TR-ESOR) of the German Federal Office for Information Security describes the preservation of evidential value of cryptographically signed and unsigned documents over long periods. It defines a middleware in front of the actual storage and uses Evidence Records in accordance with RFC 4998 and RFC 6283: hash values are combined in hash trees and secured with archive timestamps that are renewed in good time. The current version is 1.3. TR-ESOR is aimed primarily at public authorities but is also relevant for companies with qualified signed contracts.
BSI TR-03138 (TR-RESISCAN), issued by the German Federal Office for Information Security, describes replacement scanning. It is based on a structural analysis and a protection requirements analysis of the paper documents. A basic module always applies; additional modules are added for high or very high protection requirements for integrity, confidentiality or availability. Every scan product receives a transfer note. For high integrity protection requirements, the guideline provides for advanced signatures, seals or timestamps, and for very high requirements, qualified ones.
The protection requirements analysis is the lever: for normal protection requirements, the basic module is sufficient, with additional modules only where the analysis requires them. Details on the page Replacement scanning under TR-RESISCAN.
05
Email archiving: journaling and business letters
Emails must be retained if they are commercial or business letters, i.e. relate to a commercial transaction (Section 257(2) of the German Commercial Code, HGB), or are otherwise relevant for tax purposes. The retention period is generally six years. If the email merely serves to transport an invoice, the attachment is what counts. Technically, there are three approaches:
enaio archives emails with attachments directly from Outlook and on a rule basis from Exchange. Data protection, private use and the works council (Betriebsrat) should be clarified before you start; guidance is provided on the page on GDPR-compliant document management. More on the technology: GoBD-compliant email archiving.
- JournalingThe mail server creates a copy of every incoming and outgoing message before users can delete it. Maximum completeness, but private and irrelevant emails also end up in the archive.
- Rule-based archivingRules based on mailbox, sender or content determine what is archived. Complete only if the rules are maintained.
- Filing from the clientUsers file emails from Outlook into the relevant file. Precise in terms of content, but dependent on discipline.
06
Metadata model, indexing and storage hierarchy
An archive is only as good as its metadata. For each document class, the metadata model defines which fields are mandatory, which source they come from and how they are validated.
- Mandatory fieldsDocument class, document date, business partner, document number, organisational unit and the triggering event of the retention period.
- Origin of valuesERP master data instead of free text: supplier, customer and personnel number are looked up, not typed.
- IndexingText recognition for full text, classification and data extraction with enaio capture and enaio classify, validation against master data.
- Storage hierarchyHierarchical Storage Management automatically moves rarely used documents to lower-cost storage tiers without changing search or access for users.
Define the metadata model before the migration. Fields introduced only later will be missing from legacy holdings forever.
Together with you, we clarify which storage technology, which long-term formats and which metadata model your documents need before the first document is archived.
When do retention periods start in the archive?
In the archive, retention periods do not run from the filing date but from the end of the calendar year in which the relevant event occurred, such as the creation of the voucher or the receipt of the letter (Section 147(4) of the German Fiscal Code, AO; Section 257(5) of the German Commercial Code, HGB). That is why every document class needs the correct event as metadata.
| Records | Period | Period starts: end of the calendar year of |
|---|---|---|
| Books, inventories, annual financial statements, organisational documents | 10 years | the last entry, preparation or adoption |
| Accounting vouchers, including invoices | 8 years | the creation of the voucher |
| Commercial and business letters, including emails | 6 years | receipt or dispatch |
| Delivery notes without voucher function | until receipt or dispatch of the invoice | not tied to the calendar year |
The tax retention period does not expire as long as the records are relevant for taxes whose assessment period has not yet expired (Section 147(3) of the German Fiscal Code, AO). For credit institutions, insurance companies and investment firms, a period of ten years applies to accounting vouchers. Overview: Retention periods 2026.
How do you migrate legacy archives without losing auditability?
You migrate legacy archives in an auditable way in four phases, from inventory through mapping and test migration to transfer with proof, with all documents, including metadata, links and checksums, transferred completely and reconciled against the legacy system. Many companies operate an older archive system that is no longer maintained. Under the German GoBD (principles for proper electronic bookkeeping, para. 142 to 144), a migration must transfer all data subject to retention, together with metadata and links, in a quantitatively and qualitatively equivalent form. Mere exports as print files are not sufficient. Only after the end of the fifth calendar year following the changeover does a machine-readable data carrier suffice under certain conditions, in accordance with Section 147(6) of the German Fiscal Code (AO).
01
Inventory
Systems, formats, volumes, metadata, signatures and running retention periods are recorded. The result is a volume breakdown for each document type.
02
Mapping and validation
Old document types and fields are mapped to the document classes in enaio. Mandatory fields, date formats and master data references are checked in advance.
03
Test migration
A subset is transferred and checked against the legacy system by volume reconciliation, checksum comparison per document and random samples.
04
Transfer and proof
Complete migration with a log of volumes, checksums and deviations, followed by an orderly shutdown of the legacy system.
More on this: Migration to enaio and enaio update and version upgrade
How long will it take in your case? We will estimate it with you.
Request an estimate +49 6104 94738-13What are the most common mistakes in archiving projects?
The most common mistakes in archiving projects are PDF copies instead of the original format, retention periods calculated from the filing date, migrations without checksums, signed documents without preservation of evidential value, journaling without a concept and scanning without organisational instructions. They cost time or are flagged during audits, but can all be avoided with proper planning.
| Typical mistake | Consequence | Better approach |
|---|---|---|
| Only PDF archived instead of original | The XML data of the e-invoice or evaluable exports are missing, and the conversion is not documented. | Archive the original and the rendition together under one document ID. |
| Retention calculated from filing date | Documents are deleted too early or never, because the triggering event is missing. | Period start as metadata per document class, calculated from the calendar year end. |
| Migration without checksums | It cannot be proven retrospectively whether all documents arrived unchanged. | Compare hash values before and after the migration and log deviations. |
| Signatures without evidence preservation | Qualified signed documents lose evidential value as algorithms age. | Where needed, plan archive timestamps and Evidence Records in accordance with TR-ESOR. |
| Journaling without a concept | Private emails and spam end up in the audit-proof archive and can no longer be deleted. | Filter rules, a private use policy and a data protection review before you start. |
| Scanning without organisational instructions | Paper is destroyed, but the scanning process is not documented. | Organisational instructions with quality control, guided by TR-RESISCAN. |
Do you have a specific question about your case?
What do customers say about their digital archive?
Above all, customers report that documents are stored centrally and found quickly. Here are two voices from companies that archive their documents with AWP Consult and enaio.
We introduced the software to greatly simplify searching for documents and to optimise our incoming and outgoing invoice process. We achieved both with the help of AWP. The very pleasant collaboration was and still is characterised by a high level of professionalism.
After several meetings and presentations, enaio was exactly the solution we had envisaged for a new DMS and a new incoming invoice workflow. Easy to use, a clear user interface, clear processes. All documents can be found quickly and easily.
What criteria should you use to choose document archiving software?
You choose archiving software based on nine criteria: audit-proof compliance, automatic capture, search, formats, retention and deletion, integration, operating model, migration and export, and support. Vendors' feature lists are similar; the differences show mainly in integration, operation and exit. Use these questions to compare document archiving software for businesses.
| Criterion | Questions for the vendor | Why it matters |
|---|---|---|
| Audit-proof compliance | How is immutability ensured technically? Are there hash values and verification runs? What is logged? | Basis for GoBD compliance and tax audits |
| Capture | Are scans, email mailboxes, e-invoices and ERP documents captured automatically? | Every manual filing step is a gap |
| Search | Is there full-text search with text recognition and metadata search across all files? | An archive pays off when you retrieve documents |
| Formats | Are XML originals preserved and PDF/A files validated? | Legible for the entire period |
| Retention and deletion | Can retention periods be managed per document class with a triggering event, and are deletions logged? | Required under AO, HGB and GDPR |
| Integration | Are there interfaces to SAP, DATEV, Dynamics 365, Outlook and Microsoft 365? | Archive in your familiar tools |
| Operating model | Is the software available in the cloud and on-premises? Where are the data centres located? | Data protection, IT strategy and effort |
| Migration and export | How are legacy archives transferred? How do data and metadata get out if you switch later? | Protection against vendor dependency |
| Support | Who handles setup, training, updates and support? | An archive runs for many years |
More on selection: Eight criteria for the right ECM system, Avoiding vendor lock-in and Cloud or on-premises.
Together with you, we review capture, retention periods, integration and migration for your documents and show what an audit-proof archive with enaio could look like at your company.
Frequently asked questions about archiving software
What is document archiving software?
A system that stores completed documents digitally, unalterably and in searchable form throughout the entire retention period. It captures documents from scanning, email and specialist applications, adds metadata, protects them against alteration and makes them retrievable via search and files. Retention periods, permissions and logs are part of the system.
Which archiving software is audit-proof?
Software is audit-proof if it stores documents unalterably, logs changes, manages retention periods and keeps documents legible at all times. There is no official seal for this; the German GoBD (principles for proper electronic bookkeeping) and the ten VOI principles serve as the reference. enaio meets the technical requirements; the archive becomes audit-proof through its configuration and procedural documentation.
What is the difference between archiving software and a DMS?
A DMS manages documents in ongoing business, with editing, versions and workflows. Archiving software retains completed documents unalterably. enaio combines both in one system, so that documents move into the archive without media breaks once the process is completed.
Which archiving software is suitable for medium-sized businesses?
A solution that grows with your requirements: start with invoices and the archive, then add contracts, personnel files and workflows later. What matters are interfaces to ERP and email and a partner who supports implementation and operation, such as a certified enaio partner. enaio is used by medium-sized companies as well as by larger organisations.
Which law governs electronic archiving?
There is no specific law on electronic archiving; the key provisions are Section 147 of the German Fiscal Code (AO), Section 257 of the German Commercial Code (HGB), Section 14b of the German VAT Act (UStG) and the GoBD (principles for proper electronic bookkeeping). Section 147(2) AO and Section 257(3) HGB permit retention on data carriers if it complies with the principles of proper accounting and the data remains available and legible throughout the retention period. Received commercial letters and accounting vouchers must match the original visually, while for e-invoices a match in content is sufficient. Opening balance sheets and annual financial statements must be retained in the original.
How long must documents be archived digitally?
The same periods apply as for paper: ten years for books and annual financial statements, generally eight years for accounting vouchers and invoices, six years for commercial and business letters. The period begins at the end of the calendar year in which the document was created or received. As long as records are relevant for open tax assessments, the period does not expire.
Which format is suitable for long-term archiving?
PDF/A for documents, the original XML file for e-invoices, and PDF/A or TIFF with text recognition for scans. PDF/A-3 permits embedded files and is therefore the basis of ZUGFeRD. Where evaluability matters, the original format is archived as well.
What is the difference between WORM and software WORM?
Hardware WORM uses data carriers that can physically be written only once. Software WORM achieves the same goal with disk or object storage that uses a retention lock to refuse deletion and overwriting until the end of the retention period. The German GoBD (principles for proper electronic bookkeeping) permit both approaches, as well as organisational and software measures such as versioning and logging.
May I destroy paper after scanning?
In principle, yes, if the scanning process is documented in organisational instructions, the scans are complete and legible and no other regulations require the original. Guidance is provided by TR-RESISCAN of the German Federal Office for Information Security (BSI), with its protection requirements analysis, quality control and transfer note.
Do I need TR-ESOR for my company archive?
Not for most commercial records: the German GoBD (principles for proper electronic bookkeeping) do not require TR-ESOR conformity. Preservation of evidential value in accordance with TR-ESOR makes sense if you need to keep qualified signed documents valid as evidence over many years or if you are a public authority. The guideline secures evidential value via hash trees and renewed archive timestamps.
Can I transfer my old archive to enaio?
Yes. We migrate documents and metadata from legacy systems following a test migration with volume reconciliation and checksum comparison. Links and index data are transferred as well, so that the same evaluations remain possible. Data access for tax audits is preserved throughout.
Is the archiving software also available as a cloud solution?
Yes. enaio is available on-premises and in AWP Consult's cloud hosting. The data centres are located in Germany and are ISO 27001 certified. For tax purposes, retention in other EU member states is permitted under Section 146(2a) of the German Fiscal Code (AO), provided that full data access remains possible.
Not sure where to start? We will assess your starting position.
Which electronic archiving terms should you know?
In electronic archiving, you should above all know the terms that come up most often in requirements specifications, tenders and audits, from audit-proof and WORM to hash value, timestamp and Evidence Record, through to PDF/A, transfer note and metadata model. The following explanations summarise them briefly.
- Audit-proof
- Archiving that meets the principles of the German GoBD (principles for proper electronic bookkeeping) and the VOI: complete, unalterable, protected, retrievable and auditable. Not a legal term.
- WORM
- Write Once Read Many. Storage that keeps data read-only once it has been written, implemented in hardware or via software.
- Hash value
- Cryptographic fingerprint of a document. Even a minimal change results in a different value.
- Qualified timestamp
- Timestamp from a qualified trust service provider under eIDAS that proves the point in time at which data existed.
- Evidence Record
- Evidence data set in accordance with RFC 4998, consisting of a hash tree and archive timestamps, with which TR-ESOR proves integrity over the long term.
- PDF/A
- ISO 19005, series of standards for PDF files suitable for long-term archiving, in parts 1 to 4.
- Transfer note
- Documentation for a scan product under TR-RESISCAN: who scanned it and when, any anomalies and the result of quality assurance.
- Journaling
- Server-side copy of every email at the time of sending or receipt, before users can intervene.
- Metadata model
- Definition of the index fields per document class, with mandatory entries, sources and validation rules.
- Hierarchical Storage Management
- Automatic movement of data between fast and lower-cost storage tiers based on access frequency.
Sources and legal basis
The information on this page is based on the following official sources in the version applicable at the time of publication. It does not replace tax or legal advice in individual cases.
- Section 146 AO (German Fiscal Code): Rules on bookkeeping Legibility and availability of stored data, retention in other EU countries
- Section 147 AO (German Fiscal Code): Retention of records Retention on data carriers, periods, start of periods and data access
- Section 257 HGB (German Commercial Code): Retention periods Retention under commercial law, including commercial letters
- Section 14b UStG (German VAT Act): Retention of invoices Eight years for invoices
- GoBD amendment of 14 July 2025 Assessment by the German Confederation of Skilled Crafts (ZDH) with a link to the Federal Ministry of Finance letter, retention of e-invoices
- BSI TR-03125 Preservation of Evidence (TR-ESOR) Technical guideline of the German Federal Office for Information Security, version 1.3
- BSI TR-03138 Replacement Scanning (RESISCAN) Technical guideline for replacement scanning, version 1.5
Further topics
Your archive, central and audit-ready
In the archive consultation, we look at your current filing systems and legacy systems and show what an audit-proof archive with enaio could look like at your company.
- In person in Dietzenbach or online
- With business departments and IT
- Result: archiving concept and next step