What is the difference between document management software and document workflow automation?
A document management system (DMS) is the repository: it controls where documents are stored, who can access them, how versions are managed and how you find them again. Document workflow automation controls who does what with those documents as they move through your process: arriving, being classified, having data extracted, being routed to the right people, being approved and being passed on to downstream systems. In practice, a workflow platform is often linked to a DMS: once a document has completed its workflow, it is automatically archived in the DMS with the right metadata and version information. The two systems therefore complement each other, but they solve different problems and need to be designed separately.
What exactly is document workflow software and how does it work in practice?
Document workflow software automates a document's path through your organisation. An incoming invoice or contract is picked up by a trigger (mailbox, upload, scan, API), automatically classified by type, and the relevant fields are extracted using OCR or AI. Based on content, amount or project, the document is routed to the right reviewer. It then moves through an approval chain, for example manager, finance and, where needed, legal, which can run in parallel or in sequence. At the end, the document is archived in a DMS with an audit trail, and the next action follows automatically: posting to the accounting system, preparing the payment, registering the contract or closing the case file. Good document workflow software handles all of this without manual steps for the exceptions.
Do you replace Power Automate, Nintex or Kissflow for our flows?
For simple flows with a few hundred documents a month and a handful of rules: no, and we would actively advise against it. Power Automate, Make, Zapier, Kissflow and Process Street work well for such use cases, are quick to set up and cheaper to maintain than a custom platform. Our added value comes into play when one of these limits is crossed: OCR with industry-specific fields, a rules engine with dozens of conditions, a deep two-way integration with your core ERP or CRM, multi-tenancy for your own customer base, or compliance requirements that the standard platforms do not cover, or only partially. In the introductory call, we will tell you openly whether your situation is better served by low-code or by a custom solution.
How reliable is OCR on our documents?
For standard document types such as invoices, packing slips and receipts, modern OCR engines from Azure, Google and AWS are approaching high reliability, especially on printed documents. For specialist documents, such as handwritten notes, technical drawings, policy schedules with tables and exclusions, or medical results, generic OCR falls short. In that case we train a dedicated model on your historical documents, measure extraction accuracy per field, and build a review step for fields below the threshold so that uncertain extractions are always confirmed by a person. To be honest: 100% automation is rarely realistic, nor is it desirable. Your exceptions are exactly where human expertise adds value.
How do you integrate the document workflow platform with our ERP, CRM or case management system?
Integrations are almost always part of a project, as pure document processing with no link to your core systems delivers little. We integrate with SAP via S/4HANA REST, BAPI or OData; AFAS via Profit connectors; Exact and Twinfield via their official APIs; and Salesforce, Dynamics 365 and HubSpot via their cloud APIs. For sector-specific case management systems, such as insurance core systems, municipal case systems or legal practice tools, we build the integration to order, based on the integration options the system offers. We document all integrations so that your IT team can later manage or extend them itself.
What about GDPR, audit trails and compliance?
An audit trail is a standard part of every document workflow platform we build: immutable logging of who viewed, edited, approved or rejected which document, and when. GDPR-compliant data processing is our starting point, with data residency in an EU region, encryption in transit and at rest, and clear retention-period enforcement per document type. For sectors with additional requirements, such as the Wwft (Dutch anti-money laundering act) for accountancy and legal practices, Solvency II and EIOPA for insurers, and GDPR for medical data in healthcare organisations, we build in the specific requirements from the start, not as an afterthought. For larger projects, a DPIA and optionally an external pen test are standard.
What determines the cost of a document workflow automation project?
Mainly four things. First, the breadth of the scope: invoice processing only, or the full range of documents including contracts, HR and case files. Second, the OCR complexity: standard invoice fields are cheaper than industry-specific models that need to be trained on your own data. Third, the number of integrations with external systems, since every ERP, CRM or case management integration is a mini-project in its own right. Fourth, whether we take care of monitoring, model retraining and ongoing development on a structural basis, or whether you handle that in-house. After the scope document, we give you an honest estimate with fixed sprint prices, so there are no surprises.
How long does it take to go live with a first document type?
A well-defined first document type, for example incoming invoices with a few suppliers and one accounting integration, can be in production within a few sprints. A broader platform with multiple document types, a complex rules engine and deeper ERP integration takes a project of several sprints. We always phase the work so that after the first few sprints, one document type is actually running in production. The business can then start phasing out manual work while we continue building the broader scope. Only once the first flow is running stably do we add the next document types.
Who benefits most from document workflow automation?
In practice, most enquiries come from mid-market and larger organisations with more than a hundred documents a day in workflow: accountancy firms with client-file flows, insurers with claims and policy-change flows, HR departments with onboarding and absence management, local and central government with subsidy, objection and permit processes, notaries and law firms with case administration, and real estate organisations with rental and sales administration. For smaller organisations with lower volumes, a standard low-code solution is usually sufficient and more proportionate. We're happy to give you honest advice on which side of that line your situation falls.
Do you work with our in-house IT department or existing supplier?
Almost always. A document workflow project will almost certainly touch existing systems: accounting, ERP, CRM, a legacy DMS, and sometimes a Power Automate layer built earlier that we take parts of over. We work transparently with your IT team and, where needed, your existing suppliers. Clear API contracts, documented integrations and an incident runbook are standard. Code, infrastructure as code and knowledge stay with you, so you never become dependent on a single agency.