SharePoint as a document management system: where it works and where it falls short

Short answer: As of 3 October 2026, SharePoint can store, version, tag and protect documents, and with Microsoft Purview it can keep them from being deleted before a retention period ends. It is not a finance archive out of the box: e-invoice handling, invoice approval, accounting interfaces and an auditor's report on the archive are missing, and the stronger records functions need Microsoft 365 E5 or a Purview add-on. Most organisations end up with one of three set-ups: SharePoint alone with a careful Purview configuration, SharePoint plus an archive or DMS add-on, or a dedicated DMS that works inside Microsoft 365.

Many European companies already pay for SharePoint as part of Microsoft 365, so almost every DMS project asks: do we need anything else? This guide checks SharePoint against what finance and IT teams expect from a document management system, using Microsoft’s own documentation. Vendor facts come from our checked SharePoint data sheet and the other data sheets in the DMS directory. Microsoft documentation and prices were checked on 3 October 2026; confirm licence details before you buy, as Microsoft changes plans regularly.

The answer depends on the documents. For project files, policies and team folders, SharePoint is often a good tool. For inbound invoices, accounting vouchers and anything a tax auditor will ask for, it needs more work, more licences or a second system.

Is SharePoint a document management system?

SharePoint is a document management system for storing, versioning, tagging and finding documents, but not, out of the box, a finance archive with invoice processing. It is included in all Microsoft 365 and Office 365 plans, according to Microsoft’s SharePoint limits; the Business plans contain SharePoint Plan 1 (price page). For on-premises operation there is SharePoint Server Subscription Edition, in support since November 2021. This guide covers SharePoint in Microsoft 365, for which Microsoft documents the Purview retention and records functions.

The document management basics are there:

• Libraries and sites as the storage structure, with permissions at site, library, folder and file level.
• Metadata through columns, content types and managed metadata (term sets), so users filter by supplier or fiscal year instead of browsing folders.
• Version history. By default at least 500 major versions per file, adjustable (Microsoft).
• Search through Microsoft Search. Text recognition (OCR) for scans and images is a separate pay-as-you-go service (OCR overview).
• Workflows through Power Automate, for example approvals. Microsoft 365 licences include a limited set of Power Automate capabilities; premium and custom connectors need a Power Automate Premium or Process licence (licence overview).
• Integration with Outlook, Teams, Word and Excel, plus mobile apps.

What SharePoint lacks is business logic for specific document types. It does not recognise an inbound invoice, match it to a supplier, route it for approval or post it to accounting unless you build or buy that.

Limits worth knowing before you design the structure

Some SharePoint service limits matter for archives that grow over ten years:

• A library can hold up to 30 million files and folders. Once a library or folder holds more than 100,000 items, you can no longer break or restore permission inheritance on it.
• The supported limit for unique permissions in a list or library is 50,000; the recommended general limit is 5,000.
• The full decoded path, including the file name, cannot exceed 400 characters.
• Tenant storage is 1 TB plus 10 GB per licence, so a tenant with 50 licences has 1.5 TB.

For finance archives, permissions are the practical constraint: if every invoice folder carries its own permissions, you reach the recommended limit long before the storage limit.

Retention in Microsoft Purview: policies and labels

Retention in SharePoint document management comes from Microsoft Purview, the compliance part of Microsoft 365, and works through retention policies for whole locations and retention labels for single items. The functions that move SharePoint towards an archive come from Purview, and two of its tools are often confused.

Retention policies apply to whole locations, for example all SharePoint sites or a selected set of sites. Retention labels apply to individual items and can be set by users, by an auto-apply policy or as a library default. Both define how long content is kept and whether it is deleted afterwards. An item can be subject to several policies, but it can carry only one retention label at a time, according to Microsoft’s retention overview.

When settings conflict, Microsoft applies four principles. Retention wins over deletion. The longest retention period wins. For deletion, an explicit label wins over an implicit policy. Among the remaining policies, the shortest deletion period wins. If a policy deletes files after three years and a label keeps them for eight, the file is kept for eight years.

What happens when someone edits or deletes a file

