By Sagar Shankaran, Founder of CallSphere
Casinos hand-key FinCEN Form 112 CTRs into BSA E-Filing. An agent can draft them from the Multiple Transaction Log; the compliance officer still submits.
Key takeaways
Forty-one. That is the number of Currency Transaction Reports one regional property filed for a single Super Bowl Sunday gaming day — every one keyed into FinCEN's BSA E-Filing System by hand, by a compliance clerk who had to go find half the information first.
A casino is a financial institution under the Bank Secrecy Act. Cash in or cash out above $10,000 for the same patron in the same gaming day means a FinCEN Form 112, filed within fifteen calendar days. The form itself is not complicated — it is just long, and the information sits in five different places. The patron's name, date of birth, taxpayer identification number, identification type and number and issuing state, address, and occupation. The amounts, broken out by kind: chip purchases, front money deposits, bets placed, currency exchanges on the cash-in side; chip redemptions, ticket redemptions, payments on winning wagers, jackpot payouts on the cash-out side. Then the property's own details, then the filer's.
Your clerk pulls that from the Multiple Transaction Log, the cage system, the pit's handwritten sheets, the sportsbook ticket writer's records, the kiosk log and the players club record in Oasis 360, SYNKROS or IGT Advantage — then retypes it into a web form that times her session out while she hunts for the missing identification number.
It looks like a pile of Multiple Transaction Log sheets, a printout from the cage, and a clerk who will not get to anything else before lunch. Somebody has to decide which patrons aggregated past ten thousand, find the ones whose identification was captured at the three-thousand-dollar recordkeeping line but never verified, and start typing.
The workaround every property runs is the same: batch it. Nobody files on Monday for Sunday. They let the week pile up and grind through it on Wednesday and Thursday, which is fine until somebody is on vacation, or the pile hits day thirteen, or a filing goes in with the occupation field reading "retired" with nothing else — which is the kind of vague entry examiners flag every time.
There is an electronic batch path in BSA E-Filing for institutions whose systems can produce the file. Plenty of casinos cannot get their vendor to build it, cannot justify the change to an approved gaming system, or have it and still key exceptions by hand. If your clerk still opens a browser and types, this article is about you.
Screen automation is not new. Recorded keystroke macros have existed forever, and every one broke the first time FinCEN moved a field. That is why nobody in a cage office trusts them.
Hear it before you finish reading
Talk to a live CallSphere AI voice agent for hospitality in your browser — 60 seconds, no signup.
What arrived in 2026 is different in kind: computer use — an agent that drives the screen the way a person does. It looks at what is actually on the page, finds the field labelled "Occupation", clicks it, types, and if a validation message appears it reads the message and responds instead of blindly continuing. It does not need the portal to offer a connection for other software, because it is using the same login, the same buttons and the same forms your clerk uses.
That matters enormously in gaming, because the portals this industry lives inside were built for people, not for other systems: FinCEN's filing system, your state board's employee registration renewals, the monthly gaming tax return, the self-exclusion list check. None were designed to be talked to by your casino management system, and none are going to be.
flowchart TD
A["Gaming day closes at 6am"] --> B["Agent reads the Multiple Transaction Log"]
B --> C{"Cash in or cash out over $10,000?"}
C -->|No| D["Leave in the log, keep aggregating"]
C -->|Yes| E["Agent logs into BSA E-Filing, drafts Form 112"]
E --> F{"Missing ID number, TIN or a real occupation?"}
F -->|Yes| G["Flag to cage supervisor to capture at next visit"]
G --> E
F -->|No| H["Compliance officer reviews the draft and clicks Submit"]
H --> I["Confirmation number filed back to the patron record"]
Tuesday, 7:10 a.m. The agent reads yesterday's Multiple Transaction Log and the cage records, groups the entries by patron, and produces a short list: nine patrons crossed ten thousand, two of them across more than one department — a table games buy-in plus a sportsbook cash-out, the kind of aggregation that gets missed when two different clerks are looking at two different logs.
For each of the nine, it opens the filing system, starts a report, and fills the fields from the player record and the prior filings on file. Where the information is complete, the draft is ready. Where it is not — no identification number captured, a taxpayer identification number missing, an occupation entered as "self-employed" with nothing more — it stops, marks the reason, and drops a note for the cage supervisor to capture the detail at the patron's next visit.
At 8:30 the Title 31 compliance officer opens seven finished drafts and two exceptions, reads each against the log, corrects one amount and submits. Thirty-five minutes — on day one of fifteen instead of day twelve.
Illustrative figures for a mid-size property; substitute your own filing count.
| Assumption | Today | With screen automation |
|---|---|---|
| Form 112 filings per week, annual average | 46 | 46 |
| Gathering and typing, per filing | 9.5 min | 0 min (drafted overnight) |
| Human review, per filing | included above | 3.0 min |
| Clerk hours per week | 7.3 | 2.3 |
| Hours saved per year | — | 260 |
| Loaded cost per hour, compliance clerk | $34 | $34 |
| Annual labour value returned | — | $8,840 |
| Average days from gaming day to filing | 11 | 2 |
The $8,840 is real but it is not the main number. The main number is the eleven days becoming two. Late and incomplete Bank Secrecy Act filings carry civil penalties assessed per filing and adjusted for inflation each year — your anti-money-laundering officer knows the current figure, and it is not small when a pattern is alleged rather than a single miss. A property that files on day two never has a day-fifteen problem, never has a vacation problem, and never has the awkward examination finding where twenty filings all went in on the same afternoon.
There is a second saving nobody counts: amendments. A corrected Form 112 costs as much clerk time as the original and looks worse in a file.
The Submit button, first. A filing is a legal statement by your property with a named human filer on it. The agent drafts; the compliance officer reads and files. If a vendor says the review step can be dropped once accuracy is proven, end the meeting.
Still reading? Stop comparing — try CallSphere live.
See the hospitality AI agent handle a real call — complete, industry-specific, and live in your browser. No signup.
Suspicious Activity Reports, second, and this one is absolute. Deciding that a pattern looks like structuring, that a patron is minimum-play chip-walking, or that an employee is involved, is judgment — and the narrative on a Form 111 is written argument that an examiner and possibly a prosecutor will read. Have the agent assemble the transaction history that supports the narrative. Do not have it write the narrative or make the decision to file.
Identification verification, third. Nothing on a screen can look at a driver's licence. The cage and the pit capture and verify identification the way your internal controls describe, and no amount of automation upstream changes that.
And the source of truth stays where it is. The agent reads the Multiple Transaction Log; it does not maintain it. If your log is unreliable, faster filing just spreads the errors around more efficiently. Fix the log first.
Once one portal works, the pattern repeats across every screen your staff logs into by hand. Gaming employee badge renewals — a property with 900 badge holders renews on a rolling schedule all year, with a human resources coordinator retyping details out of your HR system. The monthly gaming tax return. The self-exclusion list check. Vendor registration renewals.
Start with the one that has the clearest deadline attached and the least judgment involved, which for almost every property is the CTR queue. Run it in draft-only mode for two weeks alongside your current process and compare the drafts against what your clerk filed. If they match, you have a case. If they do not, you have found something worth knowing about your log.
That is exactly the question to put to your anti-money-laundering officer and your counsel before anything is set up, not after. Filing credentials are personal and accountability follows them. The workable arrangement most properties land on is the agent preparing drafts and a credentialed human performing the login and submission — which is also what keeps the named-filer requirement clean.
The examination looks at whether filings were accurate, complete and timely, and whether your written program describes what you actually do. So write it into the program: what the agent drafts, who reviews, what happens to exceptions. A documented drafting aid with human review is a stronger position than a pile of hand-keyed forms filed on day fourteen.
Get the quote and the timeline, then compare it with a screen-driven approach you can trial in two weeks. Batch filing is the better long-term answer if it arrives, but changes to approved gaming systems are rarely quick, and nothing stops you doing the cheap thing now.
That is the single best reason to do this. A patron buying in at a table, cashing tickets at a kiosk, and collecting at the sportsbook window in one gaming day is precisely the case a tired clerk misses at four in the afternoon. Grouping the day's activity by patron across every department is a mechanical task, and machines are better at it than people are.
Worth noting where the phone fits into all this. Compliance filings are back-of-house, but the same weekend that generates forty-one filings also generates a switchboard nobody can keep up with — jackpot questions, lost players club cards, room and bus programme calls. CallSphere builds AI voice and chat agents that answer business phone lines and web chat, book appointments and capture leads around the clock. It does not touch your Title 31 program, and it should not; it just keeps the front-of-house calls from piling onto the same Monday your compliance office is already buried in.
Written by
Sagar Shankaran· Founder, CallSphere
LinkedInSagar Shankaran is the founder of CallSphere, where he builds production AI voice and chat agents deployed across healthcare, hospitality, real estate, and home services. He writes about agentic AI, LLM engineering, and shipping voice agents that handle real calls in production.
See how AI voice agents work for your industry. Live demo available -- no signup required.
Held-away 401(k)s, annuities and non-traded alts have no feed into Orion. How browser-driving AI agents cut five days out of the quarter-end reporting run.
Nobody built a connection between veterinary software and the state monitoring portal. Computer use closes that gap - with the limits an owner should insist on.
Carrier order portals and utility interval data have no export. Computer use lets an agent drive those screens, and pulls six days out of your billing cycle.
Two casino systems land in the EU AI Act high-risk bucket: face matching and marker scoring. What US gaming operators document, disclose and can ignore.
WH-347 uploads across LCPtracker, AASHTOWare CRL and B2Gnow cost a payroll clerk nine hours a week. What changes when a 2026 agent does the clicking work.
ServiceChannel, Corrigo and FMPilot eat 90 minutes a morning. What changes for a 90-site snow account when an agent drives the screen instead of a coordinator.
© 2026 CallSphere Inc. All rights reserved.
Made within San Francisco
Watch how CallSphere handles real customer calls, schedules appointments, and processes payments — live.
Try Live DemoBook a DemoCalculate Your ROI