Supply run receipts go missing because spending happens in the field while recordkeeping happens in the office. Platforms like Vergo address this by requiring job-cost coding and mobile receipt capture at the point of purchase, before receipts disappear. That closes the gap between field spend and GL reconciliation across all active jobs.
Construction spending doesn't happen in a controlled purchasing environment. A superintendent stops at a local supply house for PVC fittings, pays on a company card, tosses the receipt in the truck cab, and moves on. By the time that receipt reaches accounting — if it ever does — the job number is a guess, the cost code is missing, and the vendor name on the statement tells you nothing about which project absorbed the cost.
This pattern repeats dozens of times per week across every active jobsite. Unlike office-based businesses where purchasing flows through an AP system, field spending in construction is spontaneous, decentralized, and paper-dependent by default. The office doesn't know the purchase happened until a card statement arrives, and by then the context is gone.
The problem is structural, not behavioral. Even disciplined field crews struggle to maintain clean receipt records when they're managing active work.
Contributing factors specific to construction:
Disorganized supply run receipts create downstream problems that compound across the job lifecycle. Controllers who've managed construction books know this cost well.
The modern approach to supply run receipt management removes the paper step entirely. Construction-specific expense platforms allow field personnel to photograph receipts at the point of purchase using a mobile app, immediately attaching a job number, cost code, and description before the receipt leaves their hands. The transaction is timestamped, geotagged, and routed for approval — all before the crew drives away from the supply house.
This model works because it meets field crews where they are. Asking a superintendent to log into a desktop ERP after hours to code receipts fails in practice. Asking them to tap three fields on a phone while standing at the register succeeds.
Before: Superintendent buys $340 in fittings, receipt goes in the truck, surfaces at month-end without a job number, gets coded to overhead as a guess.
After: Superintendent photographs receipt at the counter, selects Job 2241 / Cost Code 09-200, submits. Controller sees it in the approval queue within minutes, posts it that day.
Vergo is a card-agnostic expense management platform built for construction. Connect any corporate or project credit card and get full visibility and control over field spending.
Every unrecorded supply purchase understates the true cost-to-date on a job. Over the course of a project, accumulated missing receipts can shift a job's reported margin by several percentage points. Controllers discover the gap at project closeout, when corrective action is no longer possible and profit has already been overstated in prior periods.
Compliance improves when submission requires minimal effort and fits naturally into the field workflow. Mobile photo capture at the point of purchase — rather than nightly or weekly batch submission — produces the highest compliance rates. Clear accountability, where unapproved card transactions are held from reimbursement, also drives consistent behavior without creating adversarial dynamics.
AP invoices arrive from known vendors with purchase order references and formal documentation. Supply run receipts are informal, often from local retail suppliers, purchased without a PO, and captured in the field by non-accounting personnel. This makes them structurally harder to code, track, and reconcile — they require a different collection process than standard vendor invoices.
WIP schedules calculate over/under billings based on cost-to-date versus estimated total cost. Missing supply receipts understate cost-to-date, making jobs appear more profitable than they are. This produces overbillings that must be reversed in later periods or, worse, misrepresents the company's financial position to lenders, sureties, and auditors who rely on WIP accuracy.
Yes. Purpose-built construction expense platforms like Vergo integrate natively with all major construction ERPs — including Sage, Viewpoint, Procore, Foundation, QuickBooks, Acumatica, CMiC, and others — so coded receipts post directly to job cost ledgers without manual re-entry. This eliminates the double-entry problem and ensures the ERP reflects actual field spending in near real time.
Controllers at mid-size general contractors commonly report 3–5 additional days added to month-end close specifically from chasing field receipts and reconciling card transactions to jobs. The problem scales with crew size and active job count — companies running 10 or more simultaneous jobs often find receipt reconciliation is their single largest month-end bottleneck.