Skip to content

15 Questions to Ask When Choosing a Workflow and Document Management System

Tolga Eşiz17 min read
Team working together on a laptop at a meeting table

A workflow and document management platform carries an organisation's approvals, documents and tasks for years. That is why the choice should not rest on a product presentation. The products on a shortlist look alike in their demos. The differences appear once you ask questions about your own needs.

You can use the 15 questions in this article as a checklist in evaluation meetings. Under each question you will find why it matters and PaperWork's answer. Ask the same questions to the other platforms on your shortlist and put the answers side by side in the summary table at the end.

If you want to know more about the one-platform approach, how the layers work together and a rollout roadmap, see our article Managing Enterprise Operations on One Platform: A Complete Guide.

Who it is for: Operations and process managers, IT teams, managers of document- and approval-heavy departments such as finance, procurement, legal, quality and HR, and decision makers preparing for a digital transformation project.

Architecture and existing systems

1. Do processes, documents, reports and cases run on the same infrastructure?

Why it matters: When separate products are connected to each other, every new need can turn into a new integration project. Managing users, permissions and document definitions separately in each product also adds workload.

PaperWork's answer: Process automation, document management, business intelligence, process analytics, case management and task management run on the same platform. These components share four common foundations:

  • One data model: A request, its documents, its approval history and the related case are linked to the same record.
  • One permission model: Users, roles and the organisation chart are defined once; every module works with the same rules.
  • One task list: Employees see all their work on a single screen, whichever process it comes from.
  • One AI layer: Document reading, classification and assistant capabilities are used in processes through shared services.

2. Can it work without replacing the ERP? Which systems does it connect to?

Why it matters: The number of systems that must be replaced determines the duration and risk of the project.

PaperWork's answer: PaperWork does not replace the ERP; it works alongside it. Financial records and master data stay in the ERP. PaperWork manages the work around the ERP, such as approvals, documents and tasks, and passes the results back to the ERP.

  • SAP: SAP functions (BAPIs and custom functions) can be called from processes and forms through a ready-made connector, without writing code. There is also a document archive solution that runs inside SAP screens (PWSAPECM).
  • Local and other ERPs: A no-code connection (Connector) can be set up with local ERPs such as Logo. Customer projects include installations integrated with Logo Tiger, Canias, Netsis, IFS, abas and DIA.
  • Databases: Operations can be run directly on SQL, Oracle, DB2 and HANA databases.
  • Web services: SOAP and REST services of external systems are defined, tested and used in a process step with field mapping.
  • RPA: For legacy applications without an interface, software robots are triggered from the process.

3. Does it run in the cloud or on our own servers? How do we migrate from our current system?

Why it matters: In regulated sectors such as banking, insurance, the public sector and healthcare, where data is stored can decide the purchase.

PaperWork's answer: PaperWork can be installed in the cloud or on the organisation's own servers (on-premises). With an on-premises installation, data stays in the organisation's infrastructure. Processes, forms and reports prepared in the development environment can be moved to production as a single package. For organisations moving from another workflow application, there is a migration solution for existing flows and archives. Document archives can be moved by automatic transfer through a metadata table or by bulk upload via API.

PaperWork supports MS SQL Server 2017 Standard and later. If more than one million documents will be stored or more than 2,000 new flows will be started per day, MS SQL Server 2019 Enterprise is recommended.

Development and flexibility

4. Can a business unit build processes without writing code?

Why it matters: On a platform where every change depends on the software team, requests pile up and the project slows down.

PaperWork's answer: The business analyst defines the data structure and the form is generated from it automatically. The process is drawn in a BPMN 2.0 compliant editor with drag and drop and then published. A simple approval process can be designed within hours. Form behaviours such as showing, hiding, making fields mandatory and calculating are also defined without code, through a wizard.

Process steps can include human approval, conditional branching, parallel branches, sub-flows, waits, and email and SMS notifications. Generating a PDF from a document, calling a web service and running an ERP function can also be added to these steps. Forms come with ready-made components such as Turkish ID number (TCKN), IBAN, barcode and QR code reader, photo, location and in-form Word document editing. Forms can be prepared in more than one language.

