Implementation Checklist For Oracle E-Business Tax: Step Number Step Description

Implementation Checklist for Oracle E-
Business Tax
This table provides a checklist of the mandatory and optional implementation steps in other applications for E-
Business Tax. Some optional implementation steps may be conditionally mandatory, depending on your
overall setup.
Note: You must have access to the system administrator responsibility to perform many of these tasks.
Step Number Step Description
1 Setting Up Tax Users
2 Setting Profile Option Values
3 Setting Up Lookup Codes
4 Setting Up TCA Geography Hierarchy
5 Setting Up Legal Entity
6 Setting Up Operating Units
7 Setting Up Accounts and Accounting Information
8 Setting Up TCA Classifications
9 Setting Up Oracle Inventory
Setting Up Tax Users

Set up your tax users and assign each user a tax-related responsibility. Oracle E-Business Tax provides these
seeded responsibilities:
 Tax Manager. Assign this responsibility to users who will set up and maintain tax configuration data.
The tax manager responsibility is the responsibility with the highest level of access to E-Business Tax
functionality.
If you want to include the GL Tax Options window, you must assign a data access set to the GL: Data
Access Set profile option under the Tax Manager responsibility.
 Tax Administrator. Update and assign this responsibility to users who will provide E-Business Tax
technical setup and support services. You can update this responsibility according to the duties of each
tax administrator user.
 Oracle Tax Simulator. Assign this responsibility to users who test tax setups with the Oracle Tax
Simulator.
You can also set up new E-Business Tax menus and responsibilities according to your requirements.
Setting Profile Option Values

Set values for E-Business Tax profile options to control the availability of certain tax options and to maintain
your Vertex or Taxware installation.
The table in this section summarizes E-Business Tax profile option information:
 The Default column displays either the default profile option value in italics, or No Default if none
exists.
 The User Access column indicates whether you can view or update the profile option.
 The System Administration: Site, Application, Responsibility, and User columns indicate at which
levels the system administrator can update these profile options.
The key for this table is:
 Update: You can update the profile option.

 View Only: You can view the profile option but cannot change it.
 No Access: You cannot view or change the profile option.
Profile Option Default User Access System Administration: Sit
eBTax: Allow Ad Hoc Tax Changes Yes No Access Update
eBTax: Allow Manual Tax Lines Yes No Access Update
eBTax: Allow Override of Customer Exemptions Yes No Access Update
eBTax: Allow Override of Tax Classification Code Yes No Access Update

eBTax: Allow Override of Tax Recovery Rate No Default No Access Update
eBTax: Inventory Item for Freight Freight Charge No Access Update
eBTax: Invoice Freight as Revenue No No Access Update
eBTax: Read/Write Access to GCO Data Yes No Access Update
eBTax Taxware: Service Indicator Non-Service View Only Update
eBTax Taxware: Tax Selection Jurisdiction and Tax View Only Update
eBTax Taxware: Use Nexpro No No Access Update
eBTax Vertex: Case Sensitive Yes View Only Update
eBTax: Allow Ad Hoc Tax Changes

The eBTax: Allow Ad Hoc Tax Changes profile option controls which users can make ad hoc tax changes on
the transaction line, such as selecting a different tax status or tax rate. The changes that a user can make also
depend upon the details of the applicable tax setups.
If the tax rate associated with a tax has the Allow Ad Hoc Rate option enabled, then users can override the
calculated tax rate on the transaction line.
See: Setting Up Tax Rates, Oracle E-Business Tax User Guide for more information.
eBTax: Allow Manual Tax Lines

The eBTax: Allow Manual Tax Lines profile option controls which users can enter manual tax lines on the
transaction for the tax setups that allow this update.
If the tax configuration has the related options enabled, then users can enter manual tax lines on the transaction
for the applicable tax.
The related tax setups are:
 Taxes: Allow Entry of Manual Tax Lines

 Configuration Owner Tax Options:
o Allow Entry of Manual Tax Lines
o Allow Manual Tax Only Lines
eBTax: Allow Override of Customer Exemptions
The eBTax: Allow Override of Customer Exemptions profile option controls the display of the Tax Handling
field on the transaction line. You use the Tax Handling field to apply and update customer tax exemptions to
transactions.
If you set the eBTax: Allow Override of Customer Exemptions profile option to Yes, you must also complete
the related setups for tax exemptions.
eBTax: Allow Override of Tax Classification Code

The eBTax: Allow Override of Tax Classification Code profile option controls whether users can update the
tax classification code that is defaulted to the transaction line.
E-Business Tax defaults the tax classification code to the transaction line according to the defaulting hierarchy
defined for the operating unit and application. See: Using Application Tax Options, Oracle E-Business Tax
User Guide for more information.
eBTax: Allow Override of Tax Recovery Rate

The eBTax: Allow Override of Tax Recovery Rate profile option controls which users can enter or update the
calculated tax recovery rates on the transaction for the tax recovery rate setups that allow this update.
If the tax recovery rate associated with a tax has the Allow Ad Hoc Rate option enabled, then users can
override the calculated tax recovery rate on the transaction.
The meaning of ad hoc entry of tax recovery rates differs according to the source application for the
transaction:
 Payables - The user can only select another previously defined recovery rate for the tax.
 Procurement - The user can either select another previously defined recovery rate for the tax or enter
a new recovery rate.
See: Setting Up Tax Recovery Rates, Oracle E-Business Tax User Guide for more information.
eBTax: Inventory Item for Freight (Oracle Order

Management only)
The eBTax: Inventory Item for Freight profile option lets Order Management use an Inventory item defined
as Freight on Receivables transaction lines. You can use the freight Inventory item to control the tax rate on
taxable freight amounts.
The values for this profile option are:
 Freight Charge - The freight Inventory item applies to external Receivables transactions.
 Freight for Intercompany - The freight Inventory item applies to internal Receivables transactions
only.
You must also set the eBTax: Invoice Freight as Revenue profile option to Yes.
Note: You may also need to set the OE: Item Validation Organization profile option.
eBTax: Invoice Freight as Revenue (Oracle Order

Management only)
The eBTax: Invoice Freight as Revenue profile option controls whether to consider freight amounts as taxable
line items.
Set the eBTax: Invoice Freight as Revenue profile option to Yes, if you are required to tax freight amounts.
The freight amounts entered in the Order Management Ship Confirm window are then passed to Receivables
transactions as taxable line items.
If you set the eBTax: Invoice Freight as Revenue profile option to Yes, you must also set the eBTax: Inventory
Item for Freight profile option.
eBTax: Read/Write Access to GCO Data

The eBTax: Read/Write Access to GCO Data profile option controls whether users can set up tax configuration
data for the global configuration owner.
If you set the eBTax: Read/Write Access to GCO Data profile option to Yes, then the applicable users can set
up taxes and related configuration data for the global configuration owner. Legal entities and operating units
can then share the global configuration owner tax setups.
See: Configuration Options in Oracle E-Business Tax, Oracle E-Business Tax User Guide for more
information.
eBTax Taxware: Service Indicator

The eBTax Taxware: Service Indicator profile option indicates whether taxes are calculated on service or a
rental transactions.
The Taxware API parameter that accepts this profile option value is JurLink.ServInd.
 Service - Service transaction.

 Rental - Rental transaction.
 Space - Non-service transaction.
eBTax Taxware: Tax Selection
The eBTax Taxware: Tax Selection profile option indicates whether Taxware uses jurisdiction-level
jurisdiction codes to calculate taxes.
The Taxware API parameter that accepts this value is TaxSelParm of Taxfn_Tax010.
 Tax only - Taxware calculates tax based on the ship-to address only.
 Jurisdiction and Tax - Taxware calculates tax based on all jurisdiction information, including ship-to,
ship-from, point of order origin (POO), and point of order acceptance (POA).
eBTax Taxware: Use Nexpro

The eBTax Taxware: Use Nexpro profile option indicates whether Taxware uses the Nexpro functionality. If
you enable this option, additional configuration is required on the Taxware side of the integration to achieve
nexus-based taxation.
The Taxware API parameter that accepts this value is TaxLink.UseNexproInd.
See: Technical Reference, Oracle E-Business Tax: Vertex Q-Series and Taxware Sales/Use Tax System
Implementation Guide for information about the Nexpro functionality.
eBTax Vertex: Case Sensitive

the eBTax Vertex: Case Sensitive profile option enables case-sensitive searches of Vertex tax calculation data.
The default value is Yes.
Set this profile option if you intend to use Vertex to calculate tax on transactions.
Setting Up Lookup Codes

Use the Application Object Library Lookups window to maintain existing lookup codes and define additional
lookup codes for E-Business Tax lookup types.
Note: E-Business Tax does not perform validation on updated or disabled lookups. If you want to disable,
update, or apply an end date to an E-Business Tax lookup type, please ensure that the applicable values are not
in use in the E-Business Tax setup.
ZX_INPUT_CLASSIFICATIONS and
ZX_OUTPUT_CLASSIFICATIONS
Use the ZX_INPUT_CLASSIFICATIONS and ZX_OUTPUT_CLASSIFICATIONS lookup types to create
tax classification codes for use in tax determination.
Release 11i tax codes and tax groups migrate to E-Business Tax as tax classification codes. Payables and
Purchasing tax codes migrate as tax classification codes under ZX_INPUT_CLASSIFICATIONS. Receivables
and Projects tax codes migrate as tax classification codes under ZX_OUTPUT_CLASSIFICATIONS. You can
set up additional tax classification codes for use with a migrated tax data model or as an additional determining
factor in tax determination.
ZX_WEB_EXP_TAX_CLASSIFICATIONS
Use the ZX_WEB_EXP_TAX_CLASSIFICATIONS lookup type to create tax classification codes for use in
tax determination for transactions originating from Internet Expenses.
ZX_EXEMPTION_REASON_CODE
Use the ZX_EXEMPTION_REASON_CODE lookup to create exemption reason lookup code for use in tax
exemptions. The exemption reason is a user-defined code that lets you monitor the use of customer or product
tax exemptions issued by the tax authority and applied to specific transactions.
When you set up a tax exemption, you can use the exemption reason to identify the reason for this exemption
or to monitor a customer's application for an exemption. At transaction time, E-Business Tax only considers
certain tax exemptions if the exemption reason and certificate number entered on the transaction line match the
exemption definition.
ZX_JEBE_VAT_TRANS_TYPE
Use the ZX_JEBE_VAT_TRANS_TYPE lookup type to create tax transaction types for use with tax rate
codes. You use transaction types when you set up a tax rate.
Tax rate transaction types represent local tax authority codes both for reporting purposes and for controlling
which rates appear on an invoice. See: Setting Up Tax Rates, Oracle E-Business Tax User Guide for more
information.
ZX_REGISTRATIONS_REASON
Use the ZX_REGISTRATIONS_REASON lookup type to create tax registration reason codes. You use
registration reason codes when you set up a tax registration to represent the reason for the tax registration.
The tax registration reason code is for tax reporting purposes only. See: Setting Up a Tax Registration, Oracle
E-Business Tax User Guide for more information.
ZX_REGISTRATIONS_TYPE
Use the ZX_REGISTRATIONS_TYPE lookup type to create tax registration type codes. You use tax
registration type codes when you set up a tax registration to organize your tax registrations into categories.
E-Business Tax provides these seeded tax registration types: CNPJ; CPF; CUIL; CUIT; DNI; NIT; OTHERS;
VAT. The tax registration types CPF, CNPJ, and OTHERS are used in tax registration number validation for
Brazil. All other seeded tax registration types, and the tax registration types that you define, are for tax
reporting purposes only.
See: Setting Up a Tax Registration, Oracle E-Business Tax User Guide for more information.
ZX_REGISTRATION_STATUS
Use the ZX_REGISTRATION_STATUS lookup type to create tax registration status codes. You use tax
registration status codes as determining factors in tax rules.
E-Business Tax provides these seeded tax registration types:
Lookup Code
Agent The company acts as a withholding agent for the tax authority for the applicable
Registered The company is registered for the applicable tax.
Not Registered The company is not registered for the applicable tax.
See: Setting Up Tax Rules, Oracle E-Business Tax User Guide for more information.
ZX_TAX_TYPE_CATEGORY
Use the ZX_TAX_TYPE_CATEGORY lookup type to create tax types. You use tax types when you set up a
tax.
You can use tax types to classifies taxes for tax reporting purposes. See: Setting Up Taxes, Oracle E-Business
Tax User Guide for more information.
The ZX_TAX_TYPE_CATEGORY lookup type contained these seeded tax types:
Lookup Code
Sales Direct taxes that are collected from the consumer by the supplier and paid to the tax
VAT Value added or cascading taxes.
Excise Taxes on the production and manufacture of goods.

Customs Duty Taxes charged on imported and exported products.
Environmental Taxes charged as a result of environmental regulations.
Setting Up TCA Geography Hierarchy

Set up and maintain the TCA geography hierarchy for each country where you have a tax requirement. The
TCA geography hierarchy provides a single reference source for all geographical and location-based
information for all E-Business Suite applications.
You use the TCA geography hierarchy in these cases:
 Taxes that are levied at a level lower than the country level, for example, state or provincial taxes.
 Tax characteristics, such as the tax rate, vary at a lower level than the country level.
You must set up and maintain the TCA geography hierarchy before you can perform these tax-related setups:
 Legal entities and establishments - Enter and maintain location information for first party legal
entities and the first party legal establishments. See: Setting Up Legal Entity for more information.
 Tax zones - Set up tax zones to represent regions according to a tax requirement. Tax zones let you
group together regions otherwise separated by geographical or political boundaries where a tax
treatment is identical throughout these regions. See: Setting Up Tax Zones, Oracle E-Business Tax
User Guide for more information.
 Tax regimes - Set up tax regimes for a country or tax zone. See: Setting Up Tax Regimes, Oracle E-
Business Tax User Guide for more information.
 Taxes - Set up taxes and specify the geographical level where each tax applies, such as a city tax or a
county tax. See: Setting Up Taxes, Oracle E-Business Tax User Guide for more information.
 Tax jurisdictions - Set up tax jurisdictions for a tax using geographies or tax zones. See: Setting Up
Tax Jurisdictions, Oracle E-Business Tax User Guide for more information.
 Tax rules - Use the Geography determining factor class to set up determining factor sets that use
geographical locations in tax rules. Use the User Defined Geography determining factor class to set up
determining factor sets that use tax zones in tax rules. See: Setting Up Tax Determining Factor
Sets, Oracle E-Business Tax User Guide for more information.
Use TCA administration to maintain these aspects of the geography hierarchy:
 Country structure - Set up and maintain the hierarchical structure of a country. The structure begins
with the largest geography type and ends with the smallest geography type. For example, the United
States structure is: State > County > City > Postal Code.
 Geography types - TCA provides seeded geography types for certain countries. The geography types
are used to create the geographical hierarchy of a country. Perform these tasks for geography types:
o If necessary, set up new geography types in accordance with the structure of a country.
o Set up and maintain aliases for specific Geography elements. An alias is an alternative
name for a geography type. You can use aliases as a part of your address validation.
o Define the contents of a geography type within the context of a country structure, for
example, the states belonging to the United States or the provinces belonging to
Canada.
 Address validations - Set up mappings and validations between country address formats and the TCA
geography hierarchy. TCA uses the definitions you provide to validate an address entry against the
geography hierarchy. You use address validation for taxes levied below the country level to verify that
it is a valid address for tax purposes.
For example, set up a list of Canadian provinces to verify each applicable address against a valid
province for the correct handling of Canadian PST.
Enable both the Geography Validation and Tax Validation options for each level for which you need
to create tax jurisdictions.
Related Topics
Setting Up Real-Time Address Validation, Oracle Trading Community Architecture Administration Guide
Administrating Geography Hierarchy, Oracle Trading Community Architecture Administration Guide
Geography Name Referencing Process, Oracle Trading Community Architecture Administration Guide
Setting Up Legal Entity

Use the Legal Entity Configurator to set up these parties:
 First party legal entity - The legal entities that represent your company.
 First party legal establishments - The legal establishments that have or require tax registrations,
either implied or explicit, from one or more tax authorities.
 Legal authorities - The legal authorities that represent the tax authorities in the tax regimes where
you do business.
When you set up a legal entity or establishment, you can also set up party tax profile details, including general
information, rounding rule, and tax registrations. See: Party Tax Profiles in Oracle E-Business Tax, Oracle E-
Business Tax User Guide for more information.
If you set up country default controls for the countries where you do business, then the applicable tax regime
and tax values default to the legal establishment tax registration record. See: Setting Up Country Default
Controls, Oracle E-Business Tax User Guide for more information.
Setting Up Legal Entities

Set up the legal entities that represent your company. You must set up your company as a legal entity before
you can perform these tax-related setups:
 Party tax profiles - Party tax profiles contain the information that relates to a party's transaction tax
activities, and identify the legal entity to the tax authorities. See: Setting Up a First Party Tax
Profile, Oracle E-Business Tax User Guide for more information.
 Configuration options - Configuration options indicate the tax regimes to which the legal entity is
subject. For each tax regime/legal entity assignment, the configuration option also defines the way in
which the legal entity uses tax configuration data for the regime. See: Setting Up Configuration
Options, Oracle E-Business Tax User Guide for more information.
 Configuration owner tax options - Configuration owner tax options let you set specific transaction
tax processing and control options for a combination of configuration owner and application event
class. See: Setting Up Configuration Owner Tax Options, Oracle E-Business Tax User Guide for more
information.
When you set up legal entities for your company, set the Transacting Entity option to Yes. See: Creating a
Legal Entity, Oracle Financials Implementation Guide for more information.
After you set up legal entities, set up the legal establishments that belong to the legal entity.
Setting Up First Party Legal Establishments

Set up a legal establishment record for each office, service center, warehouse and any other location within the
company that requires a registration with a tax authority for one or more taxes. You set up legal establishments
under a parent legal entity.
When you set up legal establishments, you can also perform these tax-related setups:
 Party tax profiles - Set up a party tax profile for each legal establishment. You can set up certain
details of the party tax profile when you create the legal establishment. See: Setting Up a First Party
Tax Profile, Oracle E-Business Tax User Guide for more information.
 Tax registrations - Set up tax registrations for each legal establishment. Depending on the applicable
tax requirements, you may need to set up more than tax registration for an establishment. You must
complete additional setup in E-Business Tax to set up a tax registration. See: Setting Up a Tax
Registration, Oracle E-Business Tax User Guide for more information.
Use the Associate Business Entities region to link a tax-related business entity to a legal establishment. See:
Creating Establishments, Oracle Financials Implementation Guide for more information.
Setting Up Legal Authorities

Set up a legal authority record for each tax authority that administers taxes in a tax regime where you do
business. While not mandatory, you can set up legal authority records before you perform these tax-related
setups:
 Tax authority tax profile - Set up tax authority tax profiles for your collecting, reporting, and issuing
tax authorities. A collecting tax authority manages the administration of tax remittances. A reporting
tax authority receives and processes all company transaction tax reports. An issuing tax
authority issues tax registration numbers and tax exemption certificates. See: Setting Up a Tax
Authority Tax Profile, Oracle E-Business Tax User Guide for more information.
 Basic tax configuration - The collecting and reporting tax authorities appear in the corresponding list
of values on these tax configuration setups:
o Tax regimes
o Taxes
o Tax jurisdictions
 Tax registrations - Enter the tax authority responsible for issuing the legal establishment tax
registration number. Update the collecting and reporting tax authorities that default from the tax
jurisdiction record. See: Setting Up a Tax Registration, Oracle E-Business Tax User Guide for more
information.
 Tax exemptions - Enter the tax authority that issues the tax exemption certificate. See: Setting Up
Tax Exemptions, Oracle E-Business Tax User Guide for more information.
When you set up a legal authority, set the Legislative Category to Transaction Tax. See: Creating and
Updating Legal Authorities, Oracle Financials Implementation Guide for more information.
Applying End Dates to Legal Entities

If you apply an end date to a legal entity or legal establishment, you must manually apply the same end date to
any related E-Business Tax entities that refer to the legal entity or establishment.
 Legal entities - Apply an end date to the related tax reporting types, party classifications, and
configuration options.
 Legal establishments - Apply an end date to the related tax reporting types, party classifications, and
tax registrations.
Setting Up Operating Units

Set up the operating units that you need to process your tax transactions. An operating unit is an organization
that uses Oracle Cash Management, Order Management and Shipping Execution, Oracle Payables, Oracle
Purchasing, or Oracle Receivables.
For tax-related transactions:
 Assign users to responsibilities associated with the operating units for the applicable applications.
 Assign user to an E-Business Tax responsibility. See: Setting Up Tax Users for more information.
 Assign operating units to the applicable primary ledgers. See: Setting Up Accounts and Accounting
Information.
You must set up and maintain operating units before you can perform these tax-related setups:
 Party tax profiles - Set up a tax profile for each operating unit. The tax profile indicates that the
operating unit either uses the tax configuration of the legal entity for transactions involving the legal
entity and tax regime, or acts as a configuration owner for the applicable tax regime. See: Setting Up
an Operating Unit Tax Profile, Oracle E-Business Tax User Guide for more information.
 Tax configuration options - Set up configuration options for applicable operating units when you set
up a tax regime or a party tax profile. The configuration option associates the operating unit with tax
regimes either to share the tax setup of the global configuration owner or to act as a configuration
owner and maintain a separate tax setup. See: Configuration Options in Oracle E-Business
Tax, Oracle E-Business Tax User Guide for more information.
 Tax accounts - You can set up tax accounts for a single operating unit, or you can share tax accounts
across multiple operating units. The accounting segments associated with the selected operating units
are available for tax account purposes. The calculated tax amounts post to the operating unit accounts
that you define. See: Setting Up Tax Accounts, Oracle E-Business Tax User Guide for more
information.
 Configuration owner tax options - Set up configuration owner tax options for a combination of
operating unit configuration owner and application event class. The configuration owner tax option
settings let you modify the manner in which tax data is configured. See: Setting Up Configuration
Owner Tax Options, Oracle E-Business Tax User Guide.
You can set up operating units using Oracle Human Resources, Oracle Inventory, or Oracle General Ledger.
The setup of operating units requires a number of prerequisite setups. The number and kind of prerequisite
setups depends upon your organization and your tax implementation.
Related Topics
Updating Establishments, Oracle Financials Implementation Guide
Setting Up Accounts and Accounting

Information
Set up accounts and accounting information for your tax transactions. You must set up and maintain
accounting information before you can set up tax accounts for the applicable operating units. You set up tax
accounts by operating unit for taxes, tax rates, tax jurisdictions, tax recovery rates, and tax registrations of first
party legal establishments. See: Setting Up Tax Accounts, Oracle E-Business Tax User Guide for more
information.
Review and complete these accounting setup tasks according to your requirements:
 Ledgers - Set up the chart of accounts, accounting calendar and currency for the primary ledger of
your legal entities and, if applicable, any secondary ledgers.
 Legal entity balancing segments - Define balancing segment values for the legal entities involved in
tax transactions.
 Accounting setup - Create an accounting setup for each legal entity with the ledger or ledgers that
