StationPro playbook

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.
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.
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
- Capture the invoice. PDF, photo, or paper slip. Drop or snap into the OCR queue.
- 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.
- System runs the four matches. Receiving, expected cost, POS, approval. Flags any out-of-band line.
- Owner reviews flags. Cost increases, short-ships, credit memos. Decisions: approve, dispute, escalate to vendor.
- 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):
| Process | Time per invoice | Monthly cost (50 invoices) |
|---|---|---|
| Hand entry into QB | 15–25 min | ~17 hours @ $30/hr = $510 |
| Cost-change review | Skipped in 90%+ of cases | Hidden cost: ~$200/mo unflagged |
| OCR + reconciliation | 30 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?
What are the most common invoice problems?
How long does invoice reconciliation take?
How do you catch vendor cost increases?
When should I document a short-ship?
Does invoice reconciliation help with inventory?
What if a vendor sends a paper invoice?
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.
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.
Keep reading
The record July 4 travel week: is your busiest fuel days' close capturing the volume, or leaking it?
AAA projected a record 72.2 million travelers over July 4, 2026, with 85 percent driving. Your highest-volume days are also your highest-variance days: more tank drops, more shift handoffs, more cash, more room for a leak to hide. A pre-holiday checklist for closing tight when the forecourt is slammed.
How to retain fleet card customers at a gas station: competing with Pilot and Love's for the WEX and Comdata fleet.
Fleet card customers value IFTA-ready reporting and clean monthly billing as much as price per gallon. WEX OTR transactions grew 1 percent in 2025 while local fleets dropped 3.7 percent. The 5 things independent stations can do that the chains cannot, and the back-office reports a fleet manager actually wants.
How to retain truck drivers at a truck stop or fuel station.
NATSO 2025: parking comes first, showers second, food third, and fuel price fourth in driver retention. Drivers lose $4,600 a year and 56 minutes a day hunting parking. What independents can do to win share from Pilot, TA, and Love's, and the back-office data that tells you who your highest-LTV drivers are.
