“Title 31” is the name casino employees commonly use for the U.S. federal anti-money-laundering and financial-recordkeeping rules that apply to casinos and card clubs under the Bank Secrecy Act. It covers much more than one cash threshold. A functioning Title 31 program connects customer identification, transaction aggregation, currency reports, suspicious-activity review, record retention, staff training, independent testing, and day-to-day compliance ownership.
The term is U.S.-specific. Other countries may impose similar anti-money-laundering duties under different laws and regulators. This page explains the casino meaning of Title 31, not legal advice for a particular transaction.
The name is shorthand, not a single form
The relevant federal rules sit in Title 31 of the Code of Federal Regulations, especially Part 1021 for casinos and card clubs. In ordinary casino conversation, however, staff may use “Title 31” to describe the whole operational program: the procedures at the cage, the identification requests on the floor, the logs used to aggregate cash, the compliance review, and the reports filed with the Financial Crimes Enforcement Network, or FinCEN.
That shorthand creates confusion because several different duties are being compressed into one phrase.
| Duty | What it means operationally | What it does not mean |
|---|---|---|
| AML program | Written controls, training, testing, and a designated compliance function | A cashier improvising a response at the window |
| Currency reporting | Reporting qualifying cash-in or cash-out activity | Reporting every gambling win or every non-cash transaction |
| Aggregation | Combining related cash transactions when the casino has knowledge they are by or for the same person during one gaming day | Looking at only one window or one department |
| Suspicious-activity review | Examining facts and patterns that may indicate evasion, unlawful funds, or misuse of the casino | Assuming that every large transaction is criminal |
| Recordkeeping | Retaining required identity, account, credit, transaction, and supporting records | Keeping informal notes with no access or retention control |
Title 31 is also separate from W-2G. W-2G concerns federal tax reporting for certain gambling winnings. Title 31 concerns anti-money-laundering, currency reporting, suspicious transactions, and financial records. A single event can involve both, either, or neither.
Which casinos are covered?
Under the federal definition, a duly licensed or authorized U.S. casino or card club generally becomes a financial institution for these rules when gross annual gaming revenue exceeds $1 million. The definition includes qualifying state, territorial, and tribal operations. Smaller establishments and non-gaming resort businesses can still have other cash-reporting duties, so the threshold should not be read as a universal exemption from all federal reporting.
For the current legal text, the federal definition of a casino and card club is the correct starting point. Property procedures may be stricter than the federal minimum because of state, tribal, internal-control, or risk requirements.
The cash-reporting rule people notice first
A covered casino must file a Currency Transaction Report for each transaction in currency involving cash in or cash out of more than $10,000. The words matter:
- currency means physical cash, not every monetary instrument;
- more than $10,000 is different from exactly $10,000;
- cash in and cash out are considered separately;
- multiple transactions can be aggregated during the casino’s gaming day when the casino has knowledge they are by or on behalf of the same person.
Cash in can include chip purchases, front-money deposits, safekeeping deposits, cash payments on credit, money plays, currency exchanges, and bills inserted into gaming devices. Cash out can include chip or ticket redemptions, front-money withdrawals, check cashing, currency exchanges, and certain payments or incentives. The regulations contain details and exemptions; staff should follow the approved property procedure rather than a simplified list on a glossary page.
Aggregation example
Suppose a customer buys $6,000 in chips at a table and later buys another $5,500 in chips at the cage during the same gaming day. If the casino has knowledge that both cash-in transactions are by the same person, the aggregate cash in is:
[ $6{,}000 + $5{,}500 = $11{,}500 ]
Because $11,500 is more than $10,000, the activity reaches the federal currency-reporting threshold. The compliance question is not solved by asking whether either transaction, viewed alone, exceeded $10,000.
This is why floor, cage, slots, credit, hosts, and compliance cannot operate as isolated islands. Knowledge held in one part of the casino may matter to the total picture. Casino Management Systems Explained describes the systems problem behind that cross-department view.
A SAR is not a “large cash form”
A Suspicious Activity Report, or SAR, is conceptually different from a Currency Transaction Report. The casino SAR rule applies to conducted or attempted transactions involving or aggregating at least $5,000 in funds or other assets when the casino knows, suspects, or has reason to suspect specified suspicious circumstances. Those circumstances include possible illegal proceeds, concealment, evasion of BSA requirements, transactions with no apparent lawful purpose after review, or use of the casino to facilitate criminal activity.
The $5,000 amount is therefore not an automatic filing rule by itself. Suspicion and the regulatory criteria matter. Likewise, a transaction above $10,000 is not suspicious merely because it is large. A legitimate customer can create a routine CTR. A smaller pattern can raise serious concerns if it appears designed to evade reporting or lacks a reasonable purpose.
SAR confidentiality is strict. Casino employees generally must not tell a customer that a SAR was filed or reveal information that would disclose its existence. A player who asks, “Are you reporting me?” should not expect staff to confirm or deny a suspicious-activity report.
The current federal requirements for casino AML programs, CTRs, aggregation, SARs, confidentiality, and records appear in 31 CFR Part 1021.
What a credible casino program contains
The federal rule requires more than forms after the fact. A casino AML program must be written and reasonably designed to assure and monitor compliance. At minimum, it includes:
- internal controls for continuing compliance;
- independent testing with scope and frequency matched to risk;
- training for personnel who need to recognize and escalate relevant activity;
- a person or function responsible for daily compliance;
- procedures that use available information to identify customers, report patterns, and create required records;
- automated support, where the casino has automated data-processing systems.
A strong program assigns responsibilities by role. A dealer is not expected to conduct a full money-laundering investigation. The dealer may be expected to record a cash buy-in accurately and alert a supervisor. A cashier may collect identification and complete a log. Surveillance may preserve a timeline. A host may provide known customer context without interfering with compliance. The compliance team evaluates the combined information and decides what filing or escalation is required.
FinCEN’s casino red-flags guidance emphasizes risk-based procedures and the value of information casinos already hold through deposits, credit, check cashing, ratings, and player accounts.
Why casinos ask for identification
Identification requests can arise for several reasons: a CTR, account opening, credit, jackpot or tax paperwork, age verification, self-exclusion controls, property policy, or another legal requirement. The employee should explain what information is needed and the immediate transaction requirement without guessing, threatening, or disclosing confidential compliance decisions.
A refusal to provide required identification may prevent the casino from completing the transaction. It does not give staff permission to invent data or split the transaction into smaller pieces. “Helping” a customer avoid paperwork can expose both the employee and the casino to serious risk.
Structuring makes the situation worse
Structuring means arranging transactions to evade a reporting requirement. In casino settings it may involve attempts to divide cash among windows, times, departments, accounts, or people. The danger is not limited to a customer explicitly saying, “I want to stay under the limit.” Staff must consider conduct and patterns, not only admissions.
The correct employee response is not to teach the threshold or suggest a smaller amount. It is to follow the approved procedure, record facts, and escalate. This is one reason threshold signs, casual staff comments, and host intervention require careful control.
A practical operating sequence
Consider a player who buys chips with cash, deposits front money, redeems tickets, and cashes out chips during the same gaming day.
A disciplined operation should be able to:
- associate the activity with the correct person where required;
- distinguish cash in from cash out;
- aggregate known transactions across systems and departments;
- retain the underlying records and identification details;
- document unusual behavior factually;
- prevent commercial pressure from suppressing an alert;
- route the case to trained compliance staff;
- keep SAR decisions confidential;
- preserve supporting material for the required retention period.
That sequence depends on KYC, Know Your Customer, accurate cage records, reliable player identification, and controlled access to sensitive information.
Common failures
Treating it as a cage-only duty
Large cash activity can begin on a table, at a slot machine, through credit, with a host, or at the cage. A program fails when each department sees only its own transaction.
Confusing actual gambling with financial movement
A customer may buy in, wager meaningfully, and cash out. Another may move a similar amount with little gaming. The dollar total alone does not explain purpose. Compliance review needs the transaction history and the gambling context.
Using player value as an exception
A high-value customer is not exempt. Hosts and executives should not pressure staff to ignore identification, alter logs, or delay escalation because the relationship is commercially important.
Filing without fixing data quality
Duplicate player records, shared accounts, wrong gaming-day settings, missing cashier identifiers, and broken interfaces can prevent accurate aggregation. Repeated manual corrections are an operational warning, not a permanent solution.
Discussing SARs casually
The existence of a SAR is confidential. Training must cover conversations, email, chat, report distribution, and access permissions, not just the filing screen.
What players should understand
Routine identification or reporting does not prove wrongdoing. Casinos are financial institutions for BSA purposes and must document qualifying activity. A player can reduce confusion by using their own identity, keeping transactions straightforward, answering legitimate questions accurately, and not trying to divide activity to avoid a perceived threshold.
A casino employee cannot provide a customer with a safe method to “stay under Title 31.” The lawful approach is transparent activity and accurate records.
The useful distinction
Title 31 is not one alarm that sounds at one number. It is a control system. CTR rules document qualifying currency activity. SAR rules address suspicious facts and patterns. AML programs define how the casino detects, reviews, reports, trains, tests, and retains evidence. Customer identification and recordkeeping allow those duties to work.
That is why the term appears across Anti-Money Laundering, KYC, cage operations, player tracking, credit, surveillance, and management reporting. The forms matter, but the quality of the program is determined by what happens before the form is filed.