whats-best.ai
Search Sign in

Document Management (DMS)

PaperOffice

Provenance unknown Report an error

Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: not determined

0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.

by PaperOffice · www.paperoffice.com

Report an error on this page Is this your product? →

Link to this page

PaperOffice: AI-assisted analysis on whats-best.ai PaperOffice: AI-assisted analysis on whats-best.ai (dark)

Add ?theme=dark to the image address for dark backgrounds. The badge shows the category and the month of the latest evaluation, and EU-Made where that is the product’s provenance. It never shows a score.

PaperOffice at a glance

Vendor
PaperOffice
Headquarters
Not stated on the vendor’s pages as of 20 Oct 2026
Data hosting
Default not stated; pages mention the EU source, captured 20 Oct 2026
Free plan
Not stated on the vendor’s pages as of 20 Oct 2026
Panel verdict
The AI panel rates PaperOffice 3/5, the mean of 6 judges. PaperOffice is a document management system from PAPEROFFICE ENTERPRISE OPERATIONS, S.L.U. how scores are made
As of
Vendor pages captured 20 Oct 2026; evaluated by the panel 21 Oct 2026. all sources

PaperOffice alternatives, European ones first →

Read this page as one judge. Each weighs the same scores by what they care about.

The Data Protection Officer

Weighted verdict

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.

Same scores as the panel view — this lens weights them the way this judge cares.

Scored by The Data Protection Officer

Panel median The Data Protection Officer This judge’s scores over the panel median. Each label opens its reasoning below.
Scores per criterion, in stars out of 5
Criterion Panel median The Data Protection Officer
Capture, OCR & indexing 4 of 5 4 of 5
Versioning, permissions & audit trail 3.5 of 5 3.5 of 5
Audit-proof archiving & retention 3 of 5 3.5 of 5
Document workflows & integrations 3 of 5 3 of 5
Search, retrieval & exit 3.5 of 5 3.5 of 5
European sovereignty 2.5 of 5 2.5 of 5
Pricing transparency 1.5 of 5 1.5 of 5

Capture, OCR & indexing

How this is scored

How documents get in and become findable: scanning and email intake, OCR, classification and metadata extraction, and whether incoming e-invoices (XRechnung, ZUGFeRD) are read as structured data rather than as pictures.

0 — Manual upload only; no OCR, no metadata beyond file name and folder.

3 — Upload, drag-and-drop and scan import with OCR mentioned, but indexing is manual and no word on email intake or e-invoice formats.

5 — Scanner, email and folder intake, full-text OCR, document types with metadata fields, and automatic extraction of common fields (date, sender, amount) documented.

8 — AI- or rule-based classification and field extraction with confidence and a validation step, XRechnung and ZUGFeRD read as structured data, mailbox and Microsoft 365 intake, and duplicate detection documented.

10 — Capture is engineered and shown: classification and extraction trainable per document type, validation queues, e-invoice validation against the standard, intake channels listed with their limits, and where AI processing runs (location, model provider) stated.

Report an error

The Data Protection Officer

Intake runs through a scanner inbox over SFTP, watched folders, a mailbox connector with stated intervals (the captured pages say Microsoft 365 OAuth sign-in is not supported yet), upload, API and webhook; OCR covers more than 120 languages, every field carries a confidence value, uncertain results go to a review list or quarantine, and duplicate detection is documented. E-invoices in XRechnung, ZUGFeRD and Factur-X can be created and validated against EN 16931, and — decisive for me — OCR and analysis run in the vendor's own EU data center. I found no public information on training the extraction per document type. 2 5 6 10

Report an error

Versioning, permissions & audit trail

How this is scored

Who may see and change which document, what happened to it, and whether earlier states can be recovered: version history, check-in and check-out, role- and attribute-based rights, and an audit trail of reads and changes.

0 — Files overwrite each other; rights only at folder level or not described; no log of who did what.

3 — Version history and folder permissions exist, but no check-out, no record-level rights and no documented audit log.

5 — Version history with restore, check-in and check-out, roles and groups with document-type or record-level rights, and an audit log of changes documented.

8 — Metadata-driven permissions (by department, client or confidentiality), audit trail covering reads, exports and deletions, single sign-on and directory sync (Entra ID, LDAP) documented, and administrators' own actions logged.

10 — Access is provable: the audit trail is tamper-evident and exportable, permission changes are themselves versioned, field-level rights and need-to-know access for HR or legal records documented, and the log retention period stated.

Report an error

The Data Protection Officer

Every revision is kept as its own version with a SHA-256 checksum, rights are set per workspace for users and groups at read, write and admin levels, and the audit trail records every access and every field change with person, time, old and new value — entries cannot be changed or deleted in the app or via API. For personnel files I found no public information on single sign-on or directory sync, on check-in and check-out, or on whether administrators' own actions and permission changes are themselves logged. 3 4 7 8

Report an error

Audit-proof archiving & retention

