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 its own rule file (own-rules, synthetic)

Client: Demo client with its own rule file (own-rules, synthetic). Data: 2026-08 to 2026-10 (monthly periods). Cut-off: 2026-10-01 (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

1,950
Transactions reviewed
Transactions file, 2026-08 to 2026-10
723
Alerts
Rule-hit log, 2026-08 to 2026-10
103
Confirmed fraud
Labels file, known by 2026-10-01
450
False alarms
Rule-hit log and labels, mature hits, 2026-08 to 2026-10
2,328.00 USD
False-alarm cost (estimate)
Your unit costs, 2026-08 to 2026-10
79.6%
Share of fraud with a rule hit
Labels and rule-hit log, 2026-08 to 2026-10

Value in your own costs

In 2026-08 to 2026-10, false alarms took 45.0 analyst hours and cost 2,328.00 USD. Source: your unit costs and the rule-hit log.

Charts

Alerts and confirmed fraud per period3 periods from 2026-08 to 2026-10. Alerts total 723; confirmed fraud total 103.Alerts38502026-08: 385 alerts2026-09: 328 alerts2026-10: 10 alerts385Confirmed fraud7402026-08: 74 confirmed fraud2026-09: 29 confirmed fraud2026-10: 0 confirmed fraud742026-082026-092026-10
Alerts (bars) and confirmed fraud (dashed line) per period. Two scales: fraud is far smaller than alerts. Source: rule-hit log and labels, 2026-08 to 2026-10.
False-alarm cost by rule, top 8tp_u21_transfer_over_500 (Rule ID: tp_u21_transfer_over_500) (agreement with your engine's log: 100%): 2,092.07 USD; tp_u21_large_txn_9k (Rule ID: tp_u21_large_txn_9k) (agreement with your engine's log: 88%): 90.93 USD; tp_u21_wire_total_gt4999_7d (Rule ID: tp_u21_wire_total_gt4999_7d) (agreement with your engine's log: 100%): 83.67 USD; tp_ffiec_fan_in_5_senders_5d (Rule ID: tp_ffiec_fan_in_5_senders_5d) (agreement with your engine's log: 100%): 23.20 USD; tp_u21_fan_out_5_benef_5d (Rule ID: tp_u21_fan_out_5_benef_5d) (agreement with your engine's log: 100%): 20.20 USD; tp_u21_wire_count_gt2_7d (Rule ID: tp_u21_wire_count_gt2_7d) (agreement with your engine's log: 100%): 17.93 USDtp_u21_transfer_over_500 (Rule ID: tp_u21_transfer_over_500) (agreement with your engine's log: 100%)tp_u21_transfer_over_500tp_u21_transfer_over_500 (Rule ID: tp_u21_transfer_over_500) (agreement with your engine's log: 100%): 2,092.07 USD2,092.07 USDtp_u21_large_txn_9k (Rule ID: tp_u21_large_txn_9k) (agreement with your engine's log: 88%)tp_u21_large_txn_9ktp_u21_large_txn_9k (Rule ID: tp_u21_large_txn_9k) (agreement with your engine's log: 88%): 90.93 USD90.93 USDtp_u21_wire_total_gt4999_7d (Rule ID: tp_u21_wire_total_gt4999_7d) (agreement with your engine's log: 100%)tp_u21_wire_total_gt4999_7dtp_u21_wire_total_gt4999_7d (Rule ID: tp_u21_wire_total_gt4999_7d) (agreement with your engine's log: 100%): 83.67 USD83.67 USDtp_ffiec_fan_in_5_senders_5d (Rule ID: tp_ffiec_fan_in_5_senders_5d) (agreement with your engine's log: 100%)tp_ffiec_fan_in_5_senders_5dtp_ffiec_fan_in_5_senders_5d (Rule ID: tp_ffiec_fan_in_5_senders_5d) (agreement with your engine's log: 100%): 23.20 USD23.20 USDtp_u21_fan_out_5_benef_5d (Rule ID: tp_u21_fan_out_5_benef_5d) (agreement with your engine's log: 100%)tp_u21_fan_out_5_benef_5dtp_u21_fan_out_5_benef_5d (Rule ID: tp_u21_fan_out_5_benef_5d) (agreement with your engine's log: 100%): 20.20 USD20.20 USDtp_u21_wire_count_gt2_7d (Rule ID: tp_u21_wire_count_gt2_7d) (agreement with your engine's log: 100%)tp_u21_wire_count_gt2_7dtp_u21_wire_count_gt2_7d (Rule ID: tp_u21_wire_count_gt2_7d) (agreement with your engine's log: 100%): 17.93 USD17.93 USD
False-alarm cost per rule in USD. An alert hit by several rules shares its cost equally. Source: your unit costs, 2026-08 to 2026-10. Imported rules in this chart: tp_u21_transfer_over_500 tp_u21_transfer_over_500 (agreement with your engine's log: 100%); tp_u21_large_txn_9k tp_u21_large_txn_9k (agreement with your engine's log: 88%); tp_u21_wire_total_gt4999_7d tp_u21_wire_total_gt4999_7d (agreement with your engine's log: 100%); tp_ffiec_fan_in_5_senders_5d tp_ffiec_fan_in_5_senders_5d (agreement with your engine's log: 100%); tp_u21_fan_out_5_benef_5d tp_u21_fan_out_5_benef_5d (agreement with your engine's log: 100%); tp_u21_wire_count_gt2_7d tp_u21_wire_count_gt2_7d (agreement with your engine's log: 100%).

Top 5 actions

ActionTypeExpected effect (backtest)Confidence
REC-16a49a98 Add a rule for: Gambling winnings arrive with no deposits, then card transfers followAdd a missing fraud typeNo effect estimate.low
REC-fc5701c9 Add a rule for: Large loans are taken and repaid again and againAdd a missing fraud typeNo effect estimate.low
REC-5ff2bbff Add a rule for: One type of operation makes up an unusual share of a user's activityAdd a missing fraud typeNo effect estimate.low
REC-8078ec06 Add a rule for: Payment purposes do not fit the merchant's category codeAdd a missing fraud typeNo effect estimate.medium
REC-05f946b2 Add a rule for: Regular transfers to a personal account look like business activityAdd a missing fraud typeNo effect estimate.low

Effects come from a backtest on 2026-08 to 2026-10. 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.

Your imported rules

5 of 9 imported rules replayed and agreed with your engine's log; 4 did not agree, so no what-if is shown for them.

Your ruleActionStatusAgreementLogged hitsReplay hits
Single transfer above 9000 tp_u21_large_txn_9k (agreement with your engine's log: 88%)reviewBelow the agreement floor88%8090
Transfer above 500 tp_u21_transfer_over_500 (agreement with your engine's log: 100%)reviewAgrees100%701701
One sender pays five or more receivers in five days tp_u21_fan_out_5_benef_5d (agreement with your engine's log: 100%)alertAgrees100%2525
More than two wires from one sender in a week tp_u21_wire_count_gt2_7d (agreement with your engine's log: 100%)reviewAgrees100%2222
Wire total from one sender in a week tp_u21_wire_total_gt4999_7d (agreement with your engine's log: 100%)declineAgrees100%8989
Five or more senders pay one account in five days tp_ffiec_fan_in_5_senders_5d (agreement with your engine's log: 100%)reviewAgrees100%2424
Device risk score from the vendor R-509 (agreement: not replayable)reviewNot replayable—0—
One device used by several customers R-610 (agreement: not replayable)alertNot replayable—0—
Very large transfer after a quiet spell R-900 (agreement: cannot be compared)reviewCannot be compared—045

For a replayed rule, both counts leave out its warm-up rows. For a rule that is not replayed, the logged hits are its hits in your whole log.

What-if on past data

Backtest on past data, not a forecast. A changed threshold can change how fraudsters behave.

A payment that was declined has no outcome. Hits on declined payments are counted as 'outcome unknown', not as caught or as false alarms. A rule that declines payments hides the fraud it stopped, so 'caught' can be lower than the real number.

This collector changes no live rule. A threshold change goes through your own change and approval process.

Format of the rule file: Download an example rule file (JSON, with a note on every key; replace its example consent line before you use it).

Side by side with WoWyrd rules

Each of your rules next to the WoWyrd rule for the same fraud type and the requirement it relates to. A link found by the rule's name says "please check".

Your ruleFraud type and WoWyrd ruleRequirement it relates to
Single transfer above 9000 tp_u21_large_txn_9k (agreement with your engine's log: 88%)
Trigger: amount is at least 9000. Action: review. Logged hits: 80. Replay: Below the agreement floor.
No fraud type in our library matches this rule. Add a typology ID to the rule file.No requirement in our library relates to this rule.
Transfer above 500 tp_u21_transfer_over_500 (agreement with your engine's log: 100%)
Trigger: amount is more than 500. Action: review. Logged hits: 701. Replay: Agrees.
No fraud type in our library matches this rule. Add a typology ID to the rule file.No requirement in our library relates to this rule.
One sender pays five or more receivers in five days tp_u21_fan_out_5_benef_5d (agreement with your engine's log: 100%)
Trigger: the number of different receiver id values with the same sender id in 5 days is at least 5. Action: alert. Logged hits: 25. Replay: Agrees.
One payer sends to far more payees than similar payers
WoWyrd rule available: One account pays many different payees; numbers: not run on your data
NBU draft, Annex 2 sign. Status: draft (NBU draft resolution on control of payment operations, published 2026-07-17; not law); as of 2026-11-11. bank.gov.ua
More than two wires from one sender in a week tp_u21_wire_count_gt2_7d (agreement with your engine's log: 100%)
Trigger: channel is "wire" and the number of transactions with the same sender id in 7 days is more than 2, counting only transactions where channel is "wire". Action: review. Logged hits: 22. Replay: Agrees.
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; numbers: not run on your data
NBU draft, Annex 2 sign. Status: draft (NBU draft resolution on control of payment operations, published 2026-07-17; not law); as of 2026-11-11. bank.gov.ua
Wire total from one sender in a week tp_u21_wire_total_gt4999_7d (agreement with your engine's log: 100%)
Trigger: channel is "wire" and the total amount with the same sender id in 7 days is more than 4999, counting only transactions where channel is "wire". Action: decline. Logged hits: 95. Replay: Agrees.
No fraud type in our library matches this rule. Add a typology ID to the rule file.No requirement in our library relates to this rule.
Five or more senders pay one account in five days tp_ffiec_fan_in_5_senders_5d (agreement with your engine's log: 100%)
Trigger: the number of different sender id values with the same receiver id in 5 days is at least 5. Action: review. Logged hits: 24. Replay: Agrees.
matched by name: please check
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; numbers: not run on your data
Many payers send to one payee, far more than for similar payees
WoWyrd rule available: Many senders pay one account; One payee shared by several customers; numbers: not run on your data
Many different senders pay one account within a short time
WoWyrd rule available: Many senders pay one account; numbers: not run on your data
matched by name: please check
NBU draft, Annex 2 sign. Status: draft (NBU draft resolution on control of payment operations, published 2026-07-17; not law); as of 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. Status: adopted by the Rada 28.10.2026; presidential signature not confirmed; as of 2026-11-11. itd.rada.gov.ua
FinCEN advisories and alerts (money-mule red flags). Status: public red-flag references; own wording; as of 2026-11-11. No official page confirmed
FFIEC BSA/AML Examination Manual, Appendix F (red flags). Status: public red-flag references; own wording; as of 2026-11-11. No official page confirmed
Unit21 recommended rules (2024 public copies). Status: public red-flag references; own wording; as of 2026-11-11. No official page confirmed
Monitor both outgoing and incoming payments for fraud. Status: agreed, not adopted (EU Payment Services Regulation; adoption expected by 12.2026); as of 2026-11-11. oeil.europarl.europa.eu
Sending and receiving providers share APP scam refunds; a claim has a maximum level. Status: in force since 07.10.2024; as of 2026-11-11. psr.org.uk
Monitor incoming as well as outgoing payments, with money-mule signs. Status: consultation; comments close 24.12.2026; as of 2026-11-11. fca.org.uk
Receiving banks monitor incoming credits, including new, dormant and mule accounts. Status: in force: phase 1 20.03.2026, phase 2 22.06.2026; as of 2026-11-11. nacha.org
Device risk score from the vendor R-509 (agreement: not replayable)
Trigger: not expressible in the rule file. Action: review. Logged hits: 0. Replay: Not replayable.
matched by name: please check
One device fingerprint is used by unrelated users
WoWyrd rule available: One device used by several customers; numbers: not run on your data
matched by name: please check
NBU draft, Annex 2 sign. Status: draft (NBU draft resolution on control of payment operations, published 2026-07-17; not law); as of 2026-11-11. bank.gov.ua
One device used by several customers R-610 (agreement: not replayable)
Trigger: the number of different sender id values with the same device id in 1 day is at least 3. Action: alert. Logged hits: 0. Replay: Not replayable.
One device fingerprint is used by unrelated users
WoWyrd rule available: One device used by several customers; numbers: not run on your data
NBU draft, Annex 2 sign. Status: draft (NBU draft resolution on control of payment operations, published 2026-07-17; not law); as of 2026-11-11. bank.gov.ua
Very large transfer after a quiet spell R-900 (agreement: cannot be compared)
Trigger: amount is more than 20000. Action: review. Logged hits: 0. Replay: Cannot be compared.
A dormant account suddenly moves large amounts
WoWyrd rule: planned
FFIEC BSA/AML Examination Manual, Appendix F (red flags). Status: public red-flag references; own wording; as of 2026-11-11. No official page confirmed
Monitor incoming as well as outgoing payments, with money-mule signs. Status: consultation; comments close 24.12.2026; as of 2026-11-11. fca.org.uk
Large amounts soon after opening; a dormant account suddenly active. Status: guidance; as of 2026-11-11. bsaaml.ffiec.gov
Receiving banks monitor incoming credits, including new, dormant and mule accounts. Status: in force: phase 1 20.03.2026, phase 2 22.06.2026; as of 2026-11-11. nacha.org

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.

Below-the-line sample (AML rules)

AML rules have no labels below the threshold: nobody reviews a payment the rule did not flag. For each number threshold of a rule marked aml, the collector picked up to 20 payments in each of 3 bands just under the line (each band 10% of the threshold). Your analysts review them in btl-sample.csv: write suspicious or not_suspicious in analyst_label. The next run reads the marked file and shows the share marked suspicious. The file holds transaction IDs: it stays inside your environment and is never in the summary. The order is fixed by your token key and the seed "wowyrd-btl", so a re-run gives the same list. Nothing here changes a score.

RuleCheckBandPayments in bandSampledSuspiciousSuspicious share
tp_u21_fan_out_5_benef_5dthe number of different receiver id values with the same sender id in 5 days is at least 5from 4 below 541200 of 170.0%
tp_u21_fan_out_5_benef_5dthe number of different receiver id values with the same sender id in 5 days is at least 5from 3 below 4141202 of 2010.0%
tp_u21_fan_out_5_benef_5dthe number of different receiver id values with the same sender id in 5 days is at least 5from 2 below 3537200 of 200.0%
tp_u21_wire_count_gt2_7dthe number of transactions with the same sender id in 7 days is more than 2, counting only transactions where channel is "wire"more than 1 up to 25620——
tp_ffiec_fan_in_5_senders_5dthe number of different sender id values with the same receiver id in 5 days is at least 5from 4 below 515151 of 616.7%
tp_ffiec_fan_in_5_senders_5dthe number of different sender id values with the same receiver id in 5 days is at least 5from 3 below 496204 of 2020.0%
tp_ffiec_fan_in_5_senders_5dthe number of different sender id values with the same receiver id in 5 days is at least 5from 2 below 3451201 of 205.0%

Of the reviewed payments just under this threshold, this share was marked suspicious by your analysts. A high share means the threshold may be too high. It is not projected to all payments.

Not sampled

What changed since the previous report

Compared with the previous report, which covers data up to 2026-08-27 (35 days earlier). Its numbers are as measured at its own cut-off: labels that matured later are not added to it.

Per rule

Sorted by the size of the change in alerts, largest first. Precision is shown only with at least 30 hits with a known outcome in each run. Hit rate = alerts / transactions.

RuleAlerts thenAlerts nowChangePrecision thenPrecision nowChangeHit rate thenHit rate now
tp_u21_transfer_over_500324701+116%3.3%8.5%+5.1 points37.6%35.9%
tp_u21_wire_total_gt4999_7d3295+197%no datano datanot measured3.7%4.9%
tp_u21_large_txn_9k3680+122%no data34.5%not measured4.2%4.1%
tp_u21_wire_count_gt2_7d522+340%no datano datanot measured0.6%1.1%
tp_u21_fan_out_5_benef_5d1525+67%no datano datanot measured1.7%1.3%
tp_ffiec_fan_in_5_senders_5d1524+60%no datano datanot measured1.7%1.2%
R-50900no changeno datano datanot measured0.0%0.0%
R-61000no changeno datano datanot measured0.0%0.0%
R-90000no changeno datano datanot measured0.0%0.0%

Rules added and removed

Added: none.

Removed: none.

Threshold changes

No threshold changed.

Requirements

No requirement file was given for this run, so requirement changes are not compared.

Recommendations from the previous report

Of the previous report's 7 recommendations: 0 changed as proposed, 0 partly changed, 2 not changed, 5 where we cannot tell.

Too few dated changes for a median (0; at least 3 needed).

Open recommendations by age: 7 up to 30 days, 0 of 31–90 days, 0 over 90 days.

Days count from the first report that made each recommendation. A change dated before that report, a change with no exact date and an upper bound ("at most") are shown but not counted. This is a measurement on your own records, not a judgement of your change process.

ReferenceNo. in the previous reportRecommendationStatusSourceChange dateFirst recommendedDays to changeBefore → afterPredictedAgainst the prediction
REC-733094771Turn off rule tp_u21_transfer_over_500Not changed.your rule filenot known2026-11-20, in 1 reportopen 0 days, in 1 reportNot measured.Predicted: 9.5 fewer alerts per day (estimated on your data).—
REC-16a49a982Add a rule for: Gambling winnings arrive with no deposits, then card transfers followCannot tell: no change record or rule file covers it, and your data cannot show this kind of change.nonenot known2026-11-20, in 1 reportopen 0 days, in 1 reportNot measured.No effect was estimated for this recommendation.—
REC-fc5701c93Add a rule for: Large loans are taken and repaid again and againCannot tell: no change record or rule file covers it, and your data cannot show this kind of change.nonenot known2026-11-20, in 1 reportopen 0 days, in 1 reportNot measured.No effect was estimated for this recommendation.—
REC-5ff2bbff4Add a rule for: One type of operation makes up an unusual share of a user's activityCannot tell: no change record or rule file covers it, and your data cannot show this kind of change.nonenot known2026-11-20, in 1 reportopen 0 days, in 1 reportNot measured.No effect was estimated for this recommendation.—
REC-8078ec065Add a rule for: Payment purposes do not fit the merchant's category codeCannot tell: no change record or rule file covers it, and your data cannot show this kind of change.nonenot known2026-11-20, in 1 reportopen 0 days, in 1 reportNot measured.No effect was estimated for this recommendation.—
REC-05f946b26Add a rule for: Regular transfers to a personal account look like business activityCannot tell: no change record or rule file covers it, and your data cannot show this kind of change.nonenot known2026-11-20, in 1 reportopen 0 days, in 1 reportNot measured.No effect was estimated for this recommendation.—
REC-d74333d37Rule tp_u21_transfer_over_500, check 1: threshold 500 → 1000Not changed.your rule filenot known2026-11-20, in 1 reportopen 0 days, in 1 reportNot measured.Predicted: 0.9 fewer alerts per day (backtest on past data).—

Observed after the change, not proven to be caused by it. Traffic, fraud patterns and other changes in the same weeks also move these numbers. A status is about your own change, not about any regulation. This is a measurement for the rule owner, not an audit of your change process.

Coverage by fraud type

Fraud types present in your labels

Fraud types present in your labelsOne out to many (fan-out): 13 caught, 0 missed; Many into one (fan-in): 11 caught, 1 missed; Type not given: 58 caught, 20 missedOne out to many (fan-out)One out to many (fan-out)One out to many (fan-out): 13 caught13 caught, 0 missedMany into one (fan-in)Many into one (fan-in)Many into one (fan-in): 11 caughtMany into one (fan-in): 1 missed11 caught, 1 missedType not givenType not givenType not given: 58 caughtType not given: 20 missed58 caught, 20 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
One out to many (fan-out)13130WoWyrd rule available: One account pays many different payees
Many into one (fan-in)12111WoWyrd rule available: Many senders pay one account; One payee shared by several customers
Type not given785820WoWyrd 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).

Our reference set has not changed since your last report (version v0.7.0).

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

Your rules may not cover a requirement of NBU draft §16(10), §65-66

Review every rule at least monthly by back-testing it. (NBU draft §16(10), §65-66, status as of 2026-11-11). The previous report (data up to 2026-08-27) found it too (Gap), and it is still open. Now: Partly met.

We found no implementation guidance from the regulator for this requirement.

Public cases where a regulator named the same kind of gap (monitoring rules, scenarios or thresholds not reviewed, tested or tuned):

Your rules may not cover a requirement of NBU draft §60(1)

Metric 1: compare how often each rule fired with how many payments were actually stopped. (NBU draft §60(1), status as of 2026-11-11). The previous report (data up to 2026-08-27) found it too (Partly met), and it is still open. Now: Partly met.

We found no implementation guidance from the regulator for this requirement.

Public cases where a regulator named the same kind of gap (transaction monitoring not effective or not calibrated to the firm's risks):

Your rules may not cover a requirement of NBU draft §60(2)

Metric 2: share of fraud value that was prevented, out of all fraud value. (NBU draft §60(2), status as of 2026-11-11). The previous report (data up to 2026-08-27) found it too (Partly met), and it is still open. Now: Partly met.

We found no implementation guidance from the regulator for this requirement.

Public cases where a regulator named the same kind of gap (transaction monitoring not effective or not calibrated to the firm's risks):

Your rules may not cover a requirement of NBU draft §62-64

Set rule-effectiveness thresholds in writing. A rule under its threshold gets an immediate review. (NBU draft §62-64, status as of 2026-11-11). The previous report (data up to 2026-08-27) found it too (Gap), and it is still open. Now: Gap.

We found no implementation guidance from the regulator for this requirement.

Public cases where a regulator named the same kind of gap (monitoring rules, scenarios or thresholds not reviewed, tested or tuned; transaction monitoring not effective or not calibrated to the firm's risks):

Your rules may not cover a requirement of NBU draft §68-69

Record a review decision for every rule: keep, adjust or cancel. (NBU draft §68-69, status as of 2026-11-11). The previous report (data up to 2026-08-27) found it too (Partly met), and it is still open. Now: Partly met.

We found no implementation guidance from the regulator for this requirement.

Public cases where a regulator named the same kind of gap (monitoring rules, scenarios or thresholds not reviewed, tested or tuned):

Your rules may not cover a requirement of NBU draft §16, §18, §2

Reconcile payment operations every day. (NBU draft §16, §18, §2, status as of 2026-11-11). The previous report (data up to 2026-08-27) found it too (Partly met), and it is still open. Now: Partly met.

We found no implementation guidance from the regulator for this requirement.

We found no public enforcement case for this kind of gap.

Your rules may not cover a requirement of NBU draft §19

Have evidence ready for a supervisor: documents, rules, risk markers. (NBU draft §19, status as of 2026-11-11). The previous report (data up to 2026-08-27) found it too (Partly met), and it is still open. Now: Partly met.

We found no implementation guidance from the regulator for this requirement.

Public cases where a regulator named the same kind of gap (monitoring rules, scenarios or thresholds not reviewed, tested or tuned; transaction monitoring not effective or not calibrated to the firm's risks):

Your rules may not cover a requirement of 3 NYCRR 504.3

Analyse scenarios, rules and thresholds on an ongoing basis. (3 NYCRR 504.3, status as of 2026-11-11). The previous report (data up to 2026-08-27) found it too (Partly met), and it is still open. Now: Partly met.

How the regulator describes doing this:

Public cases where a regulator named the same kind of gap (monitoring rules, scenarios or thresholds not reviewed, tested or tuned):

Resolved since the previous report

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.No gap found in your dataguidance 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.No gap found in your dataguidance2026-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.

Many into one (fan-in) FAN-IN
Many accounts send money into one account, which collects it.
One out to many (fan-out) FAN-OUT
One account sends money out to many accounts, so it spreads thin.
Type not given no type
Fraud labels in your file that do not say which kind of fraud it was.