Trade contractors reimburse job site purchases by routing receipts through a review process where each expense is coded to a specific job and cost code before payment is issued. Platforms like Vergo address this by combining mobile receipt capture with job-cost coding, keeping reimbursements tied directly to project financials. Untracked reimbursements distort WIP schedules and erode cost-to-complete accuracy.
An employee reimbursement is a payment made to a worker who spent personal funds on behalf of the company. In trade contracting — electrical, plumbing, HVAC, mechanical, and similar trades — this happens constantly. A foreman picks up pipe fittings at a supply house before the PO is approved. An apprentice buys fasteners mid-job to avoid a work stoppage. A service tech grabs refrigerant on a weekend emergency call.
These purchases are legitimate business expenses, but they enter the accounting system through a different door than invoices or purchase orders. They rely on the employee to submit a receipt, the supervisor to verify the work was real, and the accounting team to code it correctly before cutting a check or processing direct deposit.
What distinguishes construction reimbursements from other industries is the job costing requirement. Every dollar reimbursed must be assigned to a job number, a cost code (labor, material, equipment, subcontract, or overhead), and often a cost phase. A reimbursement coded to the wrong job doesn't just create a bookkeeping error — it misrepresents profitability on two jobs simultaneously.
For trade contractors running multiple active jobs, unmanaged reimbursements create compounding problems. The reimbursement process is often informal — receipts handed to a foreman, texts to an office manager, or paper forms dropped at the front desk. Without a consistent intake process, receipts get lost, duplicates get submitted, and job cost reports become unreliable.
The downstream effects are significant:
For a controller, this means the job cost ledger may be understated throughout the project and corrected in a lump sum at month-end — making real-time financial management impossible. For a project manager, it means budget-to-actual reports can't be trusted mid-job.
Before — informal process, broken job costing: A plumbing foreman on the Riverside Medical job buys $340 in copper fittings at Ferguson, pays out of pocket, and hands the receipt to his supervisor at the end of the week. The supervisor puts it on his desk. Three weeks later, the accounting manager finds it and codes it to overhead because there's no job number written on it. The Riverside Medical job shows understated material costs; overhead is overstated. Month-end job cost report is wrong.
After — structured reimbursement process: The same foreman photographs the receipt in the field using a reimbursement submission tool, selects job number 2241 (Riverside Medical), selects cost code 04-200 (plumbing materials), and submits. The project manager approves it that day. Accounting reviews and queues it for the next payment run. The expense hits the right job within 48 hours of the purchase. Job cost data stays current.
Complex scenario — multi-job purchase: A service tech buys $180 in supplies at a hardware store for two different work orders in the same run. She splits the receipt — $95 to job 1801 and $85 to job 1803 — before submitting. Without a system that supports receipt splitting, this either gets coded to one job incorrectly or sits in a queue until someone calls her for clarification.
High-performing trade contractors have moved away from paper-based and email-based reimbursement workflows. They use construction-specific platforms that connect receipt submission directly to job costing, require job number and cost code at the point of submission, and route approvals through the project manager before reaching accounting.
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.
Either method can work, but consistency matters most. Processing through payroll simplifies direct deposit but complicates cost coding. Processing through AP keeps expenses in the right ledger but adds steps. Most construction accountants prefer AP for reimbursements because it preserves job cost integrity and keeps payroll records clean.
Reimbursements should be coded to the same cost code as the purchased item — typically materials (04-xxx), small tools (05-xxx), or equipment (06-xxx), depending on the CSI or company-specific chart of accounts. Coding everything to overhead or a generic expense code defeats the purpose of job costing and makes project profitability reports unreliable.
Industry practice is seven to fourteen days from submission to payment. Delays beyond two weeks create morale problems and informal pressure on managers to bypass approval steps. Contractors with structured workflows — digital submission, same-day manager approval, weekly payment runs — typically reimburse within five to seven business days of receipt submission.
At minimum: an itemized receipt, the job number or work order the purchase supports, the applicable cost code, and supervisor approval. For tax and bonding purposes, the business purpose should also be documented. Credit card statements alone are not sufficient — itemized receipts showing vendor, items purchased, and amount are required.
Duplicate submissions are a real risk when receipts are submitted via email or paper. Prevention requires a centralized submission log with receipt image storage so accounting can visually match submissions. Construction reimbursement platforms like Vergo flag duplicate amounts from the same employee within a defined date range, reducing the manual review burden on the accounting team.
Yes, and they often need to — service techs and foremen frequently purchase supplies for multiple jobs in one trip. The reimbursement process should support line-level job code assignment so each item or dollar amount is allocated correctly. Without this capability, the receipt either gets coded to one job entirely or held up in accounting for manual correction.