Skip to main content

Legal

Tax & Accounting

Trade & Supply

Risk & Fraud

News & Media

Books

Developers

Mappings

Conditional mappings

In some cases, a product can be referred to by different product categories and thus be taxed in a different way by virtue of its use. Conditional mappings enable you to specify custom fields, which, when evaluated together, drive the specific product and taxability to be used for a transaction line.
Using Determination, elements of a tax request can be used to infer product end-use. You can create a configuration so that tax request elements can be used to determine what the product or commodity code is for a tax line request.
By default, each transaction submitted for tax calculation contains 1 product code per line. This enables the appropriate sales tax calculation to proceed based on that product's attributes.
Using conditional mappings, you can base product code selection on a variety of input criteria such as cost center, part number, GL account code, and many others. This enables you to account for use tax (purchasing) scenarios, as well as those in which the vendor charged tax when invoicing your company.
Conditional mappings are grouped
, and a group belongs to a single company. Each company has a default conditional mapping group, and in general, you should use it as the preferred group. Within each conditional mapping group, conditional mappings may be arranged in a preferred order, and are evaluated in that order.
Each conditional mapping will have associated conditions you set up. The conditions specify how the mapping values are to be evaluated, and may use operators to specify the action (using symbols to represent equal, not equal, not like, and so on).

This article applies to:

  • Product: ONESOURCE Determination, ONESOURCE Indirect Tax