An accounts payable system is the combination of processes, controls, and software that manages how a business receives, validates, approves, and pays supplier invoices. Most tools on the market handle the intake and data extraction parts adequately. What they miss is the control layer: the checks that happen between an invoice arriving and money leaving the account. That gap is where errors compound, fraud enters, and GST claims go wrong. This guide covers what each component of a well-designed AP system actually needs to do for an Australian SMB, and what to look for when you are evaluating options.
What Most Accounts Payable Systems Actually Skip
The default assumption is that AP software is primarily about getting invoice data into your accounting system faster. That framing is wrong for any business managing more than a handful of invoices a week.
Getting data in faster without verifying what you are putting in does not reduce risk. It accelerates it. An incorrect account code, a GST treatment applied without checking, a supplier bank detail that changed last week: all of these move through a fast workflow just as easily as a legitimate, clean invoice. The speed advantage disappears when the rework and fraud exposure are factored in.
A well-designed accounts payable system has seven functional components. Most off-the-shelf tools handle two or three of them. Understanding which components are present, and which are absent, is what distinguishes a buying decision from a software selection.
The Seven Components of a Well-Designed AP System
1. Invoice Intake: One Channel, All Formats
The first function of any AP system is collecting invoices from wherever they arrive. For most Australian SMBs this means email (PDF attachments), portal submissions from construction management platforms like Procore, and occasionally paper invoices that have been scanned.
The intake function needs to handle multi-page documents, supporting attachments, and variation in invoice layout without requiring manual pre-sorting. If a team is still manually forwarding PDFs from a shared inbox into a processing tool, or re-uploading documents they already received digitally, the intake function is not doing its job.
A single intake point matters because fragmented intake creates gaps. Invoices that arrive via a secondary channel and do not make it into the main workflow are the ones that get paid twice, or do not get approved at all until a supplier follows up.
2. Pre-Approval Validation: Catching Problems Before They Reach the Queue
Validation is the function that examines an invoice before it enters the approval workflow. It is the most commonly underdeveloped component in AP systems marketed to SMBs.
Pre-approval validation should check:
- ABN validity. The ATO requires that businesses verify supplier ABNs before payment. If a supplier’s ABN is not active or does not match the business name on the invoice, the business is required to withhold 47% of the payment under PAYG withholding rules. An AP system that does not check ABNs is leaving a compliance gap open on every invoice.
- Duplicate detection. The same invoice number, the same supplier, the same amount, within a short window: any of these combinations should trigger a flag before the invoice reaches an approver. Duplicate payments are one of the most common and most preventable AP errors. They are also one of the most embarrassing to explain to a supplier who has now been paid twice.
- Supplier bank detail changes. When a supplier’s bank account details differ from what is recorded in history, that discrepancy should be flagged immediately. Bank detail fraud does not look like fraud. It looks like a normal invoice from a familiar supplier. The difference only appears when the BSB and account number are compared systematically against prior transactions. A manual check relies on whoever is processing the invoice noticing something they have seen dozens of times before.
The 2024 ACCC Targeting Scams report confirmed that payment redirection scams cost Australian businesses $152.6 million in 2024, a 66% increase from the prior year. The construction, real estate, and legal industries are specifically identified as the most targeted sectors, due to large transaction values and frequent invoicing. Validation at the pre-approval stage is the point where this risk is neutralised or allowed through.
3. Automated Line-Item Coding: Consistency, Not Speed
Line-item coding is the function that assigns each line of an invoice to the correct account code, with the correct GST treatment. For industrial businesses, this is not a minor task.
A single invoice from a construction subcontractor can cover labour, materials, equipment hire, and site costs, each mapping to a different account and potentially a different GST classification. Fuel tax credits, mixed-supply items, and project-based cost allocations add further complexity. Getting this wrong creates downstream problems: incorrect job costing, distorted project profitability reporting, and GST input tax credit claims that do not match the invoice detail.
The problem with manual coding is inconsistency. When different people process the same supplier’s invoices each month, they make different coding decisions. Over time, the same subcontractor ends up spread across multiple account codes depending on who processed their invoice that week. Reconciliation at month-end then requires interpretation work that should not exist.
An AP system that uses supplier history to auto-code line items closes this gap. It is not about coding faster. It is about coding the same way, every time, regardless of who is processing the invoice.
4. GST Handling: Flagging Exceptions, Not Reviewing Everything
GST treatment in Australia operates at the line level, not the invoice level. A single invoice from a freight supplier might include both GST-inclusive items and GST-free items. Applying a single GST code to the whole invoice introduces an error on every one of those invoices.
An AP system should apply correct GST treatment automatically based on supplier type and line-item description, and flag only the exceptions: items where the treatment is ambiguous or differs from the historical pattern. Finance teams should not be manually verifying GST on every line of every invoice. That is the kind of low-value work that creates errors through repetition and fatigue.
The ATO’s record-keeping requirements require businesses to retain AP records for five years. An AP system that applies and records GST treatment at the line level makes BAS preparation and ATO audit responses significantly simpler.
5. Approval Routing: Authority, Not Just Notification
Approval routing is the function that sends invoices to the right people for sign-off before payment. Most AP tools include some version of this. The functional difference is between approval routing that enforces authority limits and approval routing that merely notifies.
A notification-based approval system sends an invoice to a manager. They can approve or ignore it. If they are travelling, the invoice waits or gets sent to the wrong person. If the invoice is above their authority limit, the system does not know or does not care.
An approval routing system with proper controls does the following:
- Routes invoices based on the amount, the cost centre, and the supplier category
- Enforces delegation of authority: a $10,000 invoice does not get approved by someone with a $5,000 limit
- Escalates automatically when an approver is unavailable, rather than stalling
- Creates a complete audit trail of who approved what, when, and at what amount
Segregation of duties is relevant here. The person who creates a supplier record should not also be the person who approves payment to that supplier. An AP system that does not enforce this separation creates an internal control gap that auditors will flag and that fraudulent employees can exploit.
6. Purchase Order Matching: Catching Discrepancies Before Payment
PO matching is the function that compares an invoice against the purchase order that authorised the spend. Two-way matching checks the invoice against the PO. Three-way matching adds the goods receipt or delivery confirmation.
For Australian wholesale and construction businesses, PO matching is not optional. A subcontractor submitting a progress claim for work that has not been signed off, a materials supplier invoicing for a delivery quantity that does not match what was received: these discrepancies need to be caught before the invoice is approved, not discovered during project reconciliation three months later.
An AP system without PO matching capability means someone is manually cross-referencing invoice values against purchase orders in a separate system, or not checking at all. The first option is slow. The second is an internal control failure.
The practical benefit of automated purchase order matching is not just catching fraud. It is catching the mundane errors that accumulate over time: invoices billed at the wrong rate because the supplier was not notified of a contract price change, quantities that do not match delivery dockets, partial deliveries billed as complete.
7. Ledger Publishing: Clean Bills, First Time
The final function is publishing the processed, approved invoice to the accounting system as a clean bill, correctly coded, with all approvals recorded.
For Australian SMBs, this almost always means Xero or MYOB. Both platforms are strong ledgers. What neither does natively is the work that should happen before an invoice reaches them. Xero has no native line-item coding based on supplier history, no exception flagging, no vendor validation, and no PO matching at the line level. MYOB is the same. The manual process that sits in front of both platforms is where the errors and fraud exposure live.
An AP system that connects directly to Xero or MYOB and publishes clean, coded, approved invoices closes the gap between intake and ledger without requiring duplicate data entry, manual re-keying, or reconciliation work at month-end.
What This Looks Like in Practice
A financial controller at a Brisbane wholesale distributor manages around 80 supplier invoices per week across three cost centres. Before implementing a structured AP system, invoices arrived by email, were keyed into Xero manually, and coding decisions varied depending on which team member processed the batch. PO matching was done by pulling up the original order in a separate system and comparing values by eye.
The failure point was not obvious day-to-day. It showed up at month-end: account codes for the same freight supplier split across three different codes depending on who had processed the invoice, GST claims that did not reconcile with the invoice detail, and two instances per quarter on average of duplicate payments that needed chasing and crediting.
The cost was not just the duplicate payments. It was the six to eight hours of reconciliation work each month-end to untangle the inconsistency and prepare accurate reporting.
A system that coded automatically from supplier history, flagged duplicates before approval, and published clean bills to Xero eliminated the reconciliation work. Month-end close went from two days to half a day.
Where Xero and MYOB Fall Short
Xero and MYOB are excellent accounting platforms. They record, report, and reconcile financial data reliably. The gap is in what they do not do.
Neither platform validates supplier bank details against historical records. Neither applies automated line-item coding based on supplier history. Neither flags GST exceptions at the line level. Neither enforces approval limits or segregation of duties natively. Neither matches invoices against purchase orders without manual intervention.
This is a known limitation, not a criticism. Both platforms are built as ledgers. The workflow that should sit in front of them, between invoice arrival and ledger entry, is designed to be served by specialised tools.
The common approach of combining Dext for extraction with ApprovalMax for approvals partially addresses this. Dext handles OCR extraction well. ApprovalMax handles approval workflows. But the combination creates its own problems: two subscription costs, context loss between tools because coding history in one does not automatically inform logic in the other, and a gap in vendor validation that neither tool addresses directly.
An AP automation platform that handles intake, coding, validation, matching, and ledger publishing in a single workflow does not require two tools to cover one process.
Evaluation Checklist for an Accounts Payable System
Use this checklist when assessing any AP system for an Australian SMB:
Intake and extraction
- [ ] Accepts invoices from email, portals, and upload without manual pre-sorting
- [ ] Handles multi-page documents and supporting attachments
- [ ] Extracts line-item detail, not just header data
Pre-approval validation
- [ ] Validates ABN against the Australian Business Register
- [ ] Flags changed supplier bank details against historical records
- [ ] Detects duplicate invoices before they enter the approval queue
Coding and GST
- [ ] Auto-codes line items using supplier history
- [ ] Applies correct GST treatment at line level, not invoice level
- [ ] Flags GST exceptions for review rather than requiring manual verification on every invoice
Approval routing
- [ ] Routes invoices based on amount, cost centre, and supplier type
- [ ] Enforces delegation of authority limits
- [ ] Maintains a complete, timestamped audit trail of approvals
- [ ] Enforces segregation of duties between supplier management and payment approval
PO matching
- [ ] Supports two-way matching (invoice vs. PO)
- [ ] Supports three-way matching (invoice vs. PO vs. goods receipt)
- [ ] Flags mismatches before the invoice reaches the approval queue
Ledger publishing
- [ ] Publishes directly to Xero or MYOB without manual re-entry
- [ ] Carries account codes and GST treatment through to the ledger accurately
- [ ] Retains records in a format suitable for ATO audit and BAS preparation
Reporting and audit
- [ ] Provides a full audit trail from invoice receipt to ledger entry
- [ ] Allows exception reporting: what was flagged, why, and how it was resolved
Questions to Ask Vendors
Before committing to an AP system, ask these questions:
-
How does your system validate supplier bank details? Can it compare new bank details against the account’s history automatically, or does it rely on manual review?
-
What happens when a PO and invoice do not match? Does the system flag the discrepancy, route it for manual review, or pass it through?
-
How does line-item coding work? Does the system learn from supplier history, or does someone need to configure rules manually for each supplier?
-
How is GST applied? Is it at the invoice level or the line level? How are mixed-supply invoices handled?
-
What approval controls exist? Can you enforce delegation of authority limits by approver and by amount? Is segregation of duties built in?
-
How does it connect to Xero or MYOB? Does it publish clean bills directly, or does it require manual export and re-import?
-
What does the exception workflow look like? When the system flags something, how does the finance team resolve it and what is recorded?
- Does ABN validation run on every invoice, or only on new suppliers?
Who This Fits and Who It Does Not
| Business profile | Recommendation |
|---|---|
| Under 20 invoices per week, single approver, no POs | Xero or MYOB native approvals may be sufficient. A dedicated AP system adds cost without proportionate benefit. |
| 20-50 invoices per week, multiple suppliers, basic approval tiers | A mid-market AP tool with approval routing and duplicate detection. Full line-item coding is optional at this volume unless the invoices are complex. |
| 50+ invoices per week, multiple approvers, project-based costing, or PO workflows | A dedicated AP system with full validation, coding, PO matching, and direct ledger publishing is required. Manual processes at this volume create reconciliation debt that compounds each month. |
| Construction, wholesale, or healthcare businesses at any volume above 30 invoices per week | Line-item complexity and fraud risk in these sectors means ABN validation, bank detail checking, and PO matching are not optional, regardless of invoice volume. |
| Accountants and bookkeepers managing multiple clients | A system that handles multi-entity management without per-client pricing is the relevant evaluation criterion, alongside clean Xero and MYOB integration. |
The Control Layer That Most Tools Ignore
There is a temptation to evaluate AP systems primarily on throughput: how fast can invoices be processed, how many steps are automated, how much manual work is removed.
Throughput matters. But the more important question is what happens at the edges: the invoice that arrives with changed bank details, the duplicate that comes in from a supplier who resubmitted after not hearing back, the GST treatment that is wrong because the supplier changed their pricing structure and the invoice does not make the split explicit.
These are the moments where money is lost or retained. An AP system that processes routine invoices at high speed but passes edge cases through unchecked is not providing control. It is providing the illusion of it.
The validation and exception review layer is where this is resolved in practice: flagging anomalies before they reach the approval queue, not after payment has been made. Pulsify builds its workflow around this principle, comparing supplier details against historical behaviour, flagging exceptions with colour-coded risk signals, and routing only clean invoices through for approval. The control function is upstream of the ledger, not bolted on after the fact.
Businesses that have processed 90 invoices this week without a problem should not take comfort in that. They have processed 90 invoices without detecting a problem. That is a different thing.
Frequently Asked Questions
What does an accounts payable system actually do?
An accounts payable system manages the full process from receiving a supplier invoice to paying it: intake, validation, coding, approval, and ledger entry. A well-designed system does each of these steps in sequence, with controls at each stage to catch errors and flag anomalies before money leaves the account.
How is GST handled in an Australian AP system?
GST should be applied at the line-item level, not at the invoice level. Mixed-supply invoices (where some lines are GST-inclusive and others are GST-free) need to be treated line by line to produce correct input tax credit claims. An AP system should apply GST treatment automatically based on supplier type and item description, flagging exceptions where the treatment is ambiguous rather than requiring manual verification on every invoice.
What is the difference between two-way and three-way PO matching?
Two-way matching compares the invoice against the purchase order: is the amount correct, and does the item match what was ordered? Three-way matching adds the delivery receipt or goods receipt confirmation: was the item actually received in the quantity billed? Three-way matching provides stronger control and is particularly important for construction and wholesale businesses where partial deliveries and progress claims are common.
How should an AP system handle changed supplier bank details?
Bank detail changes should trigger an automatic flag before the invoice enters the approval queue. The system should compare the bank details on the current invoice against historical records for that supplier and alert the finance team when a discrepancy appears. This is the primary control against payment redirection fraud, which cost Australian businesses $152.6 million in 2024 according to the ACCC Targeting Scams report.
Does Xero or MYOB handle the full AP process natively?
Neither platform handles the full process natively. Both are strong ledgers: they record and report financial data well. What they do not provide is line-item coding based on supplier history, ABN validation, bank detail change flagging, duplicate detection, or PO matching at the line level. These functions require a tool that sits in front of the accounting system, handling the workflow between invoice arrival and ledger entry.
When does an SMB actually need a dedicated AP system?
When manual processing is creating reconciliation work at month-end, when the same supplier is being coded inconsistently across different team members, when PO matching is being skipped because it takes too long, or when invoice volume has grown to a point where a missed duplicate or a fraudulent bank detail change would be easy to overlook. For construction, wholesale, and healthcare businesses, the threshold is lower than for service businesses because invoice complexity and fraud risk are higher.