Document Management (DMS)

The GoBD Auditor v1.0

Has sat through tax audits on the company side and knows that "GoBD-konform" on a homepage proves nothing. Wants the auditor's Testat with its scope and date, archived documents that cannot change, retention per document type, and a Z3 export the tax office can read.

The Records Manager v1.0

Owns the filing plan and gets the call when a contract from 2019 cannot be found. Wants metadata that is set at capture rather than typed later, version history with restore, search that respects permissions, and a bulk export that keeps metadata and versions together.

The IT Integrator v1.0

Connects the DMS to the ERP, DATEV and Microsoft 365 and maintains it afterwards. Wants connectors with a stated scope rather than a logo wall, a documented API with webhooks, single sign-on, and a migration path in and out that does not depend on the vendor's services team.

The Mittelstand Owner v1.0

Runs a forty-person company and wants the paper out of the office and the invoices approved without chasing anyone. Reads for e-invoice intake, an approval workflow that works without a consultant, and a price for users, storage and modules before the partner visit, not after.

The Data Protection Officer v1.0

Knows the DMS ends up holding personnel files, health certificates and customer contracts in one place. Asks where the cloud edition stores them, which AI provider reads them during capture, who the subprocessors are, and how GDPR deletion is reconciled with retention duties.

The Skeptic v1.0

Has read "revisionssicher" on every DMS homepage and a Testat on almost none. Distrusts "AI-powered capture" without a validation step, "seamless SAP integration" without a scope, and "no vendor lock-in" from a vendor that documents no export — and treats "price on request from your partner" as an answer.