Skip to main content

Legal

Tax & Accounting

Trade & Supply

Risk & Fraud

News & Media

Books

Developers

Reference data

Units of measure configuration examples

These examples describe how the different unit of measure (UOM) configurations work together.

Default UOM in transaction, matching UOM on fee

Example: A quantity in the transaction's specified as the default. That default quantity uses a unit of measure which matches the unit of measure found on the fee triggered by the tax calculation.
Result: No UOM conversion is needed and the transaction proceeds normally.

Default UOM in transaction, non-matching UOM on fee

Example: A quantity in the transaction's specified as the default. That default quantity uses a UOM that doesn't match the unit of measure found on the fee triggered by the tax calculation.
Result: Assuming that the different UOMs are of the same category (for example volume) and that a conversion factor's available, the amount from the transaction is converted to match the unit of measure on the fee; and then tax gets calculated using the converted amount.
For example:
  • Default UOM in transaction is LBR (pounds); amount is 10.
  • Default UOM on rate's KGM (kilograms).
  • Both UOMs are in the same category (mass).
  • 10 pounds are converted to 4.5359237 kilograms and the calculation proceeds.

Default UOM in transaction, "Use Default Input UOM" checked on fee

Example: A quantity in the transaction's specified as the default. The
Use Default Input UOM
 option's been selected for the fee.
Result: No unit of measure conversion's needed and the transaction proceeds normally.

No default UOM in transaction, "Use Default Input UOM" checked on fee, matching authority UOM

Example: No quantity in the transaction's specified as the default. The
Use Default Input UOM
 option's been selected for the fee. The associated authority uses a default unit of measure that matches 1 of the quantities passed in with the transaction.
Result: In this case, the first quantity matching the authority default UOM's used. Consider the following sample transaction:
  • A line in a transaction includes three quantities: 10 LBR, 4.5359237 KGM, and 4535.9237 GRM.
  • The Authority default UOM's set to KGM.
  • 4.5359237 KGM's used as the quantity for the transaction.

No default UOM in transaction, "Use Default Input UOM" not checked on fee, non-matching authority UOM

Example: No quantity in the transaction's specified as the default. The
Use Default Input UOM
 isn't selected for the fee. The associated authority uses a default unit of measure that doesn't match any of the quantities passed in with the transaction.
Result: Determination attempts to convert each quantity to the authority default, first using direct conversion factors and then using conversions where each UOM shares the same base attribute. If no conversion's possible, the transaction fails.
Example:
  • A line in a transaction includes a single quantity: 10 LBR.
  • The Authority default UOM is set to KGM.
  • A direct conversion can be performed between LBR and KGM.
  • 4.5359237 KGM is used as the quantity for the transaction.
Determination defines the following base attributes for the associated category:
  • KGM (kilogram): Mass
  • LTR (liter): Volume
  • MTK (square meter): Area
  • MTR (meter): Length
You can create additional base attributes or use these defaults.

No UOM in transaction

If no UOM's specified in a transaction, Determination applies a default unit of measure of each to the quantity. each has a conversion factor of 1:1 to all other units of measure. Once this unit of measure has been assigned, transaction processing takes place as indicated in the previous examples.

This article applies to:

  • Product: ONESOURCE Determination, ONESOURCE Indirect Tax

Related content