Supplier fuel consumption reporting is the delivery ticket, bill of lading, and consolidated usage or invoice record your vendor generates for every drop. It matters because those documents are what let you verify the gallons you were billed for actually landed in your tank, catch overbilling before payment goes out, and hand an auditor a clean trail from purchase order to reconciled invoice.
TL;DR:
- Fuel delivery records must include supplier and delivery details, product type, gallons with temperature adjustment, truck and driver ID, and acknowledgment signatures.
- Site verification requires pre- and post-delivery tank readings with timestamps, and the process should be assigned to a consistent operator for accuracy.
- Reconciliation of invoices should occur immediately upon receipt, comparing delivered quantities and prices with established thresholds for variances.
- Fuel records should be systematically organized by quarter and document type, with retention for several years to ensure audit readiness.
- Common audit gaps include missing written procedures, unattended deliveries without evidence, and invoices paid before matching delivery tickets.
Table of Contents
- What Should a Complete Fuel Report and Delivery Ticket Include?
- How Do You Verify Deliveries on Site?
- How Do You Reconcile Fuel Invoices Against Delivery Tickets?
- How Should You Organize and Retain Fuel Delivery Records?
- What Do Fuel Audits Actually Check?
- Audit-Ready Reporting, Built Into Every Delivery
- Sources
What Should a Complete Fuel Report and Delivery Ticket Include?
A delivery ticket that can’t stand up to scrutiny is worse than no ticket at all, because it gives you false confidence. State regulations on bulk fuel delivery, including New York’s disclosure rule, require sellers to supply written proof of delivery with specific fields at the time fuel changes hands. That legal baseline lines up almost exactly with what a facilities or fleet team needs for its own recordkeeping.
A complete ticket or supplier report should show:
- Supplier name, delivery date, and time of drop
- Product type (clear diesel, dyed diesel, gasoline, or DEF)
- Gross and net gallons, with temperature or volume compensation noted
- Delivery truck or vehicle ID and driver identification
- Meter printout number or electronic ticket ID
- Unit price and a reference to the agreed invoice price
- Signature or electronic acknowledgment from site personnel
Each field earns its place. Gross versus net gallons matters because temperature swings change fuel volume, and a ticket that only shows one number hides the compensation math behind your invoice. The truck ID and meter printout give you something to check against if a dispute ever surfaces months later. Delivery formats vary. Some suppliers still hand over a carbon-copy paper ticket, others email a PDF the same day, and a growing number push data straight into a portal or CSV export you can pull into a spreadsheet. Format matters less than completeness. A tidy PDF missing the meter reading is still an incomplete record.
How Do You Verify Deliveries on Site?
Verification happens in the window around the delivery itself, not weeks later when the invoice lands on someone’s desk. Build the habit into your standard operating routine and it takes minutes per drop.
- Record the tank reading before the delivery starts, with a timestamp and the name of the operator who took it.
- Stay present, or assign someone to be present, while fuel transfers, and confirm the delivery truck ID matches the ticket.
- Take the tank reading again immediately after the delivery finishes, and log the same details.
- Collect the bill of lading or meter printout on the spot, not after the driver leaves.
- For unattended deliveries, require photo evidence of the tank gauge, the meter readout, and any tamper-evident seal, uploaded to a central folder the same day.
- When temperature or volume compensation was applied, record both the compensated and uncompensated figures if the supplier’s system provides both.
- If the delivery feeds a bulk tank shared across cost centers, log the withdrawal allocation so gallons tie back to the correct unit or department.
Unattended deliveries are where most reporting gaps start. A driver who arrives at 4:00 AM to top off a generator at an unstaffed site has no one to sign anything, so the paper trail depends entirely on the supplier’s electronic ticketing and your own tamper-evident seal check the next morning.
Pro Tip: Assign one person per site as the designated reading-taker, even on a rotating schedule. When three different people take tank readings inconsistently, your reconciliation team spends more time chasing down who measured what than actually reconciling the numbers.
Our guide on fuel delivery safety protocols covers the physical side of this checklist in more depth, including what to do when a seal looks compromised.
How Do You Reconcile Fuel Invoices Against Delivery Tickets?
Reconciliation should happen when the invoice arrives, not during a quarter-end scramble. Waiting turns a five-minute check into an hour of digging through email threads trying to remember which delivery a charge belongs to.
The workflow itself is straightforward once someone owns it:
- Match the delivery ticket to the tank or meter readings taken on site.
- Compare that ticket to the supplier invoice for quantity and confirm the price against the agreed reference, whether that’s a contract rate, an index-plus-margin formula, or a quoted daily price.
- Flag any variance beyond your threshold before approving payment.
- Route flagged invoices to a named approver, not back to whoever happens to be free.
- Log every reconciled invoice in a standing spreadsheet with columns for date, site, gallons billed, gallons confirmed, variance, and disposition.
Set your variance threshold based on what’s normal for your metering equipment and delivery volume. Best practice across procurement teams is to verify quantity and price before an invoice ever gets approved, not after, so a documented variance threshold and a clear escalation path keep that check consistent even when the usual reviewer is out.
Ownership needs to be explicit. Someone performs the ticket-to-invoice match, someone else (or the same person on a different day) approves disputes, and a third person, often in accounts payable, actually releases payment. That separation is exactly what auditors look for. Our breakdown of fuel delivery verification best practices walks through building this workflow into an existing accounts payable process without adding headcount.
How Should You Organize and Retain Fuel Delivery Records?
Filing by quarter and by document type keeps retrieval fast and helps avoid last-minute sorting of multiple receipts at the end of the filing period. Organizing purchase documents this way, and reconciling as soon as receipts arrive rather than batching them, is what separates teams that respond to an IFTA reporting deadline calmly from teams that don’t.
A workable folder structure looks like this:
- One top-level folder per quarter, with subfolders for paper tickets, emailed invoices, fuel card exports, and bulk-tank delivery records.
- Original delivery tickets, the matching invoice, and your reconciliation summary filed together, never split across separate systems.
- A monthly validated summary showing gallons by site or unit, an exception log for anything still unresolved, and a tracker for missing documents.
Retention periods vary by contract and auditing agency, so check your specific requirements. A recommended minimum retention period for delivery tickets and invoices is several years to ensure records are available if audited.
Auditors expect to see three controls in place regardless of how you organize files: a documented reconciliation procedure, a regular cadence for verifying tank-monitor readings against physical measurement, and separation between the person who orders fuel and the person who approves payment. Our KPI tracking guide breaks down which monthly figures matter most for spotting problems before an audit does.
What Do Fuel Audits Actually Check?
Run this checklist against your current practice before an auditor does it for you:
- Do you have a written fuel ordering and reconciliation procedure, not just an informal habit?
- Are pre-delivery and post-delivery tank readings recorded with timestamps and names?
- Are delivery tickets retained and matched to every invoice before payment?
- Is there a documented variance threshold and a dispute log for exceptions?
- Is fuel ordering separated from invoice approval, so no single person controls both ends?
- Are tank-monitor readings periodically verified against physical dipstick or gauge checks?
Audits of fleet fuel programs, including one review by the City of Denton, commonly flag the same handful of gaps: no written procedure at all, unattended deliveries with no photo or electronic evidence, invoices paid before anyone matched them to a ticket, and bulk tanks with no withdrawal log tying gallons to specific units. Every one of those has a direct fix, and effective bulk-fuel recordkeeping depends on tracking beginning inventory, every incoming receipt, and verified withdrawals so your calculated ending inventory actually matches what’s physically in the tank. When you present remediation to an auditor, a simple packet showing the source ticket, the reconciliation entry, and the approval signature for a sample of deliveries does more to build confidence than a written policy alone ever will.
Audit-Ready Reporting, Built Into Every Delivery
Some fuel delivery providers build the documentation into the delivery itself, so you’re never reconstructing records after the fact. Every drop generates an electronic delivery ticket with the fields auditors and procurement teams actually check: gallons, product type, truck ID, and timestamp, consolidated into usage summaries you can hand straight to accounts payable or pull for a quarterly review.
For operators running sites in multiple states, that consistency compounds. Rather than reconciling different supplier formats across states, a nationwide partner network can provide one point of contact, one invoicing standard, and one ticket format whether you’re topping off a generator or fueling a mining fleet. Transparent invoicing means the price reference on your ticket matches the price on your invoice, which is an important check your reconciliation workflow should run. If you’re evaluating a fuel partner for a multi-site contract or just want to see what a sample ticket and invoice actually look like before you commit, request fuel delivery information and get a procurement-ready packet built around the same audit trail this guide just walked through.
Sources
- Bulk-fuel recordkeeping requirements (J.J. Keller Compliance Network)
- Audit of Fleet Services Operations: Fuel Management (City of Denton audit)
- 1 NYCRR § 224.5 — Bulk delivery disclosure requirements (New York regulation, Cornell LII)
Recent Comments