Most systems that receive a fuel bill of lading treat it like any other piece of freight paperwork. They capture the shipper, the carrier, the consignee and a quantity, attach the image to the delivery, and move on. For a pallet of goods that is close to enough. For a truckload of gasoline or diesel lifted at a terminal rack, it misses the point of the document. The fuel bill of lading is the source record of fuel excise reporting. The terminal operator reports it to the IRS, the carrier reports it again, and a state return counts tax from the gallons and the destination printed on it.
That changes what a correct extraction looks like. A freight document is right when its pieces and weight match the shipment. A fuel document is right when its gallons, its product, its destination state and its document number match what two other parties will file about the same load. The weight hardly matters. The temperature at which the gallons were measured matters a great deal.
This piece reads a rack bill of lading the way the reporting side has to read it. The federal rules quoted come from the IRS Instructions for Form 720-TO and Form 720-CS (Rev. July 2017), which are the current instructions for the terminal operator and carrier information returns, and from 26 CFR 48.4081-1 and 48.4101-1. For the state side, Chapter 82.38 of the Revised Code of Washington is used as one example of how a state ties tax to the same document. Every state writes its own fuel tax law, and nothing here is tax advice or a description of any particular state’s return.
Where a rack bill of lading comes from
Fuel moves through the bulk transfer/terminal system, which 26 CFR 48.4081-1 defines as the refineries, pipelines, vessels and terminals that make up the taxable fuel distribution system. Fuel in that system has not left it yet. Fuel in a truck, a rail car or a trailer is outside it. The point where the fuel crosses from one to the other is usually a terminal rack, which the same regulation defines as a mechanism capable of delivering taxable fuel into a means of transport other than a pipeline or vessel. The bill of lading is issued at that crossing, which is why it carries so much tax weight.
Four parties appear on it, and each one files or relies on it differently:
| Party | Who it is | What the bill of lading is to them |
|---|---|---|
| Terminal operator | The person that owns, operates or controls the terminal | The document it issues at the rack and reports, line by line, on Form 720-TO |
| Position holder | The person that holds the inventory position in the fuel on the terminal operator’s records | Evidence of which owner’s inventory left the terminal, and in which product |
| Carrier | The truck, rail, barge or pipeline company that moves the fuel | The document it reports again on Form 720-CS, under the same number |
| Consignee or purchaser | The distributor, retailer or end user receiving the load | Proof of what was delivered, at what volume, to which state |
The position holder is the party freight systems most often lose. It is not the carrier and it is not necessarily the buyer. It is whoever held the fuel inside the terminal, and the terminal operator’s report is organized around it: the 720-TO instructions require a separate Schedule B for each position holder, for each product code, and separately for each destination state and mode of transport. If the extraction cannot say whose inventory a bill of lading came from, the load cannot be placed on the right schedule.
Two gallon figures, both on the page
A rack bill of lading usually prints two volumes for the same load, and they are not a reading and a correction. They are two different measurements, and the reports use them for different things. The 720-TO instructions define them precisely:
- Gross gallons — the total product measured in US gallons without temperature or barometric adjustments.
- Net gallons — liquid product measured in US gallons corrected to a temperature of 60° Fahrenheit or 15° Celsius and to a pressure of 14.7 pounds per square inch.
Fuel expands as it warms, so the same mass of product occupies more gallons on a hot afternoon than on a cold morning. A load lifted warm shows more gross gallons than net; a load lifted cold can show the reverse. Neither figure is wrong. They answer different questions, and the reporting asks both. On Schedule B of Form 720-TO, column (f) is the actual net gallons disbursed from the terminal and column (g) is the gross gallons disbursed, as shown on the shipping document. On Form 720-CS, the carrier reports net gallons. Which figure a given state return uses is set by that state’s law, and states do not all choose the same one.
That has a direct consequence for extraction. Both figures have to be captured as printed, each labeled by what it is, together with the temperature and gravity if the document shows them. An extraction should never compute net gallons from gross with a generic factor. The terminal’s meter applied the correction with the product’s measured properties at the moment of loading, and that number is the one the terminal reported. A recomputed figure that differs by a few gallons on every load is exactly the kind of discrepancy reconciliation exists to find, and it would have been created by the reader, not the record.
The same discipline applies to the terminal’s own books. Part III of Form 720-TO is a monthly summary by product code, built from physical inventory in net gallons, receipts and disbursements, with gains and losses reported on their own line. The instructions say book adjustments and other known transactions are not gains or losses, and that zero-gallon transactions are not allowed on either schedule. A bill of lading read with the wrong volume does not just misstate one load. It moves the gain or loss line for the month.
The destination state decides whose tax it is
On a freight bill of lading the destination is an address for the driver. On a fuel bill of lading it is a jurisdiction. The 720-TO instructions require the destination state code on Schedule B for non-bulk disbursements, which means truck and rail car loads, and they add a specific rule: if a fuel transport truck receives fuel destined for different states, the terminal operator issues a bill of lading, manifest or other shipping document for each destination state, and each separate shipping document is reported as a separate transaction.
State law hangs the tax on the same field. Washington is a clear example. RCW 82.38.030(14)(a) imposes the fuel tax when fuel is removed in the state from a terminal at the rack, unless the removal is by a licensed supplier or distributor for direct delivery to a destination outside the state. The same rack, the same product and the same volume are taxed in Washington or not depending on the destination the shipping document records. A destination read wrong is not a delivery problem. It puts the gallons on another state’s return.
| Field on the bill of lading | Where it lands | What goes wrong if it is misread |
|---|---|---|
| Destination state | 720-TO Schedule B destination state; the state return that taxes the removal | Gallons taxed in, or exempted from, the wrong state |
| Product | Product code on both federal returns; the tax rate class on the state return | The load is reported on the wrong schedule, at the wrong rate |
| Net and gross gallons | 720-TO columns (f) and (g); 720-CS net gallons; state volume | A mismatch between the terminal’s and the carrier’s filings |
| Terminal control number | The terminal identified on 720-TO; the origin on 720-CS | A disbursement assigned to the wrong facility |
| Carrier name and identifier | 720-TO carrier columns; the filer of 720-CS | The load cannot be matched to the carrier’s report |
| Document number and date | The transaction identifier on both federal returns | The two reports of one load cannot be joined |
Split loads are the case most likely to be flattened. A compartmented trailer can carry gasoline to one state and diesel to another, or one product to two states, on a single trip. The terminal issues separate documents, and each one is its own transaction. An extraction that merges them because they share a truck, a driver and a departure time produces one record that matches neither report.
The document number is the join key
The single most useful sentence in both sets of instructions is about the number on the document. The 720-TO instructions tell the terminal operator to enter the identifying number from the document provided to the carrier that reflects the details of the transaction, which could be a bill of lading, manifest, inspection report or other shipping document. The 720-CS instructions tell the carrier to enter the identifying number from the same document. Both say that the carrier and the terminal operator must report the same document number.
That makes the bill of lading number the key that joins two independent filings about one load. Each party fills in its own return from its own copy, and the two are expected to agree. Anyone reconciling them, whether a carrier checking its own summary or a distributor checking what it was billed, is doing the same join:
| Divergence between the two records | Likely cause | Action |
|---|---|---|
| Document number on one side only | A load missed on one report, or a number misread on one copy | Find the paper; do not create or drop a transaction to force a match |
| Same number, different net gallons | Gross read as net, or a recomputed volume on one side | Compare against the printed figures on the document |
| Same number, different product | A product description mapped to the wrong code | Keep the product text verbatim and review the mapping |
| Same number, different date | Loading date confused with delivery date | Use the date the product was removed from the terminal, as the instructions require |
| One document on one side, two on the other | A split load merged or a single load split by the reader | Reconcile against the separate documents issued per destination state |
None of these is unusual. They are what happens when a document number is treated as a freight reference rather than as the identity of a reported transaction. The fix is the same in every row: keep the printed values, keep the number exactly as printed, and let the comparison find the difference instead of hiding it.
A notice that is a field, not boilerplate
Some text on a fuel bill of lading looks like the fine print every shipping document carries. One notice is not. Under 26 CFR 48.4101-1(h)(3)(i), a terminal operator must give anyone receiving dyed diesel fuel at its rack a legible and conspicuous notice stating “DYED DIESEL FUEL, NONTAXABLE USE ONLY, PENALTY FOR TAXABLE USE”, with a parallel notice for dyed kerosene, and that notice must appear on all shipping papers, bills of lading and similar documents provided to accompany the removal.
The same regulation works in the other direction. Paragraph (h)(3)(v) prohibits a terminal operator from providing anyone with a bill of lading or similar document indicating that diesel fuel or kerosene is dyed and marked when it is not. Washington mirrors the rule: RCW 82.38.035 makes a terminal operator jointly and severally liable for the tax on special fuel that is removed undyed while the operator provides a bill of lading, shipping paper or similar document indicating that it is dyed. The notice is a statement of the fuel’s tax status, and the document is how that status travels.
For extraction, that means the dyed fuel notice is a field. Its presence or absence should be captured explicitly, verbatim, and checked against the product line. A product described as dyed with no notice on the document, or a notice on a document for an undyed product, is an exception for a reviewer, not text to be stripped as boilerplate. The 48.4101-1 recordkeeping rule makes the point from the terminal side: for each rack removal of diesel fuel or kerosene, the operator keeps the bill of lading, the record of whether the fuel was dyed and marked, the volume and date of the removal, and the identity of the person that physically received the fuel.
The document that travels with the load
A fuel bill of lading is also checked on the road. RCW 82.38.140(4) requires every person operating a conveyance that transports fuel in bulk to possess, the entire time, an invoice, bill of sale or other statement showing the name, address and license number of the seller or consignor, the destination, the name and address of the purchaser or consignee, the license number if applicable, and the number of gallons. The document has to be produced on request for inspection.
Read as a list of fields, that is close to the minimum a fuel extraction should treat as required rather than optional. The license numbers are the ones most often skipped, because a freight extraction has no slot for them. On a fuel document they identify the licensed parties whose status decides whether a removal was taxed, exempted for out-of-state delivery or passed between licensees.
Not the same problem as a freight bill of lading
Freight documents have their own reconciliation, and it is a different one. For a shipment, the question is whether the air waybill, the packing list, the shipping label and the customs declaration agree on weight, quantity and consignee, a problem walked through in the air waybill reconciliation article. For a delivery claim, the counts, exception notes, signature and timestamp on the proof of delivery are what settle it, as the proof of delivery article argues.
A fuel bill of lading shares the layout and differs in purpose. Its quantity is a volume measured under defined conditions, not a count. Its destination is a jurisdiction, not just an address. Its number identifies a transaction in two federal information returns. Its notices carry tax status. A system that already extracts freight bills of lading has most of the reading in place; what it needs is a schema that does not throw away the fields only fuel documents use.
What the extraction should deliver
For every rack bill of lading, a fuel-aware extraction should return:
- Origin facility — terminal name and terminal control number as printed, plus the position holder whose inventory was lifted.
- Both volumes — gross gallons and net gallons, each labeled, with temperature and gravity when the document prints them, and no volume computed by the reader.
- Product — the product description verbatim, the mapped product code, and the dyed fuel notice captured as present or absent.
- Destination state — read as its own field, with one record per shipping document even when one truck carried several.
- Parties and licenses — consignor, carrier, consignee and their license or registration numbers where shown.
- Document number and removal date — exactly as printed, because they are what the terminal’s and the carrier’s reports are joined on.
Each value should carry the place on the page it was read from. When a carrier summary and a terminal report disagree about one load months later, the only fast way to settle it is to show the printed figure, not the extracted one.
Not tax advice
The federal instructions quoted here govern information reporting by terminal operators and carriers; the Washington statute is one state’s law. Other states define taxable events, licensed parties, exemptions and the gallons they tax differently, and some file on schedules organized in ways this article does not describe. The claim is narrower and holds across them: whatever the return, it is filled from fields on the shipping document, and an extraction that keeps those fields intact, labeled and traceable makes every return easier to file and to check.
Read it as the tax record it is
A rack bill of lading looks like freight paperwork and behaves like a tax record. Its two volumes are not a reading and a correction; they are two measurements that different reports use. Its destination state decides whose tax the load carries. Its number is the key that two independent filings are expected to share, and its notices state the fuel’s tax status in words the regulations prescribe. Extract it as a shipment and those meanings disappear into a quantity and an address. Extract it as a tax record and every one of them can still be checked.