How to choose a document management system: a guide for European companies

Short answer: Choose a document management system (DMS) from your documents and processes, not from feature lists. Write down which document classes you manage, who works on them, which ERP and Microsoft 365 set-up they touch, which countries' e-invoicing and retention rules apply, and where the data may be hosted. Turn that into a handful of must-have criteria, shortlist three to five vendors that evidence them in public sources, ask every vendor to price the same scenario over three to five years, and test the best one or two with your own documents before you sign. On 3 October 2026, 44 of the 83 vendors in our directory had a checked data sheet you can filter by exactly these criteria.

Most advice on choosing a DMS ends in a list of features that every product claims: full-text search, workflows, mobile apps. Those rarely decide a project. What decides it in Europe is where the data is hosted, whether the system fits your ERP, how it handles structured e-invoices, whether its archive will satisfy a tax auditor in each of your countries, and what it really costs once services are added. This guide takes those decisions in the order that saves the most time and links to the detailed guides in this series on what a DMS costs, SharePoint as a DMS and ERP integration.

Vendor numbers come from our checked data sheets, which record every value with a link to the public source and a check date; vendor facts were checked between 1 and 3 October 2026, and the counts below were taken on 3 October 2026. Legal statements are linked to the law or the tax authority. Where a data sheet says “no public information”, that means we found nothing public, not that a function is missing.

What is a document management system, and what is it not?

A document management system (DMS) stores documents with structured metadata, controls access, keeps versions, finds documents and moves them through workflows, and keeps records unaltered until their retention period ends. A DMS keeps documents together with structured descriptions of them: document type, date, business partner, legal entity, amount, contract or order number. On that basis it controls access, keeps versions, finds documents by content and metadata, moves them through workflows such as invoice approval, and keeps records unaltered until their retention period ends. The last point separates a DMS used for finance and HR records from a file share: a file share stores files, while a DMS also knows which rules apply to each of them.

“Document management” is sold under several labels, and they overlap. Our data sheets classify each vendor by what it mainly offers. Of the 44 vendors with a checked data sheet on 3 October 2026:

Type	Count	What it usually covers	Examples from the directory
Document management system	20	Filing, metadata, search, workflows, archive; often an invoice module	DocuWare, M-Files, ecoDMS
ECM platform	14	Broader content platform for larger organisations, many modules and integrations	d.velop, ELO, OpenText
Specialist	6	One process, such as accounts payable or HR files	Yooz, Medius, aconso (HR)
Platform	2	Content and collaboration platforms often compared with a DMS	Microsoft SharePoint, Box
Part of accounting software	2	Document storage tied to one accounting product	DATEV DMS, Zucchetti

The type is a starting point, not a verdict. An accounts payable specialist can be the right choice if invoices are the reason for the project; an ECM platform can be too much for 30 users. If most of your documents are project files and policies in Microsoft 365, read first where SharePoint is enough and where it falls short.

Step 1: describe your documents and processes

The first step in choosing a DMS is an inventory of your document classes, users, legal entities, systems and constraints. Requirements written as feature wishes (“must have OCR”) produce offers that all say yes. Requirements written as facts about your documents produce offers you can compare. Before you look at a single product, collect five things.

Document classes. List each kind of document you manage: inbound invoices, outbound invoices, contracts, delivery notes, HR files, correspondence, technical documents, quality records. For each, note how many arrive per month, in which form (paper, PDF by e-mail, structured e-invoice, export from another system), who owns it, which system it relates to and how long it must be kept.

Users by role. Count full users who file and process documents, occasional users who approve or look things up, read-only users such as management or auditors, and external parties. Licence models price these groups very differently, as the cost guide shows.

Legal entities and countries. Each legal entity has its own tax obligations. A group with a German subsidiary, a Belgian sales company and a Polish plant has three retention rules and three e-invoicing regimes, and the system must separate the entities cleanly. Sixteen of the 44 checked data sheets state that the system manages several legal entities in one installation; for 24 we found no public information.

Systems. ERP or accounting software (and its version and deployment), Microsoft 365 plan, e-mail, scanners, e-invoicing provider, HR software. Integration effort sits here.