When a file under retention is changed or deleted, SharePoint copies the original into the Preservation Hold library, a hidden system location that compliance tools such as eDiscovery can search. Microsoft’s SharePoint retention page adds details that matter in practice:

• A standard retention label (not marking the item as a record) creates a copy only on deletion, not on editing.
• To retain all versions of a file, versioning must be turned on for the site.
• Under a retention policy, the library’s version limits are suspended until the period ends. Under a label alone they still apply: older versions are deleted automatically, although users cannot delete versions themselves.
• At the end of the period, content set to be deleted goes to the recycle bin and is permanently deleted after 93 days. The recycle bin is not indexed, so eDiscovery cannot find content there.

A tenant setting can block the deletion of labelled items in SharePoint; for finance libraries that is the safer default.

Records and regulatory records

A record in SharePoint is an item whose retention label blocks its deletion and, depending on the type, its editing. A retention label can also declare an item a record or a regulatory record. Microsoft’s records management documentation compares what each allows:

Action	Standard retention label	Record, locked	Record, unlocked	Regulatory record
Edit contents	allowed	blocked	allowed	blocked
Edit properties, including rename	allowed	allowed (can be blocked by a tenant setting)	allowed	blocked
Delete	allowed (can be blocked by a tenant setting)	blocked	blocked	blocked
Change or remove the label	allowed	container admin only	blocked	blocked

Once a regulatory record label is applied, nobody, not even a global administrator, can remove it. Its retention period can be extended but not shortened, it cannot be auto-applied, and the option must first be enabled with PowerShell. Records also log additional activities and give proof of disposition at the end of the period.

This covers the core archive requirement that a document cannot be altered unnoticed or deleted early. It does not happen by itself: someone has to define labels and periods, apply them to the right libraries and keep the configuration documented.

SharePoint version history: what is kept and what is trimmed

SharePoint version history keeps earlier versions of each file up to limits that administrators set, and versions beyond those limits are deleted permanently. Microsoft’s overview of version history limits (last updated 10 April 2025) describes how this works:

• Where limits are set. Organisation defaults apply to new libraries; site administrators can override them for a site or a single library.
• Automatic or manual. The automatic setting, which Microsoft recommends, balances recovery against storage. The manual setting caps the number of major versions, optionally with an expiry period; with 500 versions and 365 days, for example, no version older than 365 days is kept. The user interface does not accept fewer than 100 versions or less than 30 days.
• Trimmed versions are gone. Versions that exceed the limits bypass the recycle bin and cannot be restored from it; a version a user deletes by hand goes to the recycle bin.
• Retention changes the rules. For items under a retention policy or an eDiscovery hold, the library’s version limits are ignored until the retention period ends or the hold is released. Under a retention label alone, the limits still apply: older versions are deleted automatically, although users cannot delete versions themselves.

For finance records this means version history is not a retention tool. If every version of an invoice or contract must survive, put the library under a retention policy, or keep the original unaltered as a record.

Which Microsoft 365 licence do you need for which function?

Retention policies for SharePoint are licensed in plans such as Microsoft 365 Business Premium and E3, while records, auto-labelling and event-based retention need E5 or a Purview add-on, according to Microsoft’s service description. This is where many SharePoint-as-DMS plans change, because not every Purview function is part of every plan. The Purview service description (updated August 2026) lists, among others:

Function	Licences Microsoft names (extract)
Organisation-wide retention policies on SharePoint	Microsoft 365 E3/E5, Business Premium, Office 365 E3/E5; for SharePoint also SharePoint Plan 2
Creating retention labels	Microsoft 365 E3/E5, F1/F3, Business Premium; Office 365 E1/E3/E5
Publishing labels for manual use in SharePoint	as above; for SharePoint also SharePoint Online Plan 1 or 2
Marking items as record or regulatory record, event-based retention, disposition review	Microsoft 365 E5, Office 365 E5, Purview Suite, E5 Information Protection and Governance
Default label for a library, folder or document set; auto-applying labels	Microsoft 365 E5, Office 365 E5, Purview Suite, E5 Information Protection and Governance
File plan (import, export, maintenance of labels)	Microsoft 365 E5, Office 365 E5, Purview Suite, E5 Information Protection and Governance

