What Is Currency Transaction Report (CTR)?

How Currency Transaction Report (CTR) Works

A Currency Transaction Report is filed by a financial institution any time a customer conducts a cash transaction exceeding $10,000 in a single business day. The filing obligation arises automatically — no judgment call is required — and covers deposits, withdrawals, currency exchanges, and the purchase of monetary instruments. Understanding the mechanics is essential for compliance officers, payment operations teams, and any merchant handling significant volumes of physical cash.

Why Currency Transaction Report (CTR) Matters

The CTR is one of the highest-volume regulatory filings in the U.S. financial system and functions as a foundational data layer for anti-money laundering enforcement. Without it, law enforcement would lose visibility into the large-cash-transaction patterns that frequently accompany financial crime networks.

FinCEN received approximately 17.8 million CTRs in fiscal year 2022, according to its annual report — making it by far the most frequently filed BSA instrument. That volume reflects the breadth of the cash economy and the granularity of financial intelligence available to investigators. Each filing is retained in FinCEN's database and can be queried by authorized federal, state, and local law enforcement agencies without a subpoena, dramatically accelerating financial investigations.

The financial stakes of non-compliance are equally significant. Civil money penalties for Bank Secrecy Act violations — including CTR failures — exceeded $3.4 billion in total enforcement actions between 2015 and 2022, with individual institution fines ranging from tens of thousands to hundreds of millions of dollars. Regulatory agencies including FinCEN, the OCC, and the Federal Reserve have all levied material penalties against institutions with systemic CTR filing failures.

Beyond enforcement risk, CTRs matter because they create a paper trail that deters criminals from attempting to move illicit funds through legitimate financial channels. When paired with Suspicious Activity Reports, they give investigators the narrative and numerical data needed to pursue structuring, smurfing, and layering schemes — the core techniques used in money laundering operations globally.

Currency Transaction Report (CTR) vs. Suspicious Activity Report (SAR)

CTRs and SARs are both mandatory BSA filings, but they operate on completely different triggers and serve different investigative purposes. Conflating them is one of the most common compliance errors in financial institutions.

The Suspicious Activity Report requires a trained compliance officer to exercise judgment about whether activity is unusual or potentially criminal. The CTR requires no judgment — only accurate data collection and timely filing. Both reports feed the same FinCEN intelligence database and are often cross-referenced during investigations.

Types of Currency Transaction Report (CTR)

While there is only one official form — FinCEN Form 112 — CTR filings fall into distinct practical categories based on what triggers them and how they are structured.

Single-Transaction CTR. The most straightforward type: one customer, one cash transaction, one business day, exceeding $10,000. A retail customer depositing $15,000 in cash is a typical example. The institution captures the transaction and the individual's identifying information in a single filing.

Aggregated CTR. When a customer conducts multiple cash transactions in a single business day that collectively exceed $10,000, the institution must aggregate them into a single CTR. A business owner making a $4,000 cash deposit at opening and a $7,500 cash deposit at closing triggers an aggregated CTR for $11,500 — even though neither individual deposit crossed the threshold.

Multiple-Individual CTR. In some cases, multiple individuals conduct transactions on behalf of the same account or beneficial owner. The institution must identify all parties and document each on the CTR to prevent disguised aggregation through the use of multiple couriers or agents — a technique known as smurfing.

Exempt-Entity Monitoring Filing. When an institution grants a Phase I or Phase II exemption to a qualifying business, it removes that customer from automatic CTR generation. However, the institution must file an annual renewal and document its rationale. If the exempt business later exhibits unusual patterns, the exemption can be revoked and back-filing may be required.

Best Practices

For Merchants

Cash-handling businesses — retailers, restaurants, entertainment venues, and others — are frequently on the customer side of CTR filings. Understanding how your banking relationships work under BSA rules protects you from misunderstandings and regulatory friction.

