What is vendor master management?
Clean vendor records, including the tax data January will ask for.
The supplier master is the file every payment run, every BAS coding decision, and every invoice-fraud attempt against your AP process runs through — and it's usually the record nobody maintains once the first invoice is paid. Vendor master management treats that supplier file as its own discipline: captured properly at onboarding, deduplicated against what already exists, locked down against unauthorised bank-detail changes, and cleaned up when a supplier goes quiet, rather than left as an open, unwatched entry point sitting behind every payment run.
Onboarding is where the record gets built properly or doesn't. A new supplier record needs an ABN, checked against the ABN Lookup register, alongside the entity type — sole trader, company, trust, partnership — and its GST registration status. That last field matters more than it looks: an active ABN doesn't automatically mean the supplier is registered for GST, and whether they are determines how their invoices should be coded. We capture and verify all of it before the first invoice is queued for payment, because a supplier record built from whatever their first invoice happened to say is a record built on an assumption, not a check.
Why it matters
| Without a system | With CapEasy |
|---|---|
| Cash flow shortages that were predictable | Predictable inflows and controlled outflows |
| Revenue leakage from uninvoiced work | Aging you can act on before it is a problem |
| Duplicate or early payments | A clean audit trail on every payment |
| Supplier disputes over what was actually agreed | Working capital you can actually plan around |
What we need from you
Receivable
- Customer master data
- Sales invoices
- Payment history
- Credit terms
Payable
- Supplier master data
- Purchase orders
- Supplier invoices
- Payment terms
- Expense receipts
How it runs, step by step
- Receivable
- Invoice creation and validation
- Recurring invoice setup
- Credit notes
- Payable
- Invoice recording and coding
- Three-way matching (PO, receipt, invoice)
- Payment scheduling and due-date monitoring
- Inventory, where relevant
- SKU-level tracking
- Multi-location stock
- FIFO / weighted average costing
Who does what
| Your CapEasy team | Vendor master management, the reconciliations and reporting behind it, and the questions list that keeps it honest. |
| Your registered BAS or tax agent | Everything that carries a licence in Australia — rendered exactly as written: work out what goes on your bas, or advise you on it — under tasa 2009 that requires registration we do not hold. |
| You | One conversation with one named person, and the decisions that are genuinely yours. |
Vendor master management in Australia
ABN capture and verification at onboarding, ahead of the withholding question it prevents
A supplier's ABN is checked against the ABN Lookup register — confirming it's active and registered to the entity actually invoicing you — before the record clears onboarding. A supplier who doesn't quote a valid ABN can trigger a PAYG withholding obligation on that payment unless an exception applies; catching a missing or invalid ABN at the vendor-master stage is what keeps that from surfacing as a problem after several payments have already gone out.
GST registration status is a vendor-master field, and it drives how the invoice gets coded
An active ABN does not mean the entity is registered for GST — the two are checked separately via ABN Lookup, and both are recorded on the supplier record. Whether a supplier is GST-registered determines whether their invoices should carry a GST component at all, which is exactly the kind of detail that has to be right before a tax invoice reaches AP coding, not corrected after it's already been entered.
Entity type shapes what the supplier record needs, beyond how it's labelled
Whether a supplier is a sole trader, a company, a trust, or a partnership affects what documentation the record needs and how PAYG-withholding exposure is assessed if the ABN is missing. We capture entity type at onboarding from the supplier's own registration detail, not inferred from an invoice header or a trading name.
Bank-detail change control is treated as the fraud vector it is
Invoice and payment-redirection fraud — a spoofed or compromised email requesting a change to a known supplier's bank details — is one of the most common ways Australian businesses lose money through a process that looks completely routine from inside AP. No bank-detail change on an existing supplier record goes live from an email request alone. It requires a callback to a phone number already on file, never one supplied in the change request, verified by a named person, and logged with who verified it and when.
What your registered BAS or tax agent receives from us
- A supplier master file keyed to each supplier's verified ABN, not the trading name as typed on an invoice
- ABN Lookup verification result — active status and GST registration status — recorded on every supplier record at onboarding
- Entity type captured per supplier (sole trader, company, trust, partnership), sourced from the supplier's own registration detail
- A bank and remittance-detail audit trail: every change logged with who requested it, who verified it by callback, and when it went live
- A deduplication log showing every near-duplicate supplier record identified, merged, or flagged for review
- A dormant-supplier report — suppliers past a defined inactivity window, flagged for confirmation and deactivation
