New Workflow Approval

Implement and manage workflow approval for Purchase Invoice and Purchase Order Approval.

Written By Grainne Reidy (Super Administrator)

Updated at August 13th, 2026

Caution for users of the legacy workflow

Once you activate a new workflow, the legacy workflow approval will become unavailable. THIS IS IRREVERSIBLE. While you are preparing for the transition, new workflows can be created as drafts but DO NOT ACTIVATE them until you are ready to stop using the legacy workflow.

 

Overview

About Workflow Approval

AccountsIQ's new workflow approval engine streamlines financial processes by automating approval workflows. Approvals can be managed for key transactions, such as purchase orders, invoices, and credit notes, both through the web platform and a mobile app. 

The system is highly customizable, enabling organizations to set up workflows with pre-defined rules and hierarchies, ensuring compliance with governance policies, requirements, and budget constraints. Additionally, the platform offers efficiency when tracking approval status making the workflows more efficient and easier to monitor.

Setup Overview

Workflows are configured under Approval Settings and managed under Workflow Listing. Approvers are managed under Approvers Listing:

Workflow Overview

The moment a Purchase Order, PO Invoice, or Non-PO invoice is created, it is picked up by the applicable workflow setup and routed to the assigned approvers across different hierarchy levels for their approval or rejection based initially on net values.

The system’s approval workflow offers flexible configuration options to suit your organization’s requirements. Create as many workflows as needed to suit your approval processes. The new WFA will not impact the AP Inbox and can be used with third-party systems such as OCR and Project Management systems.

In our workflows, you can:

  1. Define what documents to process 
  2. Set an automatic approval threshold (net value)
  3. Set up re-submission rules (net, gross, or percentage)
  4. Single or multi-level approval hierarchy

Info: Price Plans

If you are on the Core price plan, you can only create one level of approval. If you would like to upgrade, please contact support. 

 
  1. Set up Approval Rules 
  2. Single or Multi-user approval 
  3. Define decision modes including Manual approval selection option  

See:

New Workflow Approval Overview (18.0N)

Configuring Workflow Approval Settings (18.1N)

