Enforcement orders reach Saudi banks electronically through Tanfeeth, and each one comes with a deadline. Blocking an account, holding a balance, transferring funds and lifting a restriction all sound simple. The difficult cases are partial execution, competing orders and the evidence a bank needs when someone asks, months later, exactly what it did.
What an enforcement order asks of a bank
Under the Kingdom's enforcement regime, courts can direct banks to act on a debtor's accounts. The orders arrive through Tanfeeth rather than on paper, and banks are expected to execute them accurately and within the time allowed. Most orders fall into a few types:
- Block: restrict the subject's accounts so that funds cannot leave.
- Hold: reserve a specified amount from the subject's available balances.
- Transfer: move held funds to the account the order designates.
- Lift: remove a block or hold when the order is settled or withdrawn.
Each order identifies its subject by an identity number, such as a national ID, Iqama or commercial registration number, and carries a reference that later orders and responses must match. The bank's answer has to state what it actually did, including any amount it could not hold.
Where manual handling breaks down
Many banks started with a desk of experienced people, a work queue and a set of core banking screens. That works at low volume. As volumes grow and requirements change, the same weaknesses tend to appear:
- execution rules live in people's heads, core banking customizations and middleware scripts, so a rule change waits for a release;
- partial execution is worked out by hand, under time pressure, across several accounts and currencies;
- lifts get less attention than blocks, so customers stay restricted after their order is settled;
- nothing ties each order to the holds, transfers and lifts it caused, so breaks surface weeks later;
- when compliance or internal audit asks what happened to an order, the answer is rebuilt from logs and email.
Each of these is an operational risk with a regulatory side and a customer side. A late block can let funds leave that a court ordered held. A late lift can leave a customer unable to pay salaries or rent.
Start the clock at intake
Automation starts when the order arrives. Every order should be received through a connector, validated against the expected format, checked for duplicates and given a deadline clock at the moment of receipt. The clock should follow the calendar rules for that order type, including weekends and public holidays, and it should be visible to the desk at all times.
Sort the work queue by earliest deadline, and alert while there is still time to act. A report of missed deadlines the next morning is useful for management, but it does nothing for the order that was missed.
Resolve the subject carefully
Matching the order to the right customer is where errors cost the most. Match on the identity number first, then confirm with name and other data. Names written in Arabic and in Latin script vary widely between systems, so name matching on its own produces both false matches and misses.
Weak matches should go to a person with the evidence on screen, and should never execute automatically. The quality of your customer master matters here. Identity data that is verified through national services such as Yakeen at onboarding and refresh, and linked across retail and corporate relationships, makes resolution faster and safer. KYCLink is our gateway for that verification work. If you are considering AI to help the desk with matching or triage, keep it to proposals that a person approves, as we describe in putting AI agents to work inside the security boundary.
Write partial execution down as rules
Full execution is the easy case. Most disputes start where the balance does not cover the order. Each of the following needs a written rule that compliance and legal have approved:
- Accounts in scope. Which account types are included, and how joint, minor and corporate accounts are treated.
- Allocation order. Which accounts are held first when several together cover the amount.
- Currency. Which exchange rate applies to foreign-currency balances, and when it is fixed.
- Protected amounts. Any balances or incoming credits that the applicable rules protect from enforcement.
- Shortfalls. What happens to new credits after a partial hold, and how the shortfall is tracked until the order is met or lifted.
- Competing orders. The sequence in which several orders against the same subject are applied.
Once the rules are explicit, they can be configured, versioned and tested. A new version can be replayed against recorded, masked orders before it goes live, so compliance sees every outcome that would change and approves the change knowing its effect. That is the approach EnforceDesk takes: each order type is a versioned catalogue service, the rules are configuration, and every change goes through maker-checker.
Give lifts the same priority
Banks tend to optimize the path that takes money. The path that releases it matters as much. A lift should release exactly what the related order held, and it should run under the same deadline discipline as a block. Track lifts as a measure in their own right: time to release, and holds still in place after their order has closed.
Keep evidence as you go
When SAMA, internal audit or a court asks what happened to an order, the bank should be able to answer in minutes. That means recording, for every order:
- what was received, when, and through which channel;
- how the subject was resolved, and who confirmed any weak match;
- which rule version applied, and what it decided for each account;
- the holds, transfers and lifts placed in the core, with their references;
- the response sent, and whether it met the deadline;
- every manual decision, with the person and the reason.
Store the record in tamper-evident form, such as a hash-chained event log, and assemble it into evidence packs by order and by period. Evidence collected at the time costs far less than evidence rebuilt under pressure, and it is far more convincing.
Reconcile orders, ledger and core
Every order should have a known position at any moment: amount ordered, amount held, amount transferred, shortfall and amount released. Those positions should agree with the holds and transactions in the core banking system and with transfers settled through the payment hub. Run that reconciliation daily, give each break an owner, and report breaks by age. A hold in the core with no live order behind it is as serious as an order with no hold.
The same positions must survive any change to the core. If a core banking migration is on your roadmap, enforcement holds belong in its scope from the first rehearsal; our note on core banking migration rehearsals explains why.
Measures for the COO and compliance
A small set of numbers shows whether the desk is under control:
- on-time response rate by order type, against target;
- share of orders handled with no manual step, and the reasons for the rest;
- time to lift, and holds remaining after their order closed;
- open shortfalls and their age;
- reconciliation breaks by age and owner;
- rule changes released, and how long each took from request to live.
What to do next
- List the order types. Record volumes, deadlines and where each type is handled today, by system and by team.
- Write the rules down. Cover accounts in scope, allocation, currency, protected amounts, shortfalls and competing orders, and get compliance and legal sign-off.
- Take a baseline. Measure on-time performance and lift times for the last quarter.
- Test your evidence. Pick one order from last year at random and check whether you can produce its complete record within a day.
- Choose what becomes configuration. Decide which rules should change without a release, and how each change will be simulated and approved.
- Reconcile daily. Match orders against core holds, transfers and lifts, with an owner for every break.
If enforcement orders still depend on a few experienced people and a lot of manual checking, book an executive briefing. We will review how orders are handled today and give you a written view on what to automate first and what evidence you should be able to produce.