Document management for SAP, Business Central, Dynamics 365 and NetSuite: integration patterns and a vendor matrix

Short answer: A document management system (DMS) connects to an ERP in one of four ways: as the archive behind the ERP (for SAP usually through ArchiveLink or ILM), as attachment storage or a document viewer inside ERP records, as an inbound invoice process that ends with an invoice in the ERP, or as the receiving point for structured e-invoices. "Integrates with SAP" can mean any of these, or only a file export. Of the 36 vendors with a checked data sheet in our directory on 3 October 2026, 30 show some form of SAP integration, 15 a Business Central integration, 9 name Dynamics 365 Finance & Operations and 6 name NetSuite. The matrix below gives each value with a link to its data sheet and source.

The ERP holds the postings, the DMS holds the documents behind them. Which DMS fits our ERP, and what does a vendor’s “integration” actually do? Most lists that answer this are written by vendors about themselves. ERP fit is one criterion among several covered in our guide on how to choose a document management system. This guide explains the integration patterns from SAP, Microsoft and Oracle documentation and builds the vendor comparison only from our checked data sheets, each value with its public source. Everything was checked between 1 and 3 October 2026; ERP functions change with every release, so confirm the details for your version.

Four integration patterns at a glance

Almost every DMS–ERP connection is one of four patterns, or a combination of them. They differ in which system is the master for the document, the metadata and the process.

Pattern	What happens	Where the document lives	Master for the process
1. Archive link	The ERP stores documents in the DMS and keeps a link on the business object	DMS (archive)	ERP
2. Attachment sync or viewer	Users see DMS documents in the ERP screen, or ERP attachments are copied to the DMS with metadata	DMS, sometimes both	ERP for records, DMS for files
3. AP inbound with posting	The DMS captures, checks and routes supplier invoices and creates the invoice in the ERP	DMS	DMS until hand-over, then ERP
4. E-invoice import	Structured e-invoices (Peppol BIS, XRechnung, FatturaPA and others) arrive in the DMS or the ERP and are converted into purchase documents	ERP, DMS or both	whichever system receives first

The patterns are not exclusive. A typical mid-sized set-up uses pattern 3 for supplier invoices, pattern 1 for the archive and pattern 2 so that buyers and controllers can open the invoice image from the purchase order. What matters is that every document type has exactly one system that owns the original.

Pattern 1: the DMS as the archive behind the ERP

In pattern 1, the ERP stores documents in the DMS and keeps a link on the business object; for SAP this runs through ArchiveLink and, for retention, ILM.

SAP: ArchiveLink and ILM

SAP’s standard for this pattern is ArchiveLink. SAP’s documentation describes it as a service integrated in the SAP application server for linking archived documents with the application documents entered in the SAP system; the links give permanent access, and users can display an archived document directly from the related business document (SAP Help, ArchiveLink). ArchiveLink handles four kinds of content: incoming documents, outgoing documents, print lists and archive files. It needs a storage system, and documents must already be electronic or be converted. The DMS plays that storage role; SAP keeps the link on the business object.

The second SAP interface is ILM (Information Lifecycle Management), which adds retention management. According to SAP, the ILM interface is an enhancement of the WebDAV protocol (SAP Help, ILM Store). An ILM-certified store must be able to receive and interpret metadata, and stored data cannot be changed or deleted within the defined retention periods (SAP Help, WebDAV server for ILM). SAP also offers its own ILM Store, which can keep data in the database, the file system or both, so a third-party archive is optional for archive files.

In short: ArchiveLink answers “where is the document for this invoice?”, ILM answers “how long must this data be kept?”. A DMS with ArchiveLink but without ILM can still fit; retention for archive files is then managed elsewhere.

Business Central, Dynamics 365 Finance & Operations, NetSuite

The Microsoft and Oracle ERPs approach storage differently. The pages we checked describe storage targets inside the vendor’s own cloud rather than a published archive protocol for third-party systems comparable to ArchiveLink. DMS vendors therefore ship their own connectors.

