What does expense management with WennSoft Signature look like?
Signature is a service and project management system for specialty contractors, sitting on Dynamics GP and holding the job cost detail the business runs on. That detail is only as good as the spend feeding it — and card spend is the category that reliably arrives last. A technician buys a part at a supply house on Tuesday; the office sees it on a statement in three weeks with no job number attached. Vergo removes that lag by making the coding part of the purchase: the technician selects the job and cost code on their phone, photographs the receipt, and the expense posts into Signature already coded.
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.
How does spend get to the right job and cost code?
Vergo presents the technician with their own jobs, not a full company list, so choosing takes seconds in a truck. Cost codes follow the structure the contractor already maintains in Signature rather than a separate scheme invented for the card programme. If a purchase covers two jobs, it is split at capture rather than reallocated by the office later.
What controls apply before the purchase happens?
Cards carry limits by amount and by merchant category, which is the practical way to keep a fuel card a fuel card. Cards can be issued per technician, per truck or per job, and shut off the moment the job closes. Approval routing sends anything above a threshold to a project manager or controller before it settles, so an unexpected purchase is a conversation on the day rather than a surprise at close.
What does the office stop chasing?
Receipts, mostly. Vergo holds the transaction incomplete until a receipt is attached, and the person who spent gets the reminder rather than the bookkeeper. The second thing it stops is retroactive job coding — the exercise where someone tries to work out, from a merchant name and a date, which job a $340 charge belonged to.
Why does the timing matter to job costing?
A job cost report is a management tool only if it is current. Card spend that lands three weeks late means every in-progress job is understated and margin problems surface after they are fixable. Coding at the point of purchase puts that spend on the job report in days, which is when a project manager can still do something about it.
What does rollout involve?
Confirm the job and cost code mapping, set card rules, and get cards to the people who buy. One enablement from IT covers the on-premise connection. Most contractors start with the crews spending the most and expand once a full month of coded spend has landed correctly in Signature.
Does Vergo integrate with WennSoft Signature?
Yes. Vergo connects to WennSoft Signature and posts coded card expenses into the system. Because Signature is on-premise, the contractor's IT team enables access once.
Can spend be coded to jobs and cost codes?
Yes. Technicians select the job and cost code at the point of purchase from their own assigned jobs, and split a purchase across jobs when needed.
How are receipts collected from the field?
Technicians photograph the receipt in the Vergo app at the time of purchase, and the transaction stays incomplete until one is attached.
Does WennSoft Signature include card issuing?
Signature covers service and project management on Dynamics GP. Issuing controlled cards, enforcing limits at the point of sale and capturing receipts in the field is what Vergo adds alongside it.
