2022
This document section illustrates a typical QuickBooks Unit Of Measurement configuration for all the ITEM List and how the same can be replicated in Salesforce under Products which is an equivalent of QuickBooks ITEMS List. The following section illustrates Unit Of Measure, Base Unit and Related Unit
The first unit defined in a unit of measure set and is usually the smallest unit of measure used for an item when purchasing it, tracking it in inventory, and selling it. In QuickBooks, the base units of items are used to count inventory, generate most inventory reports, and perform quantity-related calculations.
Important: When you create an inventory item, the cost, sales price, and on hand quantity you enter are all for the base unit.
A unit defined by the number of base units it contains. For example, if the base unit is foot, a related unit might be yard, which is defined as containing three feet.
Related units make it possible to show quantities of the same item in different measurements in different places in QuickBooks. For example, you might purchase an item called Cable in spools, count that item in inventory by the foot, and sell it by the yard. By creating a unit of measure set with a base unit of foot and related units of spool (containing 500 feet) and yard, you can enter a quantity of spools on a purchase order, show the item in feet on inventory reports, and enter a quantity of yards on an invoice.
Consists of a base unit and any number
Anchor | ||||
---|---|---|---|---|
|
Salesforce | R | QuickBooks | R | Comments |
Rate | Y | Rate | Y | The rate has to be calculated precisely based on the quantity and based on the conversion for a particular UOM. |
Quantity | Y | Quantity | Y | Quantity should be calculated from SF based on the Unit and Conversion used for a particular Product |
UOM | N | UnitOfMeasure | N | The correct UOM should be referred with the names matching the U/M list in QuickBooks |
Rate:
The rate or amount of the LineItem should be precise based on the UNIT used and the quantity used. The calculation of thisneeds to happen on the Salesforce side at the Opportunity Line Item level based on the PRODUCT selected and UNIT used before DBSync can parse / push this data into QuickBooks without the transaction erring out.
Quantity:
Quantity values should change either as 1 Ft, 1Sheet etc as shown above based on the UNIT selected for a given PRODUCT on the OpportunityLineItem. Care should be taken to make sure we are always sending in the correct Quantity along with the right UNIT.
UnitOfMeasure:
MaxLength - 31
This is the qbxml name for selecting a UOM for a given transaction line item. For a given UNIT, there are several RELATED UNITS based on which the Quantity and Rate changes as shown in the above screenshots. For a given ITEM LINE, if the right BASE UNIT name, corresponding QUANTITY and RATE should be provided at all times for a successful integration of an Invoice transaction. A corresponding field on the OpportunityProducts object can either be a Picklistor Text field and data needs to be populated at all times.
Field Mappings for Invoice integration with Sales Tax
This section illustrates the field mappings required for QuickBooksInvoice integration based on SalesTaxCode configuration in QuickBooks.
The below screenshot shows a typical Invoice transaction in QuickBookswith SalesTaxCode and Customer Tax Code information. In order to ensure a seamless integration of a transaction with SalesTaxCode DBSync will require the following information from Salesforce to integrating the same into QuickBooks.
...
CustomerSalesTaxCodeRef:MaxLength = 3
The customer Tax Code in QuickBooks holds the values Taxable Sales &Non-Taxable Sales. It could also hold custom values based on how QuickBooksCustomerTaxCode is configured. The corresponding field in SFDC needs to be again at the Opportunity level and preferably has to be Text field with the data values matching with the QuickBooksCustomerSalesTaxCodeRef list.
SalesTaxCodeRef: MaxLength = 3
SalesTaxCode by default have Tax andNonas default values which translate into Taxable &Non Taxables into QuickBooks. QuickBooks can also hold custom values but can exceed only till 3 characters in length. The corresponding SFDC field preferable needs to be a Text field and hold same vales as that of QuickBooks "SalesTaxCodeRef" list