Skip to main content

Legal

Tax & Accounting

Trade & Supply

Risk & Fraud

News & Media

Books

Developers

More tools

About model scenario

Model Scenario is a powerful tool that enables you to:
  • Create transaction scenarios to test configurations and model the impact of business and tax changes.
  • View the XML information that's needed to submit the transactions you model.
  • View the XML output once Determination calculates the results.

Model a basic transaction

When creating a model scenario, follow these guidelines to ensure clarity and accuracy:
  • Naming conventions
    : Select a name that clearly describes the scenario. For example, use "WA - Sales Exemption for Machinery" to indicate a sales exemption scenario specific to machinery in Washington.
  • Comments
    : Use comments in scenario details to add descriptive text about the scenario to describe the transaction.
  • Basic requirements
    : Enter at least a date, company role, quantity, gross amount, and ship-to address.
  • Unique requirements
    : Add data such as customer name or number, registration data, and product data.
Data entry levels
: Enter data at 2 levels, invoice (or header), and line data.
  • Invoice (or Header) Data
    : This data applies to all lines in a transaction by default.
  • Line Data
    : Use this to override Invoice data or to provide additional details not available in the header.
System data access:
 The Model Scenario accesses stored data within the system to evaluate establishments, exemptions, registrations, and licenses. This ensures that all relevant factors are considered during the modeling process.

View XML input and output

In many cases, you'll want to view both the input and output data generated by Model Scenario.
  • Input data is the XML that Model Scenario generates, and can be used to help verify that your integration's passing all the necessary attributes to enable correct taxation.
  • Output data is the XML returned by Determination if it's calculated for this transaction.

XML inputs in model scenarios

XML Input
  • Begins data processing.
  • Displays the raw XML data as submitted.
  • Applies no changes at this stage.
Filtered XML input
  • Shows XML after applying TransEditors.
  • Doesn't include allocations yet.
  • Helps users observe how TransEditors affect the data.
Allocated XML input (formerly "XML Input")
  • Displays XML after applying both TransEditors and Allocations.
  • Represents the final form of input before calculation.
Determination returns the output data as XML when it calculates for this transaction.

Model advanced transactions

As you gain experience using Determination, you may want to model transactions that include any of the following data:
  • TransEditors
  • Allocations
  • Multiple lines with different product codes, ship-to addresses, or other unique data
  • Customer exemptions
  • Registrations or licenses
For more information about using the Model Scenario, see:
  • Using Model Scenario
  • Scenario Setup
  • Header Information
  • Configure Groups
  • VAT Registrations
  • Establishments
  • Exemptions and Licenses
  • Overrides
  • Custom Fields
  • Line Information

This article applies to:

  • PRODUCT: ONESOURCE Determination,ONESOURCE Indirect Tax