Conto

Escalation paths

Approvals for payment exceptions

Set the line above which a payment waits for a person, and where that request lands.

Illustrative example

Finance review queue

Assigned to Finance · Nothing sent while approval is pending

Quill Data

$8,500.00

procurement-agent · data subscription

Needs review

Above $5,000 → Finance reviewer → awaiting decision

Helia Compute

$920.00

Known supplier · compute capacity

Approved

Within automatic approval limit · no reviewer needed

The request records the routing rule, assigned reviewer, and final decision.

Controls that decide what needs a human

Amount, category, recipient, and budget each get a line. A request under all four clears on its own.

Threshold-based holds

Approval kicks in where spend, risk, or ambiguity crosses a line. The rest doesn't become a ticket.

Policy-aware escalation

Route on category, recipient, or budget as well as amount.

Clear approver context

Surface the rule result directly in the approval flow so reviewers understand why the payment paused.

Release where the request was held

The approval is recorded by the same control layer that held the request, with the decision and the reason together.

Demo

The payments too big to auto-clear

A $3,312 purchase order crosses the $2,500 line and pauses. The reviewer gets it with the rule that stopped it.