Catch the overcharge before you pay it
Suppliers don't send wrong invoices on purpose, but they send them — and pay apps deserve more scrutiny than anyone has time for. Punch matches every invoice against the original PO line by line, analyzes every subcontract pay app three ways, and flags what doesn't add up before the money goes out.
Nobody has time to check every line of every invoice
Checking an invoice properly means pulling the PO, comparing quantities and unit prices line by line, and confirming the delivery actually happened. Multiply that by every supplier on every job, and it stops happening.
Unchecked invoices get paid. Price bumps, duplicate lines, and quantity drift slide straight through to job cost, taking the margin quietly with them.
Every invoice automatically checked against the PO
- 01
Invoices arrive, or you forward them
Supplier invoices come in by email and Punch ingests them automatically. One landed in your own inbox instead? Forward it, and Punch files it to the job and codes it, same as if it had arrived directly.
- 02
Punch matches line by line
Each invoice is matched against the original purchase order, comparing quantities and prices line by line. Partial shipment? Punch tracks the invoice against the PO it draws down, so a delivery billed in pieces still reconciles as one order. And because deliveries are logged from the ticket at the truck, the check runs against what actually arrived — not what should have.
- 03
Discrepancies get flagged — with the full picture
When something doesn’t add up, Punch flags the invoice for review with all the context in view — the PO, what’s shipped so far, and what’s been billed to date — and gives you a holistic analysis of the situation plus a recommended path forward. Then it waits for your instructions before payment is approved.
- 04
Clean records move on
Matched, approved invoices leave a clean record chain from PO to delivery to invoice, ready for the books.
Built for invoices that don't fit in one box
Invoices sometimes map one-to-one to a project or a PO — one delivery serves two jobs, one order arrives in three shipments. Punch handles the mess without making you untangle it.
One invoice, every job it touches
Split a single invoice across multiple projects and code each line independently, so every job's cost picture gets exactly its share — no lump-sum guessing, no journal entries later.
Invoices tracked against the PO they draw down
When a purchase order ships in pieces, each invoice is tracked as a partial shipment of that PO — so the order reconciles as a whole, not as a pile of unrelated bills.
What's billed and delivered to date, in one place
Every PO and invoice carries a running summary of what's been billed and what's been delivered to date — all the information at your fingertips in one area, no cross-referencing spreadsheets.
And when Punch flags an invoice for review, the AI takes all of this context into account — the splits, the partial shipments, the billed-and-delivered picture — and gives you a holistic analysis of where things stand plus a recommended path forward.
Every pay app, checked three ways before payment
Reviewing a subcontract pay app properly means checking it against what was billed last period, what the field says is actually in place, and the original schedule of values. Nobody has time to do that line by line — so most pay apps get approved on trust.
Punch runs the full analysis on every pay app automatically: against the previous period, against work in place reported from the field, and against the original subcontract schedule of values. A line billed ahead of the work, or past its scheduled value, gets flagged before the money goes out.
It works the way your subs actually bill — standard AIA G702 applications with their G703 continuation sheets, and labor subcontractors billing by the hour or by production unit. The review that used to eat an afternoon takes dramatically less time.
Forward it. Punch takes it from there.
Suppliers don't always send invoices to the right place. When one lands in your inbox, forward it to Punch. It's ingested, coded to the job, and matched against the PO automatically. No download, no re-keying, no comparison spreadsheet of your own to maintain.
Where this sits in the flow
Invoices are the last checkpoint before cost becomes fact. Matching them against the PO here means cleaner data reaches accounting, while your accounting system stays the system of record.
How work moves through this step
In to Punch
- Supplier invoices (email-ingested)
Out from Punch
- Invoice and cost-allocation data synced to accounting
Connection: Invoices arrive by email; matched results sync to your accounting system
From a real job
“RADO Mechanical caught a $1,500 invoice problem on their first day using Punch.”
Related reading
Construction Invoice Matching
2-way vs. 3-way matching, why suppliers send incorrect invoices, and how to prevent overpayment.
Read moreProductPurchase Orders
The PO is the yardstick every invoice gets measured against.
Read moreProductJob Costing
Matched invoices keep the actual-cost side of the job picture honest.
Read moreSee Punch work on your own workflow.
It's a working session, not a slide deck. Bring a real PO, an invoice, or a daily report. You'll use Punch on it live.