How to automate expense management in Wiise

Key takeaways

• Wiise is an Australian cloud ERP built on Microsoft Dynamics 365 Business Central.
• Dimensions tag transactions for reporting, with defaults on G/L accounts; GST flows to the BAS.
• ACSISS bank feeds bring Australian bank lines in for reconciliation.
• Vergo proposes account, dimensions and GST by inference and records entries through the Business Central API.

Where should you go next?

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

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

1. Connect Wiise. Vergo connects through Wiise's standard Business Central API and records coded card spend as journal lines or purchase invoices, with dimensions and GST on each line.
2. Connect your existing cards. Connecting your existing cards involves no card applications, no re-issuing and no banking change.
3. Collect receipts by text. 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. Code account, dimensions and GST. Vergo proposes the G/L account, each dimension value and the GST treatment.
5. Record and reconcile. The entry lands in Wiise, so the ACSISS feed line matches on reconciliation.

What does Wiise need on each card transaction?

• G/L account with any default dimensions.
• Dimension values, such as cost centre, location or project.
• GST treatment, for the BAS.
• Receipt, for audit.

Where does Wiise stop and automation start?

Wiise downloads bank feed lines and matches them automatically where it can, and default dimensions on G/L accounts fill in the obvious values. A new supplier, a split receipt or a purchase for a specific project still needs someone to choose. Vergo reads the receipt itself, line by line, and predicts the coding from what was actually bought — the G/L account, dimensions and GST — not just the vendor name on the header.

A practical example

An NDIS provider on Wiise tracks dimensions by program and location. A support coordinator buys activity supplies and a taxi fare on a company card. Vergo asks for the receipt by text, then proposes program supplies with the right program and location dimensions and GST for the supplies, and client transport for the taxi, as similar spend was coded. The finance officer confirms and the entry is recorded in Wiise.

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. In Wiise, that includes the dimension values your team chose beyond the G/L defaults, which is where reporting usually breaks. Every coding shows why it was chosen, so a reviewer confirms in seconds instead of re-coding by hand. 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.