Franchise Sales Crosscheck

Cross-check reported franchise royalty sales against POS records.

Description

Franchise royalty crosschecks compare reported sales with POS totals on a common period basis.

Franchise royalty crosschecks compare reported sales with POS totals on a common period basis.^[1]

Cross-check reported franchise royalty sales against POS records.

When to use Franchise Sales Crosscheck

Use this tool to cross-check reported franchise royalty sales against POS records.

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 Franchise Sales Crosscheck 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 reportedRoyaltySales, posRecordedSales, royaltyRatePercent, differenceTolerance using the field table and calculation rules, then run the tool.
Read unreportedSales, additionalRoyalty, salesDifferencePercent, withinTolerance. 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
reportedRoyaltySales	Reported royalty sales	number; minimum: 0	Required
posRecordedSales	POS-recorded sales	number; minimum: 0	Required
royaltyRatePercent	Royalty rate (%)	number; minimum: 0	Required
differenceTolerance	Sales difference tolerance	number; minimum: 0	Required

Enter nonnegative sales/rate/tolerance. Return signed difference, additional royalty, POS-normalized percentage and inclusive absolute-tolerance gate.

difference=POS−reported; royalty=max(0,difference)×rate%/100

Units, indexing, boundary conditions and exceptional cases are defined in the calculation rules above.

Output field	Meaning	Value type
unreportedSales	POS minus reported sales	number
additionalRoyalty	Additional royalty from positive difference	number; minimum: 0
salesDifferencePercent	Sales difference as POS share (%)	number
withinTolerance	Within supplied sales tolerance	boolean

json

{
  "input": {
    "reportedRoyaltySales": 900,
    "posRecordedSales": 1000,
    "royaltyRatePercent": 5,
    "differenceTolerance": 20
  },
  "output": {
    "unreportedSales": 100,
    "additionalRoyalty": 5,
    "salesDifferencePercent": 10,
    "withinTolerance": false
  }
}

Limitations and assumptions

Zero POS returns percentage zero. No source completeness, actual unreported sales or contractual royalty obligation is verified.

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 Casino Drop Reconciliation: Reconcile casino drop records with count-room and surveillance totals. For a complementary task, use Final Analytics Reconciliation: Recheck final analytical consistency after recorded corrections.

References

Franchise Sales Crosscheck — tool.io

Similar or alternative tools

Casino Drop Reconciliation
Reconcile casino drop records with count-room and surveillance totals.
Final Analytics Reconciliation
Recheck final analytical consistency after recorded corrections.