• Business Central can store document attachments outside its database in Azure Blob Storage, Azure File Share or SharePoint document libraries. The External File Storage framework is extensible, so partners can add other storage providers through an extension (Microsoft Learn). Microsoft names the reason: each tenant has a limited database capacity, by default 80 GB for production and sandbox environments plus extra storage per licence. Microsoft also states that it does not back up externally stored files; backup and access control are your responsibility, and Business Central can no longer open a file that was deleted in the external storage.
• Dynamics 365 Finance & Operations stores attachments in Azure Blob Storage by default, and SharePoint Online can be set per document type. SharePoint storage is only available in Microsoft-managed environments, on-premises SharePoint is not supported, and files stored in SharePoint can be at most 262 MB (Microsoft Learn). The same page says the system cannot store attachments in the database.
• NetSuite keeps files in its own File Cabinet. Each account comes with 10 GB of total storage unless more has been purchased; NetSuite accepts all file formats and scans every upload for viruses (Oracle NetSuite).

None of these pages describes retention periods, deletion locks or audit evidence for the stored files. That is the gap a DMS or archive fills behind these ERPs; our SharePoint guide covers what Microsoft Purview adds when the target is a SharePoint library.

What is SAP’s own document management (SAP DMS)?

SAP DMS is SAP’s own document management in SAP S/4HANA: it stores documents as document info records that can be linked to SAP objects such as materials or customers. The term “SAP DMS” refers to this component, not to a third-party DMS connected to SAP, so it helps to keep three things apart.

Document info records. SAP defines the document info record as “the master record in the SAP System that stores all the business information for a document”. It holds the metadata, such as the storage location, while the original file, for example a design drawing, holds the content. A document is identified by four key fields: document number, document type, document part and document version (SAP Help, Document Info Record, SAP S/4HANA 2025 FPS01).

In the SAP GUI, users reach the functions from the Document Management menu; SAP’s support content lists the transactions CV01N (create), CV02N (change), CV03N (display) and CV04N (find a document info record), along with status management, links to SAP objects and document distribution (SAP Support Content, Basics of Document Management). SAP’s own examples come from engineering and production: design drawings linked to material masters, and documents attached to the operations of a routing.

SAP Document Management service on SAP BTP. This is a separate cloud service. According to SAP Help, it runs in the Cloud Foundry environment, is based on the OASIS standard CMIS, and offers version management, folder hierarchies, access control and lifecycle status. It can use its own storage or connect CMIS-compliant repositories; SAP’s examples are “OpenText or document management systems like SAP S/4HANA DMS”. It comes as an API-based service instance, a UI5 component embedded in Fiori or custom apps, and a ready-to-use web app. When it is used with SAP S/4HANA in the application option, a document info record is created for every uploaded document (SAP Help, How to Create Documents).

Third-party DMS and archives. These connect through the interfaces described above: ArchiveLink and ILM for archiving, and CMIS for S/4HANA. In our data sheets, d.velop and nscale state a certified CMIS interface for SAP S/4HANA, and Fabasoft connects to SAP S/4HANA Cloud through CMIS on SAP BTP.

What this means for a decision: SAP DMS and the BTP service manage documents around SAP objects. The pages we checked do not describe inbound invoice capture, e-invoice validation or audited archiving for them; for those, ask your SAP partner what is licensed in your system, or compare third-party vendors in the matrix below.

Pattern 2: attachment sync and viewer integration

In the second pattern, users stay in the ERP: a button, panel or attachment tab shows the documents of the open record, such as the invoice image on the posted invoice. The connector either reads documents live from the DMS by a shared key (document, vendor or order number) or copies ERP attachments into the DMS with metadata.

What decides whether this works over years is deletion, and the ERP documentation is explicit:

• In Business Central with external storage, a toggle decides whether deleting an attachment also deletes the external file. If it is off, the file stays in storage but is no longer linked to a record (Microsoft Learn).
• In Dynamics 365 Finance & Operations, attachments deleted from Azure Blob Storage are permanently deleted unless the attachment recovery feature (deferred deletion) is turned on. Its default recovery period is 30 days; a value of zero keeps deleted attachments recoverable indefinitely. Attachment history, if enabled, is kept for 180 days by default (Microsoft Learn).
• In NetSuite, files are attached to records and transactions through the Communication subtab and are saved in a File Cabinet folder; a user needs access to that folder to view the attached file (Oracle NetSuite).

If the DMS is your archive for tax-relevant documents, deleting something in the ERP must not remove the archived original. Ask which direction the sync runs and what happens on deletion on either side.

Pattern 3: inbound invoices from capture to posting

In pattern 3, the DMS captures, checks and routes supplier invoices and hands them to the ERP for posting. For many companies inbound invoices are the reason to buy a DMS. The stages are the same for every ERP; the question is which happen in the DMS and which in the ERP.

