An Introduction To Oracle R12 E-Business Tax
An Introduction To Oracle R12 E-Business Tax
An Introduction To Oracle R12 E-Business Tax
This is one of a series of White Papers written by David Sparks, each one
focussing on a specific aspect of Oracle.
If you have found the content of this White Paper interesting and useful, and wish
to explore the subject matter further, or wish to discuss any other aspect of the
Oracle R12 Financial modules, then please contact David Sparks on
daveasparks@yahoo.co.uk
Getting started....................................................................................................6
External Dependencies........................................................................................8
David Sparks is an independent Oracle Applications Functional Consultant who has been
working with the Oracle Financial Modules over 20 years. He has worked throughout Europe
on a large number of pan-European implementations for companies such as Akzo Nobel,
AT&T, Eaton Corporation, Nike, Oracle, SAS, Toyota, Unisys.
PURPOSE
The purpose of this document is to try and do just that, to break down E-business Tax, and to
present the simplest of cases, thus giving the basis to build more complicated scenarios.
It does so by navigating through the E-Business Tax menus and configuration screens in the
appropriate order giving examples of a working configuration.
It does not attempt to explain every configuration option or term, as to do so would end up
recreating the existing Oracle manuals.
My starting point in this document assumes knowledge of Oracle applications and some
knowledge of Oracle Release 12.
There are many aspects of Release 12 that are new or different from previous releases. I will
not try and explain these because to do so would deviate from the purpose of this document.
My starting point assumes that a basic Organisation structure is already configured which has
a Legal Entity, a Ledger and an Operating Unit defined.
Oracle define two key aspects to the configuration of E-Business tax. The Tax Content
Services and the Tax Determination Services.
The Tax Content Services store and maintain the master and reference data components that
are needed to support E-Business Tax. This includes:
Tax Authorities and Tax Jurisdictions where taxes apply, First Party and Third party
Entities involved in transactions which are taxable, Transactions that are taxable,
Taxes that may be applicable
The Tax Determination Services are the rules and the management of the rules that are used to
determine which of the Tax Content Service components apply, and when. The rules are
organised into a hierarchy of rule processes which determine:
Place of Supply, Tax Applicability, Tax Registration, Tax Status, Tax Rate, Taxable
Basis, Tax Recovery Rates
In this document I’ll first look at the Tax Content, and then at the Tax determination. Towards
the end of this document the approach becomes iterative as further content is required to
allow specific determinations to be made.
Getting started
When I login into the E-Business Suite and select a Tax Manager Responsibility and select
Home.
External Dependencies
On the task list if the External Dependencies section is expanded a number of tasks are listed.
I have already identified and setup First Party Legal Entities and Establishments as part of the
setup of my Organisation structure and Ledgers. These are the legally registered entities of
my organisation in each country that I do business, and the sub-divisions of those
organisations that need to be registered for tax. An example of one of them is as below.
A Tax Authority is a government entity that regulates tax law, administers, or audits one or
more taxes. A legal authority record needs to be setup for each tax authority that administers
taxes in the tax regimes where you do business.
If I click on the Go to Task icon it takes me to the Legal Authorities page. Here I can create
Tax Authorities or search for existing Authorities.
The example shown below is for UK, the dearly beloved ‘HM Revenue and Customs’.
The two tasks above are the only tasks in the External Dependencies section that I shall cover
at the moment. The other tasks in this section will be covered later in this document, or in
future documents.
Tax Configuration
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.
Tax Profiles will need to be setup for the First Party Legal Entities, Legal Establishments and
Operating Units, for the Customers and Suppliers and their locations, and for the Tax
Authorities that administer tax rules and regulations.
I can then create the Tax Profile for this Authority. There is not really much to this. It’s just a
case of checking the Collecting Authority and Reporting Authority boxes and Applying.
Oracle suggest ‘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.’
And describe a Tax Regime as associating ‘a common set of default information, regulations,
fiscal classifications, and registrations to one or more taxes with the same tax requirement.’
and providing the functions:
The Tax regime must be associated with all of the First Party Legal Entities and Operating
Units that are subject to the tax regulations of the regime. This association can be done either
from the Tax Regime definition or the Party Tax profile definition. However, at this stage of
the setup the association can’t be done because the Tax Profiles for these parties have not
been created.
As said previously, 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.
Defining the Tax Profile for First Party Legal Entities is pretty straightforward. I find the
Legal Entity SPLE1 and click on Create Tax Profile
At this stage the Legal Entity can be associated with the Tax Regime defined previously.
A component of this association is the Configuration for Taxes and Rules. The Common
Configuration option provides the maximum sharing of tax setup among the parties in the
organisation with the minimum amount of maintenance. All parties that are subject to the tax
regulations of a given tax regime should use the Common Configuration option unless it is
necessary to create party-specific overrides.
Create Tax
This is where the details of the Taxes are defined for the Tax Regime. While it is possible to
define multiple Taxes for each Tax Regime, the context in which it can be viewed is that there
is one tax, VAT. The different rates of VAT are defined later as Tax Statuses (Standard, Zero
Rated, Exempt…) with associated Tax Rates (the standard rate may vary, for example, from
17.5% to 15% for a period of time, and then back to 17.5% again).
Each Tax defined here may require the definition of a corresponding Offset Tax. An Offset
Tax calculates and records third party Payables tax liabilities for reverse charges. An offset
tax record is a matching, duplicate record with negative amounts that reduces or completely
offsets the tax liability recorded in the tax transaction.
This is expressly used in Payables for recording Intra EU transactions.
The below screen shows the Taxes that have been defined for the Tax Regime GB VAT
The main details of the Tax ‘GB VAT’ are shown below.
Default tax accounts can be setup for each Tax. The tax accounts define here serve as default
accounting information for taxes, tax rates, tax jurisdictions, and tax recovery rates.
I do so by clicking on the Tax Accounts button and then creating the accounts for a particular
Ledger / Operating Unit combination. These can only be defined for those primary ledgers in
the my security profile that have at least one operating unit assignment.
Tax statuses need to be created for each tax. A Tax Status is the taxable nature of a product in
the context of a transaction and a specific tax on the transaction. They reflect the different
states of the tax, such as Standard, Reduced, Exempt or Zero
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.
A 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. A tax recovery rate code
identifies the percentage of recovery designated by the tax authority for a specific transaction.
If the Allow Tax Recovery option is set for the Tax Regime and Tax, which for VAT it should
be, then at least one recovery rate for the tax must be set up. What we see below is a standard
recovery rate of 100% for GB VAT, a 0% recovery of GB VAT, and a 100% Recovery of GB
VAT OFFSET.
Tax Rates
A Tax rate record should be setup for each applicable tax rate that a tax status identifies. The
Screen below shows the Tax Rates that have been defined for the UK.
The E-Business Tax Tax Determination process is organized into Rule Types. Each Rule Type
identifies a particular step in the determination and calculation of taxes on transactions and
each can have a Default Value, and any number of Rules. However, performance is in inverse
proportion to the number of rules!
Looking at the page below you can see the configuration of the rule types for the tax GB
VAT.
Default Values
Default values can be set for each rule type. E-Business Tax uses the default value if no rule
belonging to the rule type provides a value that applies to the transaction. For certain tax
regimes, you may be able to use default values exclusively, without the need to set up tax
rules. As a general rule of thumb, if you find in setting up tax rules that the tax condition
results and rule results always equal the default values, then you do not need a tax rule. You
only need to define a tax rule for a result that is different from the default value.
The permissible default values for the rule types are as follows
Determine Place of Supply: Bill From, Bill To, Point of Acceptance (Receivables transactions
only), Point of Origin (Receivables transactions only), Point of Payment, Ship From, Ship To,
Use Bill To as Ship To, if Ship To is not found
Determine Tax Applicability: Applicable, Not Applicable
Determine Tax Registration: Bill From Party, Bill To Party, Ship From Party, Ship To Party,
Use Bill To, if Ship To is not available
Determine Tax Status – You specify the default value when you set up the tax status. This
default can be overridden.
Determine Tax Rate – You specify the default value when you set up the tax rate. This default
can be overridden.
Determine Taxable Basis – The seeded formula STANDARD_TB (Taxable Basis = Line
Amount).
Calculate Tax Amounts – The seeded formula STANDARD_TC (Tax Amount = (Taxable
Basis) * (Tax Rate)).
In my example, the default value for Place of Supply is Ship From. If the place of supply of a
sale or purchase within the UK is the UK itself then Tax Jurisdiction and Candidate Tax GB
VAT applies.
However, in the case of services from suppliers in other countries, VAT may have to be
accounted through a mechanism known as the 'reverse charge' or 'tax shift'. A reverse charge
applies if the First party belongs in the UK and the supplier belongs in another EU country. If
the supply is a supply of services from the EU then the default of Ship From will not allow
the Tax Jurisdiction and Candidate Tax GB VAT to apply. What is required is a rule that says
that if the Bill From country is in the EU (and not the UK) and the Bill To Country is the UK,
then use Bill To to derive the place of supply. This allows the Tax Jurisdiction and Candidate
tax GB VAT to apply. At the same time the supplier configuration needs to allow Offset tax to
apply.
The Rule can be setup as follows. First create a Tax Determining Factor Set that defines the
factors that are considered together in the course of evaluating the rule, and a Tax Condition
Set that defines the resulting value that must exist for each factor, in order for the result of the
tax rule to be true.
To define a Tax Determining Factor Set click on the Advanced Setup Options on the Oracle
E-Business Tax main page and select Tax Determining Factor Sets and Create.
An example of this Tax Determining Factor Set is below.
And the Tax Condition Set can be defined from the same Advanced Setup Options Tab.
Once these two sets have been defined then they can be used in a Place of Supply rule. From
the Tax Rules Page I find the configuration for GB VAT and click on Expert Rule Entry for
the Determine Place of Supply Rule Type.
On the next page the previously defined Condition Set is chosen, and the result to return, if
the conditions are satisfied.
On the next a rule order is entered to determine in which order to process the rule (if there are
multiple rules for the type), and the rule is enabled.
First party legal establishments identify each office, service center, warehouse and any other
location within the organization that has a tax requirement. The system automatically creates
a legal entity establishment when a legal entity is created. For each legal establishment there
can be one or more tax registrations, depending upon the tax requirements of the applicable
tax authority.
These are setup from the Party Tax Profile page.
Third party tax profiles need to be setup for customers and customer sites and suppliers and
supplier sites.
This tax information can be part of the relevant third party maintenance flow (for example,
customer and supplier maintenance).
Below I’ll show examples for a Supplier, a foreign Supplier setup to use Offset Taxes, and a
Customer.
The Supplier
The Customer
A tax can be enabled by ticking the Make Tax Available for Transactions box.
The tax amount is 15 because the Invoice date falls in the period when the 15% standard rate
applied. If I look at the Tax Details I see the following
Success!!
I’m now going to go back some steps and look at some other examples of how rules can be
made to work, this time based on Products for use in Accounts Receivable.
Fiscal classifications provide tax determination values for situations where the parties,
products, or transactions are factors in tax determination. A fiscal classification type identifies
a category of fiscal classification that has a potential tax implication. Fiscal classification
types can be assigned to tax regimes and taxation countries. Fiscal classification codes are set
up under a fiscal classification type to provide additional granularity to a particular fiscal
classification category. When creating tax rules fiscal classification types are used as
determining factors and fiscal classification codes as condition set values.
Their use is optional, and depends upon the overall scheme for managing tax determination
and tax calculation requirements. They are setup under three general categories:
Party fiscal classifications - Classify the first parties, the various parts of the organisation,
and the third parties, the customers and suppliers and their locations, for use in tax
determination.
Product fiscal classifications - Classify the products and services for use in defining rules for
tax determination. These can be split into three areas, Inventory based, Non-Inventory based,
and Intended Use classifications
Transaction fiscal classifications - Classify the nature of a transaction itself, and the details
that must accompany a transaction, according to its tax requirements.
I am going to run through examples of Inventory and Non-Inventory based Product Fiscal
Classifications.
From the Task List I can go to the Product Fiscal Classification page.
When I review this data I can see the Category codes that have been defined for the Oracle
Inventory Category Set ‘GB VAT PRODUCT CLASSIFICATION’.
A Determining Factor Set has been setup that uses the Fiscal Classification Type
And a Tax Condition Set setup that sets the required condition to being equal to ‘GBG0103 -
Reduced Rate Goods’
That returns the Tax Status ‘GB VAT REDUCED’ when the Tax Condition is satisfied.
From the Product Fiscal Classification Types page I can display the Product Classification
Source of Oracle E-Business Tax and review the Product Category fiscal classification type
code.
I have a Determining Factor Set that uses the Product Category as the determining factor.
And a Determine Tax Status Rule ‘STATUS2’ that has been created for Event Class ‘Sales
Transaction’ that returns the Tax Status ‘GB VAT ZERO’ when the condition is satisfied.
SUMMARY
It is always good to quit while you are ahead. Which is what I shall do here, hopefully having
in some way achieved what I set out to do.
What I set out to do was to break down E-business Tax, and to present the simplest of cases,
thus demonstrating how it works, and how it can be made to work in more complicated
scenarios.