How this is scored

GoBD-compliant, revisionssicher archiving: immutability of archived documents, retention schedules and deletion, tax-audit data access, and the independent evidence behind the claim — scored on what is certified and documented, not on the word "GoBD-konform".

0 — No statement on archiving, retention or GoBD.

3 — "GoBD-konform" or "revisionssicher" claimed with no certificate, no description of how immutability is achieved and no retention settings documented.

5 — Archived documents documented as unchangeable, retention periods configurable per document type, deletion after expiry, and a sample Verfahrensdokumentation or GoBD guidance offered.

8 — An auditor's report (IDW PS 880 or comparable) published or named with its scope and date, WORM or equivalent storage described, legal hold, GDPR deletion reconciled with retention duties, and Z1–Z3 tax-audit export documented.

10 — Archiving is evidenced end to end: current Testat with scope covering the cloud and on-premises editions as sold, retention and deletion logged and reportable, long-term formats (PDF/A) enforced, and a documented procedure for the tax audit and for moving the archive without breaking its integrity.

Report an error

The Data Protection Officer

Sealed documents sit under WORM protection until the retention term ends, retention periods and legal basis are configured per document type with a chosen start date, the lift at term end is logged, a legal hold blocks deletion, and the GDPR access-request flow checks retention obligations first and exports redacted copies, with deletions documented in the audit trail. GoBD is named as a reference with the final assessment left to the tax advisor; I found no public information on an auditor's report such as IDW PS 880, on a Z1–Z3 tax-audit export, or on a sample Verfahrensdokumentation. 3 7 8 9

Report an error

Document workflows & integrations

How this is scored

What happens to a document after it arrives: approval and invoice workflows, tasks and deadlines, and the connectors that tie the DMS to ERP, accounting, DATEV, Microsoft 365 and the rest of the stack.

0 — No workflows; documents are stored and nothing else.

3 — A fixed approval or sharing step and a handful of named integrations, with no workflow designer and no API documentation.

5 — A workflow designer for approvals and invoice processing, tasks with deadlines and substitutes, Microsoft 365 or Outlook integration, and a documented REST API.

8 — Graphical workflow modelling without code, invoice workflow with ERP or DATEV handover documented, connectors for named ERP systems (SAP, Microsoft Dynamics, DATEV) with their scope, webhooks or events, and e-signature integration.

10 — Workflows are a platform: versioned workflow definitions, process reporting with throughput times, a public API reference with rate limits and a sandbox, a partner marketplace of integrations with stated maintainers, and workflow history kept in the audit trail.

Report an error

The Data Protection Officer

Intake, filing and follow-ups run as rule-based Workflow Agents with approvals up to two-person confirmation, signed webhook events with retries, e-signature support, and a REST API whose endpoints and limits are published alongside an MCP server. I found no public information on graphical workflow modelling or an invoice handover to ERP or DATEV, and the captured pages state that Microsoft 365 OAuth sign-in for the mailbox connector is not supported yet. 2 4 10 11

Report an error

Search, retrieval & exit

How this is scored

Finding documents again and taking them with you: full-text and metadata search, saved searches and mobile access, and whether documents, metadata, versions and audit trail can be exported in documented formats when the contract ends.

0 — Folder browsing only; no export beyond downloading single files.

3 — Full-text search exists, but no metadata filters, and bulk export is undocumented or only on request.

5 — Full-text and metadata search with filters and saved searches, mobile or web access, and bulk export of documents with their metadata (for example CSV or XML) documented.

8 — Search across versions and attachments with permissions respected, export of documents in original format with metadata, versions and audit trail in a documented structure, and an import path from other DMS or file shares named.

10 — The exit is designed in: a documented complete export with schema, export available self-service at any time, the post-termination retrieval window and data deletion stated, and archives stored in open formats so a successor system can take them over intact.

Report an error

The Data Protection Officer

Search spans full text, OCR text and semantics with saved searches, filters for workspace, document type and period, permissions respected, and a mobile app with voice input; metadata of selected documents exports as Excel, CSV, JSON or PDF with originals and OCR text, and an import path via SFTP, S3, WebDAV or ZIP is named. For the exit I found no public information on exporting versions and the audit trail in a documented structure, on a self-service complete export, or on the post-termination retrieval window and data deletion. 8 9 12 13

Report an error

European sovereignty

How this is scored

Who the contracting entity and its owner are, where documents and their metadata are stored and processed in the cloud edition, and who the subprocessors are — including any AI provider that reads document content. Independently sourced by the sovereignty pipeline.

0 — Non-EU contracting entity, no statement on where documents are stored, and subprocessors unnamed.

3 — An EU entity contracts, but the cloud edition runs on a non-EU-controlled hyperscaler without a stated safeguard, or the subprocessor list is absent.

5 — EU contracting entity and EU data centres stated for the cloud edition, with a DPA, but significant parts of the chain (hosting, AI processing, support) are non-EU-controlled without a stated safeguard.

