Masonry contractors typically collect receipts from field crews, assign costs to job-specific codes, and process reimbursements through payroll or AP. Platforms like Vergo address this by letting workers submit receipts via mobile with job cost codes attached at capture, reducing manual reconciliation for accounting teams.
Employee reimbursements in construction occur when a worker spends personal funds on a legitimate business expense and the company repays them. In masonry, this happens constantly in the field: a foreman stops at a supply house for a bag of Type S mortar, a laborer buys a tuck-pointing bit to keep a job moving, or a crew lead picks up scaffolding ties because the material delivery was short.
Unlike office environments where reimbursements are occasional and predictable, masonry jobsites generate reimbursement requests across multiple active jobs simultaneously. Each expense must be tied to the correct project, phase, and cost code — not just approved and paid. A $47 trip to the masonry supply house isn't just a reimbursement; it's a job cost entry that affects the masonry labor and materials budget for a specific WBS line item.
This distinction between simple reimbursement and job-costed reimbursement is what separates construction accounting from general accounting. Getting it wrong means inaccurate job cost reports, distorted project margins, and billing errors on time-and-material contracts.
The reimbursement process is one of the most error-prone workflows in masonry accounting. Field crews submit crumpled receipts days or weeks after a purchase. The job number is missing. The cost code is guessed. The controller is chasing down three different foremen to find out whether a $200 supply run was for the downtown brick facade or the residential veneer project two towns over.
For an accounting manager, this creates real downstream problems:
For a project manager, untracked field purchases are invisible cost creep. By the time they show up in a job cost report, it's too late to adjust the buyout or flag the GC for a change order.
Scenario 1 — The Problem: A foreman on a commercial brick façade project buys $340 in wall ties and grout from a local supply house on a Friday afternoon. He submits the receipt the following Wednesday with no job number. The AP clerk codes it to overhead. The project's material budget looks $340 under, the GC billing is short, and the overhead account is inflated — all from one untracked receipt.
Scenario 2 — With a Proper Process: The same foreman submits a reimbursement request via a mobile form immediately after purchase. He attaches a photo of the receipt, selects Job #2241 – Civic Center Exterior, and tags it to cost code 04210 – Masonry Materials. The accounting manager reviews and approves it the same day. The expense hits the correct job cost report before the next pay app cutoff.
Scenario 3 — Multi-Crew Complexity: A masonry subcontractor running five simultaneous jobs receives twelve reimbursement requests in one week. Without a system, matching each receipt to the right job, verifying amounts, and ensuring no duplicates is a manual process that can take hours. A structured digital workflow reduces that to a review queue.
High-performing masonry contractors have moved away from paper receipt envelopes and spreadsheet logs. Construction-specific reimbursement platforms let field employees submit expenses from a mobile device, attach receipt photos, and select the job and cost code at the point of submission — before the information is forgotten.
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.
Reimbursements should be coded to the same cost codes used for direct purchases — typically 04200-04220 for masonry materials, and appropriate labor burden or equipment codes for tools. The cost code should reflect what was bought, not who paid for it. Using a catch-all reimbursement code distorts job cost reports and makes billing reconciliation difficult.
On prevailing wage or Davis-Bacon projects, all job-related expenses must be documented with original receipts, the date, the worker's name, and the project number. Some contracts require proof that reimbursed items were used exclusively on the covered project. Missing documentation can trigger audit findings or affect certified payroll compliance during labor department reviews.
Company cards make sense for recurring, predictable purchases from known vendors — like a standing account at a masonry supply house. Reimbursements are better suited for unplanned, small-dollar field purchases. Many contractors use both: company cards for materials and subs, reimbursements for incidental job site expenses under a defined threshold, typically $250 or less.
Reimbursed field purchases are job costs and must appear in the cost-to-date totals used to calculate percent-complete on Schedule of Values billing. If a reimbursement is delayed or miscoded, it can cause a masonry subcontractor to underbill on a pay app — or to bill correctly but lack documentation to support the line item if a GC audits the application.
Vergo lets field employees submit reimbursement requests by job and cost code from a mobile device, with receipt photo capture at submission. Accounting managers review a consolidated queue, approve or reject with notes, and sync approved amounts directly to their ERP. This eliminates manual re-entry and ensures every reimbursement hits the correct job cost report before the next billing cycle.
Most masonry contractors set a per-transaction threshold between $100 and $500 for field-initiated purchases requiring manager pre-approval. Anything above the threshold typically requires a purchase order or company card. Setting clear thresholds reduces unauthorized spending, simplifies the approval workflow, and creates an auditable record of who authorized each job site expense.