Zum Inhalt springen

enaio Workflow: Managing Approvals, Authorisations and Deadlines

The enaio workflow is the workflow control within the enaio document management system. It routes documents and tasks to the responsible roles according to defined rules, takes deputies and deadlines into account, escalates when things fall behind and logs every step.

How to design processes in general is covered on our page on Workflow Management. This page is about the implementation in enaio: modelling, roles, deputies, deadlines, escalation and the workflows that AWP Consult has been implementing as a certified enaio partner since 2006.

Approval workflow in enaioExample view
  1. IncomingInvoice detected in the inbox
    done
  2. Factual reviewby the processing staff
    done
  3. Branch by amount thresholdone leveltwo levels
  4. Approval by department head absent, deputy takes over
    active
  5. Escalationonly when the deadline expires
    ready
  6. Handover to the ERPafter approval
    waiting
Every step logged with person and timestamp
250+
completed projects since 2006
150+
reference customers in the DACH region
12 to 18
months average payback

Key points at a glance

  • The enaio workflow is the workflow control within the enaio document management system. It distributes tasks together with the associated document to roles, applies rules, deputies and deadlines and logs every processing step with person and timestamp.
  • enaio has two types of workflow: the ad hoc workflow, which users pass on spontaneously to colleagues, and the rule-based workflow, which follows a fixed process model with conditions, amount thresholds, deputies and escalations.
  • Multi-level approvals with conditional branches and parallel authorisations are possible, for example an invoice approval with one level below and two levels above a defined amount threshold.
  • Tasks from the workflow can be handled in the enaio client, in the browser via the enaio webclient and on mobile through the app. Approvals are therefore also possible while on the move.
  • For tax-relevant processes, the GoBD require in margin no. 100 controls that are set up, exercised and logged. An approval workflow with enforced segregation of duties and a complete log implements exactly that.
  • AWP Consult usually starts with a single workflow, often invoice approval, tests it in pilot operation and then expands to further processes.

Sounds right for your company? Let us talk about it.

What is the enaio workflow?

The enaio workflow is the control of work processes built into enaio. It passes a document together with a task to the responsible role, records decisions such as approval, rejection or query, monitors deadlines, forwards to deputies in case of absence and records every step in an audit-proof way. The difference from forwarding by email: every case has a status, a responsible person and a log.

This page is deliberately concrete. Methods such as process capture, BPMN modelling or metrics for throughput times are covered on our page on Workflow Management. This page is about what the workflow delivers in enaio, which processes we implement with it and how AWP Consult sets it up in your company.

Document and task in one case Invoice Workflow Purchasing Management Deputy Case log Reviewed Approved Archived
Document on the case

Invoice, contract or application are attached to the workflow. Nobody searches for attachments in inboxes, and the file remains the single storage location.

Roles instead of names

Tasks go to roles such as department head or purchasing. Who stands behind a role is stored centrally and is changed in one place when staff change.

Deadlines and escalation

Steps are given deadlines. When a deadline expires, enaio sends a reminder, forwards to the deputy or escalates to the next level.

Log

Who decided what and when is recorded in the case log and remains traceable together with the document.

Which process should become your first enaio workflow?

In a workflow analysis we capture one of your processes with all its exceptions and show how it would look in enaio.

Which types of workflow are there in enaio: ad hoc or rule-based?

In enaio there are two types of workflow: the ad hoc workflow, in which a person passes a case spontaneously to selected colleagues, for example for comment, and the rule-based workflow, which follows a process modelled in advance with conditions, roles, deadlines, deputies and escalations. Which type fits depends on how often a process occurs and what risk is attached to the decision.

