Key takeaways
- Invoice and purchasing approvals: Partly. Approval is documented for AP bills (pre-approval and approval for payment, with email notices). However, the changelog documents no configurable approval routing for POs or expenses.
- Expense claim approvals: Partly. Employee out-of-pocket expenses are imported by CSV into AP bills, which then go through the AP bill approval process. However, NolaPro has no dedicated expense-report module.
- Vergo approvals are optional and run before coded spend posts into NolaPro.
Where should you go next?
- NolaPro AP and expense features: what's included and what to add
- Vergo's NolaPro integration
- Get started with Vergo
What NolaPro includes
Invoice and purchasing approvals
Partly. Approval is documented for AP bills (pre-approval and approval for payment, with email notices). However, the changelog documents no configurable approval routing for POs or expenses.
Expense claim approvals
Partly. Employee out-of-pocket expenses are imported by CSV into AP bills, which then go through the AP bill approval process. However, NolaPro has no dedicated expense-report module.
What teams add alongside it
- Expense management app with receipt capture
- AP automation / invoice capture (OCR)
Where Vergo fits with NolaPro
Vergo adds approvals on the spend before it reaches NolaPro. 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 NolaPro, coded to your account, job and location.
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 NolaPro, with its receipt.