1. ReceiveEmail inbox, scan, supplier portal or e-invoice network. One entry channel per legal entity keeps the routing simple.
2. Capture and checkRead header and line data from PDF or scan, or take it from the e-invoice XML. Check duplicates, VAT ID and mandatory invoice details.
3. Match against ERP master dataSupplier, purchase order, goods receipt, G/L account, cost centre. Needs current master data from the ERP.
4. ApproveApproval in the DMS workflow or in the ERP workflow, not both. The approval history belongs with the document.
5. Hand over to the ERPAs a parked or pending invoice, or posted directly. The ERP document number flows back to the DMS.
6. Archive with linkOriginal (image or XML), approval trail and ERP document number stored together and protected for the retention period.

Two-way and three-way matching

Three-way matching checks a supplier invoice against both the purchase order and the goods receipt before it is paid. Microsoft’s documentation for Dynamics 365 Finance describes the two levels (Microsoft Learn, invoice matching):

• Two-way matching compares the price information on the invoice with the purchase order.
• Three-way matching also compares the quantity on the invoice with the quantity on the product receipts selected for it.

Differences are compared with tolerances, by percentage or amount. Microsoft’s example: with a 5% net unit price tolerance, an invoice at 1.10 per unit for goods ordered at 1.00 is flagged, while 1.05 would pass. Whichever system matches, the DMS, an accounts payable tool or the ERP, needs current order and receipt data, and the result belongs in the approval trail; our guide from e-invoice to archive places matching in the full inbound process.

The ERPs have their own automation for parts of this chain, and a DMS has to fit into it rather than duplicate it:

• Dynamics 365 Finance: Microsoft notes that organisations often work with third parties or with its own Invoice capture to process paper invoices through optical character recognition (OCR), and its Accounts payable automation consumes the returned invoice data. Its vendor invoice automation can match product receipts to pending invoice lines, submit imported invoices to the workflow automatically and simulate posting. Imported invoice and sales tax totals can be included in the import file; by default the invoice can only be posted if they match the totals the system calculates (Microsoft Learn).
• NetSuite has Bill Capture: vendor bills sent by email or upload as PDF, JPEG or PNG become NetSuite vendor bills, with the uploaded file shown next to the created bill (Oracle NetSuite). Oracle limits it to files of up to 8 MB, one bill per file and PDFs of up to 30 pages, and states that Bill Capture is available only in the United States (Bill Capture considerations). European NetSuite users therefore rely on add-ons for invoice capture.
• Business Central handles incoming e-documents natively (pattern 4) and, according to Microsoft, is replacing its Copilot matching assistance with a Payables Agent that matches incoming purchase invoices with open purchase orders (Microsoft Learn).

Our data sheets show which vendors bring an inbound invoice module, and several specialists in the directory, such as Esker, Medius, Basware and Yooz, focus on accounts payable rather than general document management.

Pattern 4: e-invoice import

In pattern 4, structured e-invoices arrive in the ERP or the DMS and become purchase documents without re-keying. They change the integration picture, because the invoice data no longer has to be read from an image. The question becomes which system receives the XML, validates it, shows it to a person and keeps the original.

Business Central receives e-documents from an external service through a job queue or manual import and turns them into purchase drafts, invoices or orders. It identifies the vendor in a fixed order: GLN, VAT registration number, Peppol participation identifier, then name and address. It does not create a new incoming e-document for a duplicate with the same vendor, external document number and date. If a Peppol BIS 3 file contains an embedded PDF, Business Central adds the PDF as an attachment to the purchase document, and an E-invoice Lines tab shows the XML content in readable form (Microsoft Learn).

Dynamics 365 Finance imports vendor e-invoices through its Electronic Invoicing service from two kinds of channel, an email account or a SharePoint folder, and Microsoft’s set-up example uses Peppol invoices that are mapped to the vendor invoice header (Microsoft Learn).

For the DMS this leaves two set-ups:

1. The ERP receives first. The DMS archives the original XML unchanged, plus a readable view, linked to the posted invoice.
2. The DMS receives first. The DMS, or an e-invoicing provider connected to it, validates, routes for approval and hands structured data to the ERP without re-keying; the XML is still archived.

Either way, keep the original format. In Germany, for example, received electronic documents must be kept in the format in which they arrived, and the retention period for invoices is eight years; the e-invoice archiving guide sets out the rules for eight EU countries with their legal sources. Peppol support and further e-invoice formats are recorded per vendor in the data sheets.