Pass on spontaneously or follow a fixed model Ad hoc workflow Rule-based Participants freely chosen Review Rule Approval fixed path with rules
Characteristic Ad hoc workflow Rule-based workflow
Start Spontaneously from the document when someone needs an opinion or input Automatically through an event, such as the receipt of an invoice, or deliberately by an authorised person
Participants Are chosen in the moment Result from the roles and rules of the model
Process Open, without a fixed model Fixed path with branches, levels and deadlines
Typical use Query, comment, circulation for information Invoice approval, contract authorisation, supplier approval, onboarding
Control Logged, but without enforced rules Rules, segregation of duties and the four-eyes principle are enforced technically

Invoice, contract and master data approvals belong in rule-based workflows, because an internal control system requires traceable and logged controls.

Would you like to see this on your own documents?

Request a live demo +49 6104 94738-13

How does the enaio workflow work in detail?

The enaio workflow works through six building blocks: a process model with steps and conditions, roles instead of fixed names, stored deputy rules, deadlines and follow-up reminders, escalations for tasks left undone and a log that records every decision. Whether a workflow holds up in everyday use is decided by these definitions, not by the number of functions.

Six building blocks of an enaio workflow Roles Deputy Deadlines Escalation Log Conditions Model
Your process as an enaio workflow

Together with your departments we define the model, roles, deputies, deadlines and escalations and set up the workflow in enaio.

Arrange a workflow analysis +49 6104 94738-13
01

Modelling: is there an enaio workflow editor?

Anyone looking for an enaio workflow editor usually wants to know where processes are defined. In enaio, rule-based workflows are based on a process model. It describes steps, sequence, the roles involved, conditions and deadlines. Every new case runs through this model as its own instance with its own status.

In our projects we first draw the process as a BPMN diagram, together with the departments. The diagram is the template for the configuration in enaio and at the same time part of your documentation. AWP Consult then sets up the model and tests it with real cases.

  • StepsActivities performed by people such as reviewing or approving and system steps such as the handover to the ERP system
  • ConditionsBranches based on data from the document, for example amount, cost centre or contract type
  • Parallel pathsAuthorisations that run at the same time, for example through purchasing and quality management
Practical tip

First model the standard case completely and then the three most common exceptions. A model that maps every conceivable special case gets bypassed in everyday use.

02

Roles and segregation of duties

An enaio workflow addresses tasks to roles such as department head, purchasing or cost centre responsibility. Which people fill a role is maintained centrally. If someone changes department, the assignment changes in one place, and all workflows work with the new status.

For approvals with a control function, segregation of duties applies: whoever creates an order or changes a supplier does not approve the same case alone. In the workflow this is a rule, so that it does not depend on the goodwill of individuals.

  • Role functional responsibility, independent of the person
  • Group several authorised people, one of whom completes the step
  • Person only where a personal authority is required, for example at management level
Practical tip

Record every change to roles with a date. This makes it possible to show later who was responsible at the time of an approval.

03

Deputy rules for holiday and illness

Deputy rules ensure that no case comes to a standstill simply because someone is absent. In enaio, deputies are stored. If the responsible person is not there, the task goes to the deputy, and the log shows who actually decided.

In functional terms, a deputy should never be allowed to do more than the person being represented. For approvals with amount thresholds this means: the deputy takes on at most the threshold of the person being represented, and above that the case goes to the next level.

  • Planned absence the stored deputy takes over the tasks from the first day
  • Unplanned absence escalation after the deadline expires is the fallback level
  • Traceable the log records that the decision was made on a deputy basis
Practical tip

Define at least one deputy for every role before the workflow goes live. Missing deputies are the most common cause of cases left undone.

04

Deadlines and follow-up reminders

Deadlines turn a forwarding into a reliable process. In the enaio workflow every step can be given a processing deadline. In addition, follow-up reminders bring a document back into the work area at a fixed point in time, for example before a termination date.

Processing deadlines should suit the business: an invoice with an early payment discount period tolerates shorter deadlines than a supplier approval for which inspection reports first have to be requested.

  • Processing deadline how long a step may take at most, measured from when the task is received
  • Date from the document for example contract end or early payment discount date from the index data
  • Follow-up reminderReminder at a fixed point in time, for contracts for example 90, 60 and 30 days before expiry
