Negative Charge Mapping Group
Use the Negative Charge mapping group to map information about charges on credit (negative invoice) records in OpenAir with information about credit memos applied to invoice transaction records in NetSuite.
For reference information and best practice guidelines, review the following topics:
-
References — Overview of record types in OpenAir and NetSuite with links to the relevant reference material for information about fields available for mapping.
-
Default Field Mappings — Overview of default field mapping definitions including notes and best practice guidelines where relevant. Information imported by default includes credit memo number, date, amount, internal ID of the associated customer, service, product and project in OpenAir, charge type, time and rate or quantity and cost, and currency.
-
Additional Field Mappings — There are no specific guidelines for custom field mapping definitions in this mapping group.
References
The following table gives reference information about the records and fields available for custom field mapping definition with links to the relevant reference material. See also Schema Reference Documentation.
NetSuite Record type [ |
OpenAir Record Type [ |
Mapping Group [ |
---|---|---|
Credit Memo [ Schema: CreditMemoItem (2020.1)|CreditMemoItem (2023.1) XSD: |
Charge [ Data Dictionary: slip |
Negative Charge [ |
Default Field Mappings
The following table describes the default field mapping definitions for the Negative Charge mapping group tab.
NetSuite Field |
D |
OpenAir Field |
Notes |
---|---|---|---|
|
![]() |
|
The credit memo Date in NetSuite |
|
![]() |
|
The negative Total value of the charge in OpenAir corresponds to the positive Amount on the corresponding credit memo line item. |
|
![]() |
|
By default, the Credit # of the credit memo in NetSuite is recorded in the Notes field on the charge record in OpenAir. |
Looked up OpenAir field value — |
![]() |
|
The internal ID of the invoice associated with the charge in OpenAir. |
Looked up OpenAir field value — |
![]() |
|
The internal ID of the customer associated with the charge in OpenAir. |
Looked up OpenAir field value — |
![]() |
|
The internal ID of the service associated with the charge in OpenAir. |
Looked up OpenAir field value — |
![]() |
|
Active and visible only if the POs (Vendor Bills) import workflow is enabled. The internal ID of the product associated with the charge in OpenAir. |
Looked up OpenAir field value — |
![]() |
|
The internal ID of the project associated with the charge in OpenAir. |
|
![]() |
|
Active and visible only if the Multicurrency feature is enabled for your OpenAir account. The Currency on the charge record in OpenAir is set to the Currency on the credit memo transaction record in NetSuite. |
|
![]() |
|
[Initial Only] If the Map the charge type from the NetSuite credit memo box is checked on the Credits (Applied Credit Memos) import workflow settings form, the OpenAir: Charge Type [ Otherwise, the charge type is set to
Note:
The OpenAir: Charge Type [ |
Looked up OpenAir field value — |
![]() |
|
— |
Calculated number of hours based on |
![]() |
|
— |
Calculated number of minutes based on |
![]() |
|
— |
Calculated rate based on |
![]() |
|
— |
|
![]() |
|
— |
|
![]() |
|
— |
If the Charge type is
|
![]() |
|
— |
|
![]() |
|
Not visible in mapping definition table [Initial Only] OpenAir stores the internal ID of the credit memo in the NetSuite Credit Memo ID [ |
|
![]() |
|
Not visible in mapping definition table [Initial Only] OpenAir stores the line ID of the credit memo item in the NetSuite Credit Memo Line ID [ |
Additional Field Mappings
Review the following guidelines
-
You should contact your OpenAir Professional Services representative if you need to make changes to your integration configuration and field mapping definitions.
-
For advanced mapping usage and best practice guidelines, see Advanced Field Mapping Definition.
-
Familiarize yourself with the NetSuite and OpenAir technical documentation before attempting to set field mapping definitions using the advanced notation — See Schema Reference Documentation.
No specific guidelines