What do “integration” claims mean in practice?

An “integration” claim can mean anything from a CSV export to full process integration, and vendor integration pages rarely say which pattern they mean. The same word covers very different depths:

1. File exchangeCSV or XML export and import, often per batch. Works with almost any ERP; nothing happens in real time.
2. Link or viewerA button or panel in the ERP opens the DMS document by a shared key. No process logic.
3. Attachment storage or syncERP attachments land in the DMS, with metadata, or are shown from it. Deletion and ownership rules decide whether it is an archive.
4. Archive interfaceStandard ERP interface such as SAP ArchiveLink or ILM, often certified. The ERP keeps the link; the DMS keeps the document.
5. Process integrationMaster data sync, invoice hand-over, status and document number back to the DMS, sometimes posting from the DMS.

Typical wording on vendor pages and what to ask about it:

• “Certified”: by whom, for which interface and release? See the certification section below.
• “Native”, “standard connector”: built by the vendor. Is it in the base licence or a priced module?
• “Via partner”: built and supported by a third party, which means two contracts and two release cycles.
• “Open API”: an interface, not an integration. Someone still has to build and maintain the connection.
• “More than 250 ERP systems”: stated by Basware (via open API) and Yooz. Ask for the connector for your ERP and version.

Our data sheets use four values for each ERP: Yes (the vendor documents an integration), Add-on module (a separately licensed module or plug-in), Via partners (built or offered by a partner) and Partly (limited in scope or version, explained in the data sheet). A dash means we found no public information, not that the integration is impossible.

Vendor × ERP matrix from our checked data sheets

Of the 36 vendors with a checked data sheet on 3 October 2026, 30 show some form of SAP integration, 15 a Business Central integration, 9 name Dynamics 365 Finance & Operations and 6 name NetSuite. The table lists the 32 vendors whose checked data sheet shows a value for at least one of the four ERP families. The SAP and Business Central columns are the data sheet values. The Dynamics 365 Finance & Operations and NetSuite columns show whether the vendor names that ERP in its list of further integrations (“named”), without a depth rating. Each vendor name links to the data sheet, where every value has its source and check date (1 to 3 October 2026).

Vendor	SAP	Business Central	Dynamics 365 F&O	NetSuite
aconso	Yes	–	–	–
agorum	Add-on module	–	–	–
Amagno	Partly	Via partners	–	–
ARXivar	Via partners	Via partners	“Dynamics 365” named, product not specified	–
Basware	Yes	–	Microsoft ERP named, product not specified	–
bitfarm-Archiv	Add-on module	–	–	–
Box	–	–	–	Named
d.velop	Yes	Yes	Named	Named
DocuWare	Yes	–	–	–
Doxis	Yes	Yes	Named	–
easy software	Add-on module	Add-on module	Named	–
ecoDMS	Via partners	Via partners	–	–
ELO	Yes	Yes	–	–
enaio	Yes	Yes	Named	–
Esker	Yes	Yes	Named	Named, via partner
forcont	Yes	–	–	–
Hyland	Add-on module	–	“Microsoft Dynamics” named, product not specified	–
IBM FileNet	Add-on module	–	–	–
JobRouter	Add-on module	–	–	–
Kendox	Yes	Yes	Named	Named
Laserfiche	Partly	–	–	–
M-Files	Add-on module	–	–	–
Medius	Yes	Yes	Named	Named
nscale	Yes	–	–	–
OpenText	Add-on module	–	“Dynamics 365” named, product not specified	–
PROXESS	Add-on module	Add-on module	Named	–
SharePoint	–	Partly	–	–
Siav	Yes	–	–	–
Starke-DMS	Add-on module	–	–	–
Therefore	Add-on module	Add-on module	–	–
windream	Yes	–	–	–
Yooz	Yes	Yes	Named	Named

The four other checked data sheets, DATEV DMS, DOCUframe, docuvita and LogicalDOC, show no public information for any of these four ERP families.

What the totals say, and the qualifiers behind some cells

Across all 36 checked data sheets, the SAP column reads Yes 15 times, Add-on module 11 times, Partly and Via partners twice each, and shows no public information six times. For Business Central, 21 data sheets show no public information; the rest split into Yes (8), Add-on module (3), Via partners (3) and Partly (1). Nine vendors name Dynamics 365 Finance & Operations, six name NetSuite. In this group, SAP is by far the best-covered ERP; for NetSuite the choice is narrow, and half of the six vendors that name it are accounts payable specialists.

