Plumbing contractors typically reimburse job site purchases by collecting receipts, mapping costs to specific job numbers, and processing payments through payroll or AP. Platforms like Vergo address this by letting field workers submit receipts via mobile and tag expenses directly to cost codes, reducing miscoding and delays. Without a structured workflow, reimbursements often arrive late and erode both job margins and crew trust.
A plumbing employee reimbursement occurs when a field worker spends personal money on a job-related purchase and the company pays them back. In plumbing, these purchases happen constantly: a journeyman grabs copper fittings at the supply house to avoid a job stoppage, a foreman pays a permit fee at the municipal office, or a service tech buys a specialty tool to finish a same-day call.
Unlike a corporate credit card program, reimbursements put the initial financial burden on the employee. This creates an obligation on the employer's side — to repay accurately, quickly, and with a complete record attached. The record-keeping side is where most plumbing accounting teams struggle. A crumpled receipt handed in Friday afternoon, with no job number and no cost code, is nearly impossible to allocate correctly after the fact.
For job costing purposes, the distinction matters: a fitting purchased for the Westfield Apartments rough-in must be charged to that job's materials cost code, not the general overhead account. Misallocation quietly inflates overhead and understates true project costs, making future bids less accurate.
Plumbing contractors operate across multiple active jobs simultaneously. A crew may visit three different sites in a single day, making small purchases at each stop. When reimbursement requests come in without clear job attribution, the accounting team faces a sorting problem: reconstruct where each purchase belongs, often days or weeks after the fact.
This has direct consequences across roles:
A common failure mode: a plumbing company processes reimbursements through payroll once a month. An employee submits a $340 supply house receipt with no job noted. Accounting codes it to overhead. The job it was actually purchased for shows a $340 materials underrun — and the PM thinks the crew came in under budget. They're not. The cost is just hidden.
Scenario 1 — The manual process problem: A foreman on a commercial tenant build-out buys $215 in PEX fittings mid-week to avoid a supply delay. He texts a photo of the receipt to the office. The office coordinator prints it, staples it to a reimbursement form, and hands it to the controller on Friday. The controller manually looks up the job number, codes it, and queues it for the next payroll run — two weeks away. The foreman is out-of-pocket for 10 days.
Scenario 2 — A structured process in action: The same foreman submits the receipt through a mobile reimbursement app at the supply house, selects the job from a dropdown ("TenantBuildout-Suite400"), picks cost code 05-210 (Rough Plumbing Materials), and adds a short note. The accounting manager reviews and approves it the same day. The expense posts directly to the job cost ledger, and the reimbursement is included in the next weekly ACH run.
Scenario 3 — Permit fee reimbursement: A plumbing superintendent pays a $175 permit pull fee at city hall using personal funds. Without a structured process, this gets submitted as a generic "permit expense" with no job reference. Properly handled, it posts to the job's Permits & Inspections cost code and flows into the job's true cost total — critical when reconciling against the GC's allowance.
Leading plumbing contractors have moved away from paper-based or payroll-only reimbursement processes. Construction-specific platforms now let field employees submit reimbursements from their phones with receipt photos, job selections, and cost code assignments — eliminating the manual reconstruction work on the accounting side.
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.
At minimum: a legible receipt image, the job number or job name, the applicable cost code (e.g., rough materials, permits, small tools), the purchase date, and a brief description of what was bought and why. Missing any of these forces the accounting team to follow up, delaying approval and payment.
Both methods are used, and each has tradeoffs. Payroll reimbursements are convenient for employees but tie payment to a fixed cycle, often meaning a 1-2 week wait. AP-based reimbursements can be issued faster via ACH but require employees to be set up as vendors. Many mid-size plumbing contractors use AP for speed and audit trail clarity.
Standard controls include requiring original receipts (not summaries), flagging duplicate amounts from the same employee within a short time window, requiring manager approval before accounting approval, and setting per-transaction dollar limits that trigger additional review. Some contractors require two signatures on reimbursements above a defined threshold, typically $500.
When a single purchase covers multiple jobs — such as a shared bag of fittings split across two sites — the employee should note the allocation split at submission. The accounting manager then splits the transaction across the relevant job cost codes. Platforms designed for construction make this split-coding step part of the submission form rather than a manual workaround.
Most plumbing contractors code field material purchases to a Materials or Rough Materials cost code (often in the 05-200 range in a CSI-based chart of accounts). Small tools under a capitalization threshold typically go to a Small Tools or Consumables code. The correct code depends on the contractor's job cost structure and should be documented in a field purchasing policy.
Yes. Platforms built for construction, including Vergo, sync approved reimbursements directly to ERPs like Sage, Viewpoint, Foundation, and QuickBooks, posting the expense to the correct job and cost code without manual re-entry. This eliminates the dual-entry problem that creates reconciliation errors between reimbursement records and the general ledger.