Constraints. Hosting rules from your data protection officer or customers, IT capacity for running servers, budget, deadlines such as an e-invoicing date in one of your countries.

• Document classes with volumes, sources, owners and retention
• Users by role: full, occasional, read-only, external
• Legal entities and countries, each with its e-invoicing and retention rules
• ERP, accounting, Microsoft 365 and e-invoicing provider, with versions
• Hosting and data protection constraints
• Budget, deadlines and who decides

From this inventory, separate must-haves from nice-to-haves. Keep the must-haves short, ideally under ten, and phrase each so a vendor can prove it with a document or a demo: “stores Peppol BIS invoices in their original XML and displays them readably” is testable, “supports e-invoicing” is not.

Step 2: where should the system run?

Deployment is the first filter because it changes almost everything else: who updates the software, how costs are spread, where the data sits and how the ERP is connected.

Most vendors offer more than one model. On 3 October 2026, 42 of the 44 checked data sheets showed a cloud service, 37 software for own servers and 19 a hybrid set-up. Some are cloud-only by design: the data sheets record “No” for own servers at Box and Yooz. For others the question is open: for Basware, Esker and Medius, among others, we found no public information on operation on your own servers.

Own servers (on-premises)

• Data and update timing stay in your hands
• Licence often one-off, plus maintenance
• Hardware, backup, monitoring and patches are yours
• Simple to connect to an ERP that also runs in-house
• Cloud services, such as AI capture, may still be called from outside

Cloud service

• Vendor operates, updates and backs up the system
• Subscription per user, volume or entity, every month
• Hosting country and operator need checking
• Faster start, fewer internal IT tasks
• Exit terms and data export matter more

Two details are easy to miss. First, “on-premises” does not always mean every function runs on your servers. According to their data sheets, PROXESS offers AI document extraction and posting suggestions as a cloud service even when the system runs on your own servers, and Starke-DMS’s AI invoice recognition is based on Microsoft Azure Document Intelligence. Ask where each function processes data. Second, cost comparisons only work over the same period: a subscription looks cheap in year one, a perpetual licence in year five. Compare at least three years, preferably five.

Step 3: check hosting location, data protection and security evidence

For a cloud DMS, three questions matter: in which country the data is stored, who operates the infrastructure, and what evidence the vendor shows for its security.

Hosting country. Of the 44 checked data sheets, 34 name at least one hosting location, and each of these 34 names at least one location in Europe; 23 name Germany, 13 of them Germany only. For ten vendors we found no public statement on the hosting location. The wording varies more than the counts suggest. DocuWare’s data sheet records data centres in the EU on Microsoft Azure without the country, ELO’s “certified European data centres” without country or operator, and Box offers its storage zones in the EU and other regions from the Enterprise Plus plan. If the country matters to you, ask for it in the contract.

Data protection. A cloud DMS processes personal data on your behalf, in invoices, contracts and especially HR files. Article 28 of the GDPR requires a contract with the processor that covers, among other points, instructions, confidentiality, security measures, sub-processors, and deletion or return of the data at the end. Article 5(1)(e) limits storage to what is necessary, which is why a DMS needs controlled deletion once retention ends; Article 17(3)(b) keeps the statutory retention duty intact against erasure requests. Ask for the vendor’s processing agreement and sub-processor list with the offer.

Tax rules on storage location. Tax law adds its own conditions. Germany allows electronic storage of invoices elsewhere in the EU with full online access for the tax office, but storage outside the EU needs approval on application (§ 146(2b) AO); France and Spain attach declaration or prior-notice duties to storage abroad. Our guide to e-invoice archiving requirements has the rules for eight countries.

Security evidence. On 3 October 2026, 31 of the 44 checked data sheets named an ISO/IEC 27001 certification, sometimes only for the data centre operator. The German BSI’s cloud catalogue C5 appears for Box, Fabasoft and Microsoft; for Microsoft 365 it is a C5 Type 2 report that covers the cloud service’s security, not compliant archiving. Microsoft also commits to storing and processing customer data of EU and EFTA tenants within its EU Data Boundary, with documented exceptions. Ask what each certificate covers: the vendor, the product, the data centre or one service.

