A concrete-ticket invoice check should connect each load to its order, mixture reference, stated volume, receipt records and actual commercial terms. Preserve the meaning and source of every timestamp before calculating a time charge. Keep dispatched, received, returned and billed quantities distinguishable; a returned-volume note does not automatically determine a credit or the final amount payable.
What to take away
- Match the original load and ticket before reviewing the invoice line.
- Use the actual charge rule and defined clock events rather than a universal free-time assumption.
- Keep returned quantity and its commercial treatment separate.
- Send the supplier a source-based question and preserve the reviewed resolution.
Match the load before checking its charges
Record the project, order, supplier, original ticket ID, load or truck reference, date and current source version. Link the invoice line to that movement. Several ticket copies can describe one load, and one invoice can cover many loads. The first task is to establish which physical and commercial records are being compared.
Keep the source documents intact and distinguish a corrected ticket from an additional delivery. An emailed scan, a portal export and a field photo should not automatically become three quantities. If the ticket identity or project is unclear, request clarification before assigning its charge to the nearest matching invoice row.
Identify the receipt and any exception record required by the actual process. A dispatch record and a site statement can answer different questions. Preserve their scope and source instead of merging them into one unqualified delivered status that hides a shortage, return or review question.
Preserve the volume and mixture references
Capture the stated mixture designation and volume with their source units. NRMCA's CIP31 ordering guidance discusses identifying the mixture on the delivery ticket and concrete quantities expressed by volume. That is bounded industry context for matching records, not an instruction to select a mixture, assess quality or calculate a universal invoice adjustment.
Keep ordered, dispatched, reported received, returned and billed quantities in separate fields where relevant. They can differ for reasons that require review. Do not automatically subtract a return note from the supplier's billed quantity or treat a ticket signature as a universal decision about every charge or technical requirement.
If a quantity or mixture reference is disputed, preserve the actual statements and route the question through the authorized supplier and project process. The coordinator should not alter a ticket or infer a concrete-quality outcome from a photograph. This guide concerns administrative reconciliation, not testing, placement or acceptance procedures.
Find the actual price and charge basis
Obtain the applicable quotation, order acknowledgment, agreed charge schedule and relevant review source. Identify the currency, material rate, billing unit, time-charge basis and treatment of other lines. A base volume price may not explain every invoice item. Each additional charge needs its actual reference and owner.
Cemex UK's published ready-mix terms distinguish quotation information from supplementary charge categories, including waiting and returned materials. It is a dated UK supplier example, not a rate schedule or rule for another project. The fictional charges below do not come from that source and are not presented as industry-standard allowances.
Where the terms or their applicability are uncertain, ask the authorized commercial reviewer. A coordinator can collect records and identify an arithmetic difference, but should not decide enforceability, waive terms or promise a credit from a general checklist. Keep the actual decision source with the reconciliation.
Sources: Cemex UK: Published ready-mix trading terms, supplementary-charge example
Define the clock events before multiplying minutes
Identify what each timestamp means and who supplied it. Batch, dispatch, arrival, readiness, start, completion and departure can be different events. A field labeled out may describe departure while another system uses it for a different milestone. Preserve the original label and resolve uncertainty before using it as a charge boundary.
Read the actual commercial rule for which period, allowance, increment and rounding treatment apply. Do not assume a universal free-time period or equate every elapsed site minute with waiting. The reviewer needs the source rule and the events to which it applies, not just a pair of convenient times.
Keep a missing or contradictory timestamp as an exception. Ask the supplier or field source for the actual record and its meaning. A later recollection should remain identifiable as a later statement rather than being inserted into the original ticket as though it had been recorded contemporaneously.
Worked example: two clock bases produce different comparison amounts
The following load, rule and prices are fictional. Ticket C-701 records eight cubic yards. The exercise's comparison basis uses $165 per cubic yard, a site-elapsed period from recorded arrival to completion, 25 unbilled minutes and $2 for each additional minute, with no rounding or other time adjustments. These are invented assumptions, not a standard supplier policy.
The source records arrival at 10:05 a.m., completion at 10:55 and departure at 11:10, all on the same stated local day. Arrival to completion is 50 minutes. Under the exercise's rule, 50 minus 25 leaves 25 comparison minutes, or $50. Arrival to departure is 65 minutes and would yield $80 under a different end-event choice.
The invoice lists $80 for the time line. The coordinator asks the supplier to identify its actual clock basis and the authorized reviewer to resolve the difference. Matching the $80 arithmetic does not prove why the supplier used it, and the $30 comparison difference is not automatically an approved deduction or recoverable credit.
| Fictional time basis | Elapsed minutes | Less stated exercise allowance | Conditional time amount |
|---|---|---|---|
| 10:05 arrival to 10:55 completion | 50 | 25 minutes | $50 at $2/minute |
| 10:05 arrival to 11:10 departure | 65 | 25 minutes | $80 at $2/minute |
| Difference to investigate | 15 | Different end event | $30; not an approved credit |
Reconcile returned volume without inventing its treatment
Continue C-701: the source notes one cubic yard returned. Preserve that statement, its author, measurement basis and related supplier record. The difference between eight dispatched and one returned is seven cubic yards on the exercise's simple physical basis. That does not by itself decide the quantity billed or any charge for the returned material.
The fictional invoice retains eight cubic yards at $165, totaling $1,320, and separately lists a proposed return-related line of one cubic yard at $40. The coordinator obtains the actual commercial basis for both treatments rather than automatically replacing the billed volume with seven or approving the additional line.
Keep rejected, returned, cancelled and unused descriptions tied to their source. They can have different meanings and review paths. This article does not decide disposal, quality, responsibility or contract treatment. The record should expose the stated event and the specific question the authorized reviewer must resolve.
Keep a conditional comparison separate from approval
The exercise's invoice contains three simplified lines: $1,320 for volume, $80 for time and $40 for the proposed return-related charge, totaling $1,440. Taxes and all other adjustments are excluded from this fictional exercise. Preserve the invoice as received rather than editing its original values to match your calculation.
Using the exercise's arrival-to-completion time basis gives a conditional comparison of $1,320 plus $50 plus $40, or $1,410. The $40 treatment is still a commercial review item. Label this as a comparison using stated assumptions, not the final payable amount. The $30 difference identifies a question; it does not settle the entire invoice.
Record the actual reviewer disposition and any supplier correction or credit separately when received. A supplier explanation may resolve the time question without producing a credit, or another source may change the comparison. Preserve the decision and revised basis instead of keeping the original expected recovery as though it were cash received.
Check each additional line against its own source
Use separate review rows for short-load, cancellation, weekend, environmental, fuel, return or other charges that appear on the actual invoice. The relevant terms can vary by supplier, order and situation. Do not treat the example's list as a universal entitlement to charge or a universal reason to reject a line.
Identify the quantity or event basis for each charge and check for duplication. A fee can be applied per load, per order, per unit or under another defined basis. Two invoice rows with similar labels may need clarification rather than an automatic deletion or approval.
Keep credits and corrections linked to the relevant invoice and ticket. A supplier issuing a credit document and accounting applying it are separate events. The coordinator's register should identify the next owner if a reviewed correction has not yet reached the accounting record.
Send a source-based reconciliation request
A starting message is: For invoice [reference], ticket C-701, please identify the source rule and clock events supporting the $80 time line. Our records show arrival 10:05, completion 10:55 and departure 11:10. Please confirm the event definitions and provide the relevant supporting record. The return-related line also needs its stated quantity and commercial basis.
Use the actual approved communication route and attach or link only the records the recipient is authorized to receive. Keep the request factual. Do not assert a supplier error or promise a deduction before the source and commercial review establish the result.
Record the supplier's response, any revised ticket or invoice and the designated review outcome. If the response answers only one question, close that task and leave the other open. A new attachment should not make every disputed line appear resolved merely because the folder now looks complete.
Preserve the reconciliation cutoff and revised source
Identify the invoice version, ticket set, commercial references and cutoff used for each comparison. A later timestamp clarification or credit can change the result. Retain the earlier reconciliation and explain which input or decision changed, rather than overwriting the only record of the previous review.
Where a line remains unresolved at the reporting checkpoint, state its owner and next action. The office may need to distinguish an arithmetic check, a missing source and a commercial interpretation. Those categories should not be collapsed into one broad unpaid or disputed label without context.
Keep the operational record separate from the financial decision. The billing review should not rewrite what the field reported, and the ticket should not silently become a final settlement document. The actual project and accounting processes determine which records and approvals are required.
Use the concrete-ticket invoice register
The free blank CSV includes project, order and load ID, ticket source and version, mixture reference, volume and unit, receipt and return statements, invoice line, rate and charge source, timestamp labels and event definitions, exercise or actual comparison basis, conditional amount, unresolved question, reviewer and resolution source. It contains no universal time allowance or concrete conversion formula.
Enter C-701 and reproduce the 50- and 65-minute periods, the $50 and $80 conditional time amounts, and the $1,440 invoice versus $1,410 comparison. Keep the one-yard return note and its charge review separate from the material quantity line. The worksheet should not automatically approve either figure.
Pilot a small invoice with the field record owner, supplier contact and accounting reviewer. Ask them to explain the clock boundaries, returned-volume source and commercial treatment. Resolve those definitions before using automatic extraction or follow-up across an entire supplier account.
Coordinate invoice questions with Buildalytic
Buildalytic's custom-workflow page describes requests, logged replies, waits and named approval steps. Bring a redacted concrete ticket and a time- or return-charge question to a demo. Ask how the source request reaches the appropriate supplier or field contact and how the reply stays connected to the invoice review.
Keep technical acceptance, contract interpretation, invoice approval and credit application in their authorized processes. Confirm supported connections and permissions for your setup. Do not assume a follow-up workflow determines concrete quality, provides a universal charge rule or guarantees a supplier credit. The useful walkthrough exposes the unresolved decision.
Use C-701 to inspect a clear source clarification and a response that leaves a commercial question open. A next owner should remain visible until the actual review is recorded. The fictional arithmetic does not claim an actual overcharge, customer recovery or measured payment improvement.
Common questions
Is there a standard free waiting period for every concrete delivery?
Use the actual applicable commercial terms and event definitions. The 25-minute allowance in this article is a fictional exercise assumption, not an industry rule.
Does a returned-yard note automatically reduce the billed quantity?
Preserve the physical quantity record and obtain the actual commercial treatment. A return note, a proposed fee and an approved credit are different records.
Can a ticket review determine concrete quality or acceptance?
This guide addresses administrative and invoice reconciliation. Technical review and acceptance remain in the project’s authorized process with the required evidence.
Sources and editorial notes
- NRMCA CIP31: Ordering Ready Mixed Concrete
- Cemex UK: Published ready-mix trading terms, supplementary-charge example
- Buildalytic custom construction workflows
Prepared with AI assistance. Reference date: 2026-10-29. Worked examples are illustrative and are not customer results. Product details can change; confirm the current scope and terms before rollout.
How we prepare and update field notesBring a ticket charge whose basis is unclear
Bring a redacted ticket, invoice line and applicable charge reference. We will map the source question, linked response and named review step using your process and supported connections.
Start with the call, text or record your team already handles. Review the expected outcome and the human handoff before choosing a rollout.
Request a supplier-invoice follow-up demo Explore the relevant capability



