Demo on synthetic data (Kaggle datasets named on each report). No real client data.

WoWyrdConfidential

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: 2026-10-01 to 2026-11-29 (daily periods). Cut-off: 2026-11-29 (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

59,161
Transactions reviewed
Transactions file, 2026-10-01 to 2026-11-29
42,310
Alerts
Rule-hit log, 2026-10-01 to 2026-11-29
2,078
Confirmed fraud
Labels file, known by 2026-11-29
35,155
False alarms
Rule-hit log and labels, mature hits, 2026-10-01 to 2026-11-29
168,992.00 USD
False-alarm cost (estimate)
Your unit costs, 2026-10-01 to 2026-11-29
75.6%
Share of fraud with a rule hit
Labels and rule-hit log, 2026-10-01 to 2026-11-29

Value in your own costs

In 2026-10-01 to 2026-11-29, false alarms took 3,515.5 analyst hours and cost 168,992.00 USD. Source: your unit costs and the rule-hit log.

4 of the top actions touch different rules. Together they remove 683 alerts and save 2,851.20 USD over the same period. They lose 21 caught fraud cases. This is a backtest on past data, not a forecast.

Charts

Alerts and confirmed fraud per period60 periods from 2026-10-01 to 2026-11-29. Alerts total 42,310; confirmed fraud total 2,078.Alerts82902026-10-01: 565 alerts2026-10-02: 632 alerts2026-10-03: 617 alerts2026-10-04: 604 alerts2026-10-05: 634 alerts2026-10-06: 659 alerts2026-10-07: 661 alerts2026-10-08: 648 alerts2026-10-09: 648 alerts2026-10-10: 704 alerts2026-10-11: 655 alerts2026-10-12: 642 alerts2026-10-13: 657 alerts2026-10-14: 662 alerts2026-10-15: 662 alerts2026-10-16: 653 alerts2026-10-17: 689 alerts2026-10-18: 698 alerts2026-10-19: 650 alerts2026-10-20: 666 alerts2026-10-21: 614 alerts2026-10-22: 669 alerts2026-10-23: 651 alerts2026-10-24: 624 alerts2026-10-25: 666 alerts2026-10-26: 650 alerts2026-10-27: 682 alerts2026-10-28: 655 alerts2026-10-29: 687 alerts2026-10-30: 647 alerts2026-10-31: 677 alerts2026-11-01: 671 alerts2026-11-02: 662 alerts2026-11-03: 745 alerts2026-11-04: 724 alerts2026-11-05: 749 alerts2026-11-06: 724 alerts2026-11-07: 759 alerts2026-11-08: 779 alerts2026-11-09: 712 alerts2026-11-10: 732 alerts2026-11-11: 744 alerts2026-11-12: 763 alerts2026-11-13: 768 alerts2026-11-14: 821 alerts2026-11-15: 757 alerts2026-11-16: 779 alerts2026-11-17: 793 alerts2026-11-18: 808 alerts2026-11-19: 773 alerts2026-11-20: 764 alerts2026-11-21: 769 alerts2026-11-22: 767 alerts2026-11-23: 762 alerts2026-11-24: 782 alerts2026-11-25: 756 alerts2026-11-26: 829 alerts2026-11-27: 791 alerts2026-11-28: 828 alerts2026-11-29: 771 alerts829Confirmed fraud5702026-10-01: 31 confirmed fraud2026-10-02: 35 confirmed fraud2026-10-03: 28 confirmed fraud2026-10-04: 39 confirmed fraud2026-10-05: 57 confirmed fraud2026-10-06: 46 confirmed fraud2026-10-07: 36 confirmed fraud2026-10-08: 40 confirmed fraud2026-10-09: 39 confirmed fraud2026-10-10: 34 confirmed fraud2026-10-11: 36 confirmed fraud2026-10-12: 45 confirmed fraud2026-10-13: 42 confirmed fraud2026-10-14: 35 confirmed fraud2026-10-15: 39 confirmed fraud2026-10-16: 28 confirmed fraud2026-10-17: 43 confirmed fraud2026-10-18: 30 confirmed fraud2026-10-19: 41 confirmed fraud2026-10-20: 33 confirmed fraud2026-10-21: 44 confirmed fraud2026-10-22: 43 confirmed fraud2026-10-23: 37 confirmed fraud2026-10-24: 42 confirmed fraud2026-10-25: 29 confirmed fraud2026-10-26: 43 confirmed fraud2026-10-27: 44 confirmed fraud2026-10-28: 27 confirmed fraud2026-10-29: 39 confirmed fraud2026-10-30: 34 confirmed fraud2026-10-31: 46 confirmed fraud2026-11-01: 38 confirmed fraud2026-11-02: 26 confirmed fraud2026-11-03: 30 confirmed fraud2026-11-04: 46 confirmed fraud2026-11-05: 34 confirmed fraud2026-11-06: 35 confirmed fraud2026-11-07: 35 confirmed fraud2026-11-08: 49 confirmed fraud2026-11-09: 33 confirmed fraud2026-11-10: 47 confirmed fraud2026-11-11: 44 confirmed fraud2026-11-12: 38 confirmed fraud2026-11-13: 47 confirmed fraud2026-11-14: 55 confirmed fraud2026-11-15: 39 confirmed fraud2026-11-16: 40 confirmed fraud2026-11-17: 46 confirmed fraud2026-11-18: 40 confirmed fraud2026-11-19: 30 confirmed fraud2026-11-20: 41 confirmed fraud2026-11-21: 44 confirmed fraud2026-11-22: 56 confirmed fraud2026-11-23: 0 confirmed fraud2026-11-24: 0 confirmed fraud2026-11-25: 0 confirmed fraud2026-11-26: 0 confirmed fraud2026-11-27: 0 confirmed fraud2026-11-28: 0 confirmed fraud2026-11-29: 0 confirmed fraud572026-10-012026-10-062026-10-112026-10-162026-10-212026-10-262026-10-312026-11-052026-11-102026-11-152026-11-202026-11-25
Alerts (bars) and confirmed fraud (dashed line) per period. Two scales: fraud is far smaller than alerts. Source: rule-hit log and labels, 2026-10-01 to 2026-11-29.
False-alarm cost by rule, top 8Money from 5+ different senders into one account within 5 days (fan-in) (Rule ID: tp_ffiec_fan_in_5_senders_5d): 89,991.33 USD; Transfer above 500 USD (Rule ID: tp_u21_transfer_over_500): 45,855.33 USD; Spending in the last 3 days doubles the monthly norm (Rule ID: tp_u21_hist_deviation_3d_31d): 17,449.47 USD; Money sent to 5+ different recipients within 5 days (fan-out) (Rule ID: tp_u21_fan_out_5_benef_5d): 8,782.13 USD; Single payment above 9,000 USD (Rule ID: tp_u21_large_txn_9k): 2,858.27 USD; 10+ mid-size payments in 5 days, over 20,000 USD in total (Rule ID: tp_u21_stats_10tx_1k3k_5d): 1,943.47 USD; Many small payments in, then sent out within a day (Rule ID: tp_ffiec_small_in_rapid_out_24h): 1,091.60 USD; Money in, then almost all of it sent on within 3 days (layering) (Rule ID: tp_u21_layering_10k_90pct_3d): 913.07 USDMoney from 5+ different senders into one account within 5 days (fan-in) (Rule ID: tp_ffiec_fan_in_5_senders_5d)Money from 5+ different senders into one account wi…Money from 5+ different senders into one account within 5 days (fan-in) (Rule ID: tp_ffiec_fan_in_5_senders_5d): 89,991.33 USD89,991.33 USDTransfer above 500 USD (Rule ID: tp_u21_transfer_over_500)Transfer above 500 USDTransfer above 500 USD (Rule ID: tp_u21_transfer_over_500): 45,855.33 USD45,855.33 USDSpending in the last 3 days doubles the monthly norm (Rule ID: tp_u21_hist_deviation_3d_31d)Spending in the last 3 days doubles the monthly normSpending in the last 3 days doubles the monthly norm (Rule ID: tp_u21_hist_deviation_3d_31d): 17,449.47 USD17,449.47 USDMoney sent to 5+ different recipients within 5 days (fan-out) (Rule ID: tp_u21_fan_out_5_benef_5d)Money sent to 5+ different recipients within 5 days…Money sent to 5+ different recipients within 5 days (fan-out) (Rule ID: tp_u21_fan_out_5_benef_5d): 8,782.13 USD8,782.13 USDSingle payment above 9,000 USD (Rule ID: tp_u21_large_txn_9k)Single payment above 9,000 USDSingle payment above 9,000 USD (Rule ID: tp_u21_large_txn_9k): 2,858.27 USD2,858.27 USD10+ mid-size payments in 5 days, over 20,000 USD in total (Rule ID: tp_u21_stats_10tx_1k3k_5d)10+ mid-size payments in 5 days, over 20,000 USD in…10+ mid-size payments in 5 days, over 20,000 USD in total (Rule ID: tp_u21_stats_10tx_1k3k_5d): 1,943.47 USD1,943.47 USDMany small payments in, then sent out within a day (Rule ID: tp_ffiec_small_in_rapid_out_24h)Many small payments in, then sent out within a dayMany small payments in, then sent out within a day (Rule ID: tp_ffiec_small_in_rapid_out_24h): 1,091.60 USD1,091.60 USDMoney in, then almost all of it sent on within 3 days (layering) (Rule ID: tp_u21_layering_10k_90pct_3d)Money in, then almost all of it sent on within 3 da…Money in, then almost all of it sent on within 3 days (layering) (Rule ID: tp_u21_layering_10k_90pct_3d): 913.07 USD913.07 USD
False-alarm cost per rule in USD. An alert hit by several rules shares its cost equally. Source: your unit costs, 2026-10-01 to 2026-11-29.

Top 5 actions

ActionTypeExpected effect (backtest)Confidence
REC-2fed05c6 Retire rule Many small payments in, then sent out within a day: 2.9% of its 621 alerts with a known outcome were fraud
tp_ffiec_small_in_rapid_out_24h: Finds an account that collects several small payments and passes most of the money on at once.
Retire the rule1 fewer alerts, 0 caught fraud cases lost, 4.80 USD saved (estimate)high
REC-2a81ffc0 Retire rule Money in, then almost all of it sent on within 3 days (layering): 2.1% of its 575 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 rule0 fewer alerts, 0 caught fraud cases lost, 0.00 USD saved (estimate)high
REC-8132599b Retire rule 10+ mid-size payments in 5 days, over 20,000 USD in total: 0.5% of its 1,042 alerts with a known outcome were fraud
tp_u21_stats_10tx_1k3k_5d: Finds a burst of many similar mid-size payments that add up to a large total.
Retire the rule1 fewer alerts, 0 caught fraud cases lost, 4.80 USD saved (estimate)high
REC-80e229b9 Retire rule Money sent to 5+ different recipients within 5 days (fan-out): 4.0% of its 3,817 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 rule681 fewer alerts, 21 caught fraud cases lost, 2,841.60 USD saved (estimate)medium
REC-470735c7 Add a rule for: Gambling winnings arrive with no deposits, then card transfers followAdd a missing fraud typeNo effect estimate.medium

Effects come from a backtest on 2026-10-01 to 2026-11-29. 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 types present in your labelsAccount takeover: 535 caught, 163 missed; Purchase scam: 210 caught, 329 missed; Safe-account scam: 330 caught, 1 missed; Investment scam: 285 caught, 14 missed; Invoice redirection: 210 caught, 0 missed; Money mule: 0 caught, 1 missedAccount takeoverAccount takeoverAccount takeover: 535 caughtAccount takeover: 163 missed535 caught, 163 missedPurchase scamPurchase scamPurchase scam: 210 caughtPurchase scam: 329 missed210 caught, 329 missedSafe-account scamSafe-account scamSafe-account scam: 330 caughtSafe-account scam: 1 missed330 caught, 1 missedInvestment scamInvestment scamInvestment scam: 285 caughtInvestment scam: 14 missed285 caught, 14 missedInvoice redirectionInvoice redirectionInvoice redirection: 210 caught210 caught, 0 missedMoney muleMoney muleMoney mule: 1 missed0 caught, 1 missed
Labelled fraud cases per type. Blue: a rule fired on the payment. Orange: no rule fired. Source: labels file and rule-hit log, labels known by the cut-off.
Fraud typeLabelled casesCaughtMissedWoWyrd
Account takeover698535163WoWyrd rule: planned
Purchase scam539210329WoWyrd rule: planned
Safe-account scam3313301WoWyrd rule: planned
Investment scam29928514WoWyrd rule: planned
Invoice redirection2102100WoWyrd rule: planned
Money mule101WoWyrd 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.

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

This part measures incoming payments and three money-mule signs on your own transactions file, with our reference set's limits. FCA CP26/38, a consultation draft, names a focus on outgoing payments only as poor practice and lists money-mule signs. An account with a sign is a lead for your analysts, not a finding about the account holder. The figures give no verdict on your process.

A checklist item asks you to monitor incoming as well as outgoing payments. These figures are data next to your own statement on it; they do not change its result.

Your rule log has 91.3% of incoming credits; a rule fired on 0.0%. For outgoing payments: 100.0% and 71.5%.

PaymentsIn your fileIn your rule logA rule fired
Incoming credits2321 (91.3%)0 (0.0%)
Outgoing payments59,13859,138 (100.0%)42,310 (71.5%)
Money-mule signOur limitsAccountsA rule fired during the signA rule fired laterToo recent for labelsMule labelAny fraud labelYour matched rule
Many sendersmore than 2 different senders within 30 days5000fewer than 5fewer than 5—
Money out soon after it came inat least 80% of the money that came in within 30 minutes sent out in the same time1000not shown: it would reveal a count under 5not shown: it would reveal a count under 5—
New account paid by several peoplean account younger than 7 days, paid by at least 2 different senders within 30 days1000not shown: it would reveal a count under 5not shown: it would reveal a count under 5—

The limits are our reference set's starting values, not tuned to your data. Reference set v0.7.0, from the reference catalogue that comes with this collector, SHA-256 of the catalogue file 6a5d70c1fdfa3ef833e98cea246df506db35d699ec072159aa0ec0ba2bd04d88.

Each sign is measured on your data with our reference set's limits, over exact time windows. A rule engine that keeps its counts in another way can find other accounts.

Not in this review: the flow of money between accounts (it needs the links between your accounts), and other money-mule signs such as cash withdrawals, dormant accounts, changed login details, new devices and money moved abroad. They need data that this file does not hold.

New accounts and onboarding rating

This part shows fraud and alerts by account age and by your onboarding risk rating, on your own transactions file. FCA CP26/38, a consultation draft, names relying on transaction monitoring alone as poor practice and lists thresholds set without onboarding data as poor practice. The figures show what happened after onboarding. They do not check your onboarding checks, and they give no verdict on your process.

Each figure counts payments, not accounts: an account with many payments weighs more than one with few. A label count from 1 to 4, or one that would reveal such a count, is not shown.

By account age at the payment

By your onboarding risk rating

The rating is taken as your transactions file records it on each payment; this review cannot tell an onboarding rating from a later re-rating.

In this data, the fraud rate is not higher in each riskier band of your onboarding rating. This is a measurement on your payments, not a finding about your onboarding checks. This shows false alarms by your onboarding rating; it does not show why.

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)ResultSource statusAs ofOfficial 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 filesin force since 20.05.2026; 6 months to comply (about 20.11.2026)2026-11-11bank.gov.ua
Review every rule at least monthly by back-testing it.Partly metdraft (NBU draft resolution on control of payment operations, published 2026-07-17; not law)2026-11-11bank.gov.ua
Metric 1: compare how often each rule fired with how many payments were actually stopped.Partly metdraft (NBU draft resolution on control of payment operations, published 2026-07-17; not law)2026-11-11bank.gov.ua
Metric 2: share of fraud value that was prevented, out of all fraud value.Partly metdraft (NBU draft resolution on control of payment operations, published 2026-07-17; not law)2026-11-11bank.gov.ua
Set rule-effectiveness thresholds in writing. A rule under its threshold gets an immediate review.Gapdraft (NBU draft resolution on control of payment operations, published 2026-07-17; not law)2026-11-11bank.gov.ua
Record a review decision for every rule: keep, adjust or cancel.Partly metdraft (NBU draft resolution on control of payment operations, published 2026-07-17; not law)2026-11-11bank.gov.ua
Have evidence ready for a supervisor: documents, rules, risk markers.Partly metdraft (NBU draft resolution on control of payment operations, published 2026-07-17; not law)2026-11-11bank.gov.ua
Show the acquirer's full name before an online payment; receipts show payee, commission, purpose and category code.Not measurable from these filesin force since 20.05.2026; 6 months to comply (about 20.11.2026)2026-11-11bank.gov.ua
Reconcile payment operations every day.Partly metdraft (NBU draft resolution on control of payment operations, published 2026-07-17; not law)2026-11-11bank.gov.ua
Acquiring for natural persons only for allowed categories, with the required data passed to the issuer.Not measurable from these filesin force since 20.05.2026; 6 months to comply (about 20.11.2026)2026-11-11bank.gov.ua
Non-bank providers that acquire payments need an authorisation; the sanctions pause has ended.Not measurable from these filesin force; grace period ended 02.09.20262026-11-11bank.gov.ua
Remote verification of natural persons uses the updated procedure with credit-bureau data.Not measurable from these filesin force since 10.10.2026; 3 months to align internal procedures (about 10.01.2027)2026-11-11bank.gov.ua
Reports to the State Financial Monitoring Service go only through the e-cabinet, with numbered registers.Not measurable from these filesin force since 10.10.2026; 3 months to align internal procedures (about 10.01.2027)2026-11-11bank.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 filesadopted by the Rada 28.10.2026; presidential signature not confirmed2026-11-11itd.rada.gov.ua

