Nothing gets paid until it matches Metrc

Every week, deliveries roll into your back room and the invoices stack up behind them. You receive the boxes, you check the count looks about right, and at some point you sit down to pay. The invoice tells you what you owe, so you cut the check. Most of the time that's the whole story, and most of the time it's fine.

But the invoice is the one document in that whole chain that nobody outside the vendor's office actually verified. It's the vendor's count of what they say they shipped and what they say you owe. Pay straight off it and you're trusting a number against boxes you glanced at, not against the record of what the state says crossed your door. In cannabis, you have that record. It's Metrc.

This is about the one check ShelfSpace runs before a single dollar moves: every wholesale invoice gets compared against your Metrc manifests, and ShelfiQ tells you whether it's safe to pay. Here's how it works, and why it means you never pay an invoice nobody checked.

The invoice is just the vendor's word

An invoice is a claim. It's a count someone in the vendor's office typed up: these products, these quantities, this total. Metrc is the other side of the same delivery — the state's record of which packages actually transferred to your license, logged at the source and locked once it's there. When the two agree, you're paying for exactly what arrived. When they don't, the invoice is the version that's easy to get wrong.

None of this means your vendor is cheating you. Deliveries are messy. A package gets left on the truck, a transfer gets created late and hasn't synced yet, a line gets keyed twice, a driver grabs the wrong manifest. The point isn't suspicion. The point is that you and your vendor both want to settle on what really showed up, and Metrc is the shared record that settles it. Checking the invoice against it protects both sides from an honest mistake becoming a payment you can't claw back.

The moment you click "Approve for Payment"

On a wholesale delivery, moving it toward payment is a deliberate step. You mark it reviewed, then you approve it for payment, and that approval is what creates the purchase order the check pays against. The instant you reach for that button, ShelfiQ doesn't just flip a status. It launches an investigation against your Metrc manifests and holds the approve button until it has an answer.

Here's the whole pipeline, from the click to the cleared check:

A recommendation, not a roadblock

ShelfiQ reads the delivery and comes back with one of four answers. Each one names a next step, so you're never left staring at a wall of manifest jargon trying to figure out what to do:

1. Reconciles with Metrc. The invoice lines up with the manifest. Green light, safe to approve.
2. Link the right manifest. ShelfiQ found the correct transfer that should be bound to this order. One click links it, the check re-runs in place, and then you approve.
3. Take a closer look. There's a real mismatch — a line on the invoice that isn't on any manifest, for instance. Put it on hold, or open Troubleshoot with ShelfiQ to dig in. Don't approve until it's sorted.
4. Approve with your eyes open. There's no clean manifest to check against, usually because a transfer hasn't synced. ShelfiQ tells you that, shows its confidence, and recommends the safe move.

That fourth case is the one in the screen above, and it's the one that shows what makes this trustworthy. ShelfiQ couldn't find a matching transfer, and the sync looked stale: zero transfers in 24 hours. It didn't pretend the invoice was verified, and it didn't freeze you out either. It told you it was about 70% confident, explained why, and recommended acknowledging the gap and paying. It won't act certain when it isn't, and it won't hide the doubt from you to look smarter.

You always make the call

ShelfiQ never pays anything on its own. It reviews, it recommends, and it shows its work. What's nice is that the buttons agree with the advice. When ShelfiQ says it's safe, "Approve for Payment" sits there as the primary button. When it says don't pay yet, the loudest button quietly becomes "Put on Hold," and approving demotes to a muted "Approve anyway." You can still override it — it's your money and your vendor relationship — but you'd be doing it against the recommendation, on the record, not by accident.

If ShelfiQ found the correct manifest, the primary button turns into a one-click "Link to manifest" instead. Link it, the check re-runs against Metrc on the spot, and if it goes green you approve from the clean state. Linking and approving stay two separate steps on purpose, so you never pay your way past a discrepancy without seeing it resolve first.

The check gets checked again

Approving for payment isn't the end of the verification. It's the first of two passes. When you actually cut the check, the platform re-runs the Metrc check from scratch — not the cached verdict from when you reviewed, a fresh comparison at the moment of payment. If the order doesn't reconcile against its Metrc manifest right then, the payment stops and asks you to acknowledge before it lets the money move.

Why run it twice? Because time passes between review and payment. A transfer that hadn't synced when you approved might have landed an hour later. The live re-check catches that, so a delivery you waved through on a stale sync gets a second, current look before the check leaves your account. Two passes, two different moments, one shared record.

Once a payment clears the gate, the vendor gets a clean, itemized check they can deposit. If you want to see what lands on their end, walk through the anatomy of a vendor invoice payment — the remittance summary and the Check 21 check that comes out the other side.

Paying an invoice versus paying the right invoice

Over a year, a single store approves thousands of invoices. The $2,847.50 in the example is one delivery. Even if the invoice is right 99 times out of 100, the hundredth — the short package, the doubled line, the transfer that never came — is the one that quietly costs you, because there was never a moment in your old workflow where anything compared the bill to the boxes. We've seen exactly that play out: in one month at a single client, the Metrc check surfaced a stack of invoices that didn't match what arrived.

This isn't about distrusting your vendors. It's about giving every payment a moment of verification it never used to get, run by something that reads every line in seconds and tells you what it found. The invoice tells you what to pay. Metrc tells you what arrived. We make sure you never confuse the two. It's one piece of how the accounts payable system keeps you from overpaying without adding a single step to your week.

If you're paying cannabis invoices today without anything checking them against Metrc first, grab a few minutes with me and I'll show you exactly where the gaps tend to hide.