A Florida reconciliation workbook works best when the join key is the package or lot identifier rather than the SKU. Once you have that join, the checks that actually matter are product-master mapping, location and manifest state, and MMUR route and allotment logic. Start from SKU matching and you will miss the failures that get you in trouble here.

Three exports in, one queue out

The workbook draws from three sources and funnels disagreements into an exception queue:

  • BioTrack export: active package or lot detail with room, quantity, status, product type, and unique product ID.
  • POS export: package-level inventory, catalog mapping, room, sales, voids, and returns.
  • MMUR dispensation export: order, route, dispensation history, amount remaining, and amount eligible.

The tabs that do the work

Beyond the raw exports, each of these tabs tests a specific Florida risk:

  • Package match: the primary join between state lot ID and POS package ID.
  • Quantity variance: BioTrack vs POS vs physical.
  • Route and category mapping: MMUR form vs product type and external category.
  • THC reconciliation: expected milligrams vs the route-level dispensation total.
  • Smoking reconciliation: grams or ounces dispensed against the rolling 35-day history.
  • Transfer reconciliation: sent vs received vs rejected by manifest.
  • Adjustment audit: quantity changes with reason, user, and note.
  • Failed-sync queue: unmatched receipts, API errors, packages not posted.

The standard checks

A handful of checks catch most Florida failures:

Package match:      state lot/package ID  ==  POS package ID
Duplicate package:  flag any package ID repeated or mapped to 2+ SKUs/rooms
Quantity variance:  BioTrack Qty - POS Qty
                    Physical Qty - BioTrack Qty
                    Physical Qty - POS Qty
THC mg check:       units x mg-per-unit  vs  route-level mg dispensed
Smoking check:      ounces and grams consistent  (1 oz = 28.35 g)
Transfer aging:     sent but not received; manifest open; delivery packed past due
Adjustment audit:   flag blank, generic, or duplicate reasons

Run the package match first. The same product can live in multiple packages, and the package-level key is the only thing that keeps traceability intact. The duplicate-package and adjustment-reason checks pick up failures that a plain quantity variance never shows.

Return and void logic

Test whether return lines created new destroy-only packages, and whether voids actually restored inventory. In Florida a void returns product to inventory and a refund does not. If you skip this check, the register can balance while the inventory state underneath is wrong.

A daily cadence

The workbook supports a fixed daily rhythm:

  • Open with a room-level package spot check.
  • Review unmatched receipts and sync failures.
  • Review transfers and delivery holds before sales begin.
  • Close with package-level variance review for flower, high-volume vape SKUs, and every newly adjusted package.
  • Then review MMUR exceptions and route mismatches before the next-day open.

Where to anchor the workbook

The package or lot ID is what everything else hangs off of. Product mapping, location, and MMUR route are the tests that surface the Florida-specific risk a quantity count hides. Anchor the build on the package key and the workbook ends up flagging exceptions for you instead of producing another report nobody opens.