Practical tip

Before configuration, define whether deadlines apply in calendar days or working days. Otherwise cases escalate at weekends and on public holidays without reason.

05

Escalation when a task is left undone

If an approving person does not respond, enaio escalates the case automatically after the defined deadline. The escalation rule determines where to: to the deputy, to the manager or to a central point such as accounting.

A chain of three levels has proven effective. It is important that every level appears in the log. That way it is clear later why another person decided.

  • Level 1Reminder to the person handling the task
  • Level 2Notification to the deputy or manager
  • Level 3Redirection of the case to the next level
Practical tip

Test escalations deliberately in pilot operation by leaving tasks undone. Otherwise error scenarios that were never triggered only come to light when it really matters.

06

Log and changes to the workflow

Every step of an enaio workflow is logged with person, timestamp and decision, including rejections and queries. The log remains linked to the document. This allows a tax audit, internal audit and works council to trace how an approval came about.

Workflows are not set in stone. If approval thresholds or responsibilities change, the model is adjusted. AWP Consult supports such changes during ongoing operation and keeps the documentation at the same level.

Practical tip

According to margin no. 101 of the GoBD, it must be checked on a case-related basis whether the system in use corresponds to the documented one. Plan this check for every major change to the workflow.

How does an approval workflow run in enaio?

Using an incoming invoice as an example, an approval workflow in enaio runs in six steps: receipt, automatic data capture, review by the processing staff, a branch by amount threshold, approval in one or two levels and handover for posting to the ERP system, with deputies and escalations stored at every step. The complete process with checking rules and tolerances is covered on our page on the incoming invoice workflow.

Branch by amount threshold Receipt Data capture Review Amount threshold below above One approval Level 1 Level 2 Posting in the ERP
01

Receipt

The invoice arrives by email, as an e-invoice or as a scan. AWP SmartFlow retrieves inboxes, files the document in enaio and starts the workflow.

02

Automatic data capture

enaio classify and the AI module enaio kairos extract the supplier, invoice number, amounts and order reference. The data is available to the workflow as index data for its conditions.

03

Factual review

The processing staff check the goods or services and the data. If something is missing, a query goes out from the case without the invoice leaving the workflow.

04

Branch by amount threshold

A condition evaluates the amount. Below the threshold one approval is enough, above it two levels run. We derive the thresholds from your signature policy.

05

Invoice ap­proval with deputy

The department head approves in the client, in the browser or on mobile. If they are absent, the deputy steps in. If the task is left undone, the case escalates after the deadline expires.

06

Handover to the ERP

The approved invoice goes for posting to SAP, DATEV, Microsoft Dynamics 365 or another connected system. The document and the log remain linked in enaio.

The branch by amount is one of the most common questions: below a threshold one approval, above it two levels. In enaio this is a rule in the workflow that is adjusted when your signature policy changes.

Discuss the approval workflow

Which typical workflows does AWP Consult implement with enaio?

With enaio, AWP Consult mainly implements six workflows: invoice approval, contract authorisation with deadlines, supplier approval in quality management, onboarding and holiday requests, damage reports in fleet and logistics and the automated inbox. Each of these processes comes from projects in industry, services, welfare and logistics, not from a demo.

Six workflows from real projects Workflows in enaio Invoice approval Contract deadlines Supplier approval Onboarding Damage report Inbox Roles Deadlines Deputy Log

Invoice ap­proval

Receipt, data capture, review by the processing staff, approval by the department head and handover for posting to the ERP system. Deputies are stored, and after the deadline expires the case escalates.

Incoming invoice workflow

Contract authorisation and deadlines

New contracts go through authorisation, after which follow-up reminders alert before expiry. The responsible person is notified, and renewal or termination is documented.

Contract management

Supplier ap­proval

