Approvals and exceptions
This page covers how approvals work at Level 2 (Prepared), where a person approves every transaction an agent prepares. It then covers what counts as an exception at Level 3 (Supervised) and Level 4 (Autonomous), how exceptions reach the right person and how that person resolves one.
Approvals at Level 2
Section titled “Approvals at Level 2”The agent prepares each transaction in full. Nothing is written to the ERP until a person approves it.
Every approval screen our forward-deployed engineers build shows the approver three things at once:
- the source document, such as the customer’s purchase order or the supplier’s invoice, next to the prepared transaction
- the checks that were run and how each came out: the price against the price list, the order against the credit limit, the purchase order number against open orders
- what the agent was unsure of, marked on the field itself: a part number matched from a description, a date read from a poor scan.
Every operations layer our engineers build has an approval screen with four choices.
| Choice | What happens |
|---|---|
| Approve | The operations layer writes the transaction to the ERP and records who approved it and when. |
| Correct and approve | The same, and each correction is recorded field by field. |
| Reject | Nothing is written. The approver gives the reason, such as a duplicate or a document that is not an order. |
| Pass it on | The transaction goes to the person with the authority to decide, such as the credit manager for an order over the credit limit. |
The approval screen and the work queue behind it come from our reusable tooling. The checks, the fields the agent marks and the routing are written for your workflows.
Our engineers build to two rules at Level 2.
- Every transaction gets its own approval. There is no approve-all. If approving one at a time has become a formality, that is evidence for a promotion review, not a reason for a shortcut.
- Corrections are the measurement. How often the approver changes something, and what they change, is what the next promotion review looks at. Our engineers count the corrections and bring the numbers to the review.
What counts as an exception
Section titled “What counts as an exception”An exception is a case an agent may not or cannot complete under its limits, which goes to a person. There are two kinds.
| Kind | Examples |
|---|---|
| May not: the case is outside the agent’s limits or fails one of your rules | An order above the amount limit. A customer who is not on the agent’s list. A price that does not match the price list. An order that would take the customer over the credit limit. Work that cannot wait for the agent’s time window, such as an invoice that has to post during month-end close. |
| Cannot: the agent is unable to finish the work | A scan it cannot read. A part number that matches two of your items. A purchase order with no ship-to address. A write-back the ERP rejected. |
When the checks leave doubt, such as two possible matches or a field that could not be read cleanly, the rule is to raise an exception, not to guess. An exception raised without need costs someone a minute. A wrong guess costs more.
Exceptions at Level 3 and at Level 4
Section titled “Exceptions at Level 3 and at Level 4”| Level 3 | Level 4 | |
|---|---|---|
| The agent completes on its own | Cases inside its limits that pass every rule | The same, plus the routine problem cases your policy tells it how to handle |
| What comes to a person | Everything else | What the policy reserves for a person, anything outside the limits and anything the agent cannot finish |
| What people do | Work the exception queue every day and spot-check completed work | Set the policy and audit a sample |
At Level 3, the answer to anything unusual is to send it to a person. At Level 4, the workflow owner has written down what the agent does with each routine kind of problem. For example, when a purchase order has no ship-to address, the agent asks the customer for it. Fewer cases reach a person, but the limits, the audit trail and the stop switch still apply.
How exceptions reach people
Section titled “How exceptions reach people”Our engineers build every exception queue to five rules.
- They arrive in a queue in the operations layer, the place your people already work, not in someone’s personal inbox.
- Each one states its reason in plain words. “The price on line 3 is lower than the price list” is a reason. An error code is not.
- Each one carries the work so far: the source document and everything the agent had done when it stopped, so the person does not start from nothing.
- The workflow owner decides the routing, by reason, by amount or by customer and supplier. Price mismatches might go to inside sales, credit questions to the credit manager and unreadable documents to the order desk.
- An exception that waits too long is flagged to the workflow owner. How long is too long is set for each workflow.
How a person resolves one
Section titled “How a person resolves one”The exception screen is built around four steps.
- Open the exception and read the reason.
- Compare the source document with what the agent prepared.
- Choose what to do:
- fix the data and complete the transaction yourself
- fix the data and send it back for the agent to finish
- reject it, with a reason
- pass it to the person with the authority to decide.
- The resolution is recorded: who resolved it, what they changed and the reason they chose.
Exception reasons are also the best list of what to fix next. The workflow owner and our engineers look at the reasons that come up most. A recurring one leads to a change: a new rule, a different limit, a corrected item record in the ERP or a word with a customer about how they send orders.
Rules and limits change only with the workflow owner’s sign-off. An agent does not widen its own limits because a person resolved a similar case the day before.