Skip to content

Glossary

Agent (BudAlly)

A scheduled or triggered process that reads ledger data, applies rule packs and drafts proposals — invoices, reorders, prices, vendor credits, campaigns — into the approval queue. Agents never execute; a named person approves each proposal.

Why it matters for reconciliation: much of the work, such as matching, classifying and drafting corrections, is repetitive and rule-based. An agent does the preparation and a person makes the decision, which is also what keeps an audit trail meaningful.

Example: an agent reads the day's unmatched tickets, applies the state rule pack and drafts a re-push for two sync failures and a void for one orphaned receipt. It places them in the approval queue, where a named person approves each. The agent has not changed anything itself.

Where this comes up on budally.com

  • Proposal

    What an agent produces: a drafted action with evidence, confidence, rules applied and a precondition hash, in one of the states Proposed → Reviewed → Approved → Revalidating → Executing → Executed → Verified, or Superseded.

  • Approval queue

    The single list of proposals waiting for a human decision, filtered by store, module and role. There is no 'approve all'. Executed items run under the approver's own POS or state-system credential and are logged.

  • Drafted N · executed 0

    The footer on every BudAlly briefing and agent run: the number of proposals drafted, and the number executed without a person — always zero.

Terms that refer here

Drafted N · executed 0,Learned rule