Book a free consultation (opens in a new tab)

Document Management

ERP Document Management Module Services

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.

  • 1 clickFrom the record to the document
  • 5 to 10 yrCommon statutory retention range
  • OneCurrent version, the rest superseded
  • FullLog of view, change and approval

Why It Matters

The benefit is invisible daily and obvious the week of an audit

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.

  • 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.

  • 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

The document lifecycle, from arrival to disposal

  1. Capture

    Scanned at a desk, received at a monitored email address, photographed on a phone in the yard, or generated by the ERP itself. Source, sender and timestamp are kept from the first moment.

  2. Classify and link

    Document type, dates and reference numbers applied, then attached to the record it belongs to. Nothing is filed to a folder alone, because a folder cannot tell you which transaction the file supports.

  3. Route for approval

    Sent to the approvers the document type and value require, with reminders, delegation and a recorded decision. Approved, rejected with a reason, or returned for a corrected version.

  4. Store with controlled access

    Held as the current version with role-based rights, full text and metadata search, and a log of every view, download, edit and share. Superseded versions stay, clearly marked as superseded.

  5. Retain then dispose

    A disposal date calculated at filing from the retention rule for that document class, legal hold where a matter is live, and deletion executed as policy rather than left to nobody.

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, revision numbering and effective dating configured, with a check that only the current revision reaches 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 where a view must be evidenced.

  • Retention schedule

    Retention periods per class across your jurisdictions, legal hold, an archive tier for cold storage, and a disposal run somebody signs off.

Why teams bring us in to set this module up

  • We start from the records, not the folders

    The first workshop maps which document types attach to which ERP records. Folder structure is an output of that, and a minor one, not the design.

  • We will tell you not to migrate everything

    Twelve years of scanned PDFs with no metadata rarely justify the cleansing cost.

  • Retention written down before go-live

    We build the schedule with your finance and legal people, per class and jurisdiction, so disposal is a policy the system executes.

  • Controlled documents treated as a risk item

    Drawings, specifications and work instructions get their own revision rules and a check that the floor can only open the current version.

  • Capture at the point of work

    If filing a document means walking to a scanner, it will not happen. We put capture where the document is created, including on a phone in the yard.

  • Platform neutral

    We deliver on ERPNext, Odoo and SAP and will say when the native document handling is enough and a separate document system would be a cost with no gain.

Document management questions

How do documents get attached to ERP records?

Either at the point the record is created, by dragging the file onto the purchase order or the invoice, or automatically by a rule that reads an identifier and files the document against the matching record. The important part is that the link is a real relationship in the database, not a folder path typed into a note field. Once it exists, the document appears on the record for anyone with rights to see it, and it also appears on anything the record is joined to, so the invoice image is reachable from the purchase order, the goods receipt and the posted journal entry.

Can supplier invoices be captured from email automatically?

Yes. You publish one address, for example accounts payable at your domain, the mailbox is monitored, and every attachment that arrives is filed as an incoming document with the sender, subject and timestamp kept as metadata. That alone removes the step where somebody downloads a PDF to their desktop and forgets it. Reading the numbers off the invoice and matching it to a purchase order is a separate capability. That sits on our Invoice OCR and Data Extraction page, and it works well once email capture is already in place.

How does version control work for drawings and specifications?

One version is current and everything else is retained but marked superseded, so a shop floor terminal can only open the live revision. Each new version records who uploaded it, who approved it, when it took effect and what changed. The classic failure is a production line building to a drawing revision that was replaced three months ago. That is a scrap and safety problem, not an admin one, and it is the single strongest reason to put controlled documents in the ERP rather than on a network share.

Who can see restricted documents like contracts and salary letters?

Only the roles you grant, and the rule should sit on the document type and the record, not on a folder. Salary letters are visible to HR and the individual, contracts to legal and the contract owner, legal correspondence to a named list. The system should also log reads, not only edits, because in a dispute about a leak the question is who opened the file. If your current answer is that everyone in the company could open the share if they knew where to look, that is the gap.

How long do we have to keep documents?

It varies by document type and by jurisdiction, and several years is the common range. Tax and accounting records, employment records, product safety and test certificates and contract files all sit on different clocks, and a group operating in more than one country will have more than one rule for the same document type. Set the retention period per document class in the system, let it calculate the disposal date at filing, and allow a legal hold to override it. Keeping everything forever is not a safe default, because it grows both storage and liability.

Are electronic signatures legally valid?

In most jurisdictions a properly evidenced electronic signature is recognised for ordinary commercial documents, with a short list of exceptions such as some property and succession instruments. The distinction that matters is between an image of a signature pasted into a PDF, which proves almost nothing, and a signature backed by identity verification, a timestamp, a tamper-evident hash of the signed document and an audit record. Ask your counsel which of your document types need the higher standard, then configure the two levels separately rather than treating every signature the same.

Related

The other services in this section, and related pages from TCB Infotech.

Get Your Documents Onto Your Records

No commitment. A straight view on what to file, what to link and what is not worth migrating.