NetSuite Insights & Guides | CuriousRubik

NetSuite EDI in Australia: A Guide for Retail Suppliers

Written by Swara | Nov 19, 2026, 4:31:00 AM

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

  • Map each EDI message to its main NetSuite record and name an owner before you build.
  • Check item identifiers, delivery locations and prices against the retailer’s file.
  • The despatch advice must match the pallets on the truck, SSCC by SSCC, and arrive before the goods.
  • Plan for retailer accreditation testing, then run a daily exception search once you are live.

What is NetSuite EDI for Australian retail suppliers?

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.

Which EDI messages map to which NetSuite records?

Start with a one page map. Each retailer uses a slightly different set, so confirm the list in their current specification.

EDI messageWhat it tells youNetSuite recordUsual owner
ORDERS (purchase order)Items, quantities, prices, delivery date and locationSales order, with the retailer's order number in the PO # fieldCustomer service
ORDCHG (order change)A changed quantity, date or lineThe same sales order, updated with a noteCustomer service
ORDRSP (order response)Your confirmation or changes to the orderSent from the approved sales orderCustomer service
DESADV (despatch advice, often called the ASN)What is on each pallet, with SSCCsSent from the item fulfillmentWarehouse
INVOIC (invoice)Your tax invoice for the goodsSent from the NetSuite invoiceAccounts receivable
RCTI (recipient created tax invoice)The retailer's own tax invoice for what it receivedMatched to your NetSuite invoiceAccounts receivable
REMADV (remittance advice)Which invoices a payment covers, less any deductionsCustomer payment and credit memosAccounts 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.

How do you set up items, customers and locations for EDI?

Check these records against a sample from the retailer before the first test order.

  1. Add Global Trade Item Numbers (GTINs) to the items you trade. Put the consumer unit barcode number in the UPC Code field on the item record. Record the carton GTIN as well if the retailer orders in cartons, in a field your connector can map to the carton unit.
  2. Map the retailer's article numbers. Some retailers send their own item code beside the GTIN. Keep a cross reference so the connector can find the right NetSuite item every time.
  3. Store GLNs on delivery addresses. Retailers identify stores and distribution centers by GLN (Global Location Number). Add each GLN to the matching ship to address on the customer record, or to a custom record the connector reads.
  4. Set up one customer per trading partner. Keep the retailer's EDI settings, such as its message set and invoice method, on that customer or in the connector's configuration for it.
  5. Agree the price list. Confirm whether the order file shows prices before or after goods and services tax (GST). Load the agreed prices as a price level or customer pricing in NetSuite so the order total matches the file.
  6. Check the GST tax code. Taxable goods use the 10 percent GST code on the sales order. Any GST free lines need their own code so you can reconcile the invoice to your Business Activity Statement (BAS).
  7. Set the order defaults. Choose the department, class, location and terms that EDI orders should carry, so sales reports by channel work from the first day.

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.

How do despatch advice and SSCC labels work from NetSuite?

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.

  1. Send the despatch advice by the retailer’s cutoff before delivery. Use one business day ahead as a planning buffer until you confirm the actual deadline.
  2. Confirm whether the retailer permits multiple orders in one shipment.
  3. Assign a distinct SSCC to each pallet or other logistics unit in the shipment.

Invoices, RCTIs and payments

Your invoice or the retailer's RCTI

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.

Remittances and deductions

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.

How should you test and run EDI each day?

Ask each retailer whether it requires accreditation testing and what it expects you to prove before it sends production orders.

  1. Build in the sandbox first. Connect the connector to your NetSuite sandbox and run test orders through to invoice.
  2. Test the awkward cases. Include an order change, a short shipment, a mixed pallet, a GST free line and a canceled order.
  3. Book the retailer's test window. Send the test messages they ask for and keep their confirmation.
  4. Go live one retailer at a time. Start with the partner that sends the fewest orders, then add the next.
  5. Run a daily exception search. Have the connector log responses, shipment notices and invoice acknowledgments against the mapped NetSuite records. Use those fields or linked records in your searches to spot missing messages or RCTI matches.

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.

Related reading

NetSuite 3PL Integration in Australia for Wholesalers

How locations, order and stock messages and fulfillment fees work with a third party warehouse.

NetSuite Barcode Scanning in Australia: A Warehouse Example

GS1 carton codes, five scan points and the devices that suit an Australian warehouse.

A NetSuite EDI Integration Discovery Checklist

The questions to settle with each trading partner before an EDI build starts.