Sie sind auf Seite 1von 5

India GST:

Region/State check is this list correct?


AND Andaman Nicobar
AP Andhra Pradesh
ARP Arunachal Pradesh
AS Assam
BH Bihar
CHD Chandigarh
CHT Chattisgarh
DD Daman & Diu
DEL Delhi
DNH Dadar & Nagar Havel
GOA Goa
GUJ Gujarat
HAR Haryana
HP Himachal Pradesh
JHR Jharkhand
JK Jammu & Kashmir
KER Kerala
KN Karnataka
LAK Lakshadweep
MG Meghalaya
MH Maharashtra
MN Manipur
MP Madhya Pradesh
MZ Mizoram
NG Nagaland
OR Orissa
PO Pondicherry
PUN Punjab
RAJ Rajasthan
SIK Sikkim
TG Telangana
TN Tamil Nadu
TR Tripura
UP Uttar Pradesh
UT Uttaranchal
WB West Bengal
Tax Type
Tax type is set to VAT now in CRM. Not actually sure here what the impact is to
switch to GST, how/if it affects existing contracts, etc. When MY switched to GST,
CRM had been set to GST all along. May consider leaving this as VAT if there is no
impact or replication effects? CRM would pass only tax code.

Product Tax Classifications:


Below are the tax classifications for products in ECC and CRM. Based on our
conversation, that seems to be good.
ECC:
0 No tax
1 Full tax Materials
2 Full tax Service
3 Low tax rate

CRM:
FULLMAT Full Tax Material
FULLSER Full Tax Service
LOW Low Taxes
NONE Tax Exempt

Can you confirm that the product tax rules would:


1 Throw an error on anything that has LOW
2 set FULLMAT and FULLSER to be 18%
3 allow for a NONE to have a 0% if it existed? (or should we close that door?)

Will the current product tax classifications need to be updated? (based on India
MLAN entries pulled from production?)
Business Partner Tax Classifications:

ECC:
MWST 0 Tax Exempt
MWST 1 Liable for Taxes
MWST 2 No VAT Number
MWST 3 Government
MWST 4 Semi Government

CRM:
FORMC Form C
FORMD Form D
FORME Form E
FULL Full Taxes
NONE Tax Exempt

CRM to ECC Mapping:


IN MWST FORMC MWST 2
IN MWST FORMD MWST 3
IN MWST FORME MWST 4
IN MWST FULL MWST 1
IN MWST NONE MWST 0

Should there be any mass updates planned for BP/customer master data to set all
bps to FULL? Should add into the project a data review/update project with Fin Ops.

Storing Users GST registration number:


There is not a place or setting currently for any India registration number. SAP
would need to provide this and the associated mappings/integration between
systems (based on any codes in past (i.e. eu vat registration) they have always
included notes for this)
Tax Codes:
Current CRM tax codes:
S0 12/31/9999 01/01/1997 0% Output Tax -Export
S1 12/31/9999 01/01/1997 CST TAX 2% Against FORMC
S2 12/31/9999 01/01/1997 CST TAX 4% Against FORMD
S3 12/31/9999 01/01/1997 DVAT TAX 4% (Within Delhi)
S4 12/31/9999 01/01/1997 CST TAX4% Outside Delhi (Without FORMC or
FORMD)
S5 12/31/9999 01/01/1997 5 % Service Tax (FORME) Educational Inst.
SX 12/31/9999 01/01/1997 10.3 Output Tax Service

Future tax codes:


*0 0% Output Tax Export
*1 0% Tax Exempt
*2 IGST Bill to India (outside of Delhi)
*3 CGST + SGST Bill to Delhi
(associated tax events and middleware integration settings will be new and based
on new tax codes)

CRM will have a limitation of only being able to list 1 rate for Delhi. Would the
preference be to set it to the combined rate with a Delhi specific code? Fin Ops will
still need to manually process an invoice to send to the user?

Invoice Layout:
What changes are needed?
Mock up of new India tte tree:

Are there any decision points/variables missing?


At any point do we need to know if a user is registered? (sounds like registration
number is not a tax trigger, but rather something we may need to show on an
invoice)
Limitation on Delhi will be only a single rate is supported