What are the options for card transactions in GlobalEdge?
Davisware GlobalEdge does not publish a public API — nor does ECI Software Solutions, which acquired Davisware in 2025 — so no card program can feed it directly. That leaves manual entry, cleaning up a raw card-provider export, or importing a file that is already structured and coded. For a field-service operation with techs spending across trucks and jobs, the prepared-file path is the one that scales.
Why is the raw card export a poor starting point?
The bank's file knows the merchant, the amount, and the date — nothing about which work order or job the purchase supported, and it carries no receipt. The office ends up reconstructing that context weeks later from techs who are back in the field. That lag is exactly what keeps month-end slow and job-level cost visibility stale.
How does the Vergo-to-GlobalEdge workflow run?
Vergo issues the cards, so every transaction is visible the moment it happens. The tech snaps the receipt and codes the purchase from their phone — parts run, fuel, supplies — before the context fades. When you are ready to book activity, Vergo generates a custom-built CSV export matched to GlobalEdge's import format, shaped for your setup. Your bookkeeper imports one file into the hosted platform and the card spend arrives coded and receipted.
What are the steps each cycle?
1. Techs and office staff spend on Vergo cards and capture receipts at purchase. 2. Transactions are coded in Vergo against your GlobalEdge structure. 3. Admins review and approve in one place. 4. Vergo produces the GlobalEdge-matched CSV on your close cadence. 5. Import the file and reconcile — the imported activity already mirrors the card program.
How much time does this save at month end?
The import itself takes minutes; the real saving is upstream. Receipt-chasing, coding reconstruction, and statement re-keying disappear because they happened at the point of purchase, so closing card activity stops being the long pole in the month.
Can card transactions sync into GlobalEdge automatically?
Not over an API — GlobalEdge does not publish one, and ECI documents none. The automation path is Vergo's custom CSV export matched to GlobalEdge's import format.
What file does Vergo produce for GlobalEdge?
A custom-built CSV matched to GlobalEdge's import format and shaped for your setup, so the import runs without column re-mapping.
Who codes the spend, and when?
Cardholders — techs and office staff — code purchases in Vergo at the time of spend, so the file that reaches GlobalEdge already carries its coding.
How often should we run the import?
On your close cadence. Vergo generates the export on demand, so weekly or monthly imports are both straightforward.
