Document Management for SMEs: What You Need and When an ERP Is Enough

Document management is how a company decides where each document ends up, who can see it, which version is the right one and how long it has to be kept. In most SMEs nobody has ever made that decision: documents sit wherever the person who received them put them, spread across the shared folder on the server, the accounts team's inbox and the field technician's phone. Document management software exists to bring rules to this mess, but it is not always the first step and sometimes you don't need it at all.

The line between document management, shared folders and legally compliant archiving (which is a different thing) decides almost everything else: whether you need dedicated software, or whether your documents are better off inside the business software you already use.

What document management means in practice

Strip away the textbook definitions and a document management system does five things:

1. It collects documents from every channel they arrive through (email, scanner, app, customer portal) in a single place.
2. It classifies them with the data you need to find them again: document type, customer or supplier, job, date, status.
3. It keeps versions, so you know which one is the latest and what the earlier ones said.
4. It decides who sees what: payslips are opened by HR, purchase price lists by the purchasing manager.
5. It knows how long each type of document must be kept and what to do with it afterwards.

The more advanced features (approval workflows, deadlines, signatures, automatic reading of PDFs) sit on top of these five, and they only make sense if the basics work. A company that has never decided what a supplier invoice should be called and where it goes will not fix the problem by buying a program with OCR.

One useful clarification, because many Google results on this topic in Italy are manuals written for public bodies: the rules on electronic registry logging, homogeneous organisational areas and the document management officer set out in the AgID Guidelines on electronic documents (AgID is the Italian digital agency) apply to public administrations. A private SME in Italy does not have to log its incoming mail in a registry or write a management manual. The parts that do concern it are those on electronic documents (how they are created, how copies are made, signatures) and on archiving: this is stated in Article 2(3) of the CAD, the Italian Digital Administration Code, which the Guidelines themselves cite at the start. We cover archiving further down.

Shared folders or document management: where the line falls

A shared folder on a server or a generic cloud drive is already a form of document management, just a very basic one. It works well as long as there are few documents, few people handle them and everyone knows by heart where things are. It stops working at very recognisable moments: the quote exists in four versions with “final”, “final2” and “final_ok” in the file name, the colleague on holiday is the only one who knows where the contract was saved, the accountant asks for a delivery note from two years ago and someone spends the morning looking for it.

The row about the link to business software is the one that matters most for an SME, and the one people talk about least. A document makes sense in relation to the thing it refers to: the delivery note to the order, the service report to the job, the certificate to the installation, the contract to the customer. If the document lives in one place and the thing it refers to lives in another, someone has to bridge the gap by hand every time.

Document management and legally compliant archiving are two different things

This is where a lot of confusion starts, partly because some vendors sell the two together. Document management covers the everyday work on documents: finding them, updating them, sharing them. Legally compliant archiving (“conservazione a norma” in Italy) covers the long-term legal value of the documents the law requires you to keep.

The basic reference for an Italian company is Article 2220 of the Italian Civil Code: accounting records must be kept for ten years from the date of the last entry, and the same period applies to invoices, letters and telegrams received and copies of those sent. Article 43 of the Italian Digital Administration Code states that these obligations can be met with electronic documents, provided the procedures guarantee conformity with the originals and follow the AgID Guidelines. Article 44, paragraph 1-ter, specifies that where there is a retention obligation, including for a private party, the archiving system must ensure authenticity, integrity, reliability, legibility and retrievability. Paragraph 1-quater allows archiving to be entrusted to an external provider offering organisational, technological and data protection guarantees.

The AgID Guidelines add a detail that makes the difference clear: the archiving system must be “at least logically separate” from the document management system. In practice, the program you work in every day and the archive with legal value must stay separate at least at a logical level, even when the same company supplies both and they run on the same platform.

For e-invoices there is a free shortcut. The Agenzia delle Entrate, the Italian Revenue Agency, offers a free legally compliant archiving service through its Fatture e Corrispettivi portal, which you activate by signing a service agreement. It can also retrieve invoices that have already passed through the SdI (the Italian e-invoicing exchange system), going back at most to 1 January of the second year before you sign up. It only covers e-invoices that went through SdI: contracts, delivery notes, service reports and HR documents are left out.

