Skip to main content

Introducing Loss Radar: see which shift cost you money.Learn more

All posts

StationPro playbook

Field-tested workflow
Operator review
9 minute read
Playbooks9 min readPublished

Vendor invoice reconciliation for gas stations and convenience stores.

Reconcile vendor invoices against receiving, expected cost, POS category data, and manager approval. Common problems, duplicate invoices, short-ships, unflagged price changes, missing credits, explained with the workflow that catches them.

Written by
StationPro Editorial
Reviewed by
StationPro operator team

What is vendor invoice reconciliation?

Vendor invoice reconciliation is the process of confirming that the invoice from a distributor or vendor matches what was actually delivered, at the costs the operator expected, before the invoice gets posted to accounting and paid.

Most operators reconcile at three of four layers. The receiving layer (quantity received vs. invoiced) usually gets done because it's physical. The cost layer (this invoice vs. last invoice) usually gets skipped because it requires looking up the previous invoice. The POS layer (sales velocity consistent with receipt) almost never gets done manually. The approval layer always gets done but often without the prior three.

20+ minutes
Hand-typed McLane invoice
40–100 line items. 30 seconds with OCR. The cost difference compounds across 50+ invoices per month at a typical c-store.

What to match (the four layers)

1. Invoice amount and quantity vs. receiving

The physical match. Cartons on the dock vs. cartons on the invoice. Most operators do this correctly because it's tangible, the driver hands the receiver a slip, the receiver counts. The catch is documenting short-ships at the moment of receiving, not at end of week.

2. Expected cost vs. invoiced cost

Unit cost on each line vs. the same SKU's unit cost on the last invoice from the same vendor. Cost increases above a threshold (5% typical) flag for owner review. Without automation, this requires pulling the prior invoice, which is why it usually gets skipped.

3. POS category data cross-validation

Sales velocity on the received SKUs should be consistent with the receipt quantity. A 10-carton Marlboro Box receipt at a store that sells 4 cartons a week suggests over-ordering; the inverse suggests vendor short-ship that the receiver missed.

4. Manager approval and POS-AR-AP linkage

The owner or back-office manager approves before posting. The approved invoice posts as a vendor bill in QuickBooks with line items, vendor, date, reference number, and the inventory adjustment that updates on-hand counts.

Five common invoice reconciliation problems

1. Duplicate invoices

Same invoice submitted twice (vendor admin error, delivery and billing both sent it, copy/paste mistake). Common at high-volume vendors where invoices flow continuously. Reconciliation catches this when invoice number + amount + date all match an already-posted record.

2. Vendor short-shipment

Invoice says 10 cartons; 9 actually arrived. If receiver doesn't flag at the dock, the invoice gets approved as-is and the operator absorbs the missing carton. Detection: receiving count diverges from invoice quantity.

3. Unflagged cost increases

Marlboro Box cost rises $0.18 between invoices. Operator approves without noticing; margin compresses on that SKU until someone catches up. Detection: unit cost per SKU compared to prior invoice, threshold-flagged.

4. Missing credits / refunds

Vendor issued credit memo for last week's damaged delivery; credit doesn't appear on this week's invoice. Operator keeps paying full freight. Detection: credit-memo records cross-referenced against invoice deductions.

5. Delivery mismatch (wrong SKU)

Invoice lists Marlboro Red Box; delivery includes Marlboro Light Box. SKUs interchanged. Inventory drift on both SKUs from day one. Detection: SKU code on receiving vs. SKU code on invoice; mismatch flags.

The reconciliation workflow

  1. Capture the invoice. PDF, photo, or paper slip. Drop or snap into the OCR queue.
  2. OCR extracts line items. SKU, description, quantity, unit cost, line total. 95%+ accuracy on known distributor formats; manual review on first invoice from a new vendor.
  3. System runs the four matches. Receiving, expected cost, POS, approval. Flags any out-of-band line.
  4. Owner reviews flags. Cost increases, short-ships, credit memos. Decisions: approve, dispute, escalate to vendor.
  5. Approved invoice posts to QuickBooks.Vendor bill with line items, payable from the standard cadence. Inventory on-hand updates.

Example: an invoice with three flags

Invoice #INV-2026-04-892
Vendor: McLane
Date: 2026-04-15
Total: $12,847.32