you created, and assign the applicable operating units to the primary ledger.
 Complete the accounting setup - Complete the details of the accounting setups.
Related Topics
Setting Up General Ledger, Oracle General Ledger Implementation Guide
Creating Accounting Setups, Oracle Financials Implementation Guide
Setting Up TCA Classifications

Set up TCA classifications to classify third parties for tax purposes. You can define a TCA class category and
class codes specifically for use in tax determination. You can also use standard classifications, such as the US
Standard Industrial Classification (SIC) codes, and assign these codes a party fiscal classification.
You must set up and maintain TCA classifications before you can perform these tax-related setups:
 Party fiscal classifications - Set up party fiscal classifications for your customers and customer sites
and suppliers and supplier sites. Party fiscal classifications let you classify the customer/customer site
or supplier/supplier site according to categories you define for tax-related purposes. See: Setting Up
Party Fiscal Classifications, Oracle E-Business Tax User Guide for more information.
 Party tax profiles - Assign party fiscal classifications to third party tax profiles to use in tax
determination for invoices associated with the party. See: Setting Up a Third Party Tax
Profile, Oracle E-Business Tax User Guide for more information.
 Tax rules - Use the Party Fiscal Classification determining factor class to set up determining factor
sets for use in tax rules. The Party Fiscal Classification determining factor class uses the party fiscal
classification type defined for a TCA classification to identify the parties involved in a transaction.
See: Setting Up Tax Determining Factor Sets, Oracle E-Business Tax User Guide for more
information.
Use TCA administration to set up and maintain classifications for use in party fiscal classifications:
 Class category - Set up a class category to represent the party fiscal classification type. These rules
apply to enabling class category options for use with fiscal classifications:
o Allow Multiple Parent Codes - You cannot enable this option. E-Business Tax does
not allow the class codes in a hierarchy to have multiple parents.
o Allow Parent Code Assignment - You can enable this option. E-Business Tax lets you
use the parent code to represent a class code within the hierarchy.
o Allow Multiple Class Code Assignments - You can enable this option. E-Business
Tax lets you assign more than one class code to the same entity within the hierarchy.
 Class codes - Set up class codes under the class category to represent the detailed classifications that
belong to this class category. When you set up a party fiscal classification using a TCA class category,
the related class codes by default become party fiscal classification codes.
Setting Up Oracle Inventory

Use the Inventory Item Category functionality in Oracle Inventory to model product fiscal classifications. You
can create either a single product fiscal classification type or a hierarchy of product fiscal classification types
that matches the segments of the Inventory category.
You can either use existing Inventory category sets or set up new Inventory category sets for use with product
fiscal classifications. After you set up Inventory item categories and associate them with product fiscal
classifications, the corresponding product fiscal classification code defaults to the transaction line for any item
that belongs to the inventory category set. See: Setting Up Product Fiscal Classifications, Oracle E-Business
Tax User Guide for more information.
You can also specify a default Inventory category set for a given country. The Inventory category associated
with the item for this default category set defaults to the transaction line. See: Setting Up Country Default
Controls, Oracle E-Business Tax User Guide for more information.
To model Inventory item categories for product fiscal classifications, you create categories and category sets
and associate product fiscal classification types to the Inventory item category set.
The Inventory setup tasks to model product fiscal classifications are:
 Define Inventory Value Set

 Define Inventory Item Category Structure
 Define Category Set
 Define Inventory Categories
 Associate Inventory Items to Category Sets
You complete this setup task flow for each Inventory-based product fiscal classification type that you plan to
define.
Define Inventory Value Set

Define a value set with the value type that the segments of the item category structure will use. Select a value
type for the product fiscal classification codes that you intend to define, for example, alphanumeric code or
numeric codes.
Define Inventory Item Category Structure

Define a category structure for the Inventory category set that you will use to create product fiscal
classification types. If you are modeling a hierarchical classification system, then create a segment for each
level in the hierarchy.
Set subcategory segments as Not Required.
Define Category Set

Define a category set for the category structure that you created. Use a naming convention that corresponds to
the product fiscal classification type that you intend to create.
Define Inventory Categories

Define the values for each segment of the category structure. The values represent the product fiscal
classification codes.
This is a sample representation of numeric codes for the Brazilian CNAE and NCM product fiscal
classification:
Structure Category
BR CNAE 3901... Polymers of ethylene, in prim
BR CNAE 3901.10.10 Linear polyethylene
BR CNAE 3901.10.90 Other
Associate Inventory Items to Category Sets

Assign one or more Inventory categories belonging to the category set to the Inventory items that you intend to
use on transactions.
After you set up an Inventory item category set, use E-Business Tax to set up one or more product fiscal
classification types and associate them with the Inventory item category set. If you are setting up a hierarchy of
product fiscal classification types, define the starting point and the number of digits that make up each level
code value in the hierarchy. See: Setting Up Product Fiscal Classifications, Oracle E-Business Tax User
Guide for more information.
Country Setup Examples

This chapter contains sample tax configuration setup data for these tax regimes:
 United Kingdom Value Added Tax (VAT)
 Canadian Goods and Services Tax (GST) and Harmonized Sales Tax (HST)
 United States Sales and Use Tax
These examples are intended to demonstrate typical setups, option settings, and interdependencies
for each tax regime. They are not intended to provide an example of best practices in all cases. The
actual details of your own tax configuration setup will depend on your company's specific internal
and legal tax requirements.
United Kingdom Value Added Tax (VAT)

In the United Kingdom, Value Added Tax (VAT) is a tax on consumer expenditure that is charged on
most business transactions made in the United Kingdom and the Isle of Man. VAT is also charged
on goods and some services imported from places outside the European Union, and on goods and
some services coming into the United Kingdom from the other European Union countries.
The current rates for VAT are:
 Standard rate of 17.5%.
 Reduced rate of 5% for certain goods and services, such as domestic fuel and energy saving materials.
 Zero rate.
Some goods and services are exempt from VAT. In addition, there is a zero rate for United Kingdom
companies that supply goods and services to VAT-registered customers in other European Union
Member States, provided the company meets the appropriate conditions.
The example in this section is based on the Customs and Excise Management Act 1979.
Setup Features
This tax setup example is for a first party registered in the United Kingdom and dealing with
domestic, intra-EU and extra-EU transactions. Setup features include:
 There are five possible tax statuses for VAT: standard, reduced, exempt, zero, and Intra-European
Union zero. The Intra-European Union zero status came into effect in 2000. There is a separate tax
status record for each tax status. All records have the same tax regime code, configuration owner, and
tax, as well as the same default controls.
Although you do not need to report exempt transactions, this example illustrates the creation of a
specific Exempt tax status (with associated zero rate) to allow simple identification for reporting or
audit purposes. The separate Intra-European Union zero status also allows for easy identification and
reporting.
 A company of this kind can normally recover 100%, with standard exceptions where 0% recovery is
permitted.
 The setup uses tax rules rather than tax exceptions to define exempt and reduced rate goods.
 The setup uses tax rules rather than tax exemptions to define exempt customers, such as diplomatic
and military customers.
 The exchange rate type is User, to take into account the different options available to the company for
expressing foreign currency transactions.
Inventory Category Sets and Category Codes

These Inventory category codes are used to identify goods and services for use in tax rules.
See: Setting Up Oracle Inventory for information about creating Inventory item categories for product
fiscal classifications.
Inventory Category Set
Category Set Structure Name
GB VAT PRODUCT CLASSIFICATION Fiscal Classification

GB VAT RECOVERY Fiscal Classification
GB VAT RECOVERY Fiscal Classification
Intended Use
Party Tax Profile: Tax Authority

You first set up the United Kingdom tax authority--HM Revenue and Customs--as a legal authority
using the Oracle Legal Entity Manager, and then create a party tax profile for the legal authority.
Legal A
Field
Organization Name HM Revenue and Customs
Legislative Category Transaction Tax
Country United Kingdom
Address1 VAT Central Unit Alexander
City Southend-on-Sea
Postal Code SS99 1AA
Status Active
Primary Address Yes
Tax Au
Field
Party Type Tax Authority
Party Name HM Revenue and Customs
Address VAT Central Unit, Alexander House, Southend-on
Country Name United Kingdom
Set as a Collecting Authority Yes
Set as a Reporting Authority Yes
Tax Zones
The tax zone type European Economic Regions contains a tax zone record for each country in the
European Union. The setup values are the same for each country, except for the Geography Name
field.
Field
Tax Zone Name European Economic Commun
Tax Zone Code EU
Start Date 01-Jan-05
Tax Zone Type Economic Regions
Code Type Tax Geography Code
Geography Type Country

Geography Name Austria
Belgium
...
United Kingdom
Tax Regime Setup

Field Value
Main Information
Tax Regime Code GB VAT
Name GB VAT
Regime Level Country
Controls
Allow Tax Recovery Yes
Allow Override and Entry of Inclusive Tax Lines Yes
Defaults
Tax Currency GBP
Minimum Accountable Unit .01
Rounding Rule Nearest

Tax Precision 2
Allow Tax Inclusion Standard Non-Inclusive Handling
Allow Multiple Jurisdictions No
Allow Tax Rounding Override Yes
Configuration Options (if defined from tax regime)
Party Name Party name
Configuration for Taxes and Rules Common Configuration
Tax Setup
Field Value
Main Information
Configuration Owner Global Configuration Owner
Tax Source Create a new tax
Tax GB VAT
Tax Name GB VAT
Tax Type VAT
Effective From 18-Jun-1979
Geography Type Country

Parent Geography Type Country
Parent Geography Name United Kingdom
Controls
Allow Override for Calculated Tax Lines Yes
Tax Account Controls
Tax Accounts Creation Method Create Tax Accounts
Tax Recovery Controls
Allow Tax Recovery Rate Override Yes
Allow Primary Recovery Rate Determination Rules Yes
Allow Secondary Recovery Rate Determination Rules No
Tax Status Setup

Field Value
Main Information

Standard Status
Tax Status Code GB VAT STANDARD
Name GB VAT Standard
Reduced Status
Tax Status Code GB VAT REDUCED
Name GB VAT Reduced
Exempt Status
Tax Status Code GB VAT EXEMPT
Name GB VAT Exempt
Zero Status
Tax Status Code GB VAT ZERO
Name GB VAT Zero
Intra EU Zero Status
Tax Status Code GB VAT INTRA EU ZERO
Name GB VAT Intra EU Zero
Default Controls (all statuses)
Allow Tax Exemptions No

Allow Tax Exceptions No
Tax Jurisdiction Setup

This setup is for the one tax jurisdiction--the United Kingdom--for GB VAT.
Field
Tax Jurisdiction Code
Tax Jurisdiction Name
Tax Regime Code
Tax
Geography Type
Parent Geography Type
Parent Geography Name
Geography Name
Inner City Jurisdiction
Precedence Level
Collecting Tax Authority
Reporting Tax Authority
Effective From
Set as Default Tax Jurisdiction

Default Effective From
Tax Recovery Rate Setup

This example illustrates setup for the VAT recovery rates of standard and zero.
In some instances you may also need to set up a partial rate. A company's actual rate for partial
recovery will depend on the combination of its taxable and exempt statuses, as agreed upon with
HM Revenue and Customs.
Field Value
Main Information
Tax Regime Name GB VAT
Standard Rate
Tax Recovery Rate Code GB VAT STANDARD REC RATE
Percentage Recovery Rate 100
Zero Rate
Tax Recovery Rate Code GB VAT ZERO REC RATE

Tax Rate Setup
This example shows the standard VAT rate. There are two rate periods to reflect the rate change
After March 1991.
Field Value
Main Information
Tax Regime Code GB VAT Tax Status N
Tax Regime Name GB VAT Tax Rate Cod
Tax GB VAT Configuration
Tax Name GB VAT Rate Type
Tax Status Code GB VAT STANDARD
Rate Period 1
Percentage Rate 15 Default Effec
Effective From 18-Jun-1979 Default Effec
Effective To 31-Mar-1991 Allow Tax Inc
Default Recovery Rate Code GB VAT STANDARD REC RATE Allow Overrid
Recovery Type STANDARD Allow Ad Hoc
Default Recovery Settlement Immediate Adjustment fo
Set as Default Rate Yes
Rate Period 2
Percentage Rate 17.5 Default Effec
Effective From 1-Apr-1991 Allow Tax Inc
Default Recovery Rate Code GB VAT STANDARD REC RATE Allow Overrid
Recovery Type STANDARD Allow Ad Hoc
Default Recovery Settlement Immediate Adjustment fo
Party Tax Profile Setup

Field
First Party Legal Entity
Party Type First Party Lega
Main Information
Set for Self Assessment/Reverse Charge Yes
Rounding Level Header
Configuration Options (if defined from party tax profile)
Configuration for Taxes and Rules Common Config
Field Value
First Party Legal Establishment
Party Type First Party Legal Establishment C
Tax Registration
Tax Regime Code GB VAT T
Tax GB VAT E
Tax Registration Number GB123456789 R
Set as Default Registration Yes S
Tax Registration Status REGISTERED S
Source Explicit
Product Inventory Fiscal Classifications

This example shows the setup for Inventory-based product fiscal classifications. These fiscal
classifications are used in the creation of tax rules for the tax GB VAT.
GB VAT PRODUCT
Fiscal Classification Type Code Start Position Number of
GB VAT PRODUCT LEVEL 1 1 5
GB VAT PRODUCT LEVEL 2 1 7
GB VAT RE
Fiscal Classification Type Code Start Position Number of

GB VAT RECOVERY 1 5
Product Intended Use Fiscal Classifications

This example shows the setup for an Inventory-based product intended use fiscal classification type.
This fiscal classification type is used in the creation of tax rules for the tax GB VAT.
Fiscal Classification Type Code Effective From Invento
INTENDED_USE 18-Jun-1979 INTENDED_USE
Tax Rule Defaults

This example shows the default values that are entered for each rule type for the creation of tax
rules for the tax GB VAT. In tax rules, the default value is the most commonly expected result. E-
Business Tax uses this value on a transaction when there are no rules that determine another result.
Default Values for G
Rule Type
Determine Place of Supply S
Determine Tax Applicability A
Determine Tax Registration B
Determine Tax Status G
Determine Tax Rate G
Determine Taxable Basis S
Calculate Tax Amounts S

Tax Determining Factor Sets
This example shows tax determining factor sets that are used to create tax rules for the tax GB VAT.
There is one determining factor set per rule type. Each determining factor set contains all the
determining factors necessary to create tax conditions for the corresponding tax rule.
None of the determining factors in these sets are set as Required.
GB VAT REG
Determining Factor Class Clas
User Defined Geography Ship From
Geography Ship From
Geography Ship To
Transaction Input Factor
Registration Bill From Party
Transaction Generic Classification
GB VAT Plac
User Defined Geography Ship From
Geography Ship From
User Defined Geography Bill From
Geography Ship To

GB VAT A
Determining Factor Class Class Q
Geography Ship From
Geography Ship To
Geography Bill From
Geography Bill To
GB VAT
Geography Ship From
User Defined Geography Ship To
Geography Ship To
Product - Inventory Based
Registration Bill To Party

GB VAT Rec
Determining Factor Class Class Q
Product - Inventory Based
Tax Condition Sets

These examples show the tax condition sets that are used to create tax rules. Each tax condition set
makes use of one of the tax determining factor sets created for tax rules for the tax GB VAT. The tax
condition sets in these examples only show the determining factors that are actually used to create
tax conditions; the other determining factors in the tax determining factor set (if any) are considered
to be set to Ignore Condition.
GB Intra EU Goods Purchase and Reverse Charge

This example uses two tax condition sets to process a purchase by a UK customer from a supplier in
an EU country, and to determine a standard reverse charge on the goods shipped from an EU
country to the UK. The UK customer is GB VAT registered, but the supplier is non-GB VAT
registered.
The tax condition set GB INTRA EU GOODS PURCHASE uses the tax determining factor set GB
VAT PLACE OF SUPPLY in the Determine Place of Supply rule. The tax condition set GB GOODS
PURCHASE REVERSE CHARGE uses the tax determining factor set GB VAT REGISTRATION in
the Determine Tax Registration rule.
GB INTRA EU GO
Determining Factor Class Class Qualifier Determini
User Defined Geography Ship From Economic Regions
Geography Ship From Country
Geography Ship To Country

Transaction Generic Classification Transaction Business C
Registration Bill From Party Registration Status
Transaction Input Factor Product Type
GB GOODS PURCHAS
User Defined Geography Ship From Economic Regions
GB INTRA EU AND DOMESTIC SERVICES

This example uses the tax condition set GB INTRA EU AND DOMESTIC SERVICES to process
service transactions where the services are not explicitly defined, and thus the place of supply is
deemed to be Where the Supplier Belongs.
The tax condition set GB INTRA EU AND DOMESTIC SERVICES uses the tax determining factor
set GB VAT PLACE OF SUPPLY in the Determine Place of Supply rule.
GB INTRA EU AND DO
Determining Factor Class Class Qualifier Determining
User Defined Geography Bill From Economic Regions

GB DOMESTIC GOODS BILL FROM NON REG

This example uses the tax condition set GB DOMESTIC GOODS BILL FROM NON REG to
determine that a supplier has to be registered for UK VAT in order to charge UK VAT on goods. If
the supplier is not registered, then VAT is not applicable.
The tax condition set GB DOMESTIC GOODS BILL FROM NON REG uses the tax determining
factor set GB VAT APPLICABILITY in the Determine Tax Applicability rule.
GB DOMESTIC GOODS
Determining Factor Class Class Qualifier
Registration Bill From Party Registration Sta
GB DOMESTIC SERVICES BILL FROM NON REG

This example uses the tax condition set GB DOMESTIC SERVICES BILL FROM NON REG to
determine that a supplier has to be registered for UK VAT in order to charge UK VAT on services. If
the supplier is not registered, then VAT is not applicable.
The tax condition set GB DOMESTIC SERVICES BILL FROM NON REG uses the tax determining
factor set GB VAT APPLICABILITY in the Determine Tax Applicability rule.
GB DOMESTIC SERVICE
Geography Bill From Country

Geography Bill To Country
Registration Bill From Party Registration Sta
GB INTRA EU GOODS SALE ZERO RATE

This example uses the tax condition set GB INTRA EU GOODS SALE ZERO RATE to determine
when a zero rate is applicable for the Determine Tax Status rule.
The tax condition set GB INTRA EU GOODS SALE ZERO RATE uses the tax determining factor set
GB VAT STATUS in the Determine Tax Status rule.
GB INTRA EU GOOD
User Defined Geography Ship To Economic Regions
Registration Bill To Party Registration Status
GB GOODS REDUCED RATE

This example uses the tax condition set GB GOODS REDUCED RATE to use a reduced rate for
sales of reduced rate goods.
The tax condition set GB GOODS REDUCED RATE uses the tax determining factor set GB VAT
STATUS in the Determine Tax Status rule.
GB GOODS RE
Determining Factor Class Class Qualifier D
Product - Inventory Linked GB VAT Product
GB SERVICES REDUCED RATE

This example uses the tax condition set GB SERVICES REDUCED RATE to use a reduced rate for
sales of reduced rate goods.
The tax condition set GB SERVICES REDUCED RATE uses the tax determining factor set GB VAT
GB SERVICES R
Determining Factor Class Class Qualifier Det
Product - Inventory Linked GB VAT Product Le
GB GOODS ZERO RATE

This example uses the tax condition set GB GOODS ZERO RATE to use a zero rate for sales of
zero-rated goods.
The tax condition set GB GOODS ZERO RATE uses the tax determining factor set GB VAT
GB GOODS
Product - Inventory Linked GB VAT Produ
GB SERVICES ZERO RATE

This example uses the tax condition set GB SERVICES ZERO RATE to use a zero rate for sales of
zero-rated services.
The tax condition set GB SERVICES ZERO RATE uses the tax determining factor set GB VAT
GB SERVICES
Determining Factor Class Class Qualifier D
Product - Inventory Linked GB VAT Product
GB EXPORT GOODS OUTSIDE EU

This example uses the tax condition set GB EXPORT GOODS OUTSIDE EU for transactions
involving the export of goods to non-EU countries.
The tax condition set GB EXPORT GOODS OUTSIDE EU uses the tax determining factor set GB
VAT STATUS in the Determine Tax Status rule.
GB EXPORT GOO
Determining Factor Class Class Qualifier Determining Fa
User Defined Geography Ship To Economic Regions
GB GOODS EXEMPT RATE

This example uses the tax condition set GB GOODS EXEMPT RATE for the sale of goods with a
zero-rated exempt status.
The tax condition set GB GOODS EXEMPT RATE uses the tax determining factor set GB VAT
GB GOODS E
Product - Inventory Linked GB VAT Pr
GB SERVICES EXEMPT RATE

This example uses the tax condition set GB SERVICES EXEMPT RATE for the sale of services with
a zero-rated exempt status.
The tax condition set GB SERVICES EXEMPT RATE uses the tax determining factor set GB VAT
GB SERVICES
Product - Inventory Linked GB VAT Prod
GB PURCHASE LINKED TO EXEMPT SALE ZERO REC

This example uses the tax condition set GB PURCHASE LINKED TO EXEMPT SALE ZERO REC
for purchases linked to exempt sales with zero recovery.
The tax condition set GB PURCHASE LINKED TO EXEMPT SALE ZERO REC uses the tax
determining factor set GB VAT RECOVERY RATE in the Determine Recovery Rate rule.
GB PURCHASE LINKED TO
Determining Factor Class Class Qualifier Determ
Transaction Input Factor Intended Use
GB PRODUCT ZERO RECOVERY

This example uses the tax condition set GB PRODUCT ZERO RECOVERY for transactions on
certain goods and services that have zero recovery.
The tax condition set GB PRODUCT ZERO RECOVERY uses the tax determining factor set GB
VAT RECOVERY RATE in the Determine Recovery Rate rule.
GB PRODUCT ZE
Product - Inventory Linked GB VAT Re

Tax Rules
These examples show the tax rules created for the tax GB VAT. The tax rules make use of the tax
determining factor sets and tax condition sets created for GB VAT. Refer to these sets to understand
their usage in each tax rule.
For each tax condition used in a tax rule, the rule result applies when its corresponding tax condition
is evaluated as true.
Determine Place of Supply

This tax rule determines the place of supply on Intra-EU transactions for goods and services.
Determine Pla
Tax Rule Code Effective From Conditi
GB VAT PLACE OF SUPPLY 1-Jan-2003 GB INTRA EU GOODS PURCHASE
GB INTRA EU AND DOMESTIC SER
Determine Tax Applicability

This tax rule determines whether a supplier is registered for UK VAT in order to charge VAT on
goods and services.
Determine Ta
Tax Rule Code Effective From
GB VAT APPLICABILITY 1-Jan-2003 GB DOMESTIC GOODS BILL
GB DOMESTIC SERVICES BI
Determine Tax Registration

This tax rule determines the tax registration when a UK VAT registered customer purchases goods
from a non-UK VAT registered supplier, where the goods are sent from an EU country outside the
UK to the UK.
Determine Tax
GB VAT REGISTRATION 1-Jan-2003 GB GOODS PURCHASE
Determine Tax Status

