Rapid movement of funds rule

A rapid movement of funds rule detects money that leaves an account very soon after it arrives, typically most of the incoming amount. It does not look at either payment alone but at the pairing: a credit followed by a debit of similar size inside a short interval, which is the signature of an account used as a pass-through.

The fraud scenario this rule addresses

A mule account is rarely a place where money rests. Funds from a victim arrive, and within a short interval they are sent on to the next account in the chain, so the fraud proceeds are layered away from the original victim before a recall can reach them.

The pattern also appears in takeover cases, where an attacker credits a taken-over account and drains it, and in cash-out schemes where funds are converted at speed.

Data the rule requires

Example logic

Illustrative pseudocode: it compares each event with the rule's parameters and flags the ones that match. Parameters are symbolic: every value is institution-specific and has to be derived from your own transaction distribution.

RULE rapid_movement_of_funds
  FOR EACH credit C on account A:
    outflow = sum(debit.amount) WHERE debit.account = A
                                  AND debit.timestamp BETWEEN C.timestamp
                                                         AND C.timestamp + :holding_window
    retained = C.amount - outflow
    IF C.amount >= :min_amount
       AND outflow / C.amount >= :pass_through_ratio:
      RAISE alert(rule = "rapid_movement_of_funds",
                  account = A, evidence = C + matching debits)

Choosing a threshold

Three parameters work together: the holding window, the pass-through ratio and the minimum credit. A short holding window catches obvious pass-through but misses mules who deliberately wait. A long one catches patient layering but treats any account that spends its salary within the pay cycle as suspicious.

The pass-through ratio decides how much of an incoming amount must leave. A ratio near the whole amount finds accounts that retain almost nothing, but misses mules who are allowed to keep a commission. Lower it and the rule sweeps up customers who simply spend what they receive.

The minimum credit keeps trivial transfers out. Raise it too far and a mule network can split proceeds into many small credits, which is why this rule is paired with rules that aggregate across senders and beneficiaries.

False positives to expect

Many legitimate customers pass money straight through: someone paid by a client who immediately settles a bill, a landlord's agent collecting and forwarding rent, a small business that receives customer payments and pays its supplier the same day, a parent passing a family remittance on to a relative, or a person reimbursed for a group payment they covered.

Accounts that exist to move money, such as payment collection or marketplace settlement accounts, would alert constantly, so they need a separate profile. A history of the account behaving this way for a long time is strong evidence it is routine.

Investigating an alert from this rule

  1. Pair each credit with the debits that followed it, and confirm the amounts and timing really line up.
  2. Establish where the funds came from, and whether the sender has been reported as a victim or is linked to other alerts.
  3. Establish where the funds went: one destination or many, and whether those accounts show the same behaviour.
  4. Check the account's age and normal behaviour. A new account, or an old one with no earlier pass-through pattern, is more concerning.
  5. Look at whether the customer's profile explains the behaviour, for example a business that trades this way.
  6. If the pattern looks like a mule account, tag it, and review linked accounts, since mules rarely operate singly.

Related rules

Where this rule fits

The use case this rule supports is covered in mule accounts, and the fraud rules engine page describes how conditions like these are expressed and versioned.

Common questions

What is a rapid movement of funds rule?

A rapid movement of funds rule is a fraud rule that raises an alert when money leaves an account soon after it arrives, usually most of the incoming amount. It examines the pairing of a credit with the debits that follow it. That pass-through pattern is characteristic of mule accounts, where fraud proceeds are layered onward before a recall can reach them.

The rule has to decide how quickly and how completely funds must leave. A mule allowed to keep a commission will not move the full amount, and a patient mule will wait, so the window and the pass-through ratio are the main tuning decisions.

Accounts that legitimately move money on, such as a small business paying a supplier the day it is paid by a customer, resemble mules on this rule alone, which is why it is usually read together with the account's own history.

Discuss your transaction monitoring requirements

Tell us which transaction flows you need to monitor, which systems Akoben would integrate with, and how your fraud team works today.

Request a demo