Key takeaways
- Invoice and purchasing approvals: Yes. The PeopleSoft Approval Framework (Approval Workflow Engine) is configured in online pages and drives approvals for vouchers, expense transactions and other FSCM transactions.
- Expense claim approvals: Yes. PeopleSoft Expenses routes expense reports and cash advances through configurable Approval Framework approver types.
- Vergo approvals are optional and run before coded spend posts into PeopleSoft.
Where should you go next?
- PeopleSoft AP and expense features: what's included and what to add
- Vergo's PeopleSoft integration
- Get started with Vergo
What PeopleSoft includes
Invoice and purchasing approvals
Yes. The PeopleSoft Approval Framework (Approval Workflow Engine) is configured in online pages and drives approvals for vouchers, expense transactions and other FSCM transactions. Approvers can approve, deny, push back, hold or add approvers, and voucher rules can be set by business unit, origin, control group and supplier.
Expense claim approvals
Yes. PeopleSoft Expenses routes expense reports and cash advances through configurable Approval Framework approver types. Routing falls back to the employee's supervisor or designated approver, and reports move to Approved for Payment once the last approver authorized for payment signs off.
What teams add alongside it
- AP automation / invoice capture (third-party imaging and OCR)
- Expense management app with receipt OCR
Where Vergo fits with PeopleSoft
PeopleSoft's own workflow can keep governing the documents listed above. Vergo's approvals sit on the spend before it reaches PeopleSoft. 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 PeopleSoft, coded to your ChartFields: account, department, operating unit, fund and project.
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 PeopleSoft, with its receipt.



