NetSuite: Supported fields
The NetSuite integration supports these fields:
Tungsten AP Essentials | NetSuite field | Note |
---|---|---|
Header fields | ||
Supplier | vendor | |
InvoiceNumber | tranId | |
InvoiceOrderNumber | n/a | If InvoiceOrderNumber is set on the invoice, the NetSuite vendor bill is initialized from the purchase order. |
InvoiceDate | tranDate | |
InvoiceDueDate | dueDate | |
InvoiceCurrency | currency | |
Customer | customer |
In NetSuite, there is only one field for customer and project data. Therefore, the customer and project fields in Tungsten AP Essentials map to the same "customer" field in NetSuite. In a real-life scenario, organizations that use NetSuite probably have their system configured to use one field or the other. If, however, both fields are used, Tungsten AP Essentials makes sure the project belongs to the customer in NetSuite. |
Project | customer | See the note for the "customer" field above. |
location | location | |
Department | department | |
Class | class | |
Memo | memo | |
TaxCode | taxCode | |
Line-item fields | ||
LIT_ArticleIdentifier | item | Alternatively, this can be a Dummy item code if LIT_ArticleIdentifier is empty or an invalid item in NetSuite |
LIT_DeliveredQuantity | quantity | If the value is less than or equal to zero, it is set to 1. |
LIT_UnitPriceAmount | rate | If the value is less than or equal to zero, it is set to the LIT_VatExcludedAmount value. |
LIT_ArticleName | description | LIT_ArticleName is used for item descriptions for PO and non-PO invoices. If LIT_ArticleName is not specified during verification, the suggested value from NetSuite is used when the invoice is posted. |
LIT_VatExcludedAmount | amount | If the invoice has no line items, a row is created using InvoiceTotalVatExcludedAmount. |
LIT_Location | location | |
LIT_Department | department | |
LIT_Class | class | |
LI_TaxCode | taxCode | |
LIT_Customer | customer | See the note for the "customer" field above. |
LIT_Project | customer | See the note for the "customer" field above. |
Line-item expense fields | ||
LIT_GeneralLedgerAccount | account |
Optionally, if you use account coding, the account code you specify is used. Otherwise, the value is determined by the supplier or by the Target system configuration settings if it cannot be determined by the supplier. |
LIT_VatExcludedAmount | amount | If the invoice has no line items, a row is created using InvoiceTotalVatExcludedAmount. |
LIT_Location | location | |
LIT_Department | department | |
LIT_Class | class | |
LIT_Memo or LIT_ArticleName | memo | If LIT_Memo is defined and has a value, it is used. Otherwise, the value from LIT_ArticleName is used. |
LI_TaxCode | taxCode | |
LIT_Customer | customer |
In NetSuite, there is only one field for customer and project data. Therefore, the customer and project fields in Tungsten AP Essentials map to the same "customer" field in NetSuite. In a real-life scenario, organizations that use NetSuite probably have their system configured to use one field or the other. If, however, both fields are used, Tungsten AP Essentials makes sure the project belongs to the customer in NetSuite. |
LIT_Project | customer |
In NetSuite, there is only one field for customer and project data. Therefore, the customer and project fields in Tungsten AP Essentials map to the same "customer" field in NetSuite. In a real-life scenario, organizations that use NetSuite probably have their system configured to use one field or the other. If, however, both fields are used, Tungsten AP Essentials makes sure the project belongs to the customer in NetSuite. |