Lacls Fiscal Solution Path v1

Oracle Financials Cloud
Latin America Cloud Local Solution Brazil

Financial and Fiscal Solution Path
A Localization Approach
Doc Id 2291252.1
Version 11.1.1113.47
23-Oct-2023
DISCLAIMER:
This guide may contain screen shots and output reports to facilitate the user comprehension about the topic.
The content represents a fictitious sample. Any similarity to actual persons, living or dead, or company
names, active or inactive, is purely coincidental and not intended in any manner.
TABLE OF CONTENTS
TABLE OF CONTENTS ..............................................................................................................................................2
REVISION HISTORY ............................................................................................................................................... 10
LATIN AMERICA CLOUD LOCAL SOLUTION FOR BRAZIL ........................................................................................ 15
ERP CLOUD ROLES ................................................................................................................................................ 16
ISV INTEGRATIONS ...................................................................................................................................................... 16

Job Roles ............................................................................................................................................................. 16
Other Roles ......................................................................................................................................................... 16
Duty Roles .......................................................................................................................................................... 17
Privilegios ........................................................................................................................................................... 17
IMPLEMENTER ROLES ................................................................................................................................................... 18
FUNCTIONAL ROLES ..................................................................................................................................................... 19
ASSIGN ROLES ............................................................................................................................................................ 23
USER AS EMPLOYEE ..................................................................................................................................................... 24
GEOGRAPHY ........................................................................................................................................................ 25
DEFINE ADDRESS FORMAT ............................................................................................................................................ 25

DEFINE LOOKUP CODES FOR GEOGRAPHY......................................................................................................................... 27
Define Alternative Fields for IBGE Codes ............................................................................................................ 27
Define Alternative Fields for SISCOMEX Codes ................................................................................................... 28
Check IBGE Codes ............................................................................................................................................... 29
Check SISCOMEX Codes ...................................................................................................................................... 29
DEFINE GEOGRAPHY .................................................................................................................................................... 30
Define Geography Structure ............................................................................................................................... 30
Define Geography Validation ............................................................................................................................. 31
Define Geography hierarchy .............................................................................................................................. 32
GENERAL LEDGER ................................................................................................................................................. 33
RAPID IMPLEMENTATION .............................................................................................................................................. 34
ENTERPRISE STRUCTURE ...................................................................................................................................... 35
LEGAL ENTITIES ........................................................................................................................................................... 35

LEGAL REPORTING UNITS .............................................................................................................................................. 36
Define First-Party Taxpayer ID ........................................................................................................................... 36
Manage Associated Balancing Segments........................................................................................................... 37
Assign BSV in the Legal Reporting Unit ............................................................................................................................ 37
MANAGE ASSOCIATED BUSINESS ENTITIES........................................................................................................................ 38
NFSe Integration ................................................................................................................................................ 38
DEFINE TAX REGISTRATIONS .......................................................................................................................................... 39
Self-Assessed Taxes ............................................................................................................................................ 39
NFSe Integration ................................................................................................................................................ 39
CNO NUMBER ........................................................................................................................................................... 40
2
Define CNO Number ........................................................................................................................................................ 40
COMPANY CLASSIFICATION CODE ................................................................................................................................... 42
Define Classification Code .................................................................................................................................. 43
Manage Party Fiscal Classifications ................................................................................................................... 44
Associate the code in the LRU ............................................................................................................................ 44
DEFINE PARTIES FOR BRAZIL ................................................................................................................................ 45
Customer Information ........................................................................................................................................ 45

Freight Carrier .................................................................................................................................................... 45
Supplier Information .......................................................................................................................................... 45
International Addresses ..................................................................................................................................... 45
RECEIVABLES........................................................................................................................................................ 46
INTEREST TRANSACTION................................................................................................................................................ 46
Interest Receipt Method .................................................................................................................................................. 46
Interest Batch Source ....................................................................................................................................................... 47
Interest Transaction Type ................................................................................................................................................ 47
LOCALIZATION SYSTEM OPTIONS ......................................................................................................................... 49
ENABLE REGIONAL LOCALIZATION ................................................................................................................................... 49

LOCALIZATION SYSTEM OPTION ...................................................................................................................................... 51
INBOUND FISCAL DOCUMENTS ............................................................................................................................ 52
FISCAL DOCUMENT CAPTURE ......................................................................................................................................... 52

Main Business Flows .......................................................................................................................................... 52
FDC Main Features ............................................................................................................................................. 53
Fiscal Flows/CFOP .............................................................................................................................................. 54
Tolerances .......................................................................................................................................................... 55
Services Model 55 from Brasília ......................................................................................................................... 55
NFSE INTEGRATION ..................................................................................................................................................... 56
OUTBOUND FISCAL DOCUMENTS ........................................................................................................................ 57
FISCAL DOCUMENT GENERATION CONTROLS .................................................................................................................... 58

NFSE SUBSTITUTE ....................................................................................................................................................... 60
MACRO STEP 1: Create first NFSe (RPS-1) ........................................................................................................................ 60
mACRO STEP 2: Create secound (NFS-2) NFSe as A Substitute of RPS-1.......................................................................... 60
MACRO STEP 3: Request cancel first NFSe (RPS-1) .......................................................................................................... 60
FISCAL DOCUMENT MODEL 21 ...................................................................................................................................... 62
Setup .................................................................................................................................................................. 63
Enable Sequence Number ................................................................................................................................................ 63
DEfine Transaction Type .................................................................................................................................................. 63
Define Source ................................................................................................................................................................... 64
Define LACLS Note ........................................................................................................................................................... 65
Define LACLS Attachment ................................................................................................................................................ 66
Define Additional Messages in the Model21 ................................................................................................................... 67
Define Sequence Number ................................................................................................................................................ 69
Disable Fiscal Document Generator ................................................................................................................................. 69
3
How to Update a Note ....................................................................................................................................... 70
How to Update an Attachment .......................................................................................................................... 72
Create Model 21 (Invoice) .................................................................................................................................. 75
Create Model 21 (Credit Memo)......................................................................................................................... 76
Mapping about Model 21’s PDF Generate ......................................................................................................... 77
CTE-OS MODEL-67 .................................................................................................................................................... 85
Define Transaction Type .................................................................................................................................................. 85
Define LACLS Attachment ................................................................................................................................................ 86
How to Update an Attachment .......................................................................................................................... 87
TAX ...................................................................................................................................................................... 89
Complex Tax Rules ........................................................................................................................................................... 90
WITHHOLDING CALENDAR............................................................................................................................................. 91
Type calendars ................................................................................................................................................................. 91
TAX REGIME ............................................................................................................................................................... 93
Transaction Tax Regime ................................................................................................................................................... 93
Withholding Tax Regime .................................................................................................................................................. 96
Define Controls and Defaults ........................................................................................................................................... 98
Configuration Options and Service Subscriptions ............................................................................................................ 98
BRAZILIAN TAX TYPE .................................................................................................................................................... 99
Define Lookup Codes ....................................................................................................................................................... 99
TAX ........................................................................................................................................................................ 103
TAX RATE................................................................................................................................................................. 104
IRPF Withholding Tax progressive table association ...................................................................................................... 104
PARTY FISCAL CLASSIFICATION ..................................................................................................................................... 105
Define Organization Type Values ................................................................................................................................... 105
PRODUCT-BASED FISCAL CLASSIFICATIONS ..................................................................................................................... 106
Define Product Fiscal Classification Type ....................................................................................................................... 106
Define intended use ....................................................................................................................................................... 107
Define Withholding tax Deducitons ............................................................................................................................... 111
CONFIGURATION OWNER TAX OPTIONS ......................................................................................................................... 112
Define Configuration Owner Tax Options for Transactions Tax ..................................................................................... 112
Define Configuration Owner Tax Options for Withholding Tax ..................................................................................... 113
TAX RULES ............................................................................................................................................................... 114
ICMS ............................................................................................................................................................................... 114
PIS Tax and COFINS Tax .................................................................................................................................................. 117
IPI Tax............................................................................................................................................................................. 117
WITHHOLDING TAXES AND MULTIPLE TAXABLE BASIS ....................................................................................................... 118
Create Formula ................................................................................................................................................. 119
Create Withholding Tax Code ........................................................................................................................... 119
Create Determine Factor .................................................................................................................................. 120
Create Conditions Values ................................................................................................................................. 121
Create Tax Rules ............................................................................................................................................... 121
Purchase Document Styles ............................................................................................................................... 122
Scenario Procedure Simulation ........................................................................................................................ 122
CALCULATE WITHHOLDING TAX WITH RETAINAGE TERMS.................................................................................................. 123
Create Formula ................................................................................................................................................. 125
4
Create Withholding Tax Code ........................................................................................................................... 125
Create Document Fiscal Classification .............................................................................................................. 125
Determining Factor .......................................................................................................................................... 126
Create Conditions Values ................................................................................................................................. 127
BRAZILIAN FISCAL CODES ................................................................................................................................... 128
CST ASSOCIATION ..................................................................................................................................................... 128

MANAGE TAX RERPORTING TYPES ................................................................................................................................ 128
DEFINE CBENEF ....................................................................................................................................................... 129
DEFINE MVA RATE ................................................................................................................................................... 130
DEFINE REDUCTION BASIS RATE ................................................................................................................................... 132
DEFINE ORIGINAL RATE .............................................................................................................................................. 134
FCP DEFERRED ......................................................................................................................................................... 136
DEFINE ICMS-ST FISCAL CODES .................................................................................................................................. 138
DEFINE ICMS DESONERADO ....................................................................................................................................... 140
DEFINE LEGAL MESSAGES ........................................................................................................................................... 143
DEFINE TAX TYPE FOR WITHHOLDING AS TRANSACTION .................................................................................................... 145
DEFINE TAX TYPE FOR CFPS ........................................................................................................................................ 147
DARF AND GPS ASSOCIATION..................................................................................................................................... 148
Create Fiscal Code .......................................................................................................................................................... 148
Associate Fiscal Code ..................................................................................................................................................... 149
REINF TABLE 1 (NATUREZA DE RENDIMENTOS) ASSOCIATION ........................................................................................... 149
Create Fiscal Code .......................................................................................................................................................... 149
Associate Fiscal Code ..................................................................................................................................................... 150
PAYABLES .......................................................................................................................................................... 151
DEFINE PAYMENT TERMS ............................................................................................................................................ 151
PROCUREMENT .................................................................................................................................................. 152
DEFINE TAX AUTHORITY.............................................................................................................................................. 152

Classification .................................................................................................................................................................. 152
Sites................................................................................................................................................................................ 154
Control ........................................................................................................................................................................... 155
PROCUREMENT MANAGEMENT ......................................................................................................................... 156

MAPPING SUPPLIER ITEM............................................................................................................................................ 156
SELF-ASSESSED TAX............................................................................................................................................ 157
PROCUREMENT TRANSACTION ACCOUNT RULES .............................................................................................................. 157

LOOKUPS ................................................................................................................................................................. 158
TAX DEFINITIONS....................................................................................................................................................... 158
PIS AND COFINS DEFINITION ...................................................................................................................................... 159
Tax Accounts .................................................................................................................................................................. 164
PIS AND COFINS COST DEFINITION ............................................................................................................................ 165
Tax Accounts .................................................................................................................................................................. 169
PIS AND COFINS RECUP DEFINITION .......................................................................................................................... 170
5
Tax Accounts .................................................................................................................................................................. 174
DIFAL DEFINITION .................................................................................................................................................... 175
Tax Accounts .................................................................................................................................................................. 179
IPI REP DEFINITION................................................................................................................................................... 180
Tax Accounts .................................................................................................................................................................. 184
TAX REGISTRATION .................................................................................................................................................... 185
SPECIAL TAXES ................................................................................................................................................... 187
ICMS DEFERRED (DIFERIDO) ....................................................................................................................................... 187

ICMS Normal .................................................................................................................................................... 188
Tax Accounts .................................................................................................................................................................. 192
Tax JURISDICTION .......................................................................................................................................................... 192
ICMS Report...................................................................................................................................................... 193
Tax Accounts .................................................................................................................................................................. 197
ICMS Deferred .................................................................................................................................................. 198
Tax Accounts .................................................................................................................................................................. 202
Define Calculation Formula using ICMS-Normal and ICMS-Deferred taxes ..................................................... 203
DEFINE ICMS PARTILHA ............................................................................................................................................. 204
Tax Accounts .................................................................................................................................................................. 208
ICMS RE 574.706 ................................................................................................................................................... 208
ICMS Tax as Report .......................................................................................................................................... 208
Formula ............................................................................................................................................................ 209
Party Fiscal Classification ................................................................................................................................. 209
Tax Rules for Inbound ....................................................................................................................................... 209
Tax Rule for Outbond ....................................................................................................................................... 209
IRPF WITH SIMPLIFIED DISCOUNT ............................................................................................................................ 210
FUTURE TAX RECOVERY FOR FIXED ASSET ......................................................................................................... 214
DEFINE ICMS TAX RECOVERY IN FUTURE ....................................................................................................................... 214

Tax Accounts .................................................................................................................................................................. 219
Tax Jurisdiction .............................................................................................................................................................. 219
DEFINE PIS/COFINS TAX RECOVERY IN FUTURE ............................................................................................................. 219
Tax Accounts .................................................................................................................................................................. 224
RETURN TO VENDOR (RTV) ................................................................................................................................ 225
CONFIGURE ICMS CONTRIBUTOR AND IPI CONTRIBUTOR IN LRU SETUP.............................................................................. 226

ICMS Contributor ........................................................................................................................................................... 226
IPI Contributor ............................................................................................................................................................... 226
CONFIGURE MAPPING SET .......................................................................................................................................... 227
IMPORTATION AND EXPORTATION (GOODS/SERVICES) .................................................................................... 229
IMPORTATION ........................................................................................................................................................... 229

How to Import Goods ....................................................................................................................................... 230
How to Import Services .................................................................................................................................... 232
6
Import Setup..................................................................................................................................................... 233
Source to Oracle Payables Cloud (Conditional) ................................................................................................ 234
Bank Account (Required) .................................................................................................................................. 235
Payment Process Profile (Conditional) ............................................................................................................. 236
Foreign Supplier Address(Required) ................................................................................................................. 238
Country .......................................................................................................................................................................... 238
ZIP Code (CEP) ................................................................................................................................................................ 238
State and City ................................................................................................................................................................. 238
Tax Registration ............................................................................................................................................................. 238
Project (Conditional)......................................................................................................................................... 239
Cost Elements (Required) ................................................................................................................................. 239
Costing Lookups (Required) .............................................................................................................................. 240
Payment Terms (Required) ............................................................................................................................... 240
Incoterms (Required) ........................................................................................................................................ 240
Suppliers Tax Authority (Required) ................................................................................................................... 241
Special Instructions for Accounting .................................................................................................................. 246
EXPORTATION FLOW .................................................................................................................................................. 247
How to Export Goods ....................................................................................................................................... 247
How to Export Services ..................................................................................................................................... 249
Export Setup ..................................................................................................................................................... 250
Transaction Source (Required) ......................................................................................................................... 250
Transaction Type (Required) ............................................................................................................................ 251
Document Fiscal Classification (Required) ....................................................................................................... 252
Manage a no valid Document Numbering (Required)...................................................................................... 253
Manage no Valid Fiscal Document Generation Controls for Brazil (Required) ................................................. 255
Profile JL_ENABLE_FEATURE (Required)........................................................................................................... 255
Order Type (Required) ...................................................................................................................................... 255
Bank Account (Required) .................................................................................................................................. 256
Foreign Customer Address(required)................................................................................................................ 256
Country .......................................................................................................................................................................... 256
ZIP Code (CEP) ................................................................................................................................................................ 256
State and City ................................................................................................................................................................. 256
Tax Registration ............................................................................................................................................................. 257
SPECIAL INTRUCTIONS TAXES FOR IMPORT AND EXPORT FLOW ........................................................................................... 258
Taxes for Import Flow....................................................................................................................................... 259
PIS and COFINS Taxes for Import Flow........................................................................................................................... 259
Taxes for Import Flow .................................................................................................................................................... 259
Tax Rule for Import Commercial Invoice........................................................................................................................ 262
Tax Applicability Rule ..................................................................................................................................................... 262
Taxes for Export Flow ....................................................................................................................................... 264
Sales Order without Taxes ................................................................................................................................ 264
Taxes for Export Flow ....................................................................................................................................... 264
Tax Rules for Sales Order Without Tax........................................................................................................................... 266
Tax Rule for Export BRL Fiscal Document ...................................................................................................................... 267
Tax Applicability Rule ..................................................................................................................................................... 267
Tax Rate Rule ................................................................................................................................................................. 268
7
DOING TRANSACTION ........................................................................................................................................ 269
FISCAL DOCUMENT CAPTURE ENTRANCE ........................................................................................................................ 269

Manually Entrance ......................................................................................................................................................... 269
Electronic Entrance ........................................................................................................................................................ 273
Manage Interface Exceptions ........................................................................................................................................ 274
MAIN PROCESS JOB ................................................................................................................................................... 275
SCENARIOS ........................................................................................................................................................ 276
RESALES WITH IPI NOT ICMS ST ................................................................................................................................. 276

CONSUMPTION WITH IPI ............................................................................................................................................ 280
FREIGHT ACQUISITION (CTE) ....................................................................................................................................... 281
FIXED ASSET NOT IPI .................................................................................................................................................. 284
CONSIGNED .............................................................................................................................................................. 285
FREQUENTLY ASKED QUESTIONS (FAQ) ............................................................................................................. 288
HOW TO VIEW AN XML FILE STRUCTERED? ................................................................................................................... 288

WHAT ARE A DIFERENCE BETWEEN SPECIAL INCLUSIVE AND STANDARD INCLUSIVE TAX? ......................................................... 288
SHOULD “TIME ZONE” NEEDS TO BE DEFINED IN THE LEGAL ADDRESS? ............................................................................... 288
HOW TO HAVE A CORRECT ACCOUNTING FOR AN EXPENSES OR SERVICES PO? ..................................................................... 288
WHY IS PURCHASE ORDER NOT SHOWN IN FDC? ........................................................................................................... 288
WHY TAXES IS NOT BEEN CALCULATED IN THE ERP CLOUD? .............................................................................................. 289
WHY ICMS TAX OR ISS TAX DOES NOT CALCULATED IN THE TRANSACTIONS? ....................................................................... 289
ERROR AT “SHIP TO SITE” FOR RECOVERABLE TAX RULE .................................................................................................... 289
UNDERSTANDING PLACE OF SUPPLY .............................................................................................................................. 289
BEST PRACTICE TO SETUP A RECOVERABLE TAX RATE ........................................................................................................ 289
CAN I USE THE SAME DETERMINING FACTOR FOR MORE THAN ONE TAXES? .......................................................................... 290
HOW TO DEFINE MINIMUM TAX AMOUNT FOR WITHHOLDING TAX?.................................................................................. 290
HOW TO CHANGE IRRF TAXABLE BASES USING INSS TAX AMOUNT? ................................................................................. 291
HOW TO OPEN A SERVICE REQUEST (SR) FOR FDG, FDC AND LACLS? .............................................................................. 291
WHICH PARTY SHOULD BE DEFINE IN THE TAX REGIME? ................................................................................................... 292
WHY DOES TAX CLOUD NOT CALCULATE? ...................................................................................................................... 292
HOW TO DEFINE A BRAZILIAN CALENDAR? ..................................................................................................................... 292
HOW TO DEFINE DOCUMENT TO TAX AUTHORITY? .......................................................................................................... 293
WHY PURCHASE ORDERIS DOES NOT HAVE INCLUSIVE TAX IN AP INVOICE MATCH? ............................................................... 293
HOW TO IDENTIFY TAXABLE REGIME FOR DIFFERENT COMPANIES? ..................................................................................... 293
WHEN SHOULD IT USE A LOCATION OF FINAL DISCHARGE? ................................................................................................ 293
HOW TO IDENTIFY TAXABLE REGIME FOR DIFFERENT COMPANIES? ..................................................................................... 293
HOW TO CHANGE “ACCOUNTING CLASS” FOR FISCAL DOCUMENTS FROM FDC TO AP? .......................................................... 294
HOW TO DEFINE INTERNATIONAL SUPPLIER? .................................................................................................................. 294
HOT TO IMPORT OF GOODS USING FOREIGN PURCHASE ORDER? ........................................................................................ 294
HOW TO REVERSE FISCAL DOCUMENT CAPTURE? ............................................................................................................ 295
RECOMMENDATION TO ISSUE OWN FISCAL DOCUMENT (EMISSÃO PRÓPRIA) IN FDG .............................................................. 295
APPENDIX 1 – ACCOUTING FLOW WT TAX ......................................................................................................... 296
APPENDIX 2 – ORACLE ERP CLOUD IMPORT AND EXPORT - MACRO FLOW ........................................................ 297
8
IMPORT GOODS FLOW ............................................................................................................................................... 298
IMPORT SERVICES FLOW ............................................................................................................................................. 299
EXPORT GOODS FLOW................................................................................................................................................ 300
EXPORT SERVICES FLOW ............................................................................................................................................. 301
9
REVISION HISTORY
This document will continue to evolve as existing sections change and new information is added. All
updates are logged below, with the most recent updates at the top.
Date Version Notes

23/Oct/2023 11.1.1113.47 Included that official document by Government
(DARF/GARE) must be created by Oracle Certificated Fiscal
ISV
19/Oct/2023 11.1.1113.46 English correction Import/Export chapter
17/Oct/2023 11.1.1113.45 Procedure to define and create transaction for

Import/Export Flow in the Oracle ERP Cloud using Oracle
Certificated Trading Partner ISV
09/Sep/2023 11.1.1113.44 Version control update
09/Sep/2023 11.1.1113.43 Procedure to define IRPF WITH SIMPLIFIED DISCOUNT and

correct document structure
09/Sep/2023 11.1.1113.42 Procedure to define IRPF WITH SIMPLIFIED DISCOUNT
15-Aug-2023 11.1.1113.41 Include new setup for attend DCTF extractor in:
PROCUREMENT > DEFINE TAX AUTHORITY >
CLASSIFICATION section
16-Jan-2023 11.1.1113.40 Corrected structure layout
16-Dec-2022 11.1.1113.39 Include setup for RTV (Return to Vendor) scenario
11-Nov-2022 11.1.1113.38 Include LACLS_NAT_REND_CODE Tax Reporting Code to

comply with REINF layouts: R-4010, R-4020 and R-4040
23-Sep-2022 11.1.1113.37 Future ICMS and PIS/COFINS recovery in inbound fiscal

document to Fixed Asset
29-Aug-2022 11.1.1113.36 FCP Deferred
08-Aug-2022 11.1.1113.35 Create procedure to define CFPS Code
10
Date Version Notes
04-Aug-2022 11.1.1113.34 Review/change the procedure to generate CTE-OS in the
Oracle ERP Cloud
14-Jun-2022 11.1.1113.33 Review of date in document first page
14-Jun-2022 11.1.1113.32 Procedure to generate CTE-OS in the Oracle ERP Cloud
11-May-2022 11.1.1113.31 Update Model 21 to use Note only for invoice transactions
and use Attachment for invoice or Credit Memo
transactions
Mapping about Model 21’s PDF generate
27-Apr-2022 11.1.1113.30 Manage Associated Balancing Segments review
31-Jan-2022 11.1.1113.29 Geography to attend Importation/Exportation processes

Enterprise Structure for Self-Assessed Taxes and NFSe
Integration updated topics:
Manage Associated Balancing Segments
Manage Associated Business Entities
Define Tax Registrations
Note for Model 21 cancelation
Pasties for Brazil what´s new about 20B to customers and
supplier information and addresses procedure to
international parties
Change “Fiscal Document Capture” to “Inbound Fiscal
Documents”
New capture procedure for “NFSe Integration by Fiscal ISV”
Change “Fiscal Document Generation” to “Outbound Fiscal
Documents”
Change “User and Roles” to “ERP Cloud Roles”
Included new topic “ISV Integrations” in the “ERP Cloud
Roles”
23-Dec-2021 11.1.1113.28 Define Company Classification Code to Register 0002 from
SPED Fiscal
17-Dec-2021 11.1.1113.27 Description for Tax Reporting ICMS Deferred

Included link from FDG What´s New 20B (State Inscription)
New definition for ICMS Partilha
15-Dec-2021 11.1.1113.26 Included the following questions in the Frequently Asked
Questions (FAQ):
How To Define International Supplier?
11
Date Version Notes
Hot To Import Of Goods Using Foreign Purchase Order?
How To Reverse Fiscal Document Capture?
10-Dec-2021 11.1.1113.25 Excluded Brazilian Financial Banks from this document. It

can be find in the LACLS about banks document.
Included procedure to find internal rate for DIFAL
calculation.
Recommendation to create Transaction Tax for Brazil.
15-Oct-2021 11.1.1113.24 Define two new report codes to attend MVA Percentage for
ICMS-ST and Reduction Basis Percentage.
LACLS_BR_MVA_RATE_ICMSST
LACLS_BR_RED_BASIS_RATE
08-Sep-2021 11.1.1113.23 Include procedure to associate BSV in the LRU.
06-Sep-2021 11.1.1113.22 Update Model 21 to use Note instead DFF.

New setup and procedure to calculate withholding tax with
multiples taxable basis and retainage terms.
13-Aug-2021 11.1.1113.21 Clarify procedure when it is must calculate PIS and COFINS
taxes printed (destacado) in the fiscal document.
06-Aug-2021 11.1.1113.20 Adjusts in the ICMS Deferred definition

Procedure to attend ICMS RE#547.706
04-Aug-2021 11.1.1113.19 New Structure for Tax Reporting Type

Change original document title from "Fiscal Solution Path"
to "Financial and Fiscal Solution Path"
Pix Payment for Itau Bank
27-Jun-2021 11.1.1113.18 Reviewed spelling errors
Change Brazilian NFSe procedure to import XML in FDC
15-Jun-2021 11.1.1113.17 Define ICMS Diferred (Diferido)

Define ICMS Partilha
Define general messages for Model 21
Define Note Type to store Hash Code
Change Accounting Class for fiscal documents from FDC to
AP
19-May-2021 11.1.1113.16 Update regime for ICMS, IPI, ISS, II, IOF, PIS and COFINS
Update steps procedures for Model 21
18-May-2021 11.1.1113.15 Update new instruction about CNO Number
12
Date Version Notes
06-May-2021 11.1.1113.14 New Tax Reporting Type and Tax Type to attend ICMS
Deferred (ICMS Diferido)
05-May-2021 11.1.1113.13 New feature Model 21

Change name NFSe-Replacement to NFSe-Substitute
CNO Number for Social Security and Labor Obligations
bookkeeping (eSocial) in Brazil for services related to
construction industry
New group: G_FINAL_DISCHARGE_LOCATION in
LACLS_ExtractApSpedData_Incremental extractor
19-Mar-2021 11.1.1113.12 Tax Reporting Type to indicate Transaction Tax as

Withholding Tax in AR Extractor
New Feature NFSe-Substitute
02-Mar-2021 11.1.1113.11 Fiscal Document Services Model 55 from Brasilia-FDC
New Tax Reporting Type
Change Self-Assessed document layout
12-Feb-2021 11.1.1113.10 Change how to define IPI Tax Report and DIFAL Tax
04-Feb-2021 11.1.1113.9 Included procedure to open SR for FDG, FDC and LACLS-
Extractor
01-Jan-2021 11.1.1113.8 Included rules for tax type in the AP-ISV Extractor
03-Dec-2020 11.1.1113.7 Included important information about Tax Type on Tax

chapter
Include more information about COTO to Payables
10-Sep-2020 5 Change lookup code IRPF
Change steps and name for DARF and GPS Association
04-Sep-2020 4 New procedure to define Brazilian Tax Type

