Currency Transaction Report Filing: What It Is, What Regulators Expect, and What Gets You Cited

What is Currency Transaction Report Filing?

Currency Transaction Report (CTR) Filing is the process by which US financial institutions identify, aggregate, and report to FinCEN (the Financial Crimes Enforcement Network) all currency transactions exceeding $10,000 conducted by, through, or to that institution within a single business day. The report is filed on FinCEN Form 112 and must be submitted within 15 calendar days of the triggering transaction.

The $10,000 threshold has not changed since the Bank Secrecy Act was enacted in 1970. That matters because it means the control's effectiveness depends entirely on how institutions aggregate transactions. Multiple cash deposits by the same customer across branches or accounts on the same day must be combined. Failing to aggregate is consistently the most cited exam finding.

CTR filing sits at the intersection of transaction monitoring and customer due diligence. The CTR itself is not an allegation of wrongdoing. It's a data-collection mechanism. FinCEN and law enforcement mine the database for patterns, and a CTR filed today may surface in a tax evasion investigation three years from now.

Compliance teams sometimes conflate CTRs with SARs. A CTR is mandatory whenever the dollar threshold is met, regardless of suspicion. A SAR is filed when a transaction looks suspicious, regardless of amount. A structuring case may generate SARs but no CTRs because the individual transactions all stay below $10,000.

Similar cash-reporting thresholds exist in other jurisdictions. Canada's FINTRAC requires Large Cash Transaction Reports for CAD 10,000 or more. Australia's AUSTRAC sets an identical AUD 10,000 threshold. The EU's Fourth and Fifth AML Directives require member states to maintain equivalent high-value cash reporting regimes.

Why is Currency Transaction Report Filing required?

The primary legal basis is the Bank Secrecy Act, 31 U.S.C. § 5313, and its implementing regulations at 31 CFR Part 1010. These require covered financial institutions (banks, credit unions, money services businesses, and certain other entities) to file CTRs for all covered transactions. Willful failures carry criminal penalties of up to $250,000 and five years' imprisonment. Civil penalties run to $25,000 per violation for negligent failures.

At the international level, FATF Recommendation 11 requires financial institutions to maintain records of transactions sufficient to allow reconstruction of any transaction and to make those records available to competent authorities on request. CTR filing is a direct expression of that obligation. FATF's risk-based approach also shapes how institutions think about aggregation logic and exemption management: higher-risk customer segments warrant more conservative exemption criteria.

FATF Recommendation 10 on customer due diligence ties directly into CTR quality. The report must accurately identify the person conducting the transaction. Weak CDD degrades CTR data, which is part of why FinCEN's 2016 Customer Due Diligence Rule formalized beneficial ownership requirements for legal entity customers.

Supervisory expectations are explicit. The FFIEC BSA/AML Examination Manual devotes a dedicated section to CTR filing requirements, covering identification, aggregation, exemption management, and filing timeliness. OCC, FDIC, and Federal Reserve examiners treat weak CTR programs as evidence of broader BSA management failure. Repeat findings escalate to matters requiring attention, formal agreements, and civil money penalties.

What do regulators expect to see?

Examiners want documented evidence that the CTR program works end-to-end. Policy documents are necessary but not sufficient.

Policies and procedures. Written procedures covering the $10,000 threshold, same-day aggregation rules, Phase I and Phase II exemption criteria, and the 15-calendar-day filing deadline. Procedures should be reviewed at least annually and approved by a named senior compliance officer.

System configuration records. Documentation of how the core banking or transaction monitoring system identifies and aggregates currency transactions. If thresholds or aggregation rules have changed, tuning records showing what changed, why, and who approved it are expected.

Exemption management. A current log of all active Phase I and Phase II exemptions with supporting documentation. Phase II exemptions require annual review. Examiners check whether expired exemptions were renewed and whether any high-risk customers were incorrectly exempted.

Filing timeliness records. Evidence that CTRs are filed within 15 calendar days. Late filing rates above 1-2% attract questions. Systemic delays, such as those caused by core banking migrations, require documented root-cause analysis and a remediation plan.

Quality assurance results. Independent testing showing that a sample of transactions was reviewed for CTR accuracy. This must include testing of aggregation logic, not just spot-checks of individual filings.

Training records. Documented training for all staff who handle cash, including tellers and branch staff. Training should be current and cover both the legal requirement and the institution's internal procedures.

Suspicious activity escalation process. A documented process for handling situations where a CTR transaction also warrants a SAR review. Filing a CTR does not satisfy SAR obligations.

MI and governance reporting. Monthly reporting to the BSA/AML compliance committee covering CTR volumes, filing timeliness, exemption counts, and system issues. Board-level reporting at least annually.

What does good Currency Transaction Report Filing look like?

Best practice goes beyond meeting the minimum. Institutions with strong programs do the following.

1. Automate aggregation at the source. Manual aggregation is error-prone and slow. The best programs integrate CTR identification directly into core banking so that tellers see a real-time indicator when a customer's daily cash total approaches $10,000. Automated aggregation across branches and accounts eliminates the most common exam finding before it happens.

2. Run independent validation monthly, not just annually. Pull a random sample of cash transactions between $9,000 and $9,999 and review them for structuring indicators. This serves two purposes: it catches smurfing and structuring patterns early, and it validates that aggregation logic is functioning correctly.

3. Review exemptions quarterly. The regulatory minimum for Phase II exemptions is an annual review. Leading institutions review quarterly. Customers whose cash volumes have shifted should have their exemption status reassessed before the annual cycle, not after.