Step 4: map the ERP, accounting and Microsoft 365 connections

The DMS holds the documents, the ERP the postings. How the two connect decides how much manual work remains, so describe it before you compare vendors.

Almost every connection follows one of four patterns, set out in detail in our guide to document management for SAP, Business Central, Dynamics 365 and NetSuite:

1. Archive link. The ERP stores documents in the DMS and keeps a link on the business object; for SAP usually through ArchiveLink, sometimes with ILM for retention.
2. Attachment sync or viewer. Users see DMS documents from the ERP record, or ERP attachments are copied to the DMS with metadata.
3. Inbound invoice process. The DMS captures, checks and routes supplier invoices and hands them to the ERP.
4. E-invoice import. Structured invoices arrive in the DMS or the ERP first and are turned into purchase documents.

Coverage differs a lot by ERP. On 3 October 2026, 35 of the 44 checked data sheets showed some form of SAP integration (16 with the value “Yes”, the rest as an add-on module, via partners or partly), 18 a DATEV integration and 16 an integration with Microsoft Business Central. A value of “Yes” means the vendor documents the integration; it does not tell you which pattern it covers. Ask for the pattern, the ERP version and deployment it was tested with, and who maintains it after ERP updates.

The ERPs bring their own storage as well. Business Central, for example, can store attachments in Azure Blob Storage, Azure File Share or SharePoint libraries, and Microsoft states that backup and access control are then your responsibility (Microsoft Learn). Such storage has no retention logic of its own; that is the gap a DMS fills.

Microsoft 365 is the second connection to plan. On 3 October 2026, 28 checked data sheets documented an integration with Microsoft 365 or Outlook, and 5 more offered it as an add-on module. The depth ranges from an Outlook add-in for filing e-mails to systems that run inside Microsoft 365. If you are deciding between SharePoint and a DMS, the licence question matters: according to Microsoft’s Purview service description, records management, auto-applied labels and event-based retention need Microsoft 365 E5, Office 365 E5 or a Purview add-on.

Step 5: plan for structured e-invoices, not only scans

A DMS for European companies has to handle structured e-invoices, because receiving them is already mandatory in Germany, Belgium, Poland and France. Many DMS projects were scoped around scanning paper. In Europe, a growing share of supplier invoices now arrives as structured data, and the rules for receiving them are national.

The dates that matter for most groups, each with its legal source in our e-invoicing tracker:

• Germany: every business established in Germany must be able to receive structured e-invoices since 1 January 2025; issuing follows in 2027 or 2028.
• Belgium: domestic B2B e-invoices in Peppol BIS over the Peppol network since 1 January 2026 (FPS Finance).
• Poland: all businesses receive invoices through the national system KSeF since 1 February 2026 (KSeF portal).
• France: all businesses established in France receive e-invoices through an approved platform since 1 September 2026 (DGFiP).
• Slovakia: domestic B2B e-invoices through certified Peppol-based delivery services from 1 January 2027.
• EU-wide: from 1 July 2030, structured e-invoices compliant with EN 16931 for intra-EU B2B supplies under the ViDA directive.

Italy and Romania have run clearance systems for years. For a DMS the question is not whether it “supports e-invoicing” but which part of the chain it takes over. Someone has to receive the invoice from the network or platform, validate it against EN 16931 and the national rules, show it readably to approvers, hand the data to the ERP and archive the original XML with its transmission evidence. Our pillar guide from e-invoice to archive walks through that chain country by country.

What the data sheets show on 3 October 2026:

16evidence XRechnung processing as a standard function, 7 more as an add-on module

17evidence ZUGFeRD or Factur-X processing as a standard function

5are Peppol access points themselves: ARXivar, Medius, OpenText, Siav, Yooz

9connect to Peppol via a partner (5) or as an add-on module (4)

Two examples show how differently vendors cover this. Yooz is registered by the French tax administration as an approved platform (plateforme agréée) according to its data sheet, so it can be the legal receiving channel in France. DocuWare’s data sheet records sending and receiving over Peppol through its E-Invoicing Service, which relies on a European e-invoicing provider’s infrastructure and is available only with DocuWare Cloud. Neither model is better in general; what matters is whether it covers your countries. If you need to understand access points and Peppol IDs first, read Peppol explained for finance teams.