5. Can our software team extend the platform when needed?

Why it matters: The limits of no-code tools show up in complex needs. At that point the software team must be able to extend the platform.

PaperWork's answer: Yes, at three levels:

  • No-code: The business analyst designs forms and processes with wizards and the help of PWAI Assistant.
  • Low-code: When needed, small pieces of code can be used: JavaScript in forms, C# in processes.
  • Full development (SDK): The platform's business logic is accessible through SOAP and REST web services and .NET and REST libraries. The platform's own screens also run on this layer. The organisation's software team can upload documents, start flows, complete tasks and run searches from its own applications.

6. Can approval limits and business rules be updated without changing the process?

Why it matters: Rules change far more often than processes. If a rule is embedded in the process, every limit change means new development.

PaperWork's answer: Rules such as approval limits, authorisation matrices and discount rates are kept in Excel-like decision tables in a central rules engine. When an approval limit changes, updating the relevant table is enough; the process design stays untouched.

Documents, compliance and security

7. Are regulatory requirements in Turkey met?

Why it matters: When designing document processes in Turkey, the needs for e-invoicing, e-signature, registered electronic mail (KEP) and personal data protection must be handled together. How these components are provided should be made clear during the evaluation.

PaperWork's answer:

  • The e-invoice XML is stored together with its image, and integrator connections are set up.
  • Electronic signatures compliant with Law No. 5070 and batch signing are supported.
  • KEP messages with the status of legal evidence can be sent.
  • Personal data such as Turkish ID numbers, IBANs and phone numbers are found automatically with AI and shown masked to users without permission (ISDD). This feature is used in data protection work under KVKK and GDPR.
  • PaperWork holds a domestic production certificate.
  • PaperWork holds ISO 9001 and ISO 27001 certificates.

8. How deep is the document management?

Why it matters: Storing documents on a file server is not the same as managing them by type, permission and the process they belong to. Document management also shows which work a document belongs to, who can access it and which version is current.

PaperWork's answer:

  • Each document type has its own metadata fields, and documents are searched by these fields.
  • Smart files carry ready folder templates for an employee, a customer or a project.
  • Dynamic folders form automatically from document metadata. For example, e-invoices can be grouped by year, month and day.
  • Missing or expired documents are flagged and reported.
  • Versioning, full-text search and OCR search on scanned documents are available.
  • Comments can be added to documents.
  • Tasks with a due date can be assigned from a document.
  • Documents can be summarised with AI, and AI can answer questions about a document's content.
  • Built-in Word- and Excel-like editors are available.
  • Versions of Word documents can be compared with AI.
  • Who viewed, downloaded or deleted a document is logged.
  • Documents are kept in one central store (Content Server) and can be accessed from the screens of applications such as ERP, CRM and HR. The same document does not need to be stored separately in each system.
  • Documents can be signed with electronic or mobile signature from within PaperWork.
  • With TurkKep and TNBkep integrations, KEP messages can be received and sent from within PaperWork. Incoming and outgoing messages can be archived in document management.

9. How are identity and access secured?

Why it matters: An enterprise platform must fit the organisation's existing identity infrastructure and keep a trail of every action.

PaperWork's answer: Users are synchronised with Active Directory. Single sign-on (SSO) and multi-factor authentication are supported. Documents, reports and processes are managed with the same permission model. Viewing, editing, sharing, version changes and deletions are logged, so the action history is available during audits.

Measurement and operations

10. Can process performance be measured inside the platform?

Why it matters: To improve a process you first need to see where and why it slows down. If measurement data has to be moved to another system, getting up-to-date results becomes harder.

PaperWork's answer: Yes, in two layers:

  • Business intelligence and reporting: Part of the platform's standard features. Form, approval and document data are kept in the same database, so no separate data transfer is needed. Dashboards, scheduled reports and ready-made system reports for flow statistics, target times, delegations and permissions are available.
  • Process analytics: Tracks more than 100 metrics. It identifies bottlenecks, requests that exceed target times, workload imbalances, SLA deviations and steps that are frequently sent back. It analyses this data with AI to produce a report, defines improvement actions and assigns them as tasks.