Business Basic and Business Standard are not named for SharePoint retention policies or for creating retention labels; SharePoint Plan 1, which they include, appears only for publishing labels. Ask your licensing partner how this applies to your tenant. The same document states that every user who benefits needs a licence: for SharePoint, the owners and members of a site with a retention or label policy, but not visitors.

1. Storage, versions, metadata, searchSharePoint, in every Microsoft 365 plan
2. Retention policies and retention labelsPurview: Business Premium, E3 or higher
3. Records, auto-labelling, event-based retention, disposition reviewPurview: E5 or a Purview add-on
4. Invoice capture, e-invoices, ERP hand-over, archive audit reportnot in SharePoint: own build, ERP, e-invoicing service or DMS

What the plans cost

On 3 October 2026, Microsoft’s Irish price pages listed these prices per user and month, paid yearly, excluding VAT:

Plan	Price (Ireland)	Relevant for retention
Microsoft 365 Business Basic	EUR 6.07	not named for SharePoint retention policies
Microsoft 365 Business Standard with Copilot	EUR 20.36	not named for SharePoint retention policies
Microsoft 365 Business Premium with Copilot	EUR 27.73	retention policies, retention labels
Microsoft 365 E3	EUR 37.78	retention policies, retention labels
Microsoft 365 E5	EUR 58.13	adds records, auto-labelling, event-based retention, disposition review

Sources: SharePoint plans and Enterprise plans. Business plans are sold for 1 to 300 users; variants with and without Teams exist, and prices differ by country.

At these prices, moving a user from E3 to E5 for records management costs EUR 20.35 per month. For 15 people who own or work in the archive sites, that is EUR 3,663 a year before any partner work. Purview add-ons are an alternative to full E5; Microsoft showed no price for them on the pages we checked. Published prices of dedicated DMS products are compared in what a document management system costs.

Usage-based services come on top, billed through an Azure subscription in US dollars (pay-as-you-go price list):

• OCR: USD 0.001 per page or image. Processing runs every time the file is edited.
• Prebuilt document processing (for example the invoice model): USD 0.01 per page, counted per model applied, on upload and on later updates.
• SharePoint storage above the tenant quota: USD 0.20 per GB and month.
• Microsoft 365 Archive: USD 0.05 per GB and month, charged only where archived plus active storage exceeds the tenant’s storage allocation.

What do European archiving rules ask of SharePoint?

European archiving rules ask that invoices stay authentic, intact and legible for a national retention period, and SharePoint can meet that only in libraries where retention, versioning and permissions are configured and documented.

The EU VAT Directive sets the frame for invoices. Article 233 requires that the authenticity of origin, the integrity of the content and the legibility of an invoice are ensured from issue until the end of the storage period, on paper or electronically. Article 247 leaves the length of that period, and whether invoices must be kept in their original form, to each member state (Directive 2006/112/EC). The periods therefore differ: eight years for invoices in Germany since 2025, seven years in Belgium, six years under French tax law with ten years under commercial law, and ten years inside the Polish KSeF platform, according to our country pages for Germany, Belgium, France and Poland, each with its legal source; the country-by-country rules are in our guide to e-invoice archiving requirements.

Germany is the most detailed case and a common reason for groups to look at their archive. The rules there are known as GoBD, the tax administration’s principles for keeping books and records in electronic form. The points that matter for SharePoint:

Unalterability. A record must not be changed in a way that hides its original content. In SharePoint, versioning, retention and records provide this, but only in libraries where they are configured. A library without retention, where users may delete versions, does not meet the requirement.

Availability and machine evaluation. Under § 147 of the German Fiscal Code, electronic records must be available for the whole period, which starts at the end of the calendar year the voucher was created, and readable without delay. Tax auditors can inspect the data or require it in a machine-readable format (§ 147(6)). SharePoint can support that with read access and an export with metadata; Microsoft provides no ready-made procedure.

Original format. Since the BMF letter of 14 July 2025, GoBD paragraph 131 states that received electronic documents must be kept in the format in which they were received, for example invoices in XML format. Converting an XML e-invoice to PDF and keeping only the PDF does not satisfy this.

