Vision & BeyondSince 1996

Document Management, ECM and Records Management: Where to Store Scanned Documents

In this article
  1. The options at a glance
  2. Document management and records management: the difference
  3. What ECM adds
  4. Workflow and case management: from storing to processing
  5. Where SharePoint fits
  6. Getting scanned documents in: capture software and connectors
  7. How to choose
  8. Common pitfalls
  9. How Vision and Beyond helps
  10. Frequently asked questions
  11. Where to start

Scanning turns paper into files. Where those files go next decides whether anyone can find them, trust them and keep them for the right length of time. Document management, enterprise content management (ECM), records management, workflow and SharePoint overlap, and the terms are often used loosely. This guide explains what each one does, so you can choose before you scan.

Key points

  • Document management helps people find, share and update the current version of a file. Records management proves that a record is authentic and applies retention, disposal and audit rules. Many organisations need both.
  • ECM brings capture, document management, workflow and records management together on one platform. SharePoint can cover a good part of this, depending on how it is configured and licensed.
  • Scanned documents are most useful when they arrive with their index data, delivered by a capture connector into the right fields, not as loose files in a folder.
The question each system answers. Document management: where is the current version and who is allowed to see it. Workflow and case management: what happens next and who is responsible. Records management: is this the authentic record and when can it be disposed of. ECM: all of these, plus capture and integration, on one platform.
Which question each system answers

This guide covers the main ways to store and manage scanned documents and records, how they differ, where SharePoint fits, and how documents and their index data get in. It is general information, not legal advice, so check the records obligations that apply to your sector and jurisdiction.

The options at a glance

There is no single right answer, because documents serve different purposes. A signed contract, a patient file, an invoice waiting for approval and a working draft need different controls. This table is a quick guide, and each option is explained below.

OptionWhat it doesBest forWatch out for
File shares and cloud storageFolders of files with basic permissionsSmall volumes and working filesNo version control, retention or audit trail, and hard to search by index data
Document managementLibraries with metadata, search, versions and permissionsEveryday documents that people share and updateDoes not by itself prove that a document is an authentic, unaltered record
Records management (EDRMS)Classification, retention, disposal, holds and an audit trailRecords with legal, regulatory or archival requirementsNeeds a file plan and discipline, and can feel heavy for everyday files
ECMOne platform for capture, document management, workflow, records and integrationLarger organisations with many content types and processesScope, licensing and governance effort
Workflow and case managementRoutes documents, tasks and approvals to the right peopleClaims, applications, invoices and requestsNeeds a records store behind it for the finished documents
Line-of-business systemsAttach documents to a customer, patient, asset or transactionDocuments tied closely to one systemDocuments can be locked inside, so plan how to export and retain them

Document management and records management: the difference

Document management is about working with documents. It helps people find the right file, see the current version, share it safely and control who can change it. Typical features are libraries or folders, metadata, search, version history and permissions.

Records management is about evidence. A record is information kept to show what was decided or done, such as a contract, a claim, a clinical note or a signed approval. A records system keeps the record authentic and complete, stops it being changed without a trace, applies a retention schedule, and shows who disposed of what, and when.

Records management typically adds:

  • Classification. Each record is placed in a classification scheme or file plan.
  • Retention and disposal. Rules for how long each class is kept, with approval before anything is destroyed.
  • Holds. The ability to suspend disposal when records are needed for legal or regulatory reasons.
  • Audit trail. A log of who viewed, changed, moved or disposed of a record.
  • Protection. Records cannot be edited or deleted outside the rules.

The two overlap. A document is often drafted in a document management system, then becomes a record when it is finalised or approved. In Australia, a system that combines both is often called an EDRMS, short for electronic document and records management system. Whether a scanned copy can replace the paper original is a records question, covered in our guide to keeping records compliant.

What ECM adds

