agorum core

The Skeptic

Scanner, email and hot-folder intake into a central inbox, server-side OCR with full-text indexing, and a tagging-and-filing module are properly documented, and the Mistral OCR tool is documented as extracting structured information such as invoice data with its model provider named. But we found no public information on XRechnung or ZUGFeRD being read as structured data, on classification with a confidence value and a validation step, or on duplicate detection at intake — the e-invoice appears only as a module name with no description. 5 6 8 9 10

Report an error

The Skeptic

The versioning side is real and unusually detailed: automatic versioning with restore, edit locking producing one version per session, a permanently protected original, and change logging with timestamp and user. What we found no public information on is read and export events in the audit trail, directory sync or a described role model, and tamper-evidence or exportability of the log — and the captured pages describe the audit trail as gapless while also documenting configurable exclusions from historization. 2 7 8 11

Report an error

The Skeptic

Here the immutability mechanism is actually described rather than merely claimed: documents marked revisionssicher can neither be changed, deleted nor moved for the set period, the original version is permanently protected, retention is any number of years, and a sample Verfahrensdokumentation is offered to pro users. But we found no public information on an auditor's report or Testat, on deletion after retention expires, on legal hold, or on tax-audit data export — so the archiving claim rests on the vendor's own description alone. 7 9 10

Report an error

The Skeptic

The workflow editor is documented in genuine depth — versioned definitions with old versions kept runnable, subworkflows, test-then-deploy, process overview and log inspection — and the DATEV XML online handover is documented down to ledger types and ZIP contents, which is more scope than most vendors publish. SAP and Odoo appear only as interface module names with no stated scope, e-signature likewise only as a module name, and we found no public information on a documented REST API reference, webhooks, or Microsoft 365 integration. 2 8 11 12

Report an error

The Skeptic

Full-text, metadata and tag search on Solr with its own query syntax is documented, but we found no public information on saved searches or mobile access. The only export path we could find is the migration tool that moves data from one agorum core system into another — its stated use case is building a test system — with no documented open-format export of documents with metadata, versions and audit trail, and no word on a post-termination retrieval window or successor-system takeover. 13 14

Report an error

The Skeptic

We found no public information confirming the contracting entity's jurisdiction, the ownership, where the cloud edition stores documents and metadata, or any subprocessor list — the captured privacy policy covers website and applicant data, not the product's processing chain. An on-premises deployment option and a developed-in-Germany statement are the only signals, and the AI story depends on attachable models from OpenAI, Azure OpenAI or Mistral with the processing location unstated. 1 2 3 6 8

Report an error

The Skeptic

The pricing page discloses billing models and inclusions — cloud billed by volume and traffic including maintenance, backup, 50 GB volume and an SSL certificate, fixed or concurrent user licences, ALBERT billed by monthly token volume rather than per user — but we found no public price figure for any edition, module or maintenance, with module prices stated to be heavily project- and volume-dependent. A buyer can learn how they will be billed but cannot compute a single euro of it from these pages. 2 4

Report an error