What do I do when a construction worker loses the receipt for a reimbursable purchase?
Vergo automates lost receipt handling by letting employees submit reimbursements by text, chasing missing receipts automatically, and storing the full approval chain against the job cost code. For manual workflows, request a written lost receipt declaration from the worker, collect substitute documentation like bank statements or vendor duplicates, route through project manager and accounting for approval, and document the exception in your audit trail.
Key takeaways
- Vergo prevents most lost receipt situations by letting employees handle reimbursements by text and chasing missing receipts automatically, with the full approval chain stored against the job cost code.
- A lost receipt reimbursement requires a written declaration from the worker stating vendor, date, amount, item description, and business purpose.
- Substitute documentation—bank statements, vendor duplicates, order confirmations—should be collected to support the claim.
- The expense must be assigned to the correct cost code and job number before routing through project manager and accounting approvals.
- Document the exception with all substitute documents and approvals in your audit trail, flagged for job cost review.
- Setting a clear lost receipt policy with thresholds, deadlines, and approval levels before incidents occur prevents confusion and delays.
Why lost receipts are a persistent problem in construction
Construction reimbursements fail at the documentation stage more than any other point in the process. Workers purchasing materials at lumber yards, renting equipment from local suppliers, or buying safety gear in the field rarely have a reliable way to capture and store paper receipts before they're lost, soaked, or discarded on a job site. The handoff from field to office is the most common failure point. A foreman submits a reimbursement request days after the purchase, and by then the receipt is gone. Meanwhile, the accounting manager needs documentation to post the expense to the correct cost code, satisfy lien waiver requirements, and stay compliant with IRS substantiation rules. Common breakdowns include workers submitting reimbursement requests verbally with no backup, accounting teams holding up reimbursements while waiting on receipts that never arrive, project managers approving expenses they can't verify against the job budget, and month-end close delays caused by unresolved missing-receipt exceptions piling up.
The recommended workflow for lost receipt reimbursements
Resolving a lost receipt claim without compromising your audit trail or internal controls requires a structured process. First, the employee submits a written lost receipt declaration completing a standardized form that states the vendor name, purchase date, amount, item description, and business purpose, with a signature and the relevant job number. Next, collect substitute documentation: request any available alternatives such as a bank or credit card statement showing the charge, a vendor-issued duplicate receipt or invoice, an order confirmation email, or a photo of the purchased item with a visible timestamp. Assign the correct cost code before routing for approval—the employee or their direct supervisor maps the expense to the appropriate cost code and phase, since an unclassified expense cannot be posted to the job cost ledger. Route to the project manager for job-level approval so the PM verifies the purchase was legitimate, necessary for the project, and within budget for that cost category. Escalate to the accounting manager for exception review of the declaration, substitute documentation, and PM approval before authorizing payment; for amounts above a defined threshold (commonly $50–$100), a second approver or controller sign-off may be required. Document the exception in your audit trail by recording the lost receipt declaration, all substitute documents, and the approval chain in the employee's reimbursement file, referencing the job number and cost code in the audit note. Finally, process payment and sync to the ERP by posting the approved expense to the job cost ledger under the verified cost code, flagging it as a lost-receipt exception so it surfaces during job cost reviews.
Tips for construction accounting teams
Prevention and clear procedures reduce the frequency and impact of lost receipt incidents. Set a clear lost receipt policy before an incident occurs by defining thresholds, required documentation, and approval levels in writing, then share it during onboarding so field workers know the process before they need it. Require declarations within 5 business days of the purchase, because the longer a worker waits, the harder it is to locate substitute documentation. Train superintendents and foremen, not just office staff, since they are the first line of review on job sites and can often retrieve vendor invoices directly from suppliers before the receipt is gone for good. Keep a vendor contact list by project so a quick call to a frequently used lumber yard or equipment rental company can produce a duplicate receipt within hours. Vergo prevents most lost receipt situations by letting employees handle everything by text message and chasing missing receipts itself, so the documentation is captured at point of purchase before it can be lost on the job site.
How Vergo handles this
Vergo prevents most lost receipt situations by letting employees handle everything by text message—no app to download, no portal login—and photographs of receipts attach directly to reimbursement requests at point of purchase. Vergo chases missing receipts itself instead of waiting for a report, so workers receive automatic follow-ups when documentation is incomplete. When a lost receipt does occur, the full approval workflow routes by GL account, by amount, or by project to fit how you already control spend, and the complete audit trail—declaration, substitute documentation, and approval chain—stores against the transaction. Card spend, employee reimbursements and AP invoices run through one coding model with the same coding, same review, and one reconciliation. Transactions are ready to code the moment they happen, and once they clear, they sync into your accounting or ERP software with no manual re-entry at month-end close.
Related questions
Frequently Asked Questions
Is a lost receipt declaration legally sufficient for IRS purposes?
The IRS allows an employee's written statement as substitute documentation under an accountable plan, provided it includes the amount, date, place, and business purpose of the expense. The declaration must be paired with any available corroborating evidence—such as a bank statement—and retained for at least three years with your reimbursement records.
What dollar threshold should trigger a second approver for lost receipt claims?
Most construction accounting policies set the secondary approval threshold between $50 and $100 for lost receipt exceptions. Any claim above that amount should require both the project manager and the accounting manager or controller to sign off. Document your threshold in your written expense policy so it's applied consistently across all projects and crews.
Can a worker's bank statement substitute for a missing receipt?
Yes—a bank or credit card statement showing the transaction date, vendor name, and amount is widely accepted as substitute documentation in construction reimbursement workflows. It should be attached to the lost receipt declaration and clearly annotated with the job number, cost code, and item purchased. Some auditors may still request a vendor-issued duplicate as additional corroboration.
How should lost receipt exceptions be handled during a job cost audit?
Flag each lost receipt reimbursement with an exception code in your job cost ledger so auditors can locate them quickly. Ensure the declaration, substitute documentation, and full approval chain are stored together in the employee's reimbursement file. Auditors will look for evidence that your exception process was followed consistently, not that every receipt was original.
How does Vergo handle the approval routing for lost receipt exceptions?
Vergo routes lost receipt declarations through a configurable multi-step approval workflow—field worker to project manager to accounting manager—with each step timestamped and stored automatically. The exception is tagged to the job number and cost code, and once approved, it syncs to your connected ERP without manual re-entry, keeping your job cost ledger current at close.
What if the vendor can no longer provide a duplicate receipt?
If a vendor cannot reproduce a receipt, the employee's signed declaration plus any indirect evidence—a photo of the purchased item, a project log entry referencing the material, or a supervisor's corroborating statement—can satisfy most internal audit standards. Document every attempt to obtain the receipt and note the vendor's inability to provide one as part of the exception file.



