The order-to-cash process spans from placing an order until the business receives payment. This process encompasses order management, fulfillment, credit management, invoicing, and payment collection.
EDI is a platform that modernizes traditional B2B EDI data integrations by providing a standardized REST/JSON API endpoint for EDI transactions. It helps suppliers sell products wholesale. When these wholesalers (trading partners) create purchase orders, EDI converts the EDI X12/EDIFACT format to a JSON canonical structure and integrates it with NetSuite.
The NetSuite - EDI for B2B Manager template facilitates the exchange of purchase orders (850), purchase order change requests (860), invoices (810), purchase order acknowledgments (855), advance ship notices (856), and functional acknowledgments (997) between EDI trading partners and NetSuite. A B2B Manager subscription is required to use this template.
-
Optimize customer experience with timely sync of data.
-
Take control of your integrations with tools that let you configure and allow you to make mapping changes on the fly.
-
Efficiently scale operations by automating processes that rely on trading partners and NetSuite platforms.
-
Reduce maintenance time with a dashboard for sophisticated error handling and integration support provided by Celigo.
-
A Sales Manager of an eCommerce manufacturer/supplier:
-
wants the purchase orders placed by the Retailer to sync into NetSuite to approve the orders and pass along approved orders to downstream teams/departments for fulfillment and invoicing.
-
when a specific purchase order that is split as multiple sales orders in NetSuite is part of EDI860 should be able to see the rightly updated/newly created/deleted equivalent sales orders in NetSuite.
-
-
A Warehouse Manager of an eCommerce manufacturer/supplier wants shipped orders in NetSuite to sync directly to the trading partner source platform as order fulfillment completion.
-
An Account Receivables (AR) analyst of an eCommerce manufacturer/supplier wants invoices created in NetSuite against successfully shipped orders to sync directly to the EDI Source system and notified of the payment and records are closed.
-
A Sales Manager/Warehouse Manager of a manufacturing company wants to send the Purchase Order acknowledgements from NetSuite against the Purchase Orders created directly in the source system.
The Celigo bundle contains workflows you can easily configure and deploy without coding or IT support. The following built-in flows sync from the specified source data to the corresponding destination.
-
Purchase orders (850) to NetSuite sales orders (add): Generates the purchase orders (EDI transaction 850) from the trading partner source to NetSuite as sales orders.
-
Purchase order change requests (860) to NetSuite sales orders (update): Generates purchase order change requests (EDI transaction 860) from the trading partner source and updates the NetSuite sales orders.
-
NetSuite invoices to invoices (810): Generates the invoice from NetSuite as an invoice (EDI transaction 810) to the trading partner source. This is a once-exported scheduled flow. Before the invoice is generated, be sure to sync the sales order.
-
NetSuite sales orders to purchase order acknowledgments (855) (add): Generates the purchase order acknowledgments based on the NetSuite sales order status as purchase order acknowledgments (EDI transaction 855) to the trading partner source. This scheduled flow picks the sales orders created since the last flow run.
-
NetSuite item fulfillments to advanced ship notices (856): Generates the item fulfillment from NetSuite as advanced ship notice (EDI transaction 856) to the trading partner source. The scheduled flow generates only the fulfillment records with the status as Shipped in NetSuite. This is a once-exported scheduled flow. Before you generate the fulfillment, make sure to sync the sales order.
-
Generate functional acknowledgements (997): Generates the functional acknowledgements in integrator.io and sends them to the trading partner source as functional acknowledgements (EDI transaction 997). A functional acknowledgment is generated on a successful run of the Purchase orders (850) to NetSuite sales orders (add) and Purchase order change requests (860) to NetSuite sales orders (update) flows.
Most integrator.io error messages clearly explain the error and suggest troubleshooting methods. If you need clarification on what the error means, contact Celigo support. See the endpoint documentation for errors passed through from NetSuite or trading partners.
Comments
0 comments
Article is closed for comments.