Masonry Contractor Employee Reimbursements Explained

How do masonry contractors handle employee reimbursements for job site purchases?

Masonry contractors handle employee reimbursements by capturing receipts at the point of purchase and coding each expense to the correct job, phase, and cost code. Vergo streamlines this with text-based submission and AI-powered coding that matches expenses to projects from the first transaction.

July 29, 2026

Key takeaways

Employee reimbursements in masonry occur when workers use personal funds for job site materials like mortar, tools, or fasteners that must be repaid and coded to specific projects.
Each reimbursement must be tied to the correct job number and cost code to maintain accurate project budgets and prevent billing errors on time-and-material contracts.
Common problems include missing job numbers, delayed receipt submission, duplicate payments, and expenses coded to overhead instead of the correct project.
Vergo handles employee reimbursements through text-based submission where employees send receipts by text message, and AI proposes the coding by inference from your accounting structure and job history — no app to download, no rule library to build.

What employee reimbursements look like for masonry contractors

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.

Why accurate reimbursement coding matters for masonry operations

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. Job cost distortion happens when expenses coded to the wrong job skew profitability reports and can trigger false budget overruns or underruns. AIA billing errors occur on GC subcontracts using Schedule of Values billing, where misallocated costs can cause overbilling or underbilling on pay applications. Missing receipts or undocumented reimbursements create audit exposure, especially on prevailing wage or public works projects. Delayed reimbursements frustrate crews, and some experienced masons will simply stop buying materials out of pocket — stalling jobs. Without a tracking system, the same receipt can get submitted twice across a pay period.

A practical example

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. With a proper process, the same foreman submits a reimbursement request 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. In a multi-crew scenario, 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.

How Vergo handles this

Vergo handles employee reimbursements through a text-based workflow where employees submit receipts and expense details by text message — no app to download, no portal login. Vergo proposes the coding by inference from your own accounting structure and job history, so new vendors are coded to the correct project and GL account on first sight with no rule library to build. 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. Transactions are ready to code the moment they happen, and once they clear, they sync into your accounting or ERP software. 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.

Frequently Asked Questions

What cost codes should masonry contractors use for employee reimbursements?

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.

How should masonry contractors document reimbursements on prevailing wage jobs?

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.

When should a masonry contractor use a company card instead of employee reimbursements?

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.

How do reimbursements affect pay applications and AIA billing for masonry subcontractors?

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.

How does Vergo handle reimbursements across multiple active masonry jobs?

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.

What is a reasonable reimbursement policy threshold for masonry field crews?

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.