TPCx reaches end of life December 2026 | Don't wait until partners go dark | Plan Your Migration →
Comparatio logo
Oracle NetSuite · Managed EDI partner

NetSuite® EDI integration for distributors

Comparatio is the managed EDI partner for distributors on NetSuite. Customer orders become Sales Orders; supplier acknowledgments, ASNs and invoices land on the Purchase Order, as Inbound Shipments and as Vendor Bills. Our engineers build and run every map.

  • Customer and supplier side
  • Runs inside your NetSuite account
  • Maps run by our engineers

Your customers

  • Received: 850 orders
  • Sent: 855 · 856 · 810 · 846

Your suppliers

  • Sent: 850 purchase orders
  • Received: 855 · 856 · 810

Comparatio

Translates, checks and monitors your documents

NetSuite

  • Sales Order
  • Purchase Order
  • Inbound Shipment
  • Vendor Bill

Documents

Every NetSuite EDI document, and the record it lands on

Most NetSuite EDI pages stop at the customer’s 850, 855, 856 and 810. Distributors also buy: purchase orders go to suppliers, and their acknowledgments, ASNs and invoices come back into NetSuite. More on the supplier side: procure-to-pay EDI.

NetSuite EDI documents supported by Comparatio, with direction, NetSuite record and status
DocumentDirectionNetSuite recordStatus
850 Purchase orderFrom customerSales Order, createdCustomer-tested
855 PO acknowledgmentTo customerRead from the Sales OrderCustomer-tested
856 Advance ship noticeTo customerRead from the Item FulfillmentCustomer-tested
810 InvoiceTo customerRead from the Invoice or Credit MemoCustomer-tested
846 Inventory adviceTo customerItem quantities by locationCustomer-tested
860 PO changeFrom customerSales Order, updatedOn request
832 Price catalogTo customerItems and pricingOn request
850 Purchase orderTo supplierRead from the Purchase OrderCustomer-tested
855 PO acknowledgmentFrom supplierPurchase Order, acknowledgment fields updatedCustomer-tested
856 Advance ship noticeFrom supplierInbound Shipment (In Transit) or Item Receipt, createdCustomer-tested
810 InvoiceFrom supplierVendor Bill, created; repeat invoice numbers skippedCustomer-tested
832 Price catalogFrom supplierItem vendor pricing, updatedOn request
820 Remittance adviceTo supplierRead from the Vendor PaymentOn request
940 Warehouse shipping orderTo 3PLSales Orders ready to shipOn request
945 Warehouse shipping adviceFrom 3PLItem Fulfillment, createdOn request
846 Inventory adviceFrom 3PLInventory Adjustment, createdOn request

Customer-tested: run end to end in customers’ NetSuite accounts. On request: built, then switched on and tested for your partners during setup. Inbound X12 documents are acknowledged with a 997 as your partners require.

Partners who send PDFs instead of EDI

Our PDF Import handles them alongside your EDI traffic. In production on Prophet 21; available for CloudSuite Distribution and NetSuite. Customer purchase orders become Sales Orders, and supplier invoices that reference a PO become Vendor Bills in NetSuite®. Bills without a PO, such as carrier bills, are flagged for your team to enter. More about PDF Import

When a customer requires EDI

A trading partner wants EDI from NetSuite by a deadline

Most NetSuite EDI projects start with one requirement: a big customer asks for EDI orders, ASNs and invoices, or a supplier wants EDI purchase orders. Comparatio already trades with these partners for other distributors, so the maps exist. We connect them to NetSuite.

Supermarket aisle with stocked shelves

Retail and marketplaces

Walmart, Target, Amazon and Home Depot: purchase orders in, acknowledgments, ASNs and invoices out, checked against each partner’s rules before they go.

Brass valves and pipe fittings

Industrial and MRO

Grainger, Fastenal, MSC and Ferguson: the same documents at full catalog depth, with customer part numbers matched to your NetSuite items.

Semi-trailers backed up to warehouse loading docks

Suppliers asking for EDI POs

Send EDI 850s straight from NetSuite Purchase Orders. Supplier acknowledgments, ASNs and invoices come back onto the PO, as Inbound Shipments and as Vendor Bills.

How the integration works

Built into NetSuite, not bolted on with file drops

A NetSuite EDI connector in your account

One RESTlet script that we install and keep updated in your NetSuite account: no SuiteApp to buy, no CSV imports, no file drops. It creates and reads records through NetSuite’s own record and SuiteQL APIs.

Token-based authentication

Every call is signed with OAuth 1.0 token-based authentication (HMAC-SHA256), using a role you control. Revoke the token and access stops.

Duplicates are skipped

Each imported document carries its EDI ID. A resent order, ASN or invoice is skipped rather than posted twice, and a supplier invoice number that is already billed is caught.

Supplier ASNs as Inbound Shipments

