Approved reimbursements in a construction ERP route through AP or payroll depending on payout method, with job-cost coding applied before posting to keep expenses out of overhead. Platforms like Vergo address this by capturing cost codes and job numbers at submission, so approved expenses sync directly to the project ledger without manual reclassification.
A reimbursement workflow in construction isn't a single step — it's a handoff chain that crosses at least three functional areas: project management, accounting, and payroll or accounts payable. An employee or subcontractor submits an out-of-pocket expense, a supervisor or project manager approves it, and then the accounting team must route that approved record into the ERP so it produces an actual payment.
The routing decision is critical. If the reimbursement is paid through payroll — common when the recipient is a W-2 employee — it flows into the payroll module as a non-taxable addition. If it's paid via check or ACH to an employee or vendor, it flows into accounts payable as a manual payment or one-time vendor record. Each path requires different data fields, different approval touchpoints, and posts to different GL accounts. Getting the path wrong creates duplicate payments, tax errors, or costs that land in the wrong bucket.
Construction adds another layer that most generic accounting systems don't handle well: every reimbursable expense must carry a job number and a cost code before it can be posted. A field superintendent who buys rebar ties on a personal card isn't creating a general overhead cost — that $47.00 belongs to a specific job, a specific phase, and a specific cost type. Without that coding, the expense is useless for job cost reporting.
For a controller in construction, the approval-to-payment handoff is where reimbursements most often break down. Approvals happen in the field or in a project management tool, but payment happens in the ERP. When those two systems don't communicate, the controller is manually rekeying approved expenses — or worse, relying on employees to email PDFs and hope nothing gets lost.
The practical consequences of a broken handoff include:
For a project manager, this affects the accuracy of job cost forecasts. If reimbursed field costs don't post to the job in real time, the cost-to-complete calculation is wrong — and that flows directly into billing decisions.
Before — manual handoff: A superintendent on a bridge rehabilitation project buys fuel and supplies totaling $312. She submits a paper receipt to the PM, who signs it and puts it in the accounting inbox. Two weeks later, accounting finds it, creates a manual AP entry, and guesses the cost code. The expense posts to the wrong phase. The job cost report shows an unexplained variance at month-end closeout.
After — integrated flow: The same superintendent submits the $312 through a mobile expense tool. She selects job #2241 (Bridge Rehab — Phase 2) and cost code 01-500 (Equipment & Supplies) before submitting. The PM approves digitally. The approved record flows automatically into the ERP's AP module with all coding intact. The payment is issued in the next ACH batch. The job cost ledger updates without any manual entry.
Payroll-path example: A project engineer on a commercial tenant improvement job drives 380 miles to a remote site visit. The approved mileage reimbursement (380 × $0.67 = $254.60) is routed through payroll as a non-taxable addition rather than AP, since the company pays field staff reimbursements on the paycheck. The ERP payroll module captures the job number and cost code, and the amount posts to the correct project cost account without affecting the employee's gross taxable wages.
Leading construction finance teams eliminate the manual handoff by connecting the approval workflow directly to the ERP posting step. When an expense is approved, the system — not a person — determines the correct payment path, validates the job and cost code, and queues the record for payment. Construction-specific platforms are built to handle this routing logic natively, including the payroll-vs-AP split decision and the job costing requirements that generic expense tools ignore.
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.
Payroll routing adds the reimbursement as a non-taxable pay addition on the employee's next check — common for mileage and per diem. AP routing issues a separate check or ACH payment. The correct path depends on company policy, payment timing, and whether the recipient is a W-2 employee or an independent contractor.
Construction accounting is project-based, not department-based. Every dollar of cost must be traceable to a specific job and cost category to produce an accurate job cost report, support WIP schedule calculations, and validate billing. An uncoded reimbursement either gets rejected by the ERP or defaults to an overhead account, distorting project margins.
The most common cause is a system gap between where approvals happen and where payments are issued. Approvals captured in email, paper, or a project management tool don't automatically create a payable record in the ERP. Someone must manually bridge that gap, which introduces delay, data entry errors, and missing documentation at payment time.
Controllers should run a job cost detail report filtered by cost type (typically 'other' or 'equipment') and cross-reference it against the approved expense log. Any reimbursement without a matching approval record, or with a cost code that doesn't align with the stated purpose, should be flagged for review before the period closes.
Yes. Reimbursed field costs that post late or to the wrong job will misstate the actual costs incurred on a project, which directly affects the cost-to-complete estimate and the over/under billing calculation on the WIP schedule. Late-posting reimbursements are a common source of WIP restatements during monthly close.
Vergo automates the handoff by routing approved, job-coded expenses directly into the correct module of the connected ERP — either AP or payroll — without manual rekeying. It integrates natively with all major construction ERPs, so the approved record arrives in the ERP with job number, cost code, and payment method already validated.