Escalation paths

Approvals for payment exceptions

Keep routine payments moving while high-value or ambiguous requests pause for human review.

Industries

Supply chain · Billing · Fintech treasury · Travel & events

Run demo Talk to sales

Best for

Large orders, travel, credits

Controls

Thresholds, escalation, records

Outcome

Humans review exceptions only

How payment exceptions are reviewed and resolved

Exception

A payment trips a policy. $8,500 to quilldata.io is over the monthly cap.

Approval request

Conto packages the full context and creates one request.

agentprocurementamount$8,500rulemonthly cap

Slacksecure

Emailsecure

Telegramsecure

WhatsAppsecure

Webhooksecure

Sent to each configured channel with a secure approval link.

One-click decision

The reviewer decides right from the message.

ApproveDeny

Once a decision is submitted, the request is resolved and any other approval links close automatically.

Resolved

Approved, the payment executes. Denied, it stays blocked. Either way it is logged with who decided, when, and through which channel.

Routine spend never stops. Only exceptions ask a human, on whatever channel they already use.

Approval queues with the triggering rule attached

Approval queues include the request context, the triggering rule, and the final decision so teams do not have to reconstruct the payment story later.

Approval queue2 pending

procurement-agent → Quill Data

quilldata.io · data

$8,500.00

counterparty trust · newwaiting 4m

ApproveDenycontext

procurement-agent → Northwind Ops

over weekly limit · waiting 12m

$3,150.00

How ambiguous payments pause for approval

Agents keep their fast path for routine spend while Conto turns high-value or unclear requests into reviewable payment decisions.

Step 1

The agent reaches a decision boundary

A purchase, payout, or credit request is valid enough to consider, but large or unusual enough that it should not clear automatically.

Step 2

Conto routes the request into approval

Threshold rules, counterparty requirements, or policy combinations switch the request from autonomous execution to approval-needed.

Step 3

Humans review with full context

Approvers see the request amount, recipient, category, and the specific rule that triggered review before deciding to release or reject it.

Controls that decide what needs a human

Approval rules evaluate amount, category, recipient, and policy context so human review is reserved for the exceptions that need judgment.

Threshold-based holds

Apply approval only where spend, risk, or ambiguity crosses a line, without turning every payment into a ticket.

Policy-aware escalation

Use category, counterparty, or budget rules to decide whether the request should route to review, not just the amount.

Clear approver context

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

Release from the same control plane

Approvals happen inside the same payment and audit layer that blocked the request in the first place.

Demo

Watch an exception route to the right reviewer

A procurement agent submits a purchase order that crosses an approval threshold. The demo shows the triggering policy, reviewer context, and final payment state from hold to release or denial.

Autonomous procurement with bidding and approval workflows

Billing agents can issue credits and refunds without giving away revenue

Money movement and treasury management for fintechs

Run demo Browse demos

Conto products behind exception review

Human review

Approvals

Route only the payment requests that need judgment to a human reviewer, with the triggering policy, recipient, amount, and agent context already attached.

Explore product

Runtime controls

Policy Engine

Define the rules for how agents spend, then evaluate every payment request before funds move. Conto keeps limits, categories, trust requirements, and approval rules in the transaction path.

Explore product

Financial visibility

Audit and Reconciliation

Attach agent, counterparty, policy, approval, and execution context to every transaction so finance can understand what happened without chasing separate systems.

Explore product