An efficient Florida reconciliation workbook is built around one master join key and three secondary tests. The master key is the package or lot identifier. The secondary tests are product-master mapping, location and manifest state, and MMUR route and allotment logic. A workbook that starts from SKU matching instead of package matching misses the riskiest Florida failures.

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 high-value tabs

Beyond the raw exports, the tabs that earn their place are the ones that test 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 before they become inspection problems:

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

The package match runs first because the same product can exist in multiple packages, and only the package-level key preserves traceability. The duplicate-package and adjustment-reason checks catch the quiet failures that quantity variance alone will not surface.

Return and void logic

One check deserves to be explicit: test whether return lines created new destroy-only packages, and whether voids actually restored inventory. Because refund and void diverge in Florida, where void returns product and refund does not, a workbook that doesn't test this will show a balanced register over a broken inventory state.

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.

Build from the package key out

The package or lot ID is the spine of the workbook. Product mapping, location, and MMUR route are the three tests that catch the Florida-specific risk quantity alone hides. Build from the package key out and the workbook becomes an exception engine rather than a daily report nobody reads.