Accounts Receivable Invoice object mapping

This page helps you understand the object and field mapping between Chargebee and Sage Intacct for Accounts Receivable (AR) invoices.

Customer

Note

Source entity - Chargebee Customer
Supported actions - Create and Update
Unsupported actions - Delete and Void

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

Note

A prefix is added if the field is configured.

Sage Intacct Target Field	Chargebee Source Field	Additional information
`customerid`	`id`	The maximum allowed characters are 17
`name`	`company` `first_name + last_name` `id`	First preference is given to the `company`, then `first_name+last_name`, and the least to the `id`. The maximum allowed characters are 99
`displaycontact`		Mapping information provided in the table given below Display Contact.
`billto`	`id+` Sage Intacct Target Field	Chargebee Source Field
`trx_tax`	amount
`detailid`	based on the configuration

Display Contact

The following table provides information on the display contact object fields mapped between Chargebee and Sage Intacct:

Note

A prefix is added if the field is configured.

Sage Intacct Target Field	Chargebee Source Field	Additional information
`memo`	`description`
`glaccountno`	`glaccountno`	`glaccountno` mapped to accounting code (Item GL Group) of the line item and it is fetched based on the configured transaction definition.
`amount`	`amount`	The maximum allowed decimals are 4
`itemid`	`id`	Synced intacct item id of Chargebee's Plan/Addon and other sync items.
`locationid`	`accountingCategory2` OR based on the configuration
`departmentid`	based on the configuration
`projectid`	based on the configuration
`customerid`	based on the configuration
`employeeid`	based on the configuration
`classid`	based on the configuration
`vendorid`	based on the configuration
`revrectemplate`	based on the configuration OR `accountingCategory1`
`revrecstartdate`	`date_from`
`revrecenddate`	`date_to`
`taxentries`		Mapping information provided in the table given below Tax.
Sage Intacct Target Field	Chargebee Source Field
`trx_tax`	amount
`detailid`	based on the configuration

Tax

The following table provides information on the tax object fields mapped between Chargebee and Sage Intacct:

Note

A prefix is added if the field is configured.

Sage Intacct Target Field	Chargebee Source Field
`trx_tax`	0
`detailid`	based on the configuration

Discount

The following table provides information on the discount object fields mapped between Chargebee and Sage Intacct:

Note

A prefix is added if the field is configured.

Sage Intacct Target Field	Chargebee Source Field
`memo`	"Round-off value"
`glaccountno`	based on the configuration
`itemid`	based on the configuration
`amount`	`amount` Note: The maximum allowed decimals are 2
`locationid`	based on the configuration
`departmentid`	based on the configuration
`projectid`	based on the configuration
`customerid`	based on the configuration
`employeeid`	based on the configuration
`classid`	based on the configuration
`vendorid`	based on the configuration
`revrectemplate`	based on the configuration
`revrecstartdate`	`date`
`revrecenddate`	`date`

Applying Credit Note on Invoice

A credit note is applied over different invoices by AR payment linked to invoices over Intacct credit notes.

Applying AR Payment

The following table provides information on the AR Payment object fields mapped between Chargebee and Sage Intacct:

Note

A prefix is added if the field is configured.

Sage Intacct Target Field	Chargebee Source Field
`arpaymentkey`	`id`
`paymentdate`	`allocated_at`
`memo`	"Creditmemo applied over invoice"
`overpaylocid`	nil
`overpaydeptid`	nil
`arpaymentitems`	Items on which this payment should apply Note: Mapping information provided in the table given below AR Payment Item.

Applying AR Payment

The following table provides information on the AR payment object fields mapped between Chargebee and Sage Intacct:

Note

A prefix is added if the field is configured.

Sage Intacct Target Field	Chargebee Source Field
`arpaymentkey`	`id`
`paymentdate`	`date`
`memo`	"refund knockoff" + refund transaction id
`overpaylocid`	nil
`overpaydeptid`	nil
`arpaymentitems`	Items on which this payment should apply Note: Mapping information provided in the table given below AR Payment Item.

Creating AP Payment

The following table provides information on the AP payment object fields mapped between Chargebee and Sage Intacct:

Note

A prefix is added if the field is configured.

Sage Intacct Target Field	Chargebee Source Field
`bankaccountid`	payment account code based on the configuration
`paymentmethod`	"Cash"
`memo`	"refund id -" + `id`
`vendorId`	based on the configuration
`paymentdate`	`date`
`paymentrequestitems`	list of payment request items Note: Mapping information provided in the table given below Payment Request Items.

Applying AR Payment

The following table provides information on applying AR Payment object fields mapped between Chargebee and Sage Intacct:

Note

A prefix is added if the field is configured.

Sage Intacct Target Field	Chargebee Source Field
`arpaymentkey`	`id`
`paymentdate`	`date`
`memo`	"payment apply"
`overpaylocid`	based on the configuration
`overpaydeptid`	based on the configuration
`arpaymentitems`	Items for which invoice this payment should apply. Note: Mapping information provided in the table given below AR Payment Item.