Each step gets a target time and a tolerance. For example, a 10-minute target with a 20 percent tolerance means up to 8 minutes is early, up to 12 minutes is on time, and anything after that is late. Times are calculated according to the organisation's working calendar and holidays.

11. How is work that cannot be defined in advance managed?

Why it matters: For work such as a customer complaint, a claim file, an audit finding or a legal dispute, the path is not clear from the start. New tasks and decisions emerge as the work progresses. Forcing them into a rigid workflow makes the process harder.

PaperWork's answer: In case management, the documents, notes, correspondence and decisions belonging to the work are gathered in one file. Tasks can be opened from within the case, an owner and due date can be assigned, and a defined approval process can be started when needed. Requests coming from email, a portal or a call centre can be turned into cases automatically. SLA times are tracked; when a deadline is missed, a notification goes to the responsible managers. Tasks from processes and cases are followed in the same task list.

12. Where can users give approvals?

Why it matters: The person who approves is not always at a desk. If they cannot reach the task while in the field or in a meeting, the following steps wait too.

PaperWork's answer: Tasks can be approved via the web, email, the mobile app (Android and iOS) and the Outlook add-in. Through Teams and WhatsApp Business, users can query tasks, start workflows and give approvals with PWAI Assistant. External stakeholders such as suppliers or business partners can complete their own steps through a portal. The work of users on leave is passed to their delegates.

AI and growth

13. Is the AI connected to processes, and does it follow the permission model?

Why it matters: It may not be enough for AI to answer questions. You also need to see how its output feeds into a process, a task or a decision. It also matters that the assistant respects the user's access rights.

PaperWork's answer: AI works inside the platform according to the user's permissions. The assistant does not generate answers from documents the user is not authorised to access. PaperWork's AI investments began in 2021, when it brought an AI company into the group.

  • Intelivus (intelligent document processing): Reads, classifies and extracts key fields from documents such as invoices, delivery notes, contracts and IDs, and starts the related process. It learns new documents by itself. Documents are saved to document management without manual handling, and the extracted data can be passed to the required systems.
  • PWAI Assistant: Produces summaries and risk suggestions from document and process content. It can start a flow or create a task on the user's behalf. By reviewing process analytics data, it assesses bottlenecks, risks, the overall state of the process and key performance indicators (KPIs). It prepares a detailed analysis report and starts actions to fix problem areas.
  • Query Insight: Lets users ask questions in natural language about corporate information and documents, and answers with sources.
  • ISDD: Finds personal and sensitive data and masks it according to permissions.
  • Design with AI: The business unit describes its need in a sentence; form fields, roles and a draft flow are generated automatically.

14. Can new ready-made solutions be added to the same infrastructure?

Why it matters: Business units sometimes want a ready-made solution that fits their work and can go live quickly. That solution needs to work with the existing infrastructure and be adaptable to the organisation's rules.

PaperWork's answer: Ready-made solutions built on the same infrastructure can go live on their own or together. When a new solution is added, existing users, roles, integrations, document classes, rules and AI services are reused. Solutions can be adapted to the way the organisation works with low-code development tools. Expert AI agents for the platform solutions (97 agents in total) are ready to use; the agents make suggestions, while approval and decisions stay with the user.

Solution Scope
PWCLM Contract lifecycle and AI-based clause and risk analysis
PWSLM Supplier application, qualification, evaluation, performance and supplier portal
PWQMS Nonconformity, corrective and preventive action, audit and action tracking
PWGRC Risk inventory, controls, audit plans and findings
PWSpend Expense claims, travel requests, advances and settlement
PWCLAIMS The claim process from opening the file to payment
PWITSM IT requests, incident and service processes, asset inventory
PWPROC Purchase requests, budget control, approval and supplier management
PWCSM Central, measurable management of customer requests and complaints
PWHR Employee processes from hiring to exit, Employee 360
PWXPA Enterprise planning: budget, actuals and operational risk
PWSAPECM Document access and archiving without leaving SAP screens

