For Australian suppliers who sell to large retailers and want orders, despatch advice and invoices to flow through NetSuite.
Last reviewed: 19 November 2026. Product details reflect this review date. Availability and behavior can vary by account, role and release.
NetSuite EDI in Australia connects your account to each retailer through an EDI SuiteApp, an integration platform or a managed EDI service. Purchase orders arrive as sales orders. The connector sends shipment notices from item fulfillments with pallet identifiers. Finance either sends a tax invoice or matches the retailer’s tax invoice to the NetSuite sale.
Key takeaways
EDI (electronic data interchange) is the exchange of business documents, such as orders and invoices, between two companies' systems in an agreed format. Large Australian retailers trade this way with their suppliers. If your retailer uses UN/EDIFACT, start with the message types below and check its supplier specification for the exact format.
NetSuite runs the business side of EDI. The orders, stock, shipments, invoices and receipts all live in NetSuite as normal records. The translation into each retailer's message format sits with an EDI connector.
That can be a SuiteApp installed in your account, a connector inside an integration platform, or a managed EDI service. In the NetSuite WMS workflow, the EDI integration translates the shipment data into the format the retailer expects.
Your team keeps working in NetSuite screens they already know, and the connector handles formats, mailboxes and retailer changes. The retailer’s purchase order number gives both teams a reference when they investigate a shipment or payment.
If you are earlier in the process, our NetSuite EDI integration discovery checklist lists the questions to settle with each trading partner first.
Start with a one page map. Each retailer uses a slightly different set, so confirm the list in their current specification.
| EDI message | What it tells you | NetSuite record | Usual owner |
|---|---|---|---|
| ORDERS (purchase order) | Items, quantities, prices, delivery date and location | Sales order, with the retailer's order number in the PO # field | Customer service |
| ORDCHG (order change) | A changed quantity, date or line | The same sales order, updated with a note | Customer service |
| ORDRSP (order response) | Your confirmation or changes to the order | Sent from the approved sales order | Customer service |
| DESADV (despatch advice, often called the ASN) | What is on each pallet, with SSCCs | Sent from the item fulfillment | Warehouse |
| INVOIC (invoice) | Your tax invoice for the goods | Sent from the NetSuite invoice | Accounts receivable |
| RCTI (recipient created tax invoice) | The retailer's own tax invoice for what it received | Matched to your NetSuite invoice | Accounts receivable |
| REMADV (remittance advice) | Which invoices a payment covers, less any deductions | Customer payment and credit memos | Accounts receivable |
Use the owner column to decide who checks the original message and who can approve a corrected transaction.
Order changes need a rule too. Decide whether an ORDCHG updates the sales order automatically or waits for review. Automatic updates are faster, but a change after picking starts can leave the warehouse packing the wrong quantity. One option is to allow automatic updates before picking starts and send later changes to customer service for review.
Check these records against a sample from the retailer before the first test order.
If you are still allocating barcodes, our NetSuite barcode scanning in Australia example shows how carton codes and scan points fit together in the warehouse.
The despatch advice tells the retailer exactly what is arriving and how it is packed. The distribution center scans the SSCC (Serial Shipping Container Code) on each pallet's GS1-128 label. A mismatch can trigger a manual check. Agree with the retailer on who handles an unreadable label or a pallet missing from the notice.
In NetSuite, the item fulfillment is the source record. The warehouse packs the order into cartons and pallets, and each pallet gets a unique SSCC. The connector then builds the despatch advice from the fulfillment and its packing details.
If you use NetSuite Warehouse Management (WMS), enable its outbound ASN system rule and flag the customers or orders that need an advance shipment notice (ASN). WMS writes shipping data to custom records. Test how your connector maps those records to the retailer’s DESADV. This gives you a separate check on the WMS output before testing the message at the retailer’s end.
Confirm three shipping rules with each retailer.
Some retailers want your tax invoice as an INVOIC message, sent from the NetSuite invoice. Others raise a recipient created tax invoice (RCTI) themselves, based on what they received. Both parties must be registered for GST and have a current written agreement for eligible sales. Confirm eligibility and terms with your tax adviser.
Under an RCTI agreement, keep the NetSuite invoice as an internal record of the sale. Match it to the retailer’s RCTI when it arrives. The retailer issues the tax invoice.
A hypothetical Sydney supplier ships 120 cartons of taxable goods at A$42 each before GST. Its internal invoice shows A$5,040 plus A$504 GST, a total of A$5,544. The distribution center receives 118 cartons. The RCTI comes back at A$4,956 plus A$495.60 GST, a total of A$5,451.60.
The A$92.40 gap is two cartons, including their GST. The supplier checks pick and delivery records to find out where the two cartons went. If it accepts the shortfall, it records the agreed adjustment in NetSuite. If it disputes the difference, it keeps the balance open for review.
Remittance advice works the same way. Apply each payment to the invoices it lists, and review deductions before posting any credit memo. If you track deduction reasons in a configured field, use a saved search to group them and follow up on disputed amounts.
Ask each retailer whether it requires accreditation testing and what it expects you to prove before it sends production orders.
For a wholesaler with many retail accounts, this search becomes part of the morning routine, next to the open orders report. Our page on NetSuite for wholesale distribution shows how we set up the wider order and stock flow around it.
The first weeks after an EDI go live need the same close attention as any NetSuite launch. Our NetSuite hypercare in Singapore checklist shows a daily rhythm and an issue log that suit an EDI rollout well, wherever you trade.
If stock sits with a third party warehouse, the despatch advice may come from the warehouse's system instead. Our NetSuite 3PL integration in Australia explainer covers how those shipment messages return to NetSuite.
CuriousRubik's NetSuite fulfillment integration team can map your retailer messages to NetSuite records, set up the master data and run the accreditation tests with you.
Take your largest retail customer's EDI specification and fill in the message map above, with an owner for each row. Then pick ten items and check their GTINs and prices against the retailer's file.
How locations, order and stock messages and fulfillment fees work with a third party warehouse.
GS1 carton codes, five scan points and the devices that suit an Australian warehouse.
The questions to settle with each trading partner before an EDI build starts.