← Playbook

Sales tax

Rate schedules with effective dates, and when a cabinet rate restates history.

4 minute read

You record the rate that applies from a given date. Operator X backs that rate out of every sale from that date forward to get net revenue, and every host share and profit figure is computed on net. The receipt itself — what the customer paid — never moves.

A later schedule row never reprices stamped sales. A cabinet jurisdiction rate does.

Adding a fleet schedule row applies to new sales only. Recording that a cabinet sits in a different tax jurisdiction restates every un-remitted sale on that cabinet: tax and net move, the receipt does not. A month already remitted or paid a host out on is refused visibly, not rewritten, so a statement you already sent still reconciles.

  1. Add the schedule before you sell

    Put the fleet default on file with the date it takes effect. A later schedule row will not reprice sales already stamped.

    Tax
  2. Set a cabinet's own rate when the jurisdiction differs

    That rate overrides the schedule for that cabinet and restates un-remitted history on it. Never edit an old schedule row — add a new one. The pair of rows is the audit trail.

With no schedule on file, net revenue equals gross charged and host shares are computed on the full amount. That is correct for tax-free goods and wrong for everything else.