Haul-ticket reconciliation: match loads, units, rates and pay items

Define which reconciliation you are performing

Identify the project, period and purpose of the check. A hauler invoice, material-supplier invoice, internal job-cost allocation and owner pay application can use different references and payment bases. Do not assume one ticket total answers all four questions simply because each record concerns the same material movement.

Record the governing commercial or measurement source and the person responsible for interpreting it. The coordinator should know which quantity, unit and rate the review is meant to test. Where the basis is unclear, preserve the question rather than choosing the most convenient calculation or importing an unrelated rate.

FHWA's historical EDC-6 e-Ticketing overview describes exchanging and archiving material-ticket data for construction records. It provides context for traceable digital source records, not this article's payment formula or current adoption statistics. The fictional exercise below defines its own limited basis and does not establish acceptance or entitlement on a real contract.

Sources: FHWA: Historical EDC-6 e-Ticketing and Digital As-Builts overview

Give each movement a stable identity

Capture the original ticket ID, issuer, project, date, truck or load reference, material and source file. Link related dispatch, receiving and invoice documents to the same movement. A photograph of the ticket, a portal download and an emailed scan can all represent one load rather than three quantities.

Use enough context to resolve repeated ticket numbers across issuers or periods. A number alone may not be globally unique. Keep the original identifier and an internal movement reference instead of editing the source document to fit the spreadsheet. Ask the issuer to clarify an uncertain match.

Distinguish a replacement ticket, voided record and additional load. Preserve the correction or cancellation source and identify which version the calculation uses. A later document should not automatically add another quantity merely because it has a different filename or was received after the first reconciliation.

Preserve the source quantity and unit

Record the quantity as stated, including its unit and whether the source describes gross, tare, net, volume, load count or another basis. A net material weight and a vehicle gross weight are different measures. Confirm the intended field through the responsible source rather than adding every numeric value printed on the ticket.

Use one common basis only when the actual review permits it. US short tons, metric tonnes, cubic yards and truckloads are not interchangeable. If a conversion is authorized, preserve the factor, source, scope and reviewer. Do not infer a density or average load from an unrelated job to make the columns add up.

Keep unreadable or contradictory values as exceptions. Request a corrected source or clarification from the issuer. An automated extraction can assist transcription, but a confident-looking number does not resolve an ambiguous unit or establish that the source is the right ticket for this project.

Connect the movement to the destination record

Match the ticket to the appropriate project and receiving reference under the process. A dispatch ticket can establish what the source recorded as leaving the origin while the destination still needs its own receipt or review. Do not infer every receiving fact from a truck's planned route or a pickup message.

Record actual exceptions with their source. A partial delivery, rejected movement or changed destination may require a different reconciliation from an ordinary completed receipt. The coordinator should identify what is known and which decision remains open, without assigning a cause or commercial consequence automatically.

Keep material acceptance and quantity recording in their authorized processes. A receipt can provide useful evidence while a required quality or pay-item review remains unresolved. Preserve those states separately so a completed document collection task does not silently become approval of all associated payment lines.

Review the job and pay-item mapping

Identify the internal job, cost code or owner pay item relevant to the stated reconciliation. A ticket can be assigned to the correct project but the wrong activity or item. Use the actual mapping source and required reviewer rather than guessing from a short material description.

Where one movement supports more than one allocation, preserve the approved split and its basis. Do not duplicate the full quantity into several pay items. Conversely, an unresolved mapping should not make a real movement disappear from the source reconciliation. Keep it visible as awaiting the appropriate allocation decision.

Separate the hauler's billing basis from the owner's measurement basis. A carrier may bill a defined hauling service while an owner item uses another accepted quantity or scope. The relationship needs the actual contract and authorized review. This article does not turn one invoice rate into a universal pay-item value.

Match the rate to the right unit and scope

Record the approved rate source, effective version, currency, unit and covered service. A rate per US short ton cannot be applied to a cubic-yard total without the required basis. An hourly charge, minimum or other adjustment needs its own stated treatment rather than being hidden inside the material quantity.

Check whether the invoice uses the source you are reviewing and identify any difference. A later rate proposal does not automatically amend an earlier agreement. Keep the supplier or hauler's statement and route the commercial question to the authorized owner before changing the comparison basis.

Preserve taxes, surcharges, credits and other unresolved treatments separately where the process requires them. A simple quantity-times-rate check is useful, but it should not be presented as a final amount payable when other terms or review decisions remain open. Label the subtotal's limits clearly.

Worked example: three loads, one unresolved allocation

