Escolar Documentos
Profissional Documentos
Cultura Documentos
1
Oracle Confidential
Document Control
Change Record
Reviewers
Name Position
Rajnish Kumar Director, Tax Development
V S Baburaj Director, Product Strategy
Audience
Name Position
12.2.X Customers
2
Oracle Confidential
Table of Contents
Contents
Introduction .................................................................................................................................................................................................................................................4
Scope ...........................................................................................................................................................................................................................................................4
4.5 No Requirement for mapping different TDS Authority/Site to different TDS tax code level.................................................................................................8
3
Oracle Confidential
Introduction
This document describes about behavioral changes to TDS functionality post GST patches are applied.
The document depicts how the TDS feature will behave, what are actions required by users for TDS
feature working, once the GST patch is applied.
The TDS architecture is under-going change due to architecture enhancements done in product for GST
uptake. The intent is to minimize the user actions and impacts on TDS on end users due to the re-
architecture for TDS functionality.
Scope
As Indirect taxes (GST) will be a part of New GST solution, all the existing setup and transactional flows
will undergo a change according to the NEW GST solution Setups and Transaction flows for TDS.
The TDS functionality will remain same as current India Localization.
As part of our endeavor to minimize the business interruptions, the configuration and transactional
migration to new architecture will be handled by Oracle GST solution. The existing configuration and
transactions will be migrated from current India Localization system to GST system. There is no manual
intervention required for the same. The migration flow is being described in this document.
4
Oracle Confidential
1. Steps for TDS Migration
The TDS migration patch can only be applied after applying the India GST functional patch.
1. Tax Master (Tax Code) are migrated and created as Tax rate.
2. Tax category created and updated with the respective tax rate per new GST solution.
Note: If WCT/ESSI Sections are not used in existing India Localization then the WCT/ESSI regimes will
not get created. If business requires in future the WCT/ESSI regimes can be created manually.
6. Current India Localization Transactions data for TDS will be migrated to New Data model of
Withholding Tables in GST solution.
5
Oracle Confidential
2. Post Migration Steps:
Post applying TDS Migration patch navigate to Regime setup and update the following fields for migrated
TDS Regime
Tax Calendar
Tax Authority
The below checklist shows that the TDS Migration applied successfully:
TDS Regime created.
Tax type created.
Tax Rate created from existing tax code in current India Localization
TDS Threshold Setup created from existing setup in current India Localization
Tax category created from existing Tax Category in current India Localization
6
Oracle Confidential
3. TDS Transaction Migration:
The concurrent program will help in migration of the TDS transaction data
The program can be run multiple times for incremental migration.
Jai_ap_tds_inv_taxes =>jai_ap_wthld_inv_taxes
jai_ap_tds_prepayments =>jai_ap_wthld_prepayments
4.2 Configuration:
Only migrated Regime (TDS/WCT/ESSI) Tax Type and Rates should be used for
Transactions.
Supplier Additional Information mapped to Third party Registration which captures the
TDS regime and TDS attributes like PAN Number/Default section code etc.
Reporting Code will have all the existing TDS Regime attributes:
Deductor details for ETDS
State code
Division
Deductor Phone Number
7
Oracle Confidential
4.5 No Requirement for mapping different TDS Authority/Site to different TDS tax
code level.
Going forward it will be one Tax Authority and site for particular first party and all tax
authority invoices has to be created against the same.
The existing India Localization feature to group the payments for tax authorities for
Section, the same will be achieved using Payment segregation based on section code,
by following the PAY GROUP Approach. The steps for using Pay Group is defined below
So while TDS Invoice is generated system will automatically derive the Pay group based on the
section code attached to the transaction. The Invoices can be filtered on Pay group basis
during payments to the TDS Authority.
Client extension package is available which can customize the logic of Pay Group Derivation
based on their business need so that TDS generation procedure will populate the desired Pay
group to the TDS Vendor Invoice automatically.
8
Oracle Confidential
5. Important Migration Scripts:
Version SQL 1 Description
12.1.X jai_tax_code_to_ctgs_upg.sql This script migrates existing India
Localization tax codes to create new
tax code and Tax Category
12.1.X jai_tds_gdf_tax_ui_upg.sql This script derives the tax category
created for the TDS tax id from
Invoice distributions and updates the
newly created tax category in
JAI_AP_TDS_INV_TAXES.
9
Oracle Confidential
Note: For both 12.1.X and 12.2.X - Once all the above Migration scripts completed successfully the
concurrent program (India - TDS Migration Procedure) can be executed to migrate the TDS Transactions
Data.
1
Oracle Confidential 0
6. Frequently Asked Questions:
Question 1. Whether the migration works for all OU in system (Active/inactive)
Answer 1. Yes, current migration script shared will migrate all data of all Operating units involved in TDS
transaction in existing in current India Localization system.
Question 2. Whether the migrated TDS regime should be used and how?
Answer 2. Yes, use only Migrated TDS/WCT/ESSI regime (Mandatory) because all transactions data will
reference only the migrated regime details.
7. Points to Remember:
Existing customer with TDS should use only migrated TDS/WCT/ESSI regime.
Use migrated tax rate, Check if the Liability account is provided at the Tax rate level.
Check Regime level TDS calendar and Tax Authority is provided
Only migrated tax category should be used for existing transactions
First party registration need be done for Withholding Type with all TDS attributes.
Third party registration (Supplier Additional information) should be setup for Null and Site level
with TDS details.
1
Oracle Confidential 1