This page helps you understand the objects and field mapping that is done between Chargebee and NetSuite.
Table of Contents |
---|
Customer
Info |
---|
Source Entity - Chargebee Customer Supported Actions - Create, Update Unsupported Actions - Delete, Void |
...
NetSuite Target Field | Chargebee Source Field | Additional information |
---|---|---|
|
| 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. |
|
| A prefix is added if this field is configured. |
|
|
|
|
| This field is applicable if |
|
| This field is applicable if |
|
| If |
|
| NetSuite Reference (The reference value from NetSuite is mapped to Chargebee here.) |
| Mapped as per the configuration, otherwise left blank | NetSuite Reference (The reference value from NetSuite is mapped to Chargebee here.) |
| Mapped as per the configuration | NetSuite Reference (The reference value from NetSuite is mapped to Chargebee here.) |
|
| |
|
| |
|
| Refer to the NetSuite CustomerAddressbook section below for more details. |
| Mapped as per the backend configuration made, else not applicable. | |
|
|
...
Info |
---|
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 Field | Chargebee Source Field | Comment |
---|---|---|
entityId |
| NetSuite Reference (The reference value from NetSuite is mapped to Chargebee here.) |
tranId |
| 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. |
externalId |
| A prefix is added if this field is configured. |
tranDate |
| Mapped as invoice date. |
terms | Mapped as per the configuration made, otherwise left blank | Mapped based on the configurations made in the backend. |
|
| 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. |
|
| If |
|
| |
|
| |
|
| Mapping is done as shown in the above NetSuite Address Mappingsection. |
|
| Mapping is done as shown in the above NetSuite Address Mappingsection. |
|
| Mapped as per the backend configuration made. |
|
| Mapped as per the backend configuration made. |
|
| Mapped as per the backend configuration made. |
|
| If |
|
| See the Item List section section shown below for more details. |
| Mapped as per the configuration made, otherwise mapping is not applicable |
...
NetSuite Target Field | Chargebee Source Field | Comment |
---|---|---|
customer |
| NetSuite Reference (The reference value from NetSuite is mapped to Chargebee here.) |
tranId |
| 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. |
externalId |
| A prefix is added if this field is configured. |
currency |
| NetSuite Reference (The reference value from NetSuite is mapped to Chargebee here.) |
autoApply |
| |
payment |
| Converted from cents to amount. |
checkNum |
| |
memo |
| if |
account | Mapped based on configurations, | Gateway + currency account mapping |
|
| |
|
| If |
| Mapped based on the payment method configuration. | |
|
| |
class |
| Mapped based on the backend configuration. |
location |
| Mapped based on the backend configuration. |
department |
| Mapped based on the backend configuration. |
| Mapped based on the backend configuration, else left blank. | |
|
| payment uses refund uses |
Info |
---|
See also:
|