How to reconcile a casino gaming day before the revenue close

Match slot, table, cage and approved count records by gaming day before preparing a journal for review. Give the auditor control totals, source-linked differences and a clear view of which areas are ready to close. Keep posting and variance disposition with authorized finance staff.

Define the gaming day and the evidence each area owes

Start with one property and one source pair, such as slot meter records and the approved count file. Write down the local cutoff, property and device identifiers, expected files, signs and control totals. For each area, document its approved reconciliation method. Date boundaries, movements between accounts and offsetting entries should be explicit.

The Nevada Gaming Control Board publishes separate minimum internal control standards for gaming operations, including slots and cage and credit. Casino Cash Trac also reported that Pearl River Resorts selected software for cage, vault and revenue audit. The control owner should decide which standards and operating procedures apply to the property’s systems and license. Nevada minimum internal control standards · Pearl River Resorts selection

Build an evidence trail from source to close

What to automate

Register the files expected for each gaming day

Create a source checklist by property, business day and control area for gaming, cage and count extracts. When files arrive, keep the original bytes, checksum, source version, arrival timestamp and source-reported totals. Match each file to its expected scope and check for repeated content, missing coverage and incorrect dates. A late or corrected source opens a review item for the originating team and keeps the affected area off the ready list.

Convert source codes to approved close definitions

Apply a versioned mapping for property, gaming day cutoff, device or table, cash location, currency, transaction codes and ledger accounts. Keep the original values and the map version for every normalized row. Use the approved sign and cutoff rules so each comparison uses the same basis. Keep missing mappings and unusual currency in a separate exception file. Finance reviews the map and approves changes before a rerun.

Keep variances visible before rolling up totals

Use each control area's approved source pair, reconciliation formula and tolerance. Compare at the device, table or cash location grain and keep both source references beside every difference. Report missing rows, out-of-balance items and distinct sources whose differences offset. A property-level zero can still have open items. Send differences to the authorized auditor with expected and observed amounts, age and resolution status.

Prepare a draft journal and an evidence packet

Build the close packet from validated files, source totals, open variances, approved dispositions and the journal mapping. Generate a draft with balanced debits and credits and label any area with an unresolved control as held. Include the run ID, mapping version and source references so a reviewer can reproduce the result. The authorized approvers verify readiness and record their decision under the property's division of duties.

Record posting acknowledgment and retain corrections

Submit an approved journal only through the existing posting process. Use a stable journal reference and reconcile the acknowledgment to the approved draft. If the response is missing, check the ledger by reference and escalate uncertainty before resubmission. Link the acknowledgment to the packet. If a corrected source arrives after posting, preserve the original and use the property's approved reopening, adjustment or reversal process.

Use deterministic reconciliation rules and approval thresholds. AI can summarize variance notes for an auditor. Keep the figures, comparison logic and authority to post in the accounting workflow.

Prove the workflow can hold a bad close

Run in parallel with the approved close and compare at transaction, device and ledger levels. Track time to prepare evidence, open variances by age, late areas and differences found on review. A fast packet only helps when the auditor can trace and reproduce the result.

Build the business-day control bridge

Use source staging tables for meter readings, count-room summaries, cage movements, payment/tender records and GL entries as approved for the property. For each source keep property_id, system, business_date, record_id, revision, currency, amount_minor, evidence_ref. Different systems can close at different times. The controller approves each source’s local business-day conversion and treatment of corrections.

1. Validate the source manifest before matching. Check sequence gaps, expected files, source totals, business date, currency, and revision. Preserve records from a restated source without mixing two revisions in the same signed run.
2. Match at the approved control grain. For example, aggregate a cage tender batch to one processor settlement record after matching batch IDs and separating fees. Show duplicate and unresolved records as their own bridge buckets. Meter rollover, reset and offline sessions need the property’s approved handling.
3. Emit check_id, business_date, expected_minor, observed_minor, delta_minor, threshold_version, evidence_refs, owner, status. Block signoff for unresolved critical differences and record the independent reviewer’s disposition. An AI summary may link the evidence, and only the authorized finance operator releases journals.
4. Load a signed prior day and reconcile each total from raw entries. Then inject one duplicated cage line, a late count and one amount on the wrong business date. Expect a hold on the affected reconciliation rather than automatic balancing through an adjustment.

WITH source_totals(kind, amount) AS (
  VALUES ('expected', 125000), ('observed', 124900)
)
SELECT SUM(CASE WHEN kind = 'expected' THEN amount ELSE -amount END)
       AS unresolved_minor
FROM source_totals;