The following records and rates are fictional. The exercise uses net US short tons and a stated hauling comparison rate of $14 per US short ton, with no other adjustments. H-601 records 18.5 tons, H-602 records 20 and H-603 records 19.5. The unique source quantity totals 58 tons and its conditional comparison amount is $812.

H-601 and H-602 have completed the exercise's required allocation review, totaling 38.5 tons and $539 on that limited comparison basis. H-603's pay-item mapping remains open, representing 19.5 tons and a conditional $273. It stays in the source reconciliation but is not presented as an approved payment line.

A second scan of H-602 arrives later. It links to the same movement and adds no quantity. Counting it again would produce 78 tons and $1,092, an overstatement of 20 tons and $280 within the exercise. These figures illustrate a record check, not a finding of actual overbilling or contractual entitlement.

Resolve duplicates and corrections without losing the trail

Flag a suspected duplicate with the identifiers and source relationship supporting the match. Do not delete the only copy of a document because it resembles another ticket. Retain the link and the reviewed disposition so someone can explain why the calculation counts one movement rather than two.

For a corrected quantity, identify the original ticket, replacement source, reason as stated and current calculation version. Recalculate the affected subtotals after the source is resolved. A correction should change the relevant movement, not create an extra load with a separate unqualified total.

If a void or credit appears on an invoice, reconcile it to the actual movement and commercial record. A negative billing line is not necessarily a physical negative load. Keep quantity corrections, invoice credits and payment application distinguishable so the history remains understandable.

Send the question to the person who can resolve it

Use specific exception types: missing ticket, unreadable quantity, unknown unit, duplicate identity, wrong destination, allocation question or rate mismatch. A document request belongs with its issuer or collection owner; an interpretation or payment decision belongs with the authorized reviewer. Avoid one broad disputed label that hides the actual next action.

For H-603, a useful request names the ticket, current project and proposed pay-item references, then asks the designated owner to confirm the allocation basis. It does not ask the hauler to rewrite a ticket to fit an internal code or assume that the entire amount should be removed from the invoice.

Keep the reply and disposition source attached to the exception. Receiving another document can resolve a missing-file task while leaving a rate or allocation question open. The next owner should be clear when the response provides information but does not settle the actual review.

Freeze the review set and explain late arrivals

Choose a reconciliation cutoff and identify the tickets, invoice version and source changes included. A late ticket can affect the next review without being silently inserted into a previously issued total. Preserve the earlier version and explain which movement or decision changed the replacement report.

Reconcile the period boundary using the actual reporting basis. Dispatch date, receiving date and invoice date may differ. Do not shift a movement between periods merely to make two summaries match. The responsible owner should confirm which date governs the particular check and retain that source.

Present source quantity, reviewed allocation and unresolved quantity separately. For the fictional case, 58 source tons and 19.5 awaiting allocation can coexist without contradiction. That summary tells the reviewer what still needs a decision while avoiding an unsupported claim that every recorded ton has been accepted for payment.

Use the haul-reconciliation register

The free blank CSV includes project, period and purpose, movement ID, ticket issuer and version, load reference, material, source quantity and unit, destination record, mapping source, rate basis, conditional amount, duplicate or correction link, review state, owner and next checkpoint. It contains no embedded conversion or payment-approval formula.

Enter H-601 through H-603 and reproduce the 58-ton source total, $812 conditional comparison and $539 reviewed-allocation subtotal. Add the duplicate H-602 scan without adding a load. Then test a ticket in another unit and a corrected source version. Keep both questions visible until the required basis is resolved.

Pilot a single period with the ticket coordinator, field recipient and accounting or commercial reviewer. Ask them to locate every source and explain the unresolved rows. Clarify unit, mapping and rate definitions before expanding extraction or follow-up across a much larger ticket volume.

Coordinate ticket exceptions with Buildalytic

Buildalytic's custom-workflow page describes requests, logged replies, waits and named approval steps. Bring a redacted haul ticket with a missing receipt or unresolved allocation question to a demo. Ask how the request reaches the source owner and how the answer stays connected to the movement and review version.

Keep quantity interpretation, material acceptance, rate decisions and payment authority in their authorized processes. Confirm supported document connections and permissions for your setup. Do not assume a follow-up workflow certifies a scale, supplies a universal conversion or approves a pay item from the ticket alone.

Use H-603 and the duplicate scan to inspect two different exception paths. A useful demonstration leaves the next decision visible when the supplied paperwork is not enough. The fictional figures do not claim a customer recovery, verified overcharge or measured processing-time improvement.

Sources: Buildalytic custom construction workflows