Procedural documentation. How documents arrive, are stored, protected and found again belongs in a written procedure description, for SharePoint including the Purview configuration, the permission model and who may change them.

Audit evidence. Several DMS vendors have their archive audited by an accounting firm, often under the German standard IDW PS 880; our data sheets show this with named auditors for, among others, ELO (EY), Doxis (Deloitte) and easy (PKF). For SharePoint, Microsoft names no such audit on the pages we checked. Microsoft 365 has a C5 Type 2 report under the German BSI cloud security catalogue; it covers the security of the cloud service, not compliant archiving.

None of this rules SharePoint out. It means you or your partner build and document the compliance case, while some DMS vendors deliver part of it as a product with an audit report. This section is general information, not tax or legal advice.

E-invoices and invoice processing

SharePoint stores e-invoices, but Microsoft’s documentation describes no validation, readable display or network connection for them; that work sits in an ERP, an e-invoicing provider or a DMS. E-invoicing mandates are in force in several EU countries: German businesses must be able to receive structured e-invoices since 2025, Belgian VAT-registered businesses exchange Peppol e-invoices since 1 January 2026, and French businesses receive through an approved platform since 1 September 2026. The e-invoicing tracker lists every date with its legal source. For SharePoint this means:

• Storage works. An XML e-invoice is stored like any other file, and retention or records labels can protect it.
• Validation and display do not. Microsoft’s documentation describes no check against the European standard EN 16931 and no readable rendering of XRechnung, ZUGFeRD/Factur-X or Peppol BIS files; our data sheet records “no public information” for XRechnung and ZUGFeRD.
• No network connection. Microsoft describes no Peppol access point and no connection to platforms such as KSeF or the French approved platforms. That sits in your ERP, an e-invoicing provider or a DMS.
• Reading PDFs and scans costs extra. The prebuilt invoice model extracts fields such as customer name, due date and amount due from PDF and image files into library columns, at USD 0.01 per page. Approval, coding, purchase-order matching and the hand-over to accounting have to be built, for example in Power Automate, or bought.

Business Central users have one native link: Business Central can store document attachments in SharePoint libraries instead of its database. Microsoft’s documentation states that you are then responsible for backup and access control, and that Business Central loses access if the file is deleted in SharePoint. Put the target library under retention before you switch it on. Integration patterns for other ERPs are covered in our guide to document management for SAP, Business Central, Dynamics 365 and NetSuite.

Metadata, search and governance in daily use

A SharePoint archive is only as good as its metadata and permissions:

1. Content types with required columns. One content type per document class (inbound invoice, outbound invoice, bank statement, contract) with required fields such as document date, number, business partner, legal entity and fiscal year. That makes the archive searchable and exportable for an auditor.
2. Managed metadata for shared values. Legal entities, cost centres and document types belong in term sets, not free text. Microsoft recommends no more than 50 terms as defaults on a managed metadata column.
3. Permissions by role, not by file. Finance writes, management and auditors read, external sharing is off for archive sites, and only a few named people can change Purview settings.

Scans only become searchable once OCR has run. Microsoft’s OCR overview adds two limits: only images uploaded after OCR has been enabled are scanned, and subsites are not supported, so switch OCR on before you migrate scans. Groups with several entities should decide early between one archive site per legal entity and one site with an entity column; changing it later means moving labelled content.

Data location belongs to governance too. For tenants whose sign-up location is in the EU or EFTA, Microsoft commits to storing and processing customer data within its EU Data Boundary, with documented exceptions; Multi-Geo tenants are not in scope. Advanced Data Residency is offered in local regions including France, Germany, Italy, Poland, Spain, Sweden and Switzerland (data locations).

SharePoint alone, with an add-on or a dedicated DMS

The gaps above lead to three set-ups that appear in most tenders: SharePoint alone, SharePoint with an archive or DMS add-on, and a dedicated DMS that integrates with Microsoft 365.

SharePoint alone. You configure Purview retention, records and Power Automate flows yourself or with a Microsoft partner. This fits when most documents are project and team files, tax-relevant vouchers live mainly in the ERP, and you have Microsoft 365 skills in-house.