Create and Manage Approvers (18.2N

Create and Manage Workflows (18.3N)

Processing Documents with Approval Workflow (18.4N)

 
 

Designing your automated approval process 

Info: Multi-Entity Groups

WFA can only be set up and managed on an entity-basis. If you have multiple entities in your group, the WFA setup process must be followed in all relevant entities.

 

The new approval engine is a powerful and flexible tool. Before getting started with the setup, decide as a company how you want the approval process to work, and build from that plan.

When designing your approval processes, take into consideration:

  1. What type of purchases do you currently have? Are they specific to departments, locations or projects?
  2. Who needs to sign off on specific types of purchases (e.g. capital assets, legal invoices, etc.) or approve certain expenses?
  3. Do you have a minimum threshold for approvals?
  4. Will single step approval be sufficient in all cases? Or will some purchases require multi-step approvals?
  5. Do you maintain budgets in the system, and do you want budget holders to receive information on the budget spend? 

When it comes to setting up your workflows also think about the composition of your orders and/or invoices.  For example:   

Invoice    Workflow   
A single department/location/project invoice                                                                                                                  Create a workflow for a single department/location/or project                                                                                                                
Multi department/location/project invoice                                                                                                                  Create a workflow for the same multi- departments/locations/projects                                                                                                                  
Capital Expenditure multi-department related invoices                                                                                                                  Create a CAPEX multi department workflow using GL code rules                                                                                                                  
Employee Expense Invoices                                                                                                                  Create a designated employee expense workflow using Non PO Invoice process                                                                                                                 

Remember: Every document type = one workflow

Always ensure there is correlation between the documents that require approval and your workflows. Refer to Workflow Scenarios for more examples.

 
 

Pre-Requisites

User Types

All Approvers must be set up as system users, including those who are business user type.    

All current non-system approvers using the legacy workflow approval will automatically be converted to system users.  This conversion will be triggered as soon as the Approval Settings is saved. 

User Permissions

To use the features referred to in this article, in the Maintain Menu Profiles screen, assign the following permission to the relevant profiles:

In the Menus tab:

  • Approval Settings
  • Approvers Listing
  • Add/Edit Approvers
  • Workflows Listing
  • Add/Edit Workflows

In the Reports tab:

  • Purchase Order Reprint
  • Purchase (Product) Invoice Reprint

These insure that users will be able to access approval emails.

For more on user profiles, see Setting Up System Users.

 
 

Configuring Approval Settings

For a video tutorial of this process, watch Configuring Workflow Approval Settings (18.1N).

  1. Navigate to Setup > Approval Settings.
  2. Enable approval for the required approval modes.  If you selected both Purchase Order and Purchase Invoice approval, enable Require exact matching if needed. Refer to ‘Approval Modes’ below for more information. 
  3. Decide if you want to Re-approve PO Documents from integrated products or Re-approve PO Documents from integrated products. This means that documents that may already have been approved in a third-party system will still enter an approval workflow. Note, this does not apply to AP Inbox or Employee Expenses invoices.
  4. Enter the Workflow Approval Administrator’s email address to notify them of any pending actions on documents needing their attention. 
  5. Click Save.

Approval Modes

The approval modes you select impact how your documents progress through workflows. Note that using Purchase Order and Purchase Invoice together (see option 4 below) has a different impact using either individually.

For full details on setting up workflows, see the section ‘Creating Workflows’.

1. Purchase Orders approval (without Purchase Invoice approval)

  • Once a PO is approved, you can create and post the matching invoice immediately. 
  • Editing the invoice does NOT affect PO approval. 
  • Auto-approval and tolerance rules in the PO workflow apply only to the PO and do not affect the invoice. 

Key Concept: Workflow Tolerance

Documents are initially approved or rejected based on net value

Any edits to documents will need to go through reapproval unless you set editing tolerance values. This value can be based on net, gross, or percentage.

  • PO workflows: Tolerance values can also be applied to the associated PO Invoice by enabling ‘Auto-approve invoice with re-approval tolerance’. 
  • PO Invoice, Non PO Invoice, Credit Note workflows: The tolerance value can only impact that document type.
 

2.Purchase Invoice approval (without PO approval)

  • Used for invoices without a Purchase Order (Non PO Invoices), including Employee expenses.

3. Purchase Credit Note approval

  • Configured like Non PO invoices.

4.Purchase Orders + Purchase Invoices (PO & PI together)

What workflows can you create?

  • Non PO Invoices (no order) 
  • Purchase Orders 
  • PO Invoices (invoices linked to approved POs) 

Do PO Invoices always enter their own workflow?

Not always, this depends on PO Invoice value and settings.

  • Matching or lower value and/or quantity than the PO: The PO Invoice will be Auto-approved, with no separate workflow needed.
  • Higher quantity than the PO: This is not a permitted action. Instead, update the PO and reapprove it first.
  • Higher value than the PO: What happens depends on two settings:
    • Approval Settings: Require Exact Matching (ON/OFF) 
    • Purchase Order Workflow settings: Tolerance + Auto-approve setting 
Setting Outcome

Exact Matching = ON

Auto-approve ON

  • Within tolerance → auto-approved
  • Above tolerance → update PO + reapprove

Exact Matching = OFF

Auto-approve ON

  • Within tolerance → auto-approved
  • Above tolerance → enters invoice workflow

Exact Matching = ON

Auto-approve OFF 

  • Invoice ≤ PO value → auto-approved
  • Tolerance does NOT apply
  • Above PO value → update PO + reapprove

Exact Matching = OFF

Auto-approve OFF 

  • All invoices go through invoice workflow
  • Tolerance does NOT apply
 
 

Creating & Managing Approvers

Creating Approvers

For a video tutorial of this process, watch Create and Manage Approvers (18.2N).

  1. Navigate to Setup > Approvers and click New Approver. 
  1. Select an Approver (approvers must be set up as system users first to appear on the list).
  2. Tick the checkbox if the approver is a budget holder. Approvers flagged as Budget Holders will receive a different approval email template containing details of the budget line. If using this option, ensure that workflows are set up based on Dimension Tags and / or Dimension Codes, and that the Codes and / or Tags selected are linked to a Dimension labelled as ‘Budgetary’. See Workflow Scenarios and Using Dimensions  for further details.
  3. Assign a substitute approver if needed. Substitute approvers approve documents in place of the primary approver during specific dates, such as for annual or sick leave. If the substitute approver does not approve the document within the designated dates, it will need to be re-sent to the original approver for approval. Substitute approvers must be set up as approvers first to appear in the list. Note that if an approver regularly approves documents on behalf of someone else, they should be set up as part of the workflow. 
  4. Enable Send approval requests by Email/Mobile if the approver should be notified via email, and/ or via the Mobile app.
  5. If applicable, activate if approver can approve their own documents. (There will be a drop down to select a designated approver if the primary approver can approve their own documents.) 
  6. Save.     

Restricted Approver View

If an approver approves directly in the system rather than via email, there is a restricted view option. In the Edit Group User screen, check User can only view Purchase Orders/Invoices sent to them for approval. This means that only documents sent for their approval will be visible to that approver. If they are a Business User, they will only see POs awaiting their approval and if they are a Finance User, they will only see POs and PIs.

Managing Approvers

Manage approvers in the Approvers listing grid. Go to Setup > Approvers

Refine your search using filters and search fields and export details as an Excel report.

The Actions dropdown lets you manage approvers as follows: 

  • Edit: All approver details can be edited except their name and email. 
  • Deactivate: Approvers cannot be deleted if any of their associated workflows have been used. Instead, they can be deactivated. To re-activate users, click on this button again.
  • Show associated workflows: This will take you to the Workflow screen, showing just the workflows associated with the selected approver. 

Deactivating Approvers

If you are switching approvers for a workflow:

  1. Create the new approver as outlined in this section.
  2. Swap the old approver for the new in the relevant workflows.
  3. In the group layer, unassign the old approver from any entities and then deactivate that user. See Setting Up System Users.

If you have any concerns regarding correct billing, contact support@accountsiq.com to make them aware of the change.

 
 
 

Creating Workflows

Creating Approval Workflows

Workflows are created based on the types of documents your organisation approves, as well as factors such as whether the workflow involves single or multiple departments, requires one or several approvers, involves different hierarchy levels, and any specific conditions or rules tied to the approval of Purchase Orders and/or Invoices.

  • Before you begin, refer to section 2, “Designing your automated approval process,” for guidance on creating workflows.
  • For a video walkthrough of this process, watch Create and Manage Workflows (18.3N).

Step 1: Enable the Relevant Approval Setting

Before creating a workflow, make sure the corresponding approval process is enabled in Setup > Approval Settings

Document Type Process
Purchase Orders If your organization only approves Purchase Orders (not Invoices), only enable Purchase Orders.
Non-PO Invoices If your organization only approves Purchase Invoices that are not linked to a PO, only enable Purchase Invoice. Also enable this if employee expenses require approval.
PO Invoices

Enable both Purchase Order and PO Invoice approval workflow. This process is used when PO Invoices need an extra approval level beyond the PO approval itself. 

 

The “Require exact matching” option will only appear in Approval Settings for PO Invoices.

  • If enabled, it prevents a PO Invoice from being created if its value differs from the original approved Purchase Order. Instead, the PO must be updated, and re-approved, before the PO Invoice be created. 
  • If disabled, the PO Invoice can be created at a different value which can be controlled within the workflow using the ‘Reapproval Rules for Edits’ tolerance settings.
Credit Notes Enable the Purchase Credit Notes approval setting.

PO Invoice Process: One Workflow or Two?

This decision is unique to the PO Invoice process. You have two options:

  • One workflow: Create a workflow for your POs with rules to auto-approve PO Invoices based on a given tolerance.
  • Two workflows: Create a PO workflow, plus an additional, separate PO Invoice workflow for extra approval control. Decide whether all PO Invoices should enter a PO workflow regardless of whether they match the PO, or whether to apply a given tolerance value.
 

Step 2: Create the Workflow

  1. Navigate to Workflows.
  2. Click New Workflow.
  3. Complete the following fields:
    • Workflow: Enter a unique workflow name.
    • Process: Select the type of document the workflow will handle. Only those processes enabled in Workflow Settings will be available for selection.
    • Auto-approval: Enable this option if your organization automatically approves documents up to a specified value and enter that value here.
    • Re-approval rules for edits: If a document is changed after approval, set a tolerance value to define how much it can be edited without needing to go through approval again. Tolerance can be set as a net amount, gross amount, or percentage.
    • Auto-approve invoice within Re-approval tolerance (Purchase Orders process only): Enable this if you want the linked PO Invoice to be auto-approved when it's equal to or below the tolerance set in Re-approval rules for edits. If this is left disabled, the re-approval rules apply to the Purchase Order only, and the linked invoice will go through a separate PO Invoice workflow instead.

Step 3: Set Up Approval Steps

Approval Steps let you create multiple levels of approval and let you add multiple approvers at each level. 

Setup example

Scenario 1: Non-exclusive approval limits

  • Level 1: Biology and Chemistry Department Managers approve documents under £1K
  • Level 2: Finance Manager approves documents between £500 and £10K
  • Level 3: CFO approves documents over £5K

In this scenario, set up both department managers in Step 1, the Finance Manager in Step 2, and the CFO in Step 3.

Scenario 2: Exclusive approval limits

Alternatively, if your approvers all have approval limits that are exclusive from each other, you can set them up as one level. For example:

  • Department managers could approve under £1K
  • Finance managers above £1K and below £5K
  • The CFO could approve above £5K

For more workflow scenarios, see Workflow Scenarios.

 

Configuring the steps

  1. Click Add a Step to create the first level of approval.
  2. Use Approve based on to direct documents to the right approvers according to specific conditions. 
    • Including Conditions: You can use multiple conditions from the available options. For instance, if your approval process requires all department heads to approve their own department's expenses, you could use Dimension Tags or Dimension Codes to identify each department and assign the relevant approvers. This ensures expenses are routed correctly at every approval level.
    • Omitting Conditions: If the approval level is intended to approve any document of that type, do not apply any conditions.
    • Non-PO Invoices only: This workflow process also includes an 'Employee' condition, letting you build an approval workflow for employee expenses. After selecting an approver, only employees linked to that approver on their Employee expenses account will appear for selection.

Preventing workflow conflicts

To ensure workflow consistency and prevent issues such as conflicts between steps, documents getting stuck, or the need for admin intervention, apply the same conditions across all steps of the workflow.

 
  1. Select the Approver from the dropdown.
  1. Enter the approver's limits or select the “No limit” option. Limits are based on net value; only documents within these limits will be sent to that approver.
  2. Select the relevant codes and use the Include or Exclude options to set your conditions. For example, to include all Dimension tags except two, choose Exclude and select those two codes or if the rule applies to only one Dimension tag, choose Include and add that code. Make sure any documents set to be excluded are included in another workflow, so they aren't missed in your approval process.

Budgetary Approval

Budget holder approvers will only receive approval emails tailored to their budget lines if the workflow is set up as follows: 

  • Conditions: Use the Dimension Code and / or Dimension Tag condition. Other conditions can be included if needed. Note, it is not possible to create a budget approval workflow based on GL Code without including Dimension Tags and / or Codes. 
  • Codes: The Dimension Codes or Tags you select must be linked to a Dimension that was labelled as Budgetary. See Using Dimensions for more details.
 
  1. If needed, click Add New to include more approvers at this level.
  2. When more than one approver is set up, select the corresponding Decision Mode:
    • All approvers must approve if limits apply: Use this if you want to approve multi-line, multi-departmental documents.
    • Any can approve: Select this only if multiple approvers are linked to the same department.
    • Select when processing the document: Requires users to manually choose an approver when processing the document.
  3. When done, click Save.
  4. If needed, click Add a step to add the next level of approval. Repeat until all required approval levels are set up. If the same approver is assigned to more than one step, you can configure whether their approval or rejection applies to the current step only, or to all steps at once.

Step 4: Save and Activate the Workflow

  1. After creating the workflow, click Save. It will appear as a 'Draft' in the Workflow listing.
  2. If you're ready to start processing documents through this workflow, click Activate.

WFA Migration

Legacy WFA

Activating your very first workflow triggers activation of the new WFA engine and disables the legacy workflow approval engine. 

 

Migrating results in the following:

  • The Approver setup tab will be renamed to Bulk Payments Approvers.
  • In Company Details & Settings > Approval Settings, Purchase Approval Settings will disappear. Batch Payment Settings will remain until they are migrated later.
    Image

If you are a customer using the legacy workflow approval engine, refer to the Migration process section for more information on migration.

 
 

Managing Workflows 

For a video tutorial of this process, watch Create and Manage Workflows (18.3N).

Go to Setup > Workflows

All active workflows appear by default in the Workflows screen.To view workflows in ‘Draft’ status change the filter to ‘None.’ 

  • Each workflow can be edited, copied, or deactivated via Actions. When workflows are copied, any details can then be updated, including process type. For example, if you want the same approval setup for invoices and credit notes, create one workflow, copy it, then update the process in one.
  • Easily view workflows by document type in the Process column.
 
 

Audit Log 

Go to Setup > Audit Log

Use the Audit Log to investigate any workflow-related issues:

  • View when approver records, or workflows have been activated or deactivated.
  • View any updates made to approval settings, approver limits, substitutes, workflow steps, and auto-approval rules.
  • View a change summary along with user and timestamp details.
  • Filter and export grid contents for further analysis.
  • Add or Remove columns.
 
 

Processing Documents using WFA

Initiating Workflow Approval

Once your workflows are complete and at least one is activated, the new workflow engine will initiate. All purchase orders and/or purchase invoices in the system will be picked up by a corresponding workflow based on its setup and document type.

For a video tutorial on sending documents for approval, watch Processing Documents with Approval Workflow (18.4N).

Draft POs

Saving a Purchase Order immediately initiates its approval process. If you'd like to update the PO before initiating approval, save it as a draft instead.

 

Viewing Document Approval Status

The approval status of all documents will display in the Approval Status column of the relevant listing grid listing grids. (Note, as each document can have multiple approvers instead of just one, it is no longer possible to display have an Approvers column in the listing grid.)

Approval Status in the Purchase Orders listing grid:

Approval Status in the Purchase Item Invoices / Credit Note listing grid:

Meaning of Document Approval Statuses

Note, if you are using the legacy WFA engine, and just activated a new workflow in the new WFA engine, the Approved status of all your POs will be updated. Please refer to section 9. Migration process in this article for more details.  

When a document goes through the approval process, it may go through different approval statuses, depending on the workflow setup. Click on the Document Approval Statuses to view their meaning:

Approval Not Required

 

Pending

 

Action Required

 

Admin Required

 

Awaiting Approval

 

Approved

 

Rejected

 

Cancelled

 
 

This status will appear for:

  • Documents from integrated projects that are set to not be reapproved in AIQ.
  • Purchase Orders for those on the AIQ1 price plan.
 

This is the initial status and is used when a newly created document is waiting to be picked up by a workflow. 

Action required means a document was picked up by a workflow but:

  • A step needs to be completed, for example, selecting an approver manually.
  • The document needs to be resubmitted for approval. In this case

Workflow Approval Administrators will be notified via email when their attention is required. 

Why is Admin Required Appearing?

  • Multiple workflows: If multiple workflows are found containing the same conditions, flip the rule of the first workflow on its head in the second workflow. For example: the first workflow includes dimension condition: warehouse, and 2nd workflow includes dimension condition: warehouse and supplier: xxx. Therefore, in the first workflow add supplier based on condition and set it to exclude supplier: xxx.
  • When no workflow is found. 
  • If the document was created before the workflow. In this case, edit the document to force it to enter a workflow.
  • A workflow was edited erroneously. 

How can I investigate the cause?

  • Use the Audit Log to view details of all edits.
  • Hover over Notes to view more details of the error. The WFA administrator must update the workflow accordingly for the document to be processed successfully.  
  • See the Approval Workflow Details Report in the Report Manager. This gives a breakdown of all the settings selected in each workflow:

The metro map displays which approval steps have yet to be approved. If a step needs to be resubmitted for approval, click Resubmit next to the relevant step.

The document is fully approved by all steps in the workflow.    

Documents rejected by the approver and requiring editing. When one step is rejected by an approver, the whole document is rejected.

Cancelled documents will not be picked up by a workflow. 

 

Viewing Approval Steps Statuses

For details on workflow steps, click on the document status link in the grid or on the Notes against each document. The status link displays a useful metro map indicating where the document is within a workflow. 


The metro map shows the status of the individual steps and details of the approvers:

Step Status Explanation
Awaiting Approval No approver has interacted with this step yet.
Approved

Steps get this status when all relevant approvers have approved the step. If the step was approved by a substitute, this will be detailed along with the regular approver using ‘on behalf of’.

Rejected At least one approver has rejected this step.
Skipped This appears when the value of the document exceeds the limits of the approvers  
in a step or if an approver cannot approve their own documents.
Select Approver This appears if the decision mode was set to manual approval.

Editing Documents after Approval

Approved documents can still be edited but the following updated will cause them to require reapproval:

  • Codes: If you update the document's Dimension Tag or GL Code and its associated workflow was based on those conditions.
  • Value: If you update the document value and the associated workflow has a lower reapproval tolerance.
 
 

Approving Documents

Approver Notifications

If you are an approver, you will be notified by email and/or the approval app. 

Note the following regarding notifications:

  • Multi-Approver Workflows: If there are multiple approvers in a step and only one approver is required, the other approver/s will receive a message when they go to click on the Approve / Reject option.
  • Auto-Emailing PO: See Creating Automations for full details. This feature allows you to automate the emailing of purchase orders to suppliers directly from the system. Once a PO is approved, it is automatically sent to the designated recipient, ensuring timely communication, reducing manual effort, and minimising errors.
  • Reminders: Automated reminder notifications will be available in the next stage of development. This feature will automatically send reminders to approvers for pending tasks, such as invoice approvals or purchase order approvals. It ensures deadlines are met, keeps workflows moving efficiently, and reduces delays caused by missed approvals.

There are three ways to approve a document, email, the listing grid, and the mobile app. For full details on the app, see Using the Mobile App for Workflow Approval.

Approving Documents via Email

If this approval request option was selected during approver setup, you will receive an email as follows:

Click the Approve or Reject button, enter an optional note, then click Approve or Reject

If you are unsure about whether to Approve/Reject a document, you must select an option but can leave a note stating your concerns. All notes will appear in the email to all approvers, so the next approver in line will see your note.

Approving Documents via the listing grid

If the document has a status of ‘Awaiting Approval’, go to Actions > Register Approval or Rejection

Enter an optional note and click Approve or Reject. 

If you are unsure about whether to Approve/Reject a document, you must select an option but can leave a note stating your concerns. All notes will appear in the email to all approvers, so the next approver in line will see your note.

 
 

Migration process 

Migration and Non-System Users

The new WFA engine requires all approvers to be set up as system users. All current non-system approvers will automatically be converted to system users.  This conversion will be triggered as soon as the Approval Settings screen is saved. These approvers will not receive an email system invite. 

Non-system approvers will have the following assigned to them during migration:

  • A new profile called ‘Non Finance Approver’ with a ‘Business User’ type at entity and group level (restricted permissions to PO and PI listing screens). Note that if you want approvers to start accessing the system, change this profile as it will not be possible to edit the profile's permissions or send a password setup link. Instead, create a new profile, configure its permissions and assign it to the migrated users. See Setting Up System Users for more details.
  • If the budget holder approval type was used previously, then the new approver will have the ‘Budget holder’ flag enabled the Approvers setup screen.  
  • If the approver was using the mobile app, then the approver will have the Mobile checkbox ticked under the new Approval Preferences.

Impacts on Legacy screens

When the Approval Settings screen is saved, the Purchase Approver screen will disappear.

Once the new WFA engine is activated, the legacy WFA setup screen, will no longer exist within the Company Details and Settings screen. Instead, these settings along with additional ones will appear in the Workflow setup screens. 

Legacy WFA setup screen before activation of new WFA engine 

A screenshot of a computer
                                                                                                                                                                                                                                                Description automatically generated            
Legacy WFA setup screen after activation of new WFA engine 

A screenshot of a computer
                                                                                                                                                                                                                                                Description automatically generated

In addition, customers using the legacy WFA Supplier type will no longer see the default approver option in the Supplier account settings screen. Approvers will also be managed in the new workflow.

Migration and Document Approval Status

When a new workflow is activated, all documents pending approval in the legacy Workflow approval engine will be assigned an ‘Action Required’ status, meaning they must be redirected to the new engine by re-submitting them manually for approval.

To do this, navigate to the Purchase Orders and/or Purchase Invoices listing screens, find the documents with ‘action required’ status (by filtering Approval Status column), and click on Re-submit for approval against each document. 

Overview of Document statuses

Old Status >> New Status   Explanation   

  

  

  

  

  

Pending >> Action required  

  

Any PO or PI with a Pending status must be assigned a new workflow and re-sent for approval.  

After migration, Action required can indicate that the document has been returned by an approver for editing.  

A screenshot of a computer

AI-generated content may be incorrect.

  

Pending Approval >> Action required  

The document was waiting for someone’s approval.  Once the new WFA engine is enabled, these documents must be re-submitted for approval.  

  

Approved >> Approved  

All fully approved documents will have the same status of Approved.  
Rejected >> Rejected   Documents rejected by the approver and requiring editing will stay as Rejected.  
Cancelled >> Cancelled   Cancelled documents will stay as Cancelled and will not go through the workflow approval process.  
Approval Not Required     Only visible to old workflow approval engine users. There is no equivalent for this status in the new engine.  

 

New Status   Explanation   
Pending  

The initial status in new WFA engine. It is used when a document:  

Newly created and is awaiting being picked up by the engine  

Awaiting approval    The document is awaiting approval from assigned approvers.  
Admin required   
  • Multiple workflows: If multiple workflows are found containing the same conditions, flip the rule of the first workflow on its head in the second workflow. For example: the first workflow includes dimension condition: warehouse, and 2nd workflow includes dimension condition: warehouse and supplier: xxx. Therefore, in the first workflow add supplier based on condition and set it to exclude supplier: xxx.
  • When no workflow is found. 
  • If the document was created before the workflow. In this case, edit the document to force it to enter a workflow.

Migration and Reports

Migration will not affect the reports available to you. Rather, the content of the reports will update to reflect the new WFA setup.