NetSuite EDI integration
Weredi connects EDI to Oracle NetSuite through the SuiteTalk REST API, authorized with your own NetSuite integration record. A retailer’s 850 becomes a NetSuite invoice, a supplier’s 810 a vendor bill, an 820 a customer payment applied to its invoices, and the 810s and 820s you send are recorded as invoices and vendor payments. Sending a document again updates its record instead of duplicating it.
The trial includes the NetSuite connector. No credit card.
What syncs with Oracle NetSuite
Five flows, each one a NetSuite transaction record created through SuiteTalk REST. Today a purchase order (850) creates an invoice, not a sales order.
| EDI document | From | Becomes in NetSuite | What happens |
|---|---|---|---|
| 850 Purchase Order | Your trading partner | Invoice | The retailer’s order becomes an invoice on that customer, with the PO number in Other Ref. No., and an item, quantity and rate per line. |
| 810 Invoice | Your trading partner | Vendor bill | A supplier’s EDI invoice becomes a vendor bill on that vendor. |
| 820 Payment Order/Remittance Advice | Your trading partner | Customer payment | A customer’s remittance becomes a customer payment applied to the invoices it lists, never more than what is due on each. |
| 810 Invoice | You | Invoice | The EDI invoice you send is recorded as a NetSuite invoice, so receivables match what the retailer received. |
| 820 Payment Order/Remittance Advice | You | Vendor payment | A payment you send by EDI becomes a vendor payment applied to that vendor’s bills. |
You turn each flow on separately, per partner. Each push is logged as its own delivery with NetSuite’s answer, and a refused one can be sent again from the same screen.
Beyond the 850, 810 and 820
Any EDI document, mapped to any NetSuite field
The 5 flows above work out of the box. Every other document your partners exchange can reach NetSuite too: map its fields to the ones you need, and Weredi posts the result to NetSuite’s API, or to any system around it, the moment the document arrives.
Prefer not to build it? Our team sets up the mapping and the webhook for you.
Pick the documents
An automation listens for any transaction set, from any partner or only the ones you choose, inbound or outbound.
Map element to field
The mapping editor turns X12 elements into the exact JSON your target expects, with lookup tables for codes and item numbers.
BCH-03otherRefNumPOC-03item.quantityDeliver by webhook or API
A webhook posts it as JSON, XML or a form, signed with a bearer token, basic auth, an API key, HMAC or OAuth, and retried if the endpoint is down. Going the other way, your system sends documents out through the Weredi REST API.
How to connect EDI to Oracle NetSuite
Connect NetSuite
Enter your NetSuite account ID and the Client ID and secret of an integration record you create, then authorize with OAuth 2.0. Sandbox accounts work too.
Match your partners
Link each trading partner to its customer and vendor in NetSuite, once. Every document from that partner then lands on the right account.
Review the mapping
Each document starts from a reference mapping. Pick accounts, taxes and items from lists read live from NetSuite; translate item numbers with lookup tables.
Turn on the flows
From then on, each document is pushed to NetSuite the moment it arrives or is sent. Errors come back in NetSuite’s own words.
What is specific to NetSuite
NetSuite is the most configurable system in the family. The connector reads how your account is set up instead of assuming.
No duplicates on re-send
Each invoice and bill is written by external ID, built from its EDI document number. Sending the same document again updates the record NetSuite already has.
OneWorld and SuiteTax
On OneWorld accounts the subsidiary is picked from your list; otherwise it is left to NetSuite. Tax goes in SuiteTax tax details or in legacy tax codes, depending on your account.
Your account, your integration record
There is no shared Weredi app inside your NetSuite. You create the integration record, keep its keys, and can revoke it at any time; tokens are held per account.
Source files stay in Weredi
The REST API cannot upload to the File Cabinet, so the original EDI file is not attached in NetSuite yet. It stays on the delivery in Weredi, one click from the record.
What you need
- A Weredi Plus plan or the 14-day trial: integrations are part of Plus.
- REST Web Services and OAuth 2.0 turned on in your account’s SuiteCloud features.
- An integration record (Client ID and secret), your account ID, and a role allowed to create these transactions.
- Items in NetSuite for what you sell: every NetSuite invoice line needs one.
What Weredi handles on the EDI side
- The connection to each trading partner: AS2, SFTP or FTPS (with PGP), or a VAN mailbox.
- 997 functional acknowledgments, sent and reconciled.
- Validation of every document against the partner’s own guide before it leaves.
- The 855, 856 (with SSCC labels) and 810 built from the partner’s 850, ready to send.
- A record of every push to NetSuite: what was sent, what NetSuite answered, and a retry button.
Weredi Plus
The Oracle NetSuite integration is in Weredi Plus
One flat price: unlimited trading partners and transactions, all six ERP connectors, mappings, lookup tables, automations and the REST API. Try it free for 14 days with your own partners.
Oracle NetSuite EDI questions
Does NetSuite support EDI natively?
NetSuite does not translate X12 documents on its own. EDI reaches it through a provider: Weredi translates each document, writes it through the SuiteTalk REST API and exchanges the files with your trading partners.
Does the 850 create a sales order in NetSuite?
Not today: a purchase order creates a NetSuite invoice on the matched customer. Other records, a sales order included, can be reached through a mapped webhook to the SuiteTalk REST API; our team can set it up.
What do I need on the NetSuite side?
REST Web Services and OAuth 2.0 turned on, an integration record with its Client ID and secret, your account ID, and items for what you sell. OneWorld and SuiteTax accounts are supported, sandboxes too.
Which EDI documents does it cover?
Out of the box: purchase orders (850) in, invoices (810) in and out, and payments (820) in and out. Any other EDI document can be mapped field by field and sent to NetSuite or any other system through mapped webhooks and the Weredi REST API.
How much does the NetSuite integration cost?
It is part of Weredi Plus, $999 CAD a month at a flat price with unlimited trading partners and transactions. The 14-day free trial includes it, with no credit card.
Other ERP integrations
The same EDI side, connected to a different system.
QuickBooks Online
Purchase orders become invoices, supplier EDI becomes bills, remittances become payments.
QuickBooks Online integration →
SAP S/4HANANew
Sales orders, supplier invoices, billing documents and payment advices through SAP’s APIs.
SAP S/4HANA integration →
Xero
Sales invoices, bills and payments from EDI, in the Xero organisation you choose.
Xero integration →
Sage Accounting
Sales and purchase invoices, receipts and payments from EDI, with Canadian tax regions.
Sage Accounting integration →
OdooNew
Confirmed sales orders, vendor bills and registered payments, on Odoo 17 to 20.
Odoo integration →Running something else?
Every other system connects through the Weredi REST API and webhooks. If you would rather not build it, our team will.
See all integrations →
Speak to an EDI expert today
Connect with one of our experienced EDI experts to learn how Weredi’s Modern EDI Platform can handle your company’s EDI needs.