2022
Page History
...
Consists of a base unit and any number
| Anchor | ||||
|---|---|---|---|---|
|
When you create a unit of measure set, you can also specify which unit of measure should appear by default when adding an item to a purchase form, a sales form, and a shipping pick list. You also give the set a name, such as "Length by the foot."
Once you've created a unit of measure set and assigned it to an item, you can easily convert to other units of measure within the set when you add the item to a transaction. Continuing with the previous example, if you add the Cable item to an invoice with a quantity of 10 yards, you could then convert that quantity to 30 feet or 0.06 spools.
Note: Unit of measure sets are available only when Multiple U/M Per Item is selected as the unit of measure mode.
Set Up – Multiple Units of Measure Per Item
QB company file has multi-select UOM option per ITEM. A single item can have multiple UOM selected and one of the UOM values has to be assigned as default. However, while generating a transaction, you can use different sets based on the requirement or conversion required for a given transaction. The screenshot below illustrates the same.
In the example shown below for the ITEM z0b1-739 the default UOM set lb739has the base unit as POUND (lb) but has several related units Square Feet, Linear Feet and sheet with default values as shown. The above can be read as
1 pound = 1.03 Sq Feet
1 pound = 3.3818 Linear Feet
1 pound = 33.8183 sheets
The same ITEM when selected within a transaction in QuickBooks, we can use the following conversions based on the quantity and UOM set used. The below screenshots illustrates the same
Field Mappings for Invoice Item Line with UOM
Below is a table listing out mappings / data required from Salesforce for successful integration of a QuickBooksInvoice transaction with a Unit of Measure.
...
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.
Screen Shot for DBSync Mapping for UnitOfMeasure:
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.
Salesforce | R | QuickBooks | R | Comments |
ItemTaxCode | Y | ItemSalesTaxRef | Y | This field should be on the Opportunity object and the NAME should match with the QuickBooksSalesTaxCode list at all times |
Customer Tax Code | N | CustomerSalesTaxCodeRef | N | This field should be on the Opportunity object and the NAME should match with the QuickBooksCustomerTaxCode list at all times |
SalesTaxCode | Y | SalesTaxCodeRef | Y | This field should be on the Opportunity Products object and again should match with QuickBooks available list. |
TaxAmount | N | TaxAmount | N | Should be on the Opportunity Products Object |
CheckBox | N | IsTaxable | N | Should be on the LineItem level. |
ItemSalesTaxRef:MaxLength = 31
The ItemSalesTaxRef (marked as no.1 in the screenshot) field is the one which calculates the tax based on whether aLineItem is taxable or not (Identified as no. 3 in screenshot). The ItemSalesTax is setup on each Item in quickbooks at the time of configuration. A corresponding field in Salesforce should always be on the Opportunity object as it is on the Invoice header on QuickBooks. Secondly the SFDC field name should always match with the ItemSalesTax code list available in QuickBooks and preferable data-type in Salesforce is Text Field or Picklist.
Screen Shot for DBSync Mapping for ItemSalesTaxRef:
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.
Screen Shot for DBSync Mapping for CustomerSalesTaxCodeRef:
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 Screen Shot for DBSync Mapping for SalesTaxCodeRef:
Overview
Content Tools