This tax rule determines the tax status of the transaction. Each rule result indicates the tax status to
use on the transaction if the corresponding condition is evaluated as true.
Determine
Tax Rule Code Effective From Condi
GB VAT STATUS 1-Jan-2003 GB INTRA EU GOODS SALE ZERO RATE
GB EXPORT GOODS OUTSIDE EU
GB GOODS ZERO RATE
GB SERVICES ZERO RATE
GB GOODS EXEMPT RATE
GB SERVICES EXEMPT RATE
GB GOODS REDUCED RATE
GB SERVICES REDUCED RATE
Determine Recovery Rate

This tax rule derives a zero recovery rate for purchases linked to exempt sales with zero recovery.
Determine Re
GB VAT RECOVERY RATE 1-Jan-2003 GB PURCHASE LINKED TO EXEMPT
Canadian Sales Tax

In Canada, sales taxes exist at the federal level and at the provincial level. Goods and Services Tax
(GST) is a federal tax levied in provinces and territories across Canada on many consumer products
and professional services. Provincial Sales Tax (PST) varies by province. The tax rates within each
province apply to the value of goods or services before GST is applied. The only exceptions are
Quebec and Prince Edward Island, where the sales tax applies to the value of goods or services
after GST is applied.
A federal and provincial blended tax called Harmonized Sales Tax (HST) is levied in the three
participating provinces of Newfoundland and Labrador, Nova Scotia, and New Brunswick. The HST
operates as a single rate of 14%, of which six percent (6%) represents the federal component and
eight percent (8%) the provincial component.
The recovery of tax is made through a rebate and/or an Input Tax Credit (ITC), depending on
whether the purchases are intended for commercial or non-profit activities. Some goods and
services are exempt from GST and HST, such as health and educational services.
Taxable goods and services are subject to one of the following statuses:
 Taxable: GST - 6%; HST - 14%
 Zero-rated
 Exempt
Tax status is generally determined by product. For the consumer, there is no difference between
zero-rated and exempt goods and services: the consumer either pays tax or not. Although GST and
HST are not charged on zero-rated goods and services, the tax registrant can claim input tax credits
to recover the GST or HST paid or owed on purchases and the expenses incurred to provide them.
The example in this section is based on the changes to GST and HST rates effective July 1, 2006.
Examples
This section provides four examples of Canadian tax setup:
 Ontario Example 1 - GST and PST are typically applicable on most goods and services. In this
example, a tax is not applicable on a transaction. Since you will typically set the tax applicability of a
tax to Applicable, you will need to define a tax rule to identify when a transaction is not applicable.
 Ontario Example 2 - The taxable basis for tax calculation is typically (selling price) * (tax rate). In
this example, the taxable basis is reduced in Ontario for the purchase of portable homes to be used for
construction purposes.
 Quebec Example 1 - In Quebec, PST is calculated based on the selling price plus GST.
 Quebec Example 2 - In Quebec, PST is applied on most goods and services. For transactions relating
to resale, you can fully recovery the PST.
Prerequisites
Before you can set up the E-Business Tax tax configuration for these examples, you may need to
complete one or more of these tasks:
 Set up the legal entity for your Canadian company.
 Set up the legal establishment for your Canadian company.
 Set up legal authorities for Canada Revenue Agency, Ontario Ministry of Finance, and the Ministere
du Revenu du Quebec.
Tax Regime Setup

There are two tax regimes required for the above examples:
 CA GST HST, that contains the CA GST tax (it will also include CA HST, which is not included in
these examples).
 CA PST that contains the CA PST tax. The tax regime uses cross-regime compounding for provinces
such as Quebec, where GST is compounded with PST.
The CA GST HST regime has a compounding precedence of 1; the CA PST regime has a
compounding precedence of 2.
Field Value
Main Information
Tax Regime Code CA GST HST
Name CA GST HST

Controls
Defaults
Tax Currency CAD
Tax Precision 2
Allow Multiple Jurisdictions Yes
Field Value
Main Information
Tax Regime Code CA PST
Name CA PST
Controls
Defaults
Tax Currency CAD
Tax Precision 2
Allow Multiple Jurisdictions Yes

The tables below describe the first party legal establishment setup and tax registration setups for
Canada, Ontario, and Quebec. For Ontario Example 1, the registration status of the legal
establishment is a factor in determining whether the GST and/or PST are applicable. For this
example, the registration for this legal establishment will include GST across Canada, PST
registration in Ontario, and PST registration in Quebec.
You also need to create party tax profiles for each of the three taxing authorities: Canada Revenue
Agency for the GST across Canada, Ontario Ministry of Finance for the Ontario PST, and Ministere
du Revenu du Quebec for the Quebec PST. You need to set up each of these tax authorities in the
Legal Entity Manager as a legal authority for transaction tax. The tax authorities are all both
collecting and reporting tax authorities.
Field Value
Party Type First Party Legal Establishment
Tax Registrations
Canada Registration
Tax Registration Number 10810 2831 RT0001
Set as Default Registration Yes
Tax Registration Status REGISTERED
Issuing Tax Authority Canada Revenue Agency
Ontario Registration
Tax Registration Number 9800 1120
Set as Default Registration No
Issuing Tax Authority Ontario Ministry of Finance
Quebec Registration
Tax Registration Number 1515151515 TQ 0001
Set as Default Registration NO
Issuing Tax Authority Ministere du Revenu du Quebec
Tax Setup
Field Value
Main Information
Tax CA GST
Tax Name CA GST
Tax Type VAT
Effective From 1-Jan-2001
Geography Type Province
Parent Geography Name Canada

Compounding Precedence 1
Controls
Allow Entry of Manual Tax Lines Yes
Allow Tax Recovery Rate Override Yes
Allow Primary Recovery Rate Determination Rules Yes
Allow Secondary Recovery Rate Determination Rules Yes
Allow Tax Rate Rules No
Tax Status Setup

Create two standard statuses, one for GST (CA GST STANDARD) and one for PST (CA PST
STANDARD). The two statuses have the same settings.
Field Value
Main Information
Standard Status
Tax Status Code CA GST STANDARD
Name CA GST Standard
Default Controls
Allow Tax Exemptions No
Allow Tax Exceptions No

Tax jurisdiction setup in Canada requires a separate record for each province. In addition, provinces
that apply GST and PST separately require two tax jurisdiction records. Different PST tax rates can
apply at the jurisdiction level. Because both GST and PST apply to all transactions, neither
jurisdiction takes precedence or is set as a default jurisdiction.
This example shows the GST and PST tax jurisdictions for Ontario.
Ontario Tax Jurisdiction for GST

Field
Tax Regime Code
Tax
Geography Type
Geography Name
Precedence Level
Effective From
Ontario Tax Jurisdiction for PST

Field
Tax Regime Code
Tax
Geography Type

Geography Name
Precedence Level
Effective From
Tax Recovery Rate Setup

The Quebec PST recovery example uses a standard 100% recovery rate. Actual reduced rates at
the provincial level are agreed upon with the provincial tax authority.
Field Value
Main Information
Tax Regime Name CA PST
Standard Rate
Tax Recovery Rate Code CA PST STANDARD REC RATE

Tax Rate Setup

This example uses the standard GST rate of 7%. The standard PST for most provinces in Canada is
7%; however, the rate is 7.5% in Quebec and 8% in Ontario. As such, the PST tax rates for Quebec
and Ontario will also specify the tax jurisdiction. Additional rates may also apply at the provincial
level.
Field Value
Main Information
Tax Regime Code CA GST HST Tax Status Name
Tax Regime Name CA GST HST Tax Rate Code
Tax CA GST Configuration Owner
Tax Name CA GST Rate Type
Tax Status Code CA GST STD
Rate Period
Percentage Rate 6 Default Effective Fro
Effective From 1-Jul-2006 Allow Tax Inclusion
Default Recovery Rate Code CA GST STD REC RATE Allow Override and E
Recovery Type STANDARD Allow Ad Hoc Rate
Default Recovery Settlement Immediate Adjustment for Ad H

Fiscal Classification Setup
You must set up these fiscal classifications for the corresponding examples:
 Product Intended Use - Set up these Inventory-based product intended use fiscal classifications.
Since these are Inventory-based, you must first create Inventory category codes for these fiscal
classifications:
o Ontario Example 2 - Create an intended use fiscal classification for construction

purposes.
o Quebec Example 2 - Create an intended use fiscal classification for resale purposes.
 Non-Inventory Based Product Fiscal Classification - For Ontario Example 2, create a non-
Inventory-based product fiscal classification for portable homes.
Tax Formulas Setup

For Ontario Example 2, create a tax formula to represent the reduced taxable basis.
Field
Tax Formula Code CA TB PST ON MOBILE HOME
Name CA Taxable Basis PST ON Mobile Hom
Formula Type Taxable Basis
Taxable Basis Type Line Amount
Regime Code CA PST
Tax CA PST
Base Rate Modifier -50
For Quebec Example 1, create a tax formula to represent that PST is calculated upon the sale price
plus GST.
Field
Tax Formula Code CA TB
Name CA Ta
Formula Type Taxab
Taxable Basis Type Line A
Regime Code CA PS
Tax CA PS
Effective From 1-Jan-
Compounding Regime Code CA GS
Compounding Tax CA GS
Compounding Rule Add
Enforce Compounding Yes
Tax Zone Setup

Create a tax zone to group together provinces that share the same compounding rule for PST. In
this case, both Quebec and Prince Edward Island calculate PST on the selling price plus GST.
Field
Tax Zone Type
Country
Province Zone Creation Allowed

Tax Zone Name
Tax Zone Code
Start Date
Code Type
Geography Type
Geography Names
Tax Rule Defaults

Tax rule defaults simplify the tax rule setup and reduce the number of rules by identifying the most
common value for each rule type. For example, if GST is applicable on most transactions, then the
default value for the rule type Determine Tax Applicability for the tax CA GST is Applicable.
Rule Type
Determine Place of Supply CA GST, CA PST
Determine Tax Applicability CA GST, CA PST
Determine Tax Registration CA GST, CA PST
Determine Tax Status CA GST
Determine Tax Status CA PST
Determine Tax Rate CA GST
Determine Tax Rate CA PST
Determine Taxable Basis CA GST, CA PST
Calculate Tax Amounts CA GST, CA PST

Tax Rules Setup - Ontario Example 1
Since you will typically set the tax applicability of a tax as Applicable, you will need to define a
Determine Tax Applicability tax rule to identify when a transaction is not applicable for GST and
PST. In this particular example, the tax is not applicable when the Ship From Party is Not Registered
for the tax, and the transaction is a sales transaction.
Tax Determining Factor Set

This table describes the tax determining factor set to use with this tax rule. This tax determining
factor set identifies the registration status of the ship from party and the type of transaction.
Registration Ship From Party
Tax Condition Set

This table describes the tax condition set to use with this tax rule. This tax condition set indicates
that the Ship From Party is Not Registered for this tax, and that this rule will apply to Sales
Transactions.
Determining Factor Class Class Qualifier Determinin
Registration Ship From Party Registration Status
Transaction Generic Classification Transaction Business Ca
If the values of this tax condition set are evaluated as true, then the result of the Determine Tax
Applicability rule is Not Applicable.
Tax Rules Setup - Ontario Example 2

Because the taxable basis formula for most transactions is (line amount) * (tax rate), you will need to
define a Determine Taxable Basis tax rule to identify when a different taxable basis is needed and
which taxable basis tax formula to use. In this example, the taxable basis in Ontario is reduced for
the purchase of mobile homes that are used for construction purposes.
factor set identifies the shipping destination, the product, and the intended use of the product.
Geography Ship To
Product - Non-Inventory Based Level 3
Tax Condition Set

that the shipping destination is Ontario, the product is a portable home, and that the portable home it
will be used for construction purposes.
Determining Factor Class Class Qualifier Determining Factor Name
Geography Ship To Province
Product - Non-Inventory Based Level 3 Product Category
If the values of this tax condition set are evaluated as true, then the result of the Determine Taxable
Basis rule is the tax formula CA TB PST ON MOBILE HOME. This formula is used to determine the
taxable basis, which results in a 50% reduction in the taxable basis.
Tax Rules Setup - Quebec Example 1

As mentioned above, the taxable basis formula for most transactions is (line amount) * (tax rate).
Since the PST in Quebec is calculated on the selling price plus GST, you will need to define a
Determine Taxable Basis tax rule to identify when a different taxable basis is needed and which
taxable basis tax formula to use.

factor set identifies the shipping destination, the product, and the intended use of the product.
Geography Ship To
Tax Condition Set

that the shipping destination is either of 2 provinces that apply PST on the sale price plus GST.
Determining Factor Class Class Qualifier Determining F
User Defined Geography Ship To CA GST Incl
If the values of this tax condition set are evaluated as true, then the result of the Determine Taxable
Basis rule is the tax formula CA TB GST INCLUDED. This formula is used to determine the taxable
basis, which results in PST calculated on the sale price plus GST Note that this tax rule uses the
same tax determining factor set as in Ontario Example 2 for tax rule efficiency.
Tax Rules Setup - Quebec Example 2

This tax rule setup identifies when tax recovery is applicable and which tax recovery rate applies.
The example refers to setting up a Determine Recovery Rate tax rule for resale transactions in
Quebec.

factor set identifies the shipping destination and the intended use of the product.
Geography Ship From
Geography Ship To
Geography Ship To
Party Fiscal Classification Bill From Party
Party Fiscal Classification Ship To Party
Tax Condition Set

that the shipping destination is either of 2 provinces that apply PST on the sale price plus GST and
that the product is intended for resale.
Determining Factor Class Class Qualifier Determinin
Geography Ship To Province
If the values of this tax condition set are evaluated as true, then the result of the Determine
Recovery Rate rule is the tax recovery rate CA PST STD REC RATE.
United States Sales and Use Tax
United States Sales and Use Tax is a tax levied on the end consumer, with the business serving as
the collection agent for the tax authority. Any company receiving goods within a state must either
pay sales tax on receipt or self-accrue a use tax, usually to the same value. The self-accrual scheme
ensures that the state receives income independent of the tax registration of the business.
The details of rates and regulations surrounding sales and use tax vary from state to state, and are a
matter of state and local law and court cases. Exemptions are normally available in each state,
including, but not limited to: resales, manufacturing, research and development, non-profit or exempt
organizations, and governmental organizations.
The nexus of taxation refers to the minimum level of commerce necessary to allow a tax authority to
impose a tax registration, tax filing, and/or tax collection responsibility. The type of activity required
to create nexus is defined by state or local statute, case law, and the due process and Commerce
Clause of the United States Constitution. Whether a business has established nexus in a tax
jurisdiction requires an assessment of all facts and circumstances of its activity within that
jurisdiction. You should seek the advice of a qualified tax professional to determine if your business
has established nexus (a registration and filing requirement) before you implement sales tax.
The situs of taxation describes which tax authority levies the tax. This is typically the ship-to state,
county, or city, although there are many local taxes that base situs on the ship-from location. Any tax
collected for a given tax authority must be reported back to that same authority.
Setup Features
This tax setup example is for a first party registered in California and dealing with city, county, state
transactions. Setup features include:
 There are three taxes under the US Sales and Use tax regime, for city, county and state sales.
 US Sales and Use tax is not recoverable, so the setup does not include recovery rates.
 There are multiple tax jurisdictions at the city and county level.
Tax Regime Setup

Field Value
Main Information
Tax Regime Code US SALES AND USE
Name US Sales and Use

Controls
Allow Tax Recovery No
Allow Override and Entry of Inclusive Tax Lines No
Defaults
Tax Currency USD
Tax Precision 2
Allow Tax Inclusion Standard Non-Inclusive Handlin

Field Value
First Party Legal Entity
Party Type First Party Legal Ent

Main Information
Set for Self Assessment/Reverse Charge No
Rounding Level Header
Configuration Options (if defined from party tax profile)
Configuration for Taxes and Rules Common Configurati
Field Value
Party Type First Party Legal Establishment
Tax Registration
Tax US STATE SALES
Tax Registration Number 567890
Set as Default Registration Yes
Source Explicit
Tax Setup
There are three taxes under the US SALES AND USE tax regime for city, county, and state sales.
The example below is for state sales. All setup values are the same for the three taxes.
Field Value
Main Information
Tax US STATE SALES
Tax Name US State Sales
Tax Type Sales
Geography Type State
Parent Geography Name United States
Controls
Allow Override and Entry of Inclusive Tax Lines No

Allow Entry of Manual Tax Lines Yes
Allow Tax Recovery No
Allow Tax Recovery Rate Override No
Allow Primary Recovery Rate Determination Rules No
Tax Status Setup

Field Value
Main Information
Standard Status
Tax Status Code US STATE SALES STANDARD
Name US State Sales Standard
Reduced Status
Tax Status Code US STATE SALES REDUCED

Name US State Sales Reduced
Zero Status
Tax Status Code US STATE SALES ZERO
Name US State Sales Zero
Default Controls (all statuses)
Allow Tax Exemptions Yes
Allow Tax Exceptions Yes

This setup is for the California state tax jurisdiction.
Field
Tax Regime Code
Tax
Geography Type
Geography Name
Precedence Level
Effective From
Default Effective From
Tax Rate Setup

This example shows the standard state tax rate. The setup for reduced and zero is the same, except
for the special reduced percentage rate and a zero percentage rate.
Field Value
Main Information
Tax Regime Code US SALES AND USE Tax Sta
Tax Regime Name US Sales and Use Tax Ra
Tax US STATE SALES Configu
Tax Name US State Sales Rate Ty
Tax Status Code US STATE SALES STANDARD
Rate Period
Percentage Rate 6.25 Default
Effective From 1-Jan-2000 Set as
Allow Tax Exemptions Yes Allow A
Allow Tax Exceptions Yes Adjustm

Troubleshooting Oracle E-Business
Tax and Sample Scenarios
This appendix covers the following topics:
 Determining Why a Tax Does Not Calculate
 Using and Troubleshooting the Financial Tax Register
 Troubleshooting AutoInvoice Tax Issues
 Troubleshooting Error Messages
 Sample Scenario: EU VAT Setups
Determining Why a Tax Does Not Calculate

In release 12, many factors can influence tax applicability and prevent a tax from being levied on an
invoice. Following are many of the settings to review when troubleshooting a tax that will not apply.
Tax Regime
1. The transaction date must fall within the active dates of the regime. The transaction to be taxed must
be created in an operating unit that is associated with the taxing regime.
2. This association can either be through the operating unit party tax profile or, if the operating unit is set
up to use the subscription of the legal entity, through the legal entity party tax profile.
Note: (N) Tax Managers > Parties > Party Tax Profile > Operating Unit Owning Tax Content. To use
the Legal Entity setup, verify that the check box is selected.
3. If the tax regime has content owned at the operating unit level and not the global configuration owner
level, the operating unit on the transaction must match the tax regime setup.
Tax
The tax must be available for transactions and be within a valid date range for the tax.
Tax Status
1. Tax status must be available for transactions and fall within a valid date range for the tax.
2. Tax status must be set as the default tax status or have a tax status rule defined to derive the tax status.
Tax Rate and Jurisdiction
1. Dates on the transaction must fall within those on the rate and jurisdiction.
2. Tax rate must be defined as a child to the tax status derived in the prior section.
3. If the tax rate is associated to a jurisdiction, the place of supply specified in your tax rule setup must
match that of your transaction. For example, if the taxing jurisdiction is British Columbia, Canada and
your place of supply is ship-to, then the ship-to address must be in British Columbia.
4. If the tax rate is associated to a jurisdiction, make sure the place of supply specified in your tax rules,
for example, ship-to is valid. Check the invoice and find the address corresponding to your place of
supply and identify the geography segment in that address that you are using for your jurisdiction.
Make certain a rate exists for the exact jurisdiction. Also make sure all jurisdiction tax rates are set as
Default to automatically calculate based upon the place of supply (as opposed to explicit tax rules
dictating when the tax should apply).
Note: If you exclusively use jurisdiction based rates, taxes will not be applied if the place of supply is
null. For this reason you should use caution if you choose ship-from or ship-to as your place of supply
in receivables. If you do set these as the place of supply then all invoices must have a warehouse or
ship-to address depending upon your setup. If your address is associated to a geography that has not
been properly defined in TCA, then you may also see the following Receivables message: System
cannot determine geographical information for this location and cannot derive a tax jurisdiction.
Refer to Note 438718.1 to troubleshoot this scenario.
5. If the tax rate is not restricted to a jurisdiction, then a tax rate must exist with the jurisdiction as null
and the tax rate must be set up as default.
Note: If taxing regulations do not require a jurisdiction, then you should not link one to the tax rate.
Use of a jurisdiction on a rate mandates that an address must exist on the transaction to be taxed and
therefore restricts several features such as automated tax calculation on GL journal entries and tax
calculations on Miscellaneous Receipts in AR where no address is recorded.
Tax Rules
1. When implementing E-Business Tax you must specify default rules before taxes can be enabled.
Ensure that the default for Determine Tax Applicability is set to Applicable or that you have a rule
defined and enabled that makes the tax applicable for your specific transaction.
2. Ensure that the tax status and tax rate defaults are valid or that you have rules defined to properly
derive these values.
3. Do not define tax rules that evaluate null values.
4. If you have defined tax rules using guided rule entry or expert rule entry, ensure that the determining
factor is available in the module where you are attempting to calculate tax. Not all determining
factors, condition sets and values can be used in all modules.
Note: For more on tax determining factors including sample rules defined for each tax factor review
Note 1108463.1, How Tax Determining Factors Work in R12 E-Business Tax and the Oracle E-
Business Tax User Guide.
Configuration Owner Tax Options
1. Configuration Owner Tax Options are set in the Tax Managers responsibility under the defaults and
controls tab. Query the operating unit (or legal entity) where you have associated your tax regime. If
this is defined (optional setup), then verify the Allow tax Applicability check box is checked. Also
ensure that you have the proper tax determination method selected.
Note: STCC is only for upgraded tax calculation logic.

Intercompany (AGIS)
Intercompany transactions presently do not pass a ship-to address. Ensure that your tax rules for
intercompany transactions are flexible enough to derive the proper tax rate without reliance on ship-
to.
Transaction
1. If your tax considers ship-from in receivables, specify a warehouse on your transaction line. The same
is true if you have advanced rules defined referencing product fiscal classifications.
2. If you are using an upgrades setup, direct rate rule or if you configured rules to reference the tax
classification code, you must have a tax classification code set on your invoice line. Defaulting of this
field can be controlled in the Tax Managers responsibility under Application Tax Options.
3. Ensure the address on your transaction and for your legal entity and operating unit are valid.
Additional Considerations
E-Business Tax has the flexibility to specify complex tax rules at many levels. Rules can consider
fiscal classifications set at the party or product level, transaction classifications codes, and many
additional factors.
Using and Troubleshooting the Financial Tax
Register
Getting Started and Critical First Steps
Important: Before you attempt to use this report it is important that you apply the latest Tax
Reporting Ledger (TRL) patches. Refer to the Troubleshooting section that follows and Note
737320.1, Troubleshooting eBusiness Tax Reporting Issues in release 12.
What is the Financial Tax Register?