Initial review by purchasing, quality inspection, approval by purchasing management and quality management, then creation of the supplier. Every step is fully documented.

Quality management software

Onboarding and holiday

Employment contract, occupational safety briefing, IT access and induction as a fixed sequence, holiday requests approved digitally. No mandatory document is lost when someone joins.

Digital personnel file

Damage report

Damage photographed via the app, damage file created, insurer informed, repair order created and settlement documented. Typical for fleet and logistics.

Fleet management with enaio

Inbox

AWP SmartFlow retrieves email inboxes, files attachments in enaio and starts the appropriate workflow. The processing of every document is logged.

Automated document processing

Do you have a specific question about your case?

Ask a question +49 6104 94738-13

What does an approval work­flow for contracts look like in enaio?

An approval workflow for contracts in enaio guides a new contract through functional, legal and commercial review up to signature and then monitors the term with automatic follow-up reminders 90, 60 and 30 days before expiry, so that renewal or termination is decided in good time and the decision is documented. The contract is kept in the contract file, not in an inbox.

Follow-up reminders before expiry Contract file 90 days 60 days 30 days Process Renew Terminate Decision is documented
90 days before

First follow-up reminder to the responsible person: review the contract, clarify the need, compare terms.

60 days before

Second follow-up reminder. If no decision has been made yet, the workflow can additionally involve the deputy or manager.

30 days before

Final follow-up reminder before expiry. Renewal or termination is documented in the case.

The right reference point is decisive. What matters is not the end of the contract but the last day on which it can still be terminated. With a notice period of three months, a reminder 30 days before the end of the contract comes too late. We therefore calculate the follow-up reminders from the termination date, which follows from the contract data.

The authorisation itself follows the same building blocks as any approval: roles for the department, legal and purchasing, parallel or sequential reviews, deputies and escalation.

We show you how this looks with enaio at your company.

Where do users handle their tasks from the enaio workflow?

Users handle tasks from the enaio workflow where they work: in the enaio client at their workplace, in the browser via the enaio webclient without a local installation and on mobile through the app when an approval is to be granted while on the move. Browser access follows the same permissions as the client, so that nobody sees or decides more through a different access route than intended.

Access route Typical users Suitable for
enaio client Processing staff, accounting, key users Daily work with many cases, review with document view and index data
enaio webclient Branch offices, departments, occasional users Handling tasks in the browser, without a local installation, with the same permissions as in the client
Mobile app Managers and decision-makers who are often on the move Mobile approval of invoices and other documents from a smartphone

You can read more about browser access at enaio webclient.

Prefer to talk it through in person rather than read on?

Request a callback +49 6104 94738-13

How far does workflow automation with enaio go?

Workflow automation with enaio goes as far as decisions can be captured in rules: receipt, data capture, assignment, checking against master data, branches by amount or contract type, deadlines, escalations and the handover to the ERP system run automatically, while factual decisions such as an approval remain with the responsible people. This is intentional: an approval is a control exercised by a responsible person.

For data capture, enaio uses the AI module enaio kairos, which recognises documents without rigid templates and learns from corrections. How far invoice processing in particular can be automated is shown on our page on automated invoice processing. We describe the connection to SAP, DATEV, Microsoft Dynamics 365 and other systems at enaio interfaces.

Rules automatic, decisions with people Automatic Decision by people Receipt Data capture Rules ERP AI Approval Query Rejection
Trigger

A workflow starts as soon as a document arrives, for example via AWP SmartFlow from an email inbox.

Data for rules

Captured index data such as amount, supplier or cost centre control the branches in the model.

System steps

Matching against master data and handover of the posting to the ERP system run without manual intervention.

Human decision

Approvals, rejections and queries remain with the responsible roles and are logged.

Unsure where to start? We help you assess your situation.

Arrange an initial consultation +49 6104 94738-13

How does the enaio workflow document approvals in an audit-proof and GDPR-compliant way?

