Key takeaways
- Eclipse is Epicor's ERP for electrical, plumbing, HVAC and PVF wholesale distributors.
- Its general ledger runs at multi-branch, multi-territory and multi-company level.
- Epicor does not describe a native employee expense module; it offers an Accounts Payable API for external AP or expense platforms.
- Vergo proposes branch and GL coding, texts for receipts and posts entries through the Eclipse API.
Where should you go next?
- Vergo's Epicor Eclipse integration
- What expense management software integrates with Epicor Eclipse?
- Get started with Vergo
How do you automate expense management in Epicor Eclipse, step by step?
- Enable API access for your Eclipse instance, once.
- Keep branch cards. Connecting your existing cards involves no card applications, no re-issuing and no banking change.
- Collect receipts by text. Drivers and counter staff reply with a photo. Employees handle everything by text message — no app to download, no portal login — and Vergo chases missing receipts itself instead of waiting for a report.
- Code to branch and GL account. Vergo proposes both for each line, with the reason.
- Hand off to Eclipse. Once API access is enabled for your Eclipse instance, Vergo reads your branches, departments and GL accounts and posts coded card spend through the Eclipse API.
What does Eclipse need on each card transaction?
- Branch: for branch profitability.
- Department where you use them.
- GL account: fuel, vehicle repairs, supplies, meals.
- Receipt for audit.
Where does Eclipse stop and automation start?
Eclipse is built around the distribution business: inventory, counter sales, purchasing and branch accounting. Company card spend by drivers and branch managers sits outside that flow, and without a native expense module it tends to arrive as a statement for someone to key. Vergo reads the receipt itself, line by line, and predicts the coding from what was actually bought, not just the vendor name on the header. The branch comes from who spent and how their spend was coded before.
A practical example
An electrical distributor with eight branches on Eclipse gives cards to branch managers and delivery drivers. A driver buys diesel and a replacement strap for a flatbed. Vergo texts for the receipt, proposes fuel and vehicle maintenance with the driver's branch, and the AP lead confirms before the entry is posted to Eclipse.
How Vergo handles this
Vergo proposes the coding by inference from your own accounting structure and history — no rule library to build, no keyword lists to maintain, and new vendors are coded on first sight. For a distributor, that history is branch by branch. Card spend, employee reimbursements and AP invoices run through one coding model — same coding, same review, one reconciliation — and payment stays on the rails you already use.
Frequently Asked Questions
How does Vergo get spend into Eclipse?
Vergo posts coded spend through the Eclipse API, once API access is enabled for your instance.
Can Vergo code to branches?
Yes. Vergo reads your branch and department structure and proposes both.
Who enables the connection?
Your team enables Eclipse API access once and provides the endpoint and credentials.
Do we need new cards?
No. Connecting your existing cards involves no card applications, no re-issuing and no banking change.