Applying AR Payment

The following table provides information on the AR Payment object fields mapped between Chargebee and Sage Intacct:

Note

A prefix is added if the field is configured.

Sage Intacct Target Field	Chargebee Source Field	Additional information
`arpaymentkey`	`Id`
`paymentdate`	`date`
`memo`	"refund knockoff" + refund transaction id
`overpaylocid`	nil	If multicurrency feature is enabled, then `overpaylocid` is populated from the mapping.
`overpaydeptid`	Applicable only for multi currency feature	If multicurrency feature is enabled, then `overpaydepartid` is populated from the mapping.
`arpaymentitems`	List of invoices for which this payment should apply	Mapping information provided in the table given below AR Payment Item.

Sage Intacct Target Field	Chargebee Source Field
`key`	"bill_" + `id`
`paymentamount`	exchangerate * `amount`

Offline Payments

The following table provides information on the offline payments object fields mapped between Chargebee and Sage Intacct:

Note

A prefix is added if the field is configured.

Sage Intacct Target Field	Chargebee Source Field
`cusId`	`id`
`invId`	`id`
`amount`	`amount`
`ts - (timestamp)`	`date`
`mtd - (payment method)`	based on the configuration Note: Mapping information provided in the table given below Payment Method Mapping.
`refId`	`documentnumber`
`tpId`	`recordno`
`comment`	"Two way sync from intact Id :" + `documentnumber` + " internalid :" + `recordno`

Note

A prefix is added if the field is configured.

Sage Intacct Target Field	Chargebee Source Field
Credit card / Online Charge Card	CARD
Cash	CASH
EFT	BANK_TRANSFER
Printed Check	CHECK
If empty	CASH
If none of the above	CHECK

Accounts Receivable Invoice object mapping

This page helps you understand the object and field mapping between Chargebee and Sage Intacct for Accounts Receivable (AR) invoices.

Customer

Note

Source entity - Chargebee Customer
Supported actions - Create and Update
Unsupported actions - Delete and Void

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

Note

A prefix is added if the field is configured.

Sage Intacct Target Field	Chargebee Source Field	Additional information
`customerid`	`id`	The maximum allowed characters are 17
`name`	`company` `first_name + last_name` `id`	First preference is given to the `company`, then `first_name+last_name`, and the least to the `id`. The maximum allowed characters are 99
`displaycontact`		Mapping information provided in the table given below Display Contact.
`billto`	`id+` Sage Intacct Target Field	Chargebee Source Field
`trx_tax`	amount
`detailid`	based on the configuration

Display Contact

The following table provides information on the display contact object fields mapped between Chargebee and Sage Intacct:

Note

A prefix is added if the field is configured.

Sage Intacct Target Field	Chargebee Source Field	Additional information
`memo`	`description`
`glaccountno`	`glaccountno`	`glaccountno` mapped to accounting code (Item GL Group) of the line item and it is fetched based on the configured transaction definition.
`amount`	`amount`	The maximum allowed decimals are 4
`itemid`	`id`	Synced intacct item id of Chargebee's Plan/Addon and other sync items.
`locationid`	`accountingCategory2` OR based on the configuration
`departmentid`	based on the configuration
`projectid`	based on the configuration
`customerid`	based on the configuration
`employeeid`	based on the configuration
`classid`	based on the configuration
`vendorid`	based on the configuration
`revrectemplate`	based on the configuration OR `accountingCategory1`
`revrecstartdate`	`date_from`
`revrecenddate`	`date_to`
`taxentries`		Mapping information provided in the table given below Tax.
Sage Intacct Target Field	Chargebee Source Field
`trx_tax`	amount
`detailid`	based on the configuration

Tax

The following table provides information on the tax object fields mapped between Chargebee and Sage Intacct:

Note

A prefix is added if the field is configured.

Sage Intacct Target Field	Chargebee Source Field
`trx_tax`	0
`detailid`	based on the configuration

Discount

The following table provides information on the discount object fields mapped between Chargebee and Sage Intacct:

Note

A prefix is added if the field is configured.

Sage Intacct Target Field	Chargebee Source Field
`memo`	"Round-off value"
`glaccountno`	based on the configuration
`itemid`	based on the configuration
`amount`	`amount` Note: The maximum allowed decimals are 2
`locationid`	based on the configuration
`departmentid`	based on the configuration
`projectid`	based on the configuration
`customerid`	based on the configuration
`employeeid`	based on the configuration
`classid`	based on the configuration
`vendorid`	based on the configuration
`revrectemplate`	based on the configuration
`revrecstartdate`	`date`
`revrecenddate`	`date`

Applying Credit Note on Invoice

A credit note is applied over different invoices by AR payment linked to invoices over Intacct credit notes.

Applying AR Payment

The following table provides information on the AR Payment object fields mapped between Chargebee and Sage Intacct:

Note

A prefix is added if the field is configured.