Step 6: make compliant archiving a hard requirement

A DMS used for finance records must keep invoices authentic, intact and legible for each country’s retention period and delete them in a controlled way afterwards. Invoices and accounting records are what tax auditors ask for, and the archive is where a cheap system can become expensive. The EU sets the floor: the authenticity of origin, integrity of content and legibility of each invoice must be ensured from issue until the end of the storage period, and each member state sets the length of that period and may require storage in the original form (Articles 233 and 247 of the VAT Directive).

The national periods differ more than most system defaults assume: eight years for invoices in Germany since 2025 (§ 14b UStG), seven in Belgium, ten in Italy and Slovakia, ten inside KSeF in Poland, five under Romanian accounting law, six under Spanish commercial law, and in France ten under commercial law, with the tax period rising from six to ten years from 1 January 2027. They also start at different points: end of the calendar year, 1 January of the following year, last entry or 1 July after the financial year. The archiving requirements guide has each period with its source.

Form matters too. In Germany, the Federal Ministry of Finance requires at least the structured part of an e-invoice to be kept unaltered in its original form (BMF letter of 15 October 2025), and the amended GoBD state that the XML must not be lost through a conversion, for example to TIFF. A system that turns every incoming invoice into a PDF image does not meet this.

What to require from the archive:

• Retention classes per country and document type, with the correct start date and the legal basis recorded in the rule.
• Unalterable storage: write-once or locked objects, hash values at ingestion, annotations stored separately from the original.
• Legal hold that suspends deletion during audits or disputes.
• Controlled deletion after the period, with approval and a log that records class, year and count.
• Auditor access and export of documents with metadata in a machine-readable form.
• A migration path that keeps originals, hashes and metadata together when you change systems later.

Audit evidence. In Germany, many vendors have the archiving function of their software audited by an accounting firm, usually under the auditing standard IDW PS 880. On 3 October 2026, 12 of the 44 checked data sheets named an IDW PS 880 audit, and 7 of them named the auditor: Amagno (KRP Audit), Doxis (Deloitte), easy software (PKF), ELO (EY), Fabasoft (KPMG), Kendox (BDO Austria) and Starke-DMS (Revidata). Other evidence appears too: a TÜV Saarland seal for PROXESS, the VOI label “PK-DML ready” for docuvita, forcont, Kendox and M-Files, the French NF Z42-020 certification for Open Bee, and accreditation or qualification by the Italian agency AgID as preservation providers for ARXivar and Siav. In the data sheets, 30 vendors state compliant archiving as a standard function, 11 partly and 3 as an add-on module.

An audit report is useful evidence, but it covers a software version and an operating model, not your configuration. Your procedure documentation still has to describe how documents arrive, are stored, protected and found again. Ask which version and deployment the report covers and when it was issued.

Step 7: what do the AI features actually do with your documents?

AI in a DMS means capture and extraction, classification or assistants, and the questions that matter are where it processes data and whether a person confirms the result. Almost every vendor now advertises AI. On 3 October 2026, 24 checked data sheets showed AI features as a standard function, 11 as an add-on module, 3 as partly available and 1 through a partner; for 5 we found no public information. The label covers very different things:

• Capture and extraction: reading supplier, amounts and line items from PDFs and scans, suggesting G/L accounts and cost centres. This is the core of accounts payable specialists such as Esker, Medius (AI since 2016, according to its data sheet) and Yooz.
• Classification: recognising the document type and filling metadata, for example DocuWare’s “Intelligent Indexing” or the classification functions in d.velop, easy and nscale.
• Assistants and agents: chat with documents, summaries, translation and agents that act in workflows, such as M-Files Aino, the Doxis assistant in Microsoft Office, OpenText Content Aviator or Microsoft 365 Copilot in SharePoint.

For structured e-invoices, capture is less important because the data arrives in the XML; AI then helps with coding, matching and exceptions. For paper and PDF, it still decides how much typing remains.