Enterprise content management (ECM), now often called content services, is a platform or a set of connected tools for capturing, storing, managing, processing and preserving content across an organisation. Where document management and records management each solve one problem, ECM aims to solve them together, for many kinds of content, in one governed place.

An ECM platform typically adds:

  • Capture. Scanning, email, forms and uploads feeding one repository.
  • A shared repository. Consistent metadata and security across content types.
  • Workflow. Routing, approvals and deadlines built around the content.
  • Records management. Retention rules that apply as content is created, not afterwards.
  • Search. One place to look across documents, emails and scans.
  • Integration. Links to finance, HR, case and customer systems.

The benefits are consistency and control. The costs are scope, licensing and the effort to agree a metadata model and governance. ECM suits organisations with many content types, several departments and regulatory obligations. It is rarely the right first step for a team that only needs to stop losing files.

Workflow and case management: from storing to processing

Storage answers where a document is. Workflow answers what happens next. A workflow routes a document and its data to the right people, collects approvals, sets deadlines and records what was done. Common examples are invoice approval, application assessment, claim handling, contract review and customer requests.

Case management goes a step further. It gathers the documents, tasks, notes and decisions for one client, patient, claim or matter into a single case, so the whole story can be seen in one place.

Both depend on good index data. When a capture system reads the supplier name, invoice number and amount from a scanned invoice, that data can start an approval workflow without anyone retyping it. When the work is finished, the completed documents should pass to a records store, so retention rules still apply. Our guide to what happens after the scan covers how captured documents feed these processes, and our guide to RPA and AI agents explains where automation fits.

Where SharePoint fits

Microsoft SharePoint is the document store many organisations already have, which makes it a natural destination for scanned documents. Used well, it provides document libraries with metadata columns, content types, version history, permissions and search, with links to Microsoft 365 and Teams.

For retention and records, SharePoint works with Microsoft Purview. Retention labels can keep or delete content at item level, and they can also mark an item as a record. A default label can be applied to everything in a library, folder or document set, and labelling actions are written to an audit log. Which features you can use depends on your Microsoft 365 plan and configuration.

SharePoint needs planning to work well as a document and records store. Decide:

  • Structure. The sites and libraries, arranged the way people work.
  • Metadata. Columns and content types that match your index fields.
  • Permissions. Who can see what, especially for sensitive records such as health, HR and legal files.
  • Retention. Labels aligned with your retention schedule, and who may apply them.
  • Arrival. How scanned files get in, ideally with their metadata already filled in.

SharePoint can be enough for many organisations. Where recordkeeping requirements are strict, classification schemes are complex, or disposal needs formal approval and certification, some organisations add a dedicated records management system alongside it. Check your own obligations, and test with a small batch of real documents before you commit.

Getting scanned documents in: capture software and connectors

Between the scanner and the store sits capture software. It batches pages, separates documents, runs OCR, reads barcodes and cover sheets, extracts index data, lets a person check anything uncertain, and then exports the result. Two examples from Kodak Alaris are Kodak Capture Pro Software, which runs on a scanning workstation, and Kodak Info Input Solution, a web-based capture platform that supports scanning from remote locations. Our guide to why we recommend Kodak Alaris scanners explains how Capture Pro works with their scanners.

How the result reaches the destination matters as much as the scan. There are two broad approaches.

Hot folder compared with a capture connector. With a hot folder, files arrive first and index data is often added afterwards by hand. With a capture connector, files and index data arrive together in the matching fields.
A hot folder passes on files, a connector passes on files and index data
  • Hot folder or manual upload. The capture software saves files to a folder, and a person or a script picks them up. It is simple, but index data is often added afterwards, which means retyping, gaps and errors.
  • Connector. The capture software sends each file together with its index data directly to the destination, filling the matching fields. Kodak publishes export connectors for Microsoft SharePoint and a range of ECM platforms. The list changes, so check the current one for your system.

