Design-build firms collect job site receipts, apply cost codes by project phase, and route reimbursements through project-based approvals before syncing to their accounting system. Platforms like Vergo address this by supporting split cost coding across design and construction phases within a single reimbursement submission.
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.
For accounting managers at design-build firms, the reimbursement process is one of the most manually intensive workflows in the back office. Several structural factors make it harder than it looks:
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.
Scenario 1 — 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.
Scenario 2 — 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.
Scenario 3 — The compliant workflow: A design-build firm implements a mobile reimbursement submission process. Field and design staff photograph receipts immediately, select the job number and cost code from a dropdown tied to active projects, and route automatically to the correct phase approver. Accounting receives pre-coded, approved expenses ready to post — eliminating the backlog and the recode step entirely.
Leading design-build firms have moved away from email-and-spreadsheet reimbursement workflows toward purpose-built construction finance platforms that enforce job costing at the point of submission. These platforms require employees to select a project and cost code before a reimbursement request can be submitted, eliminating the recode burden on 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.
Cost codes for reimbursements depend on phase and cost type. Design-phase reimbursements typically fall under indirect or overhead cost codes (e.g., 00-6100 for design services). Construction-phase reimbursements post to direct job cost codes such as General Conditions (01-5000) or the applicable trade division. The correct code depends on what was purchased and when in the project lifecycle.
A reimbursement should be split when a purchase genuinely serves more than one contract phase. Common examples include equipment used in both design surveys and construction layout, or safety gear purchased during mobilization that bridges design and build phases. The split should reflect actual usage and be documented to support any owner billing or audit review.
The most effective prevention is enforcing a submission deadline tied to the project billing cutoff — typically 5 to 7 business days before month-end close. Firms also use mobile receipt capture so field staff can submit immediately after a purchase rather than batching receipts. Pre-coding at submission eliminates the accounting review step that most commonly delays posting.
Approval authority should follow the cost being reimbursed. Design-phase expenses are typically approved by the design lead or project architect. Construction-phase expenses go to the project superintendent or construction manager. Expenses above a set dollar threshold — commonly $500 or $1,000 — should require a second approval from the project executive or controller before posting.
Yes. Construction finance platforms with native ERP integrations can push approved, job-coded reimbursements directly into the general ledger without manual re-entry. Vergo supports this for all major construction ERPs including Sage, Viewpoint, Foundation, Procore, QuickBooks, Acumatica, CMiC, COINS, Epicor, Jonas, and Deltek — eliminating duplicate data entry and reducing posting errors.
At minimum: an itemized receipt, the job number, cost code, and a brief description of business purpose. For purchases over the firm's capitalization threshold, additional justification may be required. If the expense is potentially billable to the owner, employees should also note the contract line item the purchase supports, which simplifies invoice backup preparation.