AlphaAlpha Docs

Approval Workflow

Purchase order approval process

PO Approval Workflow

Configure and manage the internal approval process for purchase orders.

Approval Configuration

Approval is configured per tenant under Settings > Tenant > PO Approvals:

SettingDescription
EnabledTurn the approval workflow on or off for the tenant
Require requester signatureRequesters must sign (name + drawn signature) when submitting a PO for approval
Global approversUsers who may approve any PO, regardless of which rule matches
RulesThe list of approval rules (see below)

When approval is disabled, submitting a PO moves it straight to Ready to send.

Approval Rules

Each rule defines who must approve POs for a subsidiary:

FieldDescription
SubsidiaryThe subsidiary the rule applies to (required)
SupplierOptional — restrict the rule to one supplier. Leave empty for a catch-all rule (one per subsidiary)
Amount ThresholdOptional — POs below this total are auto-approved; POs at or above it require approval
ApproversOne or more users who can approve (at least one required)
Approval ModeAny — a single approval is enough, or All — every listed approver must approve

Rule Matching

When a PO is submitted, Alpha picks the rule as follows:

  1. Rules for the PO's subsidiary are selected
  2. A rule for the PO's exact supplier wins, if one exists
  3. Otherwise the subsidiary's catch-all rule (no supplier) applies
  4. If no rule matches, the PO cannot be submitted until a rule is configured

The matched rule is snapshotted onto the PO, so later changes to the rules don't affect POs already in approval.

Example Configuration

Thresholds are not built-in levels — they are whatever you configure. For example, a tenant could set up:

Rule 1: Subsidiary A, threshold €5,000, approver: Department Manager, mode Any
Rule 2: Subsidiary A, supplier X, threshold €50,000, approvers: Director + CFO, mode All

Approval Process

Submitting for Approval

  1. Complete the PO in Draft
  2. Click Request Approval
  3. If the tenant requires it, sign with your name and signature
  4. Depending on the matched rule:
    • Total below the threshold → auto-approved, status Ready to send
    • Otherwise → status Waiting on internal approval, all designated approvers receive an in-app notification

Approver Actions

Approvers (rule approvers and global approvers) have two options:

ActionResult
ApproveIn Any mode the PO becomes Ready to send immediately; in All mode it waits until every rule approver has approved
RejectPO becomes Internally rejected and returns to the requester (optional reason)

Only designated approvers can act, and each approver can approve a PO once. In All mode, global approvers can add an approval, but only the rule's own approvers count toward completion.

Approval Flow

For Approvers

Viewing Pending Approvals

  1. You receive an in-app notification when a PO awaits your approval
  2. Or filter the PO overview on Waiting on internal approval

Reviewing a PO

  1. Open the pending PO
  2. Review items, quantities, pricing, totals, and supplier information
  3. Approve or reject

Rejecting

  1. Click Reject
  2. Optionally enter a rejection reason
  3. The requester is notified, including the reason

For Requesters

Tracking Approval Status

  1. Open the submitted PO
  2. See which approvers have already approved (e.g. 1/2 in All mode)
  3. You are notified when the PO is approved or rejected

Handling Rejections

When a PO is rejected:

  1. Review the rejection reason
  2. Revise the PO as needed (rejected POs are editable)
  3. Resubmit for approval

Approval History

All actions are recorded on the PO's event log:

FieldRecorded
WhoApprover
WhenDate and time
ActionStatus changes, individual approvals, rejection reason

The requester's signature (when required) is stored on the PO as well.

Configuration Steps

  1. Go to Settings > Tenant > PO Approvals
  2. Enable the workflow
  3. Optionally require a requester signature and set global approvers
  4. Add rules per subsidiary (and optionally per supplier) with thresholds, approvers, and mode
  5. Save

Before going live, create test POs above and below your thresholds and verify the approve and reject paths.

On this page