How do card transactions get into E2 Shop System?
Through file import. E2 Shop System has no public API — ECI Solutions documents no read or write access for third-party tools — so there is no live connection a card program can feed. The route that works is the one E2 supports: a structured file, in the shape the system's import expects, loaded by the office.
What does this look like done by hand?
- Download the card statement at month end.
- Round up receipts from the shop floor — tooling orders, hardware-store runs, freight, maintenance parts.
- Code each line to the right vendor and GL account.
- Key the entries into E2, or wrestle the bank's CSV into an importable shape.
In a busy job shop that is hours of office time, done weeks after the purchases, with the usual mystery lines nobody remembers. Every re-keyed entry is a chance for a typo that surfaces later as a reconciliation problem.
How does Vergo automate the import?
Vergo moves the work to the point of purchase and generates the file for you:
- Capture: transactions on Vergo cards show up in real time; the buyer snaps the receipt and codes the purchase from their phone before they're back at the machine.
- Coding: each line carries the vendor and GL account references your E2 import needs — applied when the purchase is fresh, not reconstructed at month end.
- Export: Vergo generates a custom-built CSV matched to the import format E2 expects. The office reviews the batch and runs the import.
To be clear about the mechanism: this is a file integration. Vergo does not sync with E2 over an API, because E2 has no public API. What changes is that the import file arrives finished — formatted, coded, and receipt-backed.
How often should you import?
Weekly batches keep review light; monthly matches a traditional close. Since coding happens continuously, the export is ready whenever the office wants to run it — no waiting on a month-end receipt hunt.
What about the audit trail?
Receipts stay attached to each transaction in Vergo, so every imported entry in E2 traces back to a documented purchase with the buyer, receipt, and coding on record. When a customer audit or your accountant samples spend, the answer is a lookup, not an archaeology project.
What changes for the front office?
The import step stays the same E2 routine, run on your schedule. What goes away is everything before it — the statement download, the shop-floor receipt hunt, the guesswork coding, the spreadsheet wrestling. The office reviews a prepared batch instead of building one, and month end stops hinging on reconstructing card spend.
Can card transactions reach E2 automatically?
No — E2 Shop System has no public API, so nothing feeds it live. Vergo generates a custom CSV matched to E2's import format, and your office runs the import.
What is in the export file?
Each card transaction with date, amount, vendor, and the GL account coding applied in Vergo, arranged in the format E2 expects on import.
Who codes the purchases?
The person who made the purchase, in Vergo, at the time of purchase. The office reviews before export instead of reconstructing from a statement.
Does this eliminate keying entries into E2?
Yes — the import file replaces manual entry. The remaining work is reviewing the batch and running E2's import.
