Why Seed-to-Sale and Financial Records Diverge
The two systems are maintained by different people for different purposes. Compliance staff log physical events; accounting staff log financial events, and nobody owns the join between them by default.
Divergence shows up as untracked samples and promotional product, waste that was disposed of physically but never recorded financially, repackaging that breaks unit-cost lineage, transfer manifests received into inventory at the wrong cost, returns processed in only one system, and manual adjustments made to clear a compliance flag without a matching 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 lands on a computed ending balance that is compared against both the physical count and the seed-to-sale system balance.
Every difference is classified as timing, documentation gap, costing error, physical loss, or system error. Timing and documentation items get cleared. Physical losses are written off with support. Costing errors are corrected at the source so they stop recurring.
Cost Layer Integrity Through Transformation
Manufacturers and processors face a harder version of the problem. When flower converts to extract and extract converts into finished units, the tracked identifiers change, and cost has to follow the material through each transformation with a defensible allocation method.
We define the conversion costing rules up front, yield assumptions, joint and by-product allocation, processing labor and overhead absorption, and apply them consistently so finished goods carry a cost that can be explained line by line to an examiner or an auditor.
Compliance Value and Audit Defense
ADHS and ADOR both draw on seed-to-sale and financial data during examinations. Unexplained inventory disappearance raises diversion questions; unexplained inventory appearance raises unreported-purchase questions. Either way, an unprepared operator is answering questions with data it never actually reviewed.
A monthly reconciliation with signed workpapers changes that posture entirely, and it directly supports the ending inventory figure on the tax return, which is the single most examined number on a cannabis filing.
- 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 an ADHS, ADOR or IRS inventory inquiry
Systems and Integrations
We work with the seed-to-sale, POS and ERP platforms Arizona operators actually run, including METRC and comparable seed-to-sale systems used by multi-state operators, and we are candid about where the integrations break down. 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 blindly.
Where an integration cannot be trusted, we build a structured import and reconciliation process instead. It is slower, but it is auditable, and that is the trade an examination will reward.
What a Real Three-Way Reconciliation Looks Like
The reconciliation that matters compares three independent records of the same item: the seed-to-sale package quantity, 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 the seed-to-sale system, 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 the seed-to-sale system, 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
Inventory discrepancies are a licensing issue before they are an accounting issue. ADHS can and does cite marijuana establishments for inventory verification failures, and unexplained variance is a common finding during 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 Valley-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 a state inspection or an IRS information document request is answered from an existing file rather than a scramble.
