Can an AI agent freeze an account on AML grounds?

Not on its own judgement. An AI agent can prepare the case for restricting an account, draft the restriction and, once a compliance officer approves, apply it in the core system. The decision to freeze on AML grounds stays with the officer, because it cuts a customer off from their money and risks tipping them off.

Why is an AML freeze different from other freezes?

Firms freeze accounts for several reasons, and they are not the same decision.

A customer who reports a lost card wants it frozen at once, and an agent can do that on request; see whether an AI agent can freeze a customer's card. A sanctions match confirmed by a compliance officer may leave the firm no choice: the funds must be frozen by law. A fraud hold protects the customer from a payment they may not have authorised.

An AML restriction is a discretionary judgement made on suspicion. It stops a customer, who may be innocent, from paying rent or wages. It can alert them that they are under suspicion. And depending on the regime, moving funds after a report may need the authorities' consent, while blocking them without proper grounds may expose the firm to a claim. Each of those is a risk a named person has to weigh.

What may the agent prepare?

The agent may:

• Assemble the case behind the request: alerts, investigation findings, the customer's activity and any report filed.
• Check what a restriction would affect, such as scheduled payments, direct debits and salary credits.
• Draft the restriction instruction, specifying what is blocked (outbound payments, cash, cards) and what is not.
• Draft the internal note for customer-facing teams, with approved wording that does not reveal the reason.
• Apply the restriction in the core system once a named officer has approved it.
• Track the restriction, set a review date and flag when it has been in place longer than policy allows without review.

The compliance officer decides:

• Whether to restrict at all, and how far.
• Whether the regime requires consent from the authorities before any further movement of funds.
• What the customer is told, and when.
• When to lift the restriction or exit the relationship.

What does a restriction request look like?

Take a retail bank. An AML case investigation finds that a customer has received several large transfers from accounts linked to an invoice fraud, and has begun moving the money to a crypto exchange. The reporting officer files a report.

The agent prepares the restriction request. It proposes blocking outbound transfers and cash withdrawals, leaving inbound credits and two direct debits for rent and utilities untouched. It lists the balance, the scheduled payments and a mortgage payment due in four days. It drafts the note for the contact centre: "There is a restriction on this account. Please refer any query to the specialist team." It does not mention money laundering.

The officer approves the restriction but tells the agent to let the mortgage payment through as well. The agent applies the restriction as amended, records the approval and sets a review in five working days. When the customer calls, the contact centre uses the approved wording and passes the call on.

What controls make it safe?

• Held, never allowed. Applying an AML restriction is a held action: the agent drafts it and waits for a named person's approval.
• The restriction is specific. The agent applies exactly what was approved, and the record shows what was blocked.
• No reason given to the customer. Customer-facing wording is pre-approved and generic.
• Time limits tracked. Restrictions without review are flagged to the officer.
• False positives are counted. Cases where a restriction was lifted with no concern found feed back into alert tuning; what a false positive in AML is explains why that number matters.

Where an agent assesses risk in this way inside the EU, the EU AI Act may also apply; see EU AI Act and AI agents in compliance and AML teams. The general principle is in our guide to AI compliance agents.

Where Pryme fits

In Pryme, preparing a restriction case and applying a restriction are separate capabilities. Applying one is a depth 4 action because it cuts a customer off from their money, and for AML grounds it is always held for a named officer. The approval, the exact restriction applied and the review date are filed on one record.