WoWyrd · Rule review
Rule review: extended management report
Prepared for Demo client with 3 business lines (synthetic)
Client: Demo client with 3 business lines (synthetic). Data: 2022-09-01 to 2022-09-18 (daily periods). Cut-off: 2022-09-18 (set for this run). Generated: 2026-11-20 10:02 UTC.
Internal report. Do not share it outside your firm.
Internal report. Do not share it outside your firm.
This is the extended management report. The short management report is management.html; the technical report is technical.html.
Headline numbers
Value in your own costs
In 2022-09-01 to 2022-09-18, false alarms took 5,030.2 analyst hours and cost 249,889.60 USD. Source: your unit costs and the rule-hit log.
5 of the top actions touch different rules. Together they remove 7,896 alerts and save 37,704.00 USD over the same period. They lose 41 caught fraud cases. This is a backtest on past data, not a forecast.
Charts
Top 5 actions
| Action | Type | Expected effect (backtest) | Confidence |
|---|---|---|---|
| REC-80e229b9 Retire rule Money sent to 5+ different recipients within 5 days (fan-out): 0.5% of its 39,145 alerts with a known outcome were fraud tp_u21_fan_out_5_benef_5d: Finds one sender spreading money to many receivers in a short time. | Retire the rule | 7,624 fewer alerts, 40 caught fraud cases lost, 36,403.20 USD saved (estimate) | medium |
| REC-0ee48cf1 Retire rule More than 2 wire transfers in 7 days: 0.0% of its 528 alerts with a known outcome were fraud tp_u21_wire_count_gt2_7d: Finds a sender who uses wire transfers unusually often. | Retire the rule | 132 fewer alerts, 0 caught fraud cases lost, 633.60 USD saved (estimate) | high |
| REC-2266ce85 Retire rule 20+ small payments in 5 days, over 20,000 USD in total: 0.6% of its 324 alerts with a known outcome were fraud tp_u21_stats_20tx_0_1k_5d: Finds many small payments that together move a large sum. | Retire the rule | 29 fewer alerts, 0 caught fraud cases lost, 139.20 USD saved (estimate) | high |
| REC-2a81ffc0 Retire rule Money in, then almost all of it sent on within 3 days (layering): 0.9% of its 13,477 alerts with a known outcome were fraud tp_u21_layering_10k_90pct_3d: Finds an account that receives a large sum and quickly passes nearly all of it to other people. | Retire the rule | 109 fewer alerts, 1 caught fraud cases lost, 518.40 USD saved (estimate) | medium |
| REC-fdf9b021 Retire rule Wire transfers above 4,999 USD in total within 7 days: 0.0% of its 368 alerts with a known outcome were fraud tp_u21_wire_total_gt4999_7d: Finds a sender who moves a large total by wire in one week. | Retire the rule | 2 fewer alerts, 0 caught fraud cases lost, 9.60 USD saved (estimate) | high |
Effects come from a backtest on 2022-09-01 to 2022-09-18. Selective labels: a declined payment has no outcome, so fraud a rule stopped by declining is not in "caught fraud cases lost". The technical report gives the evidence and caveats for each action. A rule name links to its entry in the rule glossary. Each action has a reference (REC-…). Quote this reference in your change record.
What changed since the previous report
No previous report was given, so this report is treated as the first one. There is nothing to compare with yet. The next run can compare with this one.
Coverage by fraud type
Fraud types present in your labels
| Fraud type | Labelled cases | Caught | Missed | WoWyrd |
|---|---|---|---|---|
| Spread, then collect | 98 | 97 | 1 | WoWyrd rule available: Money leaves soon after it arrives |
| Layers of accounts | 86 | 83 | 3 | WoWyrd rule: planned |
| Collect, then spread | 84 | 83 | 1 | WoWyrd rule available: Money leaves soon after it arrives; Many small credits, then one large payout |
| One out to many (fan-out) | 83 | 83 | 0 | WoWyrd rule available: One account pays many different payees |
| Many into one (fan-in) | 54 | 52 | 2 | WoWyrd rule available: Many senders pay one account; One payee shared by several customers |
| Two groups paying each other | 49 | 47 | 2 | WoWyrd rule: planned |
| Money in a circle | 44 | 43 | 1 | WoWyrd rule: planned |
| Random hops | 41 | 40 | 1 | WoWyrd rule: planned |
| Type not given | 428 | 400 | 28 | WoWyrd rule: planned |
Not in this dataset, so it cannot be measured here
Your labels hold no case of these types, so this data cannot show whether your rules catch them. This is not a gap in your rules.
- One user holds many more accounts or cards than similar users
WoWyrd rule: planned. - One type of operation makes up an unusual share of a user's activity
WoWyrd rule available: One type of operation dominates an account. - Many operations of one type in a short time, incoming or outgoing
WoWyrd rule available: Many requests from one account in an hour, then a payout; A burst of operations of one type. - Balance stays low although large amounts pass through
WoWyrd rule available: Large amounts pass through an account that keeps a low balance. - Large loans are taken and repaid again and again
WoWyrd rule available: Large loans taken and repaid again and again. - Gambling winnings arrive with no deposits, then card transfers follow
WoWyrd rule available: Gambling winnings with no gambling deposits. - Regular transfers to a personal account look like business activity
WoWyrd rule available: A personal account paid by many payers. - A new merchant's volume is far above similar merchants, then the merchant closes
WoWyrd rule available: A merchant with little history suddenly busy. - Merchant account inflows mirror its outflows (transit)
WoWyrd rule available: A business account pays out almost all it receives. - Payment purposes do not fit the merchant's category code
WoWyrd rule available: Payment purpose does not fit the merchant's business; Card payment to a person without category or purpose. - Contacts, device, apps, IMEI, operating system or network address change often
WoWyrd rule available: Payout right after an email or phone change; One session from several network addresses; One account used from many devices. - One device fingerprint is used by unrelated users
WoWyrd rule available: One device used by several customers. - Two operations are too far apart to travel between in the time
WoWyrd rule available: Locations too far apart for the time between them. - A new account gets large or many credits soon after opening
WoWyrd rule available: A new account receives a large credit; A new account paid by several people. - A dormant account suddenly moves large amounts
WoWyrd rule: planned. - Repeated amounts just under a reporting or limit threshold
WoWyrd rule available: Payments just under a limit; Many small payments from one account add up to a large sum; Many small payments to one payee add up to a large sum. - Repeated round amounts with no business reason
WoWyrd rule available: Several payments in large round amounts. - Outgoing payments per hour above the customer's usual level
WoWyrd rule available: More payments in an hour than the customer usually makes; Many requests from one account in an hour, then a payout. - A large first payment to a payee never paid before
WoWyrd rule available: A large payment to a payee added just before. - Many senders' accounts share one beneficiary
WoWyrd rule available: One payee shared by several customers. - An amount far above the customer's own history
WoWyrd rule available: A payment far above the customer's usual amount. - Credits from many different banks into one account
WoWyrd rule available: Credits from many different banks into one account. - Transfers to or from high-risk jurisdictions
WoWyrd rule available: A payment to or from a high-risk country. - Cash withdrawn right after a credit arrives
WoWyrd rule available: Cash taken out soon after money arrives. - The payee name does not match and the payment still goes
WoWyrd rule available: Paid although the payee name did not match. - The payment reference mentions investment, crypto or a 'safe account'
WoWyrd rule available: The payment reference uses common scam wording. - An older customer suddenly sends a large amount to a new payee
WoWyrd rule available: An older customer sends a large amount to a new payee. - Activity at hours unusual for the customer
WoWyrd rule available: Activity at an hour unusual for the customer.
New in our reference set since your last report
Our reference set: version v0.7.0, published 2026-11-18 (built into this collector).
This is the first report with a record of our reference set. The next report lists what is new since this one.
Incoming payments and money-mule signs
Incoming payments not measured: your transactions file has no direction column (for example direction, with values such as in and out).
Requirements changed since the last review
Your rules are mapped to current requirements. We flag when a new requirement affects them. We follow official publications of regulators in Ukraine, the EU, the UK and the US.
Not legal advice. This report maps your rules to requirements, in our own short wording. It is not legal advice. You decide how you comply.
Requirements library read on 2026-11-11. No change file was given for this run, so no changed requirement is listed here.
Requirements still open since the previous report
No previous report was given, so this report is treated as the first one. There is nothing to compare with yet. The next run can compare with this one.
Requirements that showed a gap are followed up only when the two reports compare.
Not legal advice. Your compliance team decides how a requirement applies to you. Public cases show how regulators have treated the same kind of gap; they do not predict an outcome for you.
Regulatory checks by regulator
Not legal advice. This report maps your rules to requirements, in our own short wording. It is not legal advice. You decide how you comply.
Regulatory statuses as of 2026-11-11 (library date). Check them again before you rely on this report.
Grouped by regulator. Our own short wording, not the regulator's text. The technical report gives each finding and its evidence.
Checks per NBU requirements
Rows citing the NBU draft of 17.07.2026 — draft, not in force: its text can change before adoption. Resolutions 51, 54 and 116 are in force. Bill 16013 is a Ukrainian bill, shown here with its status.
| Requirement (our wording) | Result | Source status | As of | Official source |
|---|---|---|---|---|
| The acquirer passes payee (merchant) name and category code to the issuer. Check that these fields are filled in your data. Most time-relevant item: the deadline is about 20.11.2026. | Not measurable from these files | in force since 20.05.2026; 6 months to comply (about 20.11.2026) | 2026-11-11 | bank.gov.ua |
| Review every rule at least monthly by back-testing it. | Gap | draft (NBU draft resolution on control of payment operations, published 2026-07-17; not law) | 2026-11-11 | bank.gov.ua |
| Metric 1: compare how often each rule fired with how many payments were actually stopped. | Partly met | draft (NBU draft resolution on control of payment operations, published 2026-07-17; not law) | 2026-11-11 | bank.gov.ua |
| Metric 2: share of fraud value that was prevented, out of all fraud value. | Partly met | draft (NBU draft resolution on control of payment operations, published 2026-07-17; not law) | 2026-11-11 | bank.gov.ua |
| Set rule-effectiveness thresholds in writing. A rule under its threshold gets an immediate review. | Gap | draft (NBU draft resolution on control of payment operations, published 2026-07-17; not law) | 2026-11-11 | bank.gov.ua |
| Record a review decision for every rule: keep, adjust or cancel. | Partly met | draft (NBU draft resolution on control of payment operations, published 2026-07-17; not law) | 2026-11-11 | bank.gov.ua |
| Have evidence ready for a supervisor: documents, rules, risk markers. | Partly met | draft (NBU draft resolution on control of payment operations, published 2026-07-17; not law) | 2026-11-11 | bank.gov.ua |
| Show the acquirer's full name before an online payment; receipts show payee, commission, purpose and category code. | Not measurable from these files | in force since 20.05.2026; 6 months to comply (about 20.11.2026) | 2026-11-11 | bank.gov.ua |
| Reconcile payment operations every day. | Partly met | draft (NBU draft resolution on control of payment operations, published 2026-07-17; not law) | 2026-11-11 | bank.gov.ua |
| Acquiring for natural persons only for allowed categories, with the required data passed to the issuer. | Not measurable from these files | in force since 20.05.2026; 6 months to comply (about 20.11.2026) | 2026-11-11 | bank.gov.ua |
| Non-bank providers that acquire payments need an authorisation; the sanctions pause has ended. | Not measurable from these files | in force; grace period ended 02.09.2026 | 2026-11-11 | bank.gov.ua |
| Remote verification of natural persons uses the updated procedure with credit-bureau data. | Not measurable from these files | in force since 10.10.2026; 3 months to align internal procedures (about 10.01.2027) | 2026-11-11 | bank.gov.ua |
| Reports to the State Financial Monitoring Service go only through the e-cabinet, with numbered registers. | Not measurable from these files | in force since 10.10.2026; 3 months to align internal procedures (about 10.01.2027) | 2026-11-11 | bank.gov.ua |
| Passing cards, account access or payment data to fraudsters becomes a crime. Detect and restrict accounts used as drops. | Not measurable from these files | adopted by the Rada 28.10.2026; presidential signature not confirmed | 2026-11-11 | itd.rada.gov.ua |
Checks per EU requirements
| Requirement (our wording) | Result | Source status | As of | Official source |
|---|---|---|---|---|
| When a payee name check fails because of the payee's provider, that provider compensates the payer's provider. Keep evidence of the name check on received transfers. | Not measurable from these files | agreed, not adopted (EU Payment Services Regulation; adoption expected by 12.2026) | 2026-11-11 | oeil.europarl.europa.eu |
Checks per UK requirements
| Requirement (our wording) | Result | Source status | As of | Official source |
|---|---|---|---|---|
| A claim may carry an excess of up to 100 GBP, never for vulnerable customers. | Not measurable from these files | in force | 2026-11-11 | psr.org.uk |
| Test and review rules; a poorly calibrated rule set the firm cannot explain is poor practice. | Partly met | guidance in force | 2026-11-11 | fca.org.uk |
Checks per US requirements (FinCEN, NYDFS, FFIEC, Nacha, Federal Reserve)
FinCEN and Nacha items are not checked from your files in this run; the rows below are NYDFS and FFIEC items.
| Requirement (our wording) | Result | Source status | As of | Official source |
|---|---|---|---|---|
| Analyse scenarios, rules and thresholds on an ongoing basis. | Partly met | in force | 2026-11-11 | dfs.ny.gov |
| Test rules before and after they go live. | Not measurable from these files | in force | 2026-11-11 | dfs.ny.gov |
| Tune and validate monitoring; justify each threshold. | Partly met | guidance | 2026-11-11 | bsaaml.ffiec.gov |
Fraud types in plain words
Each fraud type named in your labels, in one sentence. The word in small grey text is the label as your file gives it.
- Collect, then spread GATHER-SCATTER
- Money from many accounts is collected in one, then sent on to many others.
- Layers of accounts STACK
- Money passes through several layers of accounts in a row, so its origin is hard to trace.
- Many into one (fan-in) FAN-IN
- Many accounts send money into one account, which collects it.
- Money in a circle CYCLE
- Money passes along a chain of accounts and comes back to the account it left.
- One out to many (fan-out) FAN-OUT
- One account sends money out to many accounts, so it spreads thin.
- Random hops RANDOM
- Money hops between accounts along an irregular path with no fixed shape.
- Spread, then collect SCATTER-GATHER
- Money is split across many accounts, then collected again in one account.
- Two groups paying each other BIPARTITE
- One group of accounts pays a second group, with many payments crossing between them.
- Type not given no type
- Fraud labels in your file that do not say which kind of fraud it was.