Key takeaways
- Invoice and purchasing approvals: Yes. AP invoices can go through web approval, and variance purchase orders use approval hierarchies.
- Expense claim approvals: not publicly documented; confirm with ECI Software Solutions.
- Vergo approvals are optional and run before coded spend posts into MarkSystems.
Where should you go next?
- MarkSystems AP and expense features: what's included and what to add
- Vergo's MarkSystems integration
- Get started with Vergo
What MarkSystems includes
Invoice and purchasing approvals
Yes. AP invoices can go through web approval, and variance purchase orders use approval hierarchies.
Expense claim approvals
Expense claim approvals are not publicly documented for MarkSystems. Confirm with ECI Software Solutions before you budget.
What teams add alongside it
- AP invoice capture / OCR
- Employee expense app with receipt capture
Where Vergo fits with MarkSystems
MarkSystems's own workflow can keep governing the documents listed above. Vergo's approvals sit on the spend before it reaches MarkSystems. Approval workflows are optional and fit how you already control spend: route by GL account, by amount, or by project — or skip approval flows entirely and let policy flags catch only what breaks a rule. Approved card spend posts into MarkSystems, coded to your house, cost code and GL account.
Frequently Asked Questions
Can Vergo route approvals by project?
Yes. Route by GL account, by amount or by project, or skip approval flows and let policy flags catch only what breaks a rule.
What happens after approval in Vergo?
The coded card spend posts into MarkSystems, with its receipt.