Checks per EU requirements

Requirement (our wording)ResultSource statusAs ofOfficial 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 filesagreed, not adopted (EU Payment Services Regulation; adoption expected by 12.2026)2026-11-11oeil.europarl.europa.eu

Checks per UK requirements

Requirement (our wording)ResultSource statusAs ofOfficial source
A claim may carry an excess of up to 100 GBP, never for vulnerable customers.Not measurable from these filesin force2026-11-11psr.org.uk
Test and review rules; a poorly calibrated rule set the firm cannot explain is poor practice.Partly metguidance in force2026-11-11fca.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)ResultSource statusAs ofOfficial source
Analyse scenarios, rules and thresholds on an ongoing basis.Partly metin force2026-11-11dfs.ny.gov
Test rules before and after they go live.Not measurable from these filesin force2026-11-11dfs.ny.gov
Tune and validate monitoring; justify each threshold.Partly metguidance2026-11-11bsaaml.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.

Account takeover ATO
A criminal gets into a customer's account and sends money out of it.
Investment scam INVEST
The customer is talked into paying into an investment that does not exist.
Invoice redirection INVOICE
A false or changed invoice makes the customer pay a criminal instead of the real supplier.
Money mule MULE
An account receives stolen money and passes it on for someone else.
Purchase scam PURCHASE
The customer pays for goods or services that never arrive.
Safe-account scam SAFE
A caller who poses as the bank tells the customer to move money to an account the caller controls.