The Financial Tax Register Report is a flexible cross-product tax register report released as part of
the E-Business Tax transaction based tax reporting solution in R12.
This report allows you to report on both Output (sales transactions) and Input (purchase
transactions) tax for specified parameters.
Important: This report can render nearly all information required by customers for their tax reporting,
but only if the proper parameters are entered. Be sure you read and understand the impact of tax
parameters when using this report.
The output created for this report is presented through the RXi tool. RXi allows you to select the
fields you wish to see, add summary columns, totals and breaks. Additionally, you can select the
output format (HTML, CSV, Text, and so on) when running these reports. In most cases this data is
used for data analysis as RXi (unlike most other reports which use XML Publisher) does not have
the formatting capabilities to embed graphics such as a company logo or otherwise customize the
presentation.
Data selected for viewing in this report uses the Tax Reporting Ledger or TRL engine to gather data.
This same engine is used across a wide number of other R12 E-Business Tax reports.
The financial tax register report was created to provide a comprehensive and flexible framework that
you can use to analyze and report on transactions based on tax activities in Release 12.
What Transactions (Modules) Appear on the Report

Output?
Transactions from the following modules can appear on the Financial Tax Register if the proper
parameters are supplied:
 Oracle Receivables
 Oracle Payables
 Oracle General Ledger

Report Parameters and What They Do
The following parameters have been organized into groups for this section. These groups are not
necessarily reflective of the order that they appear when submitting the report.
Important: Run this report from the forms UI to avoid receiving the AR_SRS_LEDGER_FLEXFIELD
has an incorrect validation type (P) error, which occurs if it is run from the Web UI.
Responsibility: Tax Managers
(N) Requests > Other > Requests > Run
Attribute Set
The Financial Tax Register is an RXi report that contains two predefined attribute sets. You can
create additional custom attribute sets as needed by copying and editing them. The seeded attribute
sets are:
 Default: The Default attribute set contains all of the available attributes from the extract view. You
can use this attribute set to create new attribute sets. There is no predefined layout. Running the report
at this level with an output format of CSV is not recommended because the standard Excel workbook
does not have enough columns. Choose HTML to see all fields.
 TaxReg: The TAXREG attribute set can be used for Oracle Payables, Oracle Receivables, and Oracle
General Ledger, or all products. The report contains the attributes most commonly included in Tax
Registers. It does not include discount amounts for Oracle Receivables and Oracle General Ledger.
Note: The reporting level selected changes the attributes that appear. This means that distribution
level attributes will not be displayed if the report is submitted at the transaction level. Similarly, some
transaction level details are shown as null (blank) if the report is submitted at the distribution level.
Output Format
RXi reports provide flexibility in selecting the format for viewing your output. Four options exist:
 CSV: Also known as comma separated this output format is typically used when importing data into a
spreadsheet such as Microsoft Excel. Data will be truncated by Excel if the number of columns exceed
the capacity of your spreadsheet. Refer to the section that follows on customizing output to modify the
fields extracted.
 HTML: This option produces output in an HTML table and is best viewed through a browser. This is
the recommended choice when exporting the Default attribute set as the table has no limitations on the
number of columns.
 TAB: A good alternative to CSV in cases where your content may include a comma, for example, as
in description or text fields.
 TEXT: Includes basic text output. This output format can be difficult to view as it may result in large
white spaces being produced on the page.
Reporting Level, Reporting Context, Company Name and Currency
Note: If you are not using Multi-Org Access Control, the report ignores the Reporting Level and
Reporting Context parameters
When submitting this report, content can be filtered at multiple levels.
Reporting Level
 Ledger: The most broad setting, this method selects all tax data for transactions within a ledger.
 Legal Entity
 Operating Unit
Reporting Context
This LOV will render a list that is contextual to the reporting level selected, for example, a list of
operating units appears if you select Operating Unit.
Note: The data displayed in this LOV is further restricted by your security settings and or operating
unit restrictions defined in System Administrator.
Company Name
This parameter is available only when the reporting context is set as Ledger and is populated by a
list of Legal Entities for a given Ledger
Set of Books Currency
The Currency LOV is restricted to the ledger currency. The ledger is identified by the Set of Books
profile option, the ledger reporting context (if selected) or the ledger that is defined for a Legal Entity
or Operating Unit.
For more on the Currency LOV refer to the value set ZX_TRL_LE_CA_CURRENCY.
Register Type
 All: All transactions
 Interim Tax Register: Limits the output to Receivables transactions that are posted to the interim tax
account. A tax is posted to the interim account when the settlement option for the tax rate is set to
Deferred and the receivables invoice has not yet been paid.
 Non-Recoverable Tax: Displays taxes sourced in both Payables and Receivables where the tax is not
recoverable.
 Tax Register: Displays recoverable taxes, excludes any tax that is deferred (posted to the Interim tax
account).
Summary Level
Allows you to select the level of detail included in the report:
 Transaction Distribution Level
 Transaction Level
 Transaction Line Level
Note: Not all attributes specified in your attribute set will be displayed at all summary levels.
Distribution accounts for example are not rendered on the output when the report is run at the
Transaction level nor are line-level attributes.
Transaction Parameters
Product Select the application to report on or select All to report on all applications.
 ALL
 Oracle General Ledger
 Oracle Payables
 Oracle Receivables
Note: You must also select the Payables or Receivables parameters or no data appears in your
report output.
GL Date Low/ High
Transaction Date Low/High
Tax Transaction Type Low
Transaction Number: Enter a specific transaction number to report on. The list of values for this field
depends on the Include options that you enable.
Currency Code Low/High
Include Discounts
Transfer to GL: You can report on transactions transferred to General Ledger, transactions not
transferred, or all transactions.
 ALL
 Not Transferred
 Transferred
Accounting Status
 Accounted
 Both Accounted and Unaccounted
 Unaccounted
Tax Type Parameters
 Tax Type Low/High: The range of tax types to include in the report. If you are reporting on a specific
tax regime or tax, then the report uses the tax types belonging to this tax regime or tax only.
 Tax Regime Code: Select a tax regime to report on, or leave blank to report on all applicable tax
regimes
 Tax: Select a tax to report on, or leave blank to report on all applicable taxes.
 Tax Jurisdiction: Select a tax jurisdiction to report on, or leave blank to report on all applicable tax
regimes.
 Tax Status Code: Select a tax status to report on, or leave blank to report on all applicable tax regimes.
 Tax Code Low/High: The range of applicable tax rate codes to include in the report
Payables Parameters
Standard Yes/No option. Set to Yes to see the parameters.
Note: The actual form does not designate these as Payables specific.
 Include Standard Invoices
 Include Debit Memos
 Include Prepayments
 Include Mixed Invoices
 Include Expense Reports
Receivables Parameters
Standard Yes/No option. You must set to Yes to see on the report output.
Note: The actual form does not designate as Receivables specific
 Include Invoices
 Include Applications
 Include Adjustments
 Include Miscellaneous Receipts
 Include Bills Receivables
 AR Exemption Status: If you are reporting on Receivables transactions, select a tax exemption status
to report on.
Matrix Report Flag
Matrix Reporting should be used to show a single line in the Tax Reporting Ledger for two or more
tax amounts. Matrix Reporting can be used to support countries with multiple taxes (for example,
Canada) or to provide a breakdown of input taxes, showing both recoverable and non-recoverable
tax amounts on the same report line.
If Matrix Reporting is enabled, the Tax Reporting Ledger groups either of the following into a single
line:
 Up to Four Output Taxes
 Up to Two Input Taxes, each with a split between Recoverable and Non-Recoverable amounts.
Include Accounting Segments
Set to Yes if your attribute set includes accounting segments. Setting to No may help performance
and is advised if you do not have accounting segments in your attribute set.
How the Tax Reporting Ledger (TRL) Works

The Tax Reporting Ledger (TRL) represents a reporting framework for E-Business Tax Release 12
reports for Receivables, Payables, and General Ledger transactions. Reports built around the TRL
(more than 50 seeded reports) share a common set of code.
When a TRL report is submitted, the main wrapper program is called. This wrapper code can take
many forms including Java, PL*SQL procedures or traditional Oracle Reports (RDFs). When a
request is submitted, you must enter parameters. The wrapper code often derives additional
parameters and then makes a call to invoke the TRL code.
When the TRL code is called, parameters are passed to a set of stored procedures. These
procedures extract data from the base table used by the product or products specified in the
parameters. TRL code then populates this information into a standard set of reporting tables.
The TRL data extract draws tax transaction data from these sources:
 Receivables Invoices, Credit Memos, and Debit Memos
 Receivables Line, Tax, and Invoice Adjustments
 Receivables Payment Applications for Deferred Tax
 Receivables Earned and Unearned Discounts
 Receivables Finance Charges
 Receivables Miscellaneous Receipts and Payments
 Payables Invoices and Credit Memos
 Payables Prepayments
 Named columns for migrated Release 11i global descriptive flexfields
 General Ledger Manual Journal Entries

Typically the wrapper code that invoked the TRL engine data extract will read the data from these
reporting tables and generate output. This output also can take many forms. For the Financial Tax
Register this is accomplished through the RXi solution. Other reports leverage Oracle Reports to
produce XML output and then utilize XML publisher and a template (RTF) to format the output.
Others use Java or the text style output available in Oracle Reports.
End users do not need to understand how the Financial Tax Register works. They will analyze the
data rendered and ensure that it meets their expectations. However, it is critical for a Tax
Administrator or System Administrator to understand this design to maintain the most current tax
patches and thoroughly test all TRL reports for your instance. See the Troubleshooting section that
follows for more details.
What Happens when this Report is Run

As discussed in the prior section, the Financial Tax Register is a TRL report and this means the
report will invoke the TRL engine. Unlike other tax reports, this report uses the RXi solution for
publishing. Submission of this report therefore involves an extra request as seen by the user. The
flow is as follows:
1. User logs on as Tax Managers and submits the report, specifying parameters including an Attribute
Set and output format (HTML, CSV, and so on).
2. A concurrent request is created along with a spawned request. The spawned request name will be
RX:Only Financial tax Register. This spawned request represents the call to the TRL engine to seed
the reporting tables. This request produces no output. If however you are asked for a debug log, it is
this request id that should be used as the target for the query to extract logs as this is where all of the
data selection occurs. See Note 417238.1 for details on how to capture a debug log.
3. After the spawned request is completed, the RXi publisher is invoked. This publisher identifies the
attribute set entered when the report was submitted and uses the definition of the attribute set to select
and summarize the fields to be displayed. The data appears in the output format as specified.
Customizing Output for this Report

Creating a New Attribute Set
Customizing a report is a task that typically requires a developer or someone skilled in Oracle XML
publisher. Because the Financial Tax Register uses the RXi engine, any user with the proper
permissions can modify the fields displayed, add summary columns and otherwise adjust the output
of this report.
While RXi is not able to generate the attractive end-user reports that XML publisher can create,
many financial analysts and tax managers prefer this format for the flexibility and ability to export
data into spreadsheet (CSV output).
This is accomplished by creating a new Attribute Set to be used by the RXi engine for publishing the
report output. This can be done following the instructions in the Oracle Financials RXi Reports
Administration Tool User Guide.
For information on setting up Financial Tax Register attribute set refer to Note 745943.1
Also please review the following information as you customize:
 Tax Reporting Ledger Column Descriptions in the Oracle E-Business Tax Reporting Guide for details
on each of the attributes available to include in the report and how they are used/displayed. Note again
that not all attributes are visible for all report types.
 Note 973041.1, How To Configure The Financial Tax Register For Decimal Precision
An abbreviated set of steps are listed in the following:
1. Switch Responsibilities to Report eXchange Designer.
2. Select Setup RXi.
3. Select the report RX-Only: Financial Tax Register Report.
Important: Do not select Financial Tax Register or RX-Only: Financial Tax Register as the report.
The Financial Tax Register spawns the RX-Only: Financial Tax Register Report. Selecting the
Financial Tax Register or RX-Only: Financial Tax Register results in the attribute sets from 11i being
updated instead of the R12 attribute set being displayed.
4. Copy the attribute set.
5. Remove the columns that you desire (limit the columns to match the number available in your version
of your spreadsheet solution if choosing CSV output).
6. Select Tools > Security and add the responsibilities permitted to access the attribute set.
7. Save.
Note: The attribute sets may only be visible from the forms based request submission.
Formatting Currency and Number Cells
To display tax amount like (XXX) instead of -XXX, you must define a format:
1. From Report eXchange Designer responsibility.
2. Double-click on Setup RXi. You can see the Attribute Set.
3. In the Report Name field enter RX-only: Financial Tax Register Report.
4. Navigate to Attribute Set field.
5. Go to the attribute set, which is used by the report.
6. In the right bottom region, click on Column Details.

Notice the Menu Bar Folder menu is disabled. If you place the cursor on any of field, the folder is
enabled.
7. Select Folder > Show Field.
8. Select Currency Column. One more column is added that is Currency Column.
9. Navigate to any amount related field. For example, Taxable_amt in the Currency Column select.
Limitations on Fields Available for Display and Fields Showing in Output
Field not showing as available to pick: Not all tax related attributes are in the available attributes. For
example, one very significant field that is not available is Jurisdiction.
Field not showing up even though they are in the attribute set: The fields displayed are dependent
upon the level from which the report is submitted (distribution, transaction, line).
For example, in order for accounting information to appear you must submit the report as noted.
Submitting at any other level returns no data for the accounting fields.
Both the include_accounting_segments must be set to Yes and Summary level must be equal to
Transaction Distribution Level for accounting information to appear.
Troubleshooting Issues with this Report

General Troubleshooting
This report works by pulling data from the underlying tables used across GL, AP and AR. The steps
used to compile this data occur in the TRL source code. Verify you have the latest patches available.
Note 737320.1 (section 4) contains the latest patches released for this code. The note also includes
comprehensive troubleshooting steps for Release 12 Tax reports including the Financial Tax
Register.
Check to see if the data missing or incorrect on your report is also wrong in the underlying view
ZX_REP_EXTRACT_V: The view upon which attributes sets are defined. When submitting this
report with FND:Debug set to Yes, data is retained in the base tables summarized by this view. You
can query this view to see if data exists. If it does not exist you can then look to see if your
parameters are properly set. If parameters are properly set then the problem is almost certainly in
the TRL engine and database packages. If you find that the data appears correct in the view but
invalid in the display, check to see if your attribute set has proper grouping and other settings. Also,
test with one of the seeded attribute sets.
Common Issues Specific to The Financial Tax Register
Symptom: Fields are showing as blank on the report output.
Cause: Check the level at which the report was run. When submitted at the transaction level, line
level details do not appear. Similarly, when run at the transaction level, distribution level details are
not shown.
Symptom: No Output when run for Reporting Set of Books
Cause: Set the profile option GL Ledger Name at the responsibility level.
Performance Issues with the Financial Tax Register

If you have performance problems with this report, check the following:
1. Ensure you have gather scheme statistics running on a regular basis and that it includes the product
short name ZX.
2. Ensure that tax debug logging is not turned on. See Note 417238.1, if you are unsure of how this is
checked.
3. Ensure you have the latest TRL code patches applied from Note 737320.1.
4. Schedule the request Purge Logs and Closed System Alerts to run regularly. This will clear out the
debug log tables and reduce the size of the tables read by the report.
5. Periodically truncate the tables below:
o ZX_REP_CONTEXT_T
o ZX_REP_TRX_DETAIL_T
o ZX_REP_TRX_JX_EXT_T
o ZX_REP_ACTG_EXT_T
These tables store data only when debug is enabled. They can grow large over time and periodically
purging them ensures that the size of the table does not interfere with the execution of individual
reports. Data in these tables is stored by concurrent request ID and is not used for any purpose except
to generate output for individual request submissions.
Troubleshooting AutoInvoice Tax Issues

AutoInvoice is used to generate invoices from a wide variety of sources. Oracle Applications such as
OKS (Contracts), Projects, Order Management and AGIS (Advanced Global Intercompany) are just
a few sources that use AutoInvoice to generate invoices. In addition to Oracle Application modules,
AutoInvoice is available for use as a tool in migrating data during an implementation and to integrate
Oracle Receivables with a legacy Order Management system.
How are Taxes Calculated

Taxes can be generated in one of two ways.
1. Transactions can be created with appropriate attributes defined such as bill_to, ship to, warehouse_id
and AutoInvoice can call E-Business Tax to calculate taxes using your tax rules.
2. Transactions can be passed into the interface tables with a pre-calculated tax line.
Note: Oracle Applications that calculate tax typically generate an estimated tax in their respective
user interfaces (such as Order Management) but do not pass this tax line to AR. Taxes are
recalculated at the time of invoicing as this is the point where the tax liability is incurred.
General Debugging Tips

Always begin the process of AutoInvoice testing by upgrading to the latest tax validation code. This
is done by applying the latest patches for critical code used in the transition between AR and E-
Business Tax.
Code Description
zxapdefvalpkgb.pls Used by the tax engine to derive tax attributes such as regime, status, rate and tax
AREBTUTB.pls Generic AR/EBTax integration package used by AutoInvoice, APIs and AR forms.
AREBTAIB.pls AutoInvoice specific package used to pass data from AR to EBTax for AutoInvoice proces
zxdiprodintgpkgb.pls Package used for Latin Tax Engine callouts to EBtax
Use the following query to find your versions of the preceding files:
select text
from all_source
where name in ('ARP_ETAX_UTIL', 'ARP_ETAX_AUTOINV_UTIL',
'ZX_PRODUCT_INTEGRATION_PKG', 'ZX_VALIDATE_API_PKG')
and text like '%$Header%'
and type = 'PACKAGE BODY';
Importing and Debugging Manual Tax Lines

Note 731149.1, How To Import and Troubleshoot Manual Tax Lines Imported Through AutoInvoice
in R12 E-Business Tax (EBTax) was created to track all known issues related to how manual tax
lines are imported and validated.
Debugging Taxes Calculated by the E-Business Tax
Engine
Replicate in AR Transaction Workbench
The first step in debugging tax calculations in AutoInvoice is always to validate that the taxes work
as expected in the Transaction Workbench form in AR. If they fail to work in the workbench form it is
easier and faster to diagnose the issue using the manual entry form.
Tip: When troubleshooting integration issues from OM you should be sure to attempt the replication
in AR by entering a transaction that includes an inventory item and warehouse.
Obtain a Tax Debug Log
If the problem cannot be replicated in the transactions form, advanced troubleshooting is required.
Just as with manual tax lines, this will involve the creation of a debug log. Follow the instructions
from Note 1079666.1 to create the required logs. Typically both the AutoInvoice debug log and the
tax (fnd) debug logs are required to troubleshoot these issues.
Note: Tax Debug logs are not the same as AutoInvoice debug logs. AutoInvoice will often return the
following message in the log file when E-Business tax fails: ERROR from eBusiness Tax - return
code = 2 is a generic error handling message that is returned by the E-Business Tax code to AR
AutoInvoice whenever an error happens during tax calculation. In order to troubleshoot this error a
tax debug log is required. The tax debug log shows why the error occurred.
Once created and exported to a text file or spreadsheet the log can be searched for error strings.
These can often be used in conjunction with the concurrent request log file and exception report to
keyword search and find known issues and fixes.
Check the Following List of Commonly Encountered Problems
 Note 603799.1, AR Reports and Vertex show Transaction Number As '~$~$$$'
 Note 745340.1, AutoInvoice Fails With Message "This Tax Rate Is Not Active"
 Note 786000.1, Credit Memo's fail with "System Cannot find tax Rate"
 Note.779616.1, Exemptions not applied when invoices imported through AutoInvoice
Intercompany Taxes
Release 12 includes the Advanced Global Intercompany Invoice feature. This provides a
responsibility that is used to generate intercompany invoices. Once generated in AGIS, a workflow
background process is run to create the invoice in the AutoInvoice interface tables. AutoInvoice is
then run to generate the invoice in Oracle Receivables.
In order to keep the taxes in sync between AR and AP, the workflow process that populates the AP
interface table does not start until the AR invoices are complete. Once completed a business event
triggers the relevant transactional data to be passed to the AP interface tables including some of the
tax attributes from the AR record. Although some of these tax attributes stored on the AR transaction
are referenced by the workflow when the AP invoice is generated, the AP tax setup must be
complete in order for taxes to be in sync.
Important: Apply 7718598 for the AR attributes to be properly copied.
Note: Although the attributes are shared, AP code is separate from AR. If you find that the AR and
AP invoices are not in sync at the completion of the processing, then you should contact the AP
support team to evaluate your tax setup and rules.
Internal Sales Orders

Internal Sales Orders follow a different flow when interfacing to Receivables. In some cases the
Order displayed in Order Management shows a tax calculation that is different from the invoice
created in AR.
Note 1048431.6, Ship To Address Not Appearing on Intercompany AR Invoices discusses this in

more detail.
The problem is typically that the tax rules have been defined to use the ship-to address but make no
allowance for bill-to to be used if a ship-to is not supplied. Since internal sales orders are not created
in AR with a ship-to address the tax rule fails to find a place of supply and taxes do not calculate.
Two potential alternatives exist:
 Modify your tax setup to use bill-to if no ship-to exists.
 Create a customization to copy the ship-to address to the ra_customer_trx_lines_all after it is sent
from inventory but prior to running AutoInvoice.
If AutoInvoice Ends In Error:

All AutoInvoice Tax errors in R12 are prefaced with the text below. The error messages are what you
find in the tax debug log when captured as previously instructed.
raaebt()+ Current system time is 08-SEP-2008 12:57:54
ERROR: from eBusiness Tax - return code = 2 Current system time is 08-SEP-2008
12:57:59
Please review the plsql debug log for additional details. Current system time
is 08-SEP-2008 12:57:59
Error calling raaebt()
Error calling raapic()
raarrt2()+ Current system time is 08-SEP-2008 12:57:59

Commit after cleanup - Current system time is 08-SEP-2008 12:58:00
...
arp_etax_util.calculate_tax_int()+
ZX_API_PUB.import_document_with_tax returns failure
Error Message
The system cannot determine the default tax rate for tax and tax status . Please contact your tax manager either to s
tax status and date <Date> or to define appropriate rate determination rules.
If AutoInvoice Ends with a Message in the Exception

Report:
Exception Message Cause
Invalid tax exempt flag In release 12.0, when interfacing an order or RMA from OM to AR with the tax
(TAX_EXEMPT_FLAG) handling set to O for Override, the record is being rejected by AutoInvoice impor
with the message in the log file shown below: Invalid tax exempt flag
(TAX_EXEMPT_FLAG). If the system option Allow Exemptions = No then valid
values are S or R, otherwise the valid values are S, R or E (O). This issue was
caused by OM allowing the tax handling to be set to Override. The value O was
obsoleted in Release 12.
This Tax Rate is Not Active This Bug 7504455

Tax Rate is Not Active on the
Transaction Date
If Error Occurs When Trying to Fix a Tax Line Using the

