The Policy Has to Live on the Glass

Leave a Comment / Artificial Intelligence, Financial Insights
A standing glass plate on a dark desk with four etched lines: Dual-review, Propose, Never post, Owner. A blurred invoice-queue monitor sits behind it.
A policy surface is the place an operator can see and change the rules the agent has to survive, without opening a prompt or a repo. Amounts. Propose vs post. Who owns the miss.
 
Most agentic finance products skip that object. The rules live in instructions. The demo still clears a clean invoice.
 

If the dual-review amount lives in a prompt, you do not have a finance workflow. You have a demo that will drift the first time someone edits the system message.

Finance already knows this. A close checklist is not tribal knowledge in Slack. An approval matrix is not a temperature setting. The rule is a surface: visible, changeable, attributable.

Agentic AP and close products keep hiding that surface. The homepage says the agent works. The demo shows a clean invoice clearing. The threshold that kept the $7,500 item in the pile is in a repo. When the pile is still $9,617, nobody can point at the line that failed. They point at the model.

What Has to Be On The Glass

Four things, at minimum, for an invoice or a journal the agent is allowed to touch:

  • Dual-review amount. Above this, a second human. Not “the model got cautious.”  
  • What the agent may propose. Draft, code, match, route.  
  • What the agent may never post. Same rule for pay, waive, override
  • Who owns the miss. A role, not “human in the loop.”
If those four cannot be seen and changed by the operator without a prompt engineer, the control does not exist for the buyer.
 
The $7,500 item stays in the pile. The $2,116 item can wait. Someone in finance has to own that split, and own it when the threshold moves.
 
That is not a chatbot preference pane. It is the same class of object as a posting period or a segregation-of-duties rule.

Why Product and PMM Both Need It

On the product side the surface stops the happy-path demo from being the product. Exception first. Policy visible. Then the clean invoice.
 
On the GTM side the surface stops the first sentence from being autonomy. “Human-in-the-loop” and “existing ERP permissions” are asterisks. The glass is the sentence.
 
The Accounting Engineer is the person who insists on that object — inside the vendor, before the demo ships. Most Office of the CFO teams will not invent the role for you. If your agent keeps the rules in a prompt, you are asking them to.
 
 

Related:

https://www.timpratt.me/what-is-an-accounting-engineer/

https://www.timpratt.me/trust-before-autonomy/

https://www.timpratt.me/agentic-ap-positioning-before-after/

Leave a Comment

Your email address will not be published. Required fields are marked *