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

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. Field staff sign for delivery without writing down the job number, leaving accounting to reconstruct the assignment later.
• Multiple jobs on one delivery. A single truck drops materials for two active sites; the ticket doesn't split quantities by job.
• PO mismatch. The quantity delivered doesn't match the original purchase order, and no one flags the variance before the invoice arrives.
• Late submission. 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

1. Require job number and cost code at point of receipt. The foreman or site supervisor who signs the delivery ticket must write the job number and Phase/Cost Code directly on the ticket before the driver leaves. No exceptions.
2. Photograph or scan the ticket immediately. The site contact captures a legible image of the signed ticket — front and back if the driver's copy has pricing — and submits it to the accounting queue the same day.
3. Match the ticket to the open purchase order. The accounts payable or job cost technician pulls the corresponding PO and checks quantity, unit, and material description. Flag any variance greater than your tolerance threshold (typically 5–10%) for foreman confirmation.
4. Assign or confirm cost codes. If the job number was written on the ticket, verify the cost code matches the PO line item. If it's missing, route the ticket back to the field supervisor for a 24-hour response window before escalating to the project manager.
5. Split tickets with multiple job allocations. When one ticket covers multiple jobs or cost codes, create separate line entries in the ERP — one per job — with quantities and amounts allocated appropriately. Document the split in the ticket notes.
6. Post to the ERP job cost module. Once matched and approved, post the ticket as a committed or actual cost against the job. Update committed costs if a formal invoice hasn't yet arrived so the job cost report reflects current exposure.
7. Reconcile at invoice receipt. When the supplier invoice arrives, three-way match it against the PO and the delivery ticket. Any variance triggers a review before payment is approved.

Tips for Construction Accounting Teams

• Pre-print job number labels for active sites. Give foremen a sheet of adhesive labels with the job number and default cost code. They peel and stick before signing — reduces missing data by over 60% in most field tests.
• Set a same-day submission rule for all delivery tickets. Every ticket signed in the field must be in the accounting queue before end of shift. Late tickets should require a supervisor explanation.
• Build a cost code cheat sheet for common materials. Concrete goes to a specific CSI division, lumber to another. A one-page reference posted in the job trailer removes guesswork for foremen who aren't fluent in cost codes.
• Track unmatched tickets as a KPI. Report the number of open, unmatched delivery tickets weekly to the project manager. Visibility alone drives field compliance.
• Use platforms like Vergo to automate intake and matching. Vergo's expense management module lets field crews photograph tickets from a mobile device, auto-populates job number and cost code from the active PO, and routes exceptions to the right approver — eliminating manual re-keying and reducing match cycle time from days to hours. See the Vergo expense management product page for workflow configuration details.

Frequently Asked Questions

See FAQ section below.

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