Interface Lines Form
Error Message Cause Action
ORA-28115: policy with check The user was attempting to enter a tax line by clicking on the Tax The solution
option violation FRM- button from the exceptions form. This is not the proper way to add distribution li
40508:ORACLE error: unable tax lines to AutoInvoice. Manual tax lines can be added, however 731149.1 Th
to insert record the Tax button is provided only to show calculated taxes on records legacy applic
processed by the interface and not to add tax lines. be performed
calculate an
re-calculate
For more information, refer to Note 751126.1, Troubleshooting AutoInvoice Tax Issues with R12 E-
Business Tax (EBTax).
Troubleshooting Error Messages

The following tables describe specific Oracle E-Business Tax error messages. The tables also
provide causes, actions, navigations and User Guide references for error messages.
Important: The message number and message code are used in the code to generate the message
in a form or report. These are listed to assist with debugging.
Tax Calculation, Import and Setup Error Messages
Message # Message Code Message Text Cause
426011 The system cannot determine the default tax rate Based on the info
ZX_DEFAULT_RATE_NOT_FOUND for tax &TAX and tax status &TAX_STATUS provided for the tr
Please contact your tax manager either to specify system could not
a default tax rate code for this tax status and date rate for the applic
&DATE or to define appropriate rate determination because either sy
rules. find any default ta
applicable tax and
tax rate determina
not be successful
426012 The system could not determine the applicable Based on the info
ZX_RATE_NOT_FOUND Tax Rate for Tax &TAX and Tax Status provided for the tr
&TAX_STATUS Please contact your Tax system did not fin
Administrator to ensure that either a default Tax defined for an app
Rate Code that is effective on &DATE is specified tax status in the c
for this Tax Status or the appropriate Rate determination dat
Determination Rules are defined. calculated withou
426013 The system could not determine the applicable Based on the info
ZX_STATUS_NOT_FOUND Tax Status for Tax &TAX. Please contact your provided for the tr
Tax Administrator to ensure that either a default system did not fin
Tax Status is specified for this Tax or the defined for an app
appropriate Status Determination Rules are the context of the
defined. determination dat
be calculated with
status.
426014 The system cannot determine the tax for this Based on the info
ZX_COMPND_TAX_NOT_FOUND transaction because the compounding tax &TAX provided for the tr
for formula code &FORMULA_CODE is not system determine
applicable. Please contact your tax manager. tax. It has a asso
formula for derivin
basis, which in tu
dependency on o
compounding. Ho
dependent tax is
(no defaults or no
transaction date.
426015 The system cannot determine the offset tax rate Based on the tran
ZX_OFFSET_RATE_NOT_FOUND for tax regime &TAX_REGIME, tax &TAX, tax information, the s
status &TAX_STATUS and tax rate code determined that a
&TAX_RATE_CODE. Please contact your tax is applicable for c
manager. regime, tax, statu
code. However, th
not determine the
tax rate for a give
date.
426016 The system could not determine a valid Recovery Based on transac
ZX_REC_RATE_CODE_NOT_FOUND Rate Code for the Tax Regime &REGIME_NAME, the system found
Content Owner &CONTENT_OWNER, Tax applicable tax is r
&TAX_NAME and Recovery Type However for a co
&RECOVERY_TYPE. Please contact your Tax configuration own
Administrator to ensure that a valid default and recovery type
Recovery Rate Code is defined for this Regime, not be calculated
Content Owner, Tax and Recovery Type. tax the tax does n
default recovery r
associated with it
426017 The system could not determine a valid Recovery Based on the tran
ZX_REC_RATE_NOT_FOUND Rate for the Tax Regime &REGIME_NAME, information, the ta
Content Owner &CONTENT_OWNER, Tax could not be proc
&TAX_NAME, Recovery Type system is unable
&RECOVER_TYPE and Recovery Rate Code recovery rate in th
&RECOVERY_RATE_CODE. Please contact your tax regime, config
Tax Administrator to ensure that a valid Recovery tax, recovery type
Rate is defined for this Regime, Content Owner, transaction date.
Tax, Recovery Type and Recovery Rate Code.
426018 The system cannot find tax regime information for Based on the tran
ZX_TAX_REGIME_INFO_NOT_FOUND tax regime &TAX_REGIME. Please contact your information, the a
tax manager. could not be proc
system could not
valid regime for th
date.
426019 The system cannot find tax status information for Based on the tran
ZX_TAX_STATUS_INFO_NOT_FOUND tax regime &TAX_REGIME, tax &TAX_CODE and information, the a
tax status &TAX_STATUS. Please contact your could not be proc
tax manager. system could not
valid tax status on
date.
426020 The system cannot find tax rate information for Based on the tran
ZX_TAX_RATE_INFO_NOT_FOUND Tax regime: &TAX_REGIME, Tax: &TAX_CODE, information, the a
Tax status: &TAX_STATUS , Tax rate code: could not be proc
&TAX_RATE_CODE and Tax Jurisdiction code: system could not
&TAX_JURISDICTION_CODE. Please contact valid tax rate for t
your tax manager. date.
426021 The system cannot find tax information for tax Based on the tran
ZX_TAX_INFO_NOT_FOUND regime &TAX_REGIME and tax &TAX. Please information, the a
contact your tax manager. could not be proc
system could not
valid tax for the tr
426022 This Tax Regime Code is not valid on the The tax regime us
ZX_REGIME_NOT_EFFECTIVE transaction date. imported tax line
the given transac
effective regimes
considered for pro
426023 This Tax Rate is not valid for the transaction date. The tax rate spec
ZX_TAX_RATE_NOT_EFFECTIVE imported tax line
context of the tran
426024 This Tax Status Code is not valid for the The tax status sp
ZX_TAX_STATUS_NOT_EFFECTIVE transaction date. imported tax line
the given transac
426025 This Tax is not valid for the transaction date. The tax specified
ZX_TAX_NOT_EFFECTIVE tax line is not vali
transaction date.
effective then the
line will not be pro
426026 This tax status code does not exist. The tax status pro
ZX_TAX_STATUS_NOT_EXIST imported tax line
for a combination
owner, regime an
valid status the im
cannot be proces
426027 This Tax does not exist. The tax specified

ZX_TAX_NOT_EXIST tax line does not
provided tax rate
existing for it to g
426028 This Tax Regime Code does not exist. The tax regime sp
ZX_REGIME_NOT_EXIST imported tax line
The provided reg
for it to get proces
426029 This Tax Rate does not exist. The tax rate spec
ZX_TAX_RATE_NOT_EXIST imported tax line
The provided tax
existing to get pro
426030 The Place of Supply Type for the Tax &TAX was The location infor
ZX_POS_MISSING_ON_TRX determined as &POS_TYPE. Please enter a associated with th
&POS_TYPE on the transaction. supply type for th
is not provided on
Unless the releva
supply type is pro
applicable tax can
calculated.
426031 This Tax is not enabled for processing. The tax indicated
ZX_TAX_NOT_LIVE tax line is not turn
processing. Unles
live, it will not be
processing.
426032 The system cannot prorate this tax amount Based on the info
ZX_HDR_CTRL_TOTAL_TAX_MISMATC because the header level control tax amount is provided for the tr
H not equal to 0, but the total calculated tax amount system calculated
for this transaction is 0. Please contact your tax zero but the user
manager. adjustment amou
zero.
426033 The system cannot calculate the taxable basis for The system cann
ZX_IMP_TAX_RATE_AMT_MISMATCH the imported tax line because the tax rate is 0 but taxable basis for
the tax amount is not 0. Please change either the line because the
tax rate or the tax amount. is zero. However,
is not zero. Tax ra
amount should m
426034 An imported tax line cannot be allocated to the When a tax line is
ZX_IMPTAX_MULTIALLOC_TO_SAMELN same transaction line more than once. cannot be allocat
transaction line m
For example, one
line can be alloca
transaction line o
combination of re
should be unique
transaction line.
426010 The Tax Liability account has not been set up for Based on the tran
ZX_INVALID_LIAB_CCID either the tax rate or the account source tax rate information the sy
for the self assessed tax. Please enter it in the determined the se
Tax Recoverable/ Liability account field using the but distributions f
Tax Rate Accounts window. cannot be genera
recoverability/ liab
not been defined
level.
426035 The system cannot prorate this tax amount Based on the info
ZX_LN_CTRL_TOTAL_TAX_MISMATCH because the line level control tax amount is not provided for the tr
equal to 0, but the total calculated tax amount for system calculated
this transaction line is 0. Please contact your tax zero but the user
manager. adjustment amou
426036 The system cannot prorate the line level control The system cann
ZX_LN_CTRL_TOTAL_TAX_NOT_EXIST tax amount because there is no applicable tax for line level tax adju
this transaction line. Please contact your tax as there is no app
manager. found for this tran
system to pro rate
amount, there mu
tax.
426037 The system cannot determine geographical The system could

ZX_GEO_NO_GEO_NAME_REF information for this location and cannot derive a the geographical
tax jurisdiction. Please contact your system the location provi
administrator. transaction, which
derive a the tax ju
Geography hierar
associations are d
their linking with t
done in Oracle E-
The tax cannot be
without a location
associated to a re
jurisdiction.
426038 There is no subscription for this tax regime code The tax regime sp
ZX_REGIME_NOT_EFF_IN_SUBSCR for the given transaction date. imported tax line
valid subscription
unit or legal entity
transaction date.
426039 The UOM &UOM_RATE for quantity rate While defining tax
ZX_UOM_NOT_MATCH &RATE_CODE does not match the UOM specify the UOM.
&UOM_TRX on the transaction line. tax rate will be ca
the UOM mention
matches with the
in the transaction
transaction, the U
does not match w
associated with th
426008 ZX_INVALID_REC_CCID The Tax Recoverable/ Liability account has not The calculated ta
been setup for either the tax rate or the account accounted as the
source tax rate. Please enter it using the Tax Rate liability account h
Accounts window. setup for either th
account source ta
this account is sp
recoverability or l
accounted and in
can not be compl
426040 This Tax Rate is not active. Based on the tran

ZX_TAX_RATE_NOT_ACTIVE information, the a
could not be proc
rate is not active
transaction/ tax d
date. Without an
tax amount will no
General Setup and Import Error Messages
Message # Message Code Message Text Cause
426041 A Party Tax Profile does not exist for this Bill The bill from party
ZX_BILFROM_PARTY_NOT_EXIST From Party. transaction does n
profile. tax related
to parties in the tra
in party tax profile.
profile, system is u
the tax calculation
party.
426042 A Party Tax Profile does not exist for this Bill The bill from party
ZX_BILLFROM_PARTYSITE_NOTEXIST From Party Site. transaction does n
to party sites are s
tax profile. Without
system will not be
the tax calculation
party site.
426043 A Party Tax Profile does not exist for this Bill The bill to party sit
ZX_BILLTO_PARTY_SITE_NOT_EXIST To Party Site. transaction does n
profile. Without a p
system will not be
the tax calculation
party site.
426044 A Party Tax Profile does not exist for this Bill The bill to party pro
ZX_BILTO_PARTY_NOT_EXIST To Party. transaction does n
to party to the tran
profile, system will
determine the tax c
parameters for tha
426045 Default values have not been defined for this The tax could not b
ZX_COUNTRY_DEFFAULTS_NOT_EXIST country. the specific countr
defaults have not b
Oracle E-Business
defaults can be us
country related tax
426046 Please enter the currency code and precision. The currency code
ZX_CURRENCY_INFO_REQD details not specifie
level. Tax precision
maximum number
used to calculate t
426047 This Fiscal Classification Code is not valid for The fiscal classific
ZX_DOC_FC_CODE_NOT_EFFECTIVE this DOCUMENT_SUBTYPE Fiscal on the imported tra
Classification Type Code for the transaction valid for the releva
date. type fiscal classific
transaction date. W
document fiscal cla
the rule based on t
subtype will not be
426048 This Fiscal Classification Code is not defined The fiscal classific
ZX_DOC_FC_CODE_NOT_EXIST for this DOCUMENT_SUBTYPE Fiscal on the imported tra
Classification Type Code. defined for the rele
sub-type fiscal clas
ZX_DOC_FC_COUNTRY_INCONSIS this DOCUMENT_SUBTYPE Fiscal on the imported tra
Classification Type Code for the specified valid for the docum
country. specified country.
426050 This party fiscal classification code is not The party fiscal cla
ZX_FC_CODE_PARAM_NOT_EXIST associated with a party Classification Code. provided on the im
not defined for any
classification.
426051 This fiscal classification type code is not The fiscal classific
ZX_FC_INV_CAT_NOT_EXIST associated with an inventory category set. provided on the im
does not have an i
set associated with
426052 This Fiscal Classification Code is not defined The intended use f
ZX_INTENDED_USE_CODE_NOT_EXIST for this INTENDED_USE Fiscal Classification code provided on t
Type Code. line is not defined
use fiscal classifica
426053 This fiscal classification code is not valid for The fiscal classific
ZX_INTENDED_USE_COUNTRY_INCON this intended use fiscal classification type code in the transaction i
for the specified country. intended use fisca
code for the specif
ZX_INTENDED_USE_NOT_EFFECTIVE this INTENDED_USE Fiscal Classification on the imported tra
Type Code on the transaction date. intended use class
for the transaction
426009 The Tax Expense account has not been set up The user has not d
ZX_INVALID_NREC_CCID for either the tax rate or the account source tax expense account f
rate. Please enter it using the Tax Rate tax rate.
Accounts window.
426055 This Tax Jurisdiction Code not valid for the The tax Jurisdictio
ZX_JUR_CODE_NOT_EFFECTIVE transaction date. provided on the im
effective for the tra
426056 This Tax Jurisdiction Code is not valid. The tax jurisdiction
ZX_JUR_CODE_NOT_EXIST the imported tax lin
for the transaction
426057 Operating unit is missing. The operating unit

ZX_ORG_ID_REQD mandatory informa
processing, is miss
transaction.
426058 A Party Tax Profile does not exist for this Party. The party tax profi
ZX_PARTY_NOT_EXISTS the party provided
tax related informa
parties in the trans
party tax profile. U
exists system will n
determine the tax c
parameters for tha
426059 A party tax profile does not exist for this party. Party tax profile do
ZX_PTP_ID_NOT_EXIST party provided in th
426060 This Fiscal classification Code is not valid for The fiscal classific
ZX_PRODUCT_CATEG_COUNTRY_INCON this PRODUCT_CATEGORY Fiscal in the imported line
Classification Type Code for the specified product category ty
Country. specified country.
426061 This fiscal classification code is not valid for The fiscal classific
ZX_PRODUCT_CATEG_NOT_EFFECTIVE this product category fiscal classification type on the imported tra
code for the transaction date. valid for this produ
classification type
transaction date.
426062 This Fiscal Classification Code is not defined The fiscal classific
ZX_PRODUCT_CATEG_NOT_EXIST for this PRODUCT_CATEGORY Fiscal on the imported ta
Classification Type Code. for the specific pro
code.
426063 This product type code does not exist. The product type c
ZX_PRODUCT_TYPE_CODE_NOT_EXIST the imported trans
exist on the transa
426064 Product type is invalid. The product type c

ZX_PRODUCT_TYPE_INVALID the imported trans
valid.
426065 This Product Type Code is not valid for the The product type c
ZX_PRODUCT_TYPE_NOT_EFFECTIVE transaction date. the imported trans
valid for the transa
426066 Tax currency &TAX_CURRENCY requires an There is no exchan

ZX_QTY_TAX_NO_EXCHG_RATE_TYPE exchange rate type for a quantity-based tax specified for the ta
rate. Please contact your tax manager. required for quanti
426067 The system has determined that the Rate Type The rate type dete
ZX_RATE_FORMULA_MISMATCH &RATE_TYPE is applicable for Tax &TAX on system for the app
this transaction. However, this Rate Type is not transaction is not c
compatible with the Taxable Basis Type relevant taxable ba
&TAXABLE_BASIS_TYPE for Formula Code applicable tax form
&FORMULA_CODE. Please contact your Tax
Administrator.
426068 A Party Tax Profile does not exist for this Ship The ship from part
ZX_SHIP_FROM_PARTY_NOT_EXIST From Party. transaction does n
profile. Tax related
the tax calculation
party.
426069 A Party Tax Profile does not exist for this Ship Ship to party provi
ZX_SHIP_TO_PARTY_NOT_EXIST To Party. transaction does n
the tax calculation
party.
426070 A Party Tax Profile does not exist for this Ship The tax could not b
ZX_SHIPFROM_PARTYSITE_NOTEXIST From Party Site. ship from party site
transaction does n
in the party tax pro
tax profile, system
determine the tax c
parameters for tha
426071 A Party Tax Profile does not exist for this Ship The ship to party s
ZX_SHIPTO_PARTY_SITE_NOT_EXIST To Party Site. transaction does n
tax profile. Without
system is unable to
calculation parame
426072 The sum of the Percentage Recovery Rates for For a combination
ZX_SUM_REC_RATE_OVER the applicable Recovery Types the percentage tot
&RECOVERY_TYPE_1 and recovery types (1 a
&RECOVERY_TYPE_2 for the Tax Regime than 100. For a pa
&REGIME_NAME and Tax &TAX_NAME is associated recove
greater than 100. than 100.
426073 This Tax Rate Percentage is invalid. The tax rate perce
ZX_TAX_RATE_PERCENTAGE_INVALID the imported trans
valid.
426074 This Transaction Business Category Code is The transaction Bu

ZX_TRX_BIZ_FC_CODE_NOT_EFFECT not valid on the transaction date. provided on the im
effective on the tra
426075 This Transaction Business Category Code The transaction bu

ZX_TRX_BIZ_FC_CODE_NOT_EXIST does not exist. provided on the im
not exist for the tra
426076 This Transaction Business Category Code is The transaction bu

ZX_TRX_BIZ_FC_COUNTRY_INCONSIS not valid for the specified Country. provided on the im
line is not associat
specified country .
426077 This Fiscal Classification Code is not valid for The user defined f
ZX_USER_DEF_COUNTRY_INCONSIS this USER_DEFINED Fiscal Classification provided on the im
Type Code for the specified Country. line is not associat
specified in the tra
426078 This Fiscal Classification Code is not valid for The user defined f
ZX_USER_DEF_FC_CODE_NOT_EFFECT this USER_DEFINED Fiscal Classification provided on the im
Type Code for the transaction date. line is not effective
date.
426079 This Fiscal Classification Code is not defined The user defined f
ZX_USER_DEF_FC_CODE_NOT_EXIST for this USER_DEFINED Fiscal Classification code provided on t
Type Code. transaction line is n
user defined fiscal
code.
426080 You cannot delete this tax line either because The selected tax li
ZX_CHILD_FROZEN associated distributions were posted to the deleted as it has a
general ledger or the corresponding transaction accounted and pos
line is paid. Please contact your tax manager. Ledger or the corre
transaction line ha
426081 Please enter at least one location. No location has be

ZX_LOCATION_MISSING imported line. With
cannot be process
426082 Please enter a unit price. The tax processing

ZX_UNIT_PRICE_REQD information and it i
the transaction line
426083 Tax amount cannot be null. Tax amount on the

ZX_TAX_AMT_MISSING cannot be null. tax
a valid positive val
426084 The tax inclusive handling of the imported tax The tax inclusive h
ZX_TAX_INCL_FLAG_MISMATCH line does not match the tax inclusive handling imported tax line is
of the tax. inclusive handling
Oracle E-Business
426085 Tax lines with the same Tax Regime and Tax The same combina
ZX_TAX_MULTIALLOC_TO_SAMELN cannot be allocated to the same transaction tax cannot be alloc
line more than once. once to single imp
line, such as one t
cannot have more
from same regime
426086 This Tax Rate Code is either Recovery Rate or The code provided
ZX_TAX_RECOV_OR_OFFSET an Offset Rate tax line is either a
or an offset tax rat
actual tax rate cod
processed.
Note: Refer to Note 744185.1, eBusiness Tax Release 12 Error Messages: Causes and Actions.
Sample Scenario: EU VAT Setups

This example provides a sample scenario of the EU VAT 2010 changes. In this example there is a
Business-to-Business (B2B) transaction for services provided by a seller in the United Kingdom to a
buyer in Germany.
Set Up in E-Business Tax for Order-to-Cash Transactions

To identify Intra EU services (B2B) transactions, the seller in the United Kingdom has to perform the
following setup steps:
Create Intra EU Transaction Type Tax Reporting Codes
1. (N) E-Business Tax > Defaults and Controls > Tax Reporting Types > Create.
2. Enter the appropriate tax reporting type code and name.
3. Select tax reporting type in the Reporting Type Purpose drop down.
4. Select the Define List of Reporting Codes check box.
5. Enable the Reporting Type Use for Tax Rate. Any other reporting type use should not be selected for
Intra EU Transaction Type.
6. Specify minimum and maximum length of reporting codes.
7. Regime and tax are not mandatory parameters. If entered, reporting codes are specific to that regime
and tax.
8. Enter appropriate tax reporting codes according to user requirements. These codes are available as
selection parameters for filtering transactions in the ESL report.
9. The value entered in Description column is printed on the ESL report.
 Reporting Codes for Triangulation transactions may not be required for all EU countries.
 Follow codification requirements of each country while defining the reporting codes and description.
Create Legal Justification Tax Reporting Codes

1. (N) E-Business Tax > Defaults and Controls > Tax Reporting Types > Create.
2. Enter appropriate tax reporting type code and name.
3. Select legal justification message type in the Reporting Type Purpose drop down.
4. The Date Type Should Be Text and Define List of Reporting Codes check boxes are automatically
selected.
5. Regime and tax are not mandatory parameters. If entered, reporting codes are specific to that regime
and tax.
6. Reporting Type Use is automatically enabled only for Tax Rate. No other reporting type use should be
selected.
7. Enter the appropriate reporting code and legal justification text.
Note: Legal Justification Text (maximum 240 characters) is printed on the invoice as per the
template created in BPA.
Associate Intra EU Transaction Type and Legal Justification Reporting Codes to Tax Rate
Code
1. (N) > Tax Configuration > Tax Rates.
2. Enter the appropriate regime, configuration owner, tax and status information.
3. Specify tax rate code and percentage rate as zero (existing/upgraded tax rate code can also be
updated).
4. (N) Rate Details > Tax Reporting Codes > Specify the Tax Reporting Type Code and Reporting
Codes created for Intra EU Transaction Type in the preceding example (UK-INTRA-EU-SERVICES).
5. (N) Rate Details > Legal Justification Message Reporting Codes > Specify the Legal Justification
Reporting Type Code and Reporting Codes created in preceding example ((UK-INTRA-EU-
SERVICES).
6. Only one effective legal justification reporting type can be associated to a tax rate.
Set Up in E-Business Tax for Payables
Buyer of services (in Germany) must create a reverse charge on the Payables invoice line for such
Intra EU services. This can be achieved by calculating the offset tax associated to the applicable
German tax or by configuring the self assessed tax setup for German Tax.
Create Input Tax Rate Code
1. Configure Regime to Rate flow for the applicable tax in supplier (Germany) country (existing/updated
Regime to Rate can also be used).
2. Specify the Tax Rate percent (19% or the applicable Tax Rate).
3. Create the set up for associated offset tax.
4. For the offset tax rate code specify the tax rate percent equal to negative of the actual tax rate (-19% or
the applicable tax rate).
5. When the applicable tax is calculated, the associated offset tax is automatically calculated.
6. Alternatively, instead of offset tax, the self-assessed tax can be configured to create a reverse charge
on the Payables invoice line.
Setting Up in Bill Presentment Architecture (BPA)

The appropriate legal message and tax date must be printed on Intra EU services (B2B) transactions
Receivables invoice. The seller (in United Kingdom) must create a new template or modify the
existing template in BPA as follows.
Steps for Creating Templates to print Country Specific Legal Messages and Tax Invoice Date on
Receivables Invoice:
(N) Bill Presentment Architecture > Template Management > Create a new template that contains
the following content (existing/upgrade template can also be modified):
 Tax invoice date at the header region.
 Legal message at the footer region (and if required on the lines).

E-Business Tax(EB-Tax) Setup
Posted on December 14, 2013
E-Business Tax provides a single point solution for managing your transaction-
based tax requirements. E-Business Tax uniformly delivers tax services to all E-
Business Suite business flows through one application interface. As a global
system architecture, E-Business Tax is configurable and scalable for adding and
maintaining country-specific tax content.
 Tax Authority=>A goverment entity that regulates tax

law,administers, and/or audits one or more taxes
 Tax Regime=>The set of Tax rules that determine the treatment of
one or more taxes administered by tax authority.That is the set of
laws and regulations that determines the treatment of one or more
taxes.
 Tax=>A classification of a charge imposed by a government
through a fiscal or tax authority.
 Tax status=>The taxable nature of a product in the context of a
transaction for a tax
 Tax rates=>The rates specified for a tax status for a given time
period. The tax rate is expressed as a percentage, a value per unit
quantity, or a fixed sum per transaction.
 Tax Jurisdiction=>A geographical area where a tax is levied by a
special tax authority
Tax determination steps flow:
 Determine Place of Supply – Determines the location where a

transaction is considered to have taken place for a specific tax.
 Determine Tax Applicability – Determines the taxes that apply to
a given transaction.
 Determine Tax Registration – Determines the tax registration
status for the applicable taxes of the parties involved in the
transaction.
 Determine Tax Status – Determines the tax status of each
applicable tax to use on the transaction.
 Determine Tax Rate – Determines the tax rate for each applicable
tax status to use on the transaction.
Advertisements
REPORT THIS AD
Pre-Requisites
1. Navigate to Tax Manager->Parties->Party Tax Profiles and Query for the

following:
 Party Type: Operating Unit Owning Tax Content

 Party Name: Vision Operations (Name of the OU you wish to
setup for tax)
Click on Go button and then click View Tax Profile.
2. Confirm if ‘Use Subscription of the Legal Entity’ is checked.
Advertisements
REPORT THIS AD
If this is checked, then the OU is set to use the subscription from Legal Entity.
The regime is then subscribed (in a later step) to the First Party Legal Entity
rather than the Operating Unit Owning Tax Content.
This is a one time setup and the value cannot be toggled. So enable this only
after you determine you want to use this setup.
In our case its Checked and therefore we need to set our Tax Regime up
against First Party Legal Entity and NOT against the Operating Unit
Steps
Step 1: Create Tax Regime
1. Navigate to Tax Manager->Tax Configuration->Tax Regimes and click on

Create button
2. Enter Regime Code,Name and Country Name.Then Click on “Show Controls
and Defaults”.
3. Enable “Allow Override and Entry of Inclusive Tax Lines”,”Allow Tax
Exemptions” & “Allow Tax Exceptions”.Also enter the other default values and
click Continue Button.
4. Enter your operating unit in Party Name.If it prompts to select Party Type,
select “First Party Legal Entity” in our case.
Advertisements
REPORT THIS AD
If ‘Use Subscription of the Legal Entity’ was unchecked then Party Type would
have been “Operating Unit Owning Tax Content”
Also select ‘Configuration for Taxes and Rules’ as “Common Configuration” &
Effective date.Then click Finish button.
Step 2: Create Tax
1. Navigate to Tax Manager->Tax Configuration->Taxes and click on Create

button.
Enter the details as shown in below screenshot and then click on Show
Controls and Defaults
Advertisements
REPORT THIS AD
2. Enter the following information under Show Controls and Defaults section :
Advertisements
REPORT THIS AD
3. Click Apply button
Step 3: Create Tax Status
1. Navigate to Tax Manager->Tax Configuration->Tax Statuses and click on

Create button.
2. Enter the details as in below screenshot and click on apply button
Note: Enter Tax Regime created in step 1 & Tax created in step2
Step 4: Create Jurisdiction
1. Navigate to Tax Manager->Tax Configuration->Tax Jurisdictions and click

on Create button.
Advertisements
REPORT THIS AD
2. Enter details as in screenshot and click on Apply button.

Step 5: Create Rate
1. Navigate to Tax Manager->Tax Configuration->Tax Rates and click on

Create button.
2. Enter the details as in below screenshot.
Advertisements
REPORT THIS AD
Then click on Rate Details button and scroll down to other details
section.Enable “Set as Default Rate” and set the Effective From date.
3. Click apply so it comes to Create Tax Rate page and then click Apply button
again.
Step 6: Enter Tax Accounts
1. Navigate to Tax Manager->Tax Configuration->Taxes, query Country & the

tax we had created before and click on Go button.
2. Click on Update button and then click on “Tax Accounts” button.
Advertisements
REPORT THIS AD
3. Search for our OU’s Ledger and click Create button.
4. Enter the Operating Unit and Tax Expense & Tax Recoverable/Liability
account
Advertisements
REPORT THIS AD
5. Click Apply button so it will come to Tax Accounts page and click Apply
button again.Again once more click Apply button.
Step 7: Create Tax Rules
1. Navigate to Tax Manager->Tax Configuration->Tax Rules and query

Configuration Owner,Tax Regime Code & Tax and click Go button.
2.Click the pencil icon in the Set Default column to change any of the defaults
defined.Update the defaults as follows:
Advertisements
REPORT THIS AD
Step 8: Make Tax Available for Transaction
Advertisements
REPORT THIS AD
1. Navigate to Tax Manager->Tax Configuration->Taxes,query Country

name,Tax Regime Code & Tax and click Go button.Then Click on Update icon.
2. Enable the Check-box ‘Make Tax Available for Transactions’ and click Apply
button.
Note:It might throw warning “This tax does not have an exchange rate type.
Are you sure you want to enable this tax?”,click Yes button for this since we
know we didn’t enter an exchange rate type.
Advertisements
REPORT THIS AD
Testing
1. Create an invoice with Ship-To location at line level containing an United
States location.Save the invoice after entering the distribution details and click
on Calculate Tax Button.Now you can see the Tax line created at Line Level.
2. Click on Tax Details button to see details.
Advertisements
BASIC TAX SETUPS IN E-BUSINESS TAX

These are the basic mandatory tax setups to be performed in the E-Business Tax Module in
R12 to enter Tax lines manually or calculate taxes for any transaction.
1. TAX REGIME: Tax Regime is setup for the taxes in each country and a geographic region
where you do business and where a separate tax applies. A tax regime associates a common
set of default information, regulations, fiscal classifications and registrations to one or more
taxes with same tax requirement.
2. TAXES: Tax is classification of a charge imposed by a Government through a fiscal or a
tax authority. Each separate tax in a tax regime includes records for statuses, tax rates and
rules used to calculate and report tax requirements
3. TAX STATUS: Tax Status is the taxable nature of a product or service in the context of a
transaction for a tax.
4. TAX JURISDICTION: A geographic area where a tax is levied by a specific tax authority.
5. TAX RATE: The rate specified for a Tax status in effect for a period of time; the tax rate
can be expressed as a percentage or as a value per unit quantity
6. TAX RULES: E-business tax uses the tax setups along with the tax rules to decide which
taxes apply to a transaction and how to calculate the tax amount for each tax that applies to a
transaction.
Case Study – 1
Business Requirement: Calculation of USE TAX in AP Invoices based on Ship To Location Zip
code and Balancing Segment of Chart of Accounts.
The requirement of client was as follows:
Use tax was calculated in an AP Invoice based on the combination of the balancing segment in
the chart of accounts and the zip code of a ship to location.
In 11i different sales tax codes were setup for each combination of balancing segment and ship
to location. An offset tax code was attached to each of the sales tax code.
For an invoice where use tax was applicable the user would enter the sales tax code (which has
been attached to an offset tax code) and validate the invoice. This would generate two tax lines
one each for sales tax and offset tax.
After the upgrade to Oracle R12; Use tax can be applied on an invoice in two ways:
1. Similar to 11i make sales tax and offset tax codes to generate the use tax lines in the AP
invoice.
1. Use feature of Self Assessed tax (newly introduced in R12) for accounting of use tax
lines. Concept of Self Assessed tax is explained later in the document.
In this case study we have used option 2 as the base.
Detailed setups performed
1. DEFINE TAX REGIME
Responsibility & Navigation:
Tax Managers – Tax Configuration – Tax Regime – Create
Define one tax regime for country United States as shown below:
2. DEFINE TAXES
Define one tax called US USE TAX under the tax regime created for United States
Tax Managers – Tax Configuration – Taxes – Create
Click on Apply to save the changes
3. DEFINE TAX STATUSES
Define one tax status for the tax regime and tax setup in the previous steps.
Tax Managers – Tax Configuration – Tax Statuses – Create
4. DEFINE TAX JURISDICTIONS

Define one tax jurisdiction for the tax regime and tax setup in the previous steps.
Tax Managers – Tax Configuration – Tax Jurisdictions – Create
5. DEFINE TAX RATES

Define multiple rates for the combination of Corp and Ship to location zip codes. A tax rate is
made for the combination of Tax Regime, Tax and Tax Status.
For instance:
Balancing Segments BAL_A and BAL_B
Ship to Location zipcode 100 and 101
The different rates which can be setup are
USE_BAL_1_100 – 5%
USE_BAL_B_101 – 10%
USE_BAL_A_101 – 2%
USE_BAL_B_100 – 1%
Tax Managers – Tax Configuration – Tax Rates – Create
Click on Tax Accounts to enter the Expense and liability account details
Enter the Tax Expense Account. If this is left blank the expense account for ITEM line will be
used.
The Tax Recoverable/Liability is the Use tax Liability Account to be used.
6. DEFINE TAX RULES
Oracle provides a seeded set of Tax Rules which can be used by the user for tax calculation.
For any transaction made the tax determination process uses these tax rules to decide the
taxes which will apply and the amount of tax which has to be applied for a transaction.
Prerequisites for setting up the Tax Rules:
Step1:
To decide whether use tax applied on any transaction within Payables module a tax
classification code called USE TAX APPLICABLE will be made. A tax classification code is
similar to a tax rate code with a tax rate of 0%.
Step2:
Create Geography Hierarchy:
The various zipcodes which will be used in the tax rules have to be setup in the geography
hierarchy in the trading community architecture.
Trading Community Manager à Administration à Geography Hierarchy
Query for country United States in the below screenshot
Click on View Details tab
Chose the State required and click on View Details

Enter the various County details or enter a default county for the state as shown below. Click on
View Details
Enter the different cities for the county and click on View Details to enter the zip code for each
city.
Enter the zip codes which will be used for tax calculation with the code type as “Tax Geography
Code”. Click on Apply after creating/updating any changes
Step3: Create Tax Determining Factor Sets
Tax Managers – Advanced Setup Options – Tax Determining Factor Sets – Create
The determining factor will work in the following manner:

Since use tax had to be calculated on invoices based on the balancing segment and ship to
location we chose the following values in a determining factor set:
1. Flexfield segment1 of the Line account is the balancing segment
2. The ship to location postal code of the invoice
3. Since use tax will apply only to certain invoices we chose a transaction input factor and
the value is called as tax classification code.
Step4: Create Tax Condition Sets
Tax Managers – Advanced Setup Options – Tax Condition Sets – Create
The tax condition set is made from the tax determining factor set. In the above screenshot we
have made a tax condition set for balancing segment CIP and postal code 62201 using the
determining factor set made in the above set.
TAX RULE SETUP
Tax Managers – Tax Configuration – Tax Rules
The following tax rules will be setup for use tax calculation:
1. Determine Tax Applicability: Since the tax US_USE applies only for use tax we make
this tax applicable only if the tax classification code in the invoice for an ITEM line is “USE TAX
APPLICABLE”

2. Determine Tax Rate – This rule will derive the use tax rate for the invoices using the
determining factor set and condition set. While making the tax rule we enter the determining
factor set and the condition set made in the previous steps as shown in below screenshot.
For each condition set there will be a different tax rate which will be applied.
Example:
As shown in above screenshot there are 4 condition sets:
1. COND_CIP_62201 – This means that the balancing segment is CIP and ship to postal
code is 62201. If the invoice satisfies these two conditions and the tax classification code is
USE TAX APPLICABLE the tax rate used will be USE_CIP_62201.
1. COND_AMC_63103 – This means that the balancing segment is AMC and ship to postal
code is 63103. If the invoice satisfies these two conditions and the tax classification code is
USE TAX APPLICABLE the tax rate used will be USE_AMC_63103.
For all the other rules the default values have been used.
7. CONCEPT OF SELF ASSESSED TAX
A self-assessed tax is a tax calculated and remitted for a transaction, where tax was not levied
by the supplier but is deemed as due (and therefore needs to be paid by the purchaser).
In such cases the purchaser is responsible for calculating and remitting the tax. Self-
assessment is also known as reverse charge or use tax in certain tax regimes.
When self-assessment applies to a tax line, E-Business Tax creates the recoverable and/or
non-recoverable distributions, and Payables creates an additional accounting distribution to
record the liability for the self-assessment.
You can set the self-assessment option:
• At the tax profile level to default to the tax registrations that you create for this party.
• At the tax registration level.
• On an individual tax line.
E-Business Tax applies self-assessment to Payables invoices received by the first party
according to the tax registration setting of the Set for Self Assessment/Reverse Charge option.
The specific tax registration record that E-Business Tax uses is derived either from Determine
Tax Registration rules or from the default tax registration.
We have setup the self assessed tax feature at the Tax Registration level.
Navigation: Tax Managers – Home – External Dependencies – Create First Party : Legal Entity
and Establishments
Query the Legal Entity -View Details – Establishments Tab – Query Establishment (which is the
OU here) – Registrations – Create Tax Registration
Since we are using the self assessed tax feature only for use tax invoices we set up this option
for the tax US_USE only. Other taxes will not have this flag checked.
8. INVOICE CREATION AND USE TAX CALCULATION

Invoice can be created in base table or interface table with the tax classification code as USE
TAX APPLICABLE. Use the correct ship to location and balancing segments in the invoice.
The tax rules will be triggered on validation of the invoice in base tables and the use tax line will
be generated.
Since we are using the self assessed tax feature there will not be any tax displayed on the
invoice line, the tax details will be visible in the Tax Details form. They will also not be stored in
ap_invoice_lines_all table; instead they will be stored in zx_lines table with the trx_id which will
be the invoice_id of the invoice.
Tax lines form indicating the use tax details.
Case Study – 2
Business Requirement: Calculation of SALES TAX in AP for Invoices made from source ERS
based on Supplier site pin code
The requirement of client was as follows:
There were many invoices created in AP using the ERS source i.e create the PO and Receipt in
Purchasing module and then run the “Pay on Receipt” program to generate the invoice in
interface tables with source as ERS.
The standard Payables Open Interface Import program will then import these invoices into base
oracle.
Sales tax applies on some of these ERS transactions based on the zip code of supplier site.
For instance: An ERS invoice with a supplier site A having zip code 63301 has a tax rate of 10%
to be applied where as supplier site B having zip code 62284 has a tax rate of 6% to be applied.
Since the ERS invoice which is inserted into the interface table consists of only ITEM line we
needed to insert one more TAX line with the correct amount. Additionally the total invoice
amount also has to be corrected to include the tax amount.
Detailed setups performed for the same.
1. DEFINE TAX REGIME
Tax Managers – Tax Configuration – Tax Regime – Create
Define one tax regime for country United States as shown below:
2. DEFINE TAXES

Define one tax called US SALES TAX under the tax regime created for United States
Tax Managers – Tax Configuration – Taxes – Create
Click on Apply to save the changes
3. DEFINE TAX STATUSES
Define one tax status for the tax regime and tax setup in the previous steps.
Tax Managers à Tax Configuration à Tax Statuses à Create
4. DEFINE TAX JURISDICTIONS

Define one default tax jurisdiction for the tax regime and tax setup in the previous steps.
Tax Managers – Tax Configuration – Tax Jurisdictions – Create
5. DEFINE TAX RATES

Define tax rates for each supplier site zip code. A tax rate is made for the combination of Tax
Regime, Tax and Tax Status.
For instance:
Supplier site zip codes are 63119 and 61548.
The different rates which will be setup are
SALES_63119 – 7.575%
SALES_61548 – 7.25%
Click on Tax Accounts to enter the Expense and liability account details
Enter the Tax Expense Account. If this is left blank the expense account for ITEM line will be
used.
The Tax Recoverable/Liability is the Use tax Liability Account to be used. Since this is a sales
tax rate we enter the default account of 000 for the same.
6. DEFINE TAX RULES
Oracle provides a seeded set of Tax Rules which can be used by the user for tax calculation.
For any transaction made the tax determination process uses these tax rules to decide the
taxes which will apply and the amount of tax which has to be applied for a transaction.
Prerequisites for setting up the Tax Rules:
Step1:
To decide whether use tax applied on any transaction within Payables module a tax
classification code called SALES TAX APPLICABLE will be made. A tax classification code is
similar to a tax rate code with a tax rate of 0%.
Step2: Create Geography Hierarchy:

The various zipcodes which will be used in the tax rules have to be setup in the geography
hierarchy in the trading community architecture. Set up the zip codes to be used for the supplier
sites where sales tax needs to be calculated based on the step 2 in Point 6 in Case study 1.
Step3: Create Tax Determining Factor Sets
Tax Managers – Advanced Setup Options – Tax Determining Factor Sets – Create
The determining factor will work in the following manner:

Since sales tax had to be calculated on invoices based on the supplier site for ERS invoices the
determining factors would be:
1. Geography – Ship From postal code
2. Transaction Input Factor – Tax classification code which will be used for ERS invoices.
Step4: Create Tax Condition Sets
Tax Managers – Advanced Setup Options – Tax Condition Sets – Create
The tax condition set is made from the tax determining factor set. In the above screenshot we
have made a tax condition set for postal code 61548 and tax classification code SALES TAX
APPLICABLE using the determining factor set made in the above set.
TAX RULE SETUP
Tax Managers – Tax Configuration – Tax Rules
The following tax rules will be setup for use tax calculation:
3. Determine Tax Applicability: Since the tax US_SALES applies only for ERS Sales Tax
we make this tax applicable only if the tax classification code in the invoice for an ITEM line is
“SALES TAX APPLICABLE”

4. Determine Tax Rate – This rule will derive the sales tax rate for the invoices using the
determining factor set and condition set. While making the tax rule we enter the determining
factor set and the condition set made in the previous steps as shown in below screenshot.
For each condition set there will be a different tax rate which will be applied.
Example:
As shown in above screenshot there are 4 condition sets:
1. COND_SALES_63119 – This means that if the ship from postal code is 63119 and the
tax classification code in the invoice is SALES TAX APPLICABLE then the tax rate used will be
SALES_63119.
1. COND_SALES_61548 – This means that if the ship from postal code is 61548 and the
tax classification code in the invoice is SALES TAX APPLICABLE then the tax rate used will be
SALES_61548.
For all the other rules the default values have been used.
7. INVOICE CREATION AND SALES TAX CALCULATION FOR ERS INVOICE.
Generate the ERS invoice in the invoice interface tables using the program Pay on Receipt
program.
Update the following values for the ERS invoice in the interface table:
TAX CLASSIFICATION CODE – SALES TAX APPLICABLE
CALCULATE TAX AMOUNT DURING IMPORT – Set the flag to Y
ADD TAX TO INVOICE AMOUNT – Set the flag to Y
The calculate tax amount flag and add tax to invoice amount is set to Y so that the Payables
Open Interface Import program would trigger tax rules and calculate the tax amount and also
add the tax amount to the invoice amount. Hence the invoice will be imported with the tax line
and correct invoice amount.
Following is the update script for the same:
UPDATE apps.ap_invoices_interface
SET add_tax_to_inv_amt_flag = ‘Y’
AND calc_tax_during_import_flag = ‘Y’
WHERE source = ‘ERS’
UPDATE apps.ap_invoice_lines_interface
SET tax_classification_code = ‘SALES TAX APPLICABLE’
WHERE invoice_id IN (SELECT invoice_id
FROM apps.ap_invoices_interface
WHERE SOURCE = ‘ERS’)
Snapshots of ERS invoices in the interface table.
Invoice header in the interface table before it was processed.
Invoice line in the interface table
Supplier site pincode – 62223
After importing this invoice; the tax line has got generated based on the tax rule for Supplier
site. The invoice amount has also changed from 1000 to 1073.50
E-Business Tax to set up and maintain your transaction tax requirements in all geographic locations
where you do business. You can set up tax configurations to include the rules, default values, and
other information necessary for each separate tax requirement. At transaction time, E-Business Tax
uses your tax configuration to determine the taxes that apply to each transaction and to calculate the
tax amounts.
The tasks involved in setting up a tax requirement in E-Business Tax fall into three general
categories:
1. Setting up transaction taxes.
2. Completing all of the setups and settings related to the processing of taxes on transactions.
3. Setting up tax rules and defaults to manage tax processing.
E-Business Tax Process

Tax Authority
“A government entity that regulates tax law, administers, or audits one or more taxes”.
Tax Regime
“The set of tax regulations that determine the treatment of one or more taxes administered by a tax
authority”
Examples of a tax regime include:
 A sales and use tax in the United States includes rules for state, county, and city sales and
use taxes.
 An excise tax regime in India includes rules for excise tax and additional excise tax.
 A VAT tax regime in Argentina includes rules for standard VAT, additional VAT, and
perception VAT.
Example in UG, in Argentina there is a tax similar to European VAT called Impuesto al Valor
Agregado (IVA). There is another tax called Impuesto al Valor Agregado Adicional, levied on
unregistered customers. These two charges are together commonly referred to as IVA. However, in
your tax configuration you define these charges as two
different taxes under the one tax regime called, for example, IVA-Argentina. This configuration
specifies that a company may charge two taxes--IVA and IVA Adicional--but these two charges are
levied by the same tax authority and the company receives only one tax registration for both taxes.
In the example above, you define the IVA-Argentina tax regime to contain the taxes IVA and IVA
Adicional. You can then define the tax registrations that your company, customers, and suppliers
have for this tax regime, instead of defining tax registrations for the individual taxes.
Thus, although UK VAT, French TVA, and Argentine IVA are all value added taxes, you define each
as a separate tax regime with one or more taxes under each regime for the applicable country.
Tax
“A distinct charge imposed through a fiscal or tax authority”
Examples of a tax include VAT for the United Kingdom and TVA for France.
Tax Jurisdiction
“A geographical area where a tax is levied by a specific tax authority or where a specific tax rate
applies”
A tax jurisdiction is limited by a geographical boundary that encloses a contiguous political or
administrative area, most commonly the borders of a country. For example, the countries of UK,
France and Argentina serve as the respective tax jurisdictions for their VAT tax regimes and related
taxes.
Often this contiguous political or administrative area falls within a country, such as a state, province,
city or a county tax jurisdiction; examples include US state sales tax and Canadian Provincial Sales
Tax (PST). In countries where you define tax jurisdictions at a level lower than the country level , you
typically need to define tax registrations for your company or your third parties at the level of tax
jurisdictions. You can define a tax registration, for example, either to capture a tax registration
number or to specify nexus for a supplier in a particular tax jurisdiction.
Examples of tax jurisdictions include:
 The tax jurisdiction for VAT in Germany is the country of Germany.

 The tax jurisdiction for a San Jose city tax is the City of San Jose, California.
 The tax jurisdiction for Provincial Goods and Services tax (PST) in Canada is a particular
Province, such as Ontario or British Columbia.
Tax Status
“The taxable nature of a product or service in the context of a transaction for a tax type”
Examples of a tax status include taxable standard rate, zero rated, exempt, and non-taxable. A tax
status is similar to the concept of the tax type definition used within Payables and receivables in
releases prior to Release12.
Tax Rate
“The rate specified for a tax status in effect for a period of time. You can express the tax rate as a
percentage or as a value per unit quantity”
An example of a tax rate is 7.5% for a state sales and use tax.
Defining Recovery Types and Recovery Rates
In some tax regimes, a tax that is paid by a registered establishment can claim back all or part of
taxes due from the tax authority. In E-Business Tax this is called tax recovery. There are usually
many regulations surrounding the details of tax recovery. Typically only a portion of the tax amount
paid is recoverable, and tax authorities designate the
tax recovery rates that indicate the extent of recovery for a specific tax.

In Canada, two types of recovery possible on Goods and Services Tax (GST). Certain types of
establishment can claim both an Input Tax Credit and a Tax Rebate. Both of these types of recovery
will have one or more recovery rates applicable under different transaction conditions. E-Business
Tax defines these two recovery types as primary and secondary recovery types. For the primary
recovery type (and, in rare cases, the secondary recovery type), you can define one or more
recovery rate codes with values between 0% to 100%. Like a tax rate code, the recovery rate code
can have different rates for different effective periods
Operating Unit Tax Accounts
The tax accounts that the system uses to post the tax amounts derived from your transactions.
The tax accounts you define serve as default accounting information for taxes, tax rates, tax
jurisdictions, and tax recovery rates.
Processing Taxes on Transactions
After you set up the basic tax configuration for the taxes that your company's legal entities and
operating units are subject to, you must decide how to automate the processing of taxes on your
transactions.
The tax determination process derives the taxes that apply to a transaction and the tax amounts
charged on the transaction by evaluating the factors of the transaction according to the rules that
you define. These taxability factors are:
Party - The parties of the transaction. This can include:
First party legal entities.
Ship from/ship to parties; bill from/bill to parties.
Tax registrations and registration statuses of each party.
Type or classification of a party.
Product - The products transacted. This can include:
Designation of physical goods or services.
Type or classification of a product.
Place - The places involved in the transaction, including the ship from and ship to locations, and the
bill from and bill to locations.
Process - The kind of transaction that takes place. This can include:
Procure to Pay transactions, such as purchases, prepayments, and requisitions.
Order to Cash transactions, such as sales, credit memos, and debit memos.
Type of sale or purchase: retail goods, manufactured goods, intellectual property, resales.
Use these factors to develop your tax determination process and translate your operational
procedures into tax rules.
Before starting the setups in e business TAX, one needs to check if the following setups are
complete or not
Set up tax regimes for the taxes in each country and geographic region where you do business and
where a separate tax applies. A tax regime associates a common set of default information,
regulations, fiscal classifications, and registrations to one or more taxes with the same tax
requirement.
The tax regime provides these functions:
 groups similar taxes together.

 designates the geography within which taxes apply.
 defaults the settings and values you define to each tax in the regime.
 contributes to the definition of configuration options and third party service subscriptions.
 optionally provides a single registration for all taxes associated with the regime.
 defines the use of fiscal classifications.
1. The common tax regime setup is one tax regime per country per tax type, with the tax
requirements administered by a government tax authority for the entire country.
2. There are also cases where tax regimes are defined for standard geographical types or
subdivisions of a country, such as a state, province, county, or city. In these cases, you base
the tax regime on the Trading Community Architecture (TCA) standard geography.
3. There are more rare cases where a tax regime is based on disparate parts of a country or
more than one country. In these cases, you can create one or more tax zones and set up tax
regimes for these tax zones
4. You can also set up a tax regime as a parent tax regime to group related tax regimes
together for reporting purposes.
Taxes and Geographic Locations
In E-Business Tax you can set up geographic information at three levels: tax regime, tax, and tax
jurisdiction. You can use these levels to define different tax requirements within a geographic
hierarchy:
 Tax regime. Tax regime level defines a tax that applies to a country or tax zone. For
example, the tax regime United States Sales and Use Tax refers to the country United
States.
 Tax. Tax level defines a tax and the geographic level for the tax, such as a City tax or a
County tax.
 Tax jurisdiction. Tax jurisdiction level defines a geographic entity and the tax and tax
jurisdiction rates, if any, that belong to this entity. For example, a US County Sales Tax
jurisdiction for San Francisco county refers to the county San Francisco as a child of the
state California as a child of the country United States.
Tax-level controls for this tax regime:

Allow Tax Recovery - Lets you set up tax recovery for the taxes in this tax regime.
You must set this option to set up tax recovery definitions at the tax level and to set up tax recovery
rates for taxes in this tax regime.
Allow Override and Entry of Inclusive Tax Lines - Lets you change the setting for tax inclusive
handling at the tax level.
You should only set this option if the taxes in this tax regime vary in their treatment of tax inclusive
handling. For example, if all taxes in this tax regime are inclusive of tax for all transactions, then do
not set this option.
Allow Tax Exemptions - Lets you set up customer tax exemptions for this tax. A tax exemption is a
full or partial exclusion from taxes within a given time period.
You must set this option to set up tax exemptions for this tax regime and for taxes in this tax regime.
Allow Tax Exceptions - Lets you designate special tax rates for specific products as determined by
the tax authorities. A tax exception is a condition or combination of conditions that result in a change
from the standard values for a
particular product.
You must set this option to set up product tax exceptions for taxes in this tax regime.
Enter a tax currency:
The tax currency is the currency required by the tax authority.
You use the tax currency to pay the tax authority and to report on all tax transactions.
The tax currency may differ from the functional currency and transaction currency.
The functional currency is the accounting currency of your primary ledger. The transaction currency
is the currency or currencies used on your transactions.
Enter the default tax authority to use on your tax reports, for the submission of tax reports
(Reporting) and the submission of tax remittances (Collecting).
Use the Allow Tax Inclusion field to define the nature of tax inclusive handling. Tax inclusive
handling defines the relationship, as designated by the tax authority, between the line amount and
the tax amount:
Standard Inclusive Handling - The price on the transaction line is inclusive of tax.
Standard Non-Inclusive Handling - The price on the transaction line is exclusive of tax. The tax
amount is added to the price.
Special Inclusive Handling - Use this option for special tax handling, such as a taxable base
amount based upon the line amount rather than the adjusted line amount, or based on the line
amount plus another tax amount
If you set the Allow Tax Recovery option, select the default recovery settlement:
 Immediate - Tax recovery is available at invoicing.
 Deferred - Tax recovery is available only after the invoice is paid
Check the Allow Cross Regime Compounding box and enter the compounding precedence, if
taxes in this regime are involved in any compounding operation with taxes in another regime of the
same configuration owner. The compounding precedence indicates the order in which to consider
the taxes in each regime.
You must set this option in each of the participating tax regimes if any of these cases apply:
• a tax in this regime impacts the taxable base of a tax in another regime.
• a tax in another regime impacts the taxable base of a tax in this regime.
• a tax in this regime impacts the taxable base of a tax in another regime on the same transaction
line.
Note: You must ensure that you set this option correctly for each tax regime. You cannot update this
setting after you save the tax regime record.
You must also complete these setup steps for cross-regime compounding:
• Define the compounding precedence for the taxes in this regime according to the cross-regime
compounding requirements.
• Set up a taxable basis tax formula or tax calculation tax formula for each tax involved in the
compounding.
• Set up a Taxable Basis tax rule or Calculate Tax tax rule for each tax regime and tax, and assign
the tax formulas to these rules.
1. Geography structure of the country
Navigate to
Define the geograpy hierarchy

setups, forms and reports used in Manufacturing and related modules
A tax jurisdiction is a geographic region or tax zone where a specific tax authority levies a tax. A
tax jurisdiction specifies the association between a tax and a geographic location.
At transaction time E-Business Tax derives the jurisdiction or jurisdictions that apply to a
transaction line based on the place of supply. The place of supply is the location where a
transaction is determined to take place for a specific tax. E-Business Tax either uses a default
place of supply or derives a place of supply based on tax rules.
You also use tax jurisdictions to define jurisdiction-based tax rates. A tax jurisdiction tax rate is a
rate that is distinct to a specific geographic region for a specific tax. For example, the tax defined
as California city sales tax can have different rates for each city tax jurisdiction.
You must set up at least one tax jurisdiction for a tax before you can make the tax available on
transactions. A tax can apply to multiple jurisdictions, such as California county sales tax to all
counties or Canadian Goods and Services Tax to many provinces. If you enable multiple
jurisdictions for the tax, you can create multiple tax jurisdictions at once based on the geographic
hierarchy defined for the tax. You can only do this if the tax uses the TCA master geography.
The tax within a jurisdiction can have different rates for the parent and child geographies. For
example, a city sales tax rate can override a county rate for the same tax. In this case, you can set
up an override geography type for the city and apply a precedence level to the city and county
tax jurisdictions, to indicate which jurisdiction takes precedence.
In addition, in some cities a different city rate applies to the incorporated area of the city, called
the inner city. In these cases you can set up an inner city tax jurisdiction with its own rate for the
applicable customers and Receivables tax. Inner city tax jurisdictions are often based on postal
code groupings.
Set up the tax statuses that you need for each tax that you create for a combination of tax regime,
tax, and configuration owner.
A tax status is the taxable nature of a product in the context of a transaction and a pecific tax on the
transaction. You define a tax status to group one or more tax rates hat are of the same or similar
nature.
For example, one tax can have separate tax statuses for standard, zero, exemption, and educed
rates. A zero rate tax status may have multiple zero rates associated with it in rder to handle
different reporting requirements for zero rate usage, such as Intra EU,zero-rated products, or zero-
rated exports.
You define a tax status under a tax and a configuration owner, and define all applicable ax rates and
their effective periods under the tax status. The tax status controls the efaulting of values to its tax
rates.
1) Set as default Tax status: Each tax status must have at least one default. Tax Rules
must be written to set alternate values as required.
2) Allow Tax Exemptions: With a rule based approach to setting tax exemptions,
exempt transactions will be linked to an exempt tax status and rate. Setting the
"Yes" value to this configuration option will also allow a user to define a tax
exemption on a transaction or directly in the party tax profile to record the exempt
reason code. This is however not required nor enforced. Because the exemptions
are primarily tracked by way of tax status/rates we suggest that you use Caution
when reporting if you intend to use the tax exemption fields on the seeded reports.
Setups Tax Rates:
Set up tax rates for your tax statuses and tax jurisdictions. For tax statuses, set up a tax rate
record for each applicable tax rate that a tax status identifies. For tax jurisdictions, set up tax rate
records to identify the tax rate variations for a specific tax within different tax jurisdictions. For
example, a city sales tax for a state or province may contain separate city tax jurisdictions, each
with a specific rate for the same tax.
You can also define tax recovery rates to claim full or partial recovery of taxes paid. You can
define tax jurisdiction and tax status rates as a percentage or as a value per unit of measure. For
example, a city may charge sales tax at a rate of 8% on most goods, but may levy a duty tax with
a special rate of $0.55 per US gallon on fuel. Values per unit of
measure are in the tax currency defined for the tax.
You define tax rate codes and rate detail information per rate period. Rate periods account for
changes in tax rates over time. A tax rate code can also identify a corresponding General Ledger
taxable journal entry.
Recoverable tax is a tax that allows full or partial recovery of taxes paid on purchases, either as a
recoverable payment or as an offset against taxes owed. Also known as "Input Tax Credits" this tax
is normally recovered because it was paid on an item that will be used in creating another item sold
to an end user.
There are usually many regulations surrounding the details of tax recovery. Typically only a portion
of the tax amount paid is recoverable, and tax authorities designate the tax recovery rates that
indicate the extent of recovery for a specific tax. As with all tax setup, consult your tax department or
a tax professional to determine how you should configure your system.
Some Examples:
1. 100% Recovery Tax: Most VAT-type taxes allow for full recovery of taxes paid on goods and
services that relate to taxable business supplies.
2. Partial Recovery Tax: In cases where an organization purchases both taxable and exempt
supplies, the tax authority can designate a partial recovery rate to reflect the combination of taxable
and exempt statuses.

Country defaults and controls:

1. Country Defaults
2. Tax Reporting Types
3. Configuration Owner Tax Options
4. Application Tax Options
Setup Tax Zones:
Use tax zones to group existing geographical regions that share the same tax requirement. You
can use tax zones with tax regimes, to identify tax requirements for a special geographic area and
to create parent tax regimes that represent a related grouping of geographic regions for tax
reporting purposes. You can also use tax zones
with tax rules, to create tax rules that refer to a specific geographic location.
The use of tax zones is optional and depends on your overall tax setup planning. For example, if
a separate economic community exists in part of a country only, you can either set up a tax zone
and corresponding tax regime for the applicable geographic area, or set up a country tax regime
and use applicability rules to exclude the parts of the country where the tax requirement does not
apply.
The tax zone setup makes use of the Trading Community Architecture (TCA) master reference
geography hierarchy. The master reference geography hierarchy identifies the hierarchical
structure of a country, such as Country: State: County: City: Postal Code in the United States,
and identifies which levels are mandatory for the tax zone. A tax zone
type references a specific part of a master reference geography hierarchy. You create tax zones
within a tax zone type to uniquely identify tax requirements within the area defined by the tax
zone type.
You can update the information in a tax zone at any time. You can also update the geographic
information in a tax zone type, as long as the tax zone type does not contain tax zones. If you
apply an end date to a geographic entity in TCA, then this removes all tax zones and tax zone
types associated with the entity.
Parties: Tax Profiles and Registrations:

Parties include:
1. All legal entities, legal establishments, and operating units in your organization that have a
transaction tax requirement.
2. Your customers and suppliers and their locations.
3. Tax authorities that administer tax rules and regulations.
A tax profile is the body of information that relates to a party's transaction tax activities. A tax profile
can include tax registration, tax exemptions, configuration options, main and default information,
party fiscal classifications, tax reporting codes, and account tax details.
The tax registration contains information related to a party's transaction tax obligation with a tax
authority for a tax jurisdiction where it conducts business. The tax registration is part of the tax profile
of a first party legal establishment and a third party and third party site.
A tax exemption defines, for a customer or a customer and product, a discount or replacement
percentage that reduces the applicable tax. The configuration options identify the tax regimes
associated with a first party and the configuration owner and service provider settings associated
with each tax regime.
The configuration options are part of the tax profile of configuration owners, that is, first party
legal entities and operating units owning tax content.
The main and default information identify characteristics of and default values for the transactions
associated with a party.
The party fiscal classifications optionally assigned to a party are used as determining factors in tax
rules.
The tax reporting codes optionally assigned to a party capture tax information from party
transactions for both internal and tax authority reporting requirements.
The account tax details maintain Release 11i migrated tax information for customer and supplier
accounts.
Setting Up Parties for Self-Assessment
You can let a first party self-assess the taxes calculated on the Payables invoices it receives. A self-
assessed tax is a tax calculated and remitted for a transaction, where tax was not levied by the
supplier but is deemed as due (and therefore needs to be paid by the purchaser). In such cases the
purchaser is responsible for calculating and remitting
the tax. Self-assessment is also known as reverse charge or use tax in certain tax regimes.

When self-assessment applies to a tax line, E-Business Tax creates the recoverable and/or non-
recoverable distributions, and Payables creates an additional accounting distribution to record the
liability for the self-assessment.
You can set the self-assessment option:
 At the tax profile level to default to the tax registrations that you create for this party.
 At the tax registration level.
 On an individual tax line.
E-Business Tax applies self-assessment to Payables invoices received by the first party according to
the tax registration setting of the Set for Self Assessment/Reverse Charge option. The specific tax
registration record that E-Business Tax uses is derived either from Determine Tax Registration rules
or from the default tax registration.
Under normal circumstances, the Determine Tax Registration rules or default tax registration will
derive the Bill From party as the place of supply for purchase transactions where the supplier is
responsible for calculating the transaction tax and collecting it from the customer. In the case of Self
Assessment, Reverse Charge, or, in the United States, Use tax, customers are responsible for self-
assessing the tax.
Customers will therefore self-assess under their own tax registration, and the Determine Tax
Registration rules or default tax registration will derive instead the Bill To party registration. In this
case, you expect to see the Set for Self Assessment/Reverse Charge option set on the applicable
first party establishment registration record.
Set up tax profiles for your first party legal entities and legal establishments. First party legal
entities identify your organization to the relevant legal authorities, for example, a national or
international headquarters. First party legal establishments identify each office, service center,
warehouse and any other location within the organization that has a tax requirement.

When you create a legal entity, the system automatically creates a legal entity establishment. You
can create additional legal establishments according to your needs. For each legal establishment
there are one or more tax registrations, depending upon the tax requirements of the applicable tax
authority.
To set up a party tax profile for a first party legal entity or first party legal establishment navigate to
the Create Tax Profile page.
1. Party main information values default to all tax registrations and invoices
belonging to this party. You can update these values at the tax registration level and, if authorized, at
the invoice line level.
Note: The values set at the tax registration level override the values set at the party tax profile level.
2.1 Check the Set for Self Assessment/Reverse Charge box to automatically self-assess taxes on
purchases.
2.2 If applicable, enter a tax classification code to use as a determining factor in tax rules for this
party or party site.
2.3 Set the rounding level and rounding rule for this party.
2.4 If this party intends to send or receive invoices with invoice line amounts inclusive of tax, check
the Set Invoice Values as Tax Inclusive box.
This option overrides the tax inclusive handling setting at the tax level, but not at the tax rate level.
Responsibility: Legal Entity Manager

Navigation: Legal Entities > Create Legal Entity
Legal Entity: A legal entity is a clearly identified entity, which is given rights and responsibilities
under commercial law, through registration with the country's appropriate legal authority. Legal
entities are responsible to account for themselves to company regulators, taxation authorities, and
owners according to rules specified in the relevant legislation.
In Release 12 Legal Entities "own" one or more Operating Units which in turn "own" transactions.
Tax Relevancy:
1) For E-Business tax, a tax regime can be associated to a Legal Entity and then optionally one or
more Operating units in that Legal Entity can share the tax setup.
2) The Registration defined on the Legal Entity record is the source for the legal establishment
defaults. The Establishment tax profile in turn feeds the Bill From in AR and the Bill To / Ship to in
AP.
3) The checkbox on the Legal Entity controls self-assessment of taxes. For Canada, GST and HST
must be self-assessed for imported goods. Be sure you update the Legal Entity to reflect this after it
is created
Legal Establishment First party legal entities identify your organization to the relevant legal
authorities, for example, a national or international headquarters. First party legal establishments
identify each office, service center, warehouse and any other location within the organization that
has a tax requirement. When you create a legal entity, the system automatically creates a legal
entity establishment. You can create additional legal establishments according to your needs. For
each legal establishment there are one or more tax registrations, depending upon the tax
requirements of the applicable tax authority.
If you have multiple legal establishments you should additionally create records as children of the
Legal Entity. Be sure to set the "Self Assessment" to the proper value when creating additional legal
establishments.
Tax Relevancy
1) The Registration defined on the legal establishment feeds the Bill From in AR and the Bill To /
Ship to in AP. These addresses are then considered if your tax rules use these as the basis for tax
calculation.
2) The checkbox on the Legal Establishment controls self-assessment of taxes. For Canada, GST
and HST must be self-assessed for imported goods. Be sure you update the Legal Establishment to
reflect this after it is created
Ledger: Also known as set of books in 11i and prior releases this is the object that owns the
accounting structure used for transactions.
Operating Unit: Assign operating units to the primary ledger to partition subledger transaction data
when multiple operating units perform accounting in the context of one or more legal entities. At
least one Operating Unit must be defined for each legal entity and set of books. Operating Units are
also referred to as "Organizations".
The Operating Unit Location is taken from the Legal Establishment record referenced in section 3
above
Tax Relevancy: Operating Unit along with Legal Entity represent two levels where tax content can
be owned and tax setup performed.
O2C
P2P
Projects
Fusion Cloud Financials
Document approval and Assign Roles
FA
Q&A
1.What is Functional setup Manager in Oracle fusion Financials?

