A Document Is Only Useful When It Is Attached to the Transaction
An auditor asks for the signed delivery note behind one invoice from fourteen months ago, and somebody loses half a day in a shared drive. A customer denies receiving the goods and nobody can find the proof of delivery because it was never scanned. A shared drive organised by month is not document management, it is a filing cabinet with a search box. Document management inside the ERP means the document lives on the record, one click from the transaction.
50+ ERP and software projects. Zero failed projects since 2021.
The benefit is invisible daily and obvious the week of an audit
That is exactly why this module gets deferred, and exactly why deferring it is expensive. You cannot retrospectively attach documents to two years of transactions. Whatever was not filed at the time stays unfiled, and the gap only shows up when somebody outside the business asks a question you have to answer.
Retrieval should be a click, not a search
The core idea is small and it changes everything. A document is linked to the customer, supplier, purchase order, invoice, employee or asset it relates to, so you reach it from the transaction rather than hunting for it. Open the posted journal entry and the supplier invoice image is on it. Open the sales order and the signed delivery note is on it. Open the asset and the warranty, the commissioning certificate and the purchase invoice are all there. Filenames are the worst possible index and every business relies on them anyway, because a folder tree cannot express that this PDF belongs to that transaction.
- The link is a relationship in the database, not a path in a note field.
- One document can hang off several records at once, and does.
- Search runs on metadata and on the linked record, not just the filename.
A superseded drawing on the shop floor is a scrap problem
Version control matters most on the documents that change: drawings, specifications, contracts, work instructions and procedures. One version is current, superseded versions are retained but clearly marked, and anybody can see what changed and who approved the change. The classic failure is a production line working to a revision that was replaced three months ago, because the old PDF was still sitting in a folder somebody had bookmarked. That is scrap, rework and in some industries a safety finding. It is not an administrative inconvenience, and it is the reason controlled documents belong in the system rather than on a network share.
- Only the live revision is servable to a shop floor or field terminal.
- Every version carries its author, approver, effective date and change note.
- Superseded copies are kept for the audit, but cannot be mistaken for current.
Six areas, and none of them is a folder structure
If a document management project produces a better organised shared drive, it has failed. These six are what separate a document system from storage.
The document lifecycle, from arrival to disposal
What we set up when we configure this module
Document type register
Every document class your business handles, with its naming, its mandatory metadata, its retention period and the record types it is allowed to attach to.
Capture channels
Scanner profiles, a monitored inbound mailbox per function, and mobile capture for delivery notes, site photos and signed paperwork collected away from a desk.
Version control rules
Controlled document classes identified, revision numbering agreed, effective dating configured and a check that only the current revision is reachable from the floor.
Approval matrices
Who signs what, at which value, with which delegate, plus escalation on documents left pending and a rejection path that keeps the reason with the file.
Access and logging policy
Role-based rights per document class, restricted categories for contracts, legal and payroll, and read logging turned on where a view itself has to be evidenced.
Retention schedule
Retention periods per class across the jurisdictions you operate in, legal hold, an archive tier for cold storage, and a disposal run somebody actually signs off.
What you notice once documents live on the records
What this connects to
Document management is only worth having because of what it attaches to. These three are where the volume and the value sit.
Why teams bring us in to set this module up
Document management questions
How do documents get attached to ERP records?
Can supplier invoices be captured from email automatically?
How does version control work for drawings and specifications?
Who can see restricted documents like contracts and salary letters?
How long do we have to keep documents?
Are electronic signatures legally valid?
Get Your Documents Onto Your Records
Book a free consultation. We will go through the document types your business actually handles, where each one is created, what it should attach to, who has to approve it and how long you are obliged to keep it, and tell you whether your ERP already does enough.
Book a Free Consultation →No commitment. A straight view on what to file, what to link and what is not worth migrating.
What ERP Document Management Actually Does
How documents get in, what they attach to, who approves them, who is allowed to open them, and what happens to them years later when the retention clock runs out.
From the scanner to the disposal run
Documents arrive already attached to something
Capture happens where the document is created. A scanner profile at the desk, a monitored inbound mailbox so a supplier invoice sent to your accounts address is filed the moment it lands, and mobile photo capture for signed delivery notes and site condition photos taken in the yard. Metadata is applied at capture, while somebody still knows what the document is, and the file is attached to the customer, supplier, order, invoice, employee, project or asset it belongs to. Reading the values off the page so they do not have to be keyed is a separate capability and sits on our Invoice OCR and Data Extraction page.
- Scan, email inbound and mobile capture, all landing in the same register.
- Document type, dates and references captured at the point of filing.
- The link is a database relationship, so the file follows the record.
One current version, and a signature with evidence behind it
Controlled documents get revision numbering, effective dates and a rule that only the current version is reachable from a shop floor or field terminal. Superseded revisions are retained and labelled so nobody can mistake one for live. Documents that need sign-off are routed by role and by value, with reminders on anything left pending, delegation when an approver is away, and the decision recorded against the document instead of buried in a mailbox. Where electronic signature is used, the useful kind is identity verified and timestamped with a tamper-evident hash, not an image of a signature pasted onto a page.
- Revision history with author, approver, effective date and change note.
- Approval matrices by document type, value band and role.
- Signature levels configured separately for routine and high-risk documents.
Who saw it, who changed it, and when it gets deleted
Contracts, salary letters and legal correspondence are restricted by role, and reads are logged as well as edits, because in a leak the question is who opened the file. Every document carries an unbroken trail of capture, change, approval, view and export, which is what gives it weight when an auditor or a court asks. Retention is set per document class and per jurisdiction, the disposal date is calculated at filing, legal hold freezes anything under dispute, and the disposal run is a scheduled job somebody signs. Keeping everything forever is not a safe default. It grows storage and it grows liability.
- Role-based rights per document class, with restricted categories.
- View, download, edit and export all logged against the file.
- Retention schedule, legal hold and a signed-off disposal run.
What the configured module delivers
Document type catalogue
Every class you handle, with its mandatory metadata, the records it may attach to and its retention period, agreed in writing before configuration.
Working capture channels
Scanner profiles, an inbound mailbox per function and mobile capture, tested with your own paperwork rather than with a sample PDF.
Search that finds things
Query by metadata, document type, date range, value and linked record. Filenames are the worst index available, so nothing depends on them.
Approval and signature setup
Routing by role and value, escalation on pending items, and electronic signature configured where it is legally recognised for that document type.
Access matrix and logging
Rights per role and class, restricted categories for legal, contracts and payroll, and read logging switched on where a view has to be evidenced.
Retention and archive plan
Periods per class across your jurisdictions, an archive tier for cold storage, legal hold, and a disposal run with a named owner and a sign-off.