Petty cash is difficult to reconcile at the job level and creates common audit liability across active jobsites. Platforms like Vergo address this by tying every reimbursement to a specific project, cost code, and employee — replacing cash drawers with a traceable, job-cost-coded paper trail. Most controllers recommend phasing out petty cash once a company operates two or more concurrent projects.
Petty cash is a fixed float of physical currency kept on-site or in an office, used for small, unplanned purchases — hardware store runs, fuel top-offs, or jobsite supplies under $50. The fund is replenished periodically, typically when it drops below a threshold. The core problem: every transaction depends on a physical receipt being collected, labeled, and matched to a replenishment request — a process that breaks down quickly across multiple crews.
A reimbursement system works differently. An employee pays out of pocket, submits a documented expense request with receipts, and is reimbursed through payroll or a direct payment run. Every request is coded at submission — project number, cost code, expense category — before any money changes hands. This creates a structured workflow rather than a retroactive reconciliation problem.
In construction, the distinction matters more than in most industries. Job costing accuracy depends on expenses being captured and coded correctly at the time of purchase. A petty cash fund replenished in a lump sum forces the bookkeeper to reverse-engineer cost allocations after the fact, often from incomplete or illegible receipts.
Petty cash tracking failures are one of the most common findings in construction audits. Physical cash has no inherent audit trail. When a jobsite superintendent uses the petty cash box for a $35 lumber purchase and a $60 tool rental in the same week, the company has two undocumented transactions that may never get properly allocated to the right job.
For a controller, this creates three compounding problems:
For a project manager, the downstream effect is inaccurate budget-to-actual reporting. If $300 in site supplies was absorbed into a petty cash replenishment rather than charged to the correct cost code, the PM's cost report understates spending and may trigger unplanned overruns in the final accounting.
When petty cash is left unmanaged across five or more active projects, it is common for companies to discover four-figure discrepancies at year-end that cannot be traced to specific jobs, employees, or vendors.
Before — Petty Cash on a Mid-Size Commercial Project:A site superintendent for a $4M office buildout keeps $500 in petty cash on site. Over six weeks, the fund is tapped for concrete sealer, a replacement drill bit, and two fuel fill-ups. When the bookkeeper requests replenishment, three of the five receipts are missing. The $180 in unreceipted purchases gets allocated to overhead — not to Division 03 Concrete or Division 01 General Requirements — distorting the job cost report.
After — Reimbursement System on the Same Project:The superintendent pays for the same purchases out of pocket and submits expense requests through the company's reimbursement workflow within 24 hours. Each request includes a photo of the receipt, the job number, and the relevant CSI cost code. The controller sees approved, coded expenses in real time. The project's cost-to-complete calculation stays accurate throughout the job.
Multi-Site Scenario:A GC running eight simultaneous projects attempts to maintain petty cash floats on three active sites. At month-end close, the AP team spends six hours reconciling discrepancies across three boxes. After switching to a reimbursement system, that same reconciliation takes under 45 minutes — because every expense arrived pre-coded and pre-approved.
Most construction companies that outgrow petty cash move to a structured reimbursement workflow supported by software that enforces coding and approval rules at the point of submission. The best platforms are built around construction-specific data structures — job numbers, cost codes, and phase breakdowns — rather than generic expense categories.
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.
Most construction controllers recommend formalizing a reimbursement system once a company operates two or more concurrent jobsites, or when monthly petty cash replenishments exceed $1,000 in aggregate. At that scale, the reconciliation burden and audit risk outweigh the convenience of on-site cash, and job cost accuracy begins to suffer measurably.
Petty cash can be practical for single-site operations with very low transaction volumes — under five transactions per month. In those cases, a tightly controlled log with mandatory receipts and a designated custodian can be sufficient. However, as project count or crew size grows, the manual controls required to keep petty cash clean become unsustainable.
A well-designed reimbursement workflow requires employees to assign a job number and cost code at the time of submission. This means expenses are coded before approval and before payment — eliminating the retroactive allocation step that distorts job cost reports. Controllers receive pre-coded, receipt-backed data that posts directly to the correct cost codes in the general ledger.
Under IRS accountable plan rules, reimbursements must be tied to a business purpose, supported by receipts for expenses over $75, and submitted within a reasonable time — typically 60 days. Reimbursements that meet these criteria are excluded from employee wages. Petty cash funds without adequate documentation often fail this standard, creating taxable income exposure for both employer and employee.
Most construction companies can complete the operational transition in two to four weeks. The primary tasks are establishing an approval workflow, training field employees on receipt submission, and setting up cost code mapping in the company's accounting system. The larger investment is cultural — field crews accustomed to on-site cash need clear communication about reimbursement timing to ensure buy-in.
Yes. Vergo allows construction companies to configure approval chains by project, dollar threshold, or employee role — so a $50 supply run might require only a foreman's approval, while a $500 equipment rental routes to the project manager and controller. Approved reimbursements sync automatically to all major construction ERPs, eliminating duplicate data entry at month-end close.