Professional Documents
Culture Documents
HCM Global HR
Define Legal Jurisdictions and
Legal Authorities for HCM
Instructor Guide
August 8, 2013
Copyright © 2013, Oracle and/or its affiliates. All rights reserved.
Disclaimer
Trademark Notice
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other
names may be trademarks of their respective owners.
CONTENTS
Lesson 1: Define Legal Jurisdictions and Legal Authorities for HCM
1
Lesson Objectives ................................................................................... 1
Legal Jurisdictions Overview...................................................................... 2
Legal Authorities Overview........................................................................ 3
Legislative Data Groups Overview .............................................................. 4
Legislative Data Groups............................................................................ 5
Instructor Note: Legislative Data Groups ..................................................... 7
Lesson Highlights .................................................................................... 8
Lesson Highlight Details ......................................................................... 9
i
Lesson 1: Define Legal Jurisdictions and Legal Authorities for HCM
Identifying Jurisdiction
Income Tax Jurisdiction
Transaction Tax Jurisdiction
Identifying Jurisdiction
An identifying jurisdiction is the first jurisdiction you must register with to be allowed to
do business in a country. For each legal entity, select an identifying jurisdiction. If there
is more than one jurisdiction that a legal entity needs to register with to commence
business, select one as the identifying jurisdiction. Typically the identifying jurisdiction is
the one you use to uniquely identify your legal entity.
Income tax jurisdictions and transaction tax jurisdictions do not represent the same
jurisdiction. Although in some countries, the two jurisdictions are defined at the same
geopolitical level, such as a country, and share the same legal authority, they are two
distinct jurisdictions.
Income tax jurisdictions impose taxes on your financial income generated by all your
entities within their jurisdiction. Create income tax jurisdictions to properly report and
remit income taxes to the legal authority.
Tax jurisdictions and their respective rates are provided with transactions from the
suppliers, and require periodic maintenance. Create transaction tax jurisdictions through
Oracle Fusion Tax in a separate business flow, because of the specific needs and
complexities of various taxes. Use transaction tax jurisdiction for legal reporting of sales
tax and value added tax.
The Internal Revenue Service is responsible for collecting taxes and the
interpretation and enforcement of the Internal Revenue Code of the United
States.
Legal authority information is printed on your tax reports to meet some countries’
requirements, such as India and Brazil.
Legal authorities are defined in the Oracle Fusion Legal Entity Configurator.
Tax authorities are a subset of legal authorities and are defined using the same
setup flow.
Legal authorities are not mandatory in Oracle Fusion Human Capital
Management (HCM), but are recommended and are generally referenced on
statutory reports.
Note: For payroll purposes, it is recommended to have one legislative data group for
each country, since you define elements, formulas, and payroll definitions for a
legislative data group. If you have multiple legislative data groups for a country, you will
need to define the information again for each legislative data group.
Each legislative data group marks a legislation in which payroll is processed, and
is associated with a legislative code, currency and its own costing allocation key
flexfield structure.
Note: You assign the costing allocation key flexfield when you create a legislative data
group, though you can use the same costing key flexfield across different legislative
data groups. It is recommended that you assign a costing key flexfield when you create
a legislative data group, even if you are not using Financials, since you cannot edit the
flexfield value once the legislative data group is created.
A legislative data group is a boundary that can share the same setup and still
comply with the local laws.
A legislative data group can span many jurisdictions as long as they are within
one country, and contain many legal entities that act as payroll statutory units.
Each payroll statutory unit can belong to only one legislative data group.
A legislative data group is typically required only if you are implementing Payroll and a
separate LDG is required for each localization that Oracle provides. If you are not
implementing Payroll, you may choose to limit the number of legislative data groups.
For example, If you are implementing Talent and Compensation only, you need not
create a legislative data group for each country.
All the above scenarios are correct. The difference is the amount of work required to
maintain the created legislative data groups.
You can add a legislative data group at any point in time. So, if in the future you decide
to implement Payroll, you can still add the required legislative data groups.
Lesson Highlights
You should have learned how to:
Define legal jurisdictions, legal authorities, and legislative data groups for
HCM
A legal authority is a government or legal body that is charged with powers to make
laws, levy and collect fees and taxes, and remit financial appropriations for a given
jurisdiction. There are predefined legal authorities in the application, you can create
your own in addition.