Approving agent proposals
AI agents do routine bookkeeping in Evenbead, but only within limits a person sets. Anything outside them becomes a proposal: the agent's work, waiting for a person to approve, change or reject. This page explains why something waits, how to fix it before you approve, and how to make a rule so the same thing never waits again. (Checked against the app on 2026-10-18.)
The queue
Proposals lists everything waiting, oldest first. Each card shows where it came from (the bank line, the date, the account), which agent proposed it, how it was coded, why it waits and the amount. Filter by agent, by Why it waits, by amount or by age. You can approve a card straight from the list, or select several and Approve selected; rejecting needs a reason. Firms see the same work for every client on the console's Approvals page.
Why something waits
Open a proposal. Why it's waiting gives the reasons in plain words. The common ones:
| Reason | What it means |
|---|---|
| Over the agent's limit | The amount is above what this agent may post on its own in this company |
| Low confidence | The agent was less sure than the floor you set (70% at least) |
| New vendor or customer / First time | Nobody has coded this vendor before |
| Not from a rule | The coding is the agent's guess, not one of your rules |
| Second opinion disagrees | Evenbead's evidence ranker named a different account |
| Sensitive account | Equity, loans and similar accounts always wait |
| Soft-locked period | The month is closed for agents |
Below that, Why this coding shows the agent's confidence, the accounts the line most likely belongs to, and how this vendor was coded before. If a receipt is in the inbox, Receipt offers to attach it.
Approve, edit or reject
- Approve posts it as the agent's entry, approved by you. A person other than the agent always approves.
- Edit before approving lets you change the account, split the line across accounts or projects, and note why. Then Approve as edited, or Save for review for someone else to approve. The agent's original stays on the record.
- Reject… asks for a reason, kept in the audit log. Snooze… hides it until a date. You can also comment, ask a colleague, or ask the client.
Approving needs the approve permission in the company. Everything you do is in the audit log, with the agent, its model and your decision.
Make a rule: "Always do this"
When the right answer is always the same for a vendor, select Always do this… on the proposal. The preview says what the rule does ("Always code ... to ..."), how many lines it matches now, and that every new line from this vendor will be coded by the rules agent within its limit. Select Create the rule.
From then on, an agent's coding that follows the rule exactly posts on its own, as long as it's within the agent's limit, and says so: the proposal shows Why it posted without a person. Making rules needs the "Create and edit categorization rules" permission; whoever runs the company (or, for a client, its firm) decides who holds it. Manage rules in Banking, Rules and suggestions.
Next
- Rules and splits: rules by amount and account, and split percentages.
- Agent Ledger Policy: the seven rules every agent works under.