Identify the hazards

In your use case, for example:

• In step 'Pays supplier invoice', the agent pays the wrong amount or the wrong party because it misreads its inputs (Matched invoice, vendor master bank details).
• In step 'Matches invoice to purchase order', the agent draws a wrong conclusion and acts on it.

In your use case, for example:

• In step 'Pays supplier invoice', the agent pays the wrong amount or the wrong party.
• In step 'Pays supplier invoice', the agent uses a tool, a recipient or a scope it was never meant to use.

In your use case, for example:

• In step 'Pays supplier invoice', the payment becomes final before anyone reviews it; afterwards the money can only be recalled with effort, and recalls often fail.
• Once the money has left the account, the payment from step 'Pays supplier invoice' cannot be taken back.

In your use case, for example:

• In step 'Pays supplier invoice', the agent meets its target but harms suppliers or the business along the way.
• The goal set for step 'Sends payment advice email to supplier' rewards a shortcut nobody wanted.
• In step 'Matches invoice to purchase order', the agent meets its target but harms suppliers or the business along the way.

In your use case, for example:

• In step 'Matches invoice to purchase order', the agent meets a case outside what it was designed for and does not notice.
• The situation of suppliers changes, and the agent keeps applying old assumptions in step 'Matches invoice to purchase order'.

In your use case, for example:

• Someone manipulates an input of step 'Pays supplier invoice' (Matched invoice, vendor master bank details) so that the agent acts against you.
• A hidden instruction in a document or message takes over the agent in step 'Matches invoice to purchase order'.

In your use case, for example:

• In step 'Pays supplier invoice', the agent treats some suppliers worse than others.
• Past data makes the agent repeat an old bias against a group in step 'Pays supplier invoice'.

In your use case, for example:

• An error in another system or agent makes the agent act wrongly in step 'Matches invoice to purchase order'.
• A mistake in step 'Matches invoice to purchase order' triggers a chain reaction further down the process.

In your use case, for example:

• The people who check step 'Pays supplier invoice' approve without really checking.
• Reviewers of step 'Pays supplier invoice' face more cases than they can check properly.

In your use case, for example:

• Nobody can explain afterwards why the agent acted as it did in step 'Pays supplier invoice'.
• When an incident needs analysis, the logs for step 'Sends payment advice email to supplier' are missing.
• Nobody can explain afterwards why the agent acted as it did in step 'Matches invoice to purchase order'.

In your use case, for example:

• In step 'Pays supplier invoice', the agent gets stuck in a loop and pays the same item twice.
• Step 'Pays supplier invoice' uses far more budget or resources than planned.

In your use case, for example:

• The vendor behind step 'Pays supplier invoice' changes or withdraws its model or tool.
• A tool or plugin used in step 'Sends payment advice email to supplier' is compromised.
• The vendor behind step 'Matches invoice to purchase order' changes or withdraws its model or tool.

In your use case, for example:

• Suppliers do not realize they are dealing with an AI in step 'Sends payment advice email to supplier', or trust it too much.
• In step 'Sends payment advice email to supplier', the agent sounds certain where it is not, and people rely on it.

In your use case, for example:

• Step 'Pays supplier invoice' silently stops, and something that must happen does not.
• In step 'Pays supplier invoice', the agent skips cases without telling anyone.

In your use case, for example:

• In step 'Pays supplier invoice', the agent reveals personal or confidential data to the wrong party.
• Details from the inputs of step 'Sends payment advice email to supplier' (Payment record, supplier contact data) end up where they should not.
• In step 'Matches invoice to purchase order', the agent reveals personal or confidential data to the wrong party.

In your use case, for example:

• After a model or prompt update, the agent gets worse in step 'Pays supplier invoice' and nobody notices.
• The agent slowly drifts in step 'Sends payment advice email to supplier' as its inputs (Payment record, supplier contact data) change over time.
• After a model or prompt update, the agent gets worse in step 'Matches invoice to purchase order' and nobody notices.