A connector keeps the index data attached to the file and lets validation happen before the import. It can also deliver the data to a queue for automation tools such as RPA, so a process starts as soon as a document arrives.

If the capture software has no ready-made connector for your system, there are other routes: exporting files with an index file that an import routine reads, or connecting through an API. We can look at what a connector would involve for a particular system and requirement.

How to choose

Start with what the documents need to do, not with the product. These questions help:

  • What must you be able to prove, and to whom, such as regulators, auditors or courts?
  • How long is each type of record kept, and who approves disposal?
  • Which platform do you already own, and how much of the need can it meet?
  • How many people need access, and to which types of content?
  • What index data does each document type need, and where will it come from?
  • Which business systems need to see these documents?
  • How sensitive is the content, and who must not see it?
  • Can you get everything out again, with its metadata, if you change systems?

Test your answers on a pilot of a few hundred real documents before you scan the backlog. A pilot shows quickly whether the index fields can be filled, whether the connector or import works, and whether people can find what they need.

Common pitfalls

  • Scanning first and choosing the destination later. It usually means reprocessing the files.
  • Treating a shared drive as a records system. Folders alone do not apply retention or keep an audit trail.
  • Too many index fields. If nobody has the information to fill them, they are left empty or filled with guesses.
  • No owner for the file plan and metadata. Without one, they drift and search gets worse.
  • Forgetting disposal. Keeping everything forever adds cost and risk.
  • Locking documents inside one system. Plan an export path, with metadata, before you need it.

How Vision and Beyond helps

Vision and Beyond has worked with scanning, document capture and records for over 30 years. We supply scanners and capture software from Kodak Alaris, organise outsourced scanning, and help organisations connect captured documents to the systems they use. We analyse your systems and work out how to move data between them, instead of retyping it. Where there is no ready-made connector, we can look at what building one would involve, depending on the system and what you need.

To see how scanning fits in, read our guide to document scanning services.

Frequently asked questions

What is the difference between document management and records management?

Document management helps people find, share and update documents. Records management keeps evidence: it protects records from change, applies retention and disposal rules, and keeps an audit trail. Many systems and organisations combine the two.

What is ECM?

Enterprise content management (ECM) is a platform, or a set of connected tools, that captures, stores, manages, processes and preserves content across an organisation. It usually combines document management, workflow and records management.

What is an EDRMS?

An EDRMS is an electronic document and records management system. The term is common in Australia for a system that combines document management with records management, particularly in government.

Is SharePoint a records management system?

SharePoint is a document management platform that can also apply retention and records controls through Microsoft Purview retention labels, depending on your Microsoft 365 plan and configuration. Whether that meets your obligations depends on your requirements, so check them and test before you rely on it.

Do I need ECM if I already use SharePoint?

Not necessarily. Many organisations manage well with SharePoint, planned properly. A larger platform or a dedicated records system makes sense when requirements are strict, content comes from many systems, or classification and disposal need formal control.

What is a capture connector?

A capture connector is software that sends scanned files and their index data from the capture software straight into the fields of another system, such as SharePoint or an ECM platform, without anyone retyping the details.

Can scanned documents go into SharePoint with their index data?

Yes, where the capture software or an integration fills SharePoint columns from the index data. Plan the columns first, then map each index field to a column.

Where to start

Start with four questions: what documents you have, which of them are records with legal or regulatory requirements, where they need to end up, and what index data each type needs. Decide the destination and the index fields before you scan, and test with a small batch first.

If you would like to talk it through, send us a message with what you have, where it needs to go and the problem you want to solve, and we will come back to you with how we would approach it.

These guides may also help:

Talk to us about a scanning project

Tell us what you have, roughly how much, and what you need to do with the files. We will come back to you with how we would approach it.

Email
sales@vision-and-beyond.com.au
Phone
02 4311 6379
Post
PO Box 441, Pyrmont NSW 2009

Send us a message

Include what you scan, roughly how much, and what you need to do with the files.