The invoice arrives without a purchase order. The supplier has changed its bank details. The delivery came in two parts and the bill covers both. Your most experienced accounts payable specialist handles each of these in a minute, the same way every time, and nobody gets paid twice. Now picture the newest clerk doing exactly that in their second week, with an AI assistant preparing every invoice and flagging the case before it reaches a payment run.
That is what a fully powered finance team looks like. It begins with the part of the procedure nobody wrote down.
The procedure records the day everything arrives complete.
A written procedure describes the path where the paperwork matches and the numbers agree. Your best people earn their reputation on the other days. They know which differences can pass with a note, which ones stop the work and whom to ask. That knowledge lives in habits and in a few sentences they say to new colleagues.
It is also exactly what a capability needs written down. An AI assistant given only the happy path will follow the happy path, confidently, into the one case that matters. The exceptions are the instructions.
A supplier-invoice approval, as written.
Here is a recognizable procedure from an invented 80-person facilities-services company. Every step is reasonable. Read it as a new clerk would.
Illustrative example with invented data. The procedure as the company has it written.
Supplier invoice approval
- Save the invoice from the accounts payable inbox.
- Match the invoice to its purchase order.
- Confirm the goods or services were received.
- Check the invoice total against the purchase order.
- Send the invoice to the budget holder for approval.
- Enter the approved invoice for the next payment run.
- File the invoice with its purchase order.
The same procedure, with the exceptions written in.
Now the same seven steps after half an hour with the specialist who runs them.
Illustrative example with invented data. Annotations from a conversation with the accounts payable specialist.
| Step | The SOP says | It leaves out | The specialist’s rule | Stop and ask |
|---|---|---|---|---|
| 1 | Save the invoice. | Duplicates and changed bank details. | Search the supplier’s last 90 days for the same number or amount. Bank details come from the supplier record, never the invoice. | Bank details differ: the controller, who confirms by phone on the number already on file. |
| 2 | Match to the PO. | Invoices with no PO. | Contracted services on the standing list need none. Anything else goes back to the requester for a PO. | No requester named: the purchasing lead. |
| 3 | Confirm receipt. | Partial deliveries. | Approve only what the receiving record shows. Hold the balance on the same invoice. | No receiving record after five business days: the site manager. |
| 4 | Check the total. | How close is close enough. | A difference within $100 or 2%, whichever is lower, proceeds with a note. | Anything larger: the buyer who raised the PO. |
| 5 | Send for approval. | Limits and absences. | Over $10,000 also needs the controller. An absent approver’s delegate is on the delegation sheet. Nobody approves their own purchase. | No delegate listed: the controller. |
| 6 | Enter for payment. | Discounts, cutoffs and disputes. | Early-payment discounts go in the earlier run. Tuesday noon is the cutoff for Thursday. | Supplier in dispute: the controller. |
| 7 | File it. | What “complete” means. | File the PO, receiving record, approval and any variance note, naming who accepted the variance. | Approval record missing: the controller, before the payment run. |
The procedure kept its seven steps. Each step gained the rule for its awkward case and the person to ask when the rule runs out. A new clerk now catches what the specialist would have caught. An AI assistant preparing each invoice packet flags the changed bank details or the variance above tolerance, and names whom to ask. The clerk enters the invoice, and the controller confirms any change to bank details. AI prepares; people decide.
Your best people decide how the work develops.
Capturing how your specialist works puts their judgment at the center of the procedure. Their rules become the draft. Where two colleagues handle the same case differently, the difference goes on paper for the controller to settle, and the team then works to one standard. Each improvement they suggest later has a place to land.
This is how you 10X what your team can do: the whole team works at the level of its best person, on every invoice, including the strange ones. It is also where AI capability planning starts. Begin with the outcome, here every supplier paid once, correctly and on time. Map the work that crosses teams: purchasing, receiving, budget holders and accounts payable. Then land each rule on the role that owns it.
Fully Powered works across ChatGPT, Claude, Copilot and Gemini. The rules run in the AI your team already uses, and your organization keeps control of how the work gets done. To turn the approved procedure into a workflow, read From SOP to AI workflow. To bring the wider team into the plan, read Build your AI plan with the people who do the work.
Five questions for a 30-minute conversation.
Sit with the person who does the work, open the written procedure and a few recent cases, and ask these in order.
- Walk me through the last one that went sideways.What did you notice first, and what did you do next?
- Where do you stop?For each step, what makes you pause the work, and whom do you ask?
- What do you check that the procedure never mentions?The search, the second look, the record you open out of habit.
- When two records disagree, which one wins?The purchase order, the receiving note or the supplier’s paperwork.
- Who does this differently from you?Name the case, and say which way you think should become the rule.
The answers become an exception register: every step with its missing decisions, stop conditions, the person asked and the evidence behind each rule. The SOP exception capture capability prepares that register for the procedure’s owner to approve. Then pilot acceptance-test preparation turns the awkward cases into tests, the subject of What we test before we call an AI workflow ready.
Bring one written procedure and the last case that went sideways.