How to automate expense management in TASS

Key takeaways

• TASS is school management software for Australian independent schools, with finance modules for GL, AP, purchasing and budgets.
• TASS documents credit card payments as Cash Book Journals, with a scanned card statement as the example attachment.
• Each school defines its own GL account structure, up to ten segments.
• Vergo reads your chart of accounts, suppliers and tax codes and posts coded invoices through TASS's API.

Where should you go next?

• Vergo's TASS integration
• What expense management software integrates with TASS?
• Get started with Vergo

How do you automate expense management in TASS, step by step?

1. Connect TASS. Vergo uses TASS's documented OAuth2 APIs to read your chart of accounts, suppliers and tax codes.
2. Keep the school's cards. Connecting your existing cards involves no card applications, no re-issuing and no banking change.
3. Receipts from staff by text. Teachers, coaches and facilities staff reply with a photo. Employees handle everything by text message — no app to download, no portal login — and Vergo chases missing receipts itself instead of waiting for a report.
4. Confirm the GL account and tax code. Vergo proposes the full account code, including the segments your school uses for department or campus, and the GST code.
5. Deliver to TASS. Confirmed spend is posted as coded invoices through TASS's API, one line per purchase, with the receipt.

What does TASS need on each card purchase?

• GL account code: built from your school's segments.
• Tax code: for GST on the purchase.
• Supplier: the card provider or the merchant.
• Attachment: the receipt behind the line.

Where does TASS stop and automation start?

Recording the card statement as a journal gets the total into the ledger, but not the detail a bursar needs: which faculty bought what, and whether GST was charged. Getting that detail means collecting receipts from dozens of staff and coding each line against a long account structure. Vergo reads the receipt itself, line by line, and predicts the coding from what was actually bought, and proposes the account code and tax code together.

A practical example

An independent school on TASS issues cards to heads of department. The science head buys lab consumables and a staff morning tea on one card. Vergo texts for the receipt, proposes the science consumables account with GST for the supplies and the staff amenities account for the catering, and shows which earlier purchases it learned from. The finance officer confirms, and both lines are delivered to TASS already coded.

How Vergo handles this

Vergo proposes the coding by inference from your own accounting structure and history — no rule library to build, no keyword lists to maintain, and new vendors are coded on first sight. For a school, that includes the segments that separate campuses or faculties, which staff rarely know by heart. 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.