PROPOSAL SUMMARY
This proposal outlines the scope of Invoice integration between NetSuite and BlueScope, and the limitations and drawbacks of this integration.
REQUIREMENT
Studco team needs to integrate BlueScope with NetSuite for creating automated invoices(vendor bills) based on the data provided by the BlueScope team using an endpoint that we will be providing.
DELIVERBALES
We will be using Oauth 2.0 client credentials flow for the integration and for this need some prerequisites from the BlueScope team.
Also, we need to setup the following in the NetSuite as initial setup,
1. Integration Records.
2. Client Credentials (Machine to Machine) setup.
For this process, BlueScope team will be providing the Certificate Public Key from the BlueScope in PEM file format
The BlueScope team will be able to send data (invoice details) to the Restlet after we update the initial setup on our end.
Processing Bills in NetSuite
We will be creating a custom record for storing the details after receiving details from the BlueScope. Then the script will be triggered, and the vendor bill will be created.
After the bill is created, we will be attaching the bill in the custom record.
Custom record will be storing the error messages in case any error is generated.
PREREQUISITES
- We need to get the certificate from the BlueScope and this certificate need to be in PEM format
- We also need the invoice response/schema sample for the mapping processes.
ASSUMPTIONS
- We will be considering only the AU subsidiary.
- BlueScope team will be providing the certificate in PEM format.
- The certificate is valid for 1 year and certificate keys need to be updated every one year.
- We will be considering only single invoices for a single day and response body will be containing details of single invoice only.
- BlueScope team will be providing the Purchase Order reference and the line id reference of the item and vendor bill will be created based on it.
- We will be using the batch number for identifying the corresponding item in the NetSuite.
- JWT Token will be created, and endpoint will be called from the BlueScope integration team.
- We will consider the vendor will always be same and the vendor is BlueScope Distribution Pty Ltd-Sheet Metal Supplies.
- If there is any item in multiple lines, we will create the same in the vendor bills.
- If the coil is consumed and BlueScope has not included it in their invoice, vendor bill will not be created for that, since the bill is prepared using the data that BlueScope sends us.
- Quantity check or weight check will need to be performed while creating a vendor bill. If the total from BlueScope and the total from Bill is not matching, a variance will be added based on that.
- If a variance occurred, will be adding another line to the bill with the variance number and bill will be generated.
- We will be considering the Melbourne location.
- We will confirm the mapping with the Studco team once the BlueScope team sends the data from the test environment.