Checking ready-mix concrete invoices against the delivery tickets

Each truck arrives with a delivery ticket (UK: concrete delivery ticket or docket; US: batch ticket or delivery ticket; Portugal: the guia de remessa for the load). What it carries varies by supplier, but it typically includes the mix or strength class, the volume (m³ in Europe, cubic yards in the US), the batch time, and often arrival and discharge times and any water added on site. Those times are what waiting-time charges are based on.

The site signs the ticket. The supplier’s invoice then usually covers every load for the period, sometimes across several job sites.

Waiting time and part loads depend on each supplier’s terms; we cover how to check them in concrete waiting time and part-load charges.

• Price per m³ — the invoiced rate is not the contracted one for that class.
• Concrete class — a C30/37 line billed where the ticket says C25/30, or the other way round.
• Volume — the invoice volume doesn’t add up to the signed tickets, or a load is billed twice.
• Waiting time — trucks billed for waiting beyond the allowed time, which should be traceable to the ticket times.
• Part-load (short-load) charges — a surcharge when a load is below the supplier’s minimum volume.
• Pumping, admixtures, extra haulage — extras billed at rates, or on dates, that the contract and tickets don’t support.

For example: a job site pouring slabs over a month takes 60 truckloads from one supplier. The invoice arrives as one document with a line per class and a handful of extras. To check it, someone has to find 60 tickets, add up the m³ by class, compare each total with the invoice, confirm each class price in the contract, and trace every pumping and waiting-time charge to a real pour. The site knows what happened; the office has the invoice and the contract. That gap is where the days go.

The job site dashboard shows contracted vs invoiced for the concrete contract and alerts you when it is running over, on the day. The same price check applies to every other material; see checking invoices against agreed prices and, for steel, rebar invoices.

1. 01The site team photographs each ticket in the chat group they already use; invoices come in as PDFs or forwarded emails.
2. 02Two AI models read each document independently: class, volume, unit and price on every line.
3. 03Each line is matched to the concrete contract item by meaning (“CONC C25/30 S3” = “Concrete C25/30 XC2”); V10 flags a different class as a different item.
4. 04Each line is priced at contract price × volume (V1); a different unit price is flagged (V8); units are checked (V9); document totals are checked against the lines (V2).
5. 05Extras such as pumping are matched to their own contract items. A line that isn’t in the contract goes to review — never dropped.
6. 06What matches is approved automatically; each difference goes to the review queue with the exact amount. Duplicate tickets are caught by document number plus supplier.

Audiree does not assess concrete quality, slump or test results, and does not replace the supplier’s ticketing system. Audiree is not an ERP, an accounting system or AP payment software. It does not pay suppliers, does not issue delivery notes or invoices, is not a certified tax archive and does not submit anything to the Portuguese tax authority (AT). It does not validate ATCUD codes, QR codes or signatures with the AT — the document number and ATCUD are used to catch duplicates. It gives no tax advice: VAT rates and reverse-charge treatment stay with your accountant. There are no ready-made connectors to specific ERPs; checked data exports to CSV for Excel or for posting in the system you already use.

Audiree is built in Portugal and works today with Portuguese construction companies. Reading does not depend on a document’s layout, so delivery notes and invoices from suppliers in other countries can be read as they are. If you run projects outside Portugal, we run demos with your own documents — but we don’t claim local tax rules or integrations for your market.