The enaio workflow documents approvals in an audit-proof way by logging every step with person, timestamp and decision, linking the log to the document in the archive and enforcing segregation of duties as a rule. It becomes GDPR-compliant when every role only sees the cases it needs for its task and logs are only evaluated for the intended purpose.

According to margin no. 100 of the Principles for the proper keeping and retention of books, records and documents in electronic form and for data access (GoBD), controls must be set up, exercised and logged to comply with the regulations of § 146 of the German Fiscal Code (AO). An approval workflow is exactly such a control. The requirements for the archive behind it are covered on our page on the GoBD-compliant DMS, and the principles on access rights and deletion on the page on document management under the GDPR.

Complete log

Who reviewed, approved, rejected or queried, and when, including decisions made on a deputy basis and after escalation.

Segregation of duties

Whoever creates a case does not approve it alone. From defined thresholds the four-eyes principle applies.

Immutability

According to § 146 (4) AO, the original content of a record must not become illegible. The document and the log are stored in an audit-proof way in enaio.

Works council

A workflow that records the decisions and processing times of people is, as a rule, a technical device within the meaning of § 87 (1) no. 6 of the German Works Constitution Act (Betriebsverfassungsgesetz). A works agreement on the evaluation of the logs is customary.

Data minimisation

Every role only sees the cases and documents in its area, in the sense of Art. 5 and Art. 25 of the General Data Protection Regulation (GDPR).

Retention

As accounting documents, approved invoices must generally be retained for eight years under § 147 AO, and the approval log is part of the document.

Sounds right for your company? Let us talk about it.

What customers say about workflows with AWP Consult and enaio

Voices from companies in forwarding, logistics and industry that have digitised their processes with AWP Consult in enaio.

With AWP's incoming invoice workflow, we standardise document processing in a secure and efficient process. Document checking is carried out digitally and in a personalised way, and at the end there is automatic posting in financial accounting.
KISSEL Spedition GmbHFORWARDING
After several meetings and presentations, enaio was exactly the solution we had envisaged for a new DMS and a new incoming invoice workflow. Simple to use, a clear user interface, well-defined processes. All documents can be found again quickly and easily.
Kommanditgesellschaft Bursped Speditions-GmbH & CoFORWARDING
With AWP we were able to successfully modernise and further develop our enaio and continuously adapt it to our business processes and to new challenges. Together we have already achieved a great deal and we very much look forward to continuing to work together.
Noerpel SELOGISTICS
For many years we have enjoyed a successful and trusting collaboration with AWP Consult. enaio supports our processes reliably and contributes significantly to the efficiency of our everyday work.
Klumpp + Müller GmbH & Co. KGINDUSTRY
Logo Kissel SpeditionLogo NoerpelLogo CargoLineLogo Caritas FrankfurtLogo DFBLogo B&B Hotels

Would you like to see this on your own documents?

Request a live demo +49 6104 94738-13

Which mistakes happen when introducing an enaio workflow?

The most common mistakes when introducing an enaio workflow are a target process designed at the desk, deputies that are only set up after go-live, approval thresholds without a signature policy, tasks assigned to names instead of roles, escalations that are never tested and too large a start with many processes at once. All of them can be avoided before go-live.

Target process instead of the process actually lived

Consequence
The workflow maps how the process should be, not how it actually runs. Exceptions migrate back into emails.
Better
Capture the actual process with all its exceptions before configuring.

Deputies only after go-live

Consequence
During the first holiday, cases pile up and acceptance suffers.
Better
Define deputies and escalations for every role right from the start.

Approval thresholds by gut feeling

Consequence
The levels have no basis, and in an audit the evidence is missing.
Better
Derive thresholds from the valid signature policy and have them confirmed by management.

Tasks assigned to names instead of roles

Consequence
Workflows have to be adjusted with every change of staff.
Better
Use roles and assign people centrally.

