Docs

Log in to read the version of docs relevant to your site, or use the dropdown versions

Objects and fields mapped between Chargebee and NetSuite

This page helps you understand the objects and field mapping that is done between Chargebee and NetSuite.

Customer

Note

Source Entity - Chargebee Customer

Supported Actions - Create, Update

Unsupported Actions - Delete, Void.

The following table provides information on the customer object fields mapped between Chargebee and NetSuite:

NetSuite Target Field,Chargebee Source Field,Additional information,
entityIdid

A prefix is added if this field is configured. For example, If the prefix is CB-Customer and the customer id in Chargebee is 100 then the prefix will be synced as CB-Customer-100. If you have checked the Allow Override option in NetSuite, then Chargebee's identifiers will be set as the primary ID for Invoices, Credit Memos, Customers, and so on. If Allow Override is not set in NetSuite, then the value we've set in Chargebee will be ignored.

external IdidA prefix is added if this field is configured.
companynamecompany or DefaultCompanyNameIf isperson is set false, this field is not applicable
customFieldList

Mapped as per the backend configuration made, else not applicable.

currencypreferredCurrencyCode

NetSuite Reference (The reference value from NetSuite is mapped to Chargebee here.)

entitystatusMapped as per the configuration, otherwise left blank

NetSuite Reference (The reference value from NetSuite is mapped to Chargebee here.)

subsidiaryMapped as per the configuration

NetSuite Reference (The reference value from NetSuite is mapped to Chargebee here.)

addressbookListbillingAddress

Refer to the NetSuite CustomerAddressbook section below for more details.

firstnamefirstName or DefaultFirstNameThis field is applicable if isperson is set true.
lastnamelastName or DefaultLastNameThis field is applicable if isperson is set true.
ispersontrue

true if the customer company name is not present and has no contacts.

emailemail
phonephone
vatRegNumbervatRegNumber

NetSuite CustomerAddressbook

Customer Address Book in NetSuite is mapped as Billing address in Chargebee. Chargebee creates or appends customer billing address to NetSuite's customer address book.

Note

Source Entity - Chargebee Customer billing address

The following table provides information on the CustomerAddressbook object fields mapped between Chargebee and NetSuite:

NetSuite Target FieldChargebee Source FieldAdditional information
citycity
statestateCode
zipzip
countrycountry
addresseefullname or companyName

Mapped based on the configurations made in the backend.Contact Chargebee Support for more help.

addr1line1
addr2line2
addr3line3

NetSuite Item Mapping

In NetSuite, Item is the object name for Plans/Addons in Chargebee.

Note

Source entity - Chargebee Plans, Addons, and Item Prices

Supported actions - Create, Update

Unsupported actions - Delete, Void

The following table provides information on the NetSuite Item mapping done between Chargebee and NetSuite:

NetSuite Target FieldChargebee Source FieldAdditional information
externalIdsku or name

A prefix is added if this field is configured.If you have checked the Allow Override option in NetSuite, then Chargebee's identifiers will be set as the primary ID for Invoices, Credit Memos, Customers, and so on. If Allow Override is not set in NetSuite, then the value we've set in Chargebee will be ignored.

itemidsku or name

If sku value is present, the source field is mapped as sku, else mapped as name. A prefix is added if this field is configured. If you have checked the Allow Override option in NetSuite, then Chargebee's identifiers will be set as the primary ID for Invoices, Credit Memos, Customers, and so on. If Allow Override is not set in NetSuite, then the value we've set in Chargebee will be ignored.

classaccountingCategory1Mapped based on Item level class or doc_level_tracking
locationaccountingCategory2Mapped based on Item level location or doc_level_tracking.
departmentaccountingCategory3Mapped based on Item level department or doc_level_tracking
revenueRecognitionRuleaccountingCategory4Mapped based on Item level Revenue Recognition Rule Id
revRecForecastRuleaccountingCategory4Mapped based on Item level Revenue Recognition Rule Id
taxSchedule

Mapped as per the backend configuration made, otherwise left blank.

NetSuite Reference (The reference value from NetSuite is mapped to Chargebee here.)

incomeAccountaccountingCodeWe will find matching account either by code or name.
salesDescriptiondescription
subsidiaryListas per configuration

NetSuite Invoice

Note

Source entity - Chargebee Invoice

Supported actions - Create, Update

The following table provides information on the Invoice mapping done between Chargebee and NetSuite:

NetSuite Target FieldChargebee Source FieldComment
billingAddressbillingAddress

Mapping is done as shown in the above NetSuite Address Mapping section.

class

doc_level_tracking or customer_level_tracking can be used (Done based on the backend configuration)

Mapped as per the backend configuration made.
currencycurrencyCode

If the invoice currency is different from customer currency, then we will add the currency to the NetSuite customer and then set the currency reference.

customFieldList

Mapped as per the configuration made, otherwise mapping is not applicable

department

doc_level_tracking or customer_level_tracking can be used (Done based on the backend configuration)

Mapped as per the backend configuration made.
dueDatedueDate
entityIdcustomerId

NetSuite Reference (The reference value from NetSuite is mapped to Chargebee here.)

exchangeRateexchangeRate

If use_tp_exchange_rate is configured, we will send a blank field and exchange rate will be handled in NetSuite. Chargebee's exchange rate will not be sent if this field is enabled.

externalIdidA prefix is added if this field is configured.
itemListlineItemsSee the Item List section section shown below for more details
location

doc_level_tracking or customer_level_tracking can be used (Done based on the backend configuration)

Mapped as per the backend configuration made.
otherRefNumpoNumber
shippingAddressshippingAddress

Mapping is done as shown in the above NetSuite Address Mapping section.