In addition, dozens of ready-made process templates are available for HR, finance, quality, occupational health and safety, procurement and sales. Purchasing, invoice approval, leave requests, advances, near-miss reporting, incoming and outgoing correspondence and quote approval are some of these templates. Organisations can use them as a starting point when designing their own processes.

15. Is it live in our sector at a similar scale? What is the licence and support model?

Why it matters: Seeing a working implementation at a similar organisation makes it easier to judge whether the product fits your needs. When choosing a long-term platform, the vendor's experience, licence terms and support structure should also be considered.

PaperWork's answer: PaperWork has been developed in Istanbul by GG Soft Yazılım Hizmetleri A.Ş. since 1998. It is used by more than 200 enterprise customers in 19 sectors, including manufacturing, energy, financial services, insurance, services, food and retail, and healthcare and pharmaceuticals. Some examples:

  • Aksa Enerji manages its processes and documents in its gas and electricity distribution operations at 150 locations across Türkiye, with about 4,000 users, on PaperWork integrated with SAP.
  • Hepiyi Sigorta manages its processes and documents on PaperWork with tens of thousands of users across its 7,000 agencies. The setup is integrated with CRM, the SFS insurance package, TNB KEP, Logo Tiger, a cargo application and the company's own applications.
  • Mazsan Makine manages, measures and monitors complex processes such as pricing and shift planning on PaperWork integrated with Canias ERP.

All products are offered on an annual licence rental model. Solution partners provide project-specific customisation services, and the PaperWork team provides customer support. Baykuş Akademi supports organisations in adapting their processes with their own teams through business analysis and process management training.

Summary table: PaperWork's answers

Add a column to this table for each platform on your shortlist and ask the same questions.

# Question PaperWork
1 Do processes, documents, reports and cases share the same infrastructure? Yes; shared data, permission model, task list and AI layer
2 Does it work without replacing the ERP? Yes; integration with SAP (BAPI), Logo, Netsis, IFS and other ERPs; SOAP/REST and RPA support
3 Cloud and on-premises installation Cloud and on-premises; package transfer between environments and options to migrate existing archives
4 No-code process design No-code design with PWAI Assistant, a BPMN 2.0 compliant process editor and a form wizard
5 Extension for the software team Low-code development (JavaScript, C#) and SDK; access via .NET, SOAP and REST
6 Are rules independent of processes? Yes, a rules engine with decision tables
7 e-Invoice, e-signature, KEP, KVKK e-Invoice, e-signature, KEP and personal data masking; domestic production certificate; ISO 9001 and ISO 27001
8 Document management Document types, versioning, OCR and full-text search, AI summarising and comparison, audit logs and central archive
9 Identity and access Active Directory, SSO and multi-factor authentication
10 Performance measurement Business intelligence, process analytics, AI analysis, target time and tolerance tracking
11 Case management SLA tracking; opening tasks and starting processes from a case
12 Approval channels Web, email, mobile app, Outlook, Teams, WhatsApp Business and external stakeholder portal
13 AI Embedded and permission-bound: Intelivus, PWAI Assistant, Query Insight, ISDD
14 Growth with ready-made solutions Ready-made solutions on the same infrastructure, 97 expert AI agents and dozens of process templates
15 References, licence and support Local platform developed since 1998; 200+ enterprise customers in 19 sectors; annual licence rental, customisation by solution partners, support from the PaperWork team and Baykuş Akademi training

How to run the evaluation

  1. Send these 15 questions in writing to every vendor on your shortlist.
  2. Put the answers side by side in the summary table. Ask for a live demonstration of every feature claimed to be supported.
  3. Choose one of your own processes, such as invoice approval or a purchase request, and ask every vendor to show the same scenario.
  4. Talk to at least one reference in your own sector.

If you would like to see PaperWork in your own process with these questions, you can request a demo.

Would you like to see PaperWork in your organization?

Request a Demo
Contact Us

Let’s Make Your Processes Smarter Together!

Let’s explore how PaperWork’s low-code BPM, document management, ERP integration and AI solutions can be used in your organization.

What happens next?
  1. 01

    We find a time that suits you.

  2. 02

    We hold an introductory meeting.

  3. 03

    We run a demo tailored to you.

Request a Free Demo