Key takeaways
- Invoice and purchasing approvals: Partly. Configurable document approval routing is described for Epicor ECM (separate product) rather than Eclipse itself; Eclipse's own PO or invoice approval features are not documented publicly.
- Expense claim approvals: not publicly documented; confirm with Epicor.
- Vergo approvals are optional and run before coded spend posts into Epicor Eclipse.
Where should you go next?
- Epicor Eclipse AP and expense features: what's included and what to add
- Vergo's Epicor Eclipse integration
- Get started with Vergo
What Epicor Eclipse includes
Invoice and purchasing approvals
Partly. Configurable document approval routing is described for Epicor ECM (separate product) rather than Eclipse itself; Eclipse's own PO or invoice approval features are not documented publicly.
Expense claim approvals
Expense claim approvals are not publicly documented for Epicor Eclipse. Confirm with Epicor before you budget.
What teams add alongside it
- AP invoice capture and approval
- Expense management with card feeds
Where Vergo fits with Epicor Eclipse
Vergo adds approvals on the spend before it reaches Epicor Eclipse. Approval workflows are optional and fit how you already control spend: route by GL account or by amount — or skip approval flows entirely and let policy flags catch only what breaks a rule. Approved card spend posts into Epicor Eclipse, coded to your branch and GL account.
Frequently Asked Questions
Does it depend on the Epicor Eclipse edition or add-ons?
Configurable document approval routing is described for Epicor ECM (separate product) rather than Eclipse itself; Eclipse's own PO or invoice approval features are not documented publicly.
How does Vergo route approvals?
By GL account or by amount, or skip approval flows entirely and let policy flags catch only what breaks a rule.
What happens after approval in Vergo?
The coded card spend posts into Epicor Eclipse, with its receipt.



