Does CoConstruct have built-in reimbursements or do I need a separate tool?
Vergo provides card-agnostic expense management that handles reimbursements alongside card spend with job-cost coding and ERP sync. CoConstruct does not include built-in employee reimbursement workflows; you will need a separate tool to capture receipts, route approvals, and post coded transactions to your accounting system.
Key takeaways
- CoConstruct focuses on project management, estimating, and client billing — not employee expense reimbursements.
- Construction reimbursements require job and cost-code assignment, approval routing, and direct posting to your accounting system.
- Without a dedicated workflow, reimbursements are often posted late, to the wrong job, or without receipts attached.
- Vergo handles employee reimbursements alongside card spend and AP invoices through one coding model, with text-based receipt capture and direct ERP sync.
What CoConstruct Does and Doesn't Handle
CoConstruct (now Buildertrend, following a 2021 merger) is a project management, estimating, and client communication platform built primarily for residential builders and remodelers. Its financial features focus on budgeting, change orders, purchase orders, and client-facing billing — not on employee expense reimbursements.
Reimbursement management is a distinct finance function. It involves collecting receipts from field employees or subcontractors, categorizing each expense against a job number and cost code, approving the claim through a defined workflow, and issuing payment. None of these steps exist as a native, end-to-end workflow inside CoConstruct.
Some contractors attempt to log reimbursable expenses as line items on a budget or as vendor bills inside their connected accounting system, but this creates manual reconciliation work and often leaves receipts disconnected from the underlying transaction.
Why Reimbursements Are a Construction-Specific Problem
In most industries, employee reimbursements are a simple accounts payable function. In construction, they carry additional complexity because every dollar must trace back to a specific job, phase, and cost code — or it distorts job cost reporting.
For a controller managing multiple active projects, untracked reimbursements create several downstream problems. Job cost overruns appear without warning when reimbursements are posted late or to the wrong cost code. Committed cost tracking breaks down if field purchases made on personal cards aren't captured in real time. Audit exposure increases when receipts are collected via email or text and stored outside the accounting system. Payroll timing conflicts arise when reimbursements are bundled with payroll rather than processed as separate AP transactions. Lien waiver and billing accuracy suffers when reimbursable costs aren't captured before an AIA or schedule-of-values invoice is submitted.
A practical example
A project manager for a $3.2M custom home submits three months of fuel and material receipts at once. The accounting team has already closed two billing periods. The costs get posted to the current month, inflating job costs on a project that's already shown as under budget, masking a real overage on the framing phase.
In a second scenario, a field supervisor works across two active jobs — Maple Creek Lot 4 and Riverside Phase 2 — and submits a single receipt batch without specifying which costs belong where. The AP clerk assigns everything to the most recent job. Both job cost reports are now wrong, and the error isn't caught until the project closeout audit.
When field employees can photograph receipts at point of purchase, select the job and cost code from a dropdown tied to the active project list, and submit for manager approval, the controller sees the request in real time, approves or flags it, and the transaction posts directly to the correct job in the accounting system — no manual entry, no period timing issues.
How Vergo handles this
Vergo handles employee reimbursements alongside card spend and AP invoices through one coding model. Employees submit receipts and expense details by text message — no app to download, no portal login — and Vergo chases missing receipts itself. Transactions are ready to code the moment they happen, with no waiting for clearing.
Vergo proposes the coding by inference from your own accounting structure and history — 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.
Once transactions clear, they sync into your accounting or ERP software. Vergo integrates with every ERP and accounting software, so card spend, employee reimbursements, and AP invoices run through the same coding, the same review, and one reconciliation — and payment stays on the rails you already use.
Related questions
Frequently Asked Questions
Can I track reimbursements inside CoConstruct's budget module?
You can manually enter reimbursable costs as budget line items in CoConstruct, but there is no receipt capture, approval workflow, or automatic posting. This creates a reconciliation burden for the accounting team and leaves no audit trail connecting the transaction to the original receipt or the employee who submitted it.
What's the difference between an employee reimbursement and a subcontractor expense in construction?
Employee reimbursements cover out-of-pocket purchases made by W-2 employees and are processed through payroll or accounts payable with IRS substantiation rules applied. Subcontractor expenses are billed through invoices under a subcontract agreement. Both must be coded to a job and cost code, but they follow different approval workflows and accounting treatments.
How should construction reimbursements be coded for job costing accuracy?
Each reimbursement should be assigned a job number, phase code, and cost code at the time of submission — not during back-office processing. Coding at the source, by the person who made the purchase, produces the most accurate job cost data. Controllers should define a required field set that mirrors the chart of accounts used in the ERP.
Does connecting CoConstruct to QuickBooks solve the reimbursement gap?
The CoConstruct–QuickBooks integration syncs budgets, invoices, and purchase orders, but it does not add a reimbursement submission or approval workflow. Controllers still need employees to submit receipts manually, and those receipts must be manually entered into QuickBooks. The integration does not automate expense capture or cost-code assignment for field reimbursements.
What should a controller look for in a construction reimbursement tool?
Key criteria include mobile receipt capture with OCR, mandatory job and cost code fields on every submission, configurable approval routing by project or dollar threshold, and direct ERP integration that posts approved expenses without manual rekeying. Construction-specific tools should also support lien-waiver-period cutoffs and match the cost code structure of the connected accounting system.
How does Vergo handle reimbursements for contractors using multiple ERPs?
Vergo has native integrations with all major construction ERPs — including Sage, Viewpoint, Procore, Foundation, QuickBooks, Acumatica, CMiC, COINS, Epicor, Jonas, and Deltek. Approved reimbursements post directly to the correct job and cost code in whichever ERP the contractor uses, eliminating duplicate data entry and reducing the risk of miscoding.