4. Set an internal SLA shorter than the regulatory deadline. If FinCEN allows 15 calendar days, file internally within 10. The gap is a buffer for system outages, data quality issues, or peak transaction periods. Track performance against your internal SLA, not just the regulatory one.

5. Route CTR data into behavioral analytics. A customer who consistently presents cash just below $10,000 is a structuring candidate. Linking CTR filing history to transaction monitoring analytics creates a feedback loop that catches layering patterns that threshold-only rules miss.

6. Document every exemption denial. When a customer qualifies for exemption but you choose not to grant it, record the reason. This creates a defensible record if the customer later complains or if examiners question why your exemption population is smaller than peer banks.

The FFIEC BSA/AML Examination Manual, FinCEN's published guidance at fincen.gov, and the Basel Committee's guidance on sound management of ML/TF risks (BIS, 2017) are the primary public benchmarks for calibrating a CTR program against supervisory expectations.

Common audit findings and exam citations

CTR filing is one of the most consistently cited BSA control areas. The patterns repeat across institutions and examiners.

Aggregation failures are the most frequent finding. Institutions that rely on branch staff to manually combine transactions miss same-day cash across multiple accounts, multiple branches, or transactions conducted by different people on behalf of the same customer. A 2020 FinCEN advisory specifically named aggregation failures as a systemic weakness at mid-size US banks.

Structuring detection gaps. An institution that files CTRs reliably but has no program to detect customers staying deliberately below the threshold has half a program. The HSBC 2012 enforcement action included findings on both CTR filing failures and structuring detection gaps. The total penalty was $1.9 billion. HSBC's examiners found that manual processes, inadequate systems, and poor oversight had left the bank unable to aggregate transactions across accounts. The case is now a standard reference in BSA examiner training.

Exemption mismanagement. Common variants: Phase II exemptions not reviewed on the annual cycle; exemptions granted to customers who don't meet the eligibility criteria; no documentation of why an exemption was approved. Examiners reviewing exemption files expect to find supporting documentation for every active exemption.

Late filing. Some institutions treat the 15-day deadline loosely. Examiners check filing timestamps against transaction dates. Late filing rates above 2-3% typically result in a matter requiring attention.

Poor data quality. CTRs with incorrect TINs, incomplete addresses, or wrong entity types are rejected by FinCEN. Rejected CTRs that aren't re-filed within the deadline become violations. A rejection rate above 0.5% suggests a data quality problem in source systems that won't resolve without a systemic fix.

No independent testing. Many smaller institutions have written CTR policies but no function reviewing filing accuracy. Examiners treat the absence of independent testing as a control gap.

Metrics and KPIs

A CTR program is only as strong as its measurement. These are the metrics that matter.

Filing timeliness rate. The percentage of CTRs filed within 15 calendar days. Target: 99% or above. Track separately against your internal SLA (e.g., 10 days) and the regulatory deadline.

Late filing count. Absolute number of CTRs filed after the 15-day deadline per month. Any nonzero number needs a root-cause explanation. A single incident is manageable; a trend is a control failure.

Exemption population size and change rate. Total active exemptions broken down by Phase I and Phase II. Track month-over-month changes. A sudden drop may indicate a system issue; a sudden increase warrants a review of whether new exemptions were properly evaluated.

Exemption review completion rate. The percentage of Phase II exemptions reviewed on schedule. Target: 100%. Overdue reviews are a finding waiting to happen.

CTR rejection rate. Track your FinCEN rejection rate and time-to-refile. A rejection rate above 0.5% suggests systematic data quality problems.

Structuring alert rate. The number of structuring alerts generated per 1,000 CTR filings. If this ratio is near zero, structuring detection is likely undercalibrated.

Below-threshold cash transaction volume. Monitor transactions between $8,000 and $9,999. A spike in this band relative to overall cash transaction volume is a structuring signal worth investigating.

Independent testing coverage. The percentage of CTR filings reviewed in the annual independent test. A statistically valid sample is the target; 50 to 100 CTRs per year is a reasonable floor for a mid-size institution.

How Currency Transaction Report Filing connects to other controls

CTR filing doesn't operate in isolation. It feeds and draws on several adjacent controls.

Transaction monitoring is the closest neighbor. The same cash transaction data that triggers a CTR also runs through monitoring scenarios for structuring, smurfing, and money mule network activity. Institutions that treat these as separate programs miss the behavioral context that makes CTR data most useful.

Customer due diligence quality determines CTR data quality directly. If KYC is weak, CTR filings contain incorrect identifiers. FinCEN's 2016 CDD Rule was partly designed to close this gap by requiring beneficial ownership information for legal entity customers.

SAR filing runs in parallel with CTR filing. A transaction above the threshold that also looks suspicious must generate both. The two obligations are independent: CTR reporting is volume-based, SAR reporting is suspicion-based, and filing a CTR does not satisfy or substitute for a SAR.

CTR data feeds typology detection as well. Layering schemes often begin with large cash deposits that generate CTRs. Connecting CTR filing history to wire transfer and account activity data gives investigators a fuller picture of the placement and layering phases of laundering.

How FluxForce supports Currency Transaction Report Filing

FluxForce monitors cash transaction activity in real time, aggregates across accounts and channels, and flags transactions approaching or crossing the reporting threshold automatically. Nova Sentinel detects behavioral patterns around the $10,000 threshold that indicate structuring before a formal alert would fire. Aiden Flux generates audit-ready evidence for every filing decision, with configurable alerts for late-filing risk and upcoming exemption expiry dates. Reporting is structured for examiner review from day one. See how it works: request a live demo.