How does Vergo connect to Epicor Eclipse?
Epicor Eclipse exposes a documented API, and Vergo connects to it in your environment. Access is customer-provisioned: your IT team enables API access once, then Vergo does the rest of the setup. Epicor Eclipse runs cloud or on-premise, and the connection works either way — the API sits where your ERP sits.
Vergo's documentation of the interface starts from Infor's and Epicor's own published material; the reference for this system is the vendor's API documentation.
What does expense management with Epicor Eclipse actually change?
Most finance teams running Epicor Eclipse handle card spend the same way: statements arrive weeks after the purchase, someone chases the buyer for a receipt, and every line gets coded in a spreadsheet before it is keyed into the ERP. The coding is guesswork by then, because the person who spent the money has moved on.
Vergo moves the coding to the moment of spend. The cardholder picks the branch, warehouse, and general ledger account on their phone and photographs the receipt before they leave the counter. By the time the statement closes, the spend is already coded, approved, and ready to post into Epicor Eclipse.
What controls does finance keep?
Card limits, merchant restrictions, and per-cardholder budgets are set in Vergo before a card is used, so the control happens ahead of the spend rather than in a month-end review. Approval rules route anything above a threshold to the right approver, and nothing posts into Epicor Eclipse until it has cleared them.
Receipt policy is enforced the same way: a charge without a receipt stays open and visible, and the cardholder gets the reminder instead of the controller writing the email.
How do distribution teams use it?
Teams are distributors running counter sales, warehouses, and multiple branches. They use Vergo to see committed spend against branches and product lines before the ledger does, and to keep the ERP as the single system of record — Vergo does the capture and the coding, Epicor Eclipse keeps the books.
The practical test is the monthly variance conversation. When card spend is coded at purchase, the manager reviewing a product line overrun is looking at charges that were categorised by the person who made them, days earlier, with a receipt attached. When it is coded at month end by someone reconstructing a statement, the same review is an argument about what a merchant name meant.
Vergo also carries reimbursements and bills on the same coding rules, so a company that starts with cards is not adopting a second workflow later.
How long does setup take?
The gating step is your IT team enabling API access on the Eclipse side. Once that is done, Vergo maps your branches and product lines and issues cards; most teams are coding live spend within the first billing cycle rather than waiting on a multi-month ERP project.
Does Vergo integrate with Epicor Eclipse?
Yes. Epicor Eclipse publishes a documented API and Vergo connects to it in your own environment. Approved card spend posts into Epicor Eclipse; your IT team enables API access once at setup.
How is card spend coded?
Cardholders code each charge to branch, warehouse, and general ledger account at the point of purchase, on their phone, with the receipt attached. The coding lists come from Epicor Eclipse, so the values match what your ledger expects.
Do we still need our Eclipse chart of accounts?
Yes — Epicor Eclipse stays the system of record. Vergo mirrors your chart of accounts and branches and product lines for coding, then posts approved spend back; it does not maintain a competing ledger.
Does Epicor Eclipse run in the cloud or on-premise?
Cloud or on-premise. The API access model is customer-provisioned either way: the interface sits in your environment and your team turns it on once.
