By Brandy Tyler, VP of Product at CCT
A guest walks up to the cage with a ticket worth $5.41. The cashier scans it, opens the drawer, and realizes there are no pennies left.
From the guest’s perspective, it’s a small moment. From an operations perspective, it’s a policy decision.
In a casino, nothing ends at the point of transaction. That one-cent difference doesn’t disappear. It rolls into a shift report, into a vault balance, into reconciliation. Multiply that across thousands of transactions and you’re no longer talking about loose change. You’re talking about consistency.
With the U.S. Mint having ceased penny production in November 2025 and shortages already impacting circulation, casinos aren’t waiting for a policy debate. They’re managing the operational reality right now. Casinos won’t experience it as a cultural event. They’ll experience it in the mechanics of redemption. Ticket-in, ticket-out redemptions are where it becomes real. If a single ticket ends in one cent, you round.
But what if a guest redeems multiple tickets in one transaction? Do you round each individually? Do you round the total? Rounding the total payout is the obvious call. But that’s one decision among many. Every edge case needs a defined answer, consistenly applied across every shift, every cashier, and every cage window, and tracking those differences manually adds burden to an already detailed reconciliation process.
That burden starts at the cage. When rounding becomes routine, cashiers may carry small, expected differences at the end of their shifts. The amounts themselves are negligible. The challenge is what happens in reporting. If expected rounding differences look identical to true discrepancies, audit teams lose signal clarity. An investigation that used to take minutes may now take hours because the noise level has increased.
No one is worried about losing meaningful revenue over pennies—the real cost is operational friction. Teams will invest time defining rounding policies, updating procedures, and answering guest questions. In some cases, they may spend more energy solving the rounding issue than the rounding differences are worth.
This is where the compliance mindset becomes important. Before I worked in product, I wrote policies inside a casino environment. I rewrote SOPs across departments. I learned quickly that the smallest ambiguities in process tend to surface later, usually during audit. That background shapes how I look at changes like this.
A shift in available currency cannot introduce ambiguity into reconciliation. Whatever rounding decision a property makes must be traceable, defensible, and visible in reporting. Otherwise, you’ve created a recurring question inside your audit process.
In highly regulated industries, rigidity creates its own risk. Systems have to absorb change without requiring operators to rebuild structure from scratch. Currency configurations should adapt. Rounding logic should align with internal controls. Reporting should clearly distinguish expected differences from true discrepancies.
Configurability is not always the easiest path from a development standpoint. It introduces more testing scenarios and adds complexity behind the scenes. But that configurability is what allows operators to adapt to change without rewriting policies or reinventing reconciliation every time something shifts.
Over the past year, we’ve created more space within product to listen closely to operators. For a long time, much of our focus was on strengthening implementation, improving efficiency, and building stability. That work still matters. But as we grow, we also need to move earlier into operational gray areas — before small friction points turn into recurring questions for our customers. The elimination of the penny is exactly that kind of gray area. It won’t shut down the floor. It won’t trigger emergency meetings. It will show up quietly in coin inventory adjustments, in slightly different reconciliation totals, in the extra time an auditor spends confirming that a variance is expected and not something more serious.
Those are the moments we want to understand. If rounding policies are creating confusion, we want to see it. If reports are becoming harder to interpret, we want to know why. Often the most valuable product improvements don’t come from large feature requests. They come from small operational friction points that repeat every day.
Small changes reveal whether systems were built thoughtfully. That’s where we focus our energy at CCT — bridging the gap between what systems can automate and what teams are currently managing by hand.
In this industry, precision doesn’t happen by accident. It comes from clear policies, consistent processes, and systems that reflect both. When those pieces line up, even something as small as a denomination change doesn’t create confusion. The numbers still make sense. The reports still tell the truth.
And that’s the standard.
One cent should never be enough to make a team doubt what they’re seeing.