Escalations never tested

Consequence
Error scenarios only come to light when it really matters.
Better
Deliberately leave tasks undone in pilot operation and check all escalation paths.

Too many workflows at once

Consequence
Training and coordination overwhelm the departments.
Better
Start with one workflow, check its effect in everyday use and then expand.

Do you have a specific question about your case?

Ask a question +49 6104 94738-13

How does AWP Consult introduce an enaio workflow?

AWP Consult introduces an enaio workflow in four phases: process capture with the departments, configuration of steps, roles, permissions and ERP interfaces, pilot operation with training by role and then go-live with expansion to further workflows. Depending on the scope, it usually takes 8 to 16 weeks until go-live. Training does not cover the system in general but exactly the steps your employees will later carry out every day.

Usually 8 to 16 weeks until go-live 0 4 8 12 16 Weeks Process capture Configuration Pilot, training Go-live, expansion
01

Process capture, weeks 1 to 2

Capture approval levels, deputies, deadlines and exceptions together with the departments and agree them as a model.

02

Configuration, weeks 3 to 6

Set up workflow steps, roles, permissions and interfaces to the ERP system in enaio.

03

Pilot and training, weeks 6 to 12

A pilot group works with real cases, feedback is incorporated, and training is carried out by role.

04

Go-live and expansion, weeks 8 to 16

Production start, measurement of throughput times and expansion to further workflows. Support and adjustments continue afterwards as well.

More on this: enaio implementation and enaio training and support and maintenance

We plan the steps together with your team.

Arrange an appointment +49 6104 94738-13

What should you define before your first enaio workflow?

We clarify these points in the process capture. The more of them that are decided in advance, the faster the configuration runs.

Organisation

  • Trigger, process and end of the workflow
  • Roles per step and the people behind them
  • Deputy for every role
  • Key users in the department
  • Involvement of the works council and data protection

Rules

  • Approval thresholds from the signature policy
  • Conditions for branches, such as amount or contract type
  • Processing deadlines per step
  • Escalation chain when a deadline expires
  • Handling of rejection and query

Technology and data

  • Index data that the workflow needs for its rules
  • Origin of the master data, for example from the ERP system
  • Access routes: client, webclient or mobile
  • Archiving of document and log
  • Test cases for pilot operation

We show you how this looks with enaio at your company.

Which terms around the enaio workflow should you know?

The terms that come up again and again in workflow projects between the department, IT and AWP Consult.

01

Workflow instance

A single run of a workflow, such as the approval of a specific invoice, with its own status and its own log.

02

Process model

The template of a rule-based workflow with steps, roles, conditions and deadlines.

03

Ad hoc workflow

A spontaneously started workflow without a fixed model, for example for a comment or a circulation for information.

04

Approval workflow

A workflow that ends in an approval, for example for an invoice, an order or the creation of a supplier.

05

Authorisation work­flow

A workflow for applications and contracts that must be authorised before implementation, such as holiday requests or new contracts.

06

Gateway

A branching point in the model at which a condition determines the further path. In BPMN it is shown as a diamond.

07

Deputy rule

Definition of who takes over a task when the responsible person is absent, with at most that person's authority.

08

Escalation

An automatic reminder or forwarding when a task is not completed after its deadline has expired.

09

Follow-up reminder

A reminder about a document at a defined point in time, for example before a termination date.

10

Subscription

A notification when a document or file changes, without a task being created.

11

Four-eyes principle

A control in which two different people review or approve a case. The workflow prevents one person from carrying out both steps.

Prefer to talk it through in person rather than read on?

Request a callback +49 6104 94738-13

Frequently asked questions about the enaio workflow

What is the enaio workflow?

The enaio workflow is the workflow control within the enaio document management system. It distributes documents and tasks to roles according to rules, takes deputies and deadlines into account and escalates when things fall behind. Every step is logged with person and timestamp. Typical areas of use are invoice approvals, contract authorisations and HR processes.

