Why is a missing day not the same as a zero?
Because a weekly total cannot tell you which you have. A store that closed for a power outage on Tuesday and a store whose register never sent Tuesday’s batch both show six days of sales. The first is correct; the second is under-reported, and royalty computed on it is short. If the franchisor polls the register directly, as Wingstop’s agreement allows[1], it may see the missing day before you do. Recording “closed, zero sales” as a fact on the day turns an ambiguous gap into a checked answer.
How do you find unreported days?
- Expect a sales record for every store for every trading day, and flag the day that is absent — not the week that looks low.
- Keep a calendar of known closures (holidays, remodels, weather) so an expected zero is not flagged and an unexpected one is.
- Check that card settlements exist for the day: a store with card deposits and no sales record traded and did not report.
- Resolve each gap the same week, before the royalty week closes; after that, the fix is a restatement.
Why do sales get restated?
Late-arriving transactions (an offline register syncing days later), voids and refunds processed after the day closed, a delivery order adjusted by the marketplace, a manager correcting a mis-rung tender, or a gift-card batch posted to the wrong date. Each changes a day that has already been reported, and often a day whose royalty has already been debited.
How should a restatement flow into royalty?
As a delta on the next payment, never as an edit to the one already made. Editing a posted royalty bill changes a document the franchisor already acted on and leaves no trail of why; a separate adjustment line does the opposite.
Week ending Sat 12 Sep, reported and debited on Tue 15 Sep Gross sales per the definition 41,860.00 Royalty at 6% 2,511.60 (posted, paid) Wed 16 Sep: an offline register syncs Tue 8 Sep restated from 5,940.00 to 6,480.00 +540.00 Next royalty (week ending Sat 19 Sep) Royalty on the week 2,604.00 Adjustment: 8 Sep restated, 540 × 6% 32.40 Total due 2,636.40
What does the audit trail need to show?
For each royalty week: the sales per day as first reported, each restatement with the date it arrived and the reason, and the adjustment line that carried it. That is the file an auditor asks for, and it is what protects you against an audit cost clause — Wingstop’s shifts the audit’s cost to the franchisee where Gross Sales were understated by 1% or more[1]. The same discipline applies to hotels reporting monthly: a late folio adjustment after the monthly fees were paid on gross room sales[2] belongs on the next month’s report as an adjustment.
Why is this worth the trouble?
Because the numbers are small per day and large per audit. A missed day a month across thirty stores is 360 store-days a year of unreported sales. The franchisor’s disclosure document tells you whether it can see your register data independently — the FTC Franchise Rule requires Item 11 to say so[3] — and if it can, the question is not whether the gap is found but who finds it first.
How Kite does this
Kite expects a sales day from every store every trading day and raises the one that is missing the next morning, naming the store and the date. A closed day is recorded as an explicit zero. When a day is restated after its royalty was paid, Kite drafts the difference as a separate charge on the next payment — a delta, never an edit to the posted bill — so the trail shows what was reported, what changed and when.
How Kite runs restaurant booksSources
- [1]Wingstop 2025 Franchise Disclosure Document (issued 28 March 2025), franchise agreement §7 — Wingstop Franchising LLC
- [2]Fairfield by Marriott 2024 Franchise Disclosure Document (issued 31 March 2024), Item 6 — Marriott International
- [3]16 CFR § 436.5 — Disclosure items (Item 11) — Electronic Code of Federal Regulations