How a Southern California Casino Filed 94,000 W-2Gs Through IRIS With Zero Rejections

In tax year 2025, a Southern California tribal casino filed 94,000+ W-2G information returns through the IRS Information Returns Intake System (IRIS). Across roughly twenty production batches, every batch was accepted by the IRS. No rejections. ~188,000 winner and payer PDFs delivered through a secure cloud portal. Six audit artifacts retained per batch. End-to-end through Morado as the IRS-listed transmitter.

If you operate a casino, sportsbook, racetrack, or tribal gaming enterprise generating thousands of W-2G obligations a year, this is what good looks like.

The numbers

Metric	Value
W-2G records filed in production	94,000+
Production batches transmitted	~20 (5,000 records each)
IRS rejection rate	0%
Issue classes auto-detected pre-submission	100+
PDFs generated and delivered	~188,000
Audit artifacts retained per batch	6
End-to-end transmission per batch	Minutes
IRS authentication	mTLS + OAuth2 JWT (RS256), direct as Transmitter

The customer

A regional Southern California tribal casino. Slot floor, table games, and ancillary gaming activity producing reportable W-2G events at high volume. Tax operations function staffed in the single digits. Pre-Morado, the team was running spreadsheets through a manual process with no programmatic IRIS connectivity. They came to Morado in early 2026 with a year of accumulated W-2G obligations, a hard regulatory deadline, and a mandate to file every record on time, with zero rejections, and a complete audit trail.

The volume alone made the spreadsheet workflow unsustainable. The schema rigidity of the IRIS XML format made vendor selection critical. And the obligation to furnish 94,000 winner-ready PDFs made distribution its own engineering problem.

The challenge

W-2G filing at this scale has three teeth.

Volume. 94,000 records is too many for any human-in-the-loop spreadsheet workflow. One stray apostrophe, one ZIP code that arrived as a float, one transaction ID with 21 characters instead of 20, and the IRS rejects the whole submission. Or accepts with errors that cascade into B-notice penalties next year.

Schema rigidity. The IRIS XML schema (TY2025, v1.1) is unforgiving on element ordering, character classes, length limits, and conditional requirements. The companion business rules layer adds semantic checks: TIN/name matching, transmitter-vs-issuer separation, RecipientAccountNum uniqueness, ATS-versus-production TIN prefixes. Each is a tripwire.

Distribution. Even after filing succeeds, the casino has to furnish a Copy B/C/2 to each winner and retain a Copy D for its own records. 94,000 jackpots means ~188,000 PDFs, structured by copy type, distributed cleanly. Click-to-generate tools time out long before they finish.

How Morado handled it

Morado runs an end-to-end IRS filing pipeline. Not pre-processing, not data cleanup, not a thin SaaS wrapper around an Excel template. The casino's spreadsheets entered Morado, and accepted IRS filings came out the other side.

The pipeline:

Ingestion. XLSX files uploaded to a project workspace.
Header categorization. Operator confirms which spreadsheet column maps to which IRS field. Heuristic auto-suggestions catch >90% of headers.
Pre-flight Excel validation. Every issue class the IRS would catch, flagged before transmission. (More on this below.)
Canonical normalization. Dates, names, ZIPs, money fields, TINs, addresses, all normalized to a canonical JSON representation.
XML generation. IRIS A2A XML built directly against the TY2025 v1.1 schema. Every transmission locally validated with xmllint --schema before it leaves Morado infrastructure.
Direct IRS submission. mTLS to the IRIS A2A endpoint, OAuth2 JWT bearer (RS256), Morado's transmitter TCC on the wire, the casino's TCC as the issuer. No middleman.
Status polling. Receipt IDs polled directly against IRIS until final disposition.
PDF generation and delivery. All ~188,000 PDFs generated against the official IRS templates and delivered through a secure cloud portal.
Audit trail. Six artifacts preserved per batch, addressable for years.

What made it work

Three things separate Morado from "we know how to call the IRIS API."

Pre-flight validation that catches what the IRS would reject

Most filing vendors transmit your spreadsheet and let the IRS tell you what's wrong. By then, you've consumed your transmission window and may owe the operator a re-file.

For this engagement, Morado ran a dedicated W-2G validator (~400 lines, against the raw XLSX) that flagged every issue class the IRS schema or business rules would catch. A short list of what it caught:

SSNs missing leading zeros (Excel float-formatting hazard)
5,337 multi-word names requiring careful first/last/suffix split (including 1,010 names with exactly four words and the Hispanic two-part-name convention ANA PATRICIA FLORES RODRIGUEZ with a double-space delimiter)
Apostrophe stripping in last names (D'ERCOLE → DERCOLE)
Periods, hash symbols, and double spaces in addresses
ZIP codes parsed as floats (92127.0 → 92127)
ISO datetimes where YYYY-MM-DD was expected
Excel "no value" dashes that currency.js parses as NaN
119 duplicate transaction IDs
17 transaction IDs over the 20-character IRIS limit
16,186 same-day multi-win combinations surfaced for operator confirmation

Every issue was triaged before a single record entered IRIS.

IRS rule encoding, not IRS rule documentation

Morado has internalized the IRIS business rules into validation, generation, and submission logic. The transmitter (Morado) is correctly separated from the issuer (the casino, with its own TCC), a TMFST002_001 violation we see legacy vendors trip on routinely. RecipientAccountNum is auto-populated as the record index, satisfying FS1H001 uniqueness and giving every record a stable identifier for corrections. Optional groups like JuratSignatureGrp are omitted, not stubbed with vendor defaults, so vendor identity never leaks into the casino's filing.

Direct IRS submission as a transmitter

Morado is on the IRS list as a Transmitter A2A. Submissions go directly from Morado infrastructure to api.www4.irs.gov over mTLS, authenticated with an OAuth2 JWT bearer token. No reseller arrangement, no queue behind another vendor, no third-hand incident response. When IRIS has an issue, we see it and respond.

The results

94,000+ records filed in production across ~20 batches.
0% rejection rate. Every batch accepted or accepted with errors. None rejected.
43 unique TIN/name mismatches flagged as Report Error findings. The operator follows up via B-notice. (These are surfaced findings, not rejections. The submissions still went through.)
~188,000 PDFs generated against the official IRS templates and delivered through a secure cloud portal.
Six audit artifacts retained per batch at a stable, addressable path.
Pre-flight validation surfaced 100+ issue classes before any record left for IRIS.

"Morado caught issues in our data we didn't know were issues, transmitted every batch directly to IRIS as our transmitter, and gave us a downloadable record of every filing the IRS accepted. Zero rejections across 94,000 records."

— Tax Operations Lead, Southern California tribal casino

What this means for your casino

If you operate a casino, sportsbook, racetrack, or tribal gaming enterprise generating thousands of W-2G obligations a year, you have three options:

Hand-roll spreadsheets through a CPA. Cheap until your first IRS rejection or B-notice cascade. Doesn't scale beyond a few thousand records.
License a legacy filing tool. Schema-rigid, vendor-locked, often a reseller arrangement, no real audit trail, and most don't deliver winner PDFs at scale.
File through Morado. End-to-end IRS filing as a direct A2A transmitter, pre-flight validation, IRS rule encoding, full audit trail, ~188,000 PDFs delivered through a cloud portal, production-proven at 94,000 records.

Book a Call

A 30-minute call with a Morado engineer. We'll walk through the pipeline against a sample of your real data and answer every question your tax operations team has.

Book a Call →

Frequently asked questions

Is Morado a Transmitter or a reseller? Direct IRS-listed Transmitter A2A. Submissions go directly from Morado to the IRS over mTLS. No middleman, no reseller queue.

What happens if the IRS rejects a batch? At 94,000 records across ~20 batches, none were rejected. If a batch were ever rejected, Morado retains the original spreadsheet, canonical JSON, transmitted XML, and IRS receipt. Corrections are a structured update against a known prior submission, not a guess.

Can Morado handle 1099 forms beyond W-2G? Yes. IRIS accepts the full 1099 series; Morado files all of them. Morado also files 1042-S directly via MeF.

How does Morado handle PII at scale? Morado's "all same form type" path bypasses any LLM inference for single-form-type batches like W-2G. Row data does not leave the operator's session. Storage is per-project, per-user, with row-level security enforced at the database layer.

What's the audit trail look like? Six artifacts per batch, retained at a stable path: original XLSX, canonical JSON, payer config, transmitted XML, IRS submission acknowledgment, IRS status response. Retrievable for years.

Where can I see Morado against my own data? Book a 30-minute call →. We'll walk through the pipeline against a sample of your real records.

How does this work with the FIRE-to-IRIS transition? FIRE retires December 31, 2026. Morado already files exclusively through IRIS for the 1099 series and W-2G, and through MeF for 1042-S. Read the full FIRE-to-IRIS transition guide →

Morado is an end-to-end IRS filing platform for 1099, 1042-S, and W-2G information returns. Direct IRIS A2A transmitter. Direct MeF connectivity for 1042. Production-certified. Built for operators who care about getting it right the first time.

Morado's IRS Transmitter A2A status is publicly listed in IRS Publication 5718 (the IRIS Implementation Guide).