How does the enaio workflow differ from general Workflow Management?

Workflow Management describes the method, that is, how processes are analysed, designed and continuously improved. The enaio workflow is the concrete implementation in the ECM system, linked to digital files, permissions and the connection to the ERP system. You can find the basics of the method on our page on Workflow Management.

Is there an enaio workflow editor for modelling processes?

In enaio, rule-based workflows are based on a process model with steps, roles, conditions and deadlines. In our projects we first draw the process as a BPMN diagram with the departments. This diagram is the template for the configuration, which AWP Consult carries out in enaio and tests with real cases. We support later adjustments during ongoing operation.

How complex can workflows in enaio become?

enaio supports multi-level workflows with conditional branches, parallel authorisations, escalation rules and deputies. AWP Consult has introduced such workflows in production in industry, welfare and logistics. In practice it is still worth starting lean. A clear standard case with few, well-defined exceptions is better accepted in everyday use.

Can enaio start the right approval workflow depending on the amount?

Yes. Invoice data is captured with enaio classify and the AI module enaio kairos and is available to the workflow as index data. A condition evaluates the amount: below the threshold one approval, above it two levels. The thresholds are rules in the workflow and are adjusted when your signature policy changes.

Which document management system offers automated authorisation workflows for contracts?

enaio maps authorisation workflows for contracts: functional, legal and commercial review, signature and then follow-up reminders, for example 90, 60 and 30 days before expiry. The contract is kept in the contract file, and decisions are logged. It is important to calculate the follow-up reminders from the termination date, not from the end of the contract.

Can workflows be approved on mobile?

Yes. With the enaio mobile app, invoices and other documents can be approved from a smartphone. This helps managers in particular who are often on the move. In the browser, the enaio webclient is also available, with the same permissions as in the client.

What happens if an approving person is absent or does not respond?

In the case of absence, the stored deputy rule takes effect and the task goes to the deputy. If no one responds, enaio escalates the case automatically after the defined deadline expires, for example to the manager. AWP Consult sets up these error scenarios before go-live and tests them in pilot operation.

How do I prove to the works council and IT that every approval step is documented?

The enaio workflow logs every step with person, timestamp and decision, including rejections, queries and decisions made on a deputy basis. The log is archived together with the document. For the works council, a works agreement is customary, because such a system is, as a rule, subject to co-determination under § 87 (1) no. 6 BetrVG. We prepare the description of roles, log and evaluation for this together with you.

Can we change existing workflows later?

Yes. Workflows in enaio can be adjusted, for example when approval thresholds or responsibilities change. AWP Consult supports such adjustments during ongoing operation. Every change should be documented with a date, so that it can be shown which rule applied at the time of an approval.

How long does the introduction of an enaio workflow take?

Depending on the scope, it usually takes 8 to 16 weeks until go-live. The first two weeks are for process capture, followed by configuration, pilot operation and training. We start with a single workflow, often invoice approval, and then expand to further processes.

What does the introduction of an enaio workflow cost?

That depends on the number of workflows, the complexity of the rules, the interfaces to the ERP system, the number of users and the licensing model. Someone already working with enaio starts differently from a company introducing enaio for the first time. You will receive a reliable quote after the workflow analysis via our contact page.

Sketch an approval workflow with your rules

Together with you we derive approval levels, deputies and escalations from your signature policy and show the process in enaio.

  • From your signature policy
  • With deputy and escalation
  • Matching your ERP system

Sources and legal bases

The legal statements and standards on this page are based on these official and established sources. Reviewed as of: October 2026.

Your first enaio workflow, set up properly

In the workflow analysis we capture one of your processes with all its exceptions and show how it looks as an enaio workflow with roles, deputies, deadlines and escalation. You receive a clear recommendation for the start.

  • In person in Dietzenbach or online
  • With your departments
  • Result: a clear first workflow