Functional setup manager is the implementation tool provided by oracle in
Fusion application. This is one of the most useful tools while doing
implantation in Oracle fusion. Functional Setup Manager (FSM) is a fully
integrated setup tool in Oracle Fusion Applications which provides end-to-end
guidance on processes to manage implementation and maintenance of the
applications thru its life cycle.
2.What is Auto Post Criteria Set?

You can automatically post journal batches that meet specific criteria that you
defined in an AutoPost criteria set. You can define multiple criteria sets that
include a range of journal effective dates and multiple AutoPost priorities.
AutoPost priorities include combinations of ledger or ledger set, journal
source, journal category, balance type, and period.
3. What is Translation in Oracle Fusion

The Translate General Ledger Account Balances is a process by which you
restate an entire ledger or a set of balances for a company from the ledger
currency to a reporting currency. Oracle Financials Cloud General Ledger
supports translation that restates your standard actual ledger
currency balances to a target currency using the appropriate currency
conversion rates.
The Translate General Ledger Account Balances process is typically run once
you have completed all journal activities for an accounting period. You run this
process at the end of an accounting period, after all transactions have been
processed and reconciled. You translate the actual ledger
currency balances of your ledger to another reporting currency to help you
consolidate the financial results
4.What is Recurring Journals?

Answers: Recurring journals uses for that entries which we entered or
reported every month. With the Help of Recurring Journals, we don’t need to
enter these manually every month but instead off system will do this
automatically.
Three Recurring Journals
Skeleton Journal Entries: Skeleton entries affect the same accounts each
period, but have different posting amounts.
Standard Recurring Journal Entries: Standard recurring journal entries use the
same accounts and amounts each period.
Recurring Journal Formula Entries: Formula entries use formulas to calculate
journal amounts that vary from period to period.
5.What is Revaluation in General Ledger ?

