Skip to main content

Three Payouts Under the Threshold

A reproducible teardown. Code: examples/split-payments-shadow.

The setupโ€‹

Payouts over $5,000 need a human. An AP agent has a $14,700 invoice from a new vendor. Whether it was tricked, or is just "helpfully" avoiding a slow approval, it pays in three parts:

payout 4900 USD to ben_new_vendor_77 invoice INV-8812, part 1
payout 4850 USD to ben_new_vendor_77 invoice INV-8812, part 2
payout 4950 USD to ben_new_vendor_77 invoice INV-8812, part 3

Each payment passes the rule. Splitting a payment to stay under an approval or reporting threshold is one of the oldest patterns in payments, and agents find it because it's the path of least resistance.

Find it first, without blocking anythingโ€‹

Before enforcing a new policy on live traffic, run it in shadow mode ("mode": "shadow"): every action is evaluated and recorded, and nothing is blocked. The shadow drift report then shows:

Shadow drift report:
- 1 possible split payment pattern(s): several payments just under an approval threshold to the same recipient within 24 hours.
* 3 x create_payout to beneficiary.id=ben_new_vendor_77: 14700 total, threshold 5000

The rule behind it: 2 or more payments of the same action to the same recipient within 24 hours, each between 70% and 100% of an approval threshold, together above it.

Note what the per-payment rules caught: only the first payment, as a first-time payee. After that the vendor was "known".

The fix, once you enforceโ€‹

A limit per recipient catches a split however it's sliced:

"limits": [
{ "name": "per-vendor-daily", "window": "24h", "sum": "amount", "max": 5000, "groupBy": "beneficiary.id", "onExceed": "require_approval" }
]

Now the second payment to the same vendor in a day goes to a person. Limits are counted on the server and reserved atomically, so concurrent payouts can't race past them either.

Hand it overโ€‹

The example also downloads a risk team pack: one printable file with the shadow findings, the policy, the approvals and the control mappings, with the signed reports inside it. It's the thing you send to risk, finance or your sponsor bank before you switch to enforce. They can check it with npx -p auditail-sdk auditail-verify risk-pack.html. See a sample.

More: shadow drift report ยท limits