Credits and refunds
Refunds and credits within your rules
Cap what an agent can credit per case and per day. Above it, a person decides.
Illustrative example
Customer credits & refunds
billing-agent · Credits up to $200 can clear automatically
Jordan Lee · Invoice 1042
$145.00
Service credit · duplicate usage charge
ApprovedWithin the $200 credit allowance
Acme Studio · Invoice 1043
$2,400.00
Refund · annual plan cancellation
Needs reviewFinance must approve before the refund is sent
Customer, original invoice, reason, and approver remain in one record.
Controls that prevent refund and credit leakage
Reason codes, a per-case cap, and a daily budget. Set them once per workflow.
Reason-code policy
Credits go out for the reasons on your list. An agent can't invent a new one on the fly.
Per-case thresholds
Keep any single correction or reimbursement inside a known range before approval is required.
Daily budget controls
Limit how much total credit or recovery spend can go out in one day across the workflow.
Escalation for edge cases
Send the oversized or odd correction to finance or operations. The easy cases don't wait behind it.
Demo
A refund with a hard ceiling
A $145 invoice credit clears on its own. A $2,400 SLA credit waits for finance, and a $5,600 refund demand stops at the adjustment cap.
Conto products behind credits and refunds
Human review
Approvals
Send payments that need approval to a reviewer before money moves.
Explore productRuntime controls
Policy Engine
As the agent owner or budget holder, decide how much it can spend, who it can pay, and when it must ask. Conto checks your policy before execution.
Explore productFinancial visibility
Audit and Reconciliation
Give finance a record of each agent payment, from the initial request to the final result.
Explore product