Human-approved automation: where to put the approval point

· Panda Yazılım

In human-approved automation the agent prepares the work and a person approves. The approval point goes in three places: when an amount exceeds a threshold, when information is missing from a record, and when a customer/supplier account is seen for the first time. A pilot usually starts at levels L2 (draft and approval) and L3 (automatic within rules).

What does human-approved automation mean?

Automation is misunderstood at two extremes. One is leaving everything to the machine; the other is still showing every record to a person. In the first, errors grow silently; in the second, the time automation saves is lost.

Human-approved design sits between the two. The agent reads, matches and writes the draft. Which records go to a person, you tie to a rule. The question is: if this step goes wrong, what does it cost and who notices?

A small test helps. Pick a process and ask: if the agent does this step wrong, who sees it, when and where? If there is no answer, or the answer is month-end reconciliation, an approval point should be placed in front of that step. If the answer is the same-day queue, the automation can move to a higher level.

What are the four autonomy levels?

Not every process has to run at the same level. The four levels are a common language for describing how much authority you give the agent.

  • L1, suggestion: the agent only suggests. For example it says which order it matched the invoice with, and a person enters the record.
  • L2, draft and approval: the agent prepares the record as a draft and it goes into the ERP once a person approves.
  • L3, automatic within rules: the agent posts by itself the records that stay inside a rule you wrote; it leaves anything outside to a person.
  • L4, autonomous: the agent posts records without asking a person; the person only reviews the report afterwards.

In most businesses L4 makes sense only for one or two low-risk jobs; for example putting a read email in the right folder. Jobs that touch money, stock or customer/supplier account balances stay between L2 and L3.

Where does the approval point go?

You do not need to look at every record. Three signals decide where to look.

Amount threshold

The cost of a wrong small amount is low, of a wrong large one high. You set a threshold: matched records below this amount pass automatically at L3, those above wait for approval. You set the threshold not by guessing but by looking at your past records; for example you sort the last three months of invoices by amount and decide above which point a person must always look.

Missing information

If the tax number cannot be read, if there is no order number, if the date and the due date conflict, the agent does not guess. The record falls into the approval queue with a missing-information label and says what is missing. Guessing looks fast; an invoice posted to the wrong customer/supplier account can go unfound for weeks.

New account or first-time situation

A supplier sending an invoice for the first time, a customer ordering for the first time, a document type not seen before: all of these go to a person. After you approve ten invoices from the same supplier, the rule for that supplier can move to L3. Trust is built through records, not given in advance.

How do levels mix within the same process?

The level is chosen per record, not per process. Think of incoming PDF invoices. An invoice from the same supplier, matching the order exactly and below the threshold you set becomes a draft at L3 and passes automatically. If the amount is above the threshold it drops to L2 and waits for approval.

If the order number is missing, or the invoice comes from a supplier seen for the first time, the agent only makes a suggestion (L1) and leaves the record to a person. In the same queue on the same morning, three different levels operate. The team does not even notice; only the records that land on screen become fewer, and the reason each one landed is written.

This differs from thinking of the approval point as a single gate. It is not a gate but a filter: ordinary records pass, risky records get caught.

What should the approval screen look like?

If the approval point is slow, people stop looking at the queue and start approving in bulk. Then approval loses its meaning. A good approval screen shows three things:

  • The source document: the PDF or email, with the places the agent read marked.
  • The agent's suggestion and its reasoning: which order it matched and why.
  • Approve, correct or reject with one click. The correction is recorded and the agent uses it on the next document.

Who gives the approval matters too. Accounting should approve invoice entry, sales operations should approve order matching. An approval by someone without authority is an approval only on paper.

At which level does a pilot start?

A pilot starts at L2. The agent prepares drafts, every record goes to approval. In the first weeks you see the agent's accuracy rate: how many drafts were approved unchanged, how many corrected?

If most drafts pass without correction, you move that document type to L3. Limits such as the amount threshold, the account list and the document type are written down; records inside the limits are automatic, those outside drop to approval. The decision to move comes not from a figure but from the approval history in your own records.

You do not jump to L4 right away. First you work at L3 for a few months and review the log. Processes involving money movements mostly stay at L3.

At the end of the pilot you have a concrete table: which document type runs at which level, which threshold was set, how long records wait in the approval queue on average. If the wait is long, the problem is not in the agent but in the approval process; you review the number of approvers or their shifts.

What happens when it goes wrong?

Wrong records can happen at L3 too. That is why every automatic posting is written to the log: which rule ran, which document it relied on, with what amount it passed. A short sampling is done in the morning or at the weekend; a few of the automatically posted records are picked at random and reviewed. If an error is found, the rule is tightened and the document type is temporarily pulled back to L2.

Rolling back should be easy. Lowering the threshold or removing a supplier from the automatic list is a one-line rule change.

How do approval points affect the team?

The team does not shrink; its work changes. The person who did data entry becomes the person who approves and manages the rule. When the agent makes a mistake or a rule gets stale, that person is the first to notice.

Every approval is a record of what you taught the agent. Rejected records improve the rule. The log keeps who approved which record and when; when asked in an audit, the answer is ready. Your ERP does not change, data does not leave the company; only a control layer enters the workflow.

At Panda you choose these levels while setting up the flow; in the demonstration given within 3 business days you see, with your sample documents, which record falls to which level. The 30-day pilot starts at L2 on one process.

Frequently asked questions

What is the difference between L1, L2, L3 and L4?

At L1 the agent only suggests. At L2 it prepares a draft and a person approves. At L3 it posts records inside the rule itself and leaves the rest to a person. At L4 it works without asking a person, and the person reviews the report afterwards.

How is the amount threshold determined?

Not by guessing but from past records. You sort the invoices of recent months by amount and decide above which amount a person must always look. The threshold is reviewed during the pilot and can be changed.

Is approval always required?

No. Records that stay inside the rule, with low amounts and from familiar accounts, can pass automatically at L3. Missing information, high amounts and new accounts go to approval. The rule is yours; you can change it.