How do I capture delivery tickets and match them to job costs?

Key takeaways

• Delivery tickets break down when field staff sign without recording the job number, or when tickets cover multiple jobs without split quantities.
• Best practice requires the foreman to write job number and cost code on the ticket at point of receipt, photograph it immediately, and submit the same day.
• Vergo captures delivery tickets by text message at the job site and codes them by inference to the correct job and cost code — no rule library to build, no keyword lists to maintain, and new vendors are coded on first sight.
• Match each ticket to the open purchase order, flag variances above your tolerance threshold, and split entries when one delivery covers multiple jobs.
• Post matched tickets to the ERP job cost module as committed costs so reports reflect current exposure before the formal invoice arrives.
• Track unmatched tickets weekly and enforce same-day submission rules to reduce coding errors and catch overruns in real time.

Why Delivery Ticket Matching Breaks Down in Construction

Delivery tickets move through multiple hands before they reach accounting — the site foreman signs for materials, the driver leaves a paper copy, and that ticket may sit in a truck cab or job trailer for days before anyone codes it. By the time accounting sees it, the job number is missing, the cost code is a guess, or the ticket covers a split delivery that belongs to two different phases. The breakdown points are predictable: no job number on the ticket at point of receipt, multiple jobs on one delivery without split quantities, purchase order mismatches where the quantity delivered differs from the original order, and late submission when tickets batch up weekly or bi-weekly, making it impossible to catch job cost overruns in real time.

The Recommended Workflow for Delivery Ticket Capture and Job Costing

The foreman or site supervisor who signs the delivery ticket must write the job number and cost code directly on the ticket before the driver leaves, with no exceptions. The site contact then captures a legible image of the signed ticket the same day and submits it to the accounting queue. The accounts payable or job cost technician pulls the corresponding purchase order and checks quantity, unit, and material description, flagging any variance greater than your tolerance threshold — typically 5–10% — for foreman confirmation. When one ticket covers multiple jobs or cost codes, create separate line entries in the ERP with quantities and amounts allocated appropriately and document the split in the ticket notes. Once matched and approved, post the ticket as a committed or actual cost against the job so the job cost report reflects current exposure, then reconcile at invoice receipt by three-way matching against the purchase order and delivery ticket.

A Practical Example

A concrete supplier delivers six yards to Site A and four yards to Site B on a single truck run. The delivery ticket shows a total of ten yards with one line item. The site foreman at Site A signs for the full delivery but writes only Site A's job number on the ticket. When accounting receives the photographed ticket that afternoon, the technician sees the mismatch between the signed quantity and the known order for six yards. She calls the foreman, who confirms the split delivery. The technician creates two cost entries: six yards against Site A job number 2401 and four yards against Site B job number 2405, allocating the total ticket amount proportionally. Both entries post to the ERP as committed costs, and the project manager sees the updated exposure in the next morning's job cost report — three days before the supplier invoice arrives. Vergo automates this split-allocation workflow by proposing the job number and cost code by inference from your own accounting structure and history, so the technician confirms in seconds instead of making manual calls and creating separate entries by hand.

Tips for Construction Accounting Teams

Pre-print job number labels for active sites and give foremen a sheet of adhesive labels with the job number and default cost code — they peel and stick before signing, which reduces missing data by over 60% in most field tests. Set a same-day submission rule for all delivery tickets so every ticket signed in the field reaches the accounting queue before end of shift; late tickets should require a supervisor explanation. Build a cost code cheat sheet for common materials, with concrete going to a specific CSI division and lumber to another, and post a one-page reference in the job trailer to remove guesswork for foremen who aren't fluent in cost codes. Track unmatched tickets as a weekly KPI reported to the project manager, because visibility alone drives field compliance.

How Vergo Handles This

Vergo captures delivery tickets by text message at the job site — employees photograph tickets from their phone with no app to download or portal login, and Vergo chases missing receipts itself instead of waiting for a report. Transactions are ready to code the moment they happen, with no waiting for clearing, and Vergo proposes the job number and cost code by inference from your own accounting structure and history — no rule library to build, no keyword lists to maintain, and new vendors are coded on first sight. Every coding shows why it was chosen, so a reviewer confirms 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. Once transactions clear, they sync into your accounting or ERP software. See the Vergo expense management product page for workflow configuration details.

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?
• How do I avoid vendor lock-in when choosing expense software for my construction ERP?