Several cells need their note from the data sheet:

• aconso integrates with SAP HCM and SAP SuccessFactors; it is a vendor for HR files, not for finance documents.
• Laserfiche has discontinued its own SAP ArchiveLink integration (support for the cloud version ended on 7 November 2024, for self-hosted on 31 December 2025) and refers to pre-built connectors or integration platforms instead.
• Amagno lists SAP Business One and SAP ERP as interfaces, with details “to follow” according to the vendor.
• bitfarm-Archiv offers the SAP content server and ArchiveLink connection in the Enterprise version only for installations that bitfarm supports directly.
• Hyland’s integration for SAP S/4HANA is initially available for its Content Innovation Cloud, with OnBase connected through a federation service.
• SharePoint shows “Partly” for Business Central because Business Central can store attachments in SharePoint libraries; that is pattern 1 without retention logic.
• JobRouter and Starke-DMS name older Microsoft ERPs (Dynamics AX, NAV, GP; NAV/Navision and AX), which are not the same products as Business Central or Dynamics 365 Finance & Operations.

Beyond the four ERP families: Sage and Odoo

Our data sheets also record Sage integrations, with the same four values. Examples, as checked between 1 and 3 October 2026:

• Yes: d.velop (standard connectors for Sage 100, Sage 50 Handwerk, Sage X3 and Sage b7), docuvita (Sage Office Line and Classic Line in its interface list), Yooz (Sage X3, Sage 300, Sage Intacct).
• Add-on module: Open Bee (connector for Sage 100, 50, X3 and 1000, among others), Zeendoc (Sage 100, connector as an option), Starke-DMS (Sage 50, Office Line and Classic Line in its interface list).
• Via partners: Esker (Sage X3, Sage FRP 1000 and Sage 100 through the partner Flowwa), Medius (Sage X3 and Sage Intacct with Acuity Solutions), ecoDMS and easy software (Sage 100).
• Partly: JobRouter (Sage 200 in Switzerland; Sage 100 in Germany on request).

Sage is a family of different products, so ask for the exact product and version. For Odoo, one checked data sheet, agorum, names it among further ERP integrations. Odoo itself is listed in our directory with its own Documents app, without a checked data sheet (odoo.com).

To filter by your ERP together with deployment, hosting country and e-invoice formats, use the DMS finder.

SAP certification: what does it prove?

An SAP integration certificate proves that one interface scenario works with one SAP release; it says nothing about the rest of the DMS. SAP’s documentation names certification for storage providers explicitly: providers of storage systems can receive ILM certification from SAP, and the documentation refers to the SAP Integration and Certification Center for the current list of certified providers (SAP Help). A certificate is tied to an integration scenario and an SAP release. Vendor pages show what that looks like: Doxis lists, among others, the scenario “S/4-BC-AL 7.40” for its HTTP content server and an ILM certification via its WebDAV connector; Therefore lists “BC-AL 7.20” for SAP NetWeaver and “S/4-BC-AL 7.20” for SAP S/4HANA, with certification dates between 2012 and 2021.

Sixteen of our checked data sheets mention an SAP certification. They fall into different kinds:

• Archive interfaces (ArchiveLink, some with ILM): Doxis and windream (ArchiveLink and ILM), enaio, forcont, IBM FileNet, PROXESS and Therefore (ArchiveLink).
• CMIS interface for SAP S/4HANA: d.velop and nscale.
• S/4HANA integration or connector: DocuWare, Esker (SAP S/4HANA Cloud), Medius, Siav.
• General statements: Basware (certified integrations to major ERPs), easy software (on-premises products SAP-certified according to the vendor), aconso (certified SAP partner, solutions in the SAP Store).

Keep three things apart when you read such claims:

1. An integration certificate names one interface scenario and one SAP release, with a date, as the vendor pages above show. It concerns that interface; it is no statement about the DMS’s archive compliance, its workflow or its other interfaces.
2. A partner level, such as the “SAP Silver Partner” status that d.velop and Kendox state, or membership in SAP PartnerEdge Build as Medius states, describes the partnership with SAP, not a certified scenario.
3. A listing in the SAP Store, which aconso and Esker state, is a sales channel. Ask separately whether the listed product carries an integration certificate.

Certificates also age. Therefore states on its certification page that its certificates were valid for three years and continuously renewed, and that SAP no longer issues this type of certification as of 2024. We could not confirm that statement in SAP’s own documentation, so treat it as the vendor’s information and ask each vendor for the scenario name, the SAP release, the date and, if relevant, the successor certification.

