Skip to content
gluon

An agent pays

The agent could queue small invoices. A large one waited for a second signature, and a bank change was refused.

We built this example on the product as it is, with invented names and figures. It is not a customer story.

Two people in an office reading an invoice held up on a clipboard.

Results

3 verdicts
for three actions of the same agent, each before it ran.
EUR 40,000
waited for the finance controller instead of leaving the account.
0
bank details changed on the strength of an email.
1 switch
that stops any action at once, without a new version.

Paying too much

A finance agent processes supplier invoices. It is useful for the hundreds of small ones, but the procurement procedure says a second approver signs above EUR 10,000, and only the supplier team may change bank details after a call-back check. An email asking for a new account number looks like any other request.

A verdict first

Actions are defined in the model with their effects, approvers and risk tier. Gluon checks each one against the procedure in force and the agent’s mandate: allowed, approval required or blocked. The right person is asked, and a kill switch stops any action at once.

  1. Allowed,
    approval required, blocked.

    The same agent, three requests, three verdicts.

    Agent · finance
    • Queue an invoice of EUR 1,200 for paymentAllowed
    • Approve an invoice of EUR 40,000Approval required
    • Change a supplier’s bank account numberBlocked
  2. Above EUR 10,000 a second approver signs.

    The decision names the rule, the mandate and the person asked.

    Decision · action

    Payment of EUR 40,000 put on hold until a second approver signs.

    Action
    invoices.approve · EUR 40,000
    Rule
    Procedure 2026 · §3.1
    Mandate
    Procurement agent · up to EUR 10,000
    Approver
    Finance controller · requested
    Approval required

Where Gluon acts