taxDetailsOverridetrue if override tax is configured

If true, Chargebee maps the tax information, else, NetSuite default mapping is followed.

termsMapped as per the configuration made, otherwise left blankMapped based on the configurations made in the backend.
tranDatedateMapped as invoice date.
tranIdid

A prefix is added if this field is configured.If you have checked the Allow Override option in NetSuite, then Chargebee's identifiers will be set as the primary ID for Invoices, Credit Memos, Customers, and so on. If Allow Override is not set in NetSuite, then the value we've set in Chargebee will be ignored.

NetSuite CreditMemo

In NetSuite, Credit Memo is the object name for Credit Notes in Chargebee.

Note

Source entity - Chargebee Credit Note Supported actions - Create, Update

NetSuite Target FieldChargebee Source FieldAdditional information
tranIdid

A prefix is added if this field is configured. If you have checked the Allow Override option in NetSuite, then Chargebee's identifiers will be set as the primary ID for Invoices, Credit Memos, Customers, and so on. If Allow Override is not set in NetSuite, then the value we've set in Chargebee will be ignored.

externalIdidA prefix is added if this field is configured.
exchangeRateexchangeRate

If use_tp_exchange_rate is configured, we will send a blank field and the exchange rate will be handled in NetSuite.

classdoc_level_tracking or customer_level_tracking can be used.Mapped as per the backend configuration.
location doc_level_tracking or customer_level_tracking can be used. Mapped as per the backend configuration.
departmentdoc_level_tracking or customer_level_tracking can be used. Mapped as per the backend configuration.
itemListlineItemsMapping is shown in the Item List section below.
exchangeRateexchangeRate

If use_tp_exchange_rate is configured, we will send a blank field and exchange rate will be handled in NetSuite. Chargebee's exchange rate will not be sent if this field is enabled.

entityIdcustomerId

NetSuite Reference (The reference value from NetSuite is mapped to Chargebee here.)

currencycurrencyCode

NetSuite Reference (The reference value from NetSuite is mapped to Chargebee here.)

setCreatedFromreferenceInvoiceId

NetSuite Reference (The reference value from NetSuite is mapped to Chargebee here.)

dueDatedueDateNot applicable for Credit Note.
billingAddressbillingAddress

Not applicable for Credit Note.Mapping is done as shown in the NetSuite Address Mapping section above.

shippingAddressshippingAddress

Not applicable for Credit Note.Mapping is done as shown in the NetSuite Address Mapping section above.

applyListallocationsWe will create or append to the applyList.
taxDetailsOverridetrue if override tax is configured

true if override tax is configured, else, NetSuite's default is followed.

tranDatedate
otherRefNumpoNumber
autoApplyfalse
customFieldListMapped as per configuration, else mapping is not applicable.

NetSuite Line Item

Line item-level tracking categories are automatically fed from the items created in NetSuite.

Note

Source entity - Chargebee Invoice / Credit Note Line Items

The following table provides information on the Line Item level mapping done between Chargebee and NetSuite:

NetSuite Target FieldChargebee Source FieldComment
ItemRefentityId based line item entityType and entityId

If UseSalesAccount (as_per_sales) is not enabled, for ad-hoc cases, setup charges, bad_debts, discounts → default item that is created by Chargebee is used.We can also map to the existing item (For ad-hoc, setup charges, bad_debts, and discounts) in NetSuite.

DescriptiondescriptionThis field is referred to as External Name on the Chargebee UI.
AmountamountFor tax inclusive cases, the amount is adjusted.
Quantityquantity
IsTaxabletrue/falseMapped based on tax details.
TaxCodeMapped based on the tax mapping and tax line item details.
customFieldList

Used for setting Advanced Revenue Management (ARM) start and end date. dateFrom dateTo

If Advanced Revenue Management (ARM) module is enabled, NetSuite supports start and end dates at line item level through custom fields of type date.

NetSuite Customer Payment and Customer Refund

Based on the transaction type, we will map the fields to either payment or refund to NetSuite.

Note

Source Entity - Chargebee Transaction

The following table provides information on the payment/refund field mapping done between Chargebee and NetSuite:

NetSuite Target FieldChargebee Source FieldComment
customercustomerId

NetSuite Reference (The reference value from NetSuite is mapped to Chargebee here.)

tranIdid

A prefix is added if this field is configured. If you have checked the Allow Override option in NetSuite, then Chargebee's identifiers will be set as the primary ID for Invoices, Credit Memos, Customers, and so on. If Allow Override is not set in NetSuite, then the value we've set in Chargebee will be ignored.

externalIdcurrencyCode

NetSuite Reference (The reference value from NetSuite is mapped to Chargebee here.)

autoApplyfalse
paymentamountConverted from cents to amount.
checkNumreferenceNumber
memoidAtGateway or referenceNumber

if idAtGateway is present,idAtGateway is mapped, else referenceNumber is mapped.

accountMapped based on configurations, currency, and paymentMethod.Gateway + currency account mapping
undepFundsfalse
exchangeRateexchangeRate

If use_tp_exchange_rate is configured, we will send a blank field and exchange rate will be handled in NetSuite.

PaymentMethodMapped based on the payment method configuration.
TranDatedate
classdoc_level_tracking or customer_level_tracking can be used.Mapped based on the backend configuration.
locationdoc_level_tracking or customer_level_tracking can be used.Mapped based on the backend configuration.
departmentdoc_level_tracking or customer_level_tracking can be used.Mapped based on the backend configuration.
customFieldListMapped based on the backend configuration, else left blank.
applyListlinkedInvoices, linkedCreditNotes, referenceTransactionId

payment uses linkedInvoices refund uses linkedCreditNotes and referenceTransactionId

Was this article helpful?