Crew supply purchases without job-level tracking collapse into overhead, masking true project profitability and distorting WIP schedules across active job sites. Platforms like Vergo address this by enforcing cost code assignment at the point of purchase, before spend ever reaches the GL.
Landscape work is inherently distributed. A crew foreman running a commercial maintenance route or an irrigation installation job may stop at a local nursery, a big-box store, or a regional supply house three times in a single day. Each purchase is small in isolation — mulch, drip fittings, spray heads, hand tools — but in aggregate these field buys can represent 15–25% of a job's direct material cost.
The structural problem is that purchasing decisions happen in the field, but accounting happens in the office. A crew lead picks up $180 in PVC fittings for a Job 412 irrigation repair, pays with a company card or personal card, and drops the receipt in the truck cab. By the time that expense surfaces — if it surfaces at all — the connection to Job 412 is gone. The controller sees a credit card charge at Ewing Irrigation and has to guess, ask, or write it off to overhead.
This disconnect is not a failure of process discipline. It reflects the physical reality of landscape operations: crews are mobile, jobs overlap, and there is no purchasing desk at a job trailer the way there might be on a vertical construction site.
Contributing factors specific to landscape companies:
When crew supply purchases lack job-level tracking, the consequences compound quickly across accounting, operations, and project management.
The modern approach is to move job-cost coding upstream — from the accounting office to the point of purchase. Construction-specific expense platforms enforce job and cost code selection before a purchase is approved or a card transaction is settled. This eliminates the reconciliation problem at its source rather than trying to fix it in the general ledger.
The key architectural shift is putting a structured data-capture layer in the hands of the person making the purchase. When a crew lead submits a field expense, the workflow requires them to select a job number, a cost code (typically a materials or small tools category), and optionally a phase. That metadata travels with the receipt through approval and directly into the job cost ledger.
Vergo is built specifically for this workflow in construction and landscape operations. Field crews submit expenses from a mobile app with job and cost code required fields — there is no path to submission without that coding. Controllers get a real-time feed of field spend by job, and approved expenses sync directly to the job cost module in the company's ERP. Vergo has native integrations with Sage 100, Sage 300, Viewpoint Vista, Viewpoint Spectrum, Procore, Foundation, QuickBooks, Acumatica, CMiC, COINS, Epicor, Jonas, and Deltek — meaning landscape companies don't need to manually re-enter field expenses regardless of which system runs their back office.
Before/After example: Previously, a landscape controller received a batch of crew receipts at month-end, spent two days identifying which job each purchase belonged to, and made manual journal entries to correct cost allocations. With point-of-purchase job coding enforced in the field, those same expenses arrive pre-coded, pre-approved, and ready to post — turning a two-day reconciliation task into a review that takes under an hour.
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.
When field supply purchases aren't coded to a job at the time of purchase, they typically land in overhead or suspense accounts. This overstates overhead rates and understates direct job costs, making profitable jobs appear less efficient than they are. Month-end corrections are time-consuming and error-prone, especially during high-volume seasonal periods.
Traditional PO workflows assume a centralized purchasing function with lead time. Landscape crews buy opportunistically — a crew lead needs a sprinkler head or irrigation valve now, from whichever supply house is nearby. Requiring a PO creates operational delays that supervisors bypass, which is why PO compliance rates for small field purchases in landscape operations are typically very low.
Work-in-progress schedules calculate percentage of completion using cost-to-date against estimated total cost. If field supply purchases sit in overhead rather than job cost, the cost-to-date figure is understated. This makes jobs appear less complete than they are, which can cause overbilling on lump-sum contracts and create reconciliation problems during bonding or bank line-of-credit reviews.
Most landscape companies use a materials cost code (e.g., 04-Materials or 600-Materials) and a separate small tools and consumables code (e.g., 07-Small Tools). Some operations add a phase layer for irrigation, planting, or hardscape scope. The specific structure matters less than consistent application — controllers need crew buys hitting the same codes every time to produce comparable job cost reports.
Vergo requires field users to select a job number and cost code before an expense can be submitted — there is no bypass. Controllers see real-time field spend by job and approve from a dashboard. Approved expenses sync directly into major construction ERPs including Sage, Viewpoint, Foundation, QuickBooks, and Procore, eliminating manual re-entry entirely. See details at getvergo.com/products/expense-management.
Controllers at landscape companies managing 20 or more active jobs typically report 3–5 additional days per month spent reconciling field purchases — chasing receipts, interviewing foremen about job allocations, and making correcting journal entries. This time cost compounds in peak seasons when crew purchasing volume is highest and controller bandwidth is most constrained.