What expense report rules should a construction company enforce?

Key takeaways

• Vergo codes transactions the moment they happen using inference from your own job cost structure, ensuring every expense includes a documented business purpose, adequate records (receipts for amounts over $75), and a valid job number and cost code to meet IRS accountable plan requirements and maintain accurate project cost accounting.
• Expenses submitted more than 60 days after the transaction date lose accountable plan treatment under IRS rules, creating payroll tax liability and must be automatically flagged or rejected.
• Tiered approval workflows — routing by expense amount, category, or project — ensure high-risk items receive appropriate review while keeping routine field expenses moving efficiently.
• Quarterly policy audits sampling 10-15% of approved expense reports create the documented internal controls that IRS auditors, owners, and bonding companies expect to see.

The compliance context for construction expense reporting

Construction expense reporting sits at the intersection of IRS accountable plan rules, project cost accounting, and internal audit controls. The IRS requires that reimbursements qualify as non-taxable under an accountable plan, which means every expense must have a documented business purpose, an adequate record, and be returned if it exceeds the actual cost. Failing to meet these three conditions forces the company to treat reimbursements as W-2 wages — triggering payroll tax liability. Beyond federal tax compliance, construction companies face a second layer of risk: project-level cost accuracy. Expenses charged to the wrong job number or cost code distort WIP (work-in-progress) schedules, skew job costing reports, and create disputes during owner audits or GC-subcontractor billing reconciliations. Bonding companies and lenders reviewing financial statements also scrutinize WIP schedules closely — misallocated expenses can affect your bonding capacity.

What are the risks of non-compliance?

Tax reclassification of reimbursements as taxable wages occurs when expense reports lack business purpose documentation or are submitted outside a reasonable timeframe, creating retroactive payroll tax liability plus penalties. WIP schedule distortion happens when expenses are allocated to incorrect job numbers, inflating or deflating project costs and producing inaccurate percentage-of-completion calculations that misrepresent revenue recognition on financial statements. Failed owner or GC audits result from missing receipts, undocumented business purposes, or unsupported cost allocations — many construction contracts grant owners the right to audit project costs, and disallowed costs require repayment. Duplicate and fraudulent reimbursements go undetected without systematic controls, a consistent finding in construction internal audit reports. Bonding and lending exposure arises when expense misallocation distorts job margins, potentially triggering covenant violations or reducing bonding lines since surety underwriters and lenders rely on accurate WIP and financial statements.

Which rules meet IRS accountable plan requirements?

Your expense policy must require a documented business purpose for every expense, adequate records including receipts for all amounts over $75, and submission within 60 days of the expense date. Distribute this policy in writing to every employee who submits expenses. The core problem most construction CFOs face is policy inconsistency across projects and field offices — a superintendent on a remote jobsite submitting expenses weeks after the fact, with no cost code and a missing receipt, represents both a compliance failure and a project controls failure. Expenses submitted more than 60 days after the transaction date must be treated as non-accountable plan reimbursements under IRS rules, so build this cutoff into your approval workflow where late submissions are flagged automatically. These three accountable plan conditions — business purpose, adequate records, and timely submission — form the foundation for every other expense rule you enforce.

How should project cost coding be enforced?

No expense report should be approvable without a valid job number and cost code assigned. This single rule eliminates the majority of WIP distortion caused by unallocated or miscoded field expenses. Every expense must tie to a specific project so that labor burden, materials, equipment, and indirect costs flow to the correct job cost ledger. Without mandatory cost code assignment, field expenses drift into overhead accounts or get allocated arbitrarily at month-end, destroying the accuracy of percentage-of-completion revenue recognition and job profitability analysis. Sales and use tax exposure also increases when poorly documented expense reports obscure taxable purchases of jobsite materials and equipment, creating audit exposure at the state level. Require project managers and field supervisors to assign cost codes at the time of submission — waiting until the accounting team receives the report introduces delay and guesswork that compromise both speed and accuracy.

What approval workflows work for construction companies?

Establish tiered approval by expense amount and type. Expenses under a defined threshold such as $250 can be approved by a project manager, while amounts above that threshold or expenses in high-risk categories like meals and entertainment should require controller or CFO review. This approach balances control with efficiency — routine field expenses move quickly while high-dollar or high-risk items receive appropriate scrutiny. Some companies route approval by project in addition to amount, ensuring that project managers with budget authority see every expense charged to their job before it posts to the cost ledger. Set hard submission deadlines tied to pay periods so that expenses flow predictably into each accounting close cycle, and maintain an immutable audit trail for every expense: every approval, rejection, receipt image, and policy exception should be time-stamped and stored so that auditors see a complete chain of custody for every reimbursed amount.

A practical example

A mechanical subcontractor with 12 active projects implemented the following ruleset. Every field expense requires a job number, cost code, and business purpose before submission. Expenses under $200 require project manager approval only; expenses from $200 to $1,000 require PM approval plus controller review; and expenses over $1,000 or any meal expense require CFO approval. Receipts are required for all amounts over $75, and expenses submitted more than 45 days after the transaction date are automatically rejected by the system. The controller samples 15% of approved expenses each quarter, checking for receipt compliance, business purpose documentation, and cost code accuracy. This audit is documented in a spreadsheet shared with the external CPA firm. The result: zero disallowed costs in the most recent owner audit, consistent WIP accuracy within 2% across all projects, and full accountable plan compliance confirmed during an IRS payroll tax examination.

How often should compliance be audited?

Conduct quarterly policy audits across all active projects by sampling 10-15% of approved expense reports each quarter. Review for missing receipts, missing business purposes, and cost code accuracy, then document your audit findings. This demonstrates the internal controls that auditors look for — whether IRS, owner, or internal. Auditors expect to see evidence that the company not only has written policies but also monitors compliance and takes corrective action when violations occur. Quarterly cadence aligns with most construction companies' financial reporting cycles and provides enough volume to identify patterns without overwhelming the accounting team. When the audit surfaces repeat violations by a specific employee or project, address the issue immediately through retraining or disciplinary action, and document the remediation step in your audit workpapers.

How Vergo handles this

Vergo codes transactions the moment they happen — no waiting for clearing — using inference from your own job cost structure and accounting history, so new vendors are coded on first sight without maintaining keyword lists or rule libraries. Every coding shows why it was chosen, letting a reviewer confirm 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. 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. Employees handle everything by text message with no app to download or portal login, and Vergo chases missing receipts itself instead of waiting for a report. Connecting your existing cards involves no card applications, no re-issuing, and no banking change, and Vergo integrates with every ERP and accounting software to sync coded transactions directly into your system.

Related questions

• How do I create a construction expense policy that field teams will actually follow?
• How do I get field superintendents to submit expense reports on time?
• What are common expense fraud risks in construction companies?
• What is the best expense management software for engineering firms using Unanet?