How do I code fuel expenses to the right construction job?

Why Fuel Expenses End Up in Overhead

Fuel is one of the most frequently miscoded expenses in construction accounting. Unlike a material delivery with a purchase order tied to a job, fuel purchases happen at gas stations, on-site mobile fueling trucks, or through fleet fuel cards — none of which automatically associate the transaction with a specific project.

The breakdown typically follows a predictable pattern:

• No job context at purchase. A superintendent fills up a pickup truck between two job sites. The receipt shows a dollar amount and a gas station address — nothing that tells accounting which job benefited.
• Fleet fuel cards lack job-level coding. Most fleet cards (WEX, Fuelman, Comdata) categorize by vehicle or driver but not by active project. Accounting receives a monthly statement with hundreds of transactions and no job numbers.
• Field crews skip receipt submission. Operators and foremen treat fuel stops as low-priority paperwork. Receipts get lost, submitted weeks late, or arrive without job or equipment details.
• Accounting defaults to overhead. When a fuel receipt cannot be matched to a job, the path of least resistance is coding it to a general fuel overhead account. Over a fiscal year, this can shift tens of thousands of dollars away from true job costs.

The result is inflated overhead, understated job costs, and profitability reports that hide which projects are actually burning through fuel budgets.

Recommended Workflow for Coding Fuel to the Right Job

1. Establish a fuel cost code in your job cost structure. Create a dedicated cost code (e.g., 4-3200 or a subdivision under equipment costs) so fuel is never lumped into miscellaneous expenses. Apply this code consistently across every active job.
2. Require job number and equipment ID on every fuel transaction. Make it policy: no fuel receipt is complete without the job number the equipment is serving and the asset tag or unit number of the vehicle or machine fueled.
3. Capture data at the point of purchase. Have operators photograph the receipt and enter the job number, cost code, and equipment ID immediately — at the pump or fueling truck. Delayed entry is where data degrades.
4. Match fleet fuel card transactions to jobs weekly. Pull the weekly transaction report from your fleet card provider. Cross-reference each transaction against equipment dispatch logs or daily field reports to assign the correct job number.
5. Route coded fuel expenses through a project manager or superintendent for approval. The PM or super confirms that the equipment was active on that job during the transaction date. This is a 30-second verification that catches miscodes before they hit the general ledger.
6. Sync approved fuel expenses to your ERP's job cost module. Once approved, the coded expense should flow directly into your construction ERP — whether that is Sage 300, Viewpoint Vista, Foundation, or another platform — without manual re-entry.
7. Run a monthly fuel-to-job reconciliation. Compare total fuel spend (from fleet card statements and submitted receipts) against total fuel coded to jobs. The gap is your unallocated fuel — the amount still sitting in overhead that should be distributed.
8. Allocate residual fuel based on equipment hours. For any fuel that cannot be traced to a single job, allocate proportionally using equipment hour logs from daily reports or telematics. This is more defensible than a flat overhead spread.

Tips for Construction Teams

• Pre-load active job numbers on mobile devices. Field crews should never have to remember or look up a job number. Give them a dropdown of active projects so coding takes seconds, not minutes.
• Set a 48-hour submission window for fuel receipts. Receipts older than two days are exponentially harder to code correctly. Enforce the deadline with automated reminders.
• Track fuel consumption per equipment unit per job. This data does more than fix accounting — it reveals which machines are burning fuel inefficiently and which jobs have excessive idle time.
• Use equipment dispatch logs as a cross-check. If a dozer is dispatched to Job 2240 all week, every fuel transaction for that unit during that period should map to 2240. Dispatch logs are your audit trail.
• Automate the capture-to-ERP pipeline. Platforms like Vergo let field crews photograph a fuel receipt, tag the job and cost code on their phone, and sync the approved expense directly to your construction ERP — eliminating the manual spreadsheet step that causes most miscoding.
• Flag fuel transactions above a threshold for review. Set a dollar or gallon threshold (e.g., over 100 gallons) that triggers automatic review. Large fills are high-impact if miscoded.

How Vergo Helps

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.

• Job-cost coding at the point of capture — field teams assign job number, cost code, and cost type from their mobile device before the receipt leaves the job site.
• Per-job spend controls — set card limits by project, cost code, or cardholder so spending stays within approved budgets.
• Mobile receipt capture — superintendents and PMs photograph receipts on-site with automatic data extraction.
• Role-based approval workflows — route expenses through project managers, job-level approvers, and controllers based on your org structure.
• Vergo integrates natively with major construction ERPs, syncing coded expenses directly into job cost and general ledger without manual re-entry.

Related Questions

• Why do construction expense coding errors happen so often?
• Best way to automate cost code assignment for construction expenses
• How do construction companies handle expense reports with job cost codes?
• What is the best expense management software for oil and gas companies using Oracle?