- Preparing mapping on our Bill Sync for NetSuite
- Requires a LaunchDarkly flag to be enabled
Before you begin:
Before taking any actions from this article, please ensure you understand how NetSuite expects data to be formatted in Procurify.
Defining data mapping:
Once connected, you can define data mapping; choosing how Procurify Fields link to NetSuite Fields when syncing a bill.
There are three existing levels for this mapping:
- Default field mapping
- Custom field mapping
- Advanced field mapping
Default field mapping
The default fields section is minimized by default as this information cannot be modified. You can click on the arrow next to the title to show these fields. They are as visible in this screenshot:
Custom field mapping
This section contains five frequently used standard NetSuite fields with dropdown menus allowing you to select standard or custom Procurify fields to choose from.
Click Edit to make selections from the dropdown menus.
- The choices will list all active AND inactive fields in titled sections.
- Selecting an Inactive field will display: “This is a disabled custom field”.
- Any selections you no longer need can be cleared by clicking the X at the right of the selection box as seen below.
The “Select a source” message is displayed for NetSuite fields that are not mapped.
Please note that each Bill can only be assigned to a single NetSuite Subsidiary and that only the value for the first line item on the bill will be used for this NetSuite field.
Advanced custom field mapping
Advanced custom field mapping enables any data from Procurify to be mapped to any non-standard NetSuite field on your NetSuite Bill form. Fields can be created and assigned to the Bill form in NetSuite. You will need to identify the NetSuite Field ID values to point to the correct field. This value would be entered in the NetSuite Fields box for each field you want to map.
You can get these names in NetSuite by:
- Navigating to Customization → Lists →Records, & Fields
- Click Transaction Body Fields (for header fields) or Transaction Line Fields (for line fields).
The value required would be in the ID column from these lists. Note that you may require your NetSuite Administrator to get access to this.
For example, to map a custom date field from Procurify (as selected in the Procurify Fields dropdown box) to Controller Approval Date, enter custbody_powf_ctrl_dt in the NetSuite Fields box.
Best practice: Matching field Type in both Procurify and NetSuite and ensure any values coming from Procurify is a valid selection for the mapped field in NetSuite. Otherwise bill sync may fail. If mapping to a List type field fails to populate the information correctly, please refer to this article.