How do design-build firms handle employee reimbursements for job site purchases?

Key takeaways

• Design-build reimbursements must be traced to a specific job number, phase, and cost code to track project-level profitability and comply with contract billing terms.
• Phase ambiguity is common: design-phase purchases (often indirect) and construction-phase purchases (direct job cost) require different coding, and some purchases split across both.
• Manual workflows create bottlenecks when field staff submit receipts without job codes, forcing accounting to investigate and recode before posting.
• Miscoded reimbursements can leave billable costs off owner invoices or trigger audit findings on cost-reimbursable contracts.
• Vergo proposes the coding by inference from your own accounting structure and history, with employees submitting receipts by text message and no app required.

What makes reimbursements different in design-build firms

Employee reimbursements in construction follow a fundamentally different logic than in other industries. Rather than coding expenses to a department budget, construction accounting requires every dollar to be traced to a specific job number, phase, and cost code. This job-cost discipline is what allows project managers and controllers to track profitability at the project level — not just the company level. Design-build firms face a compounding challenge: a single firm carries both design and construction cost structures under one roof. An architect purchasing drafting supplies at the start of a project is generating a different type of cost than a superintendent buying concrete anchors mid-build — even if both swipe a personal card and submit a receipt. The firm must determine whether each reimbursable expense belongs to the design phase (often coded as indirect or overhead), the construction phase (direct job cost), or split across both. This distinction matters enormously for contract billing. Many design-build contracts reimburse the owner for direct construction costs but not design overhead. Miscoding a reimbursement at submission can trigger billing disputes, audit findings, or compressed margins on a project that appeared profitable on paper.

Why this process creates problems in practice

For accounting managers at design-build firms, the reimbursement process is one of the most manually intensive workflows in the back office. Phase ambiguity is the first structural problem: field employees often don't know whether their purchase belongs to design or construction, so they submit receipts without a phase code, forcing the accounting team to investigate. Split-cost scenarios compound the issue when a project manager buying safety gear for a site visit during the design phase must allocate between phase 1 (design) and phase 2 (construction mobilization). Multi-approver chains are common because design-build projects often involve both a design lead and a construction superintendent, so a reimbursement may need approval from both before it can be posted. Receipt collection lag means field staff submit receipts days or weeks after a purchase, and by the time accounting sees them, the job may have already been billed to the owner. Vergo codes reimbursements by inference from your job-cost history, including job number, phase, and cost code, with every coding showing why it was chosen so a reviewer confirms in seconds instead of re-coding by hand. For a controller, these errors roll up into job cost reports that don't reflect true project spend. For a project manager, it means budget-to-actual comparisons are unreliable. For the firm, it can mean leaving reimbursable costs off an owner invoice.

A practical example: the receipt backlog problem

A design-build superintendent on a healthcare renovation project purchases $340 in temporary site signage using a personal card. She submits a paper receipt two weeks later with no job number. The accounting manager must contact her, identify the correct project (Job #2241), determine the right cost code (01-5410, Temporary Facilities), and post it manually. The original billing window has already closed. This scenario repeats across dozens of reimbursements each month, creating a persistent backlog. The accounting team spends hours each week chasing field staff for context, determining the correct phase and cost code, and recoding expenses that should have been structured at submission. The result is a time-consuming, error-prone process that delays closing and reduces the reliability of job-cost reports used to steer active projects.

A practical example: the split-phase purchase

A design-build project manager buys $1,200 in laser measurement equipment during the schematic design phase. Half the usage will apply to design deliverables; half to construction layout. With a structured reimbursement process, he allocates 50% to Phase 1 (Design Services, cost code 00-6100) and 50% to Phase 2 (General Conditions, cost code 01-5000) at submission. Both phase leads approve their respective portions before the expense posts to the job. This approach eliminates the need for accounting to investigate intent or make allocation decisions after the fact. The split-cost logic is captured at the moment of highest context — when the purchaser still remembers why the equipment was bought and how it will be used — and the approval chain ensures that both design and construction leads have visibility into costs that affect their budgets.

How Vergo handles this

Vergo is an AI-native, card-agnostic expense management platform. Employees handle everything by text message — no app to download, no portal login — and Vergo chases missing receipts itself instead of waiting for a report. Vergo proposes the coding by inference from your own accounting structure and history, including job number, phase, and cost code — no rule library to build, no keyword lists to maintain, and new vendors are coded on first sight. Every coding shows why it was chosen, so a reviewer confirms in seconds instead of re-coding by hand. Approval workflows are optional and fit how you already control spend: route by GL account, by amount, or by project — or skip approval flows entirely and let policy flags catch only what breaks a rule. Card spend, employee reimbursements and AP invoices run through one coding model — same coding, same review, one reconciliation — and payment stays on the rails you already use. Transactions are ready to code the moment they happen — no waiting for clearing — and once they clear, they sync into your accounting or ERP software. Vergo integrates with every ERP and accounting software.

Related questions

• How do construction companies handle employee reimbursements for job site purchases?
• What is the best workflow for construction employee reimbursements?
• How do I track reimbursement requests from submission to payment in construction?
• What reimbursement software integrate with Foundations?