Key takeaways
- Invoice and purchasing approvals: Partly. MoneyWorks Gold and Datacentre support custom purchase order approval built with validations, mwScript scripts and custom forms, so approval has to be configured rather than switched on. However, the standard user privileges have no approve or authorise privilege, only entry and processing rights.
- Expense claim approvals: not publicly documented; confirm with Cognito Software.
- Vergo approvals are optional and run before coded spend posts into MoneyWorks.
Where should you go next?
- MoneyWorks AP and expense features: what's included and what to add
- Vergo's MoneyWorks integration
- Get started with Vergo
What MoneyWorks includes
Invoice and purchasing approvals
Partly. MoneyWorks Gold and Datacentre support custom purchase order approval built with validations, mwScript scripts and custom forms, so approval has to be configured rather than switched on. However, the standard user privileges have no approve or authorise privilege, only entry and processing rights.
Expense claim approvals
Expense claim approvals are not publicly documented for MoneyWorks. Confirm with Cognito Software before you budget.
What teams add alongside it
- Expense management with card feeds and receipt capture
- Approval workflow tooling
Where Vergo fits with MoneyWorks
Vergo adds approvals on the spend before it reaches MoneyWorks. 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 MoneyWorks, coded to your GL code and department suffix.
Frequently Asked Questions
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 MoneyWorks, with its receipt.