Line items (47):
  ✓ Marlboro Box   8 cartons @ $115.50  = $924.00  (cost stable)
  ⚠ Marlboro Red   12 cartons @ $122.80 = $1,473.60 (was $115.50;
                                                     +6.3%. FLAG)
  ✓ Newport Box    6 cartons @ $128.40  = $770.40
  ✗ Camel Crush    10 cartons @ $112.00 = $1,120.00
       (received: 9 cartons. SHORT-SHIP FLAG)
  ✓ Skoal Cans     8 sleeves @ $48.20  = $385.60
  ... (42 more lines)

  ⚠ Credit memo from 2026-04-08 ($45.00 damaged Marlboro Light)
       not applied to this invoice. APPLY CREDIT FLAG

Reconciliation result:
  - Approve 45 lines as-is
  - FLAG Marlboro Red cost increase: review with owner before approval
  - FLAG Camel Crush short-ship: receiver counted 9, invoice says 10;
    file claim with McLane for $112 credit
  - FLAG missing credit: apply $45 credit to current payable

Net payable after flags resolved: $12,690.32
Saved this invoice: $157 (cost dispute + short-ship + credit)

Worked time savings

A representative c-store running 50 vendor invoices per month (McLane, Core-Mark, regional distributors, tobacco, beverages):

ProcessTime per invoiceMonthly cost (50 invoices)
Hand entry into QB15–25 min~17 hours @ $30/hr = $510
Cost-change reviewSkipped in 90%+ of casesHidden cost: ~$200/mo unflagged
OCR + reconciliation30 sec capture + 2 min review~2 hours @ $30/hr = $60

Difference per store per month: ~$450 in bookkeeper labor + ~$200 in caught cost increases = ~$650 of recovered value. At 5 stores: ~$3,250/month. Detailed ROI math.

Frequently asked questions

What is vendor invoice reconciliation at a c-store?

The process of matching each vendor invoice against four layers, receiving (quantity), expected cost (prior invoice), POS category data, and manager approval, before posting to accounting. Catches duplicate invoices, short-ships, cost increases, missing credits, and SKU delivery mismatches before they cost the operator money.

What are the most common invoice problems?

Five dominate: duplicate invoices (same invoice submitted twice), vendor short-shipments (less delivered than invoiced), unflagged cost increases (margin-compressing without notice), missing credits (vendor credit memos not applied to next invoice), and SKU delivery mismatches (wrong SKU shipped against the invoice line).

How long does invoice reconciliation take?

Hand-typed at a typical c-store: 15–25 minutes per invoice. With OCR and automated four-layer reconciliation: 30 seconds capture + 2 minutes review. At 50 invoices/month per store, the difference is ~15 hours of bookkeeper labor or ~$450/month at typical wage rates.

How do you catch vendor cost increases?

Compare unit cost per SKU against the prior invoice from the same vendor. Cost increases above a configured threshold (typically 5%) flag for owner review before approval. Without automation this requires pulling the prior invoice manually, which is why it usually gets skipped.

When should I document a short-ship?

At receiving, the moment the discrepancy is identified. The vendor charge-back window narrows fast, documented at receiving wins; documented at quarter-end usually loses because the vendor disputes the timing. Most short-ships caught at receiving resolve within 5 business days.

Does invoice reconciliation help with inventory?

Yes. Approved invoices update SKU-level on-hand inventory automatically. Short-ships caught at reconciliation prevent inventory drift from day one. Cost changes flagged at approval update the unit cost used for shrink calculations. The invoice layer feeds the inventory layer directly.

What if a vendor sends a paper invoice?

Snap a photo on a phone. OCR processes paper invoices the same as PDFs, somewhat lower accuracy on dim or wrinkled scans but usually still 90%+ on known distributor formats. First scan from a new vendor establishes the format; subsequent scans run at full accuracy.

Sources & methodology

This playbook draws on operator workflows observed in StationPro pilot stations and on anonymized product data from live pilot tenants. Figures are illustrative examples, not promises about your stores. Procedures were reviewed against the workflows of the StationPro operator team before publication. Questions or corrections: talk to the team.

Written by

StationPro Editorial

The operator team behind StationPro. We write the procedures we ship: every playbook comes from real close, reconciliation, and loss-attribution workflows in pilot stations.

See where your station is leaking money.

A 30-minute call. We build the demo around your stations, not a generic deck.