• Disclose large cash transactions proactively. Inform your bank when you expect unusually high cash volumes — seasonal peaks, events, promotions. Transparency prevents suspicion and supports the exemption designation process.
• Never restructure deposits to avoid the $10,000 threshold. Structuring is a federal crime even when the underlying funds are entirely legitimate. Deposit your full daily cash intake together rather than splitting it across days or accounts.
• Maintain your own transaction records. Keep point-of-sale logs, safe counts, and deposit slips that match your bank statements. If a CTR is ever questioned, these records demonstrate consistency and good faith.
• Understand Phase II exemption eligibility. If your business makes frequent large cash deposits, ask your bank whether you qualify for a BSA exemption. Qualified non-listed businesses that meet payroll or revenue criteria may eliminate routine CTR filings for their accounts.
• Train front-line staff. Employees who handle cash must know that asking customers to split transactions to avoid paperwork is illegal — even if a customer requests it.

For Developers

Payment and fintech platform developers building tools that touch cash-handling workflows, AML systems, or financial data pipelines need to account for CTR logic in their architecture.

• Build aggregation logic at the customer level, not the transaction level. Your CTR trigger system must sum all cash transactions by the same customer within a business day window — not just evaluate each transaction independently.
• Define "business day" carefully. Many institutions use a non-calendar business day cutoff (e.g., 10 PM EST). Your aggregation window must match the institution's defined business day, not UTC midnight.
• Automate identity data capture at the point of transaction. CTR-triggering transactions require verified customer identity fields. Build prompts and validation into the teller or POS workflow so compliance data is collected in real time, not reconstructed after the fact.
• Log all exemption statuses and review dates. Store Phase I and Phase II exemption records with expiration dates and surface renewal alerts well in advance — at minimum 60 days before annual review deadlines.
• Implement a SAR cross-check. When a CTR is generated for a customer, automatically check whether that customer has open SAR investigations. Simultaneous CTR and SAR activity on the same account warrants escalation to senior compliance review.
• Test aggregation edge cases. Unit-test scenarios where transactions straddle business day cutoffs, involve multiple tellers, or use multiple account numbers belonging to the same beneficial owner.

Common Mistakes

Failing to aggregate intra-day transactions. The most frequent CTR error. Compliance systems that only flag individual transactions above $10,000 miss the aggregation requirement entirely. A customer making three $4,000 deposits triggers a CTR; a system monitoring only single transactions will miss it. This is an examinable deficiency in every BSA audit.

Tipping off the customer. Unlike some other compliance obligations, there is no explicit federal prohibition on disclosing that a CTR was filed. However, if the disclosure is made in conjunction with a SAR or in a way that warns the customer about a potential investigation, it can constitute obstruction. Institutions should have a clear policy: CTR filings are administrative and need not be disclosed, but should never be discussed in a way that signals law enforcement interest.

Confusing CTR with SAR obligations. Receiving a large cash deposit does not require a SAR — it requires a CTR. Filing a SAR instead of (or in addition to) a CTR for a routine large cash transaction misallocates compliance resources and can create a false investigative trail. Each filing type has a distinct trigger; train compliance staff to apply them independently.

Incomplete or inaccurate identity information. FinCEN Form 112 requires specific fields: full legal name, address, date of birth, and identification number. Submitting a CTR with missing or incorrect identity data — common when tellers rush through the process — renders the filing deficient and can trigger examination findings even when the transaction itself was correctly identified.

Granting exemptions without annual review. Phase II exemptions do not expire automatically, but institutions are required to review them at least once every 12 months. Failing to document annual reviews is a common BSA audit finding. If an exempt customer's transaction patterns change materially, the exemption should be re-evaluated and potentially revoked mid-year.

Currency Transaction Report (CTR) and Tagada

Tagada operates as a payment orchestration layer, routing card, bank transfer, and alternative payment method transactions across processor networks. Because CTR obligations attach specifically to physical cash transactions handled by depository institutions, Tagada does not itself file CTRs.

However, merchants using Tagada who also operate cash channels — physical retail, hybrid commerce, or cash-equivalent instruments — need full visibility across all payment rails to manage their compliance posture accurately.