The output is 100 minor units. The audit result depends on the approved control, threshold and reason. Store the difference even when a permitted reviewer accepts it.

Implement the work step by step

Use an approved gaming-day calendar, expected source manifest and signed reconciliation thresholds. Check source totals and cross-system matches separately, then send a journal draft for approval.

1. Collect the gaming day

• CAS-02.01.01 Verify gaming day input completeness. Validate manifest, checksum and timestamps. Create hold for missing feed. Read Expected extracts, gaming system meters, count, tables and cage. Record Approved input set to normalization. Owner Analyst obtains missing source from owning function. Check A missing expected cage extract holds the gaming day with its cutoff and owner.
• CAS-02.01.02 Capture late and corrected source. Retain immutable originals and link revised version to rerun. Read Corrected count/version and prior source manifest. Record Versioned input for affected audit area. Owner Source owner verifies correction. Analyst routes any post-close restatement. Check A corrected report gets a fresh checksum and replaces the affected version in staging.

2. Reconcile areas

• CAS-02.02.01 Normalize source keys and signs. Validate versioned maps and block unknown keys. Read Machine/table/location references and approved accounting map. Record Normalized audit records and unresolved mapping list. Owner Finance approves changes and traces map gaps to source. Check An unknown transaction type is quarantined before it affects the normalized totals.
• CAS-02.02.02 Compare source and destination totals. Calculate approved tests and preserve linked differences. Read Normalized meter, count, cage and table data. Record Control totals and variance register to audit owner. Owner Auditor reviews variances, segregation of duties and support. Check A balancing total cannot hide mismatched source and destination transaction references.

3. Resolve and approve

• CAS-02.03.01 Investigate material exceptions. Route case and preserve review history. AI summarizes notes with citations. Read Variance, original records and corrective notes. Record Approved disposition or open hold. Owner Independent auditor verifies evidence and reviewer authorization. Check A material difference stays open until the auditor records accepted evidence and disposition.
• CAS-02.03.02 Prepare and approve journal. Generate balanced proposal and require signed approval. Read Approved totals and exception status. Record Authorized journal and audit packet to GL. Owner Controller approves only through agreed posting control. Check A source revision invalidates the previous approval and requires a new balanced journal draft.

4. Post and retain

• CAS-02.04.01 Post approved result and verify receipt. Match stable journal ID and record acknowledgment. No unapproved posting. Read Signed journal and accounting system. Record Posted result with reference or held rejection. Owner GL operator releases and resolves rejected entries. Check A posting timeout triggers a status lookup and one ledger entry remains.
• CAS-02.04.02 Archive and control restatements. Archive full lineage. Compare revisions without overwrite. Read Close packet, approvals, journal ID and source snapshots. Record Archived close with versioned adjustment lineage. Owner Audit lead approves reopen/reversal workflow. Check A signed close and later authorized adjustment remain independently reproducible.

Build it yourself with AI

Create fake meters.csv, counts.csv and expected_sources.csv files for one gaming day, plus a small close-playbook.md containing the cutoff, required sources, mapping, tolerance and approval rules. Use fake property, device and account codes. Keep production gaming extracts out of the coding session.

Generate a Python command that accepts a gaming day and the supplied sample
files. Record checksums and source versions. Apply only the cutoff and signed
amount definitions in close-playbook.md. Reconcile expected and counted
amounts by device using decimal arithmetic. Emit control_totals.csv and
variances.csv with source row IDs. Hold any area with missing source,
unknown code or an unresolved difference under the playbook.

Set device A to 1,000 expected and 985 counted. Set device B to 985 expected and 1,000 counted. Expect two variances of opposite signs and a zero net property difference. The close packet should preserve both items and apply the approved hold rules at device level.

Add fixtures for opposite device differences, a repeated file, a late cage
file, a wrong business date and a corrected count after posting. Assert the
draft is never duplicated for the same approved input version. Generate a
balanced draft journal and review checklist when the supplied gates pass.
Use a simulated acknowledgment log keyed by journal reference. Do not post
to a ledger or change any authorized variance disposition.

If the auditor wants a summary, give AI a precomputed variance list with safe IDs. Ask it to group unresolved items by control area, copy amounts and references verbatim, and mark missing explanations as unknown. Compare the digest with the source-linked packet. Replay the existing close for several business days and have the controller verify differences, holds and acknowledgments before changing how the approved close operates.

Need help automating this?

Explore the related casino workflows for reconciling operating records, surfacing variances and preparing review evidence. Explore Mage's casino revenue reconciliation workflows.