MEP contractors handle field reimbursements by collecting receipts, mapping costs to job-specific cost codes, and routing expenses through a tiered approval workflow before payment. Platforms like Vergo address this by letting field technicians capture receipts mobile and auto-assign them to active job cost codes without manual entry.
Employee reimbursements in construction occur when a worker pays out-of-pocket for a job-related expense and the company repays them later. In MEP (mechanical, electrical, and plumbing) contracting, this is especially common because field crews often need to make unplanned purchases mid-installation — a pipe fitting, a specialty connector, or a roll of wire that wasn't in the original material order.
Unlike office-based businesses where reimbursements are relatively infrequent, MEP contractors deal with high-volume, low-dollar transactions spread across dozens of active job sites. Each purchase must be tied to a specific project, a cost code, and a cost type (typically materials or small tools) to flow correctly into the job cost ledger.
The distinction between a reimbursement and a company credit card purchase matters for internal controls: reimbursements carry higher audit risk because the company doesn't control the point of purchase. Receipts must be collected after the fact, which creates gaps when field staff lose paper receipts or submit them weeks after the purchase.
For MEP contractors, a disorganized reimbursement process directly damages job cost accuracy. When a plumber buys $40 in fittings and submits a crumpled receipt three weeks later — or never — that cost either hits the wrong job, the wrong cost code, or disappears entirely. Multiply that across a 15-person field crew running five concurrent jobs, and job cost reports become unreliable.
The downstream effects are significant:
For a controller, this means monthly closes get delayed waiting on missing receipts. For a project manager, it means committed cost reports are understated mid-project. Both problems are avoidable with a structured workflow.
Scenario 1 — The problem (unstructured process): An HVAC technician buys $85 in sheet metal screws from a local supply house on a Friday afternoon to keep a job moving. He submits a handwritten note with a faded receipt two weeks later. The accounting team codes it to a generic overhead account because the job number is illegible. The cost never hits the HVAC retrofit project it belonged to, and the job closes appearing $85 under budget.
Scenario 2 — A structured process in action: An electrical foreman uses a mobile reimbursement submission form to photograph her receipt at the supply house. She selects Job #2241 (Office Buildout — Phase 2), assigns it to cost code 04-220 (Electrical Materials), and adds a note: "Additional conduit couplings — scope change per RFI 14." The submission routes to her PM for approval, then to accounting for posting. The cost hits the correct job within 24 hours.
Scenario 3 — Multi-job complexity: A plumbing superintendent manages crews on three simultaneous jobs. In a single week, reimbursements come in from six different field employees across all three projects. Without a system requiring job number entry at submission, coding defaults to whoever in accounting remembers which crew was on which job — a highly error-prone process.
Leading MEP contractors have moved away from paper-based or spreadsheet-driven reimbursement workflows toward purpose-built systems that enforce job cost coding at the point of submission. The critical requirement is that the reimbursement tool connect directly to the ERP so approved expenses post without manual rekeying.
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.
Reimbursements should map to the same cost codes used for direct purchases — typically materials, small tools, or subcontractor costs depending on what was bought. Most MEP contractors use a cost type flag ("reimbursable") within the existing code structure rather than creating separate reimbursement-specific codes, which keeps job cost reports consistent.
Most construction accountants recommend processing reimbursements through accounts payable rather than payroll. Payroll-based reimbursements can create tax complexity and are subject to payroll cycle delays. AP-based reimbursements post faster, carry cleaner audit trails, and integrate directly with job cost reporting in construction ERPs.
On time-and-material contracts, reimbursed employee purchases are often billable to the owner. The reimbursement workflow must capture receipt documentation, job number, and markup rate before approval. Without this, field purchases get reimbursed internally but never billed to the client — a direct margin leak on T&M work.
Standard practice is a two-step approval: the project manager verifies the job, cost code, and business purpose, then accounting confirms the receipt documentation and dollar amount before issuing payment. For reimbursements above a threshold (commonly $250–$500), some contractors require a second-level approval from the controller or project executive.
There is no federal statutory deadline for business expense reimbursements, but several states (California, Illinois, and others) require reimbursement within a reasonable time — often interpreted as 30 days. Most construction HR policies define a submission window of 30–60 days from the purchase date to maintain receipt quality and cost period accuracy.
Yes. Platforms built for construction finance offer native integrations with ERPs like Sage 100, Sage 300, Viewpoint Vista, and Viewpoint Spectrum, allowing approved reimbursements to post directly without manual entry. Vergo supports all of these integrations, along with Foundation, QuickBooks, Acumatica, CMiC, Procore, COINS, Epicor, Jonas, and Deltek.