Supplier ASNs create Inbound Shipments with status In Transit, so stock is received when it arrives, not when the ASN does. Item Receipts are an option.

Items match the way partners send them

By SKU, by UPC/GTIN, or by the customer’s own part number through NetSuite’s Supply Chain Management SuiteApp.

Original line numbers go back

Acknowledgments, ASNs and invoices return the customer’s original PO line numbers, even after NetSuite renumbers the lines.

Locations

Ship-from location per order or per line, and inventory by location for 846 feeds to customers.

Sandbox first

Sandbox and production are separate connections. Every new partner is proven in your sandbox before it touches production.

Monitored by engineers

Missing acknowledgments, unconfirmed orders and absent ASNs open a ticket with our team, usually before your customer notices.

Who does what

Managed EDI: what we run, and what your team does

Some providers sell software and leave the maps, partner testing and monitoring to you. With Comparatio, those are our job. Your team owns the NetSuite side.

Operations team working at computer monitors
Division of work between Comparatio and the customer's team
TaskComparatioYour team
Trading-partner mapsBuilds every map and changes it when a partner’s requirements changeForwards partner notices if they reach you first
Partner testingRuns the test cycle with each trading partnerChecks that test orders look right in your NetSuite sandbox
ConnectionsSets up and maintains AS2, SFTP and VAN connections and certificatesNothing
MonitoringWatches for missing orders, acknowledgments and ASNs, and opens the ticketMakes the business call when one is needed
NetSuite connectionInstalls and updates the RESTlet and runs the setup checkCreates the integration role, token and custom fields from our list
Items and partnersMaps partner item numbers, UPCs and customer part numbersKeeps NetSuite item, customer and vendor records current
Business rulesConfigures them in the integrationDecides them: order status on import, bills before receipt, which POs go out by EDI

Setup checklist

NetSuite permissions the integration needs

Missing permissions are the most common cause of a slow NetSuite go-live, because NetSuite reports them one error at a time. Grant these up front. Our setup check then reads your account and lists anything still missing in one pass.

NetSuite role permissions, features and custom fields needed for EDI
AreaWhat to grantNeeded for
Integration accessAn integration record, a role for the EDI user and an access token. The RESTlet deployment’s audience must include that role and subsidiary.Signs in Comparatio’s calls
Lists: ViewItems, Customers, Vendors, Locations, Bins, Units, Accounting Lists, Documents and FilesItem and partner lookups, and scripts on your records
Selling: transactionsFind Transaction (View), Sales Order (Full), Item Fulfillment, Invoice and Credit Memo (View)Customer orders in; acknowledgments, ASNs and invoices out
Buying: transactionsPurchase Order (Edit), Inbound Shipment (Full) or Item Receipt (Create), Bills (Create)POs out; supplier acknowledgments, ASNs and invoices in
FeaturesInbound Shipment ManagementSupplier ASNs as Inbound Shipments
Custom fieldsAbout ten EDI fields on purchase orders and order lines: acknowledgment status, date, quantity and price, vendor confirmation number, original EDI line number, 850 sent dateShows acknowledgment results where buyers work
Customer part numbers (optional)Supply Chain Management SuiteApp: Enable Customer Part Number, plus access to the Customer Part Number recordOrders that carry the customer’s own part numbers

If your account runs its own scripts or workflows on these records, the role also needs whatever those scripts use. We send the exact custom-field list during setup.

How it works

How to set up EDI in NetSuite, from sandbox to live

  1. 1

    Connect

    We install the RESTlet in your NetSuite sandbox. Your admin grants the role and token from our checklist, and our setup check confirms nothing is missing.

  2. 2

    Map and test

    We map each trading partner and run real test documents through your sandbox: orders in, acknowledgments, ASNs and invoices out, supplier documents in.

  3. 3

    Go live

    Partners move to production one at a time, or together on a planned cutover date with a rollback ready. We watch every document from day one.

FAQ

NetSuite EDI questions, answered

Does NetSuite support EDI?

Not on its own. NetSuite has no built-in EDI translator or trading-partner connections, so it is not an EDI system by itself. You need an EDI provider to translate X12 documents, connect to each trading partner and post the data into NetSuite records. Comparatio does all three, through a RESTlet in your NetSuite account.

How do you set up EDI in NetSuite?

In three steps. We install the RESTlet in your NetSuite sandbox, and your admin grants the role, token and custom fields from our checklist. We map each trading partner and run test documents through the sandbox. Then partners move to production, one at a time or all at once.

Which EDI documents post into NetSuite?

Customer purchase orders (EDI 850) become Sales Orders. Supplier acknowledgments (855) update the Purchase Order, supplier ASNs (856) create Inbound Shipments or Item Receipts, and supplier invoices (810) create Vendor Bills. Order acknowledgments, ASNs, invoices, inventory advice and purchase orders go out from the matching NetSuite records.

