TRADE SERVICES · ACCOUNTS PAYABLE
An Azure document workflow for a trade services business in Adelaide and Melbourne: bills arrive by email and become coded draft bills in Xero.
- CLIENT
- Trade services business, Adelaide and Melbourne
- SECTOR
- Accounts payable
- BUILT
- Bill processing workflow
- CONNECTS TO
- Microsoft 365, Xero

01 / THE BRIEF
The accounts team spent significant time entering supplier bills from PDFs, scans and photos into Xero. Multi-invoice files, discounts, old balances and inconsistent supplier names made simple data entry surprisingly error-prone.
BEFORE
- ×Bills downloaded from email and typed into Xero
- ×Inconsistent supplier names and discounts
- ×Old balances and multi-document files untangled by hand
AFTER
- ✓Bills picked up from the mailbox automatically
- ✓Extracted, validated and coded
- ✓Uploaded to Xero as draft bills with the source attached
- ✓Staff review exceptions and approve every bill
02 / HOW IT WORKS
- STEP 1Bill arrives by email
- STEP 2Classified and extracted
- STEP 3Validated and coded
- STEP 4Draft bill in Xero
- STEP 5Staff approve
Mailbox pickup
Connected to the Microsoft 365 accounts mailbox, with bulk upload for documents received other ways.
Classification
Invoices, statements and remittances detected and sorted automatically.
Validation and coding
Supplier, invoice number, line items, tax and totals extracted, validated and mapped to the chart of accounts.
Checks and trail
Remittance matching, duplicate checks and a review trail, with Microsoft sign-in and role-based access.
03 / RESULTS
No re-keying
coded draft bills created in Xero for staff to approve
Source attached
original document attached to each draft bill, failures flagged
4
automated checks on every bill: validation, coding, duplicates, remittance match
2
businesses running on one shared platform
During development testing, validation caught a date misread as an invoice amount and correctly preserved a negative $69 discount line. These examples show how the workflow handles specific errors; they are not an overall accuracy benchmark.
04 / BUILT WITH
05 / SECURITY, PRIVACY & GOVERNANCE
- DATA RESIDENCY AND ACCESS
- Runs in the client's own Azure environment with least-privilege Microsoft 365 permissions; Xero credentials held in Azure Key Vault.
- PRIVACY
- Supplier contact and bank details minimised in logs and AI prompts; only the fields needed to create the bill are processed.
- COMPLIANCE
- Supports Privacy Act 1988 obligations and ATO record-keeping, with source documents retained against each bill.
- GOVERNANCE
- AI governance measures informed by ISO/IEC 42001: human approval of every bill, an audit trail and documented change control.
NEXT CASE →
"Data Dan": sales role-play for energy
A sceptical data centre buyer for the sales team to practise on.

thirty minutes, free, with the people who built it
Book a free call→