SharePoint with an archive or DMS add-on. Users keep working in SharePoint and Teams, and an archive or DMS handles the documents that need fixed retention and processing. According to our checked data sheets, windream offers Teams and SharePoint archiving as a separate product that stores content outside the Microsoft cloud, nscale a connector for SharePoint Online, and d.velop a product that adds file structures, workflows and compliant storage to SharePoint in Microsoft 365.

A dedicated DMS with Microsoft 365 integration. The DMS runs archive and finance processes while users stay in Outlook, Teams and Office. Most vendors with a checked data sheet name such an integration, sometimes as a paid module, with varying depth: M-Files states that it runs within Microsoft 365, ELO names integration with Teams and SharePoint Online, others mainly offer an Outlook add-in for filing emails and attachments.

Criterion	SharePoint alone	SharePoint + archive/DMS add-on	Dedicated DMS with M365 integration
Where users work	SharePoint, Teams, Office	SharePoint, Teams, Office	DMS client plus Outlook/Teams/Office integration
Retention and records	Purview; records functions need E5 or an add-on	from the add-on, partly alongside Purview	from the DMS
Inbound invoice workflow	build with Power Automate and pay-as-you-go extraction	depends on the add-on	often a product module (check the data sheet)
E-invoice validation and display	not described by Microsoft	depends on the product	XRechnung/ZUGFeRD documented by many vendors
Accounting/ERP interface	Business Central attachment storage; others via connectors	depends on the product	DATEV, SAP and others, per data sheet
Auditor’s report on the archive	none named by Microsoft	some vendors (e.g. IDW PS 880)	some vendors (e.g. IDW PS 880)
Licence model	per user, plan-dependent	Microsoft 365 plus add-on	DMS licence plus Microsoft 365
Who owns the configuration	you or your Microsoft partner	shared	DMS vendor or partner, with you

SharePoint alternatives from a DMS perspective

The alternatives to SharePoint for document management are other content platforms, dedicated DMS and ECM products, and accounts payable specialists that cover invoices only. Lists of “SharePoint alternatives” usually compare intranet and wiki tools; for finance records the comparison runs along different lines. Our data sheets classify the checked vendors by what they mainly offer:

• Content and collaboration platforms, like SharePoint itself: Box.
• Document management systems with filing, metadata, workflows and an archive: for example DocuWare, M-Files and ecoDMS.
• ECM platforms for larger organisations: for example d.velop, ELO and OpenText.
• Accounts payable specialists, if invoices are the only reason to look beyond SharePoint: for example Yooz and Medius.

Most organisations do not replace SharePoint but add one of these for the records that need retention and processing. The DMS finder filters the vendors with a checked data sheet by Microsoft 365 integration together with ERP, e-invoice formats, hosting and archive audits, so you see which alternatives fit alongside your tenant.

When is SharePoint enough, and when is it not?

SharePoint is usually enough for project files, policies and team folders, and usually not enough on its own for inbound invoices, e-invoices and records a tax auditor will ask for. If more than one answer below points towards a DMS, compare the second and third set-up with real offers.

1. Should inbound invoices be captured, checked and approved in the document system?Yes: look at a DMS add-on or a DMS with an inbound invoice module.No: SharePoint can work as the storage layer.
2. Do you receive structured e-invoices (XRechnung, ZUGFeRD, Peppol BIS, KSeF) that someone has to read and check?Yes: you need validation and a readable view, from the ERP, an e-invoicing service or a DMS.No: storing the files under retention may be enough.
3. Do you have Microsoft 365 E5 or a Purview add-on, or plan to buy it?Yes: records, auto-labelling and event-based retention are licensed.No: retention policies and manual labels only, depending on the plan.
4. Is there someone, in-house or at a partner, who will look after Purview settings and permissions for years?Yes: SharePoint alone is realistic.No: a DMS with predefined processes takes more work off your hands.
5. Do you want to show your tax auditor an audit report on the archive?Yes: choose a vendor with a documented audit.No: your configuration and procedure documentation must carry the proof alone.

