Walk into the finance team of almost any mid-sized Australian wholesale distributor and you’ll find the same setup: MYOB for accounting and inventory, a separate warehouse management platform for stock movements, and a gap between them that someone fills manually every week.
The gap looks manageable when invoice volumes are low. It becomes structurally expensive when the business grows, when supplier count increases, or when a high-volume month collides with month-end close. At that point, the finance team isn’t processing invoices - they’re reconciling two systems that were never designed to talk to each other.
This article is about what specifically breaks when inventory and AP live in separate silos, what it costs in practice, and what a properly connected AP system actually looks like for an Australian wholesale distributor.
What is the common setup and where does the gap live?
Most Australian wholesale distributors run some version of this stack:
- MYOB AccountRight (or, less commonly, Xero) for accounting, bill processing, and inventory management
- A standalone inventory or warehouse management system - or reliance on MYOB’s own inventory module - for stock receipting, PO management, and goods receipt notes
- Email as the primary invoice intake channel, with invoices forwarded to the bookkeeper or AP officer for entry
The theoretical workflow is straightforward: buyer raises a purchase order in the inventory system, goods arrive and are receipted, supplier invoice arrives and is matched against the PO via purchase order matching, matched invoice is approved and published to the ledger.
In practice, the gap lives between step three and step four. The PO exists in the inventory system. The supplier invoice arrives by email. The AP officer enters it into MYOB. But MYOB doesn’t automatically know which PO the invoice relates to, whether quantities and prices match, or whether the goods have actually been receipted. Someone has to bridge that gap manually - checking the PO in one system, comparing it against the invoice in another, making a judgment call about whether they match closely enough to approve.
When that person is experienced and has enough time, the check works. When they’re under pressure, when invoice volumes spike, or when the regular AP officer is away, the check gets abbreviated. Invoices get approved on “looks right” rather than verified against the PO. Discrepancies reach the ledger. They surface at month-end, when correcting them takes longer than the original verification would have.
What breaks: four specific failure modes
1. Invoices paid without matching a purchase order
In a high-volume week, it’s common for AP officers to process invoices that can’t be quickly matched to a PO - because the PO number wasn’t on the invoice, because the PO was raised in the inventory system and isn’t visible in MYOB, or because the invoice value differs slightly from the PO and the officer can’t determine whether the variance is a legitimate price adjustment or an error.
When the path of least resistance is to approve and move on, that’s what happens. The result: payments for goods not received, payments at the wrong prices, payments to suppliers for orders that may have been cancelled or modified.
2. Invoice coded to the wrong product line or account
Supplier invoices in wholesale distribution rarely map cleanly to a single account code. A stock invoice from a regular supplier might include items across three product categories, each with a different cost of goods account. A freight invoice might cover inbound landed cost (which belongs on the inventory asset), outbound delivery (an operating expense), and a fuel surcharge (a separate line item).
When coding decisions are made manually by whoever processes the invoice that week, the same supplier ends up in different accounts across different months. The financial controller notices at month-end that cost of goods sold looks inconsistent, traces it back to inconsistent coding, and spends two hours on corrections - none of which would have been necessary with consistent coding rules applied at the time of processing.
3. Duplicate invoices from high-volume suppliers
Wholesale distributors deal with the same freight carriers and stock suppliers weekly. High-volume suppliers occasionally issue duplicate invoices - sometimes billing system errors, sometimes genuine oversight, occasionally deliberate fraud. The risk is highest with suppliers whose invoice formats are dense and whose references (invoice numbers, PO references, delivery codes) aren’t immediately distinctive.
Manual duplicate detection requires the AP officer to search the supplier’s recent invoice history before approving. Under time pressure, that check gets skipped. The duplicate clears approval, reaches the payment queue, and is paid. Recovery is possible but takes time, creates friction, and sometimes never fully happens.
4. Bank detail changes going undetected
Payment redirection fraud targets exactly the type of supplier relationship wholesale distributors have: regular, trusted, high-value. A fraudulent invoice that looks identical to a genuine invoice from a known supplier - same format, same reference structure, same approximate value - but with changed bank details is unlikely to be caught by a manual check unless someone is specifically looking for it.
The ACCC’s National Anti-Scam Centre reported AU$152.6 million in payment redirection losses for Australian businesses in 2024. Wholesale distributors, with their combination of high per-invoice values and many regular supplier relationships, are a structural target.
What does manual reconciliation cost?
The cost of manual reconciliation in a wholesale distribution business isn’t abstract. It shows up in two places: staff time and error correction.
A finance team at a distributor processing 200 invoices per month commonly reports something like this:
| Activity | Time per month (manual) |
|---|---|
| PO matching and variance investigation | 8–12 hours |
| Coding corrections from month prior | 4–6 hours |
| Duplicate invoice identification | 2–3 hours |
| Supplier payment queries and reconciliation | 3–5 hours |
| Month-end close reconciliation | 6–10 hours |
That’s 23 to 36 hours per month - roughly one full working week - spent on reconciliation work that exists because the inventory system and the AP system don’t share information automatically. At AU$45 to AU$65 per hour for a finance officer, that’s AU$13,000 to AU$28,000 per year in labour costs directly attributable to the silo. Before accounting for errors that reach the payment queue and aren’t caught.
What a connected AP system for wholesale looks like
A properly connected AP layer handles the gap between the inventory system and the accounting ledger systematically. The workflow:
1. Intake. Invoices arrive at a single intake point regardless of delivery method - email, PDF, supplier portal, or EDI. The intake layer extracts invoice data including supplier details, invoice number, PO references, line items, quantities, and unit prices.
2. PO matching at line level. Each invoice line is matched against the corresponding open PO line in the inventory or ERP system via two-way matching. Price variances, quantity discrepancies, and lines without a matching PO reference are flagged as exceptions before the invoice proceeds to approval. Automatically. Not on request.
3. Validation. The supplier’s bank details are compared against the historical record. Duplicate invoice detection checks against recent invoice history. New suppliers are flagged for a separate onboarding step. Exceptions from any of these checks route to a resolution queue with context - a specific flag explaining what was detected, not a generic hold.
4. Approval routing. Validated invoices route to the correct approver based on structured approval workflows with dollar threshold and invoice category rules. An approver can’t approve above their configured authority limit, and invoices above the threshold escalate automatically.
5. Ledger posting. Approved invoices publish to MYOB or Xero with account codes, cost centres, and GST treatment applied at line level. Based on supplier history and line-item rules - not on whoever processed the invoice that day.
This workflow eliminates the manual bridge between the inventory system and the AP system. Human attention concentrates on exceptions - the invoices that genuinely require judgment - rather than routine processing.
The MYOB angle for wholesale distributors
MYOB AccountRight is the dominant accounting platform in Australian wholesale distribution because of its inventory module. Stock receipting, purchase order management, and inventory valuation are more capable in MYOB AccountRight than in Xero - which is why distributors tend to stay on MYOB even as other business types migrate elsewhere.
But MYOB’s AP functionality has the same pre-ledger limitations as Xero. MYOB records what it’s given. It doesn’t automatically match invoice lines to PO lines, detect changed bank details, identify duplicates, or apply consistent coding rules based on supplier history. The work still requires manual decisions.
Some wholesale distributors run MYOB alongside a separate inventory platform like Cin7, DEAR Inventory, or Unleashed. In those setups, purchase orders are raised in the inventory platform and stock is receipted there. The AP process then requires someone to cross-reference the inventory platform’s PO and receipt data against invoices entered into MYOB. The matching complexity increases. The manual touchpoints multiply. The case for a dedicated AP layer is stronger in this configuration, not weaker.
Pulsify’s PO matching layer integrates with MYOB AccountRight to pull open PO data and perform line-level matching before invoices enter the accounting ledger. The matching result - matched, partially matched, or unmatched - is visible in the approval workflow, so approvers are working with verified data rather than trusting the invoice at face value.
When native tools are sufficient - and when they’re not
Not every wholesale distributor needs a dedicated AP automation layer. The signal is invoice volume combined with process complexity.
Native tools are sufficient when invoice volume is below 60 to 80 per month, the majority of invoices are from a small, stable group of regular suppliers, invoices generally map to a single account code and straightforward GST treatment, and a single experienced person handles all AP with enough time for manual checks.
A dedicated AP layer makes sense when invoice volume exceeds 80 to 100 per month and is growing, multiple people approve payments and authority limits need enforcing, freight invoices regularly require multi-line coding and cost centre allocation, PO mismatches are discovered at month-end rather than before payment, the same supplier is appearing in different accounts across different months, or month-end close consistently takes longer than it should because of AP corrections.
The honest test is month-end close. If the finance team’s month-end experience regularly involves correcting AP errors from the prior month rather than reporting on clean data, the manual process is already the bottleneck.
The practical case for connecting the systems
The argument for a connected AP layer isn’t primarily about technology. It’s about where judgment should be concentrated.
In a manual wholesale AP workflow, human judgment is applied to every invoice - routine or not. The AP officer makes coding decisions on invoices that have the same format from the same supplier every week. She manually cross-references PO numbers that could be automatically matched. She checks supplier bank details from memory or informal comparison. She identifies duplicates by scanning her email history.
None of that is the highest-value use of a finance officer’s time. It’s high-volume, error-prone work that happens to require human execution in the absence of a system designed to handle it.
A connected AP system shifts human judgment to where it’s actually needed: the invoice where the price doesn’t match the PO, the supplier whose bank details have changed in a potential bank account change fraud scenario, the exception that genuinely needs investigation. Everything else moves through automatically, with consistent coding, verified matching, and a clean audit trail.
For a wholesale distributor processing 150 to 300 invoices per month, the reduction in manual AP work is substantial. Finance officers are working the exceptions queue - typically fifteen to thirty minutes per day - rather than processing every invoice manually. Month-end close reflects the month’s actual activity rather than the month’s activity plus a reconciliation of the prior month’s errors.
That’s a process design outcome. The technology just makes it possible to design the process correctly.
Sources: ACCC National Anti-Scam Centre - Targeting Scams Report 2024 · ATO - e-invoicing and invoice processing in Australia · ATO record-keeping requirements for business · Australian Bureau of Statistics - Wholesale Trade industry data
Further reading: What Breaks First When an E-commerce Brand Doubles Revenue · Accounts Payable for Wholesale and Distribution Businesses · AP Automation: Retail vs Wholesale Distribution