The invoice approval problem

Finance teams are excellent at their core work: reconciliation, forecasting, reporting. But an outsized portion of their week is spent on coordination: chasing approvals, following up on missing details, explaining why a payment is delayed.

The bottleneck is almost never the finance team. It's the approval process itself — underdefined, email-based, with no visibility into status.

Here's a complete guide to fixing that.

The four-stage approval model

Most organisations need four stages for a proper invoice approval:

Capture — collect the invoice, vendor details, PO number, and cost centre

Validate — verify the invoice against the PO (can be automated)

Approve — cost centre owner approves; CFO approves if over threshold

Release — finance marks as approved for payment

Each stage is a distinct step in Atomic Work.

Stage 1: Capture (INPUT step)

Build an INPUT step with these fields:

Invoice PDF (file attachment)

Vendor name (text)

Invoice number (text)

Invoice amount (currency)

Cost centre (dropdown — pull from your chart of accounts)

PO number (text, optional)

Payment due date (date)

Notes (text, optional)

This step is assigned to whoever is submitting the invoice — typically the person who received it.

Stage 2: Validate (AI_PARSE + COMPARE steps)

Add an AI_PARSE step to extract the amount and due date from the invoice PDF and compare them to what was entered manually. If there's a discrepancy, flag it for review. If they match, continue automatically.

Then add a COMPARE step: if amount > $10,000, route to Stage 3B (CFO approval). Otherwise, route to Stage 3A (cost centre owner only).

Stage 3A: Cost centre approval (APPROVAL step)

Assign to the cost centre owner derived from the dropdown in Stage 1. Set a 48-hour escalation window — if no action, escalate to their manager.

Configure the rejection path: if rejected, notify the submitter with the reason and allow resubmission with changes.

Stage 3B: CFO approval (APPROVAL step)

Only triggered for amounts over $10,000. Assign to CFO, with a 24-hour escalation to COO.

Stage 4: Payment release (MANUAL_TASK step)

Assign to the finance team. Checklist:

Verify bank details on file match vendor record

Process payment in accounting system

Record payment reference number

Mark invoice as paid in tracker

The compliance layer

Every action in this workflow is logged with:

Who did it

When they did it

What data they were shown at the time

This is your audit trail. If a payment is ever questioned, you can show exactly who approved it, when, and what information they had. This is what "compliant, auditable" actually means in practice.

Rollout tip

Don't migrate all invoices on day one. Start with a single vendor or a single cost centre. Get feedback from the first 10 approvers. Adjust the form, the escalation windows, or the approval thresholds based on what you learn. Then roll out to everyone.

A workflow that's 90% right and actually used beats a perfect workflow that nobody follows.

The complete guide to automating invoice approvals