---
title: "Expense Approval Workflows"
url: "https://ankorpay.productfruits.help/en/article/expense-approval-workflows"
language: "en"
last_updated: "2026-10-22T11:40:05.161Z"
---

# Expense Approval Workflows

Control who approves each expense, from what amount, and in what order.

What are Approval Workflows?

Approval Workflows are rules that decide how an **expense** gets approved. Each expense is routed based on:

-   **Who** submitted it
-   The **team** they belong to
-   The **amount** of the expense
-   The **approval stages** (up to 3)
-   Whether approvals must happen in a **specific order**

**Example:** the Head of Deck approves deck expenses, while larger expenses need approval from two people.

## Where to find it

Approval Workflows are available in both modules. Go to **Menu → Approval Workflows** in:

-   **Operations** — for vessel expenses

![](https://cdn-assets.productfruits.com/26702d6e-0937-46e2-b3de-93e715a5d6a2)

  

  

  

  

  

  

-   **APA** — for Charter APA's expenses rules  
    ![](https://cdn-assets.productfruits.com/9029c493-d984-47b0-9e4a-746fe4d93989)

>   

  

  

  

  

**Important:** each module has its own setup. A user who only exists on Operations can’t be added to an APA workflow (and vice versa), so create a workflow on each side you use.

## What to expect

-   **All expenses are covered:** card expenses, manual expenses and automatically generated expenses.
-   **Transfers and payments are NOT covered** yet — payment authorisation is coming separately.
-   **Nothing changes until you add rules.** Saving the Workflow Settings alone doesn’t start a workflow.

[Loom video](https://www.loom.com/embed/a102cd485c9846a6b6aec9f966c8cc73)

## Step 1: Setting up Workflow Settings

The first time you open Approval Workflows, you’ll be asked to save these settings:

![](https://cdn-assets.productfruits.com/e718908a-7969-47d0-b706-5f7b2741407f)

## Step 2: Enable worflow and define basic rules

![](https://cdn-assets.productfruits.com/e15bc442-929f-4b11-b8c6-b7393afc9efb)

-   **Default currency** — the base currency used for your amount thresholds. Crew can still spend in any currency: a USD or JPY expense is converted to your base currency, then checked against your rules. This is not linked to KYC.
-   **Submitters can approve their own expense** — useful for a one-person team or a Vessel Admin managing their own spend. When off, submitters can’t approve their own expenses.
-   **Enable workflows** — when off, expenses follow the normal process. Your rules are kept, so you can pause workflows without deleting anything.

Once defined, click on Save Settings.

## Step 3: Create the Default workflow

Click on 'Configure Rules' for your default workflow.

![](https://cdn-assets.productfruits.com/0f420e7d-d5c2-444d-bd63-3651725a99f5)Then, click on '**Add Rules'** to create your first expense approval rule.

![](https://cdn-assets.productfruits.com/42bc5194-6747-4521-9af4-14250e6bbabf)

Start defining your rules, based on **'Up to Amount'** and who should be approving. You can select either 'Auto Approve' in case NO approval is needed, or add an existing AnkorPay user(s), in multiple stages if required. Continue Adding Rules, until you reach your highest amount and corresponding rule.

![](https://cdn-assets.productfruits.com/c7f2d10a-9a09-4648-9f0b-d3ce45dbdacb)  

This is a default workflow. meaning it will apply to all expenses, from ALL spenders.

## Step 3. 1 - How to create a Team Worklfow approval

After creating the default, click on '**\+ Create Expense Workflow**' button

Name the Group/Team (i.e Engineering, etc), select the spenders name and configure the required approval rules.

![](https://cdn-assets.productfruits.com/f3fe2e85-b723-4288-b757-dfb09b808a28)  
You can create multiple Teams, multiple expense workflows.  
  
The workflow that applies to an expense depends on the spender’s team:

| Spender is in… | They follow… |
| --- | --- |
| Deck Team | Deck workflow (e.g. Head of Deck approves) |
| Interior Team | Interior workflow (e.g. Head of Interior approves) |
| No team | **Default workflow**<br>(the catch-all) |

| Expense amount | Approval |
| --- | --- |
| Up to €50 | Automatically approved when submitted |
| Up to €200 | Two approvers (e.g. Captain + Chief Stew) |
| Over €5,000 | Further senior approval stage |

Amounts and approvers are only an example — set them to suit your organisation. Auto-approved expenses still need the spender to complete them (including the receipt) and submit.

### Multiple approvers: choose the order

-   **Any order** — set each stage to “Captain or Chief Stew”. Both must approve, but either can go first.
-   **Fixed order** — Stage 1: Chief Stew, Stage 2: Captain. The Captain can only approve after the Chief Stew has.

> **Note:** the same person can’t approve two stages. If the Captain approves stage 1, stage 2 must come from someone else.

## Step 4: How it works day to day

An expense only enters the workflow once the spender **submits** it:

1.  The expense is created (card payment or manual).
2.  The spender adds the receipt and details.
3.  The spender submits the expense.
4.  The workflow picks the matching rule.
5.  The expense is auto-approved or sent to the approver(s).
6.  Once all required approvals are done, the expense is **Approved**.

### Examples

-   **€20** — below €50, so it’s auto-approved.
-   **€150** — the first approver signs off (status: **Partially Approved**), then the second approver signs off (status: **Approved**).
-   **€5,200** — above €5,000, so it follows the senior approval rule.

### New status: Partially Approved

An expense is **Partially Approved** when it needs more than one approval and at least one approver has signed off. Filter expenses by status to find what needs action: **Ready for Review**, **Awaiting Approval**, **Partially Approved** and **Approved**.

## Changing a workflow

Organisation admins can change workflow settings and rules, add or remove approvers, pause workflows, and force-approve expenses where needed. If you remove an approver who still has expenses waiting on their stage, those need to be cleared first. All changes are tracked.

## Quick reference

-   User → Team → **Team workflow**
-   User with no team → **Default workflow**
-   Amount → Threshold → Stage → Approver(s)
-   Workflows must be **enabled** and have **rules** to apply.

Need help? Contact [support@ankor.io](mailto:support@ankor.io).
