Why can't card spend feed into SAMPro automatically?
SAMPro Enterprise has no public API — Data-Basics publishes no developer documentation, and integrations are built bespoke through the vendor. So whatever card program a service contractor runs, transactions reach SAMPro one of two ways: entered by hand or imported as a file. The goal is to make the file route as close to automatic as the system allows.
Where the time actually goes today
In a field service operation, card spend is techs at supply houses, fuel stops, and parts counters. At month end the office reconstructs it: which job was that purchase for, which work order, where is the receipt. Coding after the fact, from statement descriptors, by someone who was not at the counter — that reconstruction is the cost, more than the keying itself.
The import workflow with Vergo
1. Techs code at the counter. Each Vergo card transaction is tagged to its job and work order by the tech who made the purchase, with the receipt photographed on the spot. No end-of-month archaeology.
2. The office approves as it happens. Finance sees and approves transactions in Vergo continuously. Allocation questions get answered same-day, while the tech remembers the purchase.
3. Vergo generates the SAMPro-matched file. Vergo provides custom-built CSV exports matched to the import format SAMPro expects — job and work order references and account fields laid out to load cleanly.
4. Import into SAMPro. Your team loads the batch on whatever cadence fits the close — weekly or monthly. Every line arrives coded, approved, and receipt-backed.
What the file needs to carry
For SAMPro job costing to be right, each line needs the date, amount, and merchant plus the job and work order allocation and a receipt reference. Because those allocations were made in the field at purchase time, the costing that lands in SAMPro reflects reality rather than a best guess.
File import versus the alternatives
Manual entry scales badly with card count. A bespoke vendor-built integration through Data-Basics is possible but is a paid, per-customer project with ongoing maintenance. A raw bank export leaves every line uncoded. The matched-file approach needs no custom development on SAMPro's side and moves all the coding work to the moment of spend, where it is cheapest.
The honest framing
This is not an API sync and we do not call it one. Transactions appear in SAMPro when you run the import, not in real time. For a system with no public API, a clean scheduled import of pre-coded transactions is the practical ceiling — and it eliminates the receipt-chasing and after-the-fact job coding that were consuming the close.
Does Vergo have an API connection to SAMPro?
No — SAMPro Enterprise publishes no public API for anyone to connect to. Vergo provides custom-built CSV exports matched to SAMPro's import format instead.
Can techs really code transactions from the field?
Yes. Each card transaction is tagged to its job and work order in Vergo on the tech's phone, with the receipt photographed in the same step.
How do receipts get into the record?
Receipts are captured in Vergo and stay attached to their transactions; the import file carries a reference back to each one, so the audit trail is complete.
How often should we run the import?
Whatever cadence suits your close — many teams import weekly so month end is already done. The file is generated on demand from approved transactions.
