Three vendors, three presentations, three times the words “audit proof” on the first slide. Plus certificate logos, reference lists and the promise to cover all legal requirements. That is what a typical selection process for audit proof archiving software looks like. And that is exactly where the problem begins.
Because audit proof is not a protected product property. No law defines which software may carry this label, and no authority awards a seal for it. The GoBD, the German principles for keeping books and records electronically, explicitly make proper electronic retention dependent on the interplay of software, configuration, processes and procedural documentation. Software can enable audit proof archiving. It cannot guarantee it.
In selection projects with IT managers and compliance officers from manufacturing, medical technology and mechanical engineering, the same pattern appears again and again: decisions are made based on certificate logos and license price. The questions that actually matter in an audit or a liability case never make it into the requirements specification. Who will read the data in 15 years when the vendor ends support? Can the business unit access it without an IT ticket? Can the legacy system really be shut down after migration?
This article provides the requirements catalog for your selection: 12 criteria that audit proof archiving software must be measured against, the 5 most common selection mistakes and an honest look at the costs.
- Audit proof is not a certifiable product property. The GoBD require the interplay of software, configuration, processes and procedural documentation. A vendor certificate alone proves nothing in an audit.
- A software certificate according to IDW PS 880 checks the product, not your operation. Without up to date procedural documentation according to GoBD margin no. 151 et seq., even certified software remains vulnerable in an audit.
- The 12 selection criteria fall into three groups: legal (immutability, logging, proof of deletion), technical (open format, vendor independence, access without IT) and economic (migration, operation, application retirement).
- The most expensive selection mistake is a proprietary archive format: the data is archived but can no longer be read after a vendor change or the end of support. Retention periods of ten years and more outlast many software products.
- Cost effectiveness rarely comes from the license price but from follow up effects: smaller production databases, retired legacy systems, less load on IT.
Criteria, not logos
Select based on a written catalog with legal, technical and economic criteria.
Readable without the vendor
Is the data readable without the vendor’s software? If not, you only shift the risk.
Calculate total costs
Migration, operation and retired legacy systems decide, not the license price.
01 · Basics
Why can no software alone guarantee audit proof archiving?
The market suggests that audit proof archiving can be bought, installed and ticked off. Legally, that does not work, and anyone who builds the selection process on this assumption checks the wrong things.
The decisive rules are the GoBD (German Federal Ministry of Finance letter of 28 November 2019, last amended on 14 July 2025). They tie proper electronic retention not to a product but to the overall procedure: how is data created, indexed, stored, protected against changes and reproduced throughout the entire period? This is exactly what the procedural documentation according to GoBD margin no. 151 et seq. must describe in a traceable way. If it is missing or outdated, the bookkeeping can be formally objected to, regardless of how good the software is.
Software certificates according to IDW PS 880 are common in Germany: an auditor certifies that a product can meet the requirements when used properly. That is a useful signal in the selection process but not a free pass. The certificate checks the product in its initial state, not your configuration, your processes and your documentation.
| Proof | What it shows | What it does not show |
|---|---|---|
| Software certificate (IDW PS 880) | The product can meet the requirements when used properly | That your specific operation, configuration and processes are compliant |
| Vendor claim “audit proof” | A marketing statement without a legally defined basis | Nothing binding. The term is not protected and is not awarded by any authority |
| Procedural documentation (GoBD margin no. 151 et seq.) | The traceable overall procedure from creation to reproduction of the data | It must be maintained. Outdated documentation is almost as critical in an audit as missing documentation |
In German tax audits, the procedural documentation is regularly requested first, not the certificate. And the retention periods set the benchmark for software selection: under Section 147(3) of the German Fiscal Code (AO), books and annual financial statements must be kept for ten years, accounting vouchers for eight years and commercial and business letters for six years. For quality records, IATF 16949 (section 7.5.3.2.1) requires retention for the duration of production and service requirements plus one calendar year, unless the customer or a regulatory agency specifies longer. For implantable medical devices, Article 10(8) MDR requires 15 years. Your archiving software must support a procedure that survives several hardware generations, system changes and probably one or two vendor changes.
For your selection, this means: do not check whether a vendor uses the words audit proof. Check whether the software can support the procedure you have to document.
Why a backup has long been not enough
The white paper explains why a backup does not meet the GoBD and what audit proof archiving must deliver.
02 · Criteria
Which 12 criteria matter when selecting software?
A robust requirements specification separates three levels: legal criteria that determine audit readiness, technical criteria that determine daily usability and long term readability, and economic criteria that determine total costs. For each criterion, there is a question you should put to every vendor in writing.
Legal
| No. · Criterion | Why it matters | Question for the vendor |
|---|---|---|
| 1 · Immutability | The GoBD and Section 257 of the German Commercial Code (HGB) require that archived data cannot be changed or deleted unnoticed | How is immutability enforced technically, and can the protection be bypassed administratively? |
| 2 · Complete logging | Without an audit trail, integrity cannot be proven in an audit | Is every operation logged with user, time stamp and content, and is the log itself protected against manipulation? |
| 3 · Retention periods and proof of deletion | Articles 5 and 17 GDPR require personal data to be deleted once its purpose ends, including proof. Under Article 83 GDPR, violations can cost up to 20 million euros or 4 % of worldwide annual turnover | Can retention and deletion rules be stored per data category, and does deletion produce auditable proof? |
| 4 · Completeness and evaluability | The GoBD require complete and machine evaluable retention, not just storage | How is the completeness of the transfer proven, and does the data remain evaluable in a structured way? |
Technical
| No. · Criterion | Why it matters | Question for the vendor |
|---|---|---|
| 5 · Open, documented archive format | Periods of ten years and more outlast many software products. Proprietary formats make data unreadable after the end of support | Is the archived data fully readable without your software, and is the format disclosed? |
| 6 · Vendor independence | Source systems change. Archiving must not depend on a single database or ERP | Which source systems are supported: Oracle, SAP, MS SQL, cloud, own data center? |
| 7 · Search without an IT ticket | If every access runs through IT, the archive is not used in daily work and becomes a bottleneck in audits | Can business units search independently and based on roles? |
| 8 · Scalability and performance | A large share of the data in production databases is inactive. The archive must absorb this volume permanently | How does search speed behave as the archive grows over the years? |
| 9 · Interfaces and automation | Archiving must run based on rules, not as a manual special process | Which interfaces exist, and can archiving runs be automated based on rules? |
Economic
| No. · Criterion | Why it matters | Question for the vendor |
|---|---|---|
| 10 · Application retirement | Legacy systems that keep running only for data access cost licenses, maintenance and security effort | Can the complete data stock of a legacy system be transferred so that the system can be shut down? |
| 11 · Migration effort and project duration | An archiving project that ties up IT for months eats up the savings | How long does a typical project take, and which internal resources are needed? |
| 12 · Operating and maintenance costs | The solution runs for decades. Ongoing costs outweigh any one time price advantage | Which costs arise in operation: maintenance, storage, administration, updates? |
Knockout criterion
Criterion 5 decides. If the archived data can only be read with the vendor’s software, you trade dependence on the legacy system for dependence on the archive vendor. That is not a solution, it is a shift.
When software can be operated in an audit proof way
✓Procedural documentation according to the GoBD exists and is updated with every process change.
✓A role and permission concept governs who archives, searches and manages retention periods.
✓The archive format is openly documented and readable without the vendor’s product.
✓The audit trail is active and cannot be switched off, not even by administrators.
✓Retention and deletion rules are stored per data category, including proof of deletion.
✓Archived data can demonstrably be reproduced without the source system.
03 · Mistakes
What are the 5 most common selection mistakes?
Most wrong decisions do not happen in the technology but in the selection process itself. Five patterns appear again and again in practice.
The certificate replaces the requirements specification
A vendor presents a certificate, and the individual criteria are never checked. A certificate according to IDW PS 880 certifies the product, not your operation. It replaces neither the 12 vendor questions nor the procedural documentation. Treat the certificate as an entry ticket to the selection round, not as its result.
Backup and archive are treated as the same
A working data backup exists, so the topic seems settled. A backup serves to restore data after a loss and is overwritten in fixed rotation cycles. It can be changed, is not logged and is not designed for targeted access to individual records over ten years.
Proprietary archive format
The most expensive mistake, because it only becomes visible after years. The data is properly archived, but the vendor discontinues the product, is acquired or changes its licensing model. Over a retention period of ten years and more, it is likely that at least one of these events will occur. Without an open format, you then face a second migration, under time pressure and without alternatives.
The business units are missing from the selection
IT selects, but quality, controlling and purchasing do the work. If nobody there can search independently, every request from authorities, every audit preparation and every complaint ends up as an IT ticket. That costs time in both departments and turns the archive into an unloved special case.
Application retirement is not considered
Many archiving projects start because of a specific legacy system but only solve the data question and keep the system running for compliance reasons. License, maintenance and infrastructure costs remain, plus the security risk of unpatched software. Defining the shutdown as a project goal from the start unlocks the biggest cost lever of the entire investment.
04 · Costs
What does audit proof archiving software cost?
There are no serious flat rates, because costs depend on data volume, the number of source systems and the scope of migration. What can always be described is the structure: three cost blocks on one side, three savings levers on the other.
Cost blocks
- Implementation project: analysis, migration, testing, procedural documentation
- License
- Ongoing operation: maintenance, storage, administration
Savings levers
- Smaller production databases with lower storage costs and shorter recovery times
- Retired legacy systems: licenses, maintenance and infrastructure are eliminated
- Less load on IT because business units search themselves
Based on CSP’s experience, a CHRONOS implementation typically takes 6 to 12 weeks, depending on the scope of the system, and the existing infrastructure usually does not need to be changed.
Frequently underestimated cost factors
☐Data cleansing before migration: duplicates, test data and orphaned records in the legacy system extend every project.
☐Procedural documentation: creating and maintaining it costs internal time or external consulting, but it is not negotiable.
☐Interfaces to exotic legacy systems: standard connectors do not cover every historically grown custom development.
☐Parallel operation during the transition: legacy system and archive run simultaneously during validation.
☐Training for business units: without onboarding, access without an IT ticket remains theory.
☐Storage growth over the retention period: long retention means predictable but steady growth of the archive.
In CHRONOS customer projects, these savings add up to an ROI of over 300 %, usually reached within a few months.
The honest calculation is therefore not “What does the license cost?” but “What does the current situation cost per year, and how much of it disappears after the project?”. For companies with legacy systems still running, this calculation almost always favors archiving.
Check the 12 criteria on a real system
In a free live demo, we show you how CHRONOS archives, logs and retires legacy systems.
05 · Solution
How does CHRONOS meet the 12 criteria?
CHRONOS is the archiving module in the Manufacturing OS from CSP Intelligence GmbH. The Manufacturing OS also includes IPM for process data management, PG for worker guidance and QST for tool testing. Within it, CHRONOS handles audit proof long term archiving and the shutdown of legacy systems.
CHRONOS identifies inactive data based on rules, converts it into an open format suited for long term storage and moves it to storage systems. Production databases become smaller and faster as a result. With application retirement, the complete data stock of a legacy system can be transferred so that the application can be shut down completely. Business units search based on roles and without an IT ticket, regardless of whether the source was Oracle, SAP or MS SQL and whether the environment runs in the cloud or in your own data center.
Audit proof
Compliant with the GoBD, the German Commercial Code and the GDPR, protected against manipulation and audit ready.
Open format
Long term readability independent of software vendors and licensing models.
Application retirement
Shut down legacy systems completely, legally sound and economically sensible.
Access without an IT ticket
Business units search independently and based on roles.
Vendor independent
Oracle, SAP, MS SQL, cloud or own data center, without system breaks.
6 to 12 weeks
Typical implementation time, depending on the scope of the system.
An example from medical technology: the KLS Martin Group, a manufacturer of surgical instruments and implant systems, faced an inconsistent archive landscape with growing data volumes after several mergers. With CHRONOS, data from legacy systems is now stored in an open format in an audit proof way, and the software landscape has been consolidated. Read more in the KLS Martin success story.
Customer voice
“Our collaboration with CSP is going exceptionally well. Deadlines are met, and everything runs smoothly.”
Wojciech Wypior, Head of Business Applications, KLS Martin Group
FAQ
Frequently asked questions
Which software is suitable for audit proof archiving?+
Suitable software enforces immutability technically, logs every operation without gaps, manages retention and deletion periods per data category and stores data in an open, documented format. It is also crucial that archived data remains readable without the vendor’s software and without the source system. Audit proof archiving only results from the interplay of software, configuration and procedural documentation according to the GoBD. A product name or a certificate alone is not sufficient proof.
Is there an official certification for audit proof archiving software?+
No. No authority awards a statutory seal for audit proof archiving, and the term is not legally protected. Software certificates according to IDW PS 880 are common in Germany: an auditor certifies that a product can meet the requirements when used properly. This certificate checks the product, not how it is operated in a specific company. For proof in an audit, the procedural documentation according to GoBD margin no. 151 et seq. remains decisive.
Is a document management system automatically audit proof?+
No. A document management system organizes documents and workflows but does not automatically guarantee immutability, complete logging and long term readability over many years. Many systems can be configured to be audit proof, but they are not in their delivered state. They also often do not cover structured data from databases and legacy systems. Specialized archiving software is required for database archiving and application retirement.
Does a backup meet the requirements for audit proof archiving?+
No. A backup serves to restore data after a loss and is overwritten in fixed rotation cycles. It can be changed, is not logged and is not designed for targeted access to individual records over statutory periods of six to ten years. The GoBD require immutable, complete and machine evaluable retention. A backup structurally does not meet these requirements, regardless of its technical quality.
What does audit proof archiving software cost?+
Costs depend on data volume, the number of source systems and the scope of migration; there are no serious flat rates. In addition to the license, there is the implementation project, the procedural documentation and ongoing operation. These are offset by savings: smaller production databases, lower storage costs and legacy systems that can be shut down completely. In CHRONOS customer projects, the ROI is over 300 %, and implementation typically takes 6 to 12 weeks.
Can archiving software be used to shut down legacy systems completely?+
Yes, if the software supports application retirement. The complete data stock of a legacy system is transferred into an open format, archived in an audit proof way and kept searchable. The legacy system can then be decommissioned, and license, maintenance and infrastructure costs are eliminated. This requires that all data subject to retention, including context and metadata, is transferred and that retrieval is documented.
Choose archiving software by criteria, not by logos
Ask us the 12 vendor questions. In a live demo, we show how CHRONOS answers them.
Responsible for strategy and innovative software solutions for the manufacturing industry.