Also called the P2P cycle, Procure-To-Pay is how your business receives, processes, manages, and completes orders. It begins from the time an order takes place and includes each step of the delivery and payment process. In this case, NetSuite represents our backend.
This particular Accelerator contains prebuilt Schemas, Rulesets, Business Processes, and other resources used for development, deployment/execution, and testing. This includes mapping tools specific to several business flows as part of this Accelerator. Finally, there are also resources necessary to display data on several Cockpit monitoring pages.
Supported Integration Flows
The project is designed to process requisitioning and purchasing of goods and services. The following steps are included in the X12 P2P <> NetSuite Accelerator:
- Purchase Order from ERP to Trading Partner (X12 850)
- Order Acknowledgement from Trading Partner to ERP (X12 855)
- ASN from Trading Partner to ERP (X12 856)
- Invoice from Trading Partner to ERP (X12 810)
- Customer payment from ERP to Trading Partner(X12 820)
All the flows will have corresponding 997s generated and sent/received and reconciled.
Outbound EDI documents are created as per the EDI standard (Outbound EDI is validated for syntactical errors).
Pre-built Integration Flows: The project is designed to process requisitioning and purchasing of goods and services. The following steps are included in X12 P2P <> NetSuite Accelerator:
- Purchase orders in NetSuite are processed and corresponding X12 850s are sent to trading partners.
- Once the Orders/Items are Approved/ Canceled, Purchase Order Acknowledgement (X12 855) is used to trigger email alerts for customers.
- Inbound 856 ASN creates ‘Inbound shipment’ in NetSuite. Items are marked as received.
- Inbound 810 received from a trading partner creates ‘Vendor Bill’ in NetSuite.
- After billing, NetSuite is marked for payment, and the corresponding X12 820 is sent back to the trading partner.
For all flows the 997 acknowledgements have been set up.
- EDI 850 (Purchase Order): - Purchase Order is created in the ERP to procure goods and corresponding outbound X12 850 is sent to Trading Partners (Vendors). In the current phase of the accelerator, CIC receives Purchase Orders data from NetSuite in the form csv file and sends the corresponding Standard X12 850 to the trading Partner. The current Accelerator supports multiple location delivery mapping (SDQ segment creation based on location in Item Level).
- EDI 855 (Purchase Order Acknowledgement): Purchase Order Acknowledgements are received from trading partners (Vendors) to acknowledge the purchase orders. In the current phase of this Accelerator, CIC receives the Purchase Order Acknowledgement data in the form of an X12 file and creates the corresponding email body, and then generates an email to customers.
- EDI 856 (Inbound shipment): X12 856 ASNs are received from the Trading Partners (Vendors) to request shipment for goods. In the current phase of the accelerator, CIC receives shipment notice data in the form of an X12 file and creates the corresponding Inbound shipment in Netsuite. Supported hierarchies are: - SOPI, SOI, SOTI, SOIP
- EDI 810 (Vendor Bill): Vendor Bills are received from the Trading Partners (Vendors) to bill for purchase orders. In the current phase of the accelerator, CIC receives Vendor Bill invoice data in the form of an X12 file and creates the corresponding Standard Vendor Bill in Netsuite. Vendor Bill transaction is usually used to track all the payables as they come from Vendors.
- EDI 820 (Bill Payment): EDI 820 is also known as payment remittance normally sent in response to an EDI 810 Invoice or BILL. The bill is paid by the customer which creates a Bill Payment record in the Netsuite. In the current phase of the accelerator, CIC receives Bill payment in the form of csv from saved search execution and is sent to the trading partner in the form of X12 from CIC.
- Integration Design specification (IDs) Template: The document which explains the business rules that are applied while creating the inbound and outbound documents. The template helps in documenting any changes to the template integration as per your requirement.
- Multiple Trading Partner Onboarding: The design lets you onboard multiple Trading Partners at once using the Wizard.
- Email notification for unknown Trading Partner: If the Inbound/Outbound payloads are received where no matching configurations are found, then, an email notification will be generated.
EDI message validations:
- Duplicate Inbound messages The Accelerator has the logic to handle any duplicate EDI data that is retrieved from the Trading partner. If need be, this can be turned per partner or per doctype.
- Inbound/Outbound EDI Data validation: Accelerator is enabled to catch any invalid EDI syntaxes in both Inbound and Outbound flow. The execution will be stopped if there are any syntax errors. The settings can be changed to not stop execution as well.
- Error Handling and Ticket Creation: Accelerator ensures all the processing failures are logged as a ticket and marked as issues in the Cockpit.
Out-of-the-box Cockpit visibility: This accelerator is already enabled with the resources necessary to display data in several Cockpit monitoring pages.
- The Message Detail view (shown below) provides the life cycle of an Order untill the Payment order is generated
- The Accelerator is also enabled so that charts for monitoring various transactions are displayed.
- X12 Accelerator currently supports X12 EDI Version 4010 only.
- For Ship Notice (X12 856), SOPI structure, SOIP, SOTI, and SOI hierarchies are supported.
Detailed documentation is provided on the project structure and object-level details that are in the Accelerator. Please refer to the X12 P2P With NetSuite Accelerator Document provided in the Docs folder within the
There are several actions you may need to take that are described in these prerequisites, which include the configuration of:
- Projects and Packages
- Reference Tables
- Staging Database
- Global Variables