Why do field reimbursements distort job cost?
Because they arrive late and unattributed. A technician buys a fitting to finish a call, keeps the receipt in the truck, and hands over a crumpled stack at the end of the month. By then the job may be closed and the cost lands in overhead. Signature reports what it is given; if field spend reaches it without a job number, the job margin on the report is wrong. Vergo fixes the capture end: receipt photographed on site, job and cost code selected there and then.
How does a claim get from the truck to Signature?
The technician photographs the receipt in the app. Vergo reads the merchant, date and amount, the technician picks the job and cost code from their assigned work, and the claim goes straight to their supervisor. Once approved, Vergo reimburses the technician directly to their bank account, and the coded expense posts into WennSoft Signature against the job.
How does Vergo connect to WennSoft Signature?
WennSoft Signature runs on-premise on top of Microsoft Dynamics GP, and the integration layer sits in the customer's own environment. Their IT team enables access once — Signature's documented integration tooling is described at docs.wennsoft.com — and Vergo handles the mapping and the ongoing connection from there. Because the system is customer-provisioned, there is no vendor partner queue to wait in.
Why not run reimbursements through payroll?
Two reasons. Timing — payroll runs on its own cycle, so a technician who spent their own money on the second of the month may not see it back until the end of the following one. And coding — money routed through payroll tends to land in a payroll account rather than on the job, which is precisely the visibility the contractor was trying to get. Paying reimbursements separately keeps the cost on the job and the technician paid quickly.
What about mileage and per diems?
Mileage is captured on the claim with the configured rate applied automatically, so nobody is doing arithmetic on a form. Per diems follow the same rules-based approach: an amount defined in advance, approved by the same supervisor, coded to the job that generated the travel.
How do you reduce out-of-pocket spend altogether?
Give people a card with a boundary on it. Most field reimbursements exist because the technician had no other option at the counter. A Vergo card limited by amount and merchant category — issued per technician, per truck or per job — turns that purchase into a coded card transaction and removes the claim, the delay and the argument about whether it was in policy.
What does the office set up?
Job and cost code mapping, approval thresholds, mileage rate and category limits. IT enables access to the on-premise Signature environment once. From there supervisors approve, technicians get paid, and the office reviews exceptions rather than transcribing receipts.
How fast do technicians get their money back?
Vergo pays approved claims directly to the technician's bank account rather than waiting for a payroll run, so repayment happens within days of supervisor approval.
Is reimbursed spend coded to the job?
Yes. The technician selects the job and cost code when submitting the claim, and Vergo posts the approved expense into WennSoft Signature against that job.
Can supervisors approve from the field?
Yes. Claims route to the supervisor's phone or email with the receipt attached, so approval does not wait for anyone to be at a desk.
How do we cut the number of reimbursement claims?
Issue controlled cards for the purchases technicians currently make out of pocket. Limits by amount and merchant category keep the spend in policy and remove the claim entirely.