Associate tax in the catalog
New information on FAQ
Change procedure about Withholding Tax progressive table
association for IRPF Tax
27-Aug-2020 3 Define Configuration Owner Tax Options for Brazil and
appendix 1
Define Tax Registration
Reduction IRPF Taxable Base
Map Supplier Item to Internal Item
13
Date Version Notes
14-Aug-2020 2 Define lookups for a tax type
12-Aug-2020 1 First version document
14
LATIN AMERICA CLOUD LOCAL SOLUTION FOR BRAZIL
This document aims to help consultants that are implementing Fiscal Document Capture (FDC),
Fiscal Document Generation (FDG) and Tax for Brazil, with an easy guidelines, step by step, through
product setup configuration describing an approach already tested by Localization team. This is not
the only one approach, since company can have specific business requirements.
The way this document organized, presents some tasks are a part of common features or tax
configuration. There are briefly described here, and for more information on the setup of
common features and tax configuration, see the corresponding Oracle Financials Cloud
implementation guides at (http://docs.oracle.com).
ERP CLOUD ROLES
This topic shows what are the main roles to implement and use Oracle ERP Cloud and ISV Integrations.
ISV INTEGRATIONS
The Oracle certificated ISV must have the following configuration:
JOB ROLES
Name
Financial Integration Specialist
Integration Specialist
Supply Chain Integration Specialist
* Application Developer (is not necessary anymore)
OTHER ROLES
Name
BI Consumer Role
Rest API Extract Privilege
16
DUTY ROLES
Name
BI Publisher Data Model Developer
PRIVILEGIOS
Name
Load Electronic Fiscal Document
Process Electronic Fiscal Documents
Submit Transaction for Fiscal Document Generation
Import Fiscal Document Approval Information
Receive Tax Authority Return File for Fiscal Document
Note: Run the processes ‘Import User and Role Application Security Data’ and ‘Retrieve Latest LDAP Changes’.
17
IMPLEMENTER ROLES
The roles bellow must be assigned for implementer users:
Role Name Description
Application Implementation Performs setup tasks for ERP Cloud.

Consultant
Application Implementation Manages implementation projects. Also responsible for assigning task
Manager owners but does not perform setup tasks.
Financial Application Manages financial application administration. Collaborates with

Administrator financial application users to maintain consistent financial application
setup, rules, and access.
IT Security Manager Accesses to create users, define custom roles and assigned roles in the
users.
Employee Identifies the person as an employee.
18
FUNCTIONAL ROLES
Functional roles must be assigned for implementer users and final users that will works in the
functional areas. The table below list roles and a brief description about it.
For more information about Job Roles, see the Oracle Applications Cloud Security Reference for
Common Features and Oracle Financials Cloud Security Reference for Financials guides on the
Oracle Help Center (http://docs.oracle.com).
Accounts Payable Manager Manages Accounts Payable department and personnel. Overrides exceptions, analyzes
Oracle Fusion Payables balances, and submits income tax and withholding reports to
meet regulatory requirements.
Accounts Payable Specialist Enters invoices ensuring accuracy, uniqueness, and completeness. Matches invoices to
correct purchase orders or receipts ensuring that invoices comply with company policy.
Accounts Payable Supervisor Oversees the activities of Accounts Payables Specialists. Initiates and manages pay
runs. Resolves nondata entry holds.
Accounts Receivable Manager Manages all accounts receivable activities, including defining policy and controls,
establishing processes and procedures, resolving issues, monitoring and analyzing
accounts receivable balances, and creating reports and business intelligence.
Accounts Receivable Specialist Manages and implements all customer payment activities, including receiving
customer payments and electronic remittance advice, performing cash handling
activities, processing customer payments, and applying payments to customer
accounts.
Asset Accountant Performs asset transactions including additions, adjustments, transfers, and
retirements, ensuring accuracy and completeness. Verifies asset information,
transaction details, and accounting entries through inquiry and reports.
Asset Accounting Manager Manages fixed assets department and personnel. Monitors and performs asset
transactions, maintains asset books and set ups in Oracle Fusion Assets, and views
asset information and accounting entries.
Buyer Create purchasing order
19
Cash Manager Protects and develops the company's liquid assets maximizing their use and return to
the organization.
Catalog Manager Create and update catalog in the ERP cloud
Category Manager Create and update category in the ERP Cloud
Cost Accountant Manage Costing
20
Expense Audit Manager Plans, leads, and controls the activities of the internal audit staff to achieve the
objectives of the Internal Audit function for an organization.
Expense Auditor Reviews and audits expense reports on a daily basis to ensure compliance with the
company's reimbursement policy.
Expense Manager Manages company's expense policies and processes. Reviews and proposes changes to
expense policies.
Financial Analyst Analyzes the financial performance of an enterprise or an organization within an

enterprise.
Financial Application Manages financial application administration. Collaborates with financial application
Administrator users to maintain consistent financial application setup, rules, and access.
Financial Integration Specialist Individual responsible for planning, coordinating, and supervising all activities related
to the integration of financial information systems.
General Accountant Records and reports financial transactions and manages revenue, expense, asset,
liability and equity accounts. Responsible for recording accounting adjustments,
accruals, allocations, currency revaluations and translations.
General Accounting Manager Records and reports financial transactions and manages revenue, expense, asset,
liability and equity accounts. Responsible for recording accounting adjustments,
accruals, allocations, currency revaluations and translations.
Procurement Application Create and update procurement setup

Administrator
Procurement Contract Create and update contract setup

Administrator
Procurement Manager Create orders
Supplier Administrator Manages supplier profile and user provisioning.
21
Procurement Catalog Procurement Catalog Administrator

Administrator
Supplier Manager Create and update suppliers
Tax Accountant Prepares and files tax returns and reports for an enterprise, including country, federal,
state, and local corporate, payroll, and transaction taxes.
Tax Administrator Sets up technical areas and the integration with tax service providers.
Tax Manager Defines the tax policies and most efficient tax configuration. Sets up relatively stable
entities that seldom require updates, such as tax regimes and taxes.
Tax Specialist Maintains tax configuration, especially the variable entities that require periodic
updates, such as tax rates and tax jurisdictions.
Role do FDC Fiscal Document Capture duty role
Role do FDG Fiscal Document Generation duty role
22
ASSIGN ROLES
The user must be previous created in the Oracle ERP Cloud, please check this information with
the administrator responsible in the system
Following the steps below to define a user in the ERP Cloud:
1- Go to Tools and click on Security Console

2- Go to Users
3- Search for your user.
4- Click on the username to open a new UI to edit information.
5- Click on Edit
6- Click on Add Role
7- Search for intended role.

8- Click on the Add Role Membership and Done
NOTE: Add Role Membership option will be unavailable if the role is already associated with your user.
9- Save and Close and click Done

10- Log out from the Oracle ERP Cloud and sign in again to ensure the changes take effect.
23
USER AS EMPLOYEE
To enable your user with employee access, perform the following steps:
1- Go to Setup and Maintenance

2- Setup Financials Offerings
3- Functional Areas Users and Security
4- Task Manage Users
5- Click on Create
6- In the Personal Details, fill with the required information ( Last Name, First Name, Email,
Hire Date )
7- In the User Details, enable the Link User Account, and click on the Link icon.
8- Select your user and click Save and Close.
9- In the Employment Information, fill with the required information:
a. Person Type > Select Employee
b. Legal Employer > Select your Legal Employer
c. Business Unit > Select your Business Unit
10- Save and Close
24
GEOGRAPHY
Geography is very important definition to attend Brazilian Fiscal to generate FDG XML File and Oracle Tax Cloud
to identify Jurisdiction for tax calculation.
If the company has Importation or Exportation processes, it is important define IBGE Code to foreign countries
and in Oracle ERP Cloud it is not recommend to create state as ‘EX’ and city as ‘EXTERIOR’. In any geography
structure. This information must be converted by Oracle Certificated Fiscal ISV and the procedure was describe in
the ISVs Integrations DocId 2240956.1 available in My Oracle Support (MOS).
You must define geography to inform in the tax level region (Country, State or City) and the jurisdiction level where
the tax will apply.
This structure will affect Supplier, Customer and Legal Structure to calculate a tax in the transaction.
This step has three parts:
- Define Address Format

- Define Lookup Codes for Geography
- Define Geography
DEFINE ADDRESS FORMAT
Foreign format address is out of scope from this document.
To define the address format for Brazil, perform the following steps:
1. Click on Setup and Maintenance
2. Go to generic tasks
3. Click on Home
4. Click on Setup and Maintenance
5. Search for Define Address Configuration
6. Click on Define Address Configuration to open tasks
7. Click on task Manage Address Formats to open the task
8. Select Brazil in the Country field and search
9. Update Brazil Posta Address Format
25
10. Define address as show below:
9- Save and Close.
26
DEFINE LOOKUP CODES FOR GEOGRAPHY
The lookup code is an alternative field in the geographic structure to define some Brazilian Government
requirements for:
- IBGE Code: Brazilian Institute of Geography and Statistics where define conde for Country, States and
Cities
- SISCOMEX Code: used to define code for foreign countries
DEFINE ALTERNATIVE FIELDS FOR IBGE CODES
The Brazilian Institute of Geography and Statistics (IBGE) defines standard numeric codes for each city and state
in Brazil. The tax authority requires these geography identification codes.
To create a new alternative code type by entering a lookup value for geography identifier subtype, perform the
following steps:
1. Navigate to Setup and Maintenance

2. Search for the Manage Geography Lookups task;
3. Select HZ_GEO_IDENTIFIER_SUBTYPE;
4. In the Lookup codes section, click New;
5. Enter the lookup code as IBGE_CODE;
6. Enter the start date of the record;
7. Click Enabled;
8. Enter the following values:
Attribute Value
Brazil IBGE Geography Code

Meaning
Brazil IBGE Geography Code
Description
C
Tag
9. Click Save and Close.
27
DEFINE ALTERNATIVE FIELDS FOR SISCOMEX CODE S
The Brazilian Central Bank (BACEN) defines standard numeric codes for each Country. The tax authority requires
these geography identification codes for foreign transaction. If you do not have business in others countries you
should not define this step
To create a new alternative code type by entering a lookup value for geography identifier subtype, perform the
following steps:

2. Search for the Manage Geography Lookups task;
3. Select HZ_GEO_IDENTIFIER_SUBTYPE;
4. In the Lookup codes section, click New;
5. Enter the lookup code as SISCOMEX_CODE;
6. Enter the start date of the record;
7. Click Enabled;
Attribute Value
Siscomex Code
Meaning
Siscomex Code
Description
C
Tag
28
CHECK IBGE CODES
Define corresponding IBGE code as an alternative code for the geography for each Brazilian city and state, perform
the following steps:

2. Search for the Manage Geographies task;
3. In the Country Name field, select Brazil;
4. Select the Brazil geography record and click Hierarchy Defined;
5. In the Geography Hierarchy section, select first state under Brazil to highlight the table row;
6. Click Edit. The Edit State page opens;
7. In Primary And Alternative Codes section, click Add;
8. Enter the following values
9. Click Save and Close;
10. Repeat these steps for the other states.
Note: If the company has Importation or Exportation processes it is important define IBGE Code to foreign
countries. Search for county and inform the IBGE Code
CHECK SISCOMEX CODES
Define SISCOMEX code as an alternative code for the geography for each Country, perform the following steps:

2. Search for the Manage Geographies task;
3. In the Country Name field, select Brazil;
4. Select the Brazil in search results to highlight the table row;
5. Click Edit. The Edit Country page opens;
6. In Primary And Alternative Codes section, click Add;
29
DEFINE GEOGRAPHY
Create Brazil Geography, you must validate:
- Define Geography Structure

- Define Geography Validation
- Define Geography Hierarchy
DEFINE GEOGRAPHY STRUCTURE
Define the geography structure, perform the following steps:
1. Go to Setup and Maintenance

2. Setup Financials Offerings;
3. Navigate to Functional Areas Enterprise Profile;
4. Click on Manage Geographies task;
5. In the Country Name Field, select Brazil;
6. Search for Brazil
7. From the Actions menu, select Structure Geography;
8. Click Create;
9. Select the geography type as State and click Add;
10. Select the geography type as City and click Add;
11. Select the geography type as Postal Code and click Add;
30
DEFINE GEOGRAPHY VALIDATION
Define geography validation and address styles for Brazil, perform the following steps:
1. Navigate to Manage Geographies task;

2. Search for the country Brazil;
3. From the Actions menu select Validation Geography;
4. Click add and add the following address style formats:
5. Brazil Postal Address Format;
6. Brazil Tax Address Format.
7. In the Address Style Format field, select No Styles Format.
8. In Geography Mapping and Validation region, select the geography type as State.
9. Select the Enable List of Values, Tax Validation, and Geography Validation check boxes.
10. Select the geography type as City.
11. Select the Enable List of Values, Tax Validation, and Geography Validation check boxes.
12. Repeat these steps for the Brazil Postal Address Format and Brazil Tax Address Format address style
formats.
31
DEFINE GEOGRAPHY HIERARCHY
You can manually enter with each state and city or upload a file using “Manage File Import Activities”.
32
GENERAL LEDGER
Some specific account combinations need to be defined before working with Fiscal Documents
in Brazil.
Define General Accounting for
• transaction taxes
• withholding taxes
• recovery taxes
• fixed assets
• inventory items,
• costs
• supplier
• customer
• expense accounts
• payments
• accounts payables
• accounts receivable
• revenue
• freight
• miscellaneous
33
RAPID IMPLEMENTATION
Rapid implantation is a way to create GL Accounts in Oracle General Ledger. This spreadsheet
creates all GL Structure (chart of account, segment values, accounting calendar and ledger
book). It is possibly create a Legal Entity and Business Unit for the company.
Perform the following steps to find a General Ledger rapid implementation in the Oracle ERP
Cloud:

2. Navigate to Tasks Icon on the right side on the UI
3. Click Search;
4. In the Search page, search by Define Enterprise Structures Configuration for Rapid
Implementation and click the task link;
5. Select the Create Chart of Accounts, Ledger, Legal Entities, and Business Units in
Spreadsheet to define the business requirements;
6. After define your business requirement in the rapid implementation upload the files using the
sequence bellow:
a. ChartOfAccounts.zip
b. FinancialsCommonEntities.zip
7. If the process upload with success checks your configuration.
34
ENTERPRISE STRUCTURE
It is mandatory complement fiscal information for enterprise. All steps are described in the document LACLS Fiscal
ISV Integrations for Brazil available in My Oracle Support note number 2240956.1
This chapter lists steps to setup a basic enterprise structure for Brazil.
LEGAL ENTITIES
Verify if the Legal Entity has the Purpose defined, perform the following steps:
1. Navigate to Setup and Maintenance -> Financial -> Legal Structures

2. Select the Scope for Manage Legal Entities option;
3. If the scope already selected, click on Manage Legal Entities link.
4. In the Name field, inform the Company Legal Name;
5. In the Legal Entity Identifier field, inform the Company Taxpayer identifier;
6. In the Legal Entity Address section, click Create and in the field Purpose, inform Legal option in the
List of Value;
35
LEGAL REPORTING UNITS
Legal Reporting Units are used to issue and receiving Brazilian fiscal documents in the ERP Cloud and consume by
Oracle Certificated Fiscal ISV.
Generally, Company has one main LRU that usually it is a parent CNPJ and the others LRUs are the subsidiaries of
parent CNPJ.
How to define address and address propose for each LRU to the company.

2. Select the Scope for Manage Legal Reporting Unit option;
3. Inform the subsidiary name in the Legal Reporting Unit Name;
4. Create on Create option, in the Legal Reporting Unit Addresses section, to inform the subsidiary
address.
5. Inform the “Time Zone” for the subsidiary.
6. Inform an older date in the “From Date” field
7. Active the address as Primary flag.
8. Click on Create option, in the Address Purpose section, to define propose address for shipment
transactions, the fiscal document generation feature requires the legal reporting unit associated with the
ship-from and ship-to organizations.
Note: More information about this step go to MOS and search Order to Cash for Brazil (Doc ID
2335507.1), document name “Configuring Fiscal Documents for Brazil” chapter “Define Ship-From and
Ship-To Legal Reporting Units”.
9. Save and Close
DEFINE FIRST-PARTY TAXPAYER ID
Check the document Tax Registrations and Taxpayer IDs for Brazil (Doc ID 2347408.1) to define CNPJ, IM. IE
and SUFRAMA for subsidiaries (LRUs) to the company.
36
MANAGE ASSOCIATED BALANCING SEGMENTS
Note: This setup is mandatory for partners that integrate with Cloud ERP using General Ledger’s
LACLS extractor. Partners that have own extraction may not require this setup.
Please, check with your fiscal partner if the below setup is necessary or not for the correct integration for
accounting books.
Company must associate the Balance Segment Values (BSV) in the Main LRU that has a Parent CNPJ and based on
this setup the Oracle certificated ISV will consume journal lines and balance accounts to generate Accounting SPED.
How to associate BSV:

2. Choose for Manage Associated Balancing Segments;
3. Select the Main LRU in the Scope field;
4. Click on Create option;
5. Select the BSV;
6. Inform an older date in the “Start Date”;
7. Save and Close.
ASSIGN BSV IN THE LEGAL REPORTING UNIT
The Balance Segment Value must be associated in the Legal Reporting Unit, because LACLS ISV identify the CNPJ
for company in the SPEP Accounting.
If your company has a SPED Accounting by main CNPJ the BSV must be associated in the main LRU. However,
if the SPED Accounting is reported by establishment the association must be by LRU and if company needs to
report in this way the establishments must be defined as BSV in the General Ledger Chart of Accounts.
Note: Define establishment as BSV because ERP Cloud assign only primary segment balance in the Manage
Associated Business Entities.
1. Navigate to Setup and Maintenance > Legal Structures

2. Change the option Show field to All Tasks;
3. Choose the LRU in the Scope;
4. Select the Manage Associated Business Entities;
5. Click on Create;
6. Select the BSV for LRU;
7. Save and Close.
37
MANAGE ASSOCIATED BUSINESS ENTITIES
This setup is requirement to Brazil, because it is the way that LACLS identify CNPJ, address and Inventory
Organizations subsidiaries (LRU) in the Oracle ERP Cloud. Ensure that the same is setup for Business Unit,
Inventory Organization & Ship from or to location.
To define the Associated Business Entities structure, perform the following steps:

2. Select the Scope for Manage Associated Business Entities option;
3. If the scope already selected, click on Manage Associated Business Entities link.
4. Click Create;
5. Enter the following values, informing the respective Name for each Type selected:
Type Name
Select option in List of Values

Bill From or to location
Inventory Organization
Business Unit
Ship From or to location
NFSE INTEGRATION
This topic only aims to orient that it is necessary to have the organizational structure of the company (Associated
Business Entities), which are used in the extractor responsible to find the Purchasing Services Orders in the Oracle
ERP Cloud.
The Oracle Certificated Fiscal ISV identify the CNPJ (main or from subsidiary) based on the CNPJs capture from
ABRASF xml and the extractor ‘LACLS_PoSearch’ return information that will be used to insert NFSe in the Oracle
Fusion Payables Interface.
If the company does not have PO or Inventory Organization for LRUs it is requirement to have location to use
NFSe Integration, because the ISS can be calculated based on the service was provided and the Oracle Tax Cloud
calculate this tax using ‘Ship-to Location’ field located in the invoice lines. So, the type ‘Ship From or to location’
must be define in the system.
38
DEFINE TAX REGISTRATIONS
Check the document Tax Registrations and Taxpayer IDs for Brazil (Doc ID 2347408.1) to define CNPJ, IM. IE
and SUFRAMA for subsidiaries (LRUs) to the company.
Tax Registration must be used to the following situations:
- Self-Assessed Tax
- NFSe Integration
SELF-ASSESSED TAXES
Self-Assessed must be define when company can be recovery PIS and COFINS, because the rate was different that
XML file.
DIFAL tax is another one that be a self because is calculated when the fiscal document entry in the system and is it
informed in the XML file.
There are more Brazilian taxes that must be defined as Self-Assessed and can be find in the “Self-Assessed Tax”
chapter.
NFSE INTEGRATION
The FDG required this setup when company issue fiscal document. ICMS for goods where must be informed the
State Government Number (IE) and ISS for services where must be informed City Government Number (IE).
NFSe Integration used this setup to find the subsidiary that was responsible to receive the service fiscal document
and Oracle certificated ISV identify the subsidiary in the LACLS AP Extractor.
Note: The Registration can be check in the ‘Accounting’ tab AP Invoice Headers field name ‘First-Party Tax
Registration Number’.
If subsidiary or company does not issue service fiscal document. The recommendation is defined a Tax Registration
Number based on CNPJ.
39
CNO NUMBER
CNO (Cadastro Nacional de Obras) is requirement number control by Federal Goverment (Receita Federal) for
each activity constrution in Brazil.
This topic describes how to define the CNO Number in the ERP Cloud.
ISV integration can consume this information in LACLS_ExtractApSpedData_Incremental extractor, tag

“<CNO_NUMBER/>”.
DEFINE CNO NUMBER
Steps to define CNO Number:
1- Navigate to Setup and Maintenance click on Menu Tasks (located on right) and select Search option.
2- Inform Manage Classification Categories in the field and search for it.
3- Open Manage Classification Categories.
4- Create a new classification category.
5- Inform LACLS_BR_CNO_NUMBER in the fields:
a. Classification Category Field
b. Classification Category Meaning
c. Classification Category Description
6- Save information.
7- Click on Create Classification Codes.
8- Create a code, click on creation option.
9- Click on Next field.

10- Inform the CNO data information:
a. Classification Code: CNO Number
b. Classification Code Meaning: CNO information
c. Classification Code Description: CNO complement information
11- Save the information and OK.

12- Click on Save and Close.
13- Search the LACLS_BR_CNO_ NUMBER
14- Click on Edit
40
15- Click on Add Row in the Entity Assignment
16- Inform AP_INVOICES_ALL and HZ_PARTIES in the Table Name field
17- Save and Close
Steps to execute Classification Hierarchy Generation job:
1- Navigate to Tools option.

2- Select Scheduled Process.
3- Click on Schedule New Process.
4- Search the job.
5- Inform Classification Hierarchy Generation in the Name field and search for it.
6- Click ok.
7- Search for LACLS_BR_CNO_NUMBER in the Classification Category parameter.
8- Change Flattening Method to Force Flattening parameter.
9- Submit job.
Final steps to create a CNO Number must be check in the DocId 2654454.1 (AP: Payables Invoices Questions For
Brazil) available in My Oracle Support.
41
COMPANY CLASSIFICATION CODE
The classification code indicates the company purpose in the “Register 0002” from SPED FISCAL.
The information is based in the table below:
This topic describe how to define a classification code in the ERP Cloud.
ISV Fiscal integration can consume this information in LACLS_ExtractApSpedData_Incremental extractor, in the
tag “<G_ORG_FISCAL_CLASS>”
<G_ORG_FISCAL_CLASS>
PARTY_ID (999999999999999)
CLASS_CATEGORY (LACLS_BR_TAXPAYER_CLASSIFIC)
CLASS_CODE (02)
42
DEFINE CLASSIFICATION CODE
Steps to define Classification Code:
1- Navigate to Setup and Maintenance click on Menu Tasks (located on right) and select Search option.
2- Inform Manage Classification Categories in the field and search for it.
3- Open Manage Classification Categories.
4- Create a new classification category.
5- Inform LACLS_BR_TAXPAYER_CLASSIFIC in the fields:
a. Classification Category Field
b. Classification Category Meaning
c. Classification Category Description
Note: DO NOT ACTIVE Fields “Allow Parent Code Assignment” and “Allow Multiple Class Code Assignment”
6- Click on Add Row in the Entity Assignment

7- Inform HZ_PARTIES in the Table Name field
8- Save information.
9- Click on Create Classification Codes.
10- Create a code, click on creation option.
11- Click on Next field.

12- Inform the code data information:
a. Classification Code: number from table 4.5.5 (tipo de atividade)
b. Classification Code Meaning: description number from table 4.5.5
c. Classification Code Description: description number from table 4.5.5
13- Save the information and OK.

14- Click on Save and Close.
43
MANAGE PARTY FISCAL CLASSIFICATIONS
Steps to able Classification Code in the system:
1- Navigate to Setup and Maintenance and set opt-in to Financials.

2- Navigate through Transaction Tax > Manage Party Fiscal Classifications.
3- Create a new party fiscal classification.
4- Select LACLS_BR_TAXPAYER_CLASSIFIC in the Party Classification field.
5- Paste LACLS_BR_TAXPAYER_CLASSIFIC in the Type Code and Type Name fields.
6- Inform a star date.
7- Inform a Tax Regime, example IPI.
8- Save and Close.
ASSOCIATE THE CODE IN THE LRU
Steps to associate the classification code in the Legal Report Unit:
1- Navigate to Setup and Maintenance and set opt-in to Financials.

2- Navigate through Legal Structures > Manage Legal Reporting Unit Tax Profiles.
3- Search for an LRU.
4- Click on the edition button.
5- Go to Classification tab.
6- Click on the add row button.
7- Select LACLS_BR_TAXPAYER_CLASSIFIC.
8- Select the code.
9- Inform a start date
10- Save and Close
44
DEFINE PARTIES FOR BRAZIL
Parties can be a supplier, customer, or freight carrier that company has a business. The procedure to create Taxpayer
Id (CNPJ) and inscriptions (IM/IE) is described in the note 2347408.1 available in My Oracle Support.
After release 20B from Oracle Financials Cloud, inscriptions (IM/IE) were not more needed, and they were
replacement by new feature ‘Tax Reporting Type Code’ that must be defined in the customers. It is possible find
details information in the ‘What´s New’ release 20B topic ‘Conditional Validation of State Inscription During
Fiscal Document Generation Process for Brazil’.
CUSTOMER INFORMATION
It is important define at least one phone and e-mail in the customer. This information will be used in the Fiscal
Document Issue.
For contacts use primary contact registration available in communications area on site level.
FREIGHT CARRIER
Freight Carrier is register as supplier in the ‘Profile’ tab options field ‘Supplier Type’ equal to ‘Carrier’.
SUPPLIER INFORMATION
It is very important define ‘Payment Method’ and ‘Payment Terms’ in the suppliers ‘Profile’ or ‘Addresses’ level,
system use this information to import documents from Oracle Cloud Payables Open Interface. Documents without
payment method or payment terms will be holding in the interface.
INTERNATIONAL ADDRESSES
In the Oracle ERP Cloud all international parties must have the original address in the system, included Original
Country, State/Province and City.
It is not right defining the following combinations below:
• County as BRAZIL, State as EX and City as EXTERIOR

• Country as different to BRAZIL, State as EX and City as EXTERIOR.
The Oracle Certificated Fiscal ISV is notified by LACLS Brazilian team to change state and city when country is
different from Brazil and the FDG, AP and AR extractors will list the original addresses.
45
RECEIVABLES
As a system prerequisite for defining Localization System Options for Brazil, you need to define
which transaction source, transaction types and receipt methods that are subject to interest
transactions.
INTEREST TRANSACTION
Sales transactions (goods and services) can have interest on the receipt transaction and the system
needs the following setup to create the interest transactions.
INTEREST RECEIPT METHOD
The receipt method is import for system create an interest transaction. This value will be used in the
Localization System Option for Brazil setup.
To define an Interest Receipt Method for Brazil, performing the steps bellow:
1- Navigate to Setup and Maintenance >Financials Offerings> Customer Payments >

Manage Receipt Classes and Methods
2- In the Receipt Classes and Methods page, click on create
3- In the Create Receipt Class and Methods, enter with a name for your interest receipt
method.
4- Select the Creation Method, the Remittance method and the Clearance method.
5- In the Regional Information field, select the Receipt Class for Brazil option;
6- In the Receipt Methods section, click on create
7- Enter with an Interest Receipt Method name and the effective start date.
8- Save and Close
46
INTEREST BATCH SOURCE
Transaction sources are used to assign a default transaction type during invoice entry in the
interest transactions.
To define an Interest Transaction Source performing the steps bellow:
1- Navigate to Setup and Maintenance > Financials > Customer Billing > Manage Transaction
Source
2- In the Transaction Source page, click on Create ( + ) menu
3- In the General Information section, select the Transaction Source Set option
4- Enter with the name of Interest Transaction and Description Select Manual in the type of
option
5- Select Manual in the type of option
6- Enable the Active check box
7- Enter with the start date
8- In the Source Details section, enable check Automatic transaction numbering
9- Enter with the Last Transaction Number
10- Click Save and Close
INTEREST TRANSACTION TYPE
Transaction types contains information about interest transaction types used for invoices, bills receivable, and credit
memos.
To define an Interest Transaction Type, performing the steps bellow:
1- Navigate to Setup and Maintenance > Financials > Customer Billing > Manage Transaction Type
2- In the Transaction Type page, click on Create ( + ) menu
3- Enter with Name of the Interest Transaction in the Name field.
4- Select Debit Memo in the transaction class field
5- Select Open option in the transaction status field
6- Enter with the start date for the transaction type
7- In the Creation Sign, select Positive Sign
8- In the Generate Bill, select Yes option
9- Enable the Open Receivable option
10- Allow adjustment posting option
47
11- Enable Post to GL option
12- Enable Natural application only option
13- In the Reference Accounts, click on create and enter with accounting combination for your Business Unit and
Ledger.
14- Click Save and Close
48
LOCALIZATION SYSTEM OPTIONS
It is necessary enable Regional Localization in the Oracle ERP Cloud to define system option for
Brazilian Solution.
The configuration tasks are organized sequentially in this document to ensure that you perform
setup tasks in the appropriate order. Certain tasks are a part of common features or tax
configuration, and these are briefly described here. For more information on the setup of common
features and tax configuration, see the corresponding Oracle Financials Cloud Implementation
guides at (https://docs.oracle.com/)
ENABLE REGIONAL LOCALIZATION
Navigate through:

2. Navigate to Actions menu and click Go to Offerings;
3. Select Financials Offerings and click on Opt In Features;
49
4. Select Financials Feature and click Edit;
5. Select Regional Localizations Feature and click Edit Enable;
6. Select Brazil check box, click Save and Close and Done.
Note: This enables the specific features for Brazil.
50
LOCALIZATION SYSTEM OPTION
The steps described in this topic reference to a fresh install environment.
Before starting this setup, it is important check the Receivables Cloud topic and define values for
fields:
- Interest Receipt Method

- Interest Batch Source
- Interest Transaction Type
Navigate through:
1. In the Setup and Maintenance page, navigate to Tasks Icon ;

2. Navigate to Search Tasks;
3. Search for Manage Localization System Options and click on link;
4. Click on Create;
5. Select a Brazilian Business Unit;
6. Define the field requirement on the Localization System Options UI.
7. Enable field “Enable Fiscal Document Processing” to enable Business Unit run the FDG and
FDC.
8. Salve and Close.
When this feature is enabled, it changes the way purchasing receiving, costing, shipping,
accounting receivables works.
The PO Receiving and Costing will only consider the Inventory Item transaction from FDC
source.
The Shipping is enabled to work with FDG
The Receivables is enabled to work with FDG and the transaction is completed only with FDG
return from tax authority. Save and Close.
51
INBOUND FISCAL DOCUMENTS
There are two ways to entry Brazilian Fiscal Documents using XML:
• Fiscal Document Capture (FDC)

• NFSe Integration by Oracle Certificated Fiscal ISV
FISCAL DOCUMENT CAPTURE
This process of capturing the fiscal document information is closely related to the business flow of the receiving,
shipping (for in transit receipts), and inventory management applications.
It´s important to mention that FDC only works with fiscal document models 55 (goods) and 57 (freight) for
automatically entrance flow. For manually entrance FDC can handle other fiscal documents models beyond models
55 and 57.
The main purpose of FDC is allow entrance of fiscal documents and relationship among them in order to have
proper acquisition costs for inventory item.
Services Fiscal Documents must be entered directly in Oracle Cloud Payables, manually or using the open interface.
MAIN BUSINESS FLOWS
This is a list of business flows supported by FDC:
• Standard Documents - Purchase orders for goods

• Complementary standard documents
• Drop shipment remittances
• Drop shipment sales
• Complementary drop shipment sales
• Freight acquisition
• Complementary freight acquisition
• Internal transfer
• Import goods
• Goods Return
52
FDC MAIN FEATURES
The image bellow shown a macro view about the Fiscal Document Capture.
53
FISCAL FLOWS/CFOP
FDC needs to have all the flows defined and CFOPs associated in order to automate the inbound process, when
using XMLs files. The process uses the outbound CFOP that come in the supplier xml file to identify the right flow
to follow.
It is possible check these flows with CFOPs using navigation bellow:
1- Go to Fiscal Document Capture work area

2- Click on tasks panel drawer
3- Click on Manage Fiscal Flows
Note: It is not able create a new flow. You can enable or disenable existing flows.
Note: if for some reason you need to add a new CFOP here, it´s necessary to open an SR asking for it. It´s not
allowed to create values in the system.
All Fiscal Flows are seed data and should be reviewed by implementer because for some CFOP there are more than
one possible flow.
54
TOLERANCES
FDC will consider the tolerance defined here to validate, or not, the fiscal document entrance.
The tolerance can be defined at Supplier, Inventory Organization, and Item level.
It is possible define using navigation bellow:
1- Go to Fiscal Document Capture work area

2- Click on tasks panel drawer
3- Click on Manage Fiscal Document Tolerances
Note: If FDC doesn´t find any tolerance set here, the system follows the hierarchy existing in the process: PO,
Receiving options
SERVICES MODEL 55 FROM BRASÍLIA
Fiscal Document Capture is able to process fiscal document Services Model 55 from Brasília. Before executing check
the following tasks:
1- Map Supplier Item with Internal Item

2- Change CMK to replace 00 to 00000000 for NCM tag.
3- The XML must be in the UFT-8 format.
More information about Fiscal Document Capture see Procure to Pay for Brazil (Doc ID 2347415.1) on MyOracle
Support.
55
NFSE INTEGRATION
It is not a new feature in LACLS Brazil. It is a set of procedures that must be applied or considered when company
will use the Oracle certificated ISV to load NFSe document into Oracle Cloud Payables Open Interface.
The Oracle Certificated Fiscal ISV must read an xml file (standard ABRASF xml model) and based CNPJ (main or
subsidiary) with Supplier CNPJ the Oracle Certificated Fiscal ISV will find data in Oracle ERP Cloud, using extractor
‘LACLS_PoSearch’ to get complement requirement information to populate in the AP interface.
More technical information is available in the DocId 2240956.1(LACLS - Integrations with ISVs) available in My
Oracle Support.
The steps below it is a recommendation setup for better performance in this integration with Oracle Certificated
Fiscal ISV:
1- Company structure: check if all LRU are associated to ‘Ship from or to Location’ and ‘Business Unit’.
2- Tax Registration: check if all LRU have a tax registration form ISS tax.
3- Suppliers: check if suppliers have default information for payment method and payment term.
4- Source: define a new source in AP for integration in Manage Payables Lokkups. Lookup Type equal to
Source and Lookup Code ‘LACLS_BR_NFSE’ and Meaning/Description ‘NFSe Brasil’.
5- Distribution Sets: optional only if the company does not work with PO for NFSe.
6- Tax Drivers: according with company tax rules.
56
OUTBOUND FISCAL DOCUMENTS
The configuration tasks are organized sequentially in this document to ensure that you perform setup tasks in the
appropriate order. Certain tasks are a part of common features or tax configuration, and these are briefly described
here. For more information on the setup of common features and tax configuration, see the corresponding Oracle
Financials Cloud Implementation guides at (https://docs.oracle.com/).
For more information about Fiscal Document Generate see Order to Cash for Brazil guide (Doc ID 2335507.1)
on MyOracle Support (https://support.oracle.com/).
Before you configure a fiscal document, you must enable the fiscal document generation feature by performing the
following steps:
Note: Ensure that you assigned the Financials Administration for Brazil duty role to the user to configure the fiscal
document generation feature and the Fiscal Document Generation duty role to the user to enable the creation and
handling of fiscal documents.
57
FISCAL DOCUMENT GENERATION CONTROLS
1. In the Setup and Maintenance page, navigate to Tasks Icon ;

2. Navigate to Search Tasks;
3. Search for Manage Fiscal Document Generation Controls for Brazil task and click on link;
4. Search for Fiscal Document Control;
5. In the Search Results section, click on the Actions menu and Create;
6. On the Create Fiscal Document Generation Controls page, for Event Class field, select the
event class for which you want to define the controls and the defaults. The following table
lists the event class and the corresponding fiscal document type:
Application Event Class Fiscal Document Type
Inventory Management Returns to supplier shipment Return to supplier fiscal documents
Inventory Management Transfer order shipment Internal material transfer fiscal documents
Receivables Debit memo Complementary fiscal documents based on

debit memo transactions
Receivables Invoice Regular fiscal documents based on invoice

transactions
7. In the Associated Business Units section, for the Business Unit field, select the business
unit for which you want to define the controls and defaults for the fiscal document
generation.
Note: Only the business units that were enabled for fiscal document processing are available for selection.
8. You can optionally isolate the controls and defaults by transaction-based fiscal
classifications. In this case, in the Document Fiscal Classification field, select the fiscal
classification that identifies the transaction.
9. Enter the start date of the record.
10. Click Enabled;
58
11. In the Control Information section, enable Require Approval check box;
Note: To complete the invoice before the fiscal document is approved by the tax authority, select the Allow
Completion before Fiscal Document Generation check box in the Control Information section. In this case, you can
complete the invoice manually regardless of the fiscal document’s status. However, if this check box is not selected,
the invoice cannot be completed before the corresponding fiscal document is approved. Once the tax authority
approves it, the invoice is automatically completed.
12. Select the product type (Goods, Service, Goods and Service for mixed fiscal documents)
option;
13. Select Goods Series value;
Note: During transaction entry, this value defaults on the Fiscal Attributes page for goods and mixed fiscal
documents. Only the series defined for a business unit, application, event class, and document fiscal classification is
available for selection on the Fiscal Attributes page.
14. Select Service Series value;
Note: This value defaults on the Fiscal Attributes page for service and mixed fiscal documents. Only the series
defined for a business unit, application, event class, and document fiscal classification is available for selection on
the Fiscal Attributes page.
15. Select Attribute Template value, if necessary;
Note: During transaction entry, the default values defined for the template are automatically populated on the Fiscal
Attributes page.
16. Select Contingency Type value;

17. Select Contingency Series value;
18. Enter with a Contingency Reason;
Note: When a contingency fiscal document is requested by clicking Generate Contingency Fiscal Document on the
Manage Fiscal Document Generation page.
For more information on transaction-based fiscal classifications, see the Oracle Financials Cloud
Implementing Tax guide at docs.oracle.com and for more information about Fiscal Document
Generate see the Order to Cash for Brazil, Configuring Fiscal Documents for Brazil guide (Doc ID
2335507.1) on MyOracle Support (https://support.oracle.com/).
59
NFSE SUBSTITUTE
The Electronic Service Fiscal Document (NFSe) Substitute must be used when it is necessary to cancel a previous
issued and approved NFSe by the Government. In this case, user must create a new fiscal document using previous
information reference from the NFSe that will be cancelled.
Macro Solution Steps

This is a macro solution steps for NFSe Substitute:
MACRO STEP 1: CREATE FIRST NFSE (RPS-1)
1- Create AR Transaction (manual procedure)

2- Process RPS-1 in the FDG (manual procedure)
3- Consume information from RPS-1 by Oracle Certificated Fiscal ISV (automatic)
4- Format XML Standard Government by Oracle Certificated Fiscal ISV (automatic)
5- Send XML to Government by Oracle Certificated Fiscal ISV (automatic)
6- Return Government Status and Official NFSe number by ISV (automatic)
7- Run FDG processes to update fiscal document information (automatic)
8- Finish the process
MACRO STEP 2: CREATE SECOUND (NFS-2) NFSE AS A SUBSTITUTE OF RPS-1
1- Create AR Transaction informing LACLS attributes to reference RPS-1, attribute name and procedure are
describing in more details in Create NFSe Substitute (manual procedure)
2- Process RPS-2 in the FDG (manual procedure)
3- Consume information from RPS-2 by Oracle Certificated Fiscal ISV (automatic)
4- Format XML Standard Government by Oracle Certificated Fiscal ISV and inform tags related to NFSe
Substitute based in the LACLS Attributes (automatic)
6- Return Government Status and Official NFSe number by ISV (automatic)
7- Run FDG processes to update RPS-2 information (automatic)
8- Finish the process
Note: RPS-1 won´t be update in this moment.
MACRO STEP 3: REQUEST CANCEL FIRST NFSE (RPS-1)
1- Request to FDG cancel the RPS-1 (manual request)

2- Consume RPS-1 cancelation by Oracle Certificated Fiscal ISV (automatic)
3- Format XML Standard Government by Oracle Certificated Fiscal ISV (automatic)
5- Return Government Status by ISV. The XML (automatic)
6- Run FDG processes to update fiscal document status as “Canceled” (automatic)
7- Create a Credit Memo in AR to void RPS-1 (manual procedure) and finish the process
60
Detailed explanation about sequence 5 from Macro Step 3
The Government XML file will return with an “ERROR”, because the NFSe has been previous canceled by NFSe-
Substitute.
Oracle Certificated Fiscal ISV must process this information and return to FBDI with “Canceled” status information
and ERP Cloud, based on FBDI, will update the NFSe to cancel fiscal document.
FBDI name “TaxAuthorityReturnImportTemplate” available in Oracle Docs (https://docs.oracle.com) Cloud

Applications section.
Setup
The setup required to use the NFSe Substitute it is defining a LACLS DFFs.
Check DocId 2240956.1 (Flex Fields Configuration) in My Oracle Support (https://support.oracle.com/portal/)
61
FISCAL DOCUMENT MODEL 21
Telecommunication companies, such as multimedia communication (internet providers), radio and TV broadcasters
have a specific invoice model named Model21 (Nota Fiscal de Comunicação Modelo 21”).
This fiscal document has been in force for issuing since 2003 in Brazil.
It is important to note that Model21 must be issued for all communication services rendered in the form of
generation, transmission, retransmission, and amplification.
LACLS Brazilian development team created a special extractor to generate a “Hash Code” with important
information that must be printed in this type of fiscal document.
Note: Cancelation Model 21 has the same procedure to cancel a transaction in Oracle Cloud Receivables. It is need
create a CM and applied to Model 21 Transaction.
Macro Solution Flow
Macro solution steps:
1- Create AR Transaction
2- Run extractor LACLS_ExtractArMod21. Extractor will create a hash code and it will list only new
transaction without MD05 information
3- Consume extractor information by Oracle Certificated Fiscal ISV
4- Format the fiscal document model 21 according to customer template
5- Update AR Transaction with Hash Code in the Note name “BR Modelo 21 Hash Code” or Attachment
name “BR Modelo 21 Hash Code” by Oracle Certificated Fiscal ISV
6- Finish process
Note: Important information to Oracle Certificated Fiscal ISV. In the topics name “How to update a Note” and
“How to update an Attachment” describe in this chapter, it will find the procedure to update hash code in the
Note name “BR Modelo 21 Hash Code” or Attachment name “BR Modelo 21 Hash Code”.
62
SETUP
Below the setup requirement to attend the solution.
ENABLE SEQUENCE NUMBER
This an optional setup and should be define if the company needs to control a sequence number. It will recommend
enabling “Receivable for the Enforce Document Sequencing” available in the Ledger Options.
If the company does not define this feature Oracle Receivable Cloud will generate a number without a sequence.
Enable document sequence in the Oracle ERP Cloud:
1- Setup and Maintenance

2- Chance scope “Setup:” to Financials, if necessary.
3- Select General Ledger
4- Select the ledger name in the Scope
5- Go to Sequencing section
6- Select Ledger in the Sequencing By
7- Select Receivables for the Enforce Document Sequencing
8- Save and Close
DEFINE TRANSACTION TYPE
Create a specific Transaction Type to use Model 21. Note that if the company (Legal Entity) has a central document
sequence number for the model 21 it is recommended use only one transaction type.
However, if the document sequence number it is by establishment it is recommend to define transaction type by
each establishment.
Note: Transaction Type can be defined as “Invoice” or “Debit Memo”
Note: It is not necessary define DFFs in the Transaction Type for model 21
63
DEFINE SOURCE
Create a specific Source to use Model 21. There are attributes (ISV Additional Information) available to define a
model type.
In attribute field (Modelo/Model) it must be informed the value equal to 21. The LACLS-Extractor uses this
information to generate the XML file.
Note: The extractor will select the fiscal document 21 based on number informed in the DFF available in this section
If the attribute field (DFF) is not available in the Source UI definition. It is recommended check DocId 2240956.1
LACLS Fiscal Integration for Brazil (available in My Oracle Support (https://support.oracle.com/portal/).
Check chapter 5-Flex Fields Configuration, section 5.1.2 DFF-Receivables-Batch Sources in the manual LACLS
Fiscal Integration for Brazil.
64
DEFINE LACLS NOTE
Define a note to ISV Integration store the HashCode in the AR Transaction, only for Invoices (transaction type equal “INV”).
For Credit Memo transactions (transaction type equal “CM”) is mandatory store the HashCode in Attachment (see the next topic). Attachment can store HashCode for
invoice transaction too (transaction type equal “INV”).
So, customer can decide where will be store HashCode information for invoice transaction: Note or Attachment. Fiscal Partner must consider update HashCode in
Note (see topic “How to update a Note”) or in Attachment (see topic “How to update an Attachment”), describe in this chapter.
Follow the steps bellow to create a note:
1- Navigate through Setup and Maintenance

2- Go to Tasks and select Search option
3- Inform “Manage Receivables Note Type” and search
4- Create a new lookup code
Important: The Lookup Code field must be exactly as show in the table below. The Oracle Certificated Fiscal ISV will be use the statement code to insert Hash
Code information.
Lookup Code Display Enabled Start Date End Date Meaning Description Tag
Sequence
LACLS_BR_AR_MOD21_HASHCODE Yes 1/1/2011 BR Modelo 21 Hash Code BR Modelo 21 Hash Code
5- Save and Close.

6- Inform “Manage Receivables Note Type Mapping” in the Search field and search
7- Select “Receivables Transaction” in the Business Object field
8- Click on “Add Row”
9- Select “BR Modelo 21 Hash Code” in the Mapped Lookup Value field
10- Inform “N” in the Default field
11- Save and Close
DEFINE LACLS ATTACHMENT
Define an attachment to ISV Integration store the HashCode in the AR Transaction, for Invoice (transaction type equal “INV”) or Credit Memo (transaction type equal
“CM”).
For Credit Memo transactions (transaction type equal “CM”) is mandatory store the HashCode in Attachment.
For invoice transactions (transaction type equal “INV”), customer can be deciding if will be use Attachment or Note (see topic above) for store HashCode information.
Fiscal Partner must consider update HashCode in Note (see topic “How to update a Note”) or in Attachment (see topic “How to update an Attachment”), describe in
this chapter.
Follow the steps below to create an attachment category:

3- Inform “Manage Attachment Categories” and search
4- In “Search Results” section, click on add icon (+) for create a new attachment category
Important: The Category Name field must be exactly as show in the table below. The Oracle Certificated Fiscal ISV will be use the statement code to insert
Hash Code information.
Category Name User Name Module Description
LACLS_BR_AR_MOD21_HASHCODE BR Modelo 21 Hash Code Transactions (Module Key = HedHesTransactions) BR Modelo 21 Hash Code
5- Save and Close.

6- Select the record created. In “Attachment Entities” section, click on add icon (+)
7- In “Entity Name” field, inform: RA_CUSTOMER_TRX_ALL and click on “Search” button
8- Select “Transaction Header” in the search result
9- Click on “Save and Close” button
10- Save and Close.
66
DEFINE ADDITIONAL MESSAGES IN THE MODEL21
Define additional messages for Model21 follow the steps below:

3- Inform “Manage Common Lookups” and search
4- Create a new lookup type as show in the table
Important: The Lookup Type field must be exactly as show in the table below.
Lookup Type Meaning Description Module Lookup Rest Access Recured

Configuration
Level
LACLS_BR_MOD21_MSG LACLS_BR_MOD21_MSG Mensagens Complementares Functional Setup User Secure

para o Modelo 21 Manager
5- Save
67
6- Create new lookup code
Important 1: the TAG field will be used to separate information according to State abbreviation. If the TAG has ‘RJ’ the extractor will consider the information
for LRU that has address state equal to RJ if the state to be different the message will not listed in the Model21 extractor.
If there is no information in the TAG (null) the Model21 extractor will list the message for all LRUs.
Important 2: the lookup code can be defined according with project, there is no necessary to be the same description shown in the table below.
It is only an example.
Lookup Code Display Enabled Start Date End Meaning Description Tag
Sequence Date
MOD21_01 Yes 1/1/2011 MOD21_01 Inform the message that must be printed in the document
MOD21_02 Yes 1/1/2011 MOD21_02 If the message is bigger. It is possible continue the
information in this another lookup code
MOD_RJ_01 Yes 1/1/2011 MOD_RJ_01 PROCON Estadual: Rua da Ajuda 5 - Subsolo - Centro - RJ
Rio de Janeiro - DISK PROCON: (21) 151
www.procon.rj.gov.br
MOD_RJ_02 Yes 1/1/2011 MOD_RJ_02 Nº do Regime Especial: 009/2016 RJ
MOD_DF_01 Yes 1/1/2011 MOD_DF_01 Nº do Regime Especial: 022/2015 – DF

GEESP/COTRI/SUREC/SEF
MOD_MG_01 Yes 1/1/2011 MOD_MG_01 Nº do Regime Especial: PTA 45.000010196-19 MG
7- Save and Close
68
DEFINE SEQUENCE NUMBER
Define a numeric sequence for Model 21. There is no sequence by Business Unit or Legal Report Unit. If the
company needs a sequence by each establishment, it is recommend creating one Transaction Type for each one of
them.
Follow the steps below to define a sequence number:

3- Inform Manage Receivables Document Sequence and search
4- Open Receivables Doc Sequence
5- Inform the transaction name on the field “Document Sequence Category Name” and search
6- Find the Document Sequence Name assignment for correctly company ledger. This information is available
in the Assignment section located in the bottom of page
7- Define a initial value
8- Save
DISABLE FISCAL DOCUMENT GENERATOR
The Model 21 does not use a Fiscal Document Generator (FDG). It is important to define a setup where this type
of transaction it is disabled to go to the FDG.
To access steps to define are available in the Cloud Readiness 20D:
1- Click on the link:

https://www.oracle.com/webfolder/technetwork/tutorials/tutorial/cloud/r13/wn/fin/financials-wn.htm
2- Go to Financials for Americas
3- Click on Advanced Configuration Options to Generate Fiscal Documents for Brazil.
Macro steps described in the link:
1- Enable Fiscal Document Generation: this setup active the FDG for Brazil in the Oracle ERP Cloud.
2- Create A Document Fiscal Classification: this setup must be defined for FD Model 21 and will required to
use in the transaction.
3- Disable The Fiscal Document Generation for Specific Transactions: this setup must be defined to FD
Model 21 to disable the “Document Fiscal Classification” for FDG
4- Save
HOW TO UPDATE A NOTE
Important: “Note” is used only invoice transactions (transaction type equal “INV”). For Credit Memo transactions (transaction type equal “CM”) is mandatory store
the HashCode in Attachment. (See the next topic).
This topic is a technical procedure and must be used to Oracle Certificated Fiscal ISV to update hash code in the note name “BR Modelo 21 Hash Code”. Oracle
Certificated Fiscal ISV needs to use the following Oracle REST WebService to upload the note (Method POST):
https://servername/fscmRestApi/resources/11.13.18.05/receivablesInvoices/{CustomerTransactionId}/child/notes
- servername: it is specific by company
- CustomerTransactionId: it get from extractor tag <G_INVOICES>.<G_MD5>.<CUSTOMER_TRX_ID>
Below there are more columns that must be populated:
Columns Information Comments
"NoteTxt":
<G_INVOICES>.<G_MD5>.<MD5> This information must be in the “base64”. Example:
"NUQwMTkwMzNBOEE4NERDMDYxMkUxM0NFMkZDOUQxNTk="
"NoteTypeCode": "LACLS_BR_AR_MOD21_HASHCODE" Fix information
"SourceObjectCode": "AR_TRANSACTION" Fix information

"CreatorPartyId": <G_INVOICES>.<G_PARTIES>.<PARTY_ID>,
when
<G_INVOICES>.<G_PARTIES>.<SITE_USE_TYP
E> = "BILL_TO"
Request Payload example:
{
"NoteTxt":"MkI5OTQ5MjQ2OTI4NkU4N0MzN0JDMDBDNTkxMkM4QTE=",
"NoteTypeCode":"LACLS_BR_AR_MOD21_HASHCODE",
"SourceObjectCode":"AR_TRANSACTION",
"CreatorPartyId":300000004949782
}
Note: If there is any question. It is recommended to open an Oracle Service Request (SR) in My Oracle Support to LACLS. Details steps to open a SR is describe in
the chapter "FREQUENTLY ASKED QUESTIONS (FAQ)" in this document.
71
HOW TO UPDATE AN ATTACHMENT
Important: “Attachment” can be used for invoice transactions (transaction type equal “INV”) and Credit Memo transactions (transaction type equal “CM”). For
Credit Memo is mandatory use attachment for store HashCode information.
This topic is a technical procedure and must be used to Oracle Certificated Fiscal ISV to update hash code in the attachment name “BR Modelo 21 Hash Code”.
Oracle Certificated Fiscal ISV needs to use the following Oracle SOAP WebService to upload the attachment:
https://servername/fscmService/ErpObjectAttachmentService
Below there are columns that must be populated in payload:
Columns Information Comments
entityName
RA_CUSTOMER_TRX_ALL Fix information
categoryName
LACLS_BR_AR_MOD21_HASHCODE Fix information
allowDuplicate
N Fix information
UserKeyA
<G_INVOICES>.<ORGANIZATION_NAME> Business Unit Name
UserKeyB
<G_INVOICES>.<TRX_NUMBER> Transaction Number
UserKeyC
<G_INVOICES>.<NAME> Transaction Source Name
UserKeyD
<G_INVOICES>.<CUSTOMER_TRX_ID> Transaction Identifier
UserKeyE
#NULL Fix information
AttachmentType
TEXT Fix information
Title
LACLS_BR_HASH_CODE Fix information
Content
<G_INVOICES>.<G_MD5>.<MD5> HashCode
Request Payload example:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:typ="http://xmlns.oracle.com/apps/financials/commonModules/shared/model/erpIntegrationService/types/"
xmlns:erp="http://xmlns.oracle.com/apps/financials/commonModules/shared/model/erpIntegrationService/">
<soapenv:Header/>
<soapenv:Body>
<typ:uploadAttachment>
<typ:entityName>RA_CUSTOMER_TRX_ALL</typ:entityName>
<typ:categoryName>LACLS_BR_AR_MOD21_HASHCODE</typ:categoryName>
<typ:allowDuplicate>N</typ:allowDuplicate>
<typ:attachmentRows>
<erp:UserKeyA>Oracle Brasil</erp:UserKeyA>
<erp:UserKeyB>301120537</erp:UserKeyB>
<erp:UserKeyC>MODELO_21_MANUAL_BR</erp:UserKeyC>
73
<erp:UserKeyD>300000014294573</erp:UserKeyD>
<erp:UserKeyE>#NULL</erp:UserKeyE>
<erp:AttachmentType>TEXT</erp:AttachmentType>
<erp:Title>LACLS_BR_HASH_CODE</erp:Title>
<erp:Content>34DEB667115D6B83B9F2B1A071BFB325</erp:Content>
</typ:attachmentRows>
</typ:uploadAttachment>
</soapenv:Body>
</soapenv:Envelope>
Note: If there is any question. It is recommended to open an Oracle Service Request (SR) in My Oracle Support to LACLS. Details steps to open a SR is describe in
the chapter "FREQUENTLY ASKED QUESTIONS (FAQ)" in this document.
74
CREATE MODEL 21 (INVOICE)
After defining the required setups the company are able to create a Model 21 in ERP Cloud.
User will be able to create a transaction as Model 21 following the steps:
1- Go to Receivables
2- Select Billing option
3- Go to Tasks and select Create Transaction
4- Inform a Business Unit
5- Inform the specific Transaction Source created to Model 21
6- Inform the specific Transaction Type where the fiscal document will use the sequence number
7- Inform Customer
8- Click in the option Show More
9- Go to Miscellaneous section
10- Inform a Legal Report Unit related to the Transaction Type informed before.
Note: Step 10 it is an important step because without this information the extractor won´t list the CNPJ.
The information on the Tax Registration Number should be coherent set with the Transaction Type. Because
the fiscal document sequence is associated with Transaction Type.
11- Inform the Document Fiscal Classification (DFC) created to Model 21
Note: This is an important step because controls if the transaction must be integrated or not to FDG
12- Save and Complete the transaction

13- Finish user procedure
ISV procedure
1- Run extractor LACLS_ExtractArMod21 by ISV user does not have access to process this extractor
Note: The DocId 2240956.1 has a procedure to run the extractor for Model 21
(https://support.oracle.com/portal/)
2- Consume extractor information by ISV

4- Update AR Transaction with Hash Code in the Note name “BR Modelo 21 Hash Code” or Attachment
name “BR Modelo 21 Hash Code”
5- Finish ISV procedure
CREATE MODEL 21 (CREDIT MEMO)
After defining the required setups the company are able to create a Model 21 in ERP Cloud.
Note: Cancelation Model 21 has the same procedure to cancel a transaction in Oracle Cloud Receivables. It is need
create a CM and applied to Model 21 Transaction.
User will be able to create a credit transaction as Model 21 following the steps:
1- Go to Receivables
2- Select Billing option
3- Go to Tasks and select Credit Transaction
4- Inform “Transaction Number” that will be cancelled.
5- In “Transaction Amounts” section, inform 100 in “Credit Percentage” field, for all transaction lines
6- Save and Complete the transaction
7- Finish user procedure
ISV procedure
1- Run extractor LACLS_ExtractArMod21 by ISV user does not have access to process this extractor
Note: The DocId 2240956.1 has a procedure to run the extractor for Model 21
(https://support.oracle.com/portal/)
2- Consume extractor information by ISV

4- Update AR Transaction (Credit Memo) with Hash Code in the Attachment name “BR Modelo 21 Hash
Code”
5- Finish ISV procedure
76
MAPPING ABOUT MODEL 21’S PDF GENERATE
Tables below have mapping using Model 21 extractor for PDF layout generate.
There is no standard PDF template for model 21 print layout. So, the groups detailed in the tables below, may not be in
the customer's PDF print sequence.
ISV Fiscal Partner is responsible to generate the PDF template according to the format used by customer.
XML Extractor / PDF Template - Block 1: “Dados do emitente”
GROUP TAG COMMENTS
Logo Marca deve ser definido no template do

N/A N/A
ISV
G_ORGANIZATIONS LEGAL_ENTITY_NAME
Nomenclatura "ENDEREÇO" deve ser

definida fixa no emplate
ADDRESS1, ADDRESS2, Caracter virgula "," deve ser definida no
G_ORGANIZATIONS
ADDRESS3, ADDRESS4 cadastro de endereço ou no template
Caracter hífen "-" entre o endereço e o bairro
deve estar no template
Nomenclatura "MUNICÍPIO" deve ser definida

G_ORGANIZATIONS CITY
fixa no template
Nomenclatura "ESTADO" deve ser definida

G_ORGANIZATIONS STATE
fixa no template
Nomenclatura "CEP" deve ser definida fixa no

template
G_ORGANIZATIONS POSTAL_CODE
Caracter hífen "-" deve ser definido no cadastro
do endereço ou no template
Nomenclatura "CNPJ" deve ser definida fixa

no no template
G_ORGANIZATIONS TAXPAYER_ID
Caracteres de barra "/" e hífen "-" devem ser
definidos no template
77
TAXPAYER_NUMBER sendo
G_TAXPAYER_ORG_ Nomenclatura "INSCRIÇÃO ESTADUAL"
REPORTING_TYPE_CODE =
IDNTFS deve ser definida fixa no template
'ORA_BR_IE'
TAXPAYER_NUMBER sendo
G_TAXPAYER_ORG_ Nomenclatura "INSCRIÇÃO MUNICIPAL"
REPORTING_TYPE_CODE =
IDNTFS deve ser definida fixa no template
'ORA_BR_IM'
XML Extractor / PDF Template - Block 2: “Dados de Cabeçalho”
GROUP TAG COMMENTS
G_INVOICES TRX_TYPE_DESC Campo descrição do Transaction Type do AR
Campo DFF disponível no Transaction Source

G_INVOICES MODEL
do AR
N/A N/A Texto fixo 'Via Única' no template
Necessário definição de setup de Document

Sequence do ERP Cloud (descrito
G_INVOICES RCT_TRX_NUMBER
anteriormente nesse tópico). Nomenclatura
"No." deve ser definida fixa no template
Informar a série do documento fiscal, que

deverá conter, no mínimo, uma letra não
acentuada, ou um algarismo de 1 a 9 e ter seu
G_INVOICES SERIES
preenchimento iniciado a partir da esquerda
(exemplo: “A “, e não “ A”). Utilizar a letra
“U” para indicar a série única
Definição Lookup LACLS_BR_MOD21_MSG

G_ORG_MESSAGES DESCRIPTION Nomenclatura "No. do Regime Especial" deve
ser definida fixa no template
78
Campo Hashcode. Formato para impressão:
XXXX.XXXX.XXXX.XXXX.XXXX.XXXX.
G_MD5 MD5 XXXX.XXXX
Nomenclatura "Código de Autenticidade" deve

XML Extractor / PDF Template - Block 3: “Dados da linha/cabeçalho”
GROUP TAG COMMENTS
Utilizar o texto após o último caracter “|”,

definido no catalogo
G_LINES NAT_OPER_CODE "LACLS_SERVICE_CODE"
Nomenclatura "Natureza da Prestação de
Serviço" deve ser definida fixa no template
Nomenclatura "CFOP" deve ser definida fixa

G_LINES CFOP_CODE
no template
Formato MM/YY
G_INVOICES EMISSION_PERIOD Nomenclatura "Período da Prestação do
Formato MM/YY
G_INVOICES EMISSION_PERIOD Nomenclatura "Período da Prestação do
79
XML Extractor / PDF Template - Block 4: “Discriminação do Serviço”
GROUP TAG COMMENTS
Descrição será a definida no item

DESCRIPTION - Descrição do
G_LINESITEMS Nomenclatura "Discriminação dos Serviços"
item
deve ser definida fixa no template
O extrator exibe o valor individual por linha,

caso tenha mais de uma linha deve ser definido
GROSS_EXTENDED_AMOU
G_LINES com o cliente a regra de agrupamento
NT
Nomenclatura "TERCEIROS" deve ser
definida fixa no template

G_ORG_MESSAGES DESCRIPTION Nomenclatura "Serviço Sujeito as Seguintes
Retenções" deve ser definida fixa no template
XML Extractor / PDF Template - Block 5: “Informações do imposto - ICMS”
GROUP TAG COMMENTS
G_TAXES TAXABLE_AMT O valor será listado no extrator por linha.

Definir regra de consolidação com o cliente
Definir com cliente se deve ou não ser exibido
no template.
O valor deve ser enviado para prefeitrua
Nomenclatura "Base de Cálculo do ICMS "
deve ser definida fixa no template
G_TAXES TAX_RATE A alíquota será listada no extrator por linha

definir regra de consolidação com o cliente
no template.
Nomenclatura "Alíquota do ICMS " deve ser
80
G_TAXES TAX_AMT O valor será listado no extrator por linha
definir regra de consolidação com o cliente.
no template.
Nomenclatura "Valor do ICMS" deve ser
G_PAYMENT_SCHE AMOUNT_DUE_REMAININ O valor será listado no extrator por linha

DULE G definir regra de consolidação com o cliente.
Nomenclatura "Valor Total NFFSC" deve ser
G_TAXES CST_CODE Usado apenas para o SPED FISCAL
XML Extractor / PDF Template - Block 6: “Informações Adicionais”
GROUP TAG COMMENTS
N/A N/A Nomenclatura "Informações Adicionais" deve

G_LEGAL_MESSAGE
LEGAL_MESSAGE Definição Lookup LACLS_LEGAL_MSG
S
G_ORG_MESSAGES DESCRIPTION Definição Lookup LACLS_BR_MOD21_MSG
Verificar DFF definido pelo cliente para

N/A N/A informar o valor
Caracter "R$" deve ser definido no template
Definição Lookup. Exmplo: MOD_RJ_01.
G_ORG_MESSAGES DESCRIPTION Ver detalhes acima no topico: “DEFINE
ADDITIONAL MESSAGES IN THE
MODEL21”
Definição Lookup. Exemplo: MOD_RJ_02.
G_ORG_MESSAGES DESCRIPTION Ver detalhes acima no topico: “DEFINE
ADDITIONAL MESSAGES IN THE
MODEL21”
81
XML Extractor / PDF Template - Block 7: “Dados do Negocio”
GROUP TAG COMMENTS
N/A N/A Nomenclatura "Dados do Negócio" deve ser

Verificar DFF definido pelo cliente
N/A N/A Nomenclatura "PI" deve ser definida fixa no
template
N/A N/A Nomenclatura "RP" deve ser definida fixa no
template
N/A N/A Nomenclatura "Periodo de veiculacao" deve ser
N/A N/A Nomenclatura "Autorizacao" deve ser definida
fixa no template
N/A N/A Nomenclatura "Exibicao em:" deve ser definida
fixa no template
XML Extractor / PDF Template - Block 8: “Mensagem Legal”
GROUP TAG COMMENTS

G_ORG_MESSAGES DESCRIPTION Talvez seja necessário mais de um campo na
lookup para atender ao tamanho do texto. Essa
definição deve ser definida pelo cliente
XML Extractor / PDF Template - Block 9: “Informações de Duplicatas”
GROUP TAG COMMENTS
Necessário definição de Document Seq do

G_INVOICES RCT_TRX_NUMBER ERP Cloud (000.000.001 a 999.999.999).
Nomenclatura "Nº NFFSC" deve ser definida
fixa no template
82
O valor será listado no extrator por linha e por
G_PAYMENT_SCHE AMOUNT_DUE_REMAININ parcela.
Definir regra de consolidação com o cliente
DULES G
Nomenclatura "Nº NFFSC" deve ser definida
fixa no template
DFF definido pelo cliente Nomenclatura "Duplicata (Nº Ordem)" deve
G_PAYMENT_SCHE Nomenclatura "Vencimento" deve ser definida

DUE_DATE
DULES fixa no template
XML Extractor / PDF Template - Block 10: “Informações de Usuario/Sacado”
GROUP TAG COMMENTS
N/A N/A Nomenclatura "Usuário/Sacado" deve ser

G_PARTIES PARTY_NAME Nomenclatura "Nome / Razão Social:" deve

Bill to do Cliente
TAXPAYER_NUMBER sendo Nomenclatura "Nome / Razão Social:" deve
G_TAXPAYER_PART
REPORTING_TYPE_CODE = ser definida fixa no template
IES_IDNTFS
'ORA_BR_CNPJ' Caracteres de barra "/" e hífen "-" devem ser
Bill to do Cliente
TAXPAYER_NUMBER sendo Nomenclatura "Inscricao Estadual:" deve ser
G_TAXPAYER_PART
REPORTING_TYPE_CODE = definida fixa no template
IES_IDNTFS
'ORA_BR_IE' Caracteres de barra "/" e hífen "-" devem ser
TAXPAYER_NUMBER sendo Bill to do Cliente

G_TAXPAYER_PART
REPORTING_TYPE_CODE = Nomenclatura "Inscricao Municipal:" deve ser
IES_IDNTFS
'ORA_BR_IM' definida fixa no template
ADDRESS1 Bill to do Cliente

G_PARTIES ADDRESS2 Concatenar Assdress1, Address 2 e Address 3
Nomenclatura "Endereço:" deve ser definida
ADDRESS3 fixa no template
Bill to do Cliente
G_PARTIES ADDRESS4 Nomenclatura "Bairro:" deve ser definida fixa
no template
83
Bill to do Cliente
G_PARTIES CITY Nomenclatura "Municipio:" deve ser definida
fixa no template
G_PARTIES IBGE_CITY_CODE Bill to do Cliente
Bill to do Cliente
G_PARTIES STATE Nomenclatura "Estado:" deve ser definida fixa
no template
Bill to do Cliente
G_PARTIES POSTAL_CODE Nomenclatura "CEP:" deve ser definida fixa no
template
G_CONTACTS PHONE_NUMBER Bill to - contato
Informação deve ser definida pelo cliente

N/A N/A Nomenclatura "Praça de Pagamento:" deve ser
XML Extractor / PDF Template - Block 11: “Agência/Corretor”
GROUP TAG COMMENTS
Nomenclatura "Agencia/Corretor" deve ser

N/A N/A

N/A N/A Nomenclatura "Nome / Razão Social:" deve
XML Extractor / PDF Template - Block 12: “Valor por extenso”
GROUP TAG COMMENTS
Regra descrição do valor deve ser aplicada no

N/A N/A
template
84
CTE-OS MODEL-67
This topic describes how to generate CTE-OS (Model 67) in the Oracle ERP Cloud.
Note: The FDG only meets model 55, therefore, it is imported that Oracle Certificated Fiscal ISV converts the
layout model 55 to layout model 67.
In order for this layout conversion to work correctly, it has recorded the "ACCES KEY" generated by SEFAZ in
the Oracle ERP Cloud, so an adjust has done in the LACLS_ExtractArSpedData_Incremental extractor.
For this scenario, as FDG doesn't generate model 67 (CTEOS), it's necessary identifier a transaction using tag
<TRX_TYPE>. Fiscal partner must consider the 5 first positions, if equal CTEOS must be generate model 67 for
sent to SEFAZ.
Different of model 55, the access key it's generate for SEFAZ, when document is validated. Then, the Oracle
Certificated Fiscal ISV must update the access key in field "Attachment" of AR transaction. (Category:
LACLS_BR_AR_ACCESS_KEY). As this model 67 refers to transportation services, all transactions will have
source in AR (not be use Shipment). In LACLS AR extractor, must change tag <FISCAL_DOC_KEY> for show
access key informed in attachment field, ignoring the access key generate by FDG.
DEFINE TRANSACTION TYPE
Create a specific Transaction Type to use Model 67 where the NAME and Description field MUST HAVE started
with CTEOS
85
DEFINE LACLS ATTACHMENT
Create a LACLS_BR_AR_ACCESS_KEY to store the CTE-OS access key.
Follow the steps below to create an attachment category:

3- Inform “Manage Attachment Categories” and search
4- In “Search Results” section, click on add icon (+) for create a new attachment category
Important: The Category Name field must be exactly as show in the table below. The Oracle Certificated Fiscal ISV will be use the statement code to insert
Hash Code information.
Category Name User Name Module Description
LACLS_BR_AR_ACCESS_KEY LACLS_BR_AR_ACCESS_KEY
5- Save and Close.

6- Select the record created. In “Attachment Entities” section, click on add icon (+)
7- In “Entity Name” field, inform: RA_CUSTOMER_TRX_ALL and click on “Search” button
8- Select “Transaction Header” in the search result
9- Click on “Save and Close” button
10- Save and Close.
HOW TO UPDATE AN ATTACHMENT
Attachments can be used for invoice transactions (transaction type equal “INV”) and Credit Memo transactions
(transaction type equal “CM”).
It’s necessary get some information in LACLS AR extractor (LACLS_ExtractArSpedDataDm_Incremental)

for to use in WebService to upload the attachment. For this, you must inform the parameters as below, based on
FDG extractor tags:
Parameter Information (source: FDG extractor) Comments
P_LAST_UPDATE_FROM <FISCAL_DOC_HEADER>.<TRX_DATE> Issuing Date (is the

smallest transaction
date)
P_INVOICE_STATUS SENT Fix information
P_TRX_NUMBER <FISCAL_DOC_HEADER>.<TRX_NUMBER> Transaction Number
This topic is a technical procedure and must be used to Oracle Certificated Fiscal ISV to update CTE-OS access
key. It is imported to use the following Oracle SOAP WebService to upload the attachment:
https://servername/fscmService/ErpObjectAttachmentService
Below there are columns that must be populated in payload:
Columns Information (source: LACLS AR extractor) Comments
entityName
RA_CUSTOMER_TRX_ALL Fix information
categoryName
LACLS_BR_AR_ACCESS_KEY Fix information
allowDuplicate
N Fix information
UserKeyA
<G_INVOICES>.<BU_NAME> Business Unit Name
UserKeyB
<G_INVOICES>.<RCT_TRX_NUMBER> Transaction Number
UserKeyC
<G_INVOICES>.<NAME> Transaction Source Name
UserKeyD
<G_INVOICES>.<CUSTOMER_TRX_ID> Transaction Identifier
UserKeyE
#NULL Fix information
AttachmentType
TEXT Fix information
Title
LACLS_BR_AR_ACCESS_KEY Fix information
Content
Returned by Fiscal Partner, after SEFAZ fiscal Access Key – model 67
document approved. (CTEOS)
88
TAX
The purpose of this document is to assist in the definition of Brazilian taxes using the Oracle Tax Cloud. The product
is flexible, allowing the definition in different ways, in this document we will suggest an initial approach, but it can
be changed according to the complexity of the taxes applied by the company.
The figure below illustrates the macro structure of the Oracle Tax Cloud:
Tax Rules
Tax Regimes
Taxes
Status Jurisdiction
Rates
Tax Regime: it is the set of rules and institutions that govern the tax situation of a legal entity. There two types of
regimes:
• Transaction Tax
• Withholding Tax
Tax: it is a tax attributes as inclusive or no inclusive, government institution and defaults simple rules.
Status: classify the tax status such as Standard or Interstate for instance.
Jurisdiction: determine where the tax will be calculated.
Rate: can be define a percentage or table percentage for IRPF Tax.
Tax Rules: there are two types of rules one as a simple rule (defined in the tax) and a complex rule defined to
overlap the simple rule to calculated tax based on others determinants.
89
COMPLEX TAX RULES
The complex rule is based on Determining Factor and Condition Sets. This combination drives the calculate tax in
the transaction.
The Determining Factor it is compose in the 4 groups:
Party Party Fiscal Classification
Product Product-Based Fiscal Classification
Process Transaction-BasedFiscal Classification
Place Geography
The Determining Factor for Brazil has a specific definition for each group:
The Party Fiscal Classification: is a contribution type for Supplier, Customer and Legal Report Unit.
The Product-Based Fiscal Classification:
Product Fiscal Classification Types and Codes: used to define a NCM information.
Intended Use Fiscal Classifications: intended use for the product or service.
The Transaction-Based Fiscal Classification:
Transaction Business Category: used to define CFOP.
The Place: based on the geography defined in the Suppliers and Customers Address, Inventory Location or Legal
Address.
The picture bellow shows the complex tax rule structure in the Oracle Tax Cloud:
90
WITHHOLDING CALENDAR
Navigation path:
Setup and Maintenance > Define Tax Configuration > Manage Withholding Tax Calendars
The withholding calendar should be used to control tax calculation and the due date for tax documents.
TYPE CALENDARS
General Purpose: control the fiscal period of tax. This type is used to define the period of withholding tax.
91
Payment Terms: control the due date document created in the system. This calendar is used in the “Payment
Terms” field when it is defining a tax authority.
92
TAX REGIME
Tax Regime is a group of taxes in the Oracle Tax Cloud with rules to the system apply tax rates in
transactions according to the company's business.
Oracle Fusion Tax Cloud has two types of regimes witch we suggest grouping them according to the
example listed in the tables.
A tax regime must have a Party associated to able calculate a tax in the transactions. The list of value
shows Legal Entity or Business Unit.
Note: Associate a Business Unit in the Tax Regime.
The Oracle Tax Cloud is ready to use by Business Unit. If it is the first-time Tax Regime configuration
it can defined a Party with the Business Unit.
However if it is not first time configuration and the Oracle Tax Cloud does not calculate a tax, it must
check some steps describe in the “Why Tax Cloud does not calculate?” located in the topic
FREQUENTLY ASKED QUESTIONS (FAQ).
Navigation: Setup and Maintenance>Transaction Tax>Manage Tax Regimes
TRANSACTION TAX REGIME
Brazilian definition MUST HAVE one Tax Regime for each taxes bellow:
- ICMS
- IPI
- PIS
- COFINS
- II
Regime Tax Name Description
CIDE Regime CIDE Tax type code for CIDE Tax.
COFINS COFINS Tax type code for Social Security Funding Contribution Tax.
COFINS COFINS-ST Tax type code for Social Security Funding Contribution Tax with
tributary substitution.
93
ICMS FCP-DIFAL Tax type code for tax on circulation of goods and services with rate
differential and FCP.
ICMS DIFAL-ICMS Tax type code for tax on circulation of goods and services with rate
differential.
ICMS FCP Advance Tax type code for FCP advance.
ICMS FCP Tax type code for FCP Tax.
ICMS FCP-ST Tax type code for FCP Tax with tributary substitution.
ICMS ICMS Tax type code for Tax on Circulation of Goods and Services.
ICMS ICMS Advance Tax type code for tax on circulation of goods and services advance.
ICMS ICMS Exempted The ICMS exempted consists of a tax benefit that grants a tax
(Desonerado) discount on the amount of the tax waived on non-taxed, exempt or
suspended operations
ICMS ICMS-ST Tax type code for tax on circulation of goods and services with
tributary substitution.
II II Tax type code for import tax.
II IOF Tax type code for financial operations tax.
INSS REGIME INSS-Expense Tax type code for Expense Contribution to the National Institute of
Social Security for Companies Tax.
94
IPI IPI Tax type code for Industrial Product Tax.
PIS PIS Tax type code for Social Integration Program Tax.
PIS PIS-ST Tax type code for Municipal Service Tax with tributary substitution.
95
WITHHOLDING TAX REGIME
There are two ways to calculate tax in the ERP Cloud.
• Oracle Tax Cloud

• Oracle Payables Cloud. DO NOT use this way. Because all Brazilian features are only develop considering
Oracle Tax Cloud.
Using Oracle Fusion Tax Cloud to define:
• Deduction amount per dependent (Fixed Deduction per Dependent)

• Number of dependents (Number of dependents)
• Amount deducted from Alimony Amount
• Monthly progressive table for Individual Income Tax
• Minimum payment amount (Threshold Buckets)
• Social Security Contribution deduction amount
In this regime (only one regime is necessary) must be defined the following Brazilian Withholding Tax:
Brazil WT Tax type code for Social Security Funding

COFINS_WT
Contribution Retention Tax.
Brazil WT Tax type code for Net Income Social

CSLL
Contribution Tax.
Brazil WT Tax type code for RURAL Contribution to the

INSS_CP National Institute of Social Security for
Companies Tax.
Brazil WT Tax type code for Contribution to the

INSS_PF_WT
National Institute of Social Security for
INSS_PJ_WT
Companies Tax.
Brazil WT Tax type code for RAT Contribution to the

INSS_RAT National Institute of Social Security for
Companies Tax.
96
Brazil WT Tax type code for SENAR Contribution to the

INSS_SENAR National Institute of Social Security for
Companies Tax.
Brazil WT Tax type code for Brazilian Federal Income

IRPJ
Tax for Companies.
Brazil WT IR is a tax in which each taxpayer, whether

an individual or a legal entity, is required to
pay a certain percentage of their income to
IRRF_PF_WT the government, national or regional ,
IRRF_PJ_WT depending on each jurisdiction.
Brazil WT Tax type code for Municipal Service

ISS_WT
retention Tax.
Brazil WT Tax type code for Social Integration Program

PIS_WT
Retention Tax.
Brazil WT tax aimed at valuing autonomous

transporters and workers in the
SENAT transport sector
Brazil WT tax aimed at valuing autonomous

transporters and workers in the
SEST transport sector
97
DEFINE CONTROLS AND DEFAULTS
Define the default options that will be automatically inherited by the taxes when their creation.
Define in the Tax Inclusive Method field as Special Inclusive Handling, as it is the standard configuration adopted
for calculation in most taxes in Brazil. If you need an inclusive tax, change its method during the tax definition.
Tax Inclusive Method definition according to tax:
• Special Inclusive Handling: used for PIS, COFINS and ISS transactional tax. In this method, the tax amount is not
added to the invoice total amount at fiscal document.
• Standard Noninclusive Handling: used for IPI taxes. In this method, the tax value is added to the invoice total
amount.
CONFIGURATION OPTIONS AND SERVICE SUBSCRIPTIONS
Associate the legal entity or business unit with the Regime (depending in which level you setup was defined). This
procedure is important for Oracle Tax Cloud to recognize the regime that must be applied in the transactions legal
entity or business unit.
98
BRAZILIAN TAX TYPE
It is very important classify all Brazilian Taxes using the Tax Type field on the Manage Tax page.
This field is used to integrate fiscal document into ISV for inbound processes.
The AP-ISV Extractor has the following logic to list the tax in the XML based on field “TAG” and
the tax calculated in the transaction:
1- Show in the extractor if the tax has a Tax Type defined as “ORA_”.
2- Show is not allowed in the extractor if the tax has a Tax Type defined as “ORA_” and
another tax has a Tax Type defined as “LACLS_” plus “TAG” with “ORA_”. Example:
Recovery PIS and COFINS must be defined in the field TAG “ORA_PIS” and
“ORA_COFINS”.
IMPORTANT: This setup must be defined only if company has PIS and COFINS
recoverable.
3- Show in the extractor if the tax has defined a Tax Type with “LACLS_”.
4- Show is not allowed in the extractor if the tax does not have Tax Type defined.
DEFINE LOOKUP CODES
The table below lists the tax type that must be defined in Oracle ERP Cloud. Other tax types was
predefined in the system installation and must be considered to define tax either.
Navigation: Transaction Tax => Manage Tax Lookup Codes
In Lookup Type code, search for “ZX_TAX_TYPE_CATEGORY”.
Create values based in the table and it is import define the Lookup Code has the correctly name
informed in this topic, because it was previous mapped with ISV.
Lookup Code Reference Meaning Tag
LACLS_CIDE Common Set CIDE LACLS_ISV
LACLS_CIDE_WT Common Set CIDE Retido LACLS_ISV
LACLS_IPI_PRES Common Set IPI Presumido (Recup) ORA_IPI
99
LACLS_IPI_COST Common Set IPI Cost
LACLS_DIFAL_FCP Common Set FCP DIFAL LACLS_ISV
LACLS_DIFAL_ICMS Common Set ICMS DIFAL LACLS_ISV
LACLS_FCP Common Set FCP LACLS_ISV
LACLS_FCPST Common Set FCP ST LACLS_ISV
LACLS_FCPST_ADV Common Set FCP ST Antecipado LACLS_ISV
LACLS_ICMSST_ADV Common Set ICMS-ST Antecipado LACLS_ISV
Common Set ICMS Presumido ORA_ICMS

LACLS_ICMS_PRES (Recup)
LACLS_ICMS_COST Common Set ICMS Cost
LACLS_ICMS_DESON Common Set ICMS Desonerado LACLS_ISV
LACLS_INSS_CP_WT Common Set INSS CP Retido LACLS_ISV
LACLS_INSS_EXP Common Set INSS Despesa LACLS_ISV
LACLS_INSS_RAT_WT Common Set INSS RAT Retido LACLS_ISV
100
Lookup Code Reference Meaning Tag
LACLS_INSS_SENAR_WT Common Set INSS SENAR Retido LACLS_ISV
LACLS_INSS_SENAT_WT Common Set SENAT Retido LACLS_ISV
LACLS_INSS_SEST_WT Common Set SEST Retido LACLS_ISV
LACLS_INSS_AD15_WT Common Set INSS Adicional 15 LACLS_ISV
LACLS_IRPF_WT Common Set IRPF Retido LACLS_ISV
LACLS_ISS_WT Common Set ISS Retido LACLS_ISV
LACLS_CSRF_WT Common Set CSRF Retido LACLS_ISV
LACLS_PIS_WT Common Set PIS WT LACLS_ISV
LACLS_PISST Common Set PIS ST LACLS_ISV
LACLS_PIS_RECUP Common Set PIS RECUP ORA_PIS
LACLS_PIS_COST Common Set PIS COST
LACLS_COFINS_RECUP Common Set COFINS RECUP ORA_COFINS
LACLS_COFINS_COST Common Set COFINS COST
LACLS_COFINS_WT Common Set COFINS WT LACLS_ISV
101
LACLS_COFINSST Common Set COFINS ST LACLS_ISV
LACLS_REPORT Common Set Relatório
LACLS_FUNDERSUL Common Set FUNDERSUL LACLS_ISV
LACLS_FUNDEMS Common Set FUNDEMS LACLS_ISV
LACLS_ICMS_DEFFERED Common Set ICMS Differido LACLS_ISV
LACLS_ICMS_PART Common Set ICMS Partilha LACLS_ISV
LACLS_ICMSST_DESON Common Set LACLS_ICMSST_DESON LACLS_ISV
LACLS_FCP_DEFERRED Common Set LACLS_FCP_DEFERRED LACLS_ISV
LACLS_ICMS_FA Common Set LACLS ICMS FA LACLS_ISV
LACLS_PIS_FA Common Set LACLS PIS FA LACLS_ISV
LACLS_COFINS_FA Common Set LACLS COFINS FA LACLS_ISV
Note: Types created by the system MUST BE used normally in the Tax Definition, example ICMS Tax.
Note: The TAX_COST is not listed in the extractor outbound because it is not requirement to bookkeeping in the
fiscal book.
Note: Add PIS Tax and COFINS Tax

-indSomaPISST: get information from tag <TAX_AMT_INCLUDED_FLAG> group
<TAX_LINES> when tag <TAX_TYPE_CODE> equal to LACLS_PISST validated if the
equal to N, if positive then tax must be added in the total invoice.
-indSomaCOFINSST: get information from tag <TAX_AMT_INCLUDED_FLAG> group

<TAX_LINES> when tag <TAX_TYPE_CODE> equal to LACLS_COFINSST validated if the
equal to N, if positive then tax must be added in the total invoice.
102
TAX
To define a tax, follow:
Setup and Maintenance > Define Tax Configuration > Manage Taxes
Specify the details of the tax within the regime, be it Transaction Tax or Withholding Tax, as each tax contains its
own specification that should be assigned only to it. Oracle Fusion Tax Cloud determines that macro specifications
are defined as standards and exceptions worked through rules.Capítulo dividido em duas partes um explicando
cadastro dos impostos de transações e outro para impostos de retenção.
A quick guide to setting transaction tax. In this document you can find an example of the PIS tax, with
examples of rules and fees.
1- Define a Tax Code, Tax name and Tax Type.
Note: You must define a Tax Type for all taxes that will be integrated to ISV. If you create transactions
without a tax type, you must create the transaction again in the system. Because Tax Cloud registered the
tax type during transaction creation.
2- Define the Tax geography. Other values will be filled in automatically.

3- Define the tax point like an Invoice and keep the Tax Inclusive Handling as Regime standard.
4- Define the Tax liability account.
5- Create the indirect values for the Tax
6- Create the Jurisdiction
7- Define the Tax Status
8- Define the Standard Tax Rate
9- Active the Tax for simulation. This option help in the rules validation before definitively activating the tax.
103
TAX RATE
To define a Tax Rate, navigate to:
Setup and Maintenance > Define Tax Configuration > Manage Tax Rates and Tax Recovery Rates
The tax may have different rates, such as ISS, IR and ICMS Brazilian tax rates.
This topic will show you how to create a tax rate that is not define such as a tax standard but will be part of a tax
rule defined in Oracle Fusion Tax Cloud.
All Brazilians taxes are based on a percentage applied on the invoice total amount or item total amount (line based),
except IRPF, which is based on a progressive table by the “Receita Federal do Brasil” authority.
For other taxes, the setting is the same for both transaction tax and withholding tax. For the IRPF, the registration
of the progressive table in the system will be demonstrated in detail.
1- Select the tax, the situation and define the tax rate code. This information will be displayed on the tax lines
generated in the transactions, enter a code according to the planned percentage.
2- Inform the percentage and start date of the tax rate.
IRPF WITHHOLDING TAX PROGRESSIVE TABLE ASSOCIATION

1- Select the IRPF and inform IRPF followed by the year as best practices for identifying the tax in the fiscal
document transaction.
2- Select the IRPF and inform IRPF followed by the year as best practices for identifying the tax in the fiscal
document transaction.
3- Change the rate type to “Gross Amount Rate Schedule”;
4- Inform start date and navigate to Rate Schedule tab;
5- Inform the range and the corresponding tax rates. Note, the starting value from one range to another has
to be the same value as the final range, exactly as shown below:
6- Click on Save
104
PARTY FISCAL CLASSIFICATION
To define the Organization Type in Fusion Tax, follow the steps:
1. Browse:
Setup and Maintenance> Define Tax Configuration> Manage Party Fiscal Classifications
2. Create a record as shown in the figure below:
3. Select the value ORAGANIZATION_TYPE in the Party Classification field (option will attend the registration
of suppliers and customers).
4. Define an easy-to-understand code and nomenclature for future reference and use in the tax rules quick
implementation sheets. Example: Code: TIPO_CONTR and Name: Taxpayer Type.
5. Associate the regime in the "Associated Tax Regimes" region, be sure to associate the regime, otherwise the
classification will not be available for the definition of the rules or for the classification of suppliers and customers.
DEFINE ORGANIZATION TYPE VALUES
The definition is free and here are just a few examples, but these are generally used in most businesses
Nomenclature
Contribuinte
Não Contribuinte
Contribuinte Individual ou Pessoa Física ou Autônomo
Industrial
Simples Nacional
105
PRODUCT-BASED FISCAL CLASSIFICATIONS
The catalog LACLS_SERVICE_CODE and LACLS_NCM_SERVICE_CODE can be used to calculate tax in the transaction. The steps bellow described how
to associate the catalog with the tax.
Note: Check the LACLS - Integrations with ISVs (Doc ID 2240956.1) for more information about catalog.
Navigation: Setup and Maintenance > Transaction Tax > Manage Product-Based Tax Classifications
DEFINE PRODUCT FISCAL CLASSIFICATION TYPE
1- Create a record
2- Select the catalog in the Inventory Category Set field
3- Define levels in the Number of Levels field.
System allows to define until 5 levels. It can be used to segregate codes defined in the catalogs. See the corresponding Oracle Financials
Cloud implementation guides at (http://docs.oracle.com). In the Implementation Tax Manual, chapter “Manage Product-Based Fiscal
Classification” for more information.
4- Inform the same name from catalog in the Fiscal Classification Type Group field
5- Define levels if necessary
6- Associate the tax that will be used to calculate in the transactions.
7- Save and Close.

DEFINE INTENDED USE
1- Change “Search for” to “Intended Use Fiscal Classification Codes”
2- Create a record
3- Enter with Code, Name, Country, and Start Date
4- Save and Close
Note: The table below lists the possible intended use that can be applied in the companies. The list shown the taxes that can be applied according with operation name
(intended use).
Intended Use - Operations
Intended Use IPI ICMS ICMS ST ICMS-DIFAL PIS COFINS II
Fixed Asset Add IPI in the Add IPI in the Add IPI in the Calculate Calculate Not Applied
With IPI Calculate Taxable Basis Taxable Basis Taxable Basis if
interstate
Fixed Asset not Calculate Calculate Calculate if Calculate Calculate Not Applied
Not Applied
IPI interstate
Fixed Assets Calculate Calculate Not Applied Not Applied Calculate Calculate Calculate
Imported
107
Energy Calculate Not Applied Not Applied Calculate and Calculate and Not Applied
Not Applied
Recovery Recovery
Acquisition Calculate and Calculate and Calculate if Calculate and Calculate and Not Applied
Freight between Not Applied Recovery Recovery interstate Recovery Recovery
States
Exportation Calculate Calculate Not Applied Calculate and Calculate and Not Applied
Not Applied
Freight Recovery Recovery
Acquisition Calculate and Calculate and Not Applied Calculate and Calculate and Not Applied
Freight same Not Applied Recovery Recovery Recovery Recovery
States
Not Planned Calculate Calculate Not Applied Calculate and Calculate and Not Applied
Exportation Not Applied Recovery Recovery
Freight
Not Planned Calculate and Calculate and Not Applied Calculate and Calculate and Not Applied
Acquisition Not Applied Recovery Recovery Recovery Recovery
Freight
108
Internal Calculate and Calculate and Not Applied Calculate and Calculate and Not Applied
Not Applied
Transfer Freight Recovery Recovery Recovery Recovery
Raw Material Calculate and Not Applied Not Applied Calculate and Calculate and Calculate
Imported Calculate and Recovery Recovery Recovery
Recovery
Non-inclusive Non-inclusive Non-inclusive
Resales Calculate and Not Applied Not Applied Calculate and Calculate and Not Applied
Calculate and
Imported Recovery Recovery Non- Recovery Non-
Recovery
inclusive inclusive
Consumption Calculate Not Applied Not Applied Calculate Calculate Calculate

Calculate
Imported
109
Raw Material Calculate and Calculate and Calculate Not Applied Calculate and Calculate and Not Applied
Recovery Recovery Recovery Recovery
Raw Material Not Applied Not Applied Not Applied Not Applied Calculate and Calculate and Not Applied
CST 60 Recovery Recovery
Resales with IPI Calculate and Calculate Not Applied Add IPI in the Add IPI in the Not Applied
Calculate and
and ICMS-ST Recovery Taxable Basis and Taxable Basis and
Recovery
Recovery Recovery
Resales with IPI Calculate and Not Applied Not Applied Add IPI in the Add IPI in the Not Applied
Calculate and
and not ICMS-ST Recovery Taxable Basis and Taxable Basis and
Recovery
Recovery Recovery
Resales not IPI Not Applied Calculate and Calculate Not Applied Calculate and Calculate and Not Applied
with ICMS-ST Recovery Recovery Recovery
Resales not IPI Not Applied Calculate and Not Applied Not Applied Calculate and Calculate and Not Applied
and ICMS-ST Recovery Recovery Recovery
110
Consumption Add IPI in the Not Applied Add IPI in the Calculate Calculate Not Applied
Calculate
with IPI Taxable Basis Taxable Basis
Consumption Calculate Calculate Calculate if Calculate Calculate Not Applied

Not Applied
not IPI interstate
DEFINE WITHHOLDING TAX DEDUCITONS
Navigation: Setup and maintenance> Transaction Tax > Manage third-party tax profiles
This chapter describes the procedure for setting income taxes for the following legal requirements in Brazil:
- Deduction amount of alimony (Amount of alimony)
- Number of dependents (Number of dependents)
- Amount of Social Security Contribution deduction
Information is individualized by supplier and is available in the Withholding tax deductions option.
1- Add information in the Withholding tax deductions option
2- Inform the current Tax Regime for the Legal Entity
3- Inform the type income tax
4- Add another line (when applicable) otherwise, save your work.
111
CONFIGURATION OWNER TAX OPTIONS
This setup is important to starting Oracle Tax Cloud to calculate tax in the transactions. The configuration owner is
defined by Party instead to “Global Configuration Owner”.
It is important check which party was associated in the Tax Regime before defining the owner options. The wrong
party defined in the owner option will made the system not calculated a tax.
Choose the correct Party in the field “Configuration Owner” field.
DEFINE CONFIGURATION OWNER TAX OPTIONS FOR TRANSACTIONS TAX
Navigate to:
1. Setup and Maintenance

2. Define Tax Configuration
3. Manage Configuration Owner Tax Options
4. In the Search for, select Transaction Tax
Payables
Choose the event class for Payables and check the fields below:
• Perform additional applicability for imported documents

• Enforce tax from reference document
Another import definition is able “Receipt Tax Options”, check the field “Allow delivery-based tax calculation” and
check the bellow information:
Allow delivery-based tax calculation is used to calculated tax in the receiving processing and affect the Brazilian
Transactions created in the Fiscal Document Capture.
Receivables
At receivables transaction time, the tax option settings of the configuration owner and application event class are
used instead of the default settings.
DEFINE CONFIGURATION OWNER TAX OPTIONS FOR WITHHOLDING TAX
Navigate to
1. Setup and Maintenance

2. Define Tax Configuration
3. Manage Configuration Owner Tax Options
4. In the Search for, select Withholding Tax
Withholding Event Class
Brazil is the only country that has event class for Payables and Receivables
Payables has two event “Standard Invoices” is applied for all documents that will be enter in the Oracle Payables
Cloud. If the company applied withholding tax in the advanced documents, it is necessary define “Prepayment
Invoices”.
Calculation Point must have “Both” in this field because in this way Oracle Tax Cloud will be able to calculate tax
in the invoice enter or payment creations.
Tax Invoice Creation Point should be defined according to business company requirement. Now in Oracle Tax
Cloud it is possible choose if the system will create a document to a Tax Authority in the Oracle Payables Cloud.
If choose:
• Both: the system will create a document to a Tax Authority in the Invoice Enter or Payment Creation,
according with tax definition.
• Payment: the system will create a document only in the Payment Creation.
• Null: no definition the system won´t create document in the system.
Note: LACLS recommend to define null in the “Tax Invoice Creation Point” because this definition allow the
company has a better administration with the Tax Payments (DRAFs/GPS) created by Oracle Certificated Fiscal
ISV.
Note: Accounting flow is mapped in the appendix 1.
Receivables is available only to Brazil and could be defined if the company need to create collection documents
without tax.
113
TAX RULES
Navigation: Setup and Maintenance> Transaction Tax> Manage Tax Rules
This topic will describe the basic tax drives for each transaction tax that can be used to define a
tax rule for Brazil.
ICMS
Can be applied for all ICMS variances. The examples show the geography applicability for ICMS.
The Tax Rules can be defined by process, example Sales Transaction can be defined by two
Determining Factor Name:
• Transaction Business Category

• Transaction Type
Example 1: ICMS Tax in the same State.
Determining Factor Sets Condition
Determining Factor Class Tax Class Qualifier Determining Factor Name Operator Value
Geography Ship From State Equal to SP
Geography Ship to State Equal to SP
Party Fiscal Classification Bill from Organization_type Not SIMPLES_NACIONAL

Equal to
Transaction Input Factor Not applied Intended Use In Fixed Asset With IPI;Fixed
Asset not IPI;Fixed Assets
Imported;Energy;Exportation
Freight;Acquisition Freight
same States;Consumption with
IPI;Consumption not IPI
Transaction Input Factor Not applied Product Type Equal to GOODS
114
Example 2: ICMS Tax in the different State. Based on the LRU as a ship to location, it is necessary
two conditions
One: Include all states from South and Southwest, example:
Geography Ship From State Equal to SP;RJ;SC;RS;PR;MG
Geography Ship to State Equal to CE

Equal to
Acquisition Freight between
States;Consumption with
115
Two: Exclude all states from South and Southwest, example:
Geography Ship From State Not SP;RJ;SC;RS;PR;MG

Equal to
Geography Ship to State Equal to CE

Equal to
116
PIS TAX AND COFINS TAX
Example 1: PIS Tax and COFINS Tax
IPI TAX
Example 1: PIS Tax and COFINS Tax
Transaction Input Factor Not applied Intended Use In Fixed Asset With
IPI;Consumption with IPI;
Consumption with IPI
Product Inventory Linked Level3 NCM Equal to 99999999
Transaction input factor Not Applied Product Type Equal to GOODS

Equal to
117
WITHHOLDING TAXES AND MULTIPLE TAXABLE BASIS
Some Brazilian scenarios have Service Fiscal Documents (NFSe) with different taxable basis to calculate withholding
tax. This topic described how to calculate withholding tax using one or more taxable basis.
Let starting with a real example. The NFSe bellow has four different taxable bases to:
- INSS with R$7.000,00

- ISS with R$4.000,00
- IRPJ with R$5.000,00
- PIS, COFINS and CSLL with R$4.480,00
NFSe Total 10.000,00
INSS Taxable Basis 7.000,00
INSS 3,5% 245,00
ISS Taxable Basis 4.000,00
ISS 5% 200,00
IRPJ Taxable Basis 5.000,00
IPPJ 1,5% 75,00
NFSe Schedule Payment 9.480,00
PIS, COFINS and CSLL Taxable Basis 9.480,00
PIS, COFINS and CSLL 4,65% 440,82
NFSe Final Payment 9.039,18
The steps bellow describes how to define Oracle Tax Cloud and procedure in AP to enter and calculate this NFSe
above.
118
CREATE FORMULA
Create a formula based in the “Taxable Basis Formula” and change the “Taxable Basis Type” to “Assessable Value”
for taxes INSS, ISS and IRPJ.
The PIS, COFINS and CSLL are not applicable because the taxable basis for this tax is based on payment amount.
Steps:
1- Be sure that has a Withholding Tax in the “Scope” field before open the Manage Tax Formulas.
2- Do not change the default information in the “Search for” field.
3- Create a new formula without change ‘Search for”.
4- Inform the “Configuration Owner”, Tax Formula Code and Name.
5- Change the “Taxable Basis Type” to “Assessable Value”.
6- Maintain the default tax regime code.
7- Select a Tax.
8- Change “Start Date” to an older date.
9- Save the new formula.
CREATE WITHHOLDING TAX CODE
This is a tax drive in Oracle Tax Cloud, and it must be define to created tax rules to attend the cases when NFSe has
more than one taxable basis in the document.
Steps:
1- Go to Manage Tax Lookup Codes.

2- Inform “ZX_WHT_TAX_CLASSIFICATION_CODE” in the “Lookup Type” field.
3- Search for it.
4- Go to Financials Generic Lookup Type and click on “Create” option.
5- Inform the tax name, example, INSS in the Lookup Code, Meaning and Description fields.
6- Select the appropriate “Reference Data Set”.
7- Inform an older date in the “Start Date” field.
8- Save.
Note: Realize the same procedure for ISS and IRPJ.
119
CREATE DETERMINE FACTOR
This determine factor is a suggestion to use to create a tax rules to attend the scenario with more than one taxable
basis in the transaction.
Steps
1- Go to Manage Tax Determining Factor Sets.

2- Change “Search for” to “Withholding Tax”.
3- Click on the “Creation” option.
4- Inform a Code and Name
5- Check if the “Tax Regime Code” is related to tax that is must be defined.
6- Select the following “Determining Factor Class and Name”:
Determining Factor Class Tax Class Qualifier Determining Factor Name
Product inventory linked Automatic populated NEW_LACLS_NSM_SERVICE_CODE
Transaction input factor Null Product Type
Transaction input factor Null Withholding tax classification code
Note: It is necessary to create a determining factor for each tax INSS, ISS and IRPJ
7- Save.
120
CREATE CONDITIONS VALUES
Conditions are the value that will start Oracle Tax Cloud to calculate a tax on the transactions.
Steps
1- Inform a Condition Code and Name.

2- Fill values according with each “Tax Determining Factor”
Determining Factor Name Operator Value or Start from Range
NEW_LACLS_NSM_SERVICE_CODE Check note
Product Type Equal to SERVICES
Withholding tax classification Equal to Inform the withholding tax code created to
code attend the scenario INSS, ISS and IRPJ
Note: “Product inventory linked” has an “Operator” restriction and Brazilian consults used to define “Equal to”,
but it is important to analyze the company scenario to better definition.
Note: “Product Type” and “Withholding tax classification code” must be define as “Equal to”.
3- Save.
CREATE TAX RULES
Create three tax rules to calculate INSS, ISS and IRPJ
- Applicability rule: this rule made the Tax available to calculate on the transactions.
- Rate Rule: this rule must be defined when tax has more than one rate. The INSS and IRPJ depend on
services. For ISS depend on place, service and CPOM (Cadastro de Empresas de Fora do Município).
- Taxable Basis: create to change the taxable basis according with formulas.
Note: The ISS Tax is required to have a Determining Factor with Geography and CPOM. In this chapter the
approach was to determine how to calculate tax using different taxable basis. So, it is important to analyze which
conditions must be applied in ISS tax to derivate rates.
121
PURCHASE DOCUMENT STYLES
Define a purchase order for services using style with “Purchase Bases” only for “Amount”.
SCENARIO PROCEDURE SIMULATION
This topic describes procedures to enter with NFSe in Oracle Payables Account and calculate tax using different
taxable basis.
Purchase Orders
1- Go to Procurement.
2- Create a PO as a service.
Payables Invoices
1- Go to Payable.
2- Select Invoices.
3- Create a NFSe.
4- Inform PO number in the “Identifying PO” field.
5- Inform NFSe number, amount, date and payment terms.
6- Click on “Match Invoice Lines” to match PO Lines in the NFSe.
7- Click on the “Match” field.
8- Change the amount to the lower taxable amount generated in the NFSe in the “Amount” field.
Example: ISS tax is the lower taxable amount in the NFSe scenario in this chapter.
9- Click on “Ok” option.
10- Click on “Save” option.
11- Go to “Tax” option.
12- Click on “Withholding” field and inform the appropriate Wth Tax Code.
13- Go to “Assessable Value” field and inform the same taxable base amount.
14- Repeat the steps 6, 7 and 8
Note: If there more two taxable basis amounts, in this step you inform the lower amount. For NSFe
scenario in this chapter you must inform IRPJ taxable amount.
15- Repeat steps 9,10 11, 12 and 13.
16- Repeat steps 6 and 7
17- Change the amount to remaining value for total NFSe. In the NFSe scenario in this chapter it must be the
difference between the previous amount with total NFSe.
18- Repeat step 12 and 13.
19- Open Taxes information.
20- Check the Wth Taxes calculate.
122
CALCULATE WITHHOLDING TAX WITH RETAINAGE TERMS
In the release 21A Oracle delivered a new feature named as “Retainage” for more information about it check the
internet documents Cloud Readiness / Oracle Procurement Cloud (What's New) 21A and Oracle Cloud
Applications Documentation.
The “Retainage” can be used on Construction services fiscal documents (NFSe) where it has a percentage detention
in the amount that will be pay to supplier. However, the Retainage feature has different criteria to calculate tax where
is not applied for Brazilian Tax Legal Requirements.
Here it will describe a simple example to understand the “Retainage” feature. Supplier billing an invoice to the
company and the contract has a deduction percentage (10%). Company paid supplier with net amount, considering
deduction percentage. The 10% was deduction will be paid to supplier according with contract and this event the
only tax that must be calculated it is PIS, COFINS and CSLL.
This topic is help how to define Oracle Tax Cloud to attend the local tax legal requirement, but there are others
setups and procedure that must be define in Oracle ERP Cloud to user the “Retainage” event and to apply this
setups and procedures LACLS recommends to check documents informed in the first paragraph.
123
The NFSe bellow will be use as example using a Retainage Percentage and four different taxable basis to:
- INSS with R$7.000,00

- Retainage Amount with R$1.000,00
- ISS with R$4.000,00
- IRPJ with R$5.000,00
- PIS, COFINS and CSLL with R$4.480,00
NFSe Total 10.000,00
Retainage Percentage 10%
Retainage Percentage 1.000,00
INSS Taxable Basis 7.000,00
INSS 3,5% 245,00
ISS Taxable Basis 4.000,00
ISS 5% 200,00
IRPJ Taxable Basis 5.000,00
IPPJ 1,5% 75,00
NFSe Schedule Payment 8.480,00
PIS, COFINS and CSLL Taxable Basis 8.480,00
PIS, COFINS and CSLL 4,65% 394.32
NFSe Final Payment 8.085,68
This is an example to validate the setup in Oracle Tax Cloud.
124
CREATE FORMULA
Create a new formula or use the previous formula created to calculate withholding tax based on "Assessable Value".
CREATE WITHHOLDING TAX CODE
Create a new withholding tax code or use a previous code created.
CREATE DOCUMENT FISCAL CLASSIFICATION
It is very important define a new value for Document Fiscal Classification to attend Brazilian Tax Legal
Requirements. This new tax drive will be used to Oracle Tax Cloud “knows” when taxes must be calculated for
Retainage scenario.
Based on Brazilian Tax Legal Requirements taxes like INSS, ISS and IRPJ must be calculated on the NFSe entry and
the PIS, COFINs and CSLL in the NFSe payment.
When the retainage amount must be paid to supplier the taxes calculated in the NFSe entry do not be calculated
only withholding tax that will calculate is PIS, COFINS e CSLL.
Steps
1- Go to Manage Transaction-Based Fiscal Classifications.

2- Change “Search for” to “Document Fiscal Classification Codes”.
3- Click on the “Create Level 1 Node” option.
4- Inform a Code and Name that must be applied in the Retainage scenarios.
5- Inform Brazil in the Country field.
6- Inform older date in the “Start Date” field.
7- Save and Close.
125
DETERMINING FACTOR
A new “Determining Factor” must be created to increment the new tax drive “Document Fiscal Classification” that
will be responsible to calculate tax for Retainage Scenarios.
Note: It is very important mapping company scenarios to check if company will apply retaining scenario. If yes, the
company must consider this new determining factor instead to explain in the chapter “Withholding Taxes and
Multiple Taxable Basis”.
This new determine factor must has the following tax drivers:
Determining Factor Class Tax Class Qualifier Determining Factor Name
Document Level1 Document Fiscal Classification
Product inventory linked Automatic populated NEW_LACLS_NSM_SERVICE_CODE
Transaction input factor Null Product Type
Transaction input factor Null Withholding tax classification code, only for
INSS, ISS and IRPJ.
126
CREATE CONDITIONS VALUES
Conditions are the value that will start Oracle Tax Cloud to calculate a tax on the transactions.
Steps
1- Inform a Condition Code and Name.

2- Fill values according with each “Tax Determining Factor”
Determining Factor Name Operator Value or Start from Range
Document Fiscal Classification Check Note Name of Document Fiscal Classification

create to define this condition
NEW_LACLS_NSM_SERVICE_CODE Check note
Product Type Equal to SERVICES
Withholding tax classification Equal to Inform the withholding tax code created to
code attend the scenario INSS, ISS and IRPJ
Note: “Product inventory linked” has an “Operator” restriction and Brazilian consults used to define “Equal to”,
but it is important to analyze the company scenario to better definition.
Note: “Product Type” and “Withholding tax classification code” must be define as “Equal to”.
Note: LACLS recommend creating a Tax Applicability Rules for INSS, ISS and IRPJ using one condition set with
Document Fiscal Classification “Equal to” and another with “Not Equal to” to calculate tax for other scenarios.
3- Save.
127
BRAZILIAN FISCAL CODES
Some taxes in Brazil have a code to identify the type of operation was applied the rate. This topic explains how to
associate the code in the system. This information will be consumed by Oracle certificated Oracle Certificated Fiscal
ISV for fiscal legal requirements.
CST ASSOCIATION
CST is a Brazilian Fiscal Code to identify the rate and operation to the Government Report. For integration
proposes, this code must be defined in the rate level as listed below:
Navigate to Manage Tax Rate
1- Search for the tax rate

2- Edit the rate
3- Go to “Tax Reporting Code”
4- Inform the CST for the rate
Note: Recommend defining a rate with CST Code, example TaxName_Rate_CST ICMS_18%_00 or ICMS_18_20.
MANAGE TAX RERPORTING TYPES
The Tax Reporting Types should be used to complement fiscal information to attend Brazilian Fiscal Requirements
for inbound and outbound processes.
Define or complement a Reporting Type navigate through:
Setup and Maintenance>Define Tax Configuration>Manage Tax Reporting Type
128
DEFINE CBENEF
CBENEF (Código de Benefício Fiscal) is a new tag used in the billing fiscal document to identify the type of fiscal
privilege where company received by the Government. The CBENEF is requirement in some Brazilian States and
must be associated in the Tax Rule (Tax Cloud). Create CENEF as reporting type:
Determining Factor Class
Tax Reporting Type Code LACLS_BR_CBENEF
Tax Reporting Type Name LACLS_BR_CBENEF
Tax Reporting Type Purpose Tax reporting type
Country Brazil
Data Type Text
Tax Regime Code Inform the ICMS tax regime code
Tax Inform the ICMS tax code
Minimum Length of Reporting Codes 1
Maximum Length of Reporting Codes 10
Start Date Inform a start date
End Date
129
Reporting Type Uses
Process Result Enable
Note: Enable only the option above, because this reporting type will use only in the Tax Rule.
Tax Reporting Codes
Tax Reporting Code Inform the Fiscal Code given by the State Government
Description Inform the Fiscal Description or the Code given by the State
Government
Effective Start Date Inform a start date
DEFINE MVA RATE
This code must be defined when company bills a fiscal document with a combination of ICMS-ST reduction basis
and MVA percentage.
Tax Reporting Type Code LACLS_BR_MVA_RATE_ICMSST
Tax Reporting Type Name LACLS_BR_MVA_RATE_ICMSST
Country Brazil
Data Type Text
130
Tax Inform the ICMS-ST tax code
End Date
131
Reporting Type Uses
Note: Enable only the option above, because this reporting type will use only in the Taxable Basis Rule.
Tax Reporting Codes
Tax Reporting Code Inform MVA percentage
Description Inform MVA percentage
DEFINE REDUCTION BASIS RATE
This code must be defined when company bills a fiscal document with a combination of ICMS-ST reduction basis
and MVA percentage.
This definition can be used to define other reductions basis.
Tax Reporting Type Code LACLS_BR_RED_BASIS_RATE
Tax Reporting Type Name LACLS_BR_RED_BASIS_RATE
Country Brazil
Data Type Text
Tax Regime Code
132
Tax
End Date
133
Reporting Type Uses
Note: Enable only the option above, because this reporting type will use only in the Taxable Basis Rule.
Tax Reporting Codes
Tax Reporting Code Inform reduction basis percentage
Description Inform reduction basis percentage
DEFINE ORIGINAL RATE
The original rate should be defined because the rate used to calculate the tax amount is changing by Oracle Tax
Cloud when is applying a formula to find the taxable mount and apply the rate. This setup was identified for IMCS-
ST, FCP-ST, DIFAL and ICMS Deferred (ICMS Diferido).
Create original rate as reporting type and inform the type of code and name according to the tax:
IMCS-ST: LACLS_BR_ICMSST_ORIG_RATE
FCP-ST: LACLS_BR_FCPST_ORIG_RATE
ICMS Deferred: LACLS_BR_ICMSDEFER_ORIG_RATE (this must be used to identify the deferred percentage)
DIFAL Destination Rate and ICMS Partilha: LACLS_BR_ALIQ_INT_DEST_DIFAL
Tax Reporting Type Code According to name above
Tax Reporting Type Name According to name above
134
Country Brazil
Data Type Text
Tax Inform the tax for each type:
ICMS-ST
FCP-ST
ICMS Deferred
For DIFAL and ICMS Partilha you do not define any tax in
this field
End Date
Reporting Type Uses
Tax Rate Enable
Note: ICMS Partilha and ICMS DIFAL must have the “Reporting Type Uses” equal to “Result”, that will be
associated in the Tax Conditions (Tax Rules).
Note: Enable only the option above, because this reporting type will use only in the Tax Rate.
Tax Reporting Codes
Tax Reporting Code Inform the original rate for the tax that was informed in the
header
135
Description Inform any description that clarify the code for user
FCP DEFERRED
-pFCPDif: get information from tag <REP_CODE_TAX_RATE> from group <TAX_LINES>
when tag <REPORTING_TYPE_CODE> equal to LACLS_BR_ICMSDEFER_PERC and tag
<TAX_TYPE_CODE> equal to LACLS_FCP_DEFERRED
- vFCPDif: get information from tag <TAX_AMT> fro group <TAX_LINES> when tag
<TAX_TYPE_CODE> equal to LACLS_FCP_DEFERRED
-vFCPEfet: Fiscal ISV must be do a calculation add using tag <TAX_AMT> when
tag <TAX_TYPE_CODE> equal to LACLS_FCP_DEFERRED and tag <TAX_AMT> when tag
<TAX_TYPE_CODE> equal to LACLS_FCP
Tax Reporting Type Code LACLS_BR_ICMSDEFER_PERC
Tax Reporting Type Name LACLS_BR_ICMSDEFER_PERC
Country Brazil
Data Type Text
136
Tax NULL
End Date
Reporting Type Uses
Tax Rate Enable
137
DEFINE ICMS-ST FISCAL CODES
Define a fiscal category code that determine a taxable amount to ICMS-ST tax.
Create fiscal category code as reporting type:
Tax Reporting Type Code LACLS_BR_MOD_DET_BC_ICMSST
Tax Reporting Type Name LACLS_BR_MOD_DET_BC_ICMSST
Country Brazil
Data Type Text
Tax Inform the ICMS-ST tax code
End Date
Reporting Type Uses
138
Tax Reporting Codes
Tax Reporting Code Inform the code defined by SEFAZ
Description Inform description that clarify the code defined by SEFAZ
139
DEFINE ICMS DESONERADO
Define reason code to calculate ICMS Desonerado Tax. The codes are available in the SEFAZ manual. This code
will apply in the SEFAZ tag name “<motDesICMS>”.
**********ICMS ST DESONERADO**********
- vICMSSTDeson: get information from tag <TAX_AMT> from group <TAX_LINES>
when tag <TAX_TYPE_CODE> equal to LACLS_ICMSST_DESON
- motDesICMSST: get message from tag <REP_CODE_TAX_RATE_RULE> from group
<TAX_LINES> when tag <REPORTING_TYPE_CODE> equal to LACLS_BR_ICMS_DESON and
tag <TAX_TYPE_CODE> equal to LACLS_ICMSST_DESON
Create reason as reporting type:
Tax Reporting Type Code LACLS_BR_ICMS_DESON
Tax Reporting Type Name LACLS_BR_ICMS_DESON
Country Brazil
Data Type Text
Tax Inform the tax code related to ICMS Desonerado
140
End Date
141
Reporting Type Uses
Process result Enable
Tax Reporting Codes
Tax Reporting Code Inform the code defined by SEFAZ
Description Inform description that clarify the code defined by SEFAZ
142
DEFINE LEGAL MESSAGES
It should be defining a legal message as reporting code when fiscal description has a fix text to the tax.
Bellow the Reporting Type Code for each Taxes:
- ICMS: LACLS_BR_ICMS_MSG_LEGAL
- IPI: LACLS_BR_IPI_MSG_LEGAL
- PIS and COFINS: LACLS_BR_PIS_COF_MSG_LEGAL
Create legal message as reporting type:
Tax Reporting Type Code Inform one of reporting type code listed above.
This is code will list in the LACLS Extractors and FDG XML
and ISV will be to be able to map this information.
Tax Reporting Type Name Inform the same data from field Tax Reporting Type Code
Tax Reporting Type Purpose Legal justification message type
Country Brazil
Data Type Text
Tax Regime Code Inform the tax regime code
Tax Inform the tax code
End Date
143
Reporting Type Uses
Tax Rate Enable
Note: Choose the better place to inform a legal message.
Tax Reporting Codes
Tax Reporting Code Inform a code to the legal message
Description Inform the legal message that must be printed in the Fiscal
Document
144
DEFINE TAX TYPE FOR WITHHOLDING AS TRANSACTION
This tax reporting must be used to identify transaction tax as a withholding and the code must be informed in the
tax definition.
Create tax type as reporting type:
Tax Reporting Type Code LACLS_BR_WHT_TYPE
Tax Reporting Type Name LACLS_BR_WHT_TYPE
Country Brazil
Data Type Text
Tax Regime Code Null
Tax Null
End Date
Reporting Type Uses
Tax Enable
145
Tax Reporting Codes
Tax Reporting Code WH
Description Wihholding tax (Imposto de Retenção)
146
DEFINE TAX TYPE FOR CFPS
This tax reporting must be used to link the CFPS code in the transaction according with operation. The
recommendation is defined it in the “Tax Rules”.
Create tax type as reporting type:
Tax Reporting Type Code LACLS_BR_CFPS_CODE
Tax Reporting Type Name LACLS_BR_CFPS_CODE
Tax Reporting Type Purpose “Tax reporting type” for transaction tax
“Withholding tax reporting type” for withholding tax
Country Brazil
Data Type Text
Tax Regime Code Inform tax regime transaction for “Tax Reporting Type” and
withholding tax regime for “Withholding tax reporting type”
Tax Null
End Date
Reporting Type Uses
147
Process result Enable
Tax Reporting Codes
Tax Reporting Code CFPS Code
Description CFPS Description
DARF AND GPS ASSOCIATION
The fiscal code for withholding taxes is not a seed and must be defined in the ERP Cloud before to associate in the
rate.
CREATE FISCAL CODE
The steps below explain how to create the fiscal codes in the system:
1- Navigate Setup and Maintenance > Define Tax Configuration > Manage Tax Reporting Type
2- Search for Brazil in the Country field
3- Click on Create
4- Enter with the SAME NAME write in the table below:
Fields Value
Tax Reporting Type Code LACLS_IRS_WTH_CODE
Tax Reporting Type Name LACLS_IRS_WTH_CODE
5- Select “Withholding tax reporting type” in the Tax Reporting Type Purpose field
6- Select “Text” in the Data Type field
7- Select “Brazil” in the Country field
8- Define minimum and maximum values
148
9- Go to Reporting Type Uses section
10- Select “Tax Rate”
11- Go to Tax Reporting Codes section
12- Click on create.
13- Inform DARF Code or GPS Code in the Tax Reporting Code
14- Inform Description and the Effective Start Date
15- Save information
ASSOCIATE FISCAL CODE
The steps bellow explains how to associate fiscal codes in the system:
1- Navigate Setup and Maintenance > Define Tax Configuration > Manage Tax Rates and Tax Recovery Rates
2- Search for the IRRF or PCC Tax;
3- Go to Tax Reporting Code and click on create;
4- Save and Close.
REINF TABLE 1 (NATUREZA DE RENDIMENTOS) ASSOCIATION
The fiscal code for withholding taxes is not a seed and must be defined in the ERP Cloud before to associate in the
rate.
For comply with REINF layouts: R-4010, R-4020 and R-4040, it’s necessary create the Tax Reporting below for data
store of “Tabela 01 - Natureza de Rendimentos”.
CREATE FISCAL CODE
The steps below explain how to create the fiscal codes in the system:
1- Navigate Setup and Maintenance > Define Tax Configuration > Manage Tax Reporting Type
2- Search for Brazil in the Country field
3- Click on Create
4- Enter with the SAME NAME write in the table below:
Fields Value
Tax Reporting Type Code LACLS_NAT_REND_CODE
Tax Reporting Type Name LACLS_NAT_REND_CODE
149
5- Select “Withholding tax reporting type” in the Tax Reporting Type Purpose field
6- Select “Text” in the Data Type field
7- Select “Brazil” in the Country field
8- Define minimum and maximum values
9- Go to Reporting Type Uses section
10- Select “Tax Rate”
11- Go to Tax Reporting Codes section
12- Click on create.
13- Inform REINF Table 01 Codes in the Tax Reporting Code
14- Inform Description and the Effective Start Date
15- Save information
ASSOCIATE FISCAL CODE
The steps below explain how to associate fiscal codes in the system:
1- Navigate Setup and Maintenance > Define Tax Configuration > Manage Tax Rates and Tax Recovery Rates
2- Search for the IRRF or PCC Tax;
3- Go to Tax Reporting Code and click on create;
4- Save and Close.
150
PAYABLES
For the Tax module we use the Payment Terms to configure the conditions for paying the tax.
Each tax has a type of maturity determined by the Tax Authority for payment. For municipal
taxes (ISS) the date of collection is defined by the mayor, for federal taxes, normally, the date of
tax collection is 30 days after payment of the invoice. These settings are of paramount
importance for the tax module as it is where we define your payments.
DEFINE PAYMENT TERMS
Navigation: Setup and Maintenance > Manage Payment Terms
Create payment terms for withholding taxes in order to control the maturity of documents that will be created in the
Oracle Fusion Payables Cloud.
151
PROCUREMENT
Tax authority has the function of controlling and inspecting compliance with tax legislation
The system needs to have them registered as suppliers, classified as "Tax Authority” in order to have the
withholding taxes generating their income taxes to them.
DEFINE TAX AUTHORITY
On the Oracle ERP Cloud main page, navigate to the Procurement module and select the Suppliers option.
The Tax Authority as Supplier must be creating in order to be associated with the tax that will be used in
withholding fiscal document in Oracle Fusion Payables Cloud.
Points of attention to define Tax Authority.
CLASSIFICATION
Supplier Type: must have the same option of Tax Authority
Tax Classification: classification as Tax Authority
In “Profile Details” section, it’s necessary to classify Tax Authority as

“LACLS_BR_FEDERAL_AUTHOTITY” code. Only Tax Authority with this information can be shown in
DCTF extractor.
For define the new classification code, use topic: DEFINE CLASSIFICATION CODE as example in this
document, and create LACLS_BR_FEDERAL_AUTHORITY code.
After this, you must find the Tax Authority and classify ORGANIZATION_TYPE with code create above.
The configuration will result something like this:
152
153
SITES
In the address tab, Procurement BU’s must be associated. For the name of the site, it is recommended
define as a Tax Name.
154
CONTROL
On the website, an important point is the definition of the "Payment Terms" specific to each tax in order to
meet the salary schedule.
Another point is to define in the field “Terms Date Basis” as “Invoice Date”.
155
PROCUREMENT MANAGEMENT
Define a mapping item code must be done when the supplier item does not have the same internal item
code used by company.
The mapping is required to import XML through the Fiscal Document Capture, if there is no mapping defined
the electronic fiscal document will be held in the interface waiting for correction item.
MAPPING SUPPLIER ITEM
The procedure bellow explain how to map supplier item with internal item company.
Navigate: Product Management -> Product Information Management
1- Select Task List and choose “Manage Trading Partner Items”;

2- Click on Create;
3- Inform the supplier item in the “Trading Partner Item” field;
4- Select Supplier in the “Type” field;
5- Select supplier in the “Trading Partner” field;
6- Go to Relationships;
7- Click on Create;
8- Select the inventory organization and the item that must be mapping to supplier item;
9- Click n Ok button;
10- Save the mapping.
Note: Check note 2379878.1 to upload map item using a file. The document is available in My Oracle
Support.
156
SELF-ASSESSED TAX
Tax defined as Self-Assessed must defined and impact only for Procure-to-Pay processes together with Fiscal
Document Capture (FDC) and never must be used in the Order-to-Cash processes.
The setup must apply in the following taxes:
1. PIS e COFINS: only if the company (Legal Entity) has a Brazilian Fiscal Regime defined as “Lucro Real”.
2. IPI: this tax will define if IPI compound taxable basis amount for taxes defined as Self-Assessed.
3. DIFAL: this tax always defines as self-assessed, because it is not highlighted in the fiscal document, and it
must be calculated to register in the Fiscal Books and posted in the ledger.
This is a solution proposed by Oracle's development team to treat the entrance or recovery in FDC cloud of taxes
that do not come into the fiscal document XML file.
It is important to clarify that PIS and COFINS printed (destacado) in the fiscal document should not considered in
the tax calculation when it is entrance directly in the Oracle Payable Cloud.
The recommendation to calculate these taxes it is only applied in the FDC entrance by XML.
PROCUREMENT TRANSACTION ACCOUNT RULES
Need to define the clearing account to PIS_RECUP, PIS_COST, COFINS_RECUP and COFINS COST. It will
have the zero balance in the receiving process.
The Procurement account definition must be done at “Transaction Account Type”, option “Variance Account”.
157
LOOKUPS
The procedure lookup code for self-assessed should be define in the topic “Brazilian Tax Type”.
TAX DEFINITIONS
PIS and COFINS recovery tax rates depends entirely on buyer´s company tax regime (LRU). Because of that, it is
need to setup PIS and COFINS as SELF-ASSESSED tax. If the company does not recovery in any situation, the
steps below are not necessary.
PIS and COFINS, depending on the application of the material, needs to reach item cost or expense. In order to
attend this requirement, you need to create three taxes for each PIS and COFINS.
Lookup Code Meaning
PIS Used to carry the tax that comes printed (destacado) in the fiscal document
XML file and entered electronic through FDC´s processes
PIS_RECUP Used to calculate and recovery the tax
PIS_COST Used to achieve the cost or expense of the transaction
COFINS Used to carry the tax that comes printed (destacado) in the fiscal document
XML file and entered electronic through FDC´s processes
COFINS_RECUP Used to calculate and recovery the tax
COFINS_COST Used to achieve the cost or expense of the transaction
158
PIS AND COFINS DEFINITION
The table below describes how to define PIS and COFINS that printed (destacado) in the fiscal document (XML)
and entered electronic through FDC´s processes. The table below explains how to define tax PIS as example; please
follow the same procedure to the COFINS.
Tax Header
Tax Regime Code PIS
Configuration Owner Global configuration owner
Tax PIS
Tax Name PIS
Tax Type PIS Tax
Start Date 1/1/2019
Enable tax for simulation Yes
Enable tax for transactions Yes
Tax Information
Geography Type COUNTRY
Parent Geography Type COUNTRY
Parent Geography Name Brazil
159
Override Geography Type Null
Tax Currency BRL-Brazilian Real
Tax Minimum Accountable Unit 0,01
Tax Precision 2
Conversion Rate Type Corporate
Rounding Rule Nearest
Compounding Precedence Null
Reporting Tax Authority Null
Collecting Tax Authority Null
Applied Amount Handling Prorated
Set as offset tax Null
Set tax for reporting purposes only Null
Tax Controls and Defaults - CONTROLS
Tax Point Basis Null
Tax Inclusion Method Special inclusive handling
Allow override and entry of inclusive tax lines Yes
Allow tax rounding override Yes
160
Allow override of calculated tax lines Yes
Allow entry of manual tax lines Yes
Use legal registration number Yes
Allow duplicate registration numbers Null
Allow multiple jurisdictions Yes
Allow creation of multiple jurisdictions Null
Use in withholding tax calculation Null
Tax Controls and Defaults – TAX ACCOUNTS CONTROLS
Tax Accounts Creation Method Create tax accounts
Tax Accounts Source Null
Tax Controls and Defaults – TAX EXCEPTIONS AND EXEMPTIONS CONTROLS AND DEFAULTS
Allow tax exceptions Yes
Allow tax exemptions Yes
Use tax exemptions from an existing tax Null
Tax Exemptions Source Null
161
162
Tax Controls and Defaults – REGISTRATION NUMBER CONTROLS AND DEFAULTS
Validation Type Null
Validation Level Null
Duplicate Validation Level Null
Tax Controls and Defaults – TAX RECOVERY CONTROLS AND DEFAULTS
Allow tax recovery Null
Note: The “Allow tax recovery” flag should not be set to this tax
Tax Rule Defaults - DIRECT DEFAULTS
Place of Supply Bill from
Tax Applicability Not Applicable
Tax Registration Bill-from party
Tax Calculation Formula STANDARD_TC
Taxable Basis Formula STANDARD_TB
163
Tax Rule Defaults - INDIRECT DEFAULTS
Tax Jurisdiction Inform Jurisdiction responsible to control the tax
Tax Status Inform appropriate status to the tax
Tax Rate Should be defined a zero rate
Note: It is recommending a zero rate because the tax printed in the fiscal document won´t be used in the Tax Cloud.
However, must be posted in the ledger using the same account defined in the line type ITEM.
TAX ACCOUNTS
Inform the Liability Tax Account for the tax.
164
PIS AND COFINS COST DEFINITION
The table below describes how to define PIS_COST and COFINS_COST. The table demonstrate PIS as example;
please follow the same procedure to the COFINS.
Tax Header
Tax Regime Code PIS
Tax PIS_COST
Tax Name PIS_COST
Tax Type LACLS PIS Cost
Start Date 1/1/2019
Tax Information
165
Tax Precision 2
Tax Point Basis Invoice
166
167
Validation Type ORA_BR_OTHER
Validation Level No validation
Duplicate Validation Level None
Note: Select ORA_BR_OTHER for Validation type; NONE for validation level! This will be used in Tax Registration
setup later! This tax will be liable to be recoverable, select Allow to Recovery and RECOVERABLE to Primary Recovery
Type!
Tax Registration Bill-to party
168
Tax Rate Should be defined a negative rate
TAX ACCOUNTS
169
PIS AND COFINS RECUP DEFINITION
The table below describes how to define PIS_RECUP and COFINS_RECUP. The table demonstrate PIS as
example; please follow the same procedure to the COFINS.
Tax Header
Tax Regime Code PIS
Tax PIS_RECUP
Tax Name PIS_RECUP
Tax Type LACLS PIS Recup
Start Date 1/1/2019
Tax Information
170
Tax Precision 2
171
172
Type!
Allow tax recovery Yes
Allow tax recovery rate override Null
Primary Recovery Type RECOVERABLE
Secondary Recovery Type Null
173
Tax Recovery Rate Inform the percentage that company uses to recovery tax
Tax Rate Inform the rate used to calculate the tax
TAX ACCOUNTS
Inform the Recoverable Tax Account and Liability Tax Account for the tax.
174
DIFAL DEFINITION
Differently from PIS and COFINS, to have DIFAL tax calculated and reflected into item cost, it is necessary to
create only one “Self-Assessed” tax. Follow the steps below to do it:
Tax Header
Tax Regime Code ICMS
Tax DIFAL
Tax Name DIFAL
Tax Type ICMS DIFAL
Start Date 1/1/2019
Tax Information
Geography Type STATE
175
Tax Precision 2
Compounding Precedence Inform a number higher than IPI_REP
176
177
Type!
Place of Supply Ship to
178
Tax Jurisdiction Inform default Jurisdiction responsible to control the tax
Tax Status Inform a state in Jurisdiction that will be more applicable in the
tax
Tax Rate Should be defined default differential rate
Note: It is important create all states as Jurisdiction; use the procedure XX as state plus -GOV DO ESTADO. Example,
SP-GOV DO ESTADO
Note: DIFAL rates must be always a differential rate because Tax Self-Assessed does not calculate with a Normal Tax
in this point ICMS Tax.
Note: DIFAL Tax it is not a recoverable tax and Registration Number with no validation in the Duplicate Validation
and none in the Validation Level
TAX ACCOUNTS
179
IPI REP DEFINITION
Sometimes IPI Tax compound a taxable amount for PIS, COFINS and DIFAL.
The way to have that in Tax Cloud is creating a second tax, as reporting only, that the only purpose is to calculate
this amount and, once PIS, COFINS and DIFAL are SELF ASSESSED taxes, this IPI REP must be SELF
ASSESSED as well.
The IPI REP code was created to differentiate from regular IPI since IPI REP do not account and recover, it is just
part of the tax calculation formula for PIS, COFIN and DIFAL as SELF ASSESSED.
Tax Header
Tax Regime Code IPI
Tax IPI_REP
Tax Name IPI_REP
Tax Type Report Only
Start Date 1/1/2019
Tax Information
180
Tax Precision 2
Compounding Precedence Inform a number lower than DIFAL Tax (Self Assessed)
Set tax for reporting purposes only Yes
181
182
Type!
183
Tax Rate Inform rate for the tax report
TAX ACCOUNTS
There is no account definition for this tax.
184
TAX REGISTRATION
Enabling TAX as SELF-ASSESSED, it is necessary to setup the tax registration for each LRU. Be sure what is the
main LRU defined in the ERP Cloud and defined it first in the tax registration.
For the solution defined by the development team, it´s necessary to setup here the taxes: PIS_RECUP, PIS_COST,
COFINS_RECUP, COFINS_COST, DIFAL and IPI REP.
Legal Reporting Unit Tax Registration
Legal Reporting Unit Inform Main LRU
Tax Regime Code Inform tax regime
Tax Inform tax
Tax Jurisdiction Code Null
Registration Details
Tax Registration Type Null
Company Reporting Name Null
Legal Registration Address Null
Validation Level None
Duplicate Validation Level No validation
185
Registration Number Inform Main LRU CNPJ
Issuing Tax Authority No
Set as default registration No
Tax Registration Status Registered
Tax Registration No
Start Date Inform an old date
End Date Null
Source Null
Invoice Controls
Rounding Rule Null
Set as self-assessment Yes
Set invoice values as tax inclusive Null
Note: Other fields not listed in the table above does not be change
Note: Select the SET AS SELF-ASSESSED (reverse charge) flag; the validation type and level, set at the tax setup is
inherit here!
186
SPECIAL TAXES
Taxes that have special definitions in Oracle Tax Cloud:
- ICMS Deffered (Diferido)

- ICMS Partilha
ICMS DEFERRED (DIFERIDO)
The ICMS Deferred is a type of tax substitution, in which occurs the postponement or advanced of the tax payment,
where the recovery obligation will be transfer to another party.
This topic describes how to define this tax to attend an Outbound Fiscal Document.
It is necessary three taxes:
• ICMS Normal: used to post the tax amount, when the ICMS Differed is not equal to 100% (one hundred
percentage) and inform the CST number in the XML and base tax to use in the calculation formula with
ICMS Deferred.
• ICMS Report: used to show in the xml the original rate, taxable amount and tax amount that must be
informed in the Fiscal Document XML. The reason of this tax it is because ICMS Normal change
information after applied the formula during tax calculation.
• ICMS Deferred: used to show the deferred amount into FDG XML and base tax to use in the calculation
formula with ICMS Normal
187
ICMS NORMAL
Define ICMS Normal using the follow information. If the system has ICMS Normal defined, this step it is not
necessary.
Tax Header
Tax ICMS
Tax Name ICMS
Tax Type ICMS Tax
Start Date 1/1/2019
Tax Information
188
Tax Precision 2
Compounding Precedence If the company has IPI in the sales transactions. It is important
define a compound number lower that IPI
189
190
Allow tax recovery Enable this field if the company has ICMS Recoverable in the
purchasing process
191
Tax Rate Inform appropriate rate to the tax
TAX ACCOUNTS
Inform the Liability Tax Account for the tax and Recoverable Tax Account.
TAX JURISDICTION
Inform the 27 Brazilian States in the Jurisdiction for the ICMS Normal.
192
ICMS REPORT
Define ICMS Report using the follow information. If the system has ICMS Report defined, this step it is not
necessary.
Tax Header
Tax ICMS Report
Tax Name ICMS Report
Tax Type Report
This type must be defined before starting this setup, check the
topic Brazilian Tax Type
Start Date 1/1/2019
Tax Information
193
Tax Precision 2
Compounding Precedence It is not applied for ICMS Deferred
It is requirement to attend ICMS RE#547.706
194
195
196
TAX ACCOUNTS
Tax Account does not need for tax report.
TAX JURISDICTION
Inform the 27 Brazilian States in the Jurisdiction for the ICMS Report. It is very important define this jurisdiction
as equal to ICMS Normal.
197
ICMS DEFERRED
Define ICMS Deferred as report using the follow information.
Tax Header
Tax ICMS Deferred
Tax Name ICMS Deferred
Tax Type ICMS Deferred
This type must be defined before starting this setup, check the
topic Brazilian Tax Type
Start Date 1/1/2019
Tax Information
198
Tax Precision 2
Compounding Precedence It is necessary inform a higher number than ICMS Normal
199
200
201
TAX ACCOUNTS
Tax Account does not need for tax report.
TAX JURISDICTION
Inform the 27 Brazilian States in the Jurisdiction for the ICMS Normal.
202
DEFINE CALCULATION FORMULA USING ICMS-NORMAL AND ICMS-DEFERRED TAXES
Setup and Maintenance>Manage Tax Formula
1- Change Tax Formula Type to Tax Calculation Formula.

2- Click and Create.
3- Inform the Tax Formula Code and Tax Formula Name.
4- Select ICMS tax regime.
5- Select ICMS-Normal.
6- Change Start Date to older date.
7- Go to Details region.
8- Select ICMS tax regime in the Compound Tax Regime Code field.
9- Select ICMS-Differed in the Compound Tax field.
10- Change to Subtract in the Compounding Rule field.
11- Save.
203
DEFINE ICMS PARTILHA
Define ICMS Partilha Tax for Outbound propose (O2C) inside ICMS Tax Regime. The table below shows detail
information about field in the Tax Cloud.
Tax Header
Tax ICMS-PARTILHA
Tax Name ICMS-PARTILHA
Tax Type ICMS Partilha
This type must be defined before starting this setup.
Start Date 1/1/2019
Tax Information
204
Tax Precision 2
Compounding Precedence If the company has IPI in the sales transactions. It is important
define a compound number lower that IPI
205
206
It can be substituted for a new formula if the company use IPI

in the sales transactions.
207
Note: It is VERY IMPORTANT to define a NET rate for ICMS PARTILHA. Example if the Destination Internal
Rate is 18% and Original Internal Rate is 7% then the net rate must be 12%.
Note: It is REQUERIMENT to define a tax reporting code to inform a Destination Internal Rate for operation.
Check the section “Define Original Rate”.
TAX ACCOUNTS
TAX JURISDICTION
Inform the 27 Brazilian States in the Jurisdiction for the ICMS Partilha.
ICMS RE 574.706
The RE (Recurso Extraordinário) number 574.706 determine that companies can exclude the ICMS Amount in the
fiscal document of taxable basis to calculate PIS and COFINS taxes.
The company only applying this resource if the Government authorized.
In the Outbound process, company that has this authorization can issue the fiscal document and calculate PIS e
COFINS with ICMS exclude in the taxable basis.
However, the company must be check if their supplies were applied the RE#547.706 in the fiscal document, before
calculation the PIS and COFINS without ICMS in the taxable basis.
This topic will explain how to exclude the ICMS tax amount from taxable basis to PIS and COFINS Taxes in the
inbound and outbound process.
ICMS TAX AS REPORT
208
It needs define other ICMS with the field “Set tax for reporting purposes only”. This must calculate together with
“Original” ICMS, but using negatives rates.
Example: Interstate Operation rate 12% for ICMS Report -12%.
FORMULA
Create Taxable Basis Formula to exclude the ICMS Tax Amount from PIS and COFINS. If the company has
scenarios with Reduction Basis in the ICMS (CST-20). It is important define PIS and COFINS formulas using
Reduction Basis Percentage.
Compounding Precedence to New ICMS Report must be lower than PIS and COFINS taxes.
PARTY FISCAL CLASSIFICATION
It needs mapping which suppliers has Government authorization to exclude the ICMS Tax Amount from PIS and
COFINS taxable basis. This classification must be use in the Tax Applicability Rule as determine factor to Tax Cloud
calculated the ICMS Report.
TAX RULES FOR INBOUND
Inbound process will be necessary three rules:
1- Tax Applicability Rule to calculate ICMS Report

2- Tax Rate Rule to determine ICMS Report rates
3- Tax Taxable Basis Rule for PIS and COFINS to exclude the ICMS Report amount. In this rule it is very
important use Party Fiscal Classification as a determine factor to Tax Cloud knows when tax must exclude.
TAX RULE FOR OUTBOND
Outbound process can use two rules
1- Tax Applicability Rule to calculate ICMS Report

2- Tax Taxable Basis Rule for PIS and COFINS to exclude the ICMS Report amount. Here it is not necessary
user a Party Fiscal Classification because the company has Government authorization to exclude the ICMS
Tax Amount from PIS and COFINS taxable basis.
209
IRPF WITH SIMPLIFIED DISCOUNT
Deductions and Changes
To operationalize the new exemption range of R$2,640 announced by the government, the Federal Revenue
Service increased the initial range of the progressive table to R$2,112 and adopted a new simplified deduction
mechanism of R$528.
Thus, with the simplified discount, whoever earns up to R$ 2,640 will not pay any income tax, neither at source
nor in the annual adjustment statement.
As an alternative to deductions, such as social security, dependents, alimony, among others, the taxpayer can
choose to use a simplified monthly discount, corresponding to 25% of the initial range of the progressive table [R$
2,112], that is, R$ 528.
IRPF New Progressive Table:
To meet the new simplified calculation, it will be necessary to create a new Simplified IRPF tax. This new IRPF
Tax will be applied for the suppliers that make the option to apply the Simplified Deduction on its invoices. It is
not a system decision, it is based on supplier decision.
210
A new withholding tax rate must be created with the new progressive table and associated with the new tax:
211
On the Threshold tab, the deduction value of BRL 528.00 must be entered in the MINIMUM VALUE field for the
calculation base, this way, this value will always be deducted from the base to identify the correct range of the
deductions table.
In the THRESHOLD TAXABLE BASIS field, select the option “Amount in excess of minimum value” so that the
amount of R$528.00 can be correctly deducted from the calculation base.
As previously mentioned, the system will NOT decide which deduction is the best for the supplier, so based on
supplier request, if simplified deduction is chosen then a manual classification of the supplier must be made.
Suggestion is to create a supplier classification (ORGANIZATION_TYPE) and build a logic to apply the new IRPF
tax (with the new tax applicability rules IRPF_SIMPLIFICADO), this way the rule can be applied without the need
for manual intervention when entering the Invoice.
212
213
FUTURE TAX RECOVERY FOR FIXED ASSET
When Company can have recovery taxes (ICMS and PIS/COFINS) in Fixed Asset acquisition, it’s possible setup
these total amount of recovery taxes in moment of entry the fiscal document in FDC or AP modules, as Self
Assessed. For details about setup as Self Assessed, please see topic: SELF-ASSESSED TAX -> TAX
REGISTRATION in this document.
This setup is like recovery PIS/COFINS in fiscal document entry, when isn’t is Fixed Asset. For details, please see
topic: SELF-ASSESSED TAX -> PIS AND COFINS RECUP DEFINITION in this document. The control
of future recovery is responsibility of Fiscal Third Party, that has information about instalments quantity the recovery
will occurs.
For recovery ICMS, if inbound fiscal document has the variations about this tax, for example: ICMS DIFAL, ICMS-
ST, FCP and FCP-ST, the tax amount of all taxes must be added in the recovery ICMS calculation using Formula in
Tax Module. About CST, for ICMS always is 90.
For PIS/COFINS, the taxes recovery must be according to the Company Classification, for example: “Lucro Real”.
About CST it’s always 98.
You must use Tax Type Codes specifics for setup of this tax recovery: LACLS_ICMS_FA, LACLS_PIS_FA and
LACLS_COFINS_FA.
When theses Tax Types Codes are in XML of Extractor AP, Fiscal Third Party knows that the invoice has recovery
tax. Another way to identifier if invoice has recovery tax is the setup in Fiscal Party solution.
It’s recommended the use of the specific Recoverable Tax Account, that will have the total amount recovery tax.
For close balances in this account, the user must do manual entries in GL, with recovered tax amount monthly or
when recovery tax total amount was finished (it’s depended on Company accounting/fiscal area). Fiscal Third Party
provide reports monthly that shown recovered tax amount that was sent in Bloco F120/F130 (PIS/COFINS) and
Bloco G (ICMS-CIAP).
DEFINE ICMS TAX RECOVERY IN FUTURE
Define ICMS Tax Recovery in Future for Inbound propose inside ICMS Tax Regime. The table below shows detail
information about field in the Tax Cloud.
Define Tax navigate through:
Setup and Maintenance > Financial > Transaction Tax > Manage Taxes
214
Tax Header
Tax ICMS_FA_FUTURE
Tax Name ICMS_FA_FUTURE
Tax Type LACLS ICMS FA
Start Date 1/1/2019
Tax Information
215
Tax Precision 2
Allow override and entry of inclusive tax lines Null
216
Allow creation of multiple jurisdictions Yes
217
Tax Registration Ship-to party

You must create a Taxable Basis Rule to consider ICMS
variations as: DIFAL, ICMS-ST, FCP and FCP-ST.
218
Tax Recovery Rate Inform appropriate recovery rate to the tax. For example:
ICMS_FA_FUTURE_100%
Tax Rate Inform appropriate rate to the tax. For example:

ICMS_FA_FUTURE_100%
Note: The rate “100%” must be defined in Tax Rate Rule, corresponding to tax amount of all ICMS variations.
TAX ACCOUNTS
TAX Jurisdiction
Inform the 27 Brazilian States in the Jurisdiction for the ICMS Recovery in Future.
DEFINE PIS/COFINS TAX RECOVERY IN FUTURE
Define PIS Tax Recovery in Future for Inbound propose inside PIS Tax Regime. The table below shows detail
information about field in the Tax Cloud for PIS.
For COFINS Tax Recovery in Future, the setup in like this.
Define Tax navigate through:
Setup and Maintenance > Financial > Transaction Tax > Manage Taxes
219
Tax Header
Tax Regime Code PIS
Tax PIS_FA_FUTURE
Tax Name PIS_FA_FUTURE
Tax Type LACLS PIS FA
Start Date 1/1/2019
Tax Information
Override Geography Type BR_ZONE_TYPE_RI
220
Tax Precision 2
221
Allow creation of multiple jurisdictions Yes
222
Validation Level None
Duplicate Validation Level No Validation
Tax Registration Ship-to party
223
Tax Recovery Rate Inform appropriate recovery rate to the tax. For example:
PIS_RECUP_FA_100% / COFINS_RECUP_FA_100%
Tax Rate Inform appropriate rate to the tax. For example:

PIS_RECUP_FA_1.65% / COFINS_RECUP_FA_7.60%
Note: The recovery rate for PIS/COFINS can be variable according with Company setup
TAX ACCOUNTS
224
RETURN TO VENDOR (RTV)
For issuing RTV Fiscal Document, it’s necessary change the inbound CST to outbound CST.
This information considers if LRU is contributor of ICMS and IPI or not. So, it’s necessary include in LRU two
Tax Reporting Codes: ORA_BR_STATE_INSCRIPT_CLASS (for ICMS) and
ORA_JGBR_MFG_PROD_TAXPAYER_CLA (for IPI), according of Company legal requirement. Details
about this setup is in the next topic.
The derivation of inbound CST to outbound CST is applied for all taxes informed in fiscal document and the setup
will be done using Mapping Set UI, as detailed in the next topic.
In the example below, LRU is contributor of ICMS and IPI, in the inbound document the CST of COFINS tax is
06, in the RTV Fiscal Document will be printed CST 00.
Tax ICMS IPI Classification CST inbound CST outbound

Classification
ORA_COFINS ICMS_TAXPAYER ORA_MFG_PROD_TAXPAYER 06 00
Note: Mapping between inbound CST code and outbound CST code, must be realized by the user with
the help of a fiscal consultant, to setup correctly the customer scenarios.
Since 22C ERP Cloud version, FDG released a new XML layout that use this setup for generate tags
<ORIGINAL_CST_CODE> and <CST_CODE_RTV> in group <TAX_LINES>. Details can be found in:
https://www.oracle.com/webfolder/technetwork/tutorials/tutorial/cloud/r13/wn/fin/releases/22C/22C-
financials-wn.htm#F23997
Note: Fiscal partner must use the new tag (<TAX_LINES>.<CST_CODE_RTV>) to generate CST
information in RTV Fiscal Document before send to SEFAZ.
IMPORTANT: For RTV process are be done with successfully, it’s necessary to custom the CMK process. For
more details, please see document in section: Oracle Cloud CMK Setup to optimize Fiscal Document
information in My Oracle Support: Latin America Cloud Local Solution for Brazil (Doc ID 2291252.1)
Note: Customizations in the CMK process are the responsibility/maintenance of the project/customer.
225
CONFIGURE ICMS CONTRIBUTOR AND IPI CONTRIBUTOR IN LRU SETUP
These setups for ICMS and IPI must be doing with the Company legal information.
Note: Must have only one ICMS and IPI classification active by LRU.
ICMS CONTRIBUTOR
Steps to configure ICMS Contributor in LRU:
1- Navigate to Setup and Maintenance and set opt-in to Financials;

2- Navigate through Transaction Tax -> Manage Party Tax Profiles;
3- Select Legal Reporting Unit Tax Profiles option in Search For field, in top of page;
4- Find LRU in Legal Reporting Unit field and click on Search button;
5- Click in Legal Reporting Unit link in Search Result section;
6- Click in Edit button, in top of page, for edit LRU;
7- In tab Tax Reporting Code, click on Add (+) icon;
8- In the new line, select ORA_BR_STATE_INSCRIPT_CLASS in List of Value of the Tax Reporting
Type Code field;
9- In Tax Reporting Code field, select the option for define legal information by Company;
10- Inform the date in Effective Start Date field;
11- Save and Close;
12- Repeat these steps for all LRUs of the Company.
IPI CONTRIBUTOR
Steps to configure IPI Contributor in LRU:

2- Navigate through Transaction Tax -> Manage Party Tax Profiles;
3- Select Legal Reporting Unit Tax Profiles option in Search For field, in top of page;
4- Find LRU in Legal Reporting Unit field and click on Search button;
5- Click in Legal Reporting Unit link in Search Result section;
6- Click in Edit button, in top of page, for edit LRU;
7- In tab Tax Reporting Code, click on Add (+) icon;
8- In the new line, select ORA_JGBR_MFG_PROD_TAXPAYER_CLA in List of Value of the Tax
Reporting Type Code field;
9- In Tax Reporting Code field, select the option for define legal information by Company;
10- Inform the date in Effective Start Date field;
11- Save and Close;
12- Repeat these steps for all LRUs of the Company.
Note: All LRUs must be associated with a Business Unit. (Manage Associated Business Entities Task)
226
CONFIGURE MAPPING SET
Mapping between inbound CST code and outbound CST code must be realized by the user with the help of a fiscal
consultant, to setup correctly the Company scenarios.
Steps to configure CST inbound x CST outbound:

2- Navigate through Revenue Management > Manage Mapping Sets (scope set to “Tax”);
3- Find FDG RTV Tax Situation Codes Mapping field and click on link for edit;
4- Section: Input Sources are filled;
5- In Section: Value Sets, click on Add (+) icon;
6- Select option ORA_JGBR_FDG_CST_CODES in List of Value of field: Value Set;
7- In Section: ORA_JGBR_FDG_CST_CODES: Mappings, click on Add (+) icon;
8- You must include all options of Company, to derivate inbound CST to outbound CST:
a. Inform the tax;
b. Inform ICMS classification of LRU;
c. Inform IPI classification of LRU;
d. Inform inbound CST code;
e. Inform outbound CST code;
f. Inform a start date;
9- Click on the Add (+) button for include new records;
10- Save and Close.
Note: Must have only one valid combination active by Taxes and classification LRU for ICMS and IPI.
Table below shown an example of the setup:
SECTION: Input Sources
Column/Field Description Valid Values
In this field, inform the tax type code, All taxes for Brazil. For example:
Tax Type Code associated for each tax (Value Set: ORA_COFINS
ORA_JGBR_FDG_TAX_TYPE) ORA_PIS
ORA_IPI
ORA_ICMS
In this field, inform the LRU ICMS_TAXPAYER

User-Defined Character 1 classification, referring to ICMS ICMS_NON_TAXPAYER
contribution (Value Set: ICMS_TAXPAYER_EXEMPT_IE
ORA_JGBR_FDG_STATE_TAXPA
YER_CLASS)
227
In this field, inform the LRU ORA_MFG_PROD_TAXPAYER
User-Defined Character 2 classification, referring to IPI ORA_MFG_PROD_NONTAXPA
contribution (Value Set: YER
ORA_JGBR_FDG_MFG_PROD_TA
XPAYER_CLASS)
In this field, inform the inbound CST Values defined by the Brazilian
User-Defined Character 3 codes (Value Set: Government and can be found in the
ORA_JGBR_FDG_CST_CODES – SPEDs manuals, through the tax
Lookup Types: situation code tables for each tax.
ORA_JGBR_FDG_CST_FEDERAL Reference:
ORA_JGBR_FDG_CST_MFG http://sped.rfb.gov.br/arquivo/sho
ORA_JGBR_FDG_CST_STATE) w/1629
SECTION: Value Sets
Column/Field Description Valid Values
In this field, inform the outbound CST Values defined by the Brazilian
ORA_JGBR_FDG_CST_COD codes, that has relation with inbound Government and can be found in the
ES CST codes “FROM/TO CST RTV” SPEDs manuals, through the tax
(Value Set: situation code tables for each tax.
ORA_JGBR_FDG_CST_CODES – Reference:
Lookup Types: http://sped.rfb.gov.br/arquivo/sho
ORA_JGBR_FDG_CST_FEDERAL w/1629
ORA_JGBR_FDG_CST_MFG
ORA_JGBR_FDG_CST_STATE)
SECTION: ORA_JGBR_FDG_CST_CODES: Mappings
Tax Type User-Defined User-Defined User-Defined ORA_JGBR_FDG_ Effective

Code Character 1 Character 2 Character 3 CST_CODES Start Date
ICMS_TAXP ORA_MFG_PROD 06 Inform outbound 1/1/19

ORA_ICMS AYER _TAXPAYER CST that be used
in derivation. For
example: 00
ICMS_TAXP ORA_MFG_PROD 51 Inform outbound 1/1/19
ORA_ICMS AYER _TAXPAYER CST that be used in
derivation. For
example: 01
228
IMPORTATION AND EXPORTATION (GOODS/SERVICES)
This chapter provides a list and description of the steps to define Oracle ERP Cloud for import and export
scenarios related to goods, services, and inbound/outbound fixed assets.
It is very important that the implementor knows that this document has an approach focused on Oracle
Certificated Trading Partner ISVs. If the company does not use an ISV Trading Partner for
importation/exportation scenarios, the implementor must define a project solution approach. Brazilian LACLS
does not support or define a solution without an Oracle Certificated Trading Partner ISV.
IMPORTATION
This topic provides important definitions for working with Oracle Certificated Trading Partner ISVs in Oracle
ERP Cloud. It is important to confirm with the Oracle Certificated Trading Partner ISV some terms and
configurations used by the integration.
229
HOW TO IMPORT GOODS
How to process import of goods:
1- Create a PO in the foreign currency with “Invoice Match Option” field as “Order” and “Product Type”
field as “Goods”
Note: it is no necessary calculate tax in this PO, the Oracle Certificated Trading Partner ISV is
responsible to calculated tax in the import flow
2- Oracle Certificated Trading Partner ISVs consume the PO approved
3- Internal procedures in the Oracle Certificated Trading Partner ISVs
4- Oracle Certificated Trading Partner ISVs create a “Commercial Invoice” in Oracle Payables Cloud as
standard invoice and matched with PO in foreign currency
Note: This transaction does not have tax calculated, the Oracle Certificated Trading Partner ISV is
responsible to calculated tax, but in the Brazilian Fiscal Document (BRL Currency)
Note: The payment for import goods is processed by Oracle Certificated Trading Partner ISV, because
the bank institution requires information about DI (Declaração da Importação) into txt file. The
document in Oracle Payables Cloud is automatic settlement by Oracle Certificated Trading Partner ISV.
5- Oracle Certificated Trading Partner ISVs create a BRL Fiscal Document with taxes calculated. This steps
partner sends the XML to SEFAZ
6- Enter with BRL Fiscal Document using Oracle ERP Job´s
7- BRL Fiscal Document is available in the Oracle FDC Cloud associated with same PO matched in the
“Commercial Invoice” but showing the amounts in the BRL currency, include Brazilian Taxes
8- Confirm item delivered
9- BRL Fiscal document status as “Capture”
10- Execute the “Put away” procedure
11- Execute the jobs bellow:
a. Transfer Transactions from Receiving to Costing (AccrueCostJob)
b. Create Receipt Accounting Distributions (ReceiptAccrualProcessMasterEssJobDef)
c. Check if “Commercial Invoices” was validated and posted
d. Transfer Costs to Cost Management (APCSTTRF)
e. Transfer Transactions from Inventory to Costing (InvCstInterfaceJob)
f. Create Receipt Accounting Distributions
g. Clear Receipt Accrual Balances (AccrualClearRulesMasterEssJobDef)
12- Enter in the Cost Management and execute the “Create cost accounting distributions”, this step must
be run using the screen
13- When cost process is finish run the jobs bellow:
a. Create Accounting (Receipt Accounting)
230
b. Create Accounting (Cost Accounting)
14- Create Cost Adjustments about exchange rate variance, this step is automatic process by Oracle
Certificated Trading Partner ISV.
Note: Exchange Rate Variance in the Projects must be created manually in the system.
15- Finished
231
HOW TO IMPORT SERVICES
Before starting the steps, it is important to know that taxes are not calculate in the “Commercial Invoice”, for
services the taxes must be calculated when the exchange rate was defined to pay in the BRL Amount.
The Taxes will be calculated out of ERP Cloud with manual user procedure based on the BRL Amount
converted.
How to process import of services:
1- Create a PO in the foreign currency with “Invoice Match Option” field as “Order” and “Product Type”
field as “Services”
2- Oracle Certificated Trading Partner ISVs consume the PO approved
4- Create manually a “Commercial Invoice” in Oracle Payables Cloud as standard invoice and matched
with PO with foreign currency
5- Oracle Certificated Trading Partner ISVs process the exchange closing to commercial invoice
6- Oracle Certificated Trading Partner ISVs calculate taxes in BRL Currency and create documents in
Oracle Payables in BRL Currency
Note: These documents are taxes that must be posted and settlement
Note: Settlement is as terms that means pay, but not send to the bank
7- Oracle Certificated Trading Partner ISVs creates a payment to commercial invoice in Oracle ERP Cloud
Note: Exchange Rate Variance between Commercial Invoice and Payment must be created manually
in the Oracle Projects Cloud
8- Create a BRL Fiscal Document for Services (NFSe), manual procedure:
a. Have note the BRL Amount converted to pay the “Commercial Invoice” and the taxes amount
created in Oracle Payables Cloud
b. Create a transaction in Oracle Receivables Cloud, using details below:
- Transaction without posting and open receivables
- Inform the right Service Code (Lei 116) to the city that NFSe is issued
c. Inform manually the BRL Amount for services and taxes
d. Request Fiscal Document
e. Update Fiscal Document and submit to FDG
f. Generate fiscal document to Certificated Fiscal Partners ISV consume and send the fiscal
document to Government.
g. Return Government status by Certificated Fiscal Partners ISV.
9- Finished
232
IMPORT SETUP
The following are the steps involved in setting up and configuring the integration:
1- Source to Oracle Payables Cloud (conditional)

2- Bank Account (required)
3- Payment Process Profile (conditional)
4- Foreign Supplier Address (required)
5- Project (conditional) – required when company has fixed assets importation scenario
6- Active Inventory Organizations for Project (conditional)
7- Payment Terms (required)
8- Cost Elements (required)
9- Cost Lookups (required)
10- Incoterms (required)
11- Define Suppliers Tax Authority to register taxes importation (required)
12- Special Instructions for Accounting
233
SOURCE TO ORACLE PAYABLES CLOUD (CONDITIONAL)
This step is not required if the company does not use an Oracle Certificated Trading Partner ISV and
implementor must be check if the Oracle Certificated Trading Partner ISV creates a commercial invoice
(foreign currency) in the Oracle Payables Cloud, if yes, then implementor must check the right name
defined by Oracle Certificated Trading Partner ISV before to define in the system.
Define a source:
1. Navigate to “Setup and Maintenance”

2. Check or change the functional area to “Financials”
3. Select “Payables” and change information to “All Tasks” in the ‘Show’ field
4. Select “Manage Payables Lookups”
5. Inform “SOURCE” in the ‘Lookup Type’ field and search it
6. Create the new source according with each Oracle Certificated Trading Partner ISV (this step must
be check with trading partner)
Lookup Reference Data Set Display Enabled Start Meaning and

Sequence Date Description
Code
ISV Trading Use the refence data defined in the Null Yes 01-01- ISV Trading Partner
Partner Code project or by Oracle Certificated 2001 Code or Description
Trading Partner ISV
234
BANK ACCOUNT (REQUIRED)
The bank account in the importation and exportation flow must have the option “Multicurrency account”
enable to allow system performs final settlement commercial invoice in the foreign currency.
Applied only if the company uses an Oracle Certificated Trading Partner ISV and the ISV creates a
payment in Oracle Payables Cloud to clear commercial invoices (related to importation flow), the
implementor must define a “Payment Document” for this event. Please confirm with the ISV the specific
terms that must be used in this integration.
General – Payment Documents
Payment Document
Format Define a name for this operation, important inform the ISV Trading Partner
about this name.
First Available Document Inform “Brazilian Bordero Format” or a specific format created in the project
Number for this scenario.
235
PAYMENT PROCESS PROFILE (CONDITIONAL)
The payment for import goods is processed by Oracle Certificated Trading Partner ISV, because the bank
institution requires information about DI (Declaração da Importação) into txt file. The document in Oracle
Payables Cloud is automatic settlement by Oracle Certificated Trading Partner ISV.
Define a Payment Process Profile (PPP) only if an Oracle Certificated Trading Partner ISV creates a
payment in the Oracle Payables Cloud to clear commercial invoices (related to importation flow). This
specific PPP will be used to register the final settlement for importation flow in the Oracle ERP Cloud and
applied only for importation scenarios.
Following steps bellow:

2. Check or change the functional area to “Financials”
3. Select “Payments”
4. Select “Manage Payment Process Profile”
5. Click on ‘Create’
6. Proceed the table information bellow
Payment Process Profile
Name Inform a name can be specific or generic nomenclature for easy comprehension
Code Inform a unique code to PPP
From Date Inform a start date
Payment File Format Select the “Brazilian Bordero Format” or a specific format created in the project
Processing Type Printed
Payment File Send to file
236
Usage Rules
Payment Methods Inform a specific payment method for the operation or a generic payment
method, example: “Wire”
Disbursement Bank Inform the bank account

Accounts
Business Units All or a specific BU defined in the project
Curriencies All
7. Save and Close
237
FOREIGN SUPPLIER ADDRESS(REQUIRED)
Implementor must be import attention to define foreign supplier address
• Country
• Zip Code (CEP)
• State and City
• Tax Registrations
COUNTRY
The field “Country” must have the “real country” related to foreign supplier and it is important to inform
IBGE Code in the Country defined by Brazilian Government. This code is validated by SEFAZ.
ATTENTION: Check if the IBGE CODE for country is defined in the geography before load supplier or
created manually in the system.
ZIP CODE (CEP)
The SEFAZ required that Zip Code must have the format with 8 numbers ‘00000000’. If the foreign supplier
has lass number, it is REQUIRED to complete ZERO in the left side as show in the example bellow:
Supplier ZIP Code 9999 must be defined in the Oracle ERP Cloud as 00009999
STATE AND CITY
In the Oracle ERP Cloud implementor does not define State as “EX” and City as “EXTERIOR”. All Oracle
Certificate ISV Fiscal and Trading Partner have a procedure defined by LACLS to convert this information
in the XML.
IMPORTANT: The CMK process use the “Supplier Name” and “Zip Code” to load the electronic invoice
(XML) into FDC.
TAX REGISTRATION
In the Oracle ERP Cloud implementor must define Tax Registration as bellow:
1- Country: Inform the country origin

2- It is not necessary inform Tax Registration Number
3- Save
238
PROJECT (CONDITIONAL)
When company import a fixed asset, it is required to use Oracle Project Cloud to integrate DANFE or Brazilian
Fiscal Document nationalized into Oracle Fixed Assets Cloud.
Check the high-level flows are compound by:
1- Enter document into “Fiscal Document Capture” using fiscal flow as “Purchased Material Import”
2- Receive and post asset into “Receipt Accounting” (RCV) for expense or inventory
If asset has destination to inventory it is required create and post the item into “Cost Accounting”
3- Integrate asset to Project
4- Capitalize asset into Fixed Assets
5- Finished
COST ELEMENTS (REQUIRED)
The implementor must be check if the Oracle Certificated Trading Partner ISV the name that must be
define for cost elements. This setup will be used to create adjustment to exchange variance rates.
Define a source:

2. Check or change the functional area to “Manufacturing and Supply Chain Materials
Management”
3. Select “Cost Accounting”
4. Select “Manage Cost Elements”
5. Create a cost element using the name informed by Oracle Certificated Trading Partner ISV
6. Save and finished
239
COSTING LOOKUPS (REQUIRED)
The implementor must be check if the Oracle Certificated Trading Partner ISV the name that must be
define for reasons applied in the adjustment to exchange variance rates.
Define a source:

2. Check or change the functional area to “Manufacturing and Supply Chain Materials
Management”
7. Select “Cost Accounting” and change information to “All Tasks” in the ‘Show’ field
3. Select “Manage Costing Lookups”
4. Search for “CST_REASON_CODES”
5. Create a value using the name informed by Oracle Certificated Trading Partner ISV
6. Save and finished
PAYMENT TERMS (REQUIRED)
The implementor must be check with Oracle Certificated Trading Partner ISV the name and procedure to
define payment terms for “Prepayment Importation”.
INCOTERMS (REQUIRED)
The implementor must be defined together with Oracle Certificated Trading Partner ISV the name that must
be used to integrated “Incoterms”. This information must be informed in the “FOB” field locked in the
Purchasing Order.
The names must be defined in the “Manage Standard Lookups”, following steps bellow:
1- Navigate to “Setup and Maintenance”
2- Change setup scope to “Procurement”
3- Go to “Procurement Foundation”
4- Change “Show” field to “All Tasks”
5- Go to Manage FOB Lookup and click on the name
6- Create the name that define with Oracle Certificated Trading Partner ISV
7- Save and Close
240
SUPPLIERS TAX AUTHORITY (REQUIRED)
Some Oracle Certificated Trading Partner ISV (check with partner how do they work with tax integration?), can
generate tax documents in Accounts Payables.
These documents are taxes generated by Oracle Certificated Trading Partner ISV during create a Brazilian
Fiscal Document and automatically debited to the company bank account or the trading company. These taxes
documents can be created in Oracle Payables Cloud to account them in ledger and settlement to register the
payment in the Oracle ERP Cloud.
Important: The tax document is not a DARF it is only a standard document create in Oracle Payable Cloud to
posted taxes related an import flow. Oracle Certificated Fiscal ISV are responsible to create official document
by Government (DARF or GARE).
In this topic, it is suggest defining three suppliers, one for each type of tax (federal, state, and municipal) and
taxes defined as a site.
The table below exemplifies the suggestion:
Supplier as Tax Authority
Supplier Name Secretaria Federal da Fazenda
Alternative Name Federal
Supplier Name Secretarias Estaduais da Fazenda
Alternative Name Estadual
Supplier Name Secretarias Municipais da Fazenda
Alternative Name Municipal
Supplier as Tax Authority Common Configuration
Tax Organization Type Government Agency
241
Supplier Type Tax Authority
242
Addresses Suggestion
Define a unique address for Secretaria Federal.
Address for Secretaria Federal da Fazenda
Address Name Address
DF Setor de Autarquias Sul,Quadra 06,Ed. Órgãos centrais Bloco O,ASA SUL,70070-

900,DF,BRASILIA
Define how many addresses the company pay state taxes.
Address for Secretarias Estaduais da Fazendas
SFE-AL Praça dos Palmares, s/n, Centro, 57020-000, AL, MACEIO
SFE-ES Avenida Jerônimo Monteiro, 303, Centro, 29010-020, ES, VITORIA
SFE-RJ Av. Presidente Vargas, 670, Centro, 20071-001, RJ, RIO DE JANEIRO
SFE-SP Av. do Estado, 3700, Bela Vista, 01310-200, SP, SAO PAULO
243
Define how many addresses the company pay city taxes.
Address for Secretarias Estaduais da Fazendas
SMF-GUARULHOS Rua Américo Brasiliense, 800, Centro, 07023-000, SP, GUARULHOS
SMF-MACEIO Rua Dr. Pedro Monteiro,,47,CENTRO,57020-350,AL,MACEIO
SME-RIO DE JANEIRO Rua Afonso Cavalcanti, 455,Cidade Nova,20211-110,RJ, RIO DE JANEIRO
SME-SANTOS Praça Antônio Teles, 28, Centro, 11010-020, SP, SANTOS
SMF-VITORIA Rua João da Cruz, 250,Centro, 29010-000, ES, VIT0RIA
Sites Suggestion
The recommendation to define one site for each tax, example for Federal Taxes:
Secretaria Federal da Fazenda
Procurement BU Site
Procurement BU Name A CIDE
Procurement BU Name A IRPJ
Procurement BU Name A II
Procurement BU Name B CIDE
Procurement BU Name B IRPJ
Procurement BU Name B II
244
The recommendation to define one site for each tax, example for State Taxes:
Secretarias Estaduais da Fazendas
Procurement BU Site
Procurement BU Name A ICMS-SP
Procurement BU Name A ICMS-RJ
Procurement BU Name A ICMS-AL
Procurement BU Name B ICMS-SP
Procurement BU Name B ICMS-ES
The recommendation to define one site for each tax, example for City Taxes:
Secretarias Municipais da Fazenda
Procurement BU Site
Procurement BU Name A ISS-GUARULHOS
Procurement BU Name A ISS-SANTOS
Procurement BU Name A ISS-MACEIO
Procurement BU Name B ISS-RIO DE JANEIRO
Procurement BU Name B ISS-SANTOS
Procurement BU Name B ISS-VITORIA
245
The Brazilian LACLS team strongly recommends the use of the specific "Payment Method", "Payment Group",
"Payment Terms" and "Payment Priority" resources only for the Importation Process, ensuring the system
clearance of the associated taxes and isolating them from other tax payments.
Note: As mentioned before, these taxes should only be recorded in the ledger, as the payment has already
been made in the Importation Process.
SPECIAL INSTRUCTIONS FOR ACCOUNTING
This topic provides a detailed overview of two different methods to account Brazilian taxes in the Importation
Flow.
1- Using clearing accounting:
- Taxes: there is a strongly determination to define specific rates to inform a “liability import clearing
account” in the “Liability Account” field, related to Importation Flow. Inform the same cleating
accounting importation for taxes that are part of the flow.
- Tax Authority (suppliers): assign a “tax liability account” for each tax authority site.
- Transactions: When the Oracle Certificated Trading Partner ISV import tax documents to be registered
in the Oracle Payables Cloud it must inform the “liability import clearing account”.
2- Without clearing accounting:
- Taxes: define a rate for Importation Flow and inform specific “tax liability account” for each tax
generated in the flow.
- Tax Authority (suppliers): assign a “general liability account” for each tax authority site
in the Oracle Payables Cloud it must inform the “expense import account”.
246
EXPORTATION FLOW
This topic provides important definitions for working with Oracle Certificated Trading Partner ISVs in Oracle
ERP Cloud. It is important to confirm with the Oracle Certificated Trading Partner ISV some terms and
configurations used by the integration.
HOW TO EXPORT GOODS
How to process export goods:
1- Create a sales order in Oracle Order Management Cloud using a foreign currency and specific “Order
Type” that stops in the “Shipping Confirm”.
Note: The Sales Order cannot calculate taxes, this is a workaround to FDG creates a empty XML and
Oracle Certificated Fiscal ISV does no consume data to generated a wrong BR Fiscal Document
There is an idea to solve this workaround. Idea#: 666228
2- Inform “LACLS_BR_EXPORTATION” in the “Fiscal Document Classification” to system does not
calculate taxes in the Sales Order for Export Goods
3- Submit Sales Order to approval
4- Realized shipment procedures
5- Request Fiscal Document
6- Update Fiscal Attributes
7- Generate Fiscal Document
8- Send to Tax Authority
9- Approved manually the Fiscal Document
10- Finalized with the Ship Confirmed
Note: This document will not be integrated in Oracle Receivables Cloud
11- Oracle Certificated Trading Partner ISVs consume the Sales Order and Shipment approved
13- Oracle Certificated Trading Partner ISVs create the Fiscal Document (FD) in BRL Currency in the Oracle
Receivables Cloud.
Important to know:
- This document will be processed in normal fiscal flow with Oracle Certificated Fiscal ISV
Partners
- The transaction type used in the FD is not posted and billed
247
14- Oracle Certificated Trading Partner ISVs create a “Commercial Invoice” in Oracle Receivables Cloud in
foreign currency
Important to know:
- The transaction type used in the operation is posted and billed.
15- Oracle Certificated Trading Partner ISVs create a receipt when the customer paid the commercial
invoice and settlement the foreign transaction
16- Finished
248
HOW TO EXPORT SERVICES
Export Services using Oracle Project Cloud is out of scope.
How to process export services:
1- Export with Sales Order

a. Create an order with transaction type defined to not use shipment and goes directly to AR.
b. In the details line select the “Tax Determinants” and inform the “LACLS_BR_EXPORT_SERV”
in the “Document Fiscal Classification” field.
Note: The “LACLS_BR_EXPORT_SERV” must be informed in the sales order, because the
transaction will not be processed by FDG.
c. This sales order cannot be tax calculated, because Oracle Certificated Trading Partner ISVs
will calculate in the Brazilian Fiscal Document (BRL Currency).
2- Export without Sales Order
a. Create a transaction in Oracle Receivables Cloud using a foreign currency code and
“Transaction Type” that will be post and bill.
b. Go to “Miscellaneous” and inform “LACLS_BR_EXPORT_SERV” in the “Document Fiscal
Classification”.
Note 1: The “LACLS_BR_EXPORT_SERV” must be informed in the sales order, because the
transaction will not be processed by FDG.
Note 2: There is no need inform Service Code (Lei 116).
c. This transaction cannot be tax calculated, because Oracle Certificated Trading Partner ISVs
will calculate in the Brazilian Fiscal Document (BRL Currency).
d. Complete the foreign transaction.
3- Oracle Certificated Trading Partner ISVs consume transaction in the Oracle Receivables Cloud,
included the transaction created by sales order.
4- Oracle Certificated Trading Partner ISVs create a receipt when the customer paid the commercial
invoice and settlement the foreign transaction
5- Finished foreign transaction.
6- Create a manual transaction in Oracle Receivables Could using a BRL Currency and a “Transaction
Type” that won´t be posted and billed.
7- The fiscal document amount must be the same functional receipt amount created by Oracle
Certificated Trading Partner ISVs.
Note: The taxes applied in this fiscal document must be ZERO and using correct CST for PIS and
COFINS.
8- Finished.
249
EXPORT SETUP
TRANSACTION SOURCE (REQUIRED)
The correct nomenclature and how the source should be configured must be verified with the Oracle
Certificated Trading Partner ISV by the implementer.
Navigate through:
1- Setup and Maintenance and check or select Financials setup
2- Go to Costumer Billing in the “Functional Areas”, change to “All Tasks”
3- Select “Manage Transaction Sources”
4- Create the source and saved
250
TRANSACTION TYPE (REQUIRED)
Transactions are required
Goods:
• A transaction type that must open the Accounts Receivable account and account for the commercial
invoice in the foreign currency converted to the functional currency of the accounting ledger.
Services:
• A transaction type that must open the Accounts Receivable account and account for the commercial
invoice in the foreign currency converted to the functional currency of the accounting ledger.
For Both:
• A transaction type that does not open the Accounts Receivable and does not even account for the
operation. This configuration should only be used to generate the XML in the FDG in the functional
currency so that the Oracle Certificated Fiscal ISV can consume and prepare the standard SEFAZ XML.
Navigate through:
2- Go to Costumer Billing in the “Functional Areas”, change to “All Tasks”
3- Select “Manage Transaction Types”
4- Create and saved
251
DOCUMENT FISCAL CLASSIFICATION (REQUIRED)
The nomenclature used for this topic must be consistent with the nomenclature defined below:
Document Fiscal Classification Code
Code Name
LACLS_BR_EXPORT_SERV LACLS_BR_EXPORT_SERV
LACLS_BR_EXPORTATION LACLS_BR_EXPORTATION
Navigate through:
2- Go to Transaction Tax in the “Functional Areas”, change to “All Tasks”
3- Select “Manage Transaction-Based Fiscal Classifications”
4- Change the option default “Search for” to “Document Fiscal Classification Codes”
5- Click on “Create Level 1 Node”
6- Inform the name, displayed in the table above
7- Inform “Brazil” in the field Country
8- Define a Start Date
9- Save
Reason to define these two types:
LACLS_BR_EXPORT_SERV: this classification code is used to disable the FDG. It must be provided in the
transaction that represents the commercial invoice in foreign currency for the export of services.
LACLS_BR_EXPORTATION: This classification code will be used to define the issuance of an invalid fiscal
document, meaning that it will not be a real fiscal document. This code will serve for the Oracle Certificated
Trading Partner ISV to recognize that the series defined in Oracle ERP Cloud will not be used for fiscal
document integration. This classification code must be use in Sales Order for Export Goods to ensure that
taxes is not calculate in this transaction.
252
MANAGE A NO VALID DOCUMENT NUMBERING (REQUIRED)
This setup procedure is a workaround and must be used until new feature available in FDG. Define a no valid
document numbering when company sales goods exportation.
Note: There is a idea number about this topic Idea#: 666228.
Steps:
2- Go to “Tasks”, icon located in the right
3- Select “Search”
4- Inform “Define Configuration for Regional Localization” and search
5- Click on “Define Configuration for Regional Localization”
6- Click on “Manage Localization Document Numbering”
7- Click on “Create”
Create Fiscal Document Sequence
Field Name Information
Legal Entity Legal entity name
Legal Reporting Unit Subsidiary name
Series Create a unique no valid series that must be used to exportation invalid flow
Series Inform a unique information can be number or description,

example 001387-Exp
Note: final number from CNPJ
Series Description Inform a description, example 001387-Export
253
Model Any information
Printing Format null
Sequence No valid sequence that must be used to exportation invalid flow
Start Date Keep the current system date
8- Save
254
MANAGE NO VALID FISCAL DOCUMENT GENERATION CONTROLS FOR BRAZIL (REQUIRED)
This setup procedure is a workaround and must be used until new feature available in FDG. Define a no valid
document generation when company sales goods exportation.
Note: There is a idea number about this topic Idea#: 666228.
Steps:
2- Go to “Tasks”, icon located in the right
3- Select “Search”
4- Inform “Define Configuration for Regional Localization” and search
5- Click on “Define Configuration for Regional Localization”
6- Click on “Manage Fiscal Document Generation Controls for Brazil”
7- Click on “Create”
Manage Fiscal Document Generation Controls for Brazil
Event Class Sales order shipment
Business Unit Select the BU
Document Fiscal Inform LACLS_BR_EXPORTATION

Classification
8- Save
PROFILE JL_ENABLE_FEATURE (REQUIRED)
Lookup code to enable FDG to generate document in foreign currency.
ORDER TYPE (REQUIRED)
Goods:
255
Define an Order Type in the Oracle Order Management Cloud only to finish the process in the Shipment. The
Oracle Certificated Trading Partner ISV is responsible to create a Commercial Invoice in the Oracle Receivables
Cloud.
Services:
Define an Order Type in the Oracle Order Management Cloud only to billing, that means jump the Shipment
process and create a transaction in Oracle Receivables Cloud.
BANK ACCOUNT (REQUIRED)
Enable “Multi Currency” and the bank account to receive the export commercial invoices.
FOREIGN CUSTOMER ADDRESS(REQUIRED)
Implementor must be import attention to define foreign customer address
a. Country
b. Zip Code (CEP)
c. State and City
d. Tax Registrations
COUNTRY
The field “Country” must have the “real country” related to foreign customer and it is important to inform
IBGE Code in the Country defined by Brazilian Government. This code is validated by SEFAZ.
ATTENTION: Check if the IBGE CODE for country is defined in the geography before load supplier or
created manually in the system.
ZIP CODE (CEP)
The SEFAZ required that Zip Code must have the format with 8 numbers ‘00000000’. If the foreign customer
has lass number, it is REQUIRED to complete ZERO in the left side as show in the example bellow:
Supplier ZIP Code 9999 must be defined in the Oracle ERP Cloud as 00009999
STATE AND CITY
In the Oracle ERP Cloud implementor does not define State as “EX” and City as “EXTERIOR”. All Oracle
Certificate ISV Fiscal and Trading Partner have a procedure defined by LACLS to convert this information
in the XML.
256
TAX REGISTRATION
In the Oracle ERP Cloud implementor must define Tax Registration as bellow:
1- Country: Inform the country origin

2- It is not necessary inform Tax Registration Number
3- Save
257
SPECIAL INTRUCTIONS TAXES FOR IMPORT AND EXPORT FLOW
Existing tax rules in Oracle Tax Cloud should be reviewed and may need to be modified to trigger tax calculation
based on the operation performed in Oracle ERP Cloud.
In this context, the term "operation" refers to transactions of purchases or sales within the domestic market
(Brazil) or outside the domestic market. Therefore, if a company performs operations both within and outside
the national market, the "Tax Rate Rules" or "Tax Applicability Rules" should consider geography as a
determinant of tax calculation triggering.
This chapter approaches a suggestion to define tax rules for Import Flow and Export Flow, split into two
different topics.
Note: It is important to remember that the tax rules described in this chapter are only a suggestion for defining
tax rules in Oracle Tax Cloud. Implementers have the right to define other taxable rules as needed to meet the
company's operational requirements.
Here the list of major taxes applied in the Import/Export flow:
- ICMS
- IPI
- PIS/COFINS
- II/IOF
258
TAXES FOR IMPORT FLOW
PIS AND COFINS TAXES FOR IMPORT FLOW
Recovery PIS and COFINS cannot be Self-Assessed for import flow. This type of taxes is created in the Oracle
Payables Could and the fiscal document for import does not migrate to this system.
Oracle Receiving Cloud is responsible to post the taxes, this the ways that Oracle ERP Cloud recovery taxes in
the import flow.
TAXES FOR IMPORT FLOW
This flow requires some consideration before defining a tax rule:
- The first point is about the accounting method that the company needs to use to post journals to the
ledger
- The second point is about the CST code and non-inclusive tax
Below provides an overview of two different accounting methods that can be applied in the Import Flow.
1- Using clearing accounting:
- Taxes: there is a strongly determination to define specific rates to inform a “liability import clearing
account” in the “Liability Account” field, related to Importation Flow. Inform the same cleating
accounting importation for taxes that are part of the flow.
- Tax Authority (suppliers): assign a “tax liability account” for each tax authority site.
in the Oracle Payables Cloud it must inform the “liability import clearing account”.
2- Without clearing accounting:
- Taxes: define a rate for Importation Flow and inform specific “tax liability account” for each tax
generated in the flow.
- Tax Authority (suppliers): assign a “general liability account” for each tax authority site
in the Oracle Payables Cloud it must inform the “expense import account”.
259
The LACLS Brazil recommend defining specific rates to meet the import flow. The table below shows the
definitions that must be applied to all rate taxes:
Define Tax Rate
Tax Rate Code Name of tax rate used to Import Flow, example:
PIS_CST_70_IMPORT
COFINS_CST_70_IMPORT
ICMS_CST_40_IMPORT
IPI_CST_02_IMPORT
II_IMPORT
IOF_IMPORT
Tax Rate Type Percentage
Rate Percentage For all rates MUST BE ZERO
Rate Period Name Same names describe in the “Tax Rate Code” field
Tax Inclusion Method Standard noninclusive handling.
Maybe company has a specific tax inclusive in the import flow, so in this
case the rate must be defined as “Special inclusive handling”
Allow override and entry of Yes

inclusive tax lines
Allow ad hoc tax rate Yes
260
Accounting Define GL accounting according company requirements.
Tax Reporting Code Define CST Code related to Import Flow
261
TAX RULE FOR IMPORT COMMERCIAL INVOICE
The implementor must define two “Tax Applicability Rule” one to calculate taxes and another with a high priority of other taxes to not calculate taxes to foreign
suppliers in Oracle Payables Cloud.
TAX APPLICABILITY RULE
1- Inbound: define “Standard Invoices” in the “Event Class” field
Geography Ship from Country Not equal to determining factor Ship to
Transaction input factor null Transaction Business Category Equal to PURCHASE_TRANSACTION
Transaction generic Level 1 Product Type Is not blank

classification
2- Define “Not Applicable” in the field “Result”
Note: This rule must be defined for ICMS, IPI, PIS, COFINS II and IOF. It is important not calculate tax in AP for commercial invoices.
Define a “Tax Rate Rule” to apply the rates above. LACLS Brazil recommend using the following determinants:
1. Inbound: define “Purchase Transaction” in the “Event Class” field.
Geography Ship from Country Not equal to determining factor Ship to
Transaction generic Level 1 Product Type Equal to Goods

classification
2. Inform the right rate for Import Flow and the “Result” field.
263
TAXES FOR EXPORT FLOW
SALES ORDER WITHOUT TAXES
Below are some considerations that system does not calculate tax in sales order:
1. LACLS Brazil does not recommend calculate tax in the foreign transaction, because taxes are
calculated by Oracle Certificated Trading Partner ISV.
2. The Sales Order for Export Goods cannot calculate taxes, this is a workaround to FDG creates an
empty XML and Oracle Certificated Fiscal ISV does no consume data to generate a wrong BR Fiscal
Document.
There is an idea to solve this workaround. Idea#: 666228
Create a “Document Fiscal Classification” that must be use for Export Goods. Procedure describes in the topic
“Document Fiscal Classification” in this document
TAXES FOR EXPORT FLOW
The Brazilian Government release the tax calculation for exportation, but it is requiring inform CST in the fiscal
document generate in BRL currency.
The table below shows the definitions that must be applied to all rate taxes in the export flow:
Define Tax Rate
Tax Rate Code Name of tax rate used to Import Flow, example:
PIS_0%_07
COFINS_0%_07
ICMS_0%_40
IPI_0%_42
Tax Rate Type Percentage
Rate Percentage For all rates MUST BE ZERO

Rate Period Name Same names describe in the “Tax Rate Code” field
Tax Inclusion Method Special Inclusive handling
Allow override and entry of Yes

inclusive tax lines
Allow ad hoc tax rate Yes
Accounting Define GL accounting according company requirements.
Tax Reporting Code Define CST Code related to Export Flow
265
TAX RULES FOR SALES ORDER WITHOUT TAX
The implementor should define a “Tax Applicability Rule” using the same determining factor and condition bellow:
1- Outbound: define “Sales Transaction” in the “Event Class” field
Geography Ship to Country Not equal to determining factor Ship from
Transaction generic Null Product Type Equal to Goods

classification
Transaction input factor null Document Fiscal Classification Equal to LACLS_BR_EXPORTATION
2- Define “Not Applicable” in the field “Result” for “Tax Applicability Rule”
Note: Be sure that this rule for sales order has the low priority for next “Tax Applicability Rule”
TAX RULE FOR EXPORT BRL FISCAL DOCUMENT
The implementor should define a “Tax Applicability Rule” and “Tax Rate Rule” using the same determining factor and condition.
TAX APPLICABILITY RULE
1- Define a rule with “Sales Transaction” in the “Event Class” field
2- Use the recommendation bellow:
Transaction input factor null Transaction Type Equal to Transaction Type name
defined for exportation

classification
3- Define “Applicable” in the field “Result” for “Tax Applicability Rule”
4- Enable rule
5- Submit
267
TAX RATE RULE
1- Define a rule with “Sales Transaction” in the “Event Class” field
2- Use the recommendation bellow:
Transaction input factor null Transaction Type Equal to Transaction Type name
defined for exportation

classification
3- Define the rate code for the tax in the field “Result” for ““Tax Rate Rule”
4- Enable rule
5- Submit
6- Finished
268
DOING TRANSACTION
This topic shown the main processes jobs that should be ran to entrance a fiscal document in the
Oracle ERP Cloud.
• Entrance fiscal document in the FDC

o Manual Entrance
o Electronic Entrance
FISCAL DOCUMENT CAPTURE ENTRANCE
A fiscal document is captured automatically using an XML import process or captured manually. This
process of capturing the fiscal document information is closely related to the business flow of the
receiving, shipping (for in transit receipts), and inventory management applications.
MANUALLY ENTRANCE
You can enter a fiscal document manually in FDC (without a XML associated). To do that, you need
to provide all the main information necessarily to process the document.
Navigation: Supply Chain Execution => Fiscal Document Capture
In the Fiscal Document Capture work area, in the Fiscal Document tasks panel drawer, select ”Manage
Inbound Fiscal Documents”
On the Fiscal Document Capture page, click the Add icon
In the Header infolets, provide the required information. Based on the fiscal document information you
are recording, select a fiscal flow (as described below).
Standard Flows:
• Standard - Select this option for creating fiscal documents involving goods or services that may not match
purchase orders and may contain transactions that may not involve payments.
• Standard Complementary - Select this option for creating complementary fiscal documents for standard
fiscal documents involving goods or services that may not match purchase orders and may contain
transactions that may not involve payments.
• Bookkeeping - Select this option for creating fiscal documents involving fiscal flows that do not match
purchase orders or shipments and the fiscal documents are captured only for fiscal reporting purposes
Drop Shipment Flows:
• Drop Shipment Remittance - Select this option for creating fiscal documents involving drop shipment
remittances that match fiscal documents.
• Drop Shipment Sales - Select this option for creating fiscal documents involving drop shipment sales,
where the fiscal document includes goods or services that match purchase orders and contains transactions
that may involve payments.
• Drop Shipment Sales Complementary - Select this option for creating complementary fiscal documents
for fiscal documents involving drop shipment sales, where the fiscal document includes goods or services
that match purchase orders and contains transactions that may involve payments.
You can create a complementary fiscal document for recording additional changes to an existing fiscal document.
Freight Acquisition Flows:
• Freight Acquisition - Select this option for creating fiscal documents involving freight services that are
issued by a service provider.
• Freight Acquisition Complementary - Select this option for creating complementary fiscal documents for
fiscal documents involving freight services.
You can create a complementary fiscal document for recording additional changes to an existing fiscal document.
Internal Transfer Flow:
• Internal Transfer - You can capture internal transfer information in fiscal documents
Import Goods Flow:
• Import Material by Internal Transfer - You can import goods from the overseas branch organization to
your organization within Brazil for self-use or to be delivered to your customer organization
Goods Return Flows - Return Material Authorization:
• Material Returned by Seller - Create fiscal documents involving return of goods from sellers.
• Material Returned by Customer - Create fiscal documents involving return of goods from customers.
Based on the requirement select an infolets and provide information, once the required information is recorded,
click Save and Close.
To provide information in the Lines infolets, provide details of the line items regarding item, purchase (when
applicable), schedules (when PO applicable), and taxes.
A single fiscal document can have multiple PO schedules from a supplier shipping to a same ship to location
Click in the ADD button to insert the item line information. You can have receipts with or without a PO associated.
For receipt with PO, the required fields are:
• Document type – Select here Purchase Order if your receipt will have a PO associated, or No Source if don´t;
• Source Document BU (where the PO is placed) – Inform the BU (Business Unit) where the PO comes
from;
270
• Item – the Item code of the PO
• Type – Goods or service, depends on the nature of you item
• Quantity – Invoice Item Quantity
• UOM – unit of measure of the item in the invoice
• Unit Price – unit price of the item in the invoice
Based on the information above, the system will afford the POs that are available and eligible to be received of that
supplier and items you informed in the receipt line.
Click in the ADD button to select the POs and Schedules that will be associated with this line. (As mentioned before,
you can have multiple POs schedules for the same supplier to the same ship to location).
Enter the PO number, line number and schedule number and allocate the quantity you need to match with the fiscal
document line.
Charge lines include supplier charges paid by the supplier and billed to the buying organization. You can capture the
total amount of supplier charges shown in the fiscal document and then proportionately allocate the charge amounts
to the individual items in the fiscal document using item material amount as the allocation basis.
The freight information includes carrier waybill number and carrier vehicle plate number and whether International
Commercial Terms (INCOTERMS) are free on board (FOB) or Cost, Insurance, and Freight (CIF).
Supplier charges are taxable and are added to the material cost of the item. The summed amount of material and
supplier charges equals the tax basis of the item on which some taxes are calculated. Usually charges only include
freight charges.
To provide information on charges, provide the required information. Allocate charges manually or keep default
value as calculated by the supplier and validate taxes.
271
Other documents include referenced fiscal documents and legal documents. When additional changes are required
in a fiscal document, you can create a complementary fiscal document to record these additional changes. While
creating this complementary fiscal document, you can reference the earlier fiscal document and this reference is
recorded as a referenced fiscal document.
To provide information on other documents infotile, provide the required information. Include all the legal
transactions that are associated with this fiscal document in the legal processes. Include referenced fiscal document
information here.
After entering all the information related to the fiscal document item line, you can (when applicable) calculate the
taxes that needs to be reflected in the document. To do that, click in Actions and then click VALIDATE FISCAL
DOCUMENT. After validating all the information, system will release the function Calculate taxes.
If any taxes rule were identified by the system, you can ask FDC to do it. Click in Actions again and then click in
CALCULATE TAX.
Several aspects of a fiscal document are validated. The validation activity detects the process and type of fiscal
document and based on the expected behavior captured from the process options entity, a series of validations are
performed on the fiscal document. This activity includes validation for data integrity, price and quantity tolerances.
Based on the validation, price and quantity holds on the fiscal document are generated. Information is gathered on
tax calculation and returns that can generate tax holds on the documents. Validation also sets the fiscal document's
status. When necessary, you need to manage the system errors and holds, to perform that, click in Actions and then
click in View Validation Errors.
With the fiscal document validated, you need to Confirm Item Deliveries in order to have your fiscal document captured
by FDC and released to all the other modules integrations.
To record item deliveries, click Actions and Validate deliveries, and in the confirmation message click OK. This
action starts the fiscal document validation activity, which validates the delivered quantities entered against the
tolerance rules defined and other validation parameters. Click Save and Close.
The status of your fiscal document should be Captured at this point and time
272
ELECTRONIC ENTRANCE
The electronic entrance of the fiscal document in FDC occurs through the XML import process. It´s necessary to
upload in Oracle Cloud environment the files sent by the suppliers to be process in FDC.
For that, you need to create the files in the right place in the system:
1- Insert the XML into the system

2- Navigation: Tools>File Import and Export
3- Click on the ADD (+) button to upload the XML in the directory. Browse your file and click in Save and
Close.
Note: IMPORTANT! Your file must be browsed from a main directory tree, otherwise the system will not
recognize it as a valid directory.
The XMLs MUST be placed at the Account: scm/BrazilSEFAZSupplierMessages/import. FDC is expecting to find the
files exactly here.
Once placed the file, it will be necessary to run two processes in order to import the XMLs to FDC final tables/pages.
Run the import process to input the information as follow:
1- Navigation: Tools>Schedule Processes

2- Click on Schedule New Process button, and then search for the Import Brazil Electronic Documents job.
Note: This job doesn´t have any parameters! So just click on OK button !
After running the Import Electronic Fiscal document, to affort the xml file in the FDC pages it´s necessary to run the
Import Brazil Electronic Documents.
You can run this job for every XML uploaded or fill the parameters in order to control witch Supplier you want to
run the process.
If everything runs fine, you will be able to find your fiscal document in the Fiscal Document Capture workplace with the
status as NEW.
273
Manage the fiscal document uploaded
Click on the fiscal document link to open it and review it is content.
It´s important to mention that, in order to have everything loaded automatically, some assumptions must be
consider:
• Supplier register must be valid

• Purchase order must be with OPEN status and have the invoice match option with RECEIPT
• The supplier item cross reference MUST be done
• Tax rules should be defined
All Infolets should have been filled automatically: header, lines, charges and so on. When needed, you can complete
the information imported, such as any tax determinant, accounting combination (for freight fiscal document).
After reviewing all the necessary information, you should be able to validate the fiscal document, check and release
all holds and confirm the items deliveries.
MANAGE INTERFACE EXCEPTIONS
Exceptions can include deviations in quantity, price, taxes, general attributes, and other fiscal attributes.
The Fiscal Document Capture page with the View drop-down list set to Interface Exceptions, lists all the discrepancy
available for review and reconciliation, errors found by preprocessing validation, and errors found in the fiscal
document import process are listed here. You can resolve these exceptions automatically or through manual
intervention.
To view interface exceptions, do the following:
In the Fiscal Document Capture work area, in the Fiscal Document tasks panel drawer, select Manage Interface
Exceptions.
In the Fiscal Document Capture page, list of fiscal documents with exceptions are listed. Correct everything needed
and save it.
The status should be MODIFIED.
Back to the Schedule Process and re-run the Import Brazil Electronic Documents job. Check the FDC workplace to find
out the fiscal document imported.
274
MAIN PROCESS JOB
This topic explains the main processes that must be executed to integrate and processing data to entrance fiscal
document in the ERP Cloud.
1. Import Brazil Electronic Documents: load the fiscal document XML to FDC Interface
2. Import Electronic Fiscal Documents: import fiscal document XML to FDC
3. Put Away: delivery item to inventory organization
4. Transfer Transactions from Receiving to Costing: transfer transaction to be accounting cost
5. Create Receipt Accounting Distributions: create accounting distributions for Receiving transactions
6. Validate and Posting Payables Transactions: complete transaction payables
7. Transfer Costs to Cost Management: transfer Payables Transactions to be accounting cost
8. Transfer Transactions from Inventory to Costing: transfer Inventory Transaction to be costing
9. Create Receipt Accounting Distributions: run these processes one more time to update transactions
10. Create cost accounting distributions: create accounting distributions for Costing transactions
This process MUST BE run in the Cost Account UI
11. Create Accounting for Receipt and Cost to transfer transactions into General Ledger
12. Finish
275
SCENARIOS
This topic shows five scenarios tested and validated by Localization Brazilian Team as examples:
• Resales with PIP not ICMS ST

• Consumption with IPI
• Freight Acquisition (CTe)
• Fixed Asset not IPI
• Consigned
RESALES WITH IPI NOT ICMS ST
FDC main page and transaction line 2 represents the resales operation.
Taxes from transaction line 2
276
ICMS Rules
IPI Rules
COFINS RECUP Rules
277
COFINS COST Rules
PIS RECUP Rules
PIS COST Rules
278
IPI REP Rules
279
CONSUMPTION WITH IPI
FDC main page and transaction line 1 represents the consumption operation.
ICMS Rules
IPI Rules
280
FREIGHT ACQUISITION (CTE)
This CTe shows as reference the fiscal document used in the examples above, FD number 08157.
CTe taxes
281
PIS RECUP
PIS COST
COFINS RECUP
282
COFINS COST
283
FIXED ASSET NOT IPI
ICMS
DIFAL
284
CONSIGNED
More information about Consigned Flow check the note Procure to Pay for Brazil (Doc ID 2347415.1), available in
My Oracle Support.
FD1: entrance of consignment material in the company.
285
ICMS
IPI
FD3: entrance of sales material based on FD1 and FD2
286
PIS RECUP
PIS COST
COFINS RECUP
COFINS COST
287
FREQUENTLY ASKED QUESTIONS (FAQ)
This topic has a set of frequent questions and answers found through during implementations.
HOW TO VIEW AN XML FILE STRUCTERED?
Install the software “Notepad++” in the computer. For Oracle employees you can find it in My Desktop.
Open it and go to “Plugins>Plugins Admin>Search to XML Tools and Install.
WHAT ARE A DIFERENCE BETWEEN SPECIAL INCLUSIVE AND STANDARD INCLUSIVE T AX?
There are three different tax inclusion method in Oracle ERP Cloud.
• Standard non-inclusive handling: This option calculates the taxes as exclusive of the given
transaction line amount.
• Special inclusive handling: This option calculates the taxes as inclusive of the given transaction
line amount, but the calculation methodology differs from the standard inclusive process.
• Standard inclusive handling is not applied to Brazil.
SHOULD “TIME ZONE” NEEDS TO BE DEFINED IN THE LEGAL ADDRESS?
It is requirement to define a time zone in the legal address to avoid issues in the import XML through FDC.
HOW TO HAVE A CORRECT ACCOUNTING FOR AN EXPENSES OR SERVICES PO ?
When the FDC is enabled, the receiving has a modified behaver, and starts receiving only through FDC.
For inventory items, the correct accounting occurs in the receipt transaction (put way-FDC).
For items of expenses or services that do not enter through the FDC, it is necessary that when creating a
PO, the “Receipt Close Tolerance Percent “field, located in the “Schedules” section, must be 100%. This
way the receiving action is not necessary, because the line is automatically closed when the entrance is
done by AP.
When AP finds this PO definition, the system creates the amount value directly to the expense account
informed in the PO (accrual account).
WHY IS PURCHASE ORDER NOT SHOWN IN FDC?
Change the “Invoice Match Option” field to “Receipt” value instead of “Order”.
288
WHY TAXES IS NOT BEEN CALCULATED IN THE ERP CLOUD?
Check the level of the party. The default level is Business Unit but can be changed by Legal Entity. This
information can be checked in the Manage Party Tax Profiles.
WHY ICMS TAX OR ISS TAX DOES NOT CALCULATED IN THE T RANSACTIONS?
ICMS and ISS taxes are calculated for many Jurisdictions, so when the tax is not calculated, it is need to
check if the jurisdiction is created for the tax. ICMS must be defined at State level and ISS must be defined
at City level.
ERROR AT “SHIP TO SITE” FOR RECOVERABLE TAX R ULE
The Recoverable Tax Rule does not recognize the function “NOT EQUAL TO”. It only recognizes positive
operator like “Equal to” and “In”.
UNDERSTANDING PLACE OF SUPPLY
During in the entrance of fiscal document, the application derives the place of supply of the transaction
as shown in the table below. It is important to understand how event class consider which jurisdiction will
be used on the tax calculation.
In the table below we have Jurisdiction as a Place of Supply. Order to Cash and Procure to Pay as event
classes.
BEST PRACTICE TO SETUP A RECOVERABLE TAX RATE
In general, is more frequently to not recoverable a tax than the opposite. Because of that the
recommendation is to use ZERO as “Tax Rules Default”, leaving the rates for recovery to be defined at
“Recoverable Tax Rules”.
289
CAN I USE THE SAME DETERMINING FACTOR FOR MORE THAN ONE TAXES?
Tax Cloud allow to use the same Determining Factor and Conditions Sets for different taxes as long as
they are all under in the same Tax Regime.
HOW TO DEFINE MINIMUM TAX AMOUNT FOR WITHHOLDING TAX?
The minimum tax amount can be defined in the “Threshold Controls” section at Manage Tax UI.
Navigate to Manage Tax, search for the Tax that needs to minimum amount and go to “Threshold
Controls” section.
In the “Threshold Controls” section define minimum amount as table below:
Fields Value
Threshold Buckets Level All
Threshold Basis Period
Withholding Tax Calendar Inform the withholding tax calendar
Threshold Type Tax Amount
Minimum Value Inform minimum amount for the tax
290
HOW TO CHANGE IRRF TAXABLE BASES USING INSS TAX AMOUNT?
Fowling the steps bellow to change the IRPF taxable basis:
1- Inform a “Compounding Precedence” to determine a sequence that system will use to calculate
a tax. The sequence for INSS Tax must be lower than IRRF Tax. Example: If INSS Tax has a
compound number 10 the IRRF Tax must have a compound greater that number 10.
The “Compounding Precedence” field is located in Manage Tax, in the Tax Information region.
Note: The compound is important to define sequence calculation and tax formula definition.
2- Create a new Taxable Formula for IRRF Tax

a. Navigate through Transaction Tax > Manage Tax Formulas
b. Change the scope to “Withholding Tax” and Tax Formula Type equal to “Taxable Basis
Formula”;
c. Click on create;
d. Define Configuration Owner as “Global Configuration Owner”
e. Define Tax Formula Code and Name
f. Inform Tax Regime Code
g. Inform Tax IRRF Tax
h. In the Tax Formula Compounding Details inform Tax Regime and Compounding Tax INSS
Tax;
i. Save and close.
3- Create a Tax Rule based on the “Taxable Basis Rules”.
HOW TO OPEN A SERVICE REQUEST (SR) FOR FDG, FDC AND LACLS?
Following the steps bellow to open a SR to:
Fiscal Document Generator (FDG):
1- Inform the “Problem Summary” and “Problem Description”

2- Change the tab for “Cloud” in the section “Where is the Problem?”
3- Select “Oracle Fusion Tax Cloud Services” in the “Service Type” field
4- Choose environment if necessary
5- Select problem type in the “Choose Problem Type” drop list. For FDG select:
a. “Country Tax Reporting” and “AR Reports for AMER (Latin America)
6- Select the “Support Identifier”
291
Fiscal Document Capture (FDC):

3- Select “Oracle Fusion Inventory Management Cloud Service” in the “Service Type” field
5- Select problem type in the “Choose Problem Type” drop list. For FDC select:
a. “Fiscal Document Capture” and choose the appropriated option
LACLS Extractors:

3- Select “Latin America Cloud Local Solutions (LACLS)” in the “Service Type” field
5- Select problem type in the “Choose Problem Type” drop list. For FDC select:
a. “General Service Request - LACLS”
WHICH PARTY SHOULD BE DEFINE IN THE TAX REGIME?
Party for the Tax Regime can be Legal Entity or Business Unit and the Oracle Cloud Tax is ready to
calculate by Business Unit. So, if it is the first-time configuration, you can defined a Party with the
Business Unit.
WHY DOES TAX CLOUD NOT CALCULATE?
If the Tax Cloud does not calculate tax in the transactions, you must check the following steps:
• Manage Party Tax Profiles: you must check if the Business Unit has the fields “Use legal entity
tax subscription” and “Use legal entity withholding tax subscription”.
If the field is enabling the system will be consider to calculate tax by Legal Entity and in this
case you must associate the Legal Entity in the:
o Manage Tax Regime
o Manage Configuration Owner Tax Options.
HOW TO DEFINE A BRAZILIAN CALENDAR ?
Oracle ERP Cloud is ready to define a Brazilian Calendar to set holiday and weekend, please check
note 2347415.1 Procure to Pay for Brazil available in My Oracle Support and look for Managing
Payables Collection Documents for Brazil file.
292
HOW TO DEFINE DOCUMENT TO TAX AUTHORITY?
The Oracle ERP Cloud allow two type definition to define a document to a Tax Authority please check
the topic Configuration Owner Tax Options in this document.
WHY PURCHASE ORDERIS DOES NOT HAVE INCLUSIVE TAX IN AP INVOICE MATCH?
It is necessary enable the “Inclusive Tax handling in Procure to Pay flow” option. Following steps in the
PRC:PO: How To Enable Incorporate Tax-Inclusive Pricing on Purchase Orders / Inclusive Tax
Handling in Purchase Orders? (Doc ID 2470965.1).
HOW TO IDENTIFY TAXABLE REGIME FOR DIFFERENT COMPANIES?
There are two different taxable regimes in Brazil Assumed Profit (Lucro Pressumido) and Actual Profit
(Lucro Real).
The definition can be done in Manage Tax Profile using Legal Entity level. There is a tab
“Classifications” where it is possible define the regimes.
After this definition you must create a Tax Rule based on this classification to apply the correct rate
for PIS and COFINS.
WHEN SHOULD IT USE A LOCATION OF FINAL DISCHARGE ?
The Location of Final Discharge can be used to calculate tax when Ship-to Jurisdiction is not the basis to
apply tax. In this case it is possible define another address that is not in the linked with Legal Entity
address.
ISS tax case, example Company Address (Ship-to Location) establish in Sao Paulo city, Supplier
(Ship-from) located in Barueri City, but the service was executed in Guarulhos city. So, the ISS tax
must be calculated where service was executed (Guarulhos), in this case the recommendation is use
the field Location of Final Discharge.
There is a new group in LACLS_ExtractApSpedData_Incremental extractor named

G_FINAL_DISCHARGE_LOCATION to attend this case.
HOW TO IDENTIFY TAXABLE REGIME FOR DIFFERENT COMPANIES ?
There are two different taxable regimes in Brazil Assumed Profit (Lucro Pressumido) and Actual Profit
(Lucro Real).
293
The definition can be done in Manage Tax Profile using Legal Entity level. There is a tab
“Classifications” where it is possible define the regimes.
After this definition you must create a Tax Rule based on this classification to apply the correct rate
for PIS and COFINS.
HOW TO CHANGE “ACCOUNTING CLASS” FOR FISCAL DOCUMENTS FROM FDC TO AP?
The accounting class “NonRecoverable” can be change using the Oracle Subledger Accounting Cloud
(SLA). It is possible consolidate the line information generated in the NonRecoverable class with
Accrual, allowing the system to display only one line in the AP transaction and journal in the General
Ledger Cloud. The definition of the SLA must be done in the subledger that will generate the
accounting of the fiscal document, so the configuration may vary according to the purchase made.
HOW TO DEFINE INTERNATIONAL SUPPLIER?
When the company has international purchasing processes it is required to create supplier in the ERP Cloud. Bellow
there is the main fields that must be attention:
1- Define “Foreign Corporation” at “Tax Organization Type” field in the Profile page.
2- Define Address for supplier.
a. Inform the right country of the supplier.
b. Inform the address.
c. Inform the postal code.
CKM process the Supplier Name and Postal Code to import the XML. If the supplier information does not
derivate it is important check the XML supplier name and postal code with the information created in the
ERP Cloud.
3- Inform the original supplier country in the “Tax Registration” page.
HOT TO IMPORT OF GOODS USING FOREIGN PURCHASE ORDER?
Search Oracle Documents in the browser:
1- Click on Oracle Cloud Applications.

2- Click on Inventory Management in the Supply Chain & Manufacturing section.
3- Click on Use in the Top Tasks section.
4- Click on Capture Fiscal Documents.
5- Navigate through Receive and Process Fiscal Documents, Import Goods
6- Click on Import of Goods using Foreign Purchase Order.
294
HOW TO REVERSE FISCAL DOCUMENT CAPTURE?
Fiscal Document Capture does not have cancelation option to a capture document. There is a procedure describe
in the Doc Id 2537128.1 (How to Reverse Process to Undo Inbound Fiscal Document (FDC)?) available in My
Oracle Support.
RECOMMENDATION TO ISSUE OWN FISCAL DOCUMENT (EMISSÃO PRÓPRIA) IN FDG
It is very important check the link bellow when the company needs to issue own fiscal document. The link goes to
What´s New web site from Oracle Financials Cloud related to Fiscal Document Generation 20B where described
conditional validation of state inscription during FDG Process for Brazil.
https://www.oracle.com/WEBFOLDER/TECHNETWORK/TUTORIALS/TUTORIAL/CLOUD/R13/WN/FIN/REL
EASES/20B/20B-FINANCIALS-WN.HTM#F12498
295
APPENDIX 1 – ACCOUTING FLOW WT TAX
This topic shows the accounting flow related to Withholding Tax Document created or NOT in Oracle Payables Cloud.
APPENDIX 2 – ORACLE ERP CLOUD IMPORT AND EXPORT - MACRO FLOW
297
IMPORT GOODS FLOW
298
IMPORT SERVICES FLOW
299
EXPORT GOODS FLOW
300
EXPORT SERVICES FLOW
301
Copyright © 2020, Oracle and/or its affiliates. All rights reserved.
This document is provided for information purposes only, and the contents hereof are subject to change without notice. This document is not warranted to be error-free, nor subject
to any other warranties or conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability or fitness for a particular purpose.
We specifically disclaim any liability with respect to this document, and no contractual obligations are formed either directly or indirectly by this document. This document may not
be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without our prior written permission.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of
SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered
trademark of The Open Group.

Lacls Fiscal Solution Path v1

Uploaded by

Document Information

Original Description:

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

Lacls Fiscal Solution Path v1

Uploaded by

Copyright:

Available Formats

Oracle Financials Cloud

Latin America Cloud Local Solution Brazil

REVISION HISTORY ............................................................................................................................................... 10

LATIN AMERICA CLOUD LOCAL SOLUTION FOR BRAZIL ........................................................................................ 15

ERP CLOUD ROLES ................................................................................................................................................ 16

ISV INTEGRATIONS ...................................................................................................................................................... 16

DEFINE ADDRESS FORMAT ............................................................................................................................................ 25

GENERAL LEDGER ................................................................................................................................................. 33

RAPID IMPLEMENTATION .............................................................................................................................................. 34

ENTERPRISE STRUCTURE ...................................................................................................................................... 35

LEGAL ENTITIES ........................................................................................................................................................... 35

DEFINE PARTIES FOR BRAZIL ................................................................................................................................ 45

Customer Information ........................................................................................................................................ 45

LOCALIZATION SYSTEM OPTIONS ......................................................................................................................... 49

ENABLE REGIONAL LOCALIZATION ................................................................................................................................... 49

INBOUND FISCAL DOCUMENTS ............................................................................................................................ 52

FISCAL DOCUMENT CAPTURE ......................................................................................................................................... 52

OUTBOUND FISCAL DOCUMENTS ........................................................................................................................ 57

FISCAL DOCUMENT GENERATION CONTROLS .................................................................................................................... 58

BRAZILIAN FISCAL CODES ................................................................................................................................... 128

CST ASSOCIATION ..................................................................................................................................................... 128

PAYABLES .......................................................................................................................................................... 151

DEFINE PAYMENT TERMS ............................................................................................................................................ 151

PROCUREMENT .................................................................................................................................................. 152

DEFINE TAX AUTHORITY.............................................................................................................................................. 152

PROCUREMENT MANAGEMENT ......................................................................................................................... 156

SELF-ASSESSED TAX............................................................................................................................................ 157

PROCUREMENT TRANSACTION ACCOUNT RULES .............................................................................................................. 157

SPECIAL TAXES ................................................................................................................................................... 187

ICMS DEFERRED (DIFERIDO) ....................................................................................................................................... 187

FUTURE TAX RECOVERY FOR FIXED ASSET ......................................................................................................... 214

DEFINE ICMS TAX RECOVERY IN FUTURE ....................................................................................................................... 214

RETURN TO VENDOR (RTV) ................................................................................................................................ 225

CONFIGURE ICMS CONTRIBUTOR AND IPI CONTRIBUTOR IN LRU SETUP.............................................................................. 226

IMPORTATION AND EXPORTATION (GOODS/SERVICES) .................................................................................... 229

IMPORTATION ........................................................................................................................................................... 229

FISCAL DOCUMENT CAPTURE ENTRANCE ........................................................................................................................ 269

SCENARIOS ........................................................................................................................................................ 276

RESALES WITH IPI NOT ICMS ST ................................................................................................................................. 276

FREQUENTLY ASKED QUESTIONS (FAQ) ............................................................................................................. 288

HOW TO VIEW AN XML FILE STRUCTERED? ................................................................................................................... 288

APPENDIX 1 – ACCOUTING FLOW WT TAX ......................................................................................................... 296

Date Version Notes

17/Oct/2023 11.1.1113.45 Procedure to define and create transaction for

09/Sep/2023 11.1.1113.43 Procedure to define IRPF WITH SIMPLIFIED DISCOUNT and

09/Sep/2023 11.1.1113.42 Procedure to define IRPF WITH SIMPLIFIED DISCOUNT

16-Dec-2022 11.1.1113.39 Include setup for RTV (Return to Vendor) scenario

11-Nov-2022 11.1.1113.38 Include LACLS_NAT_REND_CODE Tax Reporting Code to

23-Sep-2022 11.1.1113.37 Future ICMS and PIS/COFINS recovery in inbound fiscal

29-Aug-2022 11.1.1113.36 FCP Deferred

08-Aug-2022 11.1.1113.35 Create procedure to define CFPS Code

14-Jun-2022 11.1.1113.33 Review of date in document first page

14-Jun-2022 11.1.1113.32 Procedure to generate CTE-OS in the Oracle ERP Cloud

31-Jan-2022 11.1.1113.29 Geography to attend Importation/Exportation processes

17-Dec-2021 11.1.1113.27 Description for Tax Reporting ICMS Deferred

10-Dec-2021 11.1.1113.25 Excluded Brazilian Financial Banks from this document. It

06-Sep-2021 11.1.1113.22 Update Model 21 to use Note instead DFF.

06-Aug-2021 11.1.1113.20 Adjusts in the ICMS Deferred definition

04-Aug-2021 11.1.1113.19 New Structure for Tax Reporting Type

15-Jun-2021 11.1.1113.17 Define ICMS Diferred (Diferido)

18-May-2021 11.1.1113.15 Update new instruction about CNO Number

05-May-2021 11.1.1113.13 New feature Model 21