Why Track-and-Trace and Financial Records Diverge
The two systems are maintained by different people for different purposes. Compliance staff record physical events; accounting staff record financial events. Nobody owns the join between them by default.
Divergence is created by untracked samples and promotional product, waste recorded physically but not financially, repackaging and remediation that changes package identity, transfer manifests received into inventory at the wrong cost, returns processed in one system only, and manual adjustments made to clear a compliance error without a corresponding journal entry.
- Sampling, R&D and employee product not costed out of inventory
- Waste and destruction events with no financial write-off
- Repackaging and conversion that breaks unit-cost lineage
- Manifest quantities that do not match receiving quantities
The Reconciliation Framework
We build a period-end rollforward that starts with opening inventory by package or SKU, adds receipts per transfer manifests, subtracts sales per POS or invoices, subtracts documented waste and conversion, and arrives at a computed ending balance that is compared to both the physical count and the track-and-trace balance.
Every difference is classified: timing, documentation, costing error, physical loss, or system error. Timing and documentation items are cleared. Physical losses are written off with support. Costing errors are corrected at the source so they do not recur.
Cost Layer Integrity Through Transformation
Manufacturers and distributors face a harder version of the problem. When flower is converted to extract and extract into finished units, the unique identifiers change and the cost has to follow the material through the transformation with a defensible allocation.
We define the conversion costing rules in advance — yield assumptions, joint and by-product allocation, processing labor and overhead absorption — and apply them consistently so that finished goods carry a cost that can be explained line by line.
Compliance Value and Audit Defense
The Department of Cannabis Control and CDTFA both look at track-and-trace data. Unexplained inventory disappearance invites questions about diversion, and unexplained inventory appearance invites questions about unreported purchases. Either way, the operator is answering questions with data it did not prepare.
A monthly reconciliation with signed workpapers changes that posture entirely. It also directly supports the inventory figure on the tax return, which is the single most examined number on a cannabis return.
- Signed monthly reconciliation workpapers retained with the tax file
- Variance log with root cause and remediation owner
- Physical count procedures and count sheet retention
- Support package ready for regulator or IRS inventory inquiry
Systems and Integrations
We work with the seed-to-sale, POS and ERP platforms California operators actually use, and we are candid about where integrations break. Automated syncs handle volume but propagate costing errors at scale, so the control has to sit on top of the integration rather than trusting it.
Where an integration cannot be trusted, we build a structured import and reconciliation process instead, which is slower but auditable.
What a Real Three-Way Reconciliation Looks Like
The reconciliation that matters compares three independent records of the same item: state track-and-trace package quantities, the point-of-sale or inventory subledger, and the general ledger inventory balance. Agreement across all three is the only credible statement that inventory is right. Two out of three is a coincidence.
We run it monthly at package and category level. Variances are classified rather than plugged: receiving errors where a transfer was accepted in one system and not the other, sales voids that reversed in the POS but not in track-and-trace, unrecorded waste and destruction, sampling and testing pulls, and genuine shrinkage. Each classification points at a different operational fix, and the classification itself is the audit documentation.
For a multi-location retailer, we run the reconciliation by license and then consolidate, because a variance that nets to nothing across three stores is usually two problems hiding each other.
- Package-level quantity comparison across METRC, subledger and ledger
- Variance classification with operational root cause, not plug entries
- Documented waste, destruction, sampling and testing adjustments
- Escalation thresholds and a signed monthly reconciliation record
Compliance Consequences and the Audit Trail
Track-and-trace discrepancies are a licensing issue before they are an accounting issue. The Department of Cannabis Control can and does cite operators for inventory reconciliation failures, and unexplained variance is a common finding in a state inspection. The same records also carry the federal tax burden, because ending inventory determines COGS and COGS is the only relief 280E allows.
A Bay Area distributor we work with had a persistent 2 percent variance that turned out to be transfer packages accepted at the dock but recorded a day later at a different weight after moisture loss. Once the receiving procedure captured weight at acceptance and the accounting policy documented normal moisture variance, both the compliance exception and the costing error disappeared.
Every reconciliation is retained with its supporting exports so that a state inspection or an IRS information document request is answered from an existing file rather than a scramble.
