What purchases should be reimbursable vs. on a company card in construction?

Key takeaways

• Company cards should cover recurring, budgeted expenses like fuel, monthly subscriptions, and office supplies where amounts are predictable.
• Employee reimbursements make sense for unplanned job-site purchases under a threshold (commonly $500), where field crews need to buy materials or tools immediately.
• Vergo runs card spend, employee reimbursements, and AP invoices through one coding model—same coding, same review, one reconciliation—so you don't maintain separate workflows for different payment types.
• Receipt capture and approval workflows should work the same way for both reimbursements and card purchases to avoid duplicate processes.
• Clear dollar thresholds and project-level routing reduce confusion about which payment method to use.

When to use company cards

Company cards work best for recurring, budgeted expenses where amounts are predictable and vendors are known in advance. Fuel purchases, monthly software subscriptions, regular supplier orders, and office supplies fit this category because they appear on budget forecasts and happen on a set schedule. Using a company card for these purchases eliminates reimbursement paperwork and speeds up month-end reconciliation, since the transaction feeds directly from the card network into your accounting system. Project managers and superintendents carrying company cards can also handle larger equipment rentals and bulk material orders that exceed typical reimbursement thresholds, ensuring those purchases stay within approved budgets and get coded to the correct job.

When employee reimbursement makes more sense

Employee reimbursement fits unplanned, small-dollar purchases that happen on the job site when a company card isn't available or practical. A crew chief buying fasteners at a local hardware store on Saturday, a foreman grabbing safety vests when a new worker arrives mid-week, or a superintendent paying for emergency equipment repair all represent scenarios where waiting for a card authorization would delay the work. Setting a clear dollar threshold—commonly $500—gives field employees the autonomy to solve problems immediately while keeping large purchases on the company card for better tracking. The trade-off is administrative: reimbursements require receipt collection, manual submission, review, and a separate payment run, which takes more effort than reviewing a card transaction that's already captured.

A practical example

A mid-size general contractor assigns company cards to all project managers and site superintendents, with individual card limits tied to each project's monthly budget. Recurring expenses like fuel for company trucks, equipment rentals from regular vendors, and monthly software subscriptions all go on those cards. Field foremen and crew leads, meanwhile, use personal funds for unplanned purchases under $500—a last-minute concrete mix delivery, replacement drill bits, or safety supplies when inventory runs low. Each foreman photographs the receipt on-site and texts it for reimbursement, and the project manager approves it the same day. At month-end, both the card transactions and the approved reimbursements flow into the ERP under the same job-cost structure, so the accounting team reconciles everything in one pass instead of managing two separate workflows.

Setting thresholds and approval routing

Clear dollar thresholds eliminate guesswork about which payment method to use. Most construction companies set reimbursement limits between $250 and $500, requiring anything above that threshold to go on a company card with prior approval. Approval routing should mirror your org structure: project managers review expenses for their own jobs, controllers or accounting managers handle cross-project or overhead costs, and executive approval kicks in only for amounts above a high threshold like $5,000. Routing by job or cost code ensures that purchases hit the right budget line and get reviewed by someone who knows whether the expense makes sense for that phase of work. Approval workflows should apply consistently whether the purchase came from a company card or a reimbursement request, so employees don't see one path as easier to bypass than the other.

How Vergo handles this

Vergo runs card spend, employee reimbursements, and AP invoices through one coding model—same coding, same review, one reconciliation—so you don't maintain separate workflows for different payment types. Employees handle reimbursements by text message with no app to download or portal login, and Vergo chases missing receipts itself instead of waiting for a report. 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. Vergo proposes the coding by inference from your own accounting structure and history, with no rule library to build and new vendors coded on first sight, and every coding shows why it was chosen so a reviewer confirms in seconds instead of re-coding by hand. Transactions are ready to code the moment they happen—no waiting for clearing—and once they clear, they sync into your accounting or ERP software. Connecting your existing cards involves no card applications, no re-issuing, and no banking change.

Related questions

• What should a construction company include in its reimbursement policy?
• What are the IRS rules for employee reimbursements in a construction company?
• How do I set spending limits for construction employee reimbursements?
• Bill.com vs construction-specific reimbursement management software — which is better for a GC?