How do card transactions get into e-Emphasys ERP?
By file import. e-Emphasys (VitalEdge) publishes no public API documentation, and the system is deployed on-premise inside the dealership's own environment — so there is no standard live feed for card activity. The working route is a structured import file, prepared in the format the system expects and loaded by accounting.
What is the manual process without tooling?
- Pull card statements for every cardholder — parts runners, service trucks, branch managers.
- Chase receipts across branches and techs.
- Code each line to vendor, GL account, and the right branch or department.
- Reshape a bank CSV into an importable file, or key entries into e-Emphasys one at a time.
For an equipment dealership group with fuel, parts, shop supplies, and travel spread over many cards and locations, that reconstruction eats days of the close — and the people who made the purchases have long since moved on to the next job.
How does Vergo automate the import?
Vergo captures the data at the point of spend and generates the import file for you:
- Capture: transactions on Vergo cards appear in real time; the spender attaches the receipt and codes the purchase from their phone.
- Coding: each line carries the vendor, GL account, and branch or department references your e-Emphasys import needs, applied before export rather than reconstructed after.
- Export: Vergo generates a custom-built CSV matched to the import format e-Emphasys expects. Accounting reviews the batch and runs the import.
Stated plainly: this is a file integration, not an API sync — none is publicly documented for e-Emphasys. What the automation changes is who prepares the file. The software does the formatting and carries the coding; your team reviews and loads.
What cadence works best?
Match your close. Weekly imports keep each batch small and reviewable; monthly fits a traditional close. Because cardholders code continuously, the export is current whenever accounting wants it — there is no month-end coding scramble to wait on.
Where do receipts end up?
Attached to each transaction in Vergo. Every entry imported into e-Emphasys traces back to a documented card transaction with spender, receipt, and coding — the trail your controller wants when an OEM audit or an internal review samples spend.
What changes for the accounting office?
The import itself stays the familiar e-Emphasys step, run on your schedule. What disappears is the upstream grind — statement downloads, receipt chasing across branches, coding from memory, spreadsheet reshaping. The office's role shifts from data entry to review, and the close stops waiting on card-spend reconstruction.
Can Vergo feed transactions into e-Emphasys live?
No. e-Emphasys publishes no public API and runs on-premise, so there is no live feed. Vergo generates a custom CSV matched to its import format, and accounting runs the import.
What does the export file carry?
Each card transaction with date, amount, vendor, GL account, and branch or department coding, arranged in the format e-Emphasys expects on import.
Who codes the spend?
Cardholders code purchases in Vergo as they happen — from the parts counter or the service truck — and finance reviews before export.
Does this handle multi-branch dealership groups?
Yes. Branch and department references ride on every transaction, so one export carries correctly attributed spend from all locations.
