Key takeaways
- Invoice and purchasing approvals: Yes. Purchasing supports requisitions submitted by staff and authorized or rejected by supervisors in Staff Kiosk before PO approval.
- Expense claim approvals: not publicly documented; confirm with The Alpha School System Pty Ltd.
- Vergo approvals are optional and run before coded spend posts into TASS.
Where should you go next?
- TASS AP and expense features: what's included and what to add
- Vergo's TASS integration
- Get started with Vergo
What TASS includes
Invoice and purchasing approvals
Yes. Purchasing supports requisitions submitted by staff and authorized or rejected by supervisors in Staff Kiosk before PO approval. Supplier invoices can be routed to staff for approval in Staff Kiosk/Portal (goods-received verification), where the first assignee to act is the final approver.
Expense claim approvals
Expense claim approvals are not publicly documented for TASS. Confirm with The Alpha School System Pty Ltd before you budget.
What teams add alongside it
- AP automation / invoice capture tool via the AP Integration API
- Staff expense claim app with receipt capture
Where Vergo fits with TASS
TASS's own workflow can keep governing the documents listed above. Vergo's approvals sit on the spend before it reaches TASS. 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 TASS, coded to your GL account segments and GST tax code.
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 TASS, with its receipt.
