The digital archive for decommissioned ERP data in insolvency proceedings.
pretor.io takes custody of an insolvent company's accounting and operational data the moment its ERP system is decommissioned, and preserves it GoBD-compliant for the full statutory retention period. Queryable, exportable, jointly worked. The Insolvenzverwalter, the firm's associates, the Steuerberater and the Finanzamt collaborate on the same archive — under role-based access and a complete audit trail.
Evaluation equivalence5 years post-decommissioning
Hand-overZ3 · DATEV · PDF
sha-256 hash chain
Four duties. One archive.
pretor.io carries the Insolvenzverwalter's duties under § 155 InsO read together with § 257 HGB and § 147 AO from data intake through to handover to a Betriebsprüfer or Steuerberater.
Ingest
Pre-built connectors for SAP, Microsoft Dynamics 365 Business Central, Microsoft Dynamics and DATEV. Generic intake for GDPdU- and IDEA-compatible exports. AI-assisted schema mapping for unknown source systems, with every mapping reviewed before commit.
§ 155 InsO · ERP decommissioning
Archive
Hash-chained, append-only storage with WORM-equivalent immutability. Per-record retention timers — 10 years for books, 8 years for Buchungsbelege, 6 years for other records — under the BEG-IV adjustment.
§ 257 HGB · § 147 AO · GoBD Unveränderbarkeit
Query
Evaluation-equivalent access throughout the first five years after decommissioning: table view, column filter, sort, joins across the canonical model. Natural-language queries with citation back to the source journal entry. Anomaly and Anfechtung-window pre-screening — the AI surfaces evidence, it does not draw legal conclusions.
GoBD Rz. 142 · §§ 130, 131, 133, 134 InsO
Hand over
On demand: Z3 packages per GDPdU Beschreibungsstandard 01.08.2002 (gdpdu-01-08-2002.dtd, index.xml, table CSVs in Windows-1252, IDEA-validated), DATEV-Format Buchungsstapel v7.0 with EXTF header for the Steuerberater, signed PDF evidence dossiers for Anfechtung work.
An insolvency case unfolds in six legally-determined phases. pretor.io carries them through — from the first day of the case until the retention duty ends.
1
Phase 1Day 0–1
Provisioned
Case file created, Verwalter invited. Empty vault, six tabs visible.
2
Phase 21–3 weeks
Initial ingest
Debtor's ERP is decommissioned. On-site bot or file upload. Once sealed, the ERP server can be switched off — Massekosten stop accruing.
3
Phase 32–24 weeks
Wind-down
Verwalter operates the company briefly through the Steuerberater's existing DATEV. pretor.io is inert for new data; Anfechtung work proceeds on the sealed archive.
4
Phase 4Until Aufhebung
Live archive
Full access: query, anomaly screening, Z3 and DATEV exports. Steuerberater and Finanzamt-Prüfer join as scoped read-only guests.
5
Phase 5Through year 5
Quiet archive
Evaluation equivalence under GoBD Rz. 142 is preserved. Less frequently touched, but always queryable.
6
Phase 6Year 6 to 10
Z3 only
From the 6th year onward, Z3 alone discharges the duty under GoBD Rz. 148. Infrastructure collapses to storage plus exporter — until retention ends.
Every entry. Hash-chained. Verifiable.
Books carry a ten-year retention duty; Buchungsbelege carry an eight-year duty after the BEG-IV reform, other records subject to the duty carry six. pretor.io commits every record append-only and chains it cryptographically — the original content remains identifiable at all times in the sense of the GoBD Unveränderbarkeit requirement.
In an Außenprüfung the Insolvenzverwalter delivers a Z3 package per Beschreibungsstandard 01.08.2002. Evaluation equivalence under GoBD Rz. 142 is preserved through the first five years after decommissioning; from the sixth year onward the Datenüberlassung alone discharges the duty under GoBD Rz. 148.
15:08:31 14.05.2026System Generated Z3 package per Beschreibungsstandard 01.08.2002 for FA Düsseldorf-Süd. pkg:7a3b1f9c…4e02
Intelligence layer
Evidence on the table — the call stays with the Verwalter.
Every ingested record is run through a forensic pre-screen automatically. pretor.io surfaces anomalies and Anfechtung candidates. The legal conclusion stays with your firm.
Source-record citationEvery hit links back to the original journal entry inside the sealed archive.
Evidence dossierSigned PDF, ready to send to the opposing party — never a legal verdict.
What sets us apart from classical archives
One archive. Many hands. A full audit trail.
Classical archive solutions deliver a static dataset operated by external consultants. pretor.io provides a live archive your firm operates itself.
Insolvenzverwalter and associates work concurrently on the same archive. Steuerberater and Finanzamt-Prüfer join as scoped guests — read-only, time- and subject-bounded. Every login, every query, every export is recorded server-side and feeds directly into the Verfahrensdokumentation.
Multi-userRole-based access per case: Verwalter, associate, guest.
Real-time syncChanges are immediately visible to all collaborators — no reload required.
External guestsSteuerberater and Finanzamt with time-bounded read access.
Audit trailMaintained server-side, part of the Verfahrensdokumentation.
Clear scope
What pretor.io is — and is not.
pretor.io is
A GoBD-compliant archive for decommissioned ERP data.
A collaborative platform for Verwalter, associates, Steuerberater and Finanzamt.
An intelligence layer for anomalies and Anfechtung evidence.
A handover surface for Z3, DATEV-Format and PDF dossiers.
pretor.io is not
Not case management — Winsolvenz, RA-MICRO, STP remain your tools.
Not a Forderungstabelle SaaS and not an ELSTER bridge.
Not a beA send/receive surface — § 130d ZPO traffic stays with you.
Not legal advice — the legal call always stays with the Verwalter.
Compliant with GoBD
Data handover GDPdU Z3 · Beschreibungsstandard 01.08.2002
Data protection Art. 28 GDPR · processing within the EU
Hosting German data centre · ISO 27001 certified operator