NetSuite Rest API
This outlines the information and steps that are needed to familiarise oneself with, before and during the implementation of the NetSuite Rest API interface in Back Office.
The content is targeted at Resellers and swiftpos Venue Administrators who have a sound knowledge of and experience with swiftpos. For further information or assistance, please contact your swiftpos Reseller or swiftpos Support.
Start HERE ▼
What To Consider? ▲ ▼
- The NetSuite Rest API interface is Location Group (Venue) specific. Each Location Group (Venue) that needs to interface with NetSuite will need to be configured. Refer HERE for more information.
- The swiftpos End of Day Service supports the NetSuite Rest API interface. Refer HERE for more information.
- Sales data is consolidated daily by location and posted as a journal. This is a balanced journal entry and includes consolidated movements for Income, Media, Cost of Goods, Stock Movements (including, stocktake, stock adjustments, stock transfers) and Stock on Hand.
Unlike other swiftpos Financial exports (such as Xero and MYOB), this export supports the exporting of transactions tagged with a swiftpos Event. This means rows in the export will be split by the Event they are tagged to. - Venues may need to enlist the services of an Accountant to ensure that their Chart of Accounts (COA) in NetSuite, is setup up and configured appropriately to support the swiftpos NetSuite Rest API interface.
- Field Mapping
- Screens
Field Mapping ▲ ▼
The mapping of NetSuite to swiftpos fields is outlined below for:
|
JOURNAL |
|
|
NetSuite |
swiftpos |
|
approvalStatus |
Location Group |
|
currency |
Location Group (Same value for both JournalEntry and VendorBill/VendorCredit) |
|
custbody_ktsp_system_name |
Location Group Can define BOTH the “custom field name” and its “value”. (Same value for both JournalEntry and VendorBill/VendorCredit) |
|
customForm |
Location Group |
|
memo |
Location |
|
exchangeRate |
Location Group |
|
reversalDefer |
hard coded (false) |
|
subsidiary |
Location |
|
tranDate |
EJTable |
|
line: { |
|
|
items: [ |
|
|
{ |
|
|
account |
Location AND Master Group or Media |
|
class |
For sales tagged with an Event: EJTable connected EventDetailExternalID, then EventExternalId
For sales NOT tagged with an Event: Location Group default (defined specifically for JournalEntry) |
|
cleared |
hard coded (false) |
|
credit/debit |
EItemsJtable OR EJMediaTable consolidated |
|
department |
Location (Same value for both JournalEntry and VendorBill/VendorCredit) |
|
location |
Location (Same value for both JournalEntry and VendorBill/VendorCredit) |
|
memo |
Location AND Master Group or Media |
|
}, |
|
|
SUPPLIER INVOICE (Vendor Bill/Credit) |
|
|
NetSuite |
swiftpos |
|
entity |
Supplier record: Id |
|
account |
Supplier record then Location Group default |
|
currency |
Location Group (Same value for both JournalEntry and VendorBill/VendorCredit) |
|
trandate |
Invoice record |
|
duedate |
N/a - NOT SENT |
|
memo |
Invoice record |
|
custbody_ktsp_system_name |
Location Group Can define BOTH the “custom field name” and its “value”. (Same value for both JournalEntry and VendorBill/VendorCredit) |
|
department |
Location (Same value for both JournalEntry and VendorBill/VendorCredit) |
|
location |
Location (Same value for both JournalEntry and VendorBill/VendorCredit) |
|
class |
Location Group (defined specifically for VendorBill/VendorCredit) |
|
expense: { |
|
|
items: [ |
|
|
{ |
|
|
account |
Location AND Master Group |
|
amount |
Invoice record |
|
location |
Location - same as header level (Same value for both JournalEntry and VendorBill/VendorCredit) |
|
class |
Location Group (Vendor Bill specific) - same as header level |
|
department |
Location - same as header level (Same value for both JournalEntry and VendorBill/VendorCredit) |
|
}, |
|
Steps To Follow ▲ ▼
IMPORTANT
It is highly recommended that the setup and configuration of swiftpos NetSuite Rest API interface is done in Test environments initially. That is, test environments for both swiftpos and NetSuite.
For Venues that are contemplating using NetSuite for the first time and are wanting to make use of swiftpos NetSuite Rest API Interface, ensure the following is addressed:
- Confirm the Venue has a NetSuite Registration. That is, registered to use NetSuite Financials. That is, they will need to have a NetSuite Account.
- Confirm the Venue has configured a Chart of Accounts (COA) in NetSuite. Venues will need to configure Accounts in NetSuite appropriate to the Venue's requirements and to ensure that Accounts are available to the swiftpos NetSuite Rest API interface, for the purposes of account assigning/mapping. Refer HERE for more information.
- Confirm the Venue has a swiftpos Registration. That is, the Venue will need to have a licence for the swiftpos NetSuite Rest API GL interface in order to access this feature. Email registrations@swiftpos.com.au to request a registration to include this licence.
- Import the Chart of Accounts (COA). Refer HERE for more information.
- Assign/Map the Accounts. Refer HERE for more information.
- Mark All As Exported. This may need to be considered when exporting for the first time. Marking all as exported will ensure that all current data will be marked as exported. Hence, providing a Venue with the option of NOT exporting historical data and thus providing a starting point for the first export. Refer HERE for more information.
- Reset Trading Dates. This allows Venue's to mark data for a selected Trading Date as NOT exported. Thus, allowing the data to be re-exported in a future Export. Refer HERE for more information.
- Export Data. Depending on the Venue's preferences, General Journal and Supplier Invoice related data can be exported as follows:
- Manually - This is achieved by using the Export screen to export data for specific Trading Dates manually. Refer HERE for more information.
- Automatically - This is achieved by configuring the swiftpos End of Day process and ensuring the NetSuite Rest API is enabled in the End Of Day Options screen. Refer HERE for more information.
End of article. ▲