The pricing of AI deserves its own line in every offer. According to the data sheets, agorum’s ALBERT AI Suite starts at EUR 120 a month including one million output tokens, with language model usage billed on top at the model provider’s prices (agorum); Amagno bills its AI service by tokens; Microsoft sells Copilot as an add-on licence. Usage-based billing is fair for low volumes and hard to budget for high ones, so ask for a monthly cap or an alert.

Four questions to ask about any AI function: which model it uses and where the processing happens; whether your documents are used to train models; whether a person confirms the result before it is posted or filed (Esker’s data sheet notes that approvals stay with the users); and whether the original document stays untouched, with AI results stored as separate metadata.

Step 8: budget for the full cost, not the licence

Budget for the full cost of a DMS: the licence is only one line, and most vendors publish no price. Price transparency is low. On 3 October 2026, 5 of the 44 checked vendors published a full price list (agorum, Box, Laserfiche, Microsoft for SharePoint in Microsoft 365, and SmartDocs), 13 published part of their prices and 26 no amount at all. Where prices exist, units differ: per named user, per concurrent connection, per seat, per legal entity or per document volume. A few published examples, all checked between 1 and 3 October 2026:

Vendor	Published price	Unit
Box	EUR 4.50 (Business Starter)	per user and month, billed annually, 3 to 10 users
M-Files	EUR 65 (Essentials)	per seat and month, usually invoiced annually
ecoDMS	EUR 125 net (Business Edition)	per concurrent connection, one-off
agorum	EUR 32.00 net (core pro, 1 user)	per user and month, falling to EUR 8.96 at 1,000 users

The licence is only one line. Hosting and storage, set-up, migration, scanning of the paper backlog, each interface, e-invoice connectors, training, support and usage-based charges for recognition or AI complete the bill, and most of these have no public price. In the illustrative three-year calculation in our cost guide, services made up 40% of the total, with year one costing more than years two and three together. Plan the budget accordingly and ask for a cost table per year in every offer.

How to choose a document management system: the selection process, step by step

Choosing a document management system takes eight steps, from setting up the team to planning migration and go-live. With the requirements and the decisions above, the selection itself follows a fixed order. Skipping steps usually costs more time later than it saves now.

1. Set up the teamFinance, IT, the data protection officer and one or two people who will use the system daily. Name one person who decides.
2. Write the requirementsInventory of documents, users, entities, systems and constraints; no more than ten must-haves, each testable.
3. Build a longlist from evidenceFilter vendors by deployment, hosting, ERP, e-invoice formats and audited archiving. Keep vendors with open points if the point can be asked.
4. Send one scenario to five vendorsSame users, entities, volumes and integrations for everyone; ask for written answers and a cost table per year.
5. Run scripted demosYour own documents and your script, not the vendor's standard demo. Score each must-have during the demo.
6. Pilot the favouriteA few weeks with real documents from one process and one entity, including archive, export and deletion tests.
7. Negotiate the contractPrice over three to five years, service levels, data location, sub-processors, exit and data export, price adjustment.
8. Plan migration and go-liveWhich documents move, which stay read-only in the old system, and how retention dates and XML originals are preserved.

A few practical points from the documents we read:

• Trials. On 3 October 2026, 16 of the 44 checked data sheets recorded a public trial version. For the others, ask for a pilot on your data.
• Minimum quantities. Box requires at least 3 users and Laserfiche at least 5, 25 or 500 users depending on the plan; the DocuWare partner package has a 12-month minimum term. Such terms belong in the comparison.
• Partners. Many vendors sell and implement through partners. DocuWare’s data sheet, for example, records sales through partners. Then the partner’s offer and support quality matter as much as the product.

Shortlisting vendors with the DMS finder

The DMS finder builds a shortlist from evidence: it ranks the vendors with a checked data sheet by how close their public sources come to your criteria. It helps most in step 3 of the selection process. It asks for your criteria in six groups: what the system should do (invoice processing, structured e-invoices, compliant archiving, mailroom, contracts, HR files, Microsoft 365), where it should run and where data must be hosted, countries and interface languages, ERP and e-invoice formats or networks, company size and several legal entities, and the evidence you expect, such as ISO/IEC 27001, BSI C5 or an IDW PS 880 audit.

