How does Vergo connect to Epicor Eclipse?
Epicor Eclipse publishes a documented API and Vergo posts approved bills into it. The access model is customer-provisioned — your IT team enables the interface once in your own environment, then Vergo handles the mapping. The system runs cloud or on-premise, and either deployment works. The vendor reference is Epicor Eclipse documentation.
What does AP automation with Epicor Eclipse replace?
The manual version is familiar: invoices arrive by email, someone saves them to a folder, a coder assigns branch, warehouse, and general ledger account, a manager approves by reply-all, and a clerk retypes the whole thing into Epicor Eclipse. Every hand-off is a place for an invoice to sit for a week.
Vergo captures the invoice, reads the header and line detail, applies the coding rules you set, and routes it for approval. Approved bills post into Epicor Eclipse over its API — the ERP still owns the ledger, the payment run, and the vendor master.
How does approval routing work?
Rules are set on the dimensions Epicor Eclipse already uses: amount thresholds, branches and product lines, and vendor. An invoice charged to one cost centre routes to the manager who owns it; anything above a limit escalates. Approvers act from email or the phone, and every approval is stamped on the bill so the audit trail travels with the document rather than living in an inbox.
Exceptions behave the same way. A bill that fails a match, arrives without a PO reference, or codes to an account nobody owns stops in Vergo with the reason attached. It does not reach Epicor Eclipse until a person resolves it, which is the point — the ERP should not be the place you discover a bad invoice.
What do distribution teams get out of it?
Teams are distributors running counter sales, warehouses, and multiple branches. The gain is timing: coded, approved payables appear against branches and product lines while the period is still open, so the accrual is a report rather than an estimate. Vergo also carries card spend and reimbursements on the same coding rules, which means one approval path instead of three.
How long does it take to get running?
Enabling API access on the Eclipse side is the one task that belongs to your team. After that, Vergo maps the chart of accounts and your branches and product lines, loads the approval rules, and runs a parallel cycle before you cut over.
This is not an ERP project. Nothing is reconfigured inside Epicor Eclipse; Vergo reads the structure that is already there and posts against it, so the work is rule-setting and vendor onboarding rather than development.
Does Epicor Eclipse already do this?
Epicor Eclipse handles the payables ledger, the payment run, and the vendor master, and it does those well enough that replacing them is not the goal. What sits outside the ERP is the front half: receiving a document, reading it, deciding who approves it, and chasing the person who has not. Vergo covers that half and hands the finished bill to Epicor Eclipse.
Does Vergo post bills into Epicor Eclipse?
Yes. Approved bills post into Epicor Eclipse over its documented API. Your IT team provisions access once, then Vergo maps your chart of accounts and branches and product lines.
What happens to invoices that fail a match?
They stop in Vergo as exceptions with the reason attached, and nothing posts into Epicor Eclipse until a person resolves them. The ERP never receives a bill that has not cleared approval.
Can approval rules follow our branches and product lines?
Yes. Rules are built on amount thresholds, vendor, and the branches and product lines already defined in Epicor Eclipse, so routing matches your existing authority matrix rather than a new one.
How long does implementation take?
The dependency is your IT team enabling API access on the Eclipse side. After that, mapping and rule setup typically run in parallel with one normal AP cycle before cutover.
