Unusual transactions
What breaks the pattern, with a clock and a file.
Flags transactions that need review, opens a case with the 24-hour deadline and documents the officer's analysis until it is closed.
OPERATIONAL SUITE · LFPIORPI COMPLIANCE
Every monthly compliance task, synchronized in one cockpit.
Explore how each module works interactively. Operations feed threshold tracking, screening, risk assessment and XML notices without duplicate manual entry.
Unusual Transactions
MODULE CAPABILITIES
What it does
- 01Feature
Red flags
Structuring, atypical amounts, sudden changes in behavior and critical list matches.
- 02Feature
24-hour case
Every unusual transaction opens a case with the clock running from the moment it becomes known.
- 03Feature
Documented analysis
Notes, owner, decision and date stay in the case and in the audit log.
- 04Feature
History per client
Check the same client's previous cases before deciding.
- 05Feature
Structuring & smurfing detection
Automatically flags split payments designed to stay just below UMA reporting thresholds or Article 32 cash caps.
- 06Feature
One-click 24-hour urgent XML generation
When a critical alert is adjudicated for reporting, it pre-populates the official 24-hour XML notice ready for the SPPLD portal.
REGULATORY & OPERATIONAL GUIDE
Compliance Guidelines for Unusual transactions
Essential LFPIORPI obligations, identification criteria, and supervisory rules applicable to this activity.
The goal is that no alert goes unreviewed and every decision has a written justification, with who made it and when.
MODULE FREQUENTLY ASKED QUESTIONS
Frequently asked questions
Why are unusual transaction alerts and 24-hour notices mandatory under the reform?
The LFPIORPI reform (enforced by June 1, 2027) requires reporting entities to operate automated mechanisms that detect unusual transactions—deviating from a client's transactional profile—and file urgent notices within 24 hours whenever illicit funds are suspected.
Which red flags and structuring patterns does the module detect automatically?
It flags structuring/smurfing (multiple transactions split just below the notice threshold or cash limit), sudden volume spikes relative to historical behavior, heavy cash usage, mismatches between declared occupation and transaction size, and watchlist hits.
Does the platform file notices automatically, or does the Compliance Officer decide?
Your Compliance Officer always makes the final call. PLDUnity surfaces the alert with full supporting evidence, opens a case management file, and lets the officer document their formal adjudication—either dismissing the alert with a reasoned justification or triggering a 24-hour XML notice.
How does the 24-hour countdown workflow operate?
When a critical alert is confirmed for urgent reporting, the dashboard tracks an auditable 24-hour SLA timer and immediately pre-populates the urgent XML notice with the client and transaction details.
How does this module connect with Watchlist Screening and the EBR Risk Engine?
They work together in real time: a positive watchlist hit (such as UIF or SAT 69-B) escalates in one click to an Unusual Transaction case, and any confirmed alert automatically increases the client's risk score in the EBR engine.
Are dismissed alerts and their justifications preserved for external auditors?
Yes. Regulators and external auditors check not only filed notices but also how internal alerts were investigated. Every dismissed alert retains its timestamp, reviewer, rationale, and supporting attachments for 10 years.
30-DAY FREE TRIAL · NO CREDIT CARD
Put the Unusual transactions module to work with your own data.
Start your 30-day free trial with your own transactions or schedule a 30-minute walkthrough with BDUnity's compliance specialists.