For every criterion and vendor, the finder shows one of four states taken from the data sheet: evidenced, partly (add-on module, via partner or limited), no public information or no. It then ranks the vendors by how close they come to your criteria. There are no paid placements. “No public information” scores like a missing point but never removes a vendor; only published data showing that a vendor does not offer the required deployment or hosting region removes it from the ranking. The rules are explained in our methodology, and the finder runs in your browser.

An example of how the evidence narrows the field: on 3 October 2026, three vendors had the value “Yes” for an SAP integration, for XRechnung processing and for compliant archiving, and named Germany as a hosting location: d.velop, Doxis and enaio. Relax “Yes” to “partly” or drop the hosting criterion and the list grows; ELO, for instance, drops out only because its data sheet names European data centres without a country. That is the point of a shortlist from evidence: it shows what you would have to ask, not just who claims what.

Read “no public information” as a question for the first call, not as a “no”. Each vendor’s data sheet in the directory lists its open points as questions, together with the sources for every value.

Comparing offers and running a pilot

Offers can only be compared if they answer the same question. Give every vendor the same scenario: users by role, entities, document and invoice volumes, storage today and in five years, integrations and countries. Ask for a cost table per year, with the unit and the VAT status of each line.

• Licence or subscription with the licence type and every add-on module you need from day one
• Hosting, storage allowance and the price of growth
• Set-up, migration and each interface as separate lines, fixed price or capped
• E-invoice connection per country: who receives, validates and archives
• Usage-based charges for recognition or AI, with a cap
• Training, support levels and the next major version
• Minimum term, renewal, notice period and price adjustment
• Data export at the end: format, scope, cost

The demo and the pilot should test what the offer promises. A good script uses your own documents: a dozen real supplier invoices, among them structured e-invoices from each of your countries and a few poor scans; a contract with a notice period; a document that has to be deleted at the end of its period. Then check whether the system classifies and extracts correctly, shows the XML readably, routes approvals the way your signing rules require, hands data to the ERP, and lets an auditor’s read-only account find and export one month of invoices with metadata.

Two tests are often skipped and later regretted. The retention test: configure one retention class, apply it, and try to delete or change a document in it as an administrator. The exit test: export a set of documents with metadata and audit trail and check that you could load it into another system. Both show how the archive behaves when it matters.

Which kind of document management system fits? A decision guide

Five questions about your documents, invoices, e-invoice channels, audit evidence and hosting decide the type of system before you compare products.

1. Are most documents project files, policies and team folders in Microsoft 365?Yes: start with SharePoint and add a DMS or archive only for finance and HR records.No: compare DMS and ECM vendors directly.
2. Are inbound invoices the main reason for the project?Yes: shortlist accounts payable specialists and DMS vendors with an invoice module and your ERP connector.No: weigh filing, search, workflows and archive more heavily.
3. Do you receive e-invoices through several national networks or platforms?Yes: prefer vendors that are access points or platforms themselves, or that document a connection to your provider.No: an ERP or provider can receive; the DMS archives the XML.
4. Do you want an auditor's report on the archive?Yes: filter for a named IDW PS 880 audit or a comparable national certification.No: your procedure documentation must carry the proof alone.
5. Must data stay on your own servers or in one country?Yes: filter by own servers or hosting country first; it removes the most vendors.No: a cloud service is usually quicker to introduce.

Where to start

Start with the inventory of documents, entities and systems; it takes days, not months, and every later step depends on it. Then filter with the DMS finder, read the data sheets of the vendors that remain, and send them one scenario. If invoices and e-invoices drive the project, read from e-invoice to archive next; for the budget, the cost guide; for SAP, Business Central, Dynamics 365 or NetSuite, the ERP integration guide. To see which e-invoicing and retention deadlines apply to each of your entities, use the readiness check.

This guide is general information, not legal or tax advice. Vendor values come from public vendor sources as recorded in our data sheets on 3 October 2026; vendors can send corrections with a source, as described in our methodology.