8 — EU entity, documents and metadata stored in named EU data centres, subprocessor list with locations published, AI processing location disclosed, an on-premises or private-cloud option offered, and certifications (ISO 27001, BSI C5) published.

10 — Sovereign end to end and evidenced: European ownership, EU entity, every processing location and subprocessor European, customer-controlled keys or on-premises operation available, and certifications with their scope published.

Report an error

The Data Protection Officer

The contracting party is a Spanish S.L.U., capture, storage, index and embeddings are stated to run in the vendor's own EU data center with no US cloud, and ISO 27001 certification is published — which answers where personnel files and customer contracts are read. I found no public information on the subprocessors, on a data processing agreement, on a named data-centre site or on the company's ownership. External AI assistants — Claude, ChatGPT, Grok and Le Chat — are offered direct archive search with nothing published about that processing chain, while a US office in San Jose handles sales and support. 2 5 8 11 13

Report an error

Pricing transparency

How this is scored

Whether a buyer can compute the cost of a given number of users, storage and modules — including cloud versus on-premises licensing, maintenance, implementation partner fees and price increases — from public pages alone.

0 — No public prices at all; every quote comes from sales or a partner.

3 — A "from" price or a single edition priced, but modules, storage, maintenance and partner implementation are unstated — the real cost is unknowable.

5 — Editions priced per user or per month, but at least one commonly needed cost (storage, archiving or workflow module, maintenance percentage, onboarding) is missing or "on request".

8 — Every edition and module priced publicly, storage limits and overage stated, on-premises licence and maintenance terms given, and contract term and notice period published.

10 — Complete cost computability: a configurator or price list covering users, modules, storage and deployment model, partner implementation priced or bounded, and price-increase terms on a public page.

Report an error

The Data Protection Officer

Public prices cover only processing units: OCR at $0.01 per page for basic, $0.02 for premium and $0.03 for ultra, and an API billed in credits — plans named Basic, Premium, Ultra and Corporate appear with search depth tied to them but with no per-user or per-month price. For storage, maintenance, contract term, notice period and price increases I found no public information, so the cost of a given team cannot be computed from the public pages. 5 7 12

Report an error

European sovereignty — proven facts

0 of 4 dimensions proven

Built only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.

Ownership Not determined — uncited Report an error
Data residency Not determined ⚠ unverified — uncited Report an error
Subprocessors Not determined ⚠ unverified — uncited Report an error

Questions about PaperOffice

Is PaperOffice European?

Not determined: the vendor’s pages as captured do not say where PaperOffice is based.

Where does PaperOffice store data?

The default storage location for customer data is not stated on the vendor’s pages as of 20 Oct 2026. The vendor’s pages mention the EU as hosting location, per the vendor’s page captured 20 Oct 2026.

Does PaperOffice have a free plan?

Not stated on the vendor’s pages as of 20 Oct 2026.

What are the best alternatives to PaperOffice?

As of 21 Oct 2026, the panel rates AMAGNO (3/5), Doxis (3/5) and EASY Archive (2.5/5) highest among the other 17 Document Management (DMS) products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is AMAGNO (EU-Made). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: PaperOffice alternatives.

Where this could be wrong

What we left out

A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.

Do you know more about PaperOffice? Tell us Report an error on this page

Sources (13)

The pages every claim on this page was read from — each one checked, dated, and kept verifiable.

  1. 1 Vendor page www.paperoffice.com Checked 20 Oct 2026 Details →
  2. 2 Legal notice — found from the homepage paperoffice.ai Checked 20 Oct 2026 Details →
  3. 3 Privacy policy — found from the homepage paperoffice.ai Checked 20 Oct 2026 Details →
  4. 4 Security / trust page — found from the homepage paperoffice.ai Checked 20 Oct 2026 Details →
  5. 5 Capture, OCR & indexing — found from sitemap paperoffice.ai Checked 20 Oct 2026 Details →
  6. 6 Capture, OCR & indexing — found from sitemap paperoffice.ai Checked 20 Oct 2026 Details →
  7. 7 Versioning, permissions & audit trail — found from sitemap paperoffice.ai Checked 20 Oct 2026 Details →
  8. 8 Audit-proof archiving & retention — found from sitemap paperoffice.ai Checked 20 Oct 2026 Details →
  9. 9 Audit-proof archiving & retention — found from sitemap paperoffice.ai Checked 20 Oct 2026 Details →
  10. 10 Document workflows & integrations — found from sitemap paperoffice.ai Checked 20 Oct 2026 Details →
  11. 11 Document workflows & integrations — found from sitemap paperoffice.ai Checked 20 Oct 2026 Details →
  12. 12 Search, retrieval & exit — found from sitemap paperoffice.ai Checked 20 Oct 2026 Details →
  13. 13 Search, retrieval & exit — found from sitemap paperoffice.ai Checked 20 Oct 2026 Details →