The practical advice is to decide first who archives what (the Agency's service for invoices, an external archiving provider for the books and other mandatory documents, or your accountant if they already do it) and only then choose the tool for day-to-day work. On these points the final word belongs to your accountant: we take care of the software side.

What document management software should do

If you have decided you need a tool, these are the features to check in a demo. Ask to see the system with your own documents, because the vendor's sample documents always work.

Filing with metadata you actually use

Each document type should have a few mandatory fields, the ones you need to find it again: for a supplier invoice, supplier, number, date and job; for a service report, customer, installation, technician and date. The more fields you ask for, the fewer get filled in. If the system reads the PDF and suggests the values, even better, but a person has to confirm them.

Versions and status

A quote moves from draft to sent to accepted; a quality procedure at revision 3 replaces revision 2. Whoever opens the document must see straight away whether it is the latest valid version, and whoever needs to must be able to go back to the earlier ones.

Role-based permissions

Shared folders think in whole folders, while in a company permissions follow roles: sales staff see their own customers' contracts, the accounts team sees all invoices, technicians see the documentation for the installations they work on. Article 5 of the GDPR requires you to protect personal data against unauthorised processing and not to keep it longer than needed for the purpose you collected it for. With employee and customer documents, permissions and deletion periods have to be set up in the tool from day one.

Search and activity log

Search must work by content and by data (“all delivery notes from supplier X in 2025 linked to job 118”), not just by file name. The log must show who uploaded, edited or deleted a document and when. If your company is working towards ISO 27001 certification or already has it, a log like this is also useful evidence during an audit.

Workflows and deadlines

Supplier invoice approval, contract review, certificate renewal. This is where a standard DMS performs best, as long as the workflow is simple and someone in the company owns it. For documents that need signing, check which type of signature the system offers: we explained the differences between simple, advanced and qualified signatures in our guide to the advanced electronic signature.

Standard document management software or documents inside your business software

It pays to settle this before you look at demos. There are two routes.

The first is standard document management software, separate from your business software. It suits documents that have no “owner” in the business software: leases, minutes, procedures, HR documents, correspondence with banks and advisors. It has ready-made approval workflows and can be configured without development; setup time and pricing model (often per user) need to be checked with the vendor. The limit shows when the document is tied to operational data: if the order lives in the business software and the delivery note in the DMS, someone has to link them by hand, or you need an integration between the two programs.

The second is to keep documents inside the business software, attached to the thing they refer to. This is what we did with Dabe Connect for a building services company: at head office every customer, building and machine has its own technical documentation and service history. In the app, technicians look up the installation's documents, fill in the report, attach photos and get the customer to sign on the phone. Customers download their reports from their private area without calling, a topic we covered in more depth in our article on the customer portal. Paper service reports have disappeared and transcription errors have dropped by 95%. In the current phase, the system reads supplier delivery notes uploaded as PDFs or scans and pre-fills the transport document, which a person checks before confirming it.

The problem that started the project was very concrete: paper service reports had to be carried back to the office by hand, some got lost or arrived illegible, and customers had to phone to track down the report of a maintenance visit. The solution was to put the document at the point in the process where it is created and where it is needed.

A practical rule for choosing:

• if the document is created or used within a process your business software already tracks (order, service call, job, shipment), keep it in the business software;
• if the document lives on its own and mainly needs approvals and deadlines, a standard DMS is usually the simplest and cheapest option to get started;
• if you have both situations, the DMS can sit alongside the business software, provided the two talk to each other. It is the same issue as data scattered across systems that don't communicate, applied to files.

If your current business software doesn't let you attach documents to records properly, add that to your list when you assess whether to replace it or have a custom one built. In that case it is also worth reading how data migration to new business software works, because attachments are the part that usually gets forgotten.

Document digitisation: where to start without scanning everything

The most common mistake is to start from the paper archive of the last twenty years. You spend a lot, you scan material nobody will ever look for, and meanwhile new documents keep arriving in the same mess. It is better to start with new flows and leave the backlog until last.

1. List the documents in circulation. For each department, the 10-15 most frequent document types: where they come from, who uses them, what they are tied to (customer, supplier, job, employee), who has to keep them and for how long. A spreadsheet and a morning with the right people are enough.
2. Decide on the classification scheme. Few categories, clear names and a file naming rule (for example date, type, counterparty, number). The rules apply even if you stay on shared folders for now: a good part of the benefit comes from here.
3. Choose where each document type goes: in the business software, in a DMS or in the archiving service, following the rule in the previous section.
4. Digitise incoming flows. E-invoices already arrive in digital form. For paper delivery notes, scan them when goods are received and link the document to the order straight away. For service reports, use an app on the technician's phone.
5. Sort out permissions before uploading. Moving confidential documents into a new tool with permissions still to be defined is the fastest way to show them to people who shouldn't see them.
6. Only at the end, the backlog. Bring into the new system what you really need (active contracts, documentation for installations under maintenance, open files). The rest can stay where it is, read-only, until the retention periods expire.

When you don't need document management software

If fewer than about ten people in the company work on documents, there are few document types and no approval workflows, dedicated software is often an extra cost and one more habit to enforce. In that case three things are enough: shared folders organised with the classification scheme from steps 1 and 2, the free Agenzia delle Entrate service in Italy for archiving e-invoices, and a backup that someone actually checks, with a test restore every now and then.

Likewise, if the documents that waste your time are all tied to orders, service calls or jobs, buying a separate DMS risks adding a program without removing the double work. Before assessing vendors, check whether the problem goes away by attaching documents in the right place in your business software.

Document management software becomes money well spent when there are several departments, confidential documents, approvals that stall on people's desks and someone in the company willing to own the rules. Without that person, even the best DMS soon starts to look like the old shared folder again.

Let's talk

If your company's documents are split between servers, email and phones and you are not sure whether you need a DMS, a module in your business software or just a tidy-up, we can start from the list of documents in circulation and work out together which process each one belongs to. We develop custom business software for SMEs with their own processes, in two-week sprints, and the code stays yours. If the analysis shows that a standard product is enough for you, we will tell you. Book a 30-minute call.