1. Implementing Tax
  2. Tax Configuration Content Upload Program

Tax Configuration Content Upload Program

The tax configuration content upload program populates data for the United States (US) in both Oracle Fusion Tax and the Oracle Fusion Trading Community Model geography hierarchy using a single data file provided by specific tax partners.

This process is limited in geographic scope to just the United States.

The data file includes:

  • US sales and use tax rate information for all states, counties, and cities which impose sales and use taxes.

  • US state, county, city, and postal code geography combinations.

Alternatively, you can upload the tax partner content using the Tax Rapid Implementation spreadsheets. The spreadsheets are more flexible and support the upload of global tax content instead of just United States tax content. The Define Taxes for Rapid Implementation task list available in the Functional Setup Manager contains individual tasks from which external tax partners can access rapid implementation spreadsheet templates to provide the tax content to customers.

Settings That Affect Tax Configuration Content Uploads

The execution of the tax configuration content upload program differs depending upon the type of Oracle Fusion Applications implementation involved.

  • For non-Software as a Service (SaaS) implementations, use the Run Jurisdiction and Rates Upload Program task in the Financials offering or the rapid implementation task list to start the Upload Tax Configuration Content job set. The Upload Tax Configuration Content job set consists of two individual jobs:

    1. Upload Tax Content File

    2. Process Tax Content Data

  • For SaaS (Oracle Cloud) implementations, run the Import Tax Configuration Content job using the Scheduled Processes page.

You must populate all parameters displayed for each process to prevent errors. Specific parameters are as follows:

Parameter

Description

File Location and Name

The full application server directory path and file name related to the specific tax partner data file that is saved on the application server.

Note: This parameter isn't used in Oracle Cloud implementations.

Tax Content Source

The name of the specific tax partner provider that was previously created in Oracle Fusion applications.

Tax Regime Code

The specific US tax regime code that already exists in Oracle Fusion Tax against which the data content upload is executed.

Prerequisites for a Cloud Implementation

Prior to running the Import Tax Configuration Content job in a Cloud implementation, to enable access to the tax partner data file, you must perform the following steps:

  1. Log into Oracle Fusion applications using a specific user that has access to complete the tax configuration content upload process.

    Note: Predefined job roles such as Tax Manager, Financial Application Administrator, and Applications Implementation Consultant, have this access.

  2. From the Navigator menu, go to the File Import and Export page.

  3. Upload the compressed version of the tax partner data file from your local directory to the Universal Content Management server.

  4. Enter fin/tax/import as the account.

  5. Before you run the Import Tax Configuration Content job, run the Load Interface File for Import process from the Scheduled Processes page on the Navigator menu. You run this to transfer the data from the UCM server to the zx_data_upload_interface table.

How Tax Data Content Is Processed

The tax data content upload process:

  1. Uploads all US sales and use tax rates available from a tax partner.

  2. Uploads new or updated US sales and use tax rates available in monthly data files provided by a tax partner.

  3. Creates entities for a specific US tax regime including:

    • Taxes

    • Tax statuses

    • Tax jurisdictions

    • Tax rates

  4. Uploads US state, county, city, and postal code combinations into the Trading Community Model geography hierarchy.

Tip: Prior to initiating the tax data content upload for a tax regime, you have the option to configure taxes directly as:

This approach is used to control configuration settings at the tax level. In this case, do not enable the taxes for simulation or for both simulation and transaction purposes until you are certain that there will not be changes to tax-level configuration.

If you configure taxes before initiating the tax data content upload for a tax regime, you can configure tax liability accounts at the tax level. The tax liability accounting configuration predefined at the parent tax level is automatically assigned to child tax jurisdictions and tax rates created during the tax data content upload process.