Casino Drop Reconciliation
Reconcile casino drop records with count-room and surveillance totals.
Description
Casino drop reconciliation compares count-room and surveillance totals with recorded drop on a common basis.
Casino drop reconciliation compares count-room and surveillance totals with recorded drop on a common basis.1
Reconcile casino drop records with count-room and surveillance totals.
When to use Casino Drop Reconciliation
Use this tool to reconcile casino drop records with count-room and surveillance totals.
Prepare the documented facts, aligned totals or expected/observed evidence labels requested. Choose applicable requirements and thresholds separately before interpreting a planning screen.
How to use Casino Drop Reconciliation and understand its results
- Prepare the documented facts, aligned totals or expected/observed evidence labels requested. Choose applicable requirements and thresholds separately before interpreting a planning screen.
- Enter tableDropRecords, countRoomTotal, surveillanceObservedTotal, tolerance using the field table and calculation rules, then run the tool.
- Read countDifference, surveillanceDifference, maximumAbsoluteDifference, reconciled. The explanation below defines the units, signs, ordering and any flags or placeholder values.
- If the tool reports an input issue, correct the values and run it again. Apply the stated assumptions when interpreting a successfully returned result.
| Input field | Meaning | Value type; see rules below | Requirement |
|---|---|---|---|
| tableDropRecords | Recorded table drop | number; minimum: 0 | Required |
| countRoomTotal | Count-room total | number; minimum: 0 | Required |
| surveillanceObservedTotal | Surveillance-observed total | number; minimum: 0 | Required |
| tolerance | Allowed difference | number; minimum: 0 | Required |
Enter nonnegative totals/tolerance; return signed differences, maximum absolute gap and inclusive gate.
differences=count−record, surveillance−record; gate=max(abs differences)≤tolerance Units, indexing, boundary conditions and exceptional cases are defined in the calculation rules above.
| Output field | Meaning | Value type |
|---|---|---|
| countDifference | Count-room minus table records | number |
| surveillanceDifference | Surveillance minus table records | number |
| maximumAbsoluteDifference | Maximum absolute difference | number; minimum: 0 |
| reconciled | All totals within tolerance | boolean |
{
"input": {
"tableDropRecords": 10000,
"countRoomTotal": 10005,
"surveillanceObservedTotal": 9998,
"tolerance": 5
},
"output": {
"countDifference": 5,
"surveillanceDifference": -2,
"maximumAbsoluteDifference": 5,
"reconciled": true
}
}Limitations and assumptions
No source evidence, count process or loss cause is examined.
Numeric inputs, where present, must be finite. Follow the calculation-specific rules for overflow, underflow and exceptional cases. Missing required fields, extra fields, wrong value types and violations of the calculation rules are input errors. A successfully returned false flag is an evaluated outcome; its meaning is explained above.
Alternative or Complementary methods
Use Franchise Sales Crosscheck: Cross-check reported franchise royalty sales against POS records. For a complementary task, use Brokerage Confirmation Reconciliation: Reconcile brokerage and custody confirmations with ledger holdings.
References
-
Casino Drop Reconciliation — tool.io
Similar or alternative tools
- Franchise Sales Crosscheck
Cross-check reported franchise royalty sales against POS records.
- Brokerage Confirmation Reconciliation
Reconcile brokerage and custody confirmations with ledger holdings.