An example: a German engineering firm with 25 employees on Business Standard, an external accountant and about 150 inbound invoices a month. SharePoint suits its project files. For invoices, three things are missing: approval, the hand-over to accounting and, with Business Standard, a plan Microsoft names for SharePoint retention policies. A DMS with inbound invoice processing, a documented accounting interface and Outlook integration is usually quicker to introduce than building all of that, while project files stay in SharePoint.

SharePoint document management best practices for finance records

SharePoint document management for finance records works best with separate archive sites, retention applied before content arrives and permissions set by role. If you keep tax-relevant records in SharePoint alone, follow a fixed order (assuming your licences cover the Purview functions):

1. Create separate archive sites for finance records. That simplifies permissions, retention scope and auditor access.
2. Build libraries by document class with content types and required columns.
3. Keep versioning on, or retention will not keep every version.
4. Set retention periods against the law, not the file date. Statutory periods usually start at the end of the calendar year, as in Germany, or on 1 January of the following year, as in Belgium. Purview counts from creation by default, alternatively from last modification, from labelling or from an event; event-based retention is an E5 function. Without it, add a buffer so that no document leaves retention before its legal period ends. Agree the periods with your tax adviser.
5. Apply retention before content arrives. Microsoft copies items to the Preservation Hold library for content that exists when the retention settings are applied and, for policies, for content added afterwards. Documents deleted before that are not protected.
6. Block deletion of labelled items with the tenant setting, and restrict who can change Purview settings.
7. Test regulatory records in a test environment first. The label cannot be removed once applied.
8. Test auditor access and export. Create a read-only account, export one month with all metadata and check whether an outsider can find and evaluate the documents.

Record every step, label, period and responsibility in your procedure documentation, and add each later change with its date.

Migrating to SharePoint, or from SharePoint to a DMS

A migration in either direction must keep original files, metadata and retention dates intact, because statutory periods do not restart when documents move.

Into SharePoint. Microsoft’s tool is Migration Manager for file shares, Box, Dropbox, Google Drive and Egnyte; the SharePoint Migration Tool handles SharePoint Server 2010, 2013 and 2016. Migration copies files and leaves the source in place, according to Microsoft’s migration overview. For records, note that SharePoint updates a file’s metadata on upload, so file size or a simple hash does not prove a file is unaltered; Microsoft’s records documentation describes comparing a QuickXorHash of the original with the vti_writevalidationtoken property. Have the target structure and retention in place before the first run, and keep the source until the migration has been checked and documented.

From SharePoint to a DMS. The statutory period does not restart with the move; in Germany it runs from the end of the calendar year in which the voucher was created. Export with all metadata, keep the XML originals of e-invoices and check how the DMS takes over existing retention dates. Content under a Purview policy or label stays in the Preservation Hold library until its period ends, so decide whether SharePoint remains the archive for older years.

Questions for your Microsoft partner or DMS vendor

Seven questions settle most of what a SharePoint-based archive or a DMS offer has to answer in writing.

1. Which Purview functions will you configure for our finance libraries, and which licences do which users need for them?
2. How are versioning, retention periods and deletion blocks set per library, and who can change them?
3. How are XML e-invoices stored, validated and displayed to an auditor?
4. How do documents and posting data reach our ERP or accounting system?
5. How does a tax auditor get read access or a machine-readable export?
6. Is there an audit report on the archive, and for which version and operating model does it apply?
7. In which country is our tenant’s data stored, and is it inside Microsoft’s EU Data Boundary?

Get the answers in writing and file them with your procedure documentation.

Finding the right set-up

The right set-up follows from your documents, not from the product. Start with the classes you manage, which of them are tax-relevant, who works on them and which systems they flow into. Where team and project documents dominate, SharePoint with a clean Purview set-up is often enough. Where invoices, e-invoices, accounting interfaces and audit evidence come first, compare a SharePoint add-on with a dedicated DMS using concrete offers over at least five years for the same number of users.

The DMS finder ranks the vendors with a checked data sheet against your criteria, including Microsoft 365 integration, ERP, e-invoice formats and hosting location. More guides on choosing and running a DMS are in the guides section.