A classic scene in a Polish SME: a vendor invoice lands on the receptionist's desk, travels to the department head for a signature, then to the board for approval, and finally to accounting. Three weeks later someone finds it on a windowsill, after the CEO's holiday. The payment deadline is long gone, and the supplier has frozen deliveries. A document management system (DMS) is sold as the cure — and sometimes it really is one, and sometimes it's just an expensive PDF in the cloud.
The difference isn't in the tool. It's in whether someone, before the rollout, wrote down what is supposed to happen inside the workflow. Because a DMS without a defined process is a binder with a blue glow. It doesn't shorten approvals — it just moves the delay from the windowsill to a "to do" tab in a browser.
This post shows when a DMS in an SME actually pays back, how to pick the starting scope, and what not to do in the first month.
What DMS means in a 20-50 person company
At large corporations, "DMS" means a platform for hundreds of thousands of złoty with electronic signatures, statutory archiving and clever OCR. In an SME you need something much simpler: a tool that routes a document to the right person, reminds people about overdue approvals, and after closing puts the file in one, known place. Nothing more.
In practice that means three elements:
- Registration — the document enters the system (from email, a scanner, a supplier portal) and gets a unique number.
- Routing — a rule states who has to approve it, in what order, with what amount threshold.
- Archiving — after closing, the workflow stays in the system together with the click history, comments and the scan. An auditable trail is created.
That's all. If the offer goes beyond these three functions, ask how many of the extras you will actually use in the first six months.
Which documents to put in the workflow first
The biggest mistake we see: a company starts with "all documents at once". Contracts, invoices, leave requests, purchase orders, travel expenses. Three months later, everyone is exhausted and the process rolls back to emails with subject lines like "APPROVAL REQUEST — URGENT".
The winning sequence is the opposite. You start with one document type that meets three conditions: it occurs often (a dozen or more a week), has clear approval rules, and hurts your wallet in a concrete way. The usual candidates are:
- Vendor invoices — because the payment deadline is real money and potential late-payment interest.
- Internal purchase orders (PO) — because this is where you control the budget before the spend happens.
- Leave requests — because they are simple, have clear rules and the team quickly sees the value.
Customer contracts, strategic decisions and anything with a non-standard approval path stay for later. Not because they aren't worth it — but because first you have to teach the team that the system works at all.
A concrete example from a project
At one of our clients — a 34-person manufacturer of steel structures in Wielkopolska — the vendor-invoice workflow took on average 11 working days. An invoice landed at reception, was scanned, went by email to the department head, then to the vice-president (if he was in the office), and finally to accounting. Every month a dozen or so invoices went past the payment deadline; two of them a year damaged supplier relationships badly enough to threaten stopping production.
We deployed a simple DMS integrated with Comarch Optima. The rules were three: an invoice up to PLN 5,000 net — approved by the department head; PLN 5,000-30,000 — head plus vice-president; above PLN 30,000 — also the president. Every approval had 48 hours, after which the system automatically escalated to a deputy. Once approved, the invoice moved into Optima as posted, with the scan attached.
After two months the average workflow time dropped from 11 days to 2.5 days. The number of overdue invoices went from ~15 a month down to 1-2. The bookkeeper got back about 6 hours per week that used to go into "where is that invoice" phone calls. The rollout cost about PLN 18,000 one-off plus PLN 350 per month for licences. It paid back in four months, counting only saved interest and the bookkeeper's time.
Note the point: it wasn't the DMS that did the work. It was the "48 hours and escalation" rule. The DMS was just the tool that enforced the rule. Without the rule — no difference.
How to pick a tool without sinking the project
The DMS market in Poland is surprisingly dense. From giants like M-Files, through local solutions (Amodit, WEBCON BPS in an SMB edition, edokumenty), to Power Automate + SharePoint inside the Microsoft 365 you probably already have. There is no single right answer, but there are three traps worth avoiding:
- "Free in our bundle" without counting per-approver licences. In Microsoft 365 a Power Automate + Approvals workflow needs a Premium licence for the flow author and for every external approver. Check this before you calculate TCO.
- ERP integration "for later". If an approved invoice is supposed to land automatically in Comarch Optima or enova365, it must be wired up on day one. "For now we'll copy it by hand" means nobody will copy it. Three months later accounting is back in Excel.
- OCR as a magic pill. OCR on invoices works really well today, but that doesn't mean it will recognise your vendor with a stamp in the corner and a handwritten note. Plan the first three months as model training — not production.
Practical test: ask the vendor for a demo on five of your real invoices from the last month. If the demo works "because those are our sample data", walk away.
When a DMS won't pay back
Not every company needs a DMS. If 30 documents flow through you each month and there are two approvers sitting in the same room — a DMS is overkill. A shared SharePoint folder, a "don't touch the file without a note in the column" rule and some discipline are enough.
A DMS starts to make sense from the moment when:
- More than 100 documents a month go through approvals.
- Three or more approvers sit in different locations or hybrid mode.
- You regularly lose money on overdue invoices, missed early-payment discounts or contract penalties for late orders.
- Audits (GDPR, ISO, NIS2 questionnaires from clients) start asking who approved what and when.
Below this threshold, simpler solutions — Teams with a clear tagging rule, Excel with version lock, a shared mailbox — give you 80% of the effect for 5% of the price.
What to do before talking to a vendor
Before anyone shows up with an offer, write down on one page:
- Which documents go into the first workflow (one type, not five).
- Who approves and at what amount threshold.
- Which system the document lands in after approval (ERP? DMS as archive? Both?).
- How many pieces a month — from the last three months, from real data.
- What the current average time of the workflow is — even roughly.
Without these five answers every offer will be "flexible" and "scalable", which in practice means "expensive and long". With these five answers a vendor call takes 30 minutes and ends with something concrete.
If you want someone to walk through that page with you and help judge whether a DMS pays back in three months or three years in your company — the first call is free and takes half an hour.
A DMS doesn't shorten approvals. The "48 hours and escalation" rule does. The DMS is just the tool that enforces the rule.