Accounts payable for wholesale and distribution businesses in Australia is not primarily a volume problem. It is a complexity problem. Where a service business might process a clean invoice from a single supplier against a single account code, a wholesale distributor routinely receives invoices that touch multiple purchase orders, multiple cost centres, multiple GST treatments, and multiple inventory lines - all from a single freight carrier or supplier. That complexity does not scale with headcount. Adding staff does not fix a process that was never designed to handle it.
This guide focuses on the specific AP challenges wholesale and distribution businesses face. If you need a broader overview of accounts payable automation, see our guide: AP Automation for Australian Businesses.
How does AP work in a wholesale or distribution business?
Most wholesale businesses operate with a purchasing workflow that looks straightforward on paper: raise a purchase order, receive goods, match the invoice, pay. In practice, the chain between those steps is where complexity accumulates.
A wholesale distributor in Adelaide dealing with twenty to thirty active suppliers will typically manage invoices across three or four categories simultaneously: stock purchases, inbound freight, outbound delivery charges, and sundry items like pallets, returns credits, and warehouse handling fees. Each category has different coding requirements, different GST treatment, and often different approval thresholds.
The accounts team is not just processing invoices. They are making repeated coding decisions that affect inventory valuation, cost of goods sold, gross margin, and GST reporting accuracy - often under time pressure and often with incomplete information, because freight invoices routinely arrive days or weeks after the stock.
MYOB is the dominant accounting platform in this segment precisely because its inventory module provides structure for stock movements. But MYOB’s AP workflow, like Xero’s, still relies on manual decisions for the pre-ledger work: coding, matching, exception handling, and supplier validation. The inventory module records what happened. It does not help the AP team process invoices more accurately before they reach the ledger.
Where it breaks: the three fault lines in wholesale AP
1. PO matching at line level
Two-way matching via purchase order reconciliation is standard practice in wholesale. But it is standard at the header level, not the line level - and that distinction matters enormously.
A supplier invoice might reference a single purchase order number but include line items that map to different deliveries, different stock locations, or different projects. If the AP team is matching at the header level only (total invoice amount against total PO value), partial deliveries and line-level variances slip through. The invoice clears matching, gets coded as a single entry, and lands in the ledger before anyone has noticed that three of the line items were priced differently to the PO, or that one line item was never received.
Line-level PO matching requires comparing each invoice line to the corresponding PO line and goods receipt. For a wholesale business processing 150 to 300 invoices a month, doing this manually is not realistic. Teams take shortcuts. Shortcuts compound.
2. Freight invoices that span multiple runs
Freight is where wholesale AP gets structurally messy in a way that most AP tools are not designed to handle.
A freight carrier covering a wholesale distributor’s weekly outbound deliveries will typically issue a single invoice covering multiple delivery runs across different customer orders. Each run may relate to a different cost centre (if the business charges freight back to customers), a different GST treatment (local freight is GST-inclusive; some export legs are GST-free), and a different purchase order if the delivery was raised against a customer-facing job.
The AP team receives one invoice. The accounting work behind it may require five or six coding decisions, three cost centre allocations, and a cross-check against delivery dockets to confirm what was actually shipped. Most of that work happens manually, in a spreadsheet, after the invoice has already been entered into MYOB.
The result is that freight costs end up either pooled into a general freight expense account (which distorts job costing and customer profitability) or allocated inconsistently, depending on who in the team processed the invoice that week. Both outcomes compound over time.
3. Inventory-linked invoicing and landed cost
Wholesale and distribution businesses carry inventory on their balance sheet. The value of that inventory depends on landed cost: the purchase price plus inbound freight, duties, and handling. When inbound freight invoices are coded incorrectly or arrive late, inventory valuation drifts from reality.
This is not a trivial issue. Understated inventory costs inflate gross margin and distort pricing decisions. Overstated costs do the reverse. Neither shows up immediately, because the error sits in the ledger silently until someone reconciles inventory at month end - or until the business notices that margins are not what the reports suggested.
The practical problem is timing. Stock arrives and is receipted into MYOB. The freight invoice for that shipment arrives two weeks later. By then, the stock may already have been sold. The landed cost calculation is now retrospective, and correcting it requires adjustments that most AP teams defer until month end, if they make them at all.
Why it breaks: the process was designed for simpler invoices
The core issue is that most AP workflows, including the default workflows in Xero and MYOB, were built around the assumption that one invoice maps to one account code and one GST treatment. That assumption holds for service businesses. It does not hold for businesses that buy and move physical goods.
Wholesale and distribution AP involves invoices that are structurally complex by default, not by exception. A freight invoice with seven line items is not an unusual invoice. It is a normal invoice. An invoice from a stock supplier that covers three partial deliveries against two purchase orders is not an edge case. It is Tuesday.
When the process treats these as exceptions to be handled manually, the manual workload is enormous. And because the decisions being made are accounting decisions with real consequences for inventory valuation, cost allocation, and GST compliance, they cannot safely be delegated to the most junior person available.
The deeper problem is inconsistency. When coding decisions are made manually by whoever processes the invoice that week, the same freight carrier ends up coded to different accounts across different months. The same landed cost gets allocated to inventory in one invoice and to freight expense in the next. Reporting becomes unreliable. Month-end becomes a reconciliation exercise rather than a reporting exercise.
A scenario: a financial controller in Melbourne managing multi-supplier freight coding
A financial controller at a Melbourne-based wholesale food distributor handles AP across three warehouses and roughly 200 invoices a month. Her two largest freight carriers each issue weekly invoices that cover between fifteen and twenty-five separate delivery runs, with line items referencing run numbers, customer codes, and weight charges.
Each run needs to be allocated against the correct customer order, and freight charges that are recoverable from customers need to be separated from internal logistics costs. Neither carrier’s invoice format is consistent with the other’s, and neither maps cleanly to the PO structure in MYOB.
She manages this with a combination of MYOB, Excel, and institutional knowledge. When she is available, it works well enough. When she is on leave or managing month-end close, the invoices either pile up or get processed by a junior staff member who applies flat-rate allocations to clear the queue. Those allocations require corrections. The corrections take longer than the original processing would have taken.
This is not a staff problem. It is a process problem. The freight coding work requires judgment, and that judgment is currently bottlenecked through one person.
What finance teams do about it (and why it does not scale)
The typical wholesale AP team response to complexity is workarounds: additional spreadsheets to track freight allocations, informal coding guides for common suppliers, verbal conventions that exist only in the memory of experienced staff.
These workarounds are rational given the constraints, but they have structural weaknesses.
First, they are not enforced. An informal coding convention is only as reliable as the person applying it. Under time pressure, team members take shortcuts. The convention degrades.
Second, they do not survive personnel changes. When the person who carries the institutional knowledge leaves, the team rebuilds the workarounds from scratch. The same errors recur.
Third, they do not surface exceptions in real time. If a supplier invoice contains changed bank details, a duplicate charge, or a line item that does not match the PO, the workaround process will often miss it. The error reaches the ledger. It is found at month end, if at all.
According to research by the Australian Taxation Office and Deloitte Access Economics, the average cost to process an emailed PDF invoice in Australia is AU$27.67. For wholesale businesses where many invoices require multiple coding decisions and manual PO matching, the actual per-invoice cost is materially higher than that average.
What the right process looks like
The correct process for wholesale AP is not a faster version of the manual process. It is a structurally different one, built around the assumption that invoices are complex and exceptions are normal.
Line-level coding, not header-level. Every invoice line should be coded independently, based on supplier history, line description, and the associated purchase order or delivery receipt. A freight invoice with six lines should produce six coded entries, not one. Automated line-item coding handles this by learning how each supplier’s invoices have been coded historically and applying that logic consistently, with exceptions flagged for human review rather than human processing.
PO matching before payment, not after. Invoice lines should be matched against open purchase orders and goods receipts before the invoice is approved for payment. Mismatches - including price variances, quantity discrepancies, and lines without a corresponding PO - should surface as exceptions that require sign-off, not as errors discovered at month end.
Exception flagging, not exception dumping. When an invoice cannot be automatically coded or matched, the workflow should route it to the right person with the relevant context: what the mismatch is, what the supplier’s history shows, and what the expected treatment should be. Dumping all unmatched invoices into a review queue without context forces the reviewer to reconstruct the same information the system already has.
Supplier validation before payment. Changed bank details on a supplier invoice should trigger an alert before the payment is processed. Payment redirection fraud cost Australian businesses AU$152.6 million in 2024, a 66% increase from the prior year, according to the National Anti-Scam Centre. Wholesale businesses, which have frequent invoicing relationships with many suppliers and high per-transaction values, are an obvious target. Manual bank detail checks performed under time pressure are not a sufficient control.
Consistent coding rules across all staff. The system should apply the same coding logic regardless of who processes the invoice. Historical supplier decisions should inform future coding automatically. This removes the dependence on institutional knowledge and eliminates the inconsistency that distorts month-end reporting.
Where MYOB fits and where it does not
MYOB is the right tool for wholesale and distribution businesses for exactly the reasons its users cite: inventory management, purchase order creation, and the ability to link stock movements to the ledger. For businesses that need to track inventory at cost and manage multiple warehouses, MYOB’s inventory module provides genuine structure.
What MYOB does not provide is an intelligent AP layer sitting in front of the ledger. The gap between receiving an invoice by email and having it correctly coded in MYOB is filled manually in most MYOB-based workflows. OCR tools like Dext can extract the data from the invoice, but they do not make the coding decisions. MYOB records what they are given. Neither tool addresses the judgment layer: how the invoice should be coded, whether it matches the PO, whether the supplier’s bank details have changed, whether a line item is a duplicate.
Some wholesale businesses run MYOB alongside a dedicated inventory management platform such as DEAR Inventory, Cin7, or Unleashed. The AP workflow in these setups often involves invoices flowing through two systems before reaching the ledger. The matching complexity increases. The manual touchpoints multiply. The case for a structured AP layer that handles coding, matching, and exception flagging before invoices reach either system becomes stronger, not weaker.
How to reduce AP complexity without adding headcount
The answer is not more staff. Australia processes approximately 1.2 billion B2B invoices annually, with around 90% still involving manual intervention. Scaling headcount to manage that volume is not a viable strategy for a 20 to 50 person wholesale business.
The practical approach is to move complexity out of the manual workflow and into the system:
- Supplier coding history should be captured and applied automatically, so the same invoice from the same freight carrier codes the same way every time without human input
- PO matching should occur at line level before approval, not after payment
- Exceptions should be surfaced with context, not just flagged as unresolved
- Bank detail changes and duplicate invoices should be detected before they reach the payment queue
- GST treatment should be assigned at line level and verified against ATO treatment rules, with exceptions flagged rather than missed
This is what a modern accounts payable automation layer does for wholesale businesses. It handles the repeatable decisions automatically and concentrates human attention on the invoices that genuinely require judgment.
Before Pulsify, teams processing fifty invoices a week were spending approximately four hours on coding, PO matching, and GST verification. After implementing Pulsify, the same workflow takes around fifteen minutes of exception review, with the remaining processing handled automatically.
Accounts payable for wholesale distribution: what good looks like
A wholesale AP workflow that handles complexity well has a few consistent characteristics.
Invoices arrive at a single intake point, regardless of how they are delivered. They are extracted and coded at line level against supplier history, with GST treatment applied automatically at each line. Freight invoices are allocated to the correct cost centres based on delivery run data or supplier coding rules. PO matching runs at line level before approval, and mismatches surface as specific exceptions rather than general holds.
Approved invoices publish directly to MYOB or Xero, coded correctly and matched. The only human touchpoints are the genuine exceptions: price variances that exceed tolerance, supplier details that have changed, invoices without a corresponding PO. Everything else moves through without interruption.
Month-end close is faster because invoices were right the first time. Inventory valuation reflects actual landed costs. Gross margin reports are reliable. The financial controller is reviewing exceptions, not rebuilding allocations.
Sources: ACCC - Targeting Scams Report 2024 · ATO - Record-keeping requirements for business
Further reading: Best AP Automation Software Australia 2026 · What a Modern AP System Needs to Do · The Real Cost of Manual AP