View

Epicor Eclipse integration with Vergo: what syncs and how

Vergo connects to the Epicor Eclipse API and posts coded distribution spend into your ledger against branches and GL accounts.

What does the Vergo + Epicor Eclipse integration do?

  • Sync card transactions, employee reimbursements and vendor invoices into Epicor Eclipse through one coding model
  • Read branches, departments, GL accounts and vendor records out of Eclipse so spend is coded to your own structure
  • Code every transaction by AI inference from your accounting structure and history — no rule library to build
  • Read receipts line by line, predicting the coding from what was actually bought rather than the vendor name on the header
  • Show why each coding was chosen, so review is confirmation rather than re-coding
  • Post coded transactions and vendor invoices into Eclipse; Eclipse stays the system of record
  • Work with the corporate, fuel and personal cards your business already holds — Vergo does not issue cards

Expense management coded to your Eclipse branches

Card spend is coded to branch, department, and GL account at the point of purchase, with the receipt captured, then posts into Eclipse as a coded transaction.

AP automation that posts vendor invoices into Eclipse

Vendor invoices are captured, coded, and approved in Vergo, then post into Eclipse against the correct vendor account. Payment runs on your existing rails.

Driver and counter-staff reimbursements

Out-of-pocket purchases made by drivers and counter staff are coded to the same branches and accounts as card spend, so reimbursements post consistently rather than as adjustments.

App information

Developer
Vergo
Integration method
API
API type
REST
Deployment
Cloud or on-premise
What syncs
Branches, departments, GL accounts, and vendor records; coded transactions and vendor invoices posted through the Eclipse API
How the connection is made
Customer-provisioned: Eclipse API access is enabled for your instance — your team does that once, then Vergo does the rest.

Security and compliance

Encryption

All data is encrypted in transit and at rest using AES-256 encryption.

Infrastructure

Vergo operates on SOC 2-compliant infrastructure with geographically redundant, continuous backups.

Access controls

Role-based access controls keep employees, approvers and finance in their own lanes.

Audits

Regular third-party security audits are conducted to maintain data protection standards.

Frequently asked questions

Does Vergo integrate with Epicor Eclipse?

Yes. Vergo connects to the Epicor Eclipse API once access is enabled for your instance, and posts coded spend into Eclipse against your branches and GL accounts.

Can Vergo attribute card spend to Eclipse branches?

Yes. Vergo reads your branch and department structure from Eclipse and codes every transaction to a branch before it posts, so branch-level reporting stays accurate.

What data syncs between Vergo and Eclipse?

Vergo reads branches, departments, GL accounts, and vendor records, and posts coded transactions and vendor invoices back through the API.

How is the Epicor Eclipse connection set up?

Your team enables API access for your instance and provides the endpoint and credentials. Cloud and on-premise deployments follow the same process.

Does Epicor Eclipse have built-in expense management?

Eclipse covers distribution operations and financials; employee expense capture is not part of it and is usually handled manually. Vergo covers that work and posts the completed entry.

Discover more integrations

Vergo integrates with every ERP and accounting software, plus the payroll platforms reimbursements flow through. Browse by industry.
Support

White-glove onboarding and customer support.