Sage Intacct Target Field	Chargebee Source Field
`arpaymentkey`	`id`
`paymentdate`	`allocated_at`
`memo`	"Creditmemo applied over invoice"
`overpaylocid`	nil
`overpaydeptid`	nil
`arpaymentitems`	Items on which this payment should apply Note: Mapping information provided in the table given below AR Payment Item.

Applying AR Payment

The following table provides information on the AR payment object fields mapped between Chargebee and Sage Intacct:

Note

A prefix is added if the field is configured.

Sage Intacct Target Field	Chargebee Source Field
`arpaymentkey`	`id`
`paymentdate`	`date`
`memo`	"refund knockoff" + refund transaction id
`overpaylocid`	nil
`overpaydeptid`	nil
`arpaymentitems`	Items on which this payment should apply Note: Mapping information provided in the table given below AR Payment Item.

Creating AP Payment

The following table provides information on the AP payment object fields mapped between Chargebee and Sage Intacct:

Note

A prefix is added if the field is configured.

Sage Intacct Target Field	Chargebee Source Field
`bankaccountid`	payment account code based on the configuration
`paymentmethod`	"Cash"
`memo`	"refund id -" + `id`
`vendorId`	based on the configuration
`paymentdate`	`date`
`paymentrequestitems`	list of payment request items Note: Mapping information provided in the table given below Payment Request Items.

Applying AR Payment

The following table provides information on applying AR Payment object fields mapped between Chargebee and Sage Intacct:

Note

A prefix is added if the field is configured.

Sage Intacct Target Field	Chargebee Source Field
`arpaymentkey`	`id`
`paymentdate`	`date`
`memo`	"payment apply"
`overpaylocid`	based on the configuration
`overpaydeptid`	based on the configuration
`arpaymentitems`	Items for which invoice this payment should apply. Note: Mapping information provided in the table given below AR Payment Item.

Applying AR Payment

The following table provides information on the AR Payment object fields mapped between Chargebee and Sage Intacct:

Note

A prefix is added if the field is configured.

Sage Intacct Target Field	Chargebee Source Field	Additional information
`arpaymentkey`	`Id`
`paymentdate`	`date`
`memo`	"refund knockoff" + refund transaction id
`overpaylocid`	nil	If multicurrency feature is enabled, then `overpaylocid` is populated from the mapping.
`overpaydeptid`	Applicable only for multi currency feature	If multicurrency feature is enabled, then `overpaydepartid` is populated from the mapping.
`arpaymentitems`	List of invoices for which this payment should apply	Mapping information provided in the table given below AR Payment Item.

Sage Intacct Target Field	Chargebee Source Field
`key`	"bill_" + `id`
`paymentamount`	exchangerate * `amount`

Offline Payments

The following table provides information on the offline payments object fields mapped between Chargebee and Sage Intacct:

Note

A prefix is added if the field is configured.

Sage Intacct Target Field	Chargebee Source Field
`cusId`	`id`
`invId`	`id`
`amount`	`amount`
`ts - (timestamp)`	`date`
`mtd - (payment method)`	based on the configuration Note: Mapping information provided in the table given below Payment Method Mapping.
`refId`	`documentnumber`
`tpId`	`recordno`
`comment`	"Two way sync from intact Id :" + `documentnumber` + " internalid :" + `recordno`

Note

A prefix is added if the field is configured.

Sage Intacct Target Field	Chargebee Source Field
Credit card / Online Charge Card	CARD
Cash	CASH
EFT	BANK_TRANSFER
Printed Check	CHECK
If empty	CASH
If none of the above	CHECK

Product Updates

Getting Started

Implementing Chargebee

AI in Chargebee

Developer Resources

Product Catalog

Subscriptions

Customers

Entitlements

Usage Based Billing

Chargebee CPQ

Invoices, Credit Notes, and Quotes

Taxes

Hosted Capabilities

Site Configuration

Multi Business Entity

Mobile Subscriptions

Reports and Analytics

Integrations

Data Privacy & Security

Data Operations

Accounts Receivable Invoice object mapping

Customer

Display Contact

Tax

Discount

Applying Credit Note on Invoice

Applying AR Payment

Applying AR Payment

Creating AP Payment

Applying AR Payment

Applying AR Payment

Offline Payments

Product Updates

Getting Started

Implementing Chargebee

AI in Chargebee

Developer Resources

Product Catalog

Subscriptions

Customers

Entitlements

Usage Based Billing

Chargebee CPQ

Invoices, Credit Notes, and Quotes

Taxes

Hosted Capabilities

Site Configuration

Multi Business Entity

Mobile Subscriptions

Reports and Analytics

Integrations

Data Privacy & Security

Data Operations

Accounts Receivable Invoice object mapping

Customer

Display Contact

Tax

Discount

Applying Credit Note on Invoice

Applying AR Payment

Applying AR Payment

Creating AP Payment

Applying AR Payment

Applying AR Payment

Offline Payments