Glossary
Metrc receipt
The sales record a POS pushes to Metrc for each ticket: packages (by tag), quantities, totals and the state's five tax fields. The thing a POS ticket must match to in daily reconciliation.
Why it matters for reconciliation: this is the record the state holds for each sale, so a ticket without one, or a receipt without a ticket, is a gap in reporting. The daily match compares them line by line.
Example: a ticket shows two packages and a total, while the receipt in Metrc shows the same packages but a different tax split. The packages and quantities match, so the problem is in the POS's tax-line mapping. Fixing the mapping fixes every later receipt, instead of editing this one.
Where this comes up on budally.com
- Metrc for dispensaries: what it records, and how a store reconciles against it
- Metrc reconciliation for dispensaries: the daily, weekly and 30-day procedure
- NMS2S vs BioTrack vs Metrc: what changed for New Mexico operators
- Dispensary POS comparison 2026: Dutchie vs Treez vs Flowhub vs Cova vs BLAZE, judged on what an operations team actually needs
- BLAZE alternatives 2026: what to weigh before you leave BLAZE, and who to look at
- Cova POS alternatives 2026: what Cova does well, why operators look elsewhere, and who to compare
- Dutchie alternatives in 2026: switch POS, or keep Dutchie and add a layer
- Flowhub alternatives 2026: what to weigh before you leave Flowhub, and who to look at
Related terms
- External receipt number (Metrc)
The POS receipt number a POS sends to Metrc with a sales receipt. Metrc's API can look up a receipt by it, which is how an operations layer joins POS tickets to Metrc receipts when the POS doesn't expose the Metrc receipt ID.
- Sales recon
The daily match of POS tickets to state-system receipts (Metrc receipts or NMS2S ticket IDs) on packages, quantities and totals, with a match rate shown per store.