Nevada proposes new pari-mutuel controls effective 1 October 2027
The draft would require at least 26 report types, 60-day location recordings and no manual tickets during system failure.
The Nevada Gaming Control Board (NGCB) has proposed Technical Standard 9, covering the integrity and accounting of computerised pari-mutuel systems. The draft is dated 9 November 2026 and is issued pursuant to Nevada Gaming Commission Regulation 14.050. It remains a proposal and states 1 October 2027 as its proposed effective date.
System and payout controls
Technical Standard 9 would require pari-mutuel systems to comply with Regulation 22 and chapter 463 unless they conflict with the new standard. Systems would have to:
- prevent off-track pari-mutuel wagers from being accepted at post time;
- make off-track pari-mutuel sports wagers final when the sporting or other event starts;
- operate with full redundancy;
- aggregate pool information separately received from each pari-mutuel sports book;
- report pool data to each book at intervals approved by the Chair;
- report results and payoffs after each event; and
- produce the accounting and reconciliation reports required by the Chair.
All pari-mutuel wagers would have to pass through the system. If a connection between a pari-mutuel book and the hub failed, the book could not issue manually written tickets.
The system would also have to create a restricted record at the same time as the original betting ticket. Book employees could access that record only through inquiry functions, while documentation produced by the system would be restricted to authorised personnel.
The draft would require systems to be configurable to return at least $1.05 for each winning dollar wagered. Unless an agreement approved under Regulation 26B.140 applied, the total commission deducted by Nevada pari-mutuel sports books from off-track pari-mutuel sports wagers could not exceed 25%.
For payouts, systems could not authorise payment of a previously paid, voided, losing or unissued ticket or wagering instrument. Winning account wagers would have to be credited to the patron’s wagering account as soon as the event officially concluded or when an employee confirmed the results. Before a ticket payout or account credit, results would have to be entered for computerised grading of all wagers.
For account wagers, posting the event results would automatically authorise payment of winning wagers and update the patron’s account.
Account and location evidence
Systems supporting wagering accounts would have to be configurable for deposits, withdrawals, credits and debits in accordance with Regulation 5.225. They could not accept an off-track horse-race wagering communication until the patron had created an account meeting Regulation 5.225(5) to (7).
Once the patron had reviewed and confirmed the wagering information and the transaction was complete, the system would have to prevent the wager from being changed.
For communications other than voice-only technology, the system would have to create a confirmation record and allow the patron to review and confirm all wagering information before acceptance. That confirmation record would be the “actual transaction of record”, regardless of what wager the system recorded. The system would also have to produce a printable record of the full transaction and reject wagering communications if the printing system was inoperable.
Before accepting a pari-mutuel wager or communication through an account, the system would have to record confirmation and patron affirmation that the patron was physically in Nevada. The draft gives an electronic or voice-only inquiry at the time of each communication as an example of reasonable location assurance. A recording of that inquiry would have to be retained for 60 days.
The same 60-day retention period would apply to call-centre wagering instructions and other wagering communications. Account wagers would require an electronic record of their terms immediately upon acceptance.
Those requirements create separate evidence obligations for account systems, call centres and mobile wagering channels. A system’s internal transaction record would not, on its own, displace the confirmed transaction record required for non-voice communications.
Reports, revenue and timing
In addition to the reports required by General Technical Standard 7.090, the proposal would require at least 26 report types. They include writer and cashier summaries, transaction and teller reports, race prices, cashed tickets, refunds, futures wagers, unpaid winners, unredeemed wagering instruments, daily account activity, account reconciliations and month-end revenue reconciliations.
The draft would also require a system exception report covering unusual events such as void authorisations, manually paid tickets, changes to configuration parameters and alterations to initially recorded data. An exception history report would record the time, employee and dollar amount for relevant exceptions. A separate void exception report would identify the ticket, time, station, writer or cashier, approving supervisor and ticket description.
Account reporting would extend to every wagering account regardless of balance. The proposed activity detail report would record each account’s deposits, withdrawals, wagers, void wagers, winning wagers, refunds, adjustments and ending balance. The summary report would include the patron’s name, the book’s name, beginning balance, deposits, wagers, winning wagers, withdrawals, adjustments and ending balance. Daily, month-to-date, year-to-date and two-year cumulative amounts could appear in separate reports.
The proposed configuration rules would define pari-mutuel gross revenue as commission on wagers, pool amounts retained because patrons did not win, unpaid winning tickets and breakage, less rights fees and commission returned to patrons under specified provisions. Amounts wagered by a book, and payments received on those wagers, would not affect the book’s gross gaming revenue calculation.
The Chair could waive any Technical Standard 9 requirement for good cause under Regulation 14.260(8).
Technical Standard 9 is part of a wider set of NGCB drafts dated 9 November. The Board has separately proposed Technical Standard 8 for computerised race and sports systems and Technical Standard 12 for cashless wagering and wagering account systems.
Atlas's records show that the NGCB has also taken enforcement action over alleged unlawful event wagering in Nevada against Polymarket, Coinbase and KalshiEX.
If adopted, the proposed Technical Standard 9 would take effect on 1 October 2027.
Permanent link to this Atlas analysis
Related Atlas analysis
Continue with coverage connected by market, topic and operating context.
- United StatesNevada finalises 10 revised gaming-device standards effective 13 DecemberThe revisions consolidate and update existing standards after a 7 October public workshop and consideration of comments.
- SlovakiaSlovakia’s MIRRI bill awaits Parliament before planned 1 January national AI frameworkThe proposal would place a National Centre for Artificial Intelligence and Data within MIRRI, combining statutory supervision with advice and business support.
- United StatesIllinois bill would require venues to offer cashless video gaming from July 2027Licensed establishments would need Illinois Gaming Board approval for their systems, while patrons could choose whether to use cashless wagering.
Continue with Atlas
Move from this development into the relevant research, comparison and workflow.
- Gambling compliance software guideSee the research, monitoring, ownership and evidence a useful platform should connect.
- Atlas vs VixioCompare gambling research, change monitoring, workflow, technical work and evidence.
- Monitoring and alertsFollow a relevant change from detection through accountable implementation.