Our suppliers want EDI purchase orders from NetSuite. Can you send them?

Yes. Purchase orders go to suppliers as EDI 850s straight from the NetSuite Purchase Order. Their 855 acknowledgments update the PO, their 856 ASNs create Inbound Shipments, and their 810 invoices create Vendor Bills. An invoice number that has already been billed is skipped, not posted twice.

Read the NetSuite supplier EDI guide

Do supplier ASNs receive stock automatically?

Not by default. A supplier ASN creates an Inbound Shipment with status In Transit, so stock is received when it actually arrives. If you prefer, ASNs can create Item Receipts instead.

Can NetSuite import PDF purchase orders and supplier invoices?

Yes, with Comparatio’s PDF Import: in production on Prophet 21; available for CloudSuite Distribution and NetSuite. Customers and suppliers who will never do EDI keep sending PDFs: purchase orders become Sales Orders, and supplier invoices that reference a PO become Vendor Bills, alongside your EDI traffic. Bills without a PO, such as carrier bills, are flagged for your team to enter. There are no per-vendor templates to build.

How do we avoid retail EDI chargebacks?

Most chargebacks come from ASNs that are late, missing or don’t match the shipment. Comparatio checks every outbound X12 document against your partners’ rules and reports the result, and a failing document can be held, per partner. Our monitoring flags an order with no ASN before the partner’s deadline.

Managed or self-service EDI for NetSuite: which is Comparatio?

Managed. Our engineers build and change the maps, test with each trading partner, maintain the connections and watch every document. Self-service platforms give you the software and leave that work to your team. With Comparatio, your team handles only the NetSuite side: the integration role, token and custom fields, from a checklist we send.

What should we look for in a NetSuite EDI provider?

Ask five things. Who changes the maps when a trading partner’s requirements change? Do supplier documents post into NetSuite, or only customer orders? Which NetSuite record does each document create? How is a new partner tested before production? And what do you pay per document, per partner and per change?

How much does NetSuite EDI cost?

It depends on how many trading partners and documents you run. Comparatio quotes a subscription and a one-time setup after a short discussion, so you know the total before you start. Maps for partners you add later, and map changes, are professional services.

How Comparatio prices managed EDI

How long does it take to implement EDI with NetSuite?

It depends on where you start. Connecting NetSuite takes days to weeks, depending mostly on how quickly the role, token and custom fields are in place, and each new trading partner typically goes live in 4–8 weeks, paced by how quickly the partner tests. Moving an existing EDI program from another ERP takes a few months: NetSuite runs side by side with your current ERP, the acknowledgments, ship notices and invoices built from NetSuite are compared with the ones the old ERP produced before anything switches, and the switch happens on a planned cutover date with a rollback ready.

Changing ERPs? Your EDI moves with you

What NetSuite permissions does the integration need?

View access to items, customers, vendors, locations and a few other lists. Full access to Sales Orders, Edit on Purchase Orders, and Create on Bills and Item Receipts or Inbound Shipments. Plus Inbound Shipment Management and about ten custom fields. Our setup check reports anything missing in one pass.

Do we need a NetSuite SuiteApp for EDI?

No. Comparatio installs one RESTlet script in your NetSuite account and keeps it updated. There is no SuiteApp to buy or license.

How does Comparatio sign in to NetSuite?

With OAuth 1.0 token-based authentication: every request is signed with HMAC-SHA256 using a token tied to a role you control. Revoke the token and access stops.

Where does Comparatio EDI run?

Comparatio runs on your server or on one we host for you. Documents travel over the connection each trading partner uses. AI features send the document, or the question and the log lines and configuration rows needed to answer it, to Anthropic’s Claude; PDF Import does this under your own API key.

Can we connect to trading partners over AS2?

Yes. Comparatio runs the AS2, SFTP and VAN connections to your trading partners, including certificates and renewals. NetSuite itself only talks to the RESTlet.

Can we test before anything touches production?

Yes. Sandbox and production are separate connections. Each trading partner runs real test documents through your NetSuite sandbox first.

We are moving from Prophet 21 to NetSuite. Do our EDI partners start over?

No. Your trading-partner connections and maps stay with Comparatio; only the ERP side changes. P21 keeps trading while the acknowledgments, ship notices and invoices NetSuite builds are compared with the ones P21 produced, and partners switch on a planned cutover date, with a rollback ready. Plan on a few months from start to cutover.

Changing ERPs? Your EDI moves with you

Do you handle drop-ship orders?

Yes for customer orders: the end customer’s ship-to address lands on the Sales Order. Purchase orders to suppliers carry the ship-to from the NetSuite PO. Tell us how your drop-ship flow works and we will confirm the setup.

Talk through your NetSuite EDI before you commit

Bring a sample 850 from a customer and an 856 from a supplier, and we’ll talk through where each one lands in NetSuite.