Why can't card transactions flow into Eagle automatically?
Epicor Eagle publishes no public API, so card platforms have no documented way to push transactions into it. For the hardware stores, lumberyards, and independent retailers running Eagle on-premise, card spend arrives as a statement that someone has to turn into coded entries by hand.
What does the manual routine cost?
Each month: download the statement, collect receipts from managers and staff across locations, decide the GL account for each purchase, and key the batch into Eagle. The coding decisions are usually easy individually — it is the volume and the chasing that eat the close. Multi-store operations feel it worst, because receipts and context live in different buildings.
How does Vergo automate the Eagle import?
Vergo captures everything upstream. Employees buy on Vergo cards; at the point of sale they attach the receipt and code the purchase against your Eagle GL structure loaded into Vergo. Finance reviews the coded transactions, then exports a custom-built CSV matched to the import format Eagle expects. One file load puts the batch into Eagle, coded and documented.
What is the step-by-step?
1. Issue Vergo cards to store managers and staff who purchase.
2. At purchase, the cardholder snaps the receipt and picks the GL coding from your Eagle chart.
3. Finance reviews and approves transactions in Vergo — across all stores from one screen.
4. Export approved transactions as a CSV built for Eagle's import format.
5. Import the file into Eagle and reconcile against the card statement.
How often should you import?
Your call — the file generates in minutes from already-approved transactions, so weekly imports for a current GL or a single month-end import both work. Either way, the keying session and the receipt chase are gone; what remains is a review and a file load.
What changes for a multi-store close?
The statement stops being a scavenger hunt across locations. Receipts are captured on phones at the register in every store, coding is picked from your Eagle chart at the moment of purchase, and finance sees every store's card activity in one review queue instead of collecting envelopes from branch managers. The general ledger receives card spend on a regular cadence, coded consistently across all stores, and the month-end card reconciliation becomes a straightforward comparison of two clean lists — the card statement on one side and the imported batch on the other — rather than a reconstruction of what forty different cardholders bought, where they bought it, and which account it should have hit.
Is there a direct card feed for Epicor Eagle?
No. Eagle publishes no public API, so card transactions enter Eagle by manual entry or file import — there is no live feed to connect.
What format does the Vergo export use?
A custom-built CSV matched to the import format Eagle expects, generated from transactions already coded and approved in Vergo.
How do receipts get handled across multiple stores?
Cardholders attach receipts on their phones at the point of purchase, so finance never has to chase paper across locations — every imported transaction has its receipt in Vergo.
Does on-premise Eagle change anything?
No. The integration is file-based, so you import the CSV into your Eagle system the same way regardless of where it runs.