On the Microsoft side, our data sheets record one comparable statement: Medius describes its Business Central integration as validated by Microsoft AppSource, Microsoft’s app marketplace. Ask any vendor that cites such a validation what exactly was checked.

Which document management system for SAP or another ERP? Questions to ask before you shortlist

The right document management system for SAP or another ERP is the one that answers these questions in writing for your ERP version. Send the same questions to every vendor and ask for written answers that name the ERP, version and deployment (cloud or on-premises) they apply to:

• Which of the four patterns does your integration cover for our ERP, and which depth (file exchange, link, attachment sync, archive interface, process integration)?
• Is the connector built by you or by a partner, is it in the base licence or a separate module, and what does it cost per year?
• For SAP: which ArchiveLink, ILM or CMIS scenario is certified, for which SAP release, and when was it certified?
• Which ERP versions and deployments are supported, for example S/4HANA Cloud Public or Private Edition, Business Central online, Finance & Operations in a Microsoft-managed environment?
• Which master data flows from the ERP to the DMS (suppliers, orders, receipts, accounts, cost centres), in which direction and how often?
• Does an invoice arrive in the ERP parked, pending or posted, and does the ERP document number flow back to the DMS?
• What happens to the archived original when a record or attachment is deleted in the ERP?
• How are e-invoices (Peppol BIS, XRechnung, ZUGFeRD/Factur-X, FatturaPA, KSeF) received, validated, displayed and archived in their original XML?
• Who supports the integration after an ERP update, and how quickly after a new ERP release is it tested?
• Can you name two reference customers on our ERP and version who use the same pattern?

Migration: moving documents between DMS and ERP

Changing the DMS behind an ERP, or moving documents out of the ERP into a DMS, is mostly a question of keeping links and evidence intact. The ERPs document the tools they offer:

• Business Central: once external storage is enabled, only new attachments go there. Existing attachments move with the Storage Sync action, which can also move files back into the database. Copy Company and environment backup or restore do not copy externally stored files; the attachment records keep pointing to the original location until you run the Migrate Files action (Microsoft Learn).
• Dynamics 365 Finance & Operations: from version 10.0.40, an Export attachments function exports attached files per table and date range as ZIP archives, with metadata as separate JSON files if selected (Microsoft Learn). Because the files are stored outside the database, a database restore affects only the attachment records, not the files.
• NetSuite: a File Cabinet folder downloads as a ZIP file that keeps the folder structure. Oracle recommends working with files of 100 MB or smaller, and folder permissions also apply to downloads (Oracle NetSuite).
• SAP: documents linked through ArchiveLink are reached through the link on the business object (SAP Help). When the content repository changes, plan with the old and new vendor how documents and links are moved, and keep the old repository readable until the move has been checked.

In every migration, the legal retention period does not restart, e-invoices stay in their original XML, and the move belongs in your procedure documentation: what was moved, when, with which checks (counts and checksums per document class) and who signed off. Test with one closed fiscal year first.

Which integration pattern do you need?

Four questions about invoices, e-invoices, SAP retention and where users work decide the pattern before you compare vendors.

1. Should supplier invoices be captured, checked and approved outside the ERP?Yes: pattern 3. Shortlist vendors with an inbound invoice module and a documented connector for your ERP.No: the ERP's own automation may be enough; plan pattern 1 for the archive.
2. Do you receive structured e-invoices in volume?Yes: decide which system receives first, and make sure the XML original ends up in the archive (pattern 4).No: PDF capture remains the main input; check the e-invoice plans for your countries anyway.
3. Do you run SAP and need retention-controlled archiving?Yes: ask for certified ArchiveLink and, if retention is managed in SAP, ILM support.No: ArchiveLink alone, or a connector-based link, may be sufficient.
4. Should users stay in the ERP screen?Yes: pattern 2 with a viewer or panel in the ERP, and clear rules for deletion.No: a link and a search in the DMS client are enough.

Start with the documents, not the vendor list: which document types belong to which ERP objects, which system owns the original and where approval happens. Then shortlist from the matrix and test the connector on your own ERP version in a pilot before you sign. Ask for each interface as a separate line in the offer; our cost guide shows how to make offers comparable. The DMS finder combines the ERP filter with deployment, hosting country and e-invoice formats; all data sheets are in the DMS directory, more guides in the guides section.

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