← All articles
·8 min read

Currency Transaction Report (CTR): The $10,000 Rule, Filing Steps, and Common Mistakes

A plain-English guide to the Currency Transaction Report (CTR): the $10,000 threshold, aggregation rules, FinCEN Form 112, filing deadlines, and how CTRs connect to sanctions screening and SAR workflows.

A Currency Transaction Report — CTR — is a report that U.S. financial institutions must file with FinCEN whenever a customer conducts a cash transaction, or a set of related cash transactions in a single business day, that exceeds $10,000. It is filed on FinCEN Form 112 and is one of the oldest and most heavily audited pieces of the Bank Secrecy Act (BSA) framework.

The rule is deceptively simple. Any cash-in or cash-out transaction over $10,000 triggers a CTR. So do multiple cash transactions by or on behalf of the same person on the same business day whose aggregate exceeds $10,000 — even if each individual transaction is smaller. Aggregation is required across branches and across account types, which is why most institutions rely on automated core-banking rules rather than teller judgment.

CTRs apply to physical currency only: bills and coins. Wire transfers, ACH, card transactions, personal checks, and cashier's checks are not currency for CTR purposes (though cashier's-check purchases funded with cash are, and they trigger separate Monetary Instrument Log obligations at $3,000+). Cryptocurrency is not currency under the BSA definition, but a growing number of virtual-asset service providers file CTR-equivalent reports under state money-transmitter rules.

Filing deadlines are strict. A CTR must be e-filed via the BSA E-Filing System within 15 calendar days of the transaction date (25 days if filed on paper, though paper filing is now rare and being phased out). Late filings are one of the most common enforcement findings and can carry per-violation civil penalties that scale with institution size and pattern of conduct.

The information collected is extensive: customer identifying details (name, address, SSN or TIN, date of birth, occupation, government-issued ID), the transaction amount, whether it was cash-in or cash-out, the account(s) affected, and the identity of any person on whose behalf the transaction was conducted (the 'beneficial cash actor'). Getting the beneficial-actor field right is the single most common CTR error — a customer depositing cash on behalf of their employer must be reported as the conductor, with the employer as the person on whose behalf.

Exemptions exist but are narrower than most staff assume. Under the Money Services Business exemption and the Phase I / Phase II exemption regime, certain listed businesses (banks, government agencies, publicly traded companies and their subsidiaries) and qualifying non-listed businesses that meet strict criteria can be exempted from CTR filing on their own accounts. Exemptions must be designated on FinCEN Form 110 and reviewed annually — an unreviewed exemption is treated by examiners as no exemption at all.

CTRs and structuring are two sides of the same coin. Structuring — breaking a cash transaction into smaller amounts to evade the $10,000 threshold — is a separate federal crime under 31 U.S.C. § 5324 and must be reported on a Suspicious Activity Report (SAR), not just avoided on the CTR. If a teller sees a customer withdraw $9,900 in cash three times in a week, the institution has both a CTR non-trigger (individually) and a likely SAR trigger (in aggregate). Training staff to recognize this pattern is a standard exam expectation.

CTR data feeds directly into sanctions and AML workflows. Every CTR is name-searched by FinCEN against Treasury watchlists, and institutions are expected to screen the conductor and beneficial actor against OFAC SDN before filing. A cash transaction with an OFAC-designated party is not merely a CTR — it is a blocked transaction requiring an OFAC report and asset freeze in addition to (or instead of) the CTR, depending on the facts.

For compliance teams, the practical CTR checklist is short but non-negotiable. Automate aggregation across the customer's day. Screen the conductor and beneficial actor against OFAC SDN, EU, UK, and UN lists at the time of the transaction, not just at onboarding. Capture the beneficial-actor field correctly. Review and re-approve exemptions annually. Reconcile filed CTRs against the general ledger monthly. And retain the underlying records for five years, in a format an examiner can pull on demand.

SanctionsScreening helps with the sanctions-screening leg of the CTR workflow: unified OFAC SDN, EU, UK and UN checks with fuzzy matching, PDF audit reports you can attach to the CTR file, and an API for real-time screening at the teller line. See the pricing page for volume tiers or run a free search from sanctionsscreening.io to test coverage against your own historical CTR conductors.

Try it free on SanctionsScreening.io

Run a free sanctions search against OFAC, EU, UK and UN lists — no signup required.