Answers :
We use Revaluation for the Foreign currency amounts. This helps to evaluate
the exact amount of Liability and revenue for the period During Month End or
unrealized gain/loss amount which occurred due to foreign exchange rate
fluctuations. Revaluation happens on the account level. We can choose for
which account we need to run the Revaluation. For Example, My Total
Liability as per my GL account is 2 Lakh in which many of the invoices are
foreign currency. So system has fetch the exchange rate as per the Invoice
Date and calculate the Liability but in actual this Liability is Wrong because if
now I have to pay this Invoice I have to pay with the Current Exchange rate so
that is the same thing Revaluation process does in the General Leger In which
It create the Revaluation Journal based on the Current Exchange rate for the
difference of the exchange rate price and evaluate the final Profit and Loss so
by this way , we do have right figures in the hand about liability and the
revenue . Revaluation only do for GL accounts. Revaluation process runs
during the period end. This process creates the Journal Entry that
either Increase or decrease the functional currency amount for that GL
account. In the Revolution Process also, this unrealized gain/loss Journal will
be auto revered during the beginning of the next period. So, this makes the
revaluation process completes.
6.Difference between Translation and Revaluation in General Ledger?

Answers:
Revaluation is used to find the unrealized gain/loss amount which occurred
due to foreign exchange rate fluctuations. This only happens for the Foreign
Currency transactions but on the Other Hand Translation is totally different,
this is used to convert the Prepared the GL balances in to Other Currency.
This helps to prepare the Financials GL reporting’s in other currency from your
functional Leger currency. Revaluation happen during the month end, but
translation happened after Period end activities. Both Revaluation and
Translation happens for GL accounts.
7.What are the Types of Journal Entries in GL?

Manual Journal Entry: - Most Common Journal entry to create the Basic GL
journal Accounting Transactions.
Reverse Journal Entry: - This Journal entry related to the reversal of

the Original Manual Journal entry. We can Post, the Reverse Journal in the
Current Open Month or in the Future Opening Periods too.
Recurring Journal entries: - This type of Journal Entries crested only once but
it automatically repeats for each Accounting Period or Month as per the rules.
Mass allocation: -
Mass Allocations are journal entries that utilize a single journal entry formula
to allocate balances across a group of cost centers, departments, divisions or
other segments;
8.What is Balancing segment in the Chart of accounts?

Answers :
Balancing Segment is one of the Import part of the chart of Accounts or
Accounting Flexfield. In Oracle Accounting Flexfield is the combination of
Multiple segments values. Each Segment values represent the one of the
characteristics of the Chart of Account like (Company, Location, Cost Center,
Department, Sub Account, Project like many). But in these GL segments
combination we should have one Segment which could be act like Balancing
Segments.
Balancing Segments helps to ensure that all journal entries balance for each
value of the balancing segment and to ensure that entries that impact more
than one balancing segment use the appropriate intercompany Account.
Balancing Segments helps to make balancing the GL journals. We can define
only one balancing segment for a one chart of account. It is best practice for
the balancing segment to equate to company so that the debits and credits in
the General Ledger balance by company.
9.What is Natural Account in Chart of account and What Is the Purpose of this
?
Answers :
Natural Account is one of the Important segments of the accounting Flexfield.
No char of Account or Accounting KFF can design without using the Natural
Account Type. We have to enable one of the Chart of accounts (KFF)
segments to Natural Account”.
Natural Account Segment Type represent the Type of accounts Values in the
Natural Account Segments (Like Asset, Expense, Liability, Revenue,
Ownership). Only one natural account segment can be defined in a chart of
accounts.
10.What is Pay Alone in AP Invoice?
Answers :
Pay alone is something related to Invoice Payment. This is the Flag we set for
AP Invoice, It Means this invoice will be paid alone. For example, Supplier A
has 3 Invoices, but for 1 Invoice we have enabled the Pay Alone Flag Then
When we will run the Payment Batch then System will create one Check for
two invoices and Separate one Check for Pay Alone Invoice. This Is the
Working of Pay Alone.
11.What is Recurring Invoice in Oracle ?

Answers :
As its name represents ‘Recurring’. Recurring means again and again. If any
Organization books the Office rent invoice every month for the same amount
or any other fixed expenses every month then oracle has provided the
Recurring Invoice. We just need to do the recurring Invoice setup for that
amount and system will create the invoice automatically on the First day of the
Months.
12. What is the Use of Payables Trial Balance report ?

Answers :
Payables Trial Balance Report shows the Total Liability or the Supplier
Outstanding in the System. This Report shows the Liability in the System
supplier and Site Level. This Provide the Summary Information’s for all the
Unpaid amount for the Supplier Invoices which are validated.
13.What is ADFDI in Fusion?

ADFDI is another Data Import tool in oracle fusion to insert the data in the
Oracle Cloud. ADFDI is the same as WebADI in Oracle Apps which is totally
integrated with the application. This works online as compared to the FBDI
which works offline means we prepare the data offline so ADFDI provided the
real time data validation.
14.What are the Reporting tools available in the Oracle Fusion?
BIP Reports
OTBI reports
Smart View Reports
Financial Reporting Studio
15.What is FR Studio in Oracle Fusion

Financial Reporting Studio is a client based Financial Reporting tool which is
uses to build the Financial reports in Oracle Fusion. This is more like FSG
reports in Oracle Apps. This FR studio works on the GL balances. This Uses
drag and drop functionality to create a grid to design the rows, columns
and pages of the financial report. This Contains grids and other objects that
are reusable across multiple reports. FR Studio Uses the GL Balances Cube
dimensions on either rows, columns, pages,
or Point of Views (POV).
16.What is Smart View Report?

Smart View is Excel Add In based Reporting Tool Suitable for End users
comfortable with Excel spreadsheets. This Provides the Multidimensional
View of data. Smart View Only provided the GL data.
Smart View is:
Microsoft Excel Based Reporting
Optionally, available for upload to Financial Reporting Center

and then download to your local drive for use.
Balance sheets using a familiar spreadsheet environment.
Smart View has two main features: -

Ad hoc Analysis: Enables you to interactively analyses balances.
Financial Reports: Define reports like income statements and
balance sheets using a familiar spreadsheet environment.
17.What is LDAP in Oracle cloud

DAP full form is Lightweight Directory Access Protocol. This is the directory
available in the Oracle Fusion/Cloud application . We can say this as LDAP
directory in Oracle cloud. The role of the LDAP in Oracle Fusion is to take
care the Oracle Fusion Application users accounts and the Role Information's.
All the Users related stuff handled in this LDAP directory separately.
18. What is Send Pending LDAP Requests

But if we are creating Users directly in the Fusion application like for example
from Employees Web pages directly then in this process as vice versa we
need to send the Information's from fusion application to the LDPA directory to
make this request complete to create new User accounts for the New or
Existing Employees.
For this Process to create User accounts from Employees we need to send
the Information from Fusion application to the Oracle LDAP directly so for this
Oracle has given us the Standard Request 'Send Pending LDAP
Requests' scheduled process to process those requests. This helps to send
information's to LDAP directory for those User requests which are created
itself in the fusion application.
19.What is Run User and Roles Synchronization Process in Oracle Cloud:

Retrieve Latest LDAP Changes process
Answers :
Run User and Roles Synchronization Process helps to synchronize the LDAP
directory with Oracle Cloud Application. In Oracle cloud, User Accounts and
User roles information’s stores in the Lightweight Directory Access Protocol
(LDAP) directory but to work in Oracle Cloud application, we need to sync
these information’s with Oracle Cloud Application. Run User and Roles
Synchronization Process in Oracle Cloud or Retrieve Latest LDAP Changes
process helps to sync the Information’s about user and their roles with LDAP
and Oracle Cloud application.
20.How to Set the override email address in Oracle Fusion for All Email
notifications in Oracle cloud
Answers :
In the BPM tool , Click on the User Name (on the top right side) which have a
drop-down menu of 'Administration'
Step2:- In Administration , Scroll Down and go to 'Test Notifications Email

Address' option. click on the Edit icon.
Step3:- Enter the email address as below for test email notifications.
22.How Rapid Implementation works in Oracle cloud
As I said , In Rapid Implementation , Oracle cloud has given Excel templates
for different types of Oracle application business objects. So we need to
prepare the data as per our business Requirment in these Excel sheets.
Then An xml file can be generated once the user has filled out the required
information on the spreadsheet.
The user can manually upload the generated xml file to the server from Oracle
Scheduler. Then the upload process will create that business object in oracle
application based on the information on the spreadsheet.
Rapid Implementation helps to upload the Very Basic information about
business objects in oracle cloud application. If user wants to add more detail,
then the user may go through the original path to make changes or provide
more details to that business object in application.
24.How to enable Supplier Auditing Report in Oracle Cloud?

We can enable Supplier auditing on these below levels
1. Profile details such as supplier identifiers (Name, Alternate Name, D-U-N-S
Number, and so on)) 2.Supplier Addresses
3.Supplier Business Classifications
4.Supplier Products and Services
5.Supplier Tax Registrations, Tax Classifications, and Tax Reporting Codes
6.Supplier Sites
7.Supplier Site Assignments
8.Supplier Contacts
9.Supplier Payment Methods
10.Supplier Payment Attributes
At present we cannot enable supplier auditing for 'Supplier Bank Accounts'

and 'Supplier Contact User Accounts'
we need to have job role of Application Administrator to enable the auditing
setup.
Users can access the audit setup page from Navigator > Setup and
Maintenance.
Then search for the task 'Manage Audit Policies'. The setup page allows you
to select objects and its attributes that you wish to enable for audit tracking.
Use the following information to configure audit setup for the Suppliers
application.

Step2:- Click Configure Business Object Attributes. This will navigate to a

page where you can select the specific business objects and attributes within
each object that you require to enable for audit history tracking.
Step3:-
Step4:- For example , We need to enable auditing Supplier Header Level so

we need to do this below setup as below.
Under Audited attributes , Click on the '+' icon to select the attributes which we
want to keep track o the change History.
The audit setup page provides users with access to all applications enabled
for audit tracking. Exercise caution when making changes in the setup page.
The impact of changes in setup can impact users across several applications.
• If an object or attribute is disabled or removed from audit tracking, the

changes are prospective and not retrospective. Audit history before such
change will continue to be available for reporting.
• Before you configure the setup, it is recommended that you consider your
change history reporting requirements. It is important to determine whether or
not you need to enable only select objects (or select attributes within an
object) for audit tracking, or enable all available objects and attributes.
25. How to Setup Customer statements in oracle fusion

Step1 :- Set Receivables System Options for Statements
Step2 :- Define Remit-to Addresses
Step3:- Define Statement Cycles
Step4:- Define Customer Site Profiles
Navigate to the 'Mange Receivables System Options' and select the
applicable business unit.
Click the Billing and Revenue tab, if it is not already displayed.
We need to Enable the Print remit-to address option to print the remit-to
addresses on customer statements
Step5:- Navigate to the 'Manage Remit-to Address' page and define the Remit
to Address.
In the Receipt from Criteria section, click the Create icon to open the Create
Receipt from Criteria window. Use this window to assign the remit-to address
you just created to customer bill-to sites in specified locations
Step6:-
Navigate to the Manage Statement Cycles page.
In the Search Results section, click the Add .In the Name field, enter a name
for this statement cycle.
In the Interval field, select the interval that determines how often to generate
statements: weekly, monthly, quarterly
In the Cycle Dates section, click the Add icon.
In the Business Unit field, select the business unit that will use this statement
cycle.
Step4:- Now We need to go to customer Master and need to do the setup for
each customer for which we want to send customer Statements.
go to Customer Site and then click on the Profiles Tab
Step8: -
Need to enable statement in Customer Site Profile level to enable customer
Statements in Oracle Fusion.
27. How to see all the reports running history in Oracle Cloud
Step 1:- Login to Oracle Fusion and go to Menu Navigator as below and Click
on Reports and Analysis option.
Step2:-
Click on the Browse Catalog Option as highlighted below
Step3:- Click on the Home Tab as highlighted below
Step4:- In the left side of the page under Browse/Manage , You will see these
options report jobs and Report Job History.
click on Job History Link as highlighted below.

Step 7:- As below , this is the Report Job History window where we can find
out the details for all the BIP & OTBI reports running history in detail.
29. Document sequencing in Oracle cloud ?

Answer:
Document sequencing in Oracle cloud helps to put more control in the
Business operations. with the help of this Ordering we can identify the missing
transactions or deletion of some entries in the system. Usually companies
create Document sequencing for each financial year for audit requirements
and for tracking too. Document sequence setup in oracle apps r12 helps to
assign the unique sequence for each transaction based on the category and
then after that, system refer that sequence number for generating numbers for
that category transactions.
30.How to Suspend, Retry, Withdraw and Reassign the Workflow Notifications

in Oracle Cloud
In Oracle apps, we also have the Administrator role in Oracle cloud in which
we can Suspend, Retry, Withdraw and Reassign any Workflow Notifications in
cloud application. As we know that in Oracle apps, we have the Responsibility
of ‘Workflow Administrator’ in which we can find and track and then to
Suspend, Retry, Withdraw and Reassign any Workflow notification in the
same way we have the possibility in the Oracle Cloud application too. There
are some Slightly changes happed in the Oracle Cloud application like, In
Oracle application all the approval and Notifications derives with the Help of
Workflows but in Oracle Cloud, this is managed by the BPM. BPM is Business
process management tool which helps to create and design the approval rules
and all the notifications derives with the help of this BPM tool.
We need to go to the Home of the Oracle Cloud Notifications. Then In Oracle

Home, We need to go to the Top of the Home page. Here we will have the
Bell icon as highlighted below.
Click on the Bell Icon and Then Click on the More details.
Step2:- Click on the Bell Icon and Then Click on the More details.
Step3:-
Now you will see this below BPM worklist Tasks or Notifications.
Click on the Administrative Tasks Highlighted below.
In the Administrative tasks you can able to see all the Oracle Cloud
Notifications ever generated.
Step4:-
Now Put you Purchase Order or Expense report number as highlighted below
to see the Notification related to this.
Step5:-
Click on the Notifications Subject and this will open the Page of the
notification. Here you will have option in the ‘Action’ Button to Suspend, Retry,
Withdraw and Reassign the Workflow Notifications in Oracle Cloud
Step6:- Here you will have option in the ‘Action’ Button to Suspend, Retry,
Withdraw and Reassign the Workflow Notifications in Oracle Cloud
31.How to send Payment Separate Remittance advice in Oracle Cloud
Separate Remittance advice is a document which have all the Payment

Related Information. Usually this document sent to supplier. Using this
Remittance advice suppliers gets that, his payment has been released against
which invoice number. Remittance advice also stores the Invoices information
too.
So, with the Help of Separate Remittance advice we get Payment
Information’s and the Invoice Information too against which this payment
released. Oracle application helps to send the Payment Separate Remittance
advice when the payment processed through Payment process profile and its
completed. Then Oracle application send Payment Separate Remittance
advice to that suppliers which got paid in that Payment Batch.
Query Payment Process Profile being used as below. Now go to the reporting
tab as highlighted below.
Step3:-
Now under Send Separate Remittance Advice do this below Configurations.
Set SRA format and delivery options as shown in the example below
If you wish to kick off SRA process automatically upon completion of
payments, check 'Automatically submit when payments are confirmed' flag.
32. How to Purge Supplier Interface records in Oracle Fusion

Answer :
We do import Supplier from External system to the Oracle Application through
Supplier Interface in Oracle fusion. All the processed and rejected suppliers
records remains in the supplier interface tables. If you want to remove or
purge these Supplier Interface records in Oracle Cloud then we need to run
Oracle cloud Standard Schedules process 'Purge Supplier Interface records'.
Step2:- In this Standard Request , we can Purge these 8 Supplier Interface
tables as per our Requirement.
In the Records Parameter , we have the option to select the Rejected or
Processed records to purge.
Step3:- Here in this example , We are trying to Purge the 'Suppliers Header'
Interface Tables.
In Records , I have selected 'All' to Purge all the Rejected and Processed
records.
33.How to Correct the AP invoices Interface rejected records in Oracle cloud?
Answer :
Step1:- We need to go to the Payables Invoices.
Go to Payables ==>Invoices
click on the Task Pane
Step2: In the Task Pane , Select the option 'Correct Invoices'.
Step3;- 'Correct Invoices' Will download the ADFDI template. In this
Template , We can search all the Error out records. We can correct it and then
re-process it.
34. What is xmlp server in Oracle Fusion BIP reports ?
Answer :
XMLP server is provided by the Oracle Fusion for the BIP reports. This is
totally integrated with the Oracle Fusion Application. XMLP server is
recommended by Oracle cloud to customize the standard reports. xmlp server
has many other benefits too but in this post , I will talk more about the xmlp
server feature we do mostly uses in the Oracle Cloud application.
Two important uses of XMLP server in Oracle Cloud

1. For The Customization of the Oracle Cloud Standard BIP reports.
2.To make the reports available to be access by the Other application outside
the Oracle Application.
FRS
the reporting capabilities in Fusion Financials Cloud. Let us look at the different
reporting available:
1.General Ledger Standard reports
2. Account Monitor
3. Account Inspector
4. Financial Reporting Studio (FRS)
5. OTBI (Oracle Transactional Business Intelligent)
6. Smart View (Covered in Part 1 – Please refer ‘Reporting in Fusion Financials
Cloud Part 1)
General Ledger Standard Reports –
Oracle General Ledger provides many seeded/pre-defined reports, which help the
organizations to perform their day-to-day operations & reconciled the GL balances
with Sub ledger applications. The reports cover Journal Entry Details, Trial Balances,
Sub ledger the General Ledger Reconciliation Reports, Chart of Account Reports etc.
The most widely used report is the Account Analysis Reports in different views that
brings the detailed transactions in one format for the given parameters.
One can run these reports from Scheduled Processes work area. These reports can be
extracted in multiple printable or analysable formats like HTML, CSV, PDF, Excel
etc.
Account Monitor –
This tool gives the users separate place (GL Dashboard) to monitor the key account
balances and activities on it. By creating the Account Groups, the user can setup the
Account Monitor with default monitoring options. We can configure the comparisons
(by time etc.); provide the thresholds, set up the tolerance limits and many more
options to view the balances at General Ledger Dashboard. Business users can create
multiple groups for the different accounts based on requirements. This can be changed
easily at any point of time. Users can also click on the displayed balances and drill
down at the detailed balances level to see the Journals and further to the source
information (Sub ledger transactions). Here, users can see the real-time balances. The
graphical representation of the balances can also be setup & seen on this page. The
system applies the colors based on whether the changes are Good or Bad for the
organization.
Account Inspector –
Account Inspector is the multi-dimensional analysis tool which helps to create the ad
hoc pivot analysis, chart-based details and drill down from account to detailed
transactions. You need to set up the report dimensions from Report & Analysis page
from GL role.
Detailed Balances:
GL Journal:
Financial Reporting Studio (FRS) –

This is the Oracle Hyperion Financial Reporting Studio also called FRS. Financial
Reporting Center provides the facilities to build the financial reports on Oracle Fusion
General Ledger balances. This tool mainly used to build the reportable financials
statements like Income Statement, Balance Sheet, and Cash Flows. The reports can be
seen in multiple output formats as PDF, Excel or HTML. An authorized user can
open, publish or drill down through the report and understand the numbers and its
origins. These reports are build using the given objects like Grids, Text Boxes,
Account Hierarchies, Images/Charts and many other formatting & formulas.
To build the FR reports –
1. Install and configure Financials Reporting Studio
2. Configure the Workspace connection
OTBI (Oracle Transactional Business Intelligent) – Financials
The Oracle Transactional Business Intelligent is called OTBI, which give users to
create their own ad hoc analysis quickly using the Oracle views access. This is the
simple drag and drop reports/analysis based on the relevant subject areas (AP, AR
etc.) The user can select the required subject areas, columns, apply formatting like a
filter, charts, colors etc. and create the analysis/reports. There are few-seeded OTBI
reports comes with the financial package.

Implementation Checklist For Oracle E-Business Tax: Step Number Step Description

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Implementation Checklist For Oracle E-Business Tax: Step Number Step Description

Uploaded by

Copyright:

Available Formats

Implementation Checklist for Oracle E-

Step Number Step Description

1 Setting Up Tax Users

2 Setting Profile Option Values

3 Setting Up Lookup Codes

4 Setting Up TCA Geography Hierarchy

5 Setting Up Legal Entity

6 Setting Up Operating Units

7 Setting Up Accounts and Accounting Information

8 Setting Up TCA Classifications

9 Setting Up Oracle Inventory

Setting Up Tax Users

Setting Profile Option Values

The key for this table is:

 Update: You can update the profile option.

Profile Option Default User Access System Administration: Sit

eBTax: Allow Ad Hoc Tax Changes Yes No Access Update

eBTax: Allow Manual Tax Lines Yes No Access Update

eBTax: Allow Override of Customer Exemptions Yes No Access Update

eBTax: Allow Override of Tax Classification Code Yes No Access Update

eBTax: Inventory Item for Freight Freight Charge No Access Update

eBTax: Invoice Freight as Revenue No No Access Update

eBTax: Read/Write Access to GCO Data Yes No Access Update

eBTax Taxware: Service Indicator Non-Service View Only Update

eBTax Taxware: Use Nexpro No No Access Update

eBTax Vertex: Case Sensitive Yes View Only Update

eBTax: Allow Ad Hoc Tax Changes

eBTax: Allow Manual Tax Lines

The related tax setups are:

 Taxes: Allow Entry of Manual Tax Lines

eBTax: Allow Override of Tax Classification Code

eBTax: Allow Override of Tax Recovery Rate

eBTax: Inventory Item for Freight (Oracle Order

The values for this profile option are:

eBTax: Invoice Freight as Revenue (Oracle Order

eBTax: Read/Write Access to GCO Data

eBTax Taxware: Service Indicator

The values for this profile option are:

 Service - Service transaction.

The values for this profile option are:

eBTax Taxware: Use Nexpro

The Taxware API parameter that accepts this value is TaxLink.UseNexproInd.

eBTax Vertex: Case Sensitive

Setting Up Lookup Codes

E-Business Tax provides these seeded tax registration types:

Registered The company is registered for the applicable tax.

The ZX_TAX_TYPE_CATEGORY lookup type contained these seeded tax types:

VAT Value added or cascading taxes.

Excise Taxes on the production and manufacture of goods.

Environmental Taxes charged as a result of environmental regulations.

Setting Up TCA Geography Hierarchy

You use the TCA geography hierarchy in these cases:

Use TCA administration to maintain these aspects of the geography hierarchy:

Setting Up Real-Time Address Validation, Oracle Trading Community Architecture Administration Guide

Administrating Geography Hierarchy, Oracle Trading Community Architecture Administration Guide

Geography Name Referencing Process, Oracle Trading Community Architecture Administration Guide

Setting Up Legal Entity

Setting Up Legal Entities

Setting Up First Party Legal Establishments

Setting Up Legal Authorities

Applying End Dates to Legal Entities

Setting Up Operating Units

For tax-related transactions: