Invoice auditing for contractors who buy concrete and aggregates
No PO system. No integration. The paper you already have.
Four steps, no software to install and nothing to connect to your accounting system.
Every invoice and every signed delivery ticket from the month, photographed or scanned, however you already have them.
Each invoice line is checked against the ticket behind it and the rate, fee, and tax terms you agreed to. Nothing gets claimed that the paper doesn't prove.
A dispute package for every line that doesn't hold up: the amount, the ticket it traces to, and a formal statement ready to send to your supplier.
Track what got credited, what got sent again, and what's still outstanding, month over month.
Every family below is backed by a rule that's already live in the audit, not a roadmap item. Each one is shown with a specimen from real public supplier paper: names withheld, arithmetic exact.
The same delivery ticket can end up on two different invoices, weeks apart, easy to miss when invoices are reviewed one at a time. We check every ticket number within an invoice and across a full month's submissions, so a ticket billed twice gets caught even when the two invoices never sit side by side on your desk.
A supplier's own credit memo, correcting 24 tickets billed on two invoices: $8,650.64 credited.
Every invoice line gets checked against your quote or contract rate, including tiered pricing, rates that change on a set date, and rates that shift partway through an invoice. We account for how each supplier rounds, so a line isn't flagged for a rounding convention that was always there, and no claim is ever larger than the line's own arithmetic supports.
One corpus invoice billed 16.5 CY at $86.50 against a job rate of $75.00. The supplier's own credit memo caught it first: a $189.75 correction, worked out on that same 16.5 CY.
Fees get checked against the terms you actually agreed to: whether a fee applies at all, whether it falls inside the season it's supposed to, and whether the same charge is being billed twice under a different name. A fee with no basis in your terms gets flagged instead of quietly paid.
One corpus job's fuel surcharge line reads $0.00 for six weeks, then $5.00 for six weeks, then $0.00 again, tracking the supplier's own fuel-surcharge notice to the week, not the calendar and not a guess.
Sales tax gets checked against what should and shouldn't sit inside the taxable base, not just the rate charged. The same delivery fee or fuel surcharge is taxable at one supplier and excluded at another, and the base has to match what your terms and your state actually require.
One corpus invoice taxes $3,150.00 at 6.75% ($212.63) and leaves a $75 fuel fee and a $75 environmental fee out of that base. Another taxes $529.00 at 8.25% ($43.64) and puts a $150 short-load charge and a $10 fuel fee inside it. Same tax question, two different answers, both printed by the supplier.
Every invoice line gets checked against the quantity on its own signed ticket, not an assumed unit or a rounded-off number. Short loads and per-unit lines are read the way the ticket actually prints them.
One corpus invoice uses the same unit abbreviation to mean three different things across its own line items. A check that assumes units stay consistent would pass a bad match without ever seeing it. Ours reads what each ticket actually prints.
Wait time gets recomputed against your own terms: the free window, the rate after it, and where the clock starts. When your terms don't say, we don't guess. We only claim what the paper proves.
One corpus invoice bills standby by the minute: 30 minutes at $0.91 a minute, 36 minutes at the same rate, both exact to the penny against the terms printed on that invoice. Most jobs aren't that explicit, which is exactly why silence gets flagged, not priced.
Every ticket's date gets checked against the invoice period it's billed under. A ticket dated outside that invoice's billing period gets flagged for review, never auto-claimed as a dollar amount. This is an observation, not a deadline clock: we don't calculate payment due dates or track a dispute window for you.
On real supplier paper, printed date fields disagree with each other routinely: one public-record packet shows three different due-date conventions on one account. Dates earn a flag and a human look, not an automatic dollar.
Every invoice line has to trace back to a signed ticket, or it gets flagged. A month's invoices and tickets get reconciled against each other so nothing quietly falls through the gap between the two stacks.
One corpus invoice set billed 54 ticket lines. Only 52 tickets were actually in the file. Every dollar total still added up; the 2 missing tickets were invisible to the math and only surfaced under a full cross-invoice count.
The mechanism is the same across materials. The paper looks different by trade, and that's where each vertical page picks up.
The day-to-day ready-mix flow: delivery tickets, wait time, rate checks, and the fee terms suppliers actually print.
See the concrete pageThe same transferable error families, checked against aggregate suppliers' own invoices and terms.
See the aggregates pagePump tickets and hour-based billing. Not live yet.
Send us last month's full stack: every invoice, every signed ticket. We check every line and send back what doesn't hold up. No cost for your first month.