Decisions and approvals
How to read a decision card, what your signature covers, why a card can turn stale, and how errors are counted.
Agents prepare work. People decide. The decision card is where the two meet: it shows what an agent proposes and why, and your signature on it is what allows anything to happen. This page covers the card, the signature and the record of what went wrong.
Post BIL-2026-0733 to Freight, VAT 25,5 %
- Reason
- Baltic Freight OÜ, 3.720,00 €. Same account as the last 11 invoices from this supplier.
- Evidence
- 11 earlier invoices
- Confidence
- 91 %
What a decision card shows
Every card has the same parts, so you can read one in a few seconds.
- Type and agent. What kind of decision this is and which agent prepared it.
- Proposal. What will happen if you approve, in one line.
- Reason. One to three plain sentences with figures.
- Evidence. Links to the records the proposal rests on. Open them before you sign.
- Confidence. How sure the agent is, and what that figure is based on: its record with similar cases, an exact rule match or a calibrated model.
A card cannot be created without a reason, evidence and confidence.
Example: the Ledger agent reads BIL-2026-0733 from Baltic Freight OÜ for 3.720,00 €. The card proposes the freight account with VAT 25,5 %, with a confidence of 91 %, and links 11 earlier invoices from the same supplier as evidence.
Approve, edit or reject
You have three answers.
- Approve. The proposal runs as shown.
- Edit. You change the proposal and sign your version. The edited content is what runs, and the correction is recorded.
- Reject. The proposal is dropped. A rejection needs a note.
Doing nothing is not an answer. A card that nobody decides expires. A timeout is never a yes.
You can decide cards in two places: the decision queue in Agents, and the morning board in Command, where the open card appears in full in the inspector. Some cards are decided only in the queue: payments, anything that touches a bank account number, cards that need two signatures and cards that send something outside the company. Reminder cards from the Collections agent can be signed together in one gesture. Each card stays listed with its own letter and amount.
What your signature covers
Your approval is bound to the exact content you saw and to the versions of the records it was computed from. Before the work runs, Tosven checks three things again:
- Are the source records still the same?
- Do you still hold the permission to approve this?
- Is the agent still allowed to act, with no kill switch in place?
If any answer is no, the card turns stale. Nothing runs, the reason is recorded and the card returns to the queue.
Example: at 08:20 Elina Koskinen approves reminder 2 of 3 for INV-2026-0418 to Nordlys AB, with 48.000,00 € open. At 08:31 Sara Nyström matches payment PAY-2026-0391 to the invoice. At 08:40 the balance is read again before sending. It has changed, so the card turns stale and no letter leaves.
When two people must sign
Some decisions need two different people:
- every payment
- every action on a new or changed bank account number
- every ledger entry above 10.000,00 €
The same person cannot sign twice, and the one who proposed a card cannot be the one who decides it.
The signed record
Three things are recorded separately for every card: who proposed, who decided and who carried it out. Decisions are linked in a chain per company. They cannot be edited or deleted.
When an entry is posted under a published rule at L2, the decision is signed in the name of that rule and of the person who published it. See autonomy levels.
An auditor can open a read-only view for any date. It shows the signatures as of the end of that day, a check that the chain is intact, and the autonomy levels and rules in force on that day.
| Card state | Meaning |
|---|---|
| Open | Waiting for a person, or for a second signature |
| Approved | Signed, waiting to run |
| Executed | Ran once, with the checks passed |
| Stale | Approved, then the data or a permission changed. Nothing ran |
| Rejected | Declined by a person, with a note |
| Replaced | A newer card exists for the same record |
| Expired | Nobody decided in time |
The error log
Clicking approve does not make an agent right. Accuracy is measured from what happened afterwards at the source:
- A coding counts as correct when the period locks and the entry was never reversed or corrected.
- A reminder is verified when the invoice is settled.
Three mistakes count as critical: a wrong VAT box, a wrong period and a wrong counterparty. A wrong account inside the same group of the income statement is an error, and is not critical.
Each agent's accuracy, cost and latest error are shown on the team roster next to its manager. The error log is what you read before you raise a level, and it is the usual reason to lower one. When a critical error is confirmed in a decision made under a published rule, that rule is retired at once.
On the way
A monthly control report for the auditor, with rule versions, overrides, level changes and replay results in one export, is planned.
Next steps
- Autonomy levels: how the error record feeds a raise, and how to lower a level at once.
- Command: the morning board where waiting decisions appear.
- Run plan: when agents prepare their cards, and how to run one now.