income tax department - clean money · the income-tax department will publish ... assessmentyear...

`

Income Tax Department

Statement of Financial Transaction (SFT)

XML Schema Guide for Developers

SFT XML Schema Guide for Developers

2

Document Version Control

Version Month Remarks

1.0 Jan 2017 First release


3

Contents Overview ............................................................................................................................................... 5

1. elementForm61A ...................................................................................................................... 6

2. Element FormCreationInfo ...................................................................................................... 7

3. Element creationInfo ................................................................................................................ 8

4. Element Form_Details ............................................................................................................. 9

5. complexType PartAStatementDtld_Type ........................................................................... 10

6. ComplexType ReportEntityDtl_Type ................................................................................... 11

7. ComplexType StatementDtl_Type ....................................................................................... 13

8. ComplexType NodalOfficerDtl_Type ................................................................................... 17

9. ComplexType NodalOfficerDtl_Type/Address ................................................................... 19

10. ComplexType NodalOfficerDtl_Type/Phone .................................................................. 21

11. ComplexType NodalOfficerDtl_Type/Fax ....................................................................... 22

12. ComplexType PartBReportDtls_Type ............................................................................. 23

13. ComplexType ReportSpec_Type ..................................................................................... 24

14. ComplexType PersonDtl_type.......................................................................................... 25

15. ComplexType PersonDtl_type/ Address ......................................................................... 30

16. ComplexType PersonDtl_type/ PrimaryContactNo ....................................................... 32

17. ComplexType PersonDtl_type/ OtherContactNo .......................................................... 33

18. ComplexType PersonDtl_type/ PhoneType ................................................................... 34

19. ComplexType FinanceTransSummary ........................................................................... 35

20. ComplexType FinanceTransDtls...................................................................................... 37

21. ComplexType PartCReportDtls_Type ............................................................................. 40


23. ComplexType AccountDtl_type ........................................................................................ 42

24. ComplexType BranchDtl_type.......................................................................................... 44

25. ComplexType BranchDtl_type/Address .......................................................................... 46

26. ComplexType AccountSummDtl_type ............................................................................ 48

27. ComplexType PartCPersonDtl_type ............................................................................... 50

28. ComplexType PartCPersonDtl_type/ personsDtls ........................................................ 51

29. ComplexType PartCPersonDtl_type/ personsDtls / Address ...................................... 56

30. ComplexType PartCPersonDtl_type/ personsDtls / PrimaryContactNo .................... 58

31. ComplexType PartCPersonDtl_type/ personsDtls / OtherContactNo ........................ 59

32. ComplexType PartCPersonDtl_type/ personsDtls / PhoneType ................................ 60

33. ComplexType PartDReportDtls_Type ............................................................................. 61



4

35. ComplexType TransacDtl_type ........................................................................................ 63

36. Element PropTransDtl_type/Address .............................................................................. 65

37. ComplexType PartDPersonDtl_type ............................................................................... 67

38. ComplexType PersonDtl_Immovable_type .................................................................... 68

39. ComplexType PersonDtl_Immovable_type/ Address ................................................... 73

40. ComplexType PersonDtl_Immovable_type/ PrimaryContactNo ................................. 75

41. ComplexType PersonDtl_Immovable_type/ OtherContactNo ..................................... 76

42. ComplexType PersonDtl_Immovable_type/ PhoneType ............................................. 77


5

Overview Section 285BA of the Income-tax Act, 1961 was introduced to provide a legal basis for the

Reporting Entities (RE) for maintaining and reporting information about the third party

transactions in Form 61A. Rules 114B to 114E have been inserted in Income-tax Rules,

1962 and Form 61A to have been developed in consultation with Regulators and Financial

Institutions in order to smoothen the reporting requirements and to address their concerns

wherever possible.

A Guidance Note has also been issued to provide guidance to the Financial Institutions,

Regulators and officers of the Tax Department for ensuring compliance with the reporting

requirements provided in Rules 114B to 114E and Form 61A of the Income-tax Rules, 1962.

The Guidance Note is intended to explain the complex reporting requirements and provide

further guidance wherever required. Since a large part of the Rules is based on CRS on

AEOI, the Financial Institutions may refer the CRS and its Commentary to get further

understanding of the terms used. In this Guidance Note, reference to the CRS and

Commentary has been given for further reference.

The requirement field for each data element indicates whether the element is validation or

optional in the schema.

Validation “Validation” elements MUST be present for ALL data records in a

file and an automated validation check will be undertaken. The

Sender should do a technical check of the data file content using

XML tools to make sure all “Validation” elements are present and

if they are not, the sender should correct the file. The Income-tax

Department will also do so and if incorrect, will reject the file.

(Optional) Mandatory An optional element that is required for reporting depending on

availability of information or legal factors. These elements may be

present in most (but not all) circumstances. The Income-tax

Department will publish separate validation rules to check these.

Optional An optional element specified in form

This section provides information about the schema for Form 61A.


6

1. elementForm61A

diagram

source <xs:element name="FORM61A"> <xs:complexType> <xs:sequence> <xs:element name="FormCreationInfo"> <xs:complexType> <xs:sequence> <xs:element ref="Form:CreationInfo"/> <xs:element ref="Form:Form_Details"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="PartAStatementDetails" type="form61a:PartAStatementDtld_Type"/> <xs:element name="PartBReportDetails" type="form61a:PartBReportDtls_Type" minOccurs="0" maxOccurs="unbounded"/> <xs:element name="PartCReportDetails" type="form61a:PartCReportDtls_Type" minOccurs="0" maxOccurs="unbounded"/> <xs:element name="PartDReportDetails" type="form61a:PartDReportDtls_Type" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> </xs:complexType> </xs:element>

The explanation of elements are as under:

Element Description Requirement

FormCreationInfo Captures the form details and its creation

information.

Validation

PartAStatementDetails Captures the statement details. Validation.

PartBReportDetails Captures the details of person based reporting.

This part is reported for financial transactions.

Optional

(Mandatory)

PartCReportDetails Captures the details for each account been

reported for bank/post office accounts

Optional

(Mandatory)

PartDReportDetails Captures the details of each transaction been

reported for immovable property.

Optional

(Mandatory)


7

2. Element FormCreationInfo

diagram

source <xs:element name="FormCreationInfo"> <xs:complexType> <xs:sequence> <xs:element ref="Form:CreationInfo"/> <xs:element ref="Form:Form_Details"/> </xs:sequence> </xs:complexType> </xs:element>



FormCreationInfo Captures the details of SWVersionNo,

SWCreatedBy, XMLCreatedBy,

XMLCreationDate

Validation

Form_Details Captures the details of FormName, Assessment

Year, SchemaVer, FormVer

Validation

8

3. Element creationInfo

diagram

source <xs:element name="CreationInfo"> <xs:complexType> <xs:sequence> <xs:element ref="SWVersionNo"/> <xs:element ref="SWCreatedBy"/> <xs:element ref="XMLCreatedBy"/> <xs:element ref="XMLCreationDate"/>  </xs:sequence> </xs:complexType> </xs:element>



SWVersionNo Software version used for creation of XML Eg.

V1.0

Validation

SWCreatedBy Software Name for creation of XML Eg. APPLE

INC

Validation

XMLCreatedBy Software used for Xml Creation, Can be same

as XML Created Eg. APPLE INC

Validation

XMLCreationDate Date on which XML has been generated,

Should be YYYY-MM-DD format.

Validation


9

4. Element Form_Details

diagram

source <xs:element name="Form_Details"> <xs:complexType> <xs:sequence> <xs:element ref="FormName"/> <xs:element ref="AssessmentYear"/> <xs:element ref="SchemaVer"/> <xs:element ref="FormVer"/> </xs:sequence> </xs:complexType> </xs:element>



FormName Name of the form. E.g. Form61A Validation

AssessmentYear Assessment Year for which the form is being

submitted (Format: YYYY)

Validation

SchemaVer Version of schema. Validation

FormVer Version of form can be kept as “Ver1.0”. In case

of any change in notified form 61A, same can

be updated.

Validation


10

5. complexType PartAStatementDtld_Type

diagram

source <xs:complexType name="PartAStatementDtld_Type">

<xs:sequence>

<xs:element name="ReportingEntity" type="form61a:ReportEntityDtl_Type"/>

<xs:element name="StatementDetails" type="form61a:StatementDtl_Type"/>

<xs:element name="PrincipalOffcrDtls" type="form61a:NodalOfficerDtl_Type"/>

</xs:sequence>



ReportingEntity Complete details of Reporting entities, i.e. Name, ITDREIN and Registration Number

Validation

StatementDetails Complete details of the statement of an individual. Validation

PrincipalOfficrDtls Complete details of the principal officer. Validation


11

6. ComplexType ReportEntityDtl_Type

diagram

source <xs:complexType name="ReportEntityDtl_Type"> <xs:sequence> <xs:element name="Name"> <xs:simpleType> <xs:restriction base="form61a:nonEmptyString"> <xs:minLength value="1"/> <xs:maxLength value="125"/> </xs:restriction> </xs:simpleType> </xs:element> <xs:element name="ITDREIN"> <xs:simpleType> <xs:restriction base="xs:string"> <xs:length value="16"/> <xs:pattern value="[A-Z]{5}[0-9]{4}[A-Z]{1}[.][A]{1}[BCDGIMNPRSZ]{1}[0-9]{3}|[A-Z]{4}[0-9]{5}[A-Z]{1}[.][A]{1}[BCDGIMNPRSZ]{1}[0-9]{3}"/> </xs:restriction> </xs:simpleType> </xs:element> <xs:element name="RegistrationNo" minOccurs="0"> <xs:simpleType> <xs:restriction base="form61a:nonEmptyString"> <xs:minLength value="1"/> <xs:maxLength value="100"/> </xs:restriction> </xs:simpleType> </xs:element> </xs:sequence> </xs:complexType>


12



Name Complete name of the reporting entity. Validation

ITDREIN ITDREIN is the Unique ID issued by ITD which will be communicated by ITD after the registration of the reporting entity with ITD. The ITDREIN is a 16-character identification number in the format XXXXXXXXXX.YYYYY where XXXXXXXXXX is the PAN or TAN of the reporting entity and YYYYY is a sequentially generated number. The reporting Entity may use a dummy number (PAN+99999 or TAN+99999) till the ITDREIN is communicated.

Validation

RegistrationNo This number is the registration number or any number used in correspondence with the regulator of the financial institution.

(Optional) Mandatory


13

7. ComplexType StatementDtl_Type

diagram

source <xs:complexType name="StatementDtl_Type"> <xs:sequence> <xs:element name="SFTCode" type="enum:SFT_EnumType"/> <xs:element name="StatementType" type="enum:Statement_EnumType"/> <xs:element name="StatementNumber"> <xs:simpleType> <xs:restriction base="xs:string"> <xs:pattern value="[1-9]{1}[0-9]{3}[//][0-9]{2}"/> </xs:restriction> </xs:simpleType> </xs:element> <xs:element name="OrgStatementId"> <xs:simpleType> <xs:restriction base="xs:string"> <xs:pattern value="0|[1-9]{1}[0-9]{14}"/> </xs:restriction> </xs:simpleType> </xs:element> <xs:element name="CorrectionReason" type="enum:CorrecReason_EnumType"/> <xs:element name="StatementDate" type="xs:dateTime"/> <xs:element name="ReportingPeriod" type="xs:date"/> <xs:element name="ReportingType" type="enum:Report_EnumType"/> <xs:element name="NoOfReports" type="xs:nonNegativeInteger"/> </xs:sequence> </xs:complexType>



SFTCode Type of transaction reported. Permissible values are:

Validation


14


SFT- 001: Purchase of bank drafts or pay

orders in cash

SFT- 002: Purchase of pre-paid instruments

in cash

SFT- 003: Cash deposit in current account

SFT- 004: Cash deposit in account other

than current account

SFT- 005: Time deposit

SFT- 006: Payment for credit card

SFT- 007: Purchase of debentures

SFT- 008: Purchase of shares

SFT- 009: Buy back of shares

SFT- 010: Purchase of mutual fund units

SFT- 011: Purchase of foreign currency

SFT- 012: Purchase or sale of immovable

property

SFT- 013: Cash payment for goods and

services

SFT- 014: Cash deposits during specified

period

StatementType Type of Statement submitted. Permissible values are:

NB – New Statement containing new information

CB – Correction Statement containing corrections for previously submitted information

ND - No Data to report

One Statement can contain only one type of Statement. Even if missing information has to be supplied, the complete report has to be submitted instead of an incremental report.

Validation

StatementNumber Statement Number is a free text field capturing the sender’s unique identifying number (created by the sender) that identifies the particular Statement being sent. The identifier allows both the sender and receiver to identify the specific Statement later if questions or corrections arise. After successful submission of the Statement to ITD, a new unique Statement ID will be allotted for future reference. The reporting entities should maintain the linkage between the Statement Number and Statement ID.

Pattern value:

The first digit cannot be 0.

The next three digit can be combination of any number running from 0 to 9,

Validation


15


Followed by “/” character.

Then the next 2 digit can be combination of any number running from 0 to 9

Example of the statement number is 2015/01.

OrgStatementId In case if the original statement is being replaced by this statement, statement ID of the original Statement which is being replaced deleted or referred by reports in the current Statement.

In case the Statement is new and unrelated to any previous Statement, mention ‘0’ here.

Pattern value:

0 or

15 digit number where first digit can take values from 1 to 9 and the next 14 digit can be combination of any number running from 0 to 9

Validation

CorrectionReason Reason for revision to be stated when the original Statement is corrected.

Permissible values are:

A - Acknowledgement of original Statement had errors which are being resolved

B - Errors in original Statement are being corrected suo-motu

C - The correction report is on account of additional information being submitted

N - Not applicable as this is a new statement/test data/ there is no data to report

Z - Other reason

Optional

StatementDate This identifies the date and time when the Statement was compiled. This element will be automatically populated by the host system. The format for use is YYYY-MM-DD’T’hh:mm:ss. Fractions of seconds are not used. Example: 2015-03-15T09:45:30.

Validation

ReportingPeriod This identifies the last day of the reporting period in YYYY-MM-DD format. For example, if reporting information for the accounts or payments made in calendar year 2014, the field would read, “2014-12-31”

Validation

ReportingType Type of report in the Statement. One Statement can contain only one type of report. Permissible values are:

AF- Aggregated Financial Transactions

BA – Bank/Post Office Account

IM - Immovable Property Transactions

Validation


16


NoOfReports Number of the reports in the statement Validation


17

8. ComplexType NodalOfficerDtl_Type

diagram

source </xs:complexType>

<xs:complexType name="NodalOfficerDtl_Type">

<xs:sequence>

<xs:element name="Name">

<xs:simpleType>

<xs:restriction base="form61a:nonEmptyString">

<xs:minLength value="1"/>

<xs:maxLength value="125"/>

</xs:restriction>

</xs:simpleType>

</xs:element>

<xs:element name="Designation">

<xs:simpleType>




</xs:restriction>

</xs:simpleType>

</xs:element>

<xs:element name="Address" type="form61a:DetailedAddress_Type"/>

<xs:element name="Phone" type="form61a:PhoneType"/>

<xs:element ref="form61a:MobileNo"/>

<xs:element name="Fax" type="form61a:PhoneType" minOccurs="0"/>

<xs:element name="Email" type="form61a:EmailType"/>

</xs:sequence>



18


Name Name of the Designated Director. Refer to the registration requirement under section 285BA of the Income-tax Act and Rule

114E(7) of the Income-tax Rule

Validation

Designation Designation of the Designated Director in the organization of statement filer.

Validation

Address Complete address consisting of house number, building name, street, locality, city, state etc.

Validation

Phone Telephone number in format STD Code-Telephone number. STD code cannot start with a ‘0’ and the total digits of the phone no including STD code must be 10 (Example 120-2894016)

Optional

Mobile Number Contact Mobile number. Please do not add “0” before the number

Validation

Fax Fax number in format STD Code-Telephone number. STD code cannot start with a ‘0’ and the total digits of the phone no including STD code must be 10 (Example 120-2894016)

Optional

Email E-mail of the Nodal Officer Validation


19

9. ComplexType NodalOfficerDtl_Type/Address

diagram


<xs:complexType name="DetailedAddress_Type">

<xs:sequence>

<xs:element name="HouseNo">

<xs:simpleType>




</xs:restriction>

</xs:simpleType>

</xs:element>

<xs:element name="BuildingName" minOccurs="0">

<xs:simpleType>




</xs:restriction>

</xs:simpleType>

</xs:element>

<xs:element name="Street" minOccurs="0">

<xs:simpleType>




</xs:restriction>

</xs:simpleType>

</xs:element>

<xs:element name="Locality">

<xs:simpleType>


20




</xs:restriction>

</xs:simpleType>

</xs:element>

<xs:element name="CityOrTown">

<xs:simpleType>




</xs:restriction>

</xs:simpleType>

</xs:element>

<xs:element name="State" type="iso:StateCode_Type"/>

<xs:element name="PostalCode" type="form61a:PinCodeType"/>

<xs:element name="CountryCode" type="iso:CountryCode_Type"/>

</xs:sequence>



House No. Complete address consisting of house number, building name, street, locality, city, state etc.

Validation

BuildingName Name of the building Optional

Street Street Name Optional

Locality Locality Name Validation

CityOrTown Name of City, Town or Village Validation

State The two digit state code has to be mentioned as per Indian Motor Vehicle Act 1988. If state code is not available, use XX.

Validation

PostalCode In case of India, the 6 digit Pin code as per India Posts has to be mentioned. In case of countries outside India, respective code may be used. If Pin code is not available, use XXXXXX.

Validation

CountryCode The Country Code as per ISO 3166 has to be mentioned. Use IN for India. If Country Code is not available, use XX

Validation


21

10. ComplexType NodalOfficerDtl_Type/Phone

diagram


<xs:complexType name="PhoneType">

<xs:sequence>

<xs:element name="STDcode">

<xs:simpleType>

<xs:restriction base="xs:unsignedLong">

<xs:totalDigits value="5"/>

</xs:restriction>

</xs:simpleType>

</xs:element>

<xs:element name="PhoneNo">

<xs:simpleType>

<xs:restriction base="xs:normalizedString">

<xs:pattern value="[0-9]{1,10}"/>

</xs:restriction>

</xs:simpleType>

</xs:element>

</xs:sequence>



STDcode STD code of city of the country for the telephone No.

Validation

PhoneNo Primary Telephone (without STD code-Telephone number) or mobile number (Please do not add “0” before the number)

Validation


22

11. ComplexType NodalOfficerDtl_Type/Fax

diagram

source <xs:element name="Fax" type="form61a:PhoneType" minOccurs="0"/>



STDcode STD code of city of the country Validation

PhoneNo Primary Telephone (without STD code-Telephone number)

Fax number in format STD Code-Telephone number. (Example 0120-2894016)

Validation


23

12. ComplexType PartBReportDtls_Type

diagram

source <xs:complexType name="PartBReportDtls_Type"> <xs:sequence> <xs:element name="ReportSpec" type="form61a:ReportSpec_Type"/> <xs:element name="PersonDtls" type="form61a:PersonDtl_type"/> <xs:element name="FinTransSummary" type="form61a:FinTransSumDtl_type"/> <xs:element name="FinTransDtls" type="form61a:FinTransDtl_type" maxOccurs="unbounded"/> </xs:sequence> </xs:complexType>



ReportSpec Captures the details of “element name=ReportSlNo” and “element name= OriginalRptSlNo”.

Validation

PersonDetails Contains the details of the person being reported.

Validation

FinanceTransSummary Contains the summary of financial transaction.

Optional

FinanceTransDtls Contains the financial transaction details for each distinctive product.

Validation


24

13. ComplexType ReportSpec_Type

diagram

source <xs:complexType name="ReportSpec_Type"> <xs:sequence> <xs:element name="ReportSlNo" type="xs:unsignedLong"/> <xs:element name="OriginalRptSlNo" type="xs:unsignedLong"/> </xs:sequence> </xs:complexType>



ReportSlNo The number uniquely represents a report within a Statement. The Report Serial Number should be unique within the Statement. This number along with Statement ID will uniquely identify any report received by ITD.

Validation

OriginalRptSlNo The Report Serial Number of the original report that has to be replaced or deleted. This number along with Original Statement ID will uniquely identify the report which is being corrected.

In case there is no correction of any report, mention ‘0’ here.

Validation


25

14. ComplexType PersonDtl_type

diagram

source <xs:complexType name="PersonDtl_type"> <xs:sequence> <xs:element name="NameOfPerson"> <xs:simpleType> <xs:restriction base="form61a:nonEmptyString"> <xs:minLength value="1"/> <xs:maxLength value="125"/> </xs:restriction> </xs:simpleType> </xs:element> <xs:element name="TypeOfPerson" type="enum:NamePerson_EnumType"/> <xs:element name="CustomerID" minOccurs="0"> <xs:simpleType> <xs:restriction base="form61a:nonEmptyString"> <xs:minLength value="1"/> <xs:maxLength value="125"/>

26

</xs:restriction> </xs:simpleType> </xs:element> <xs:element name="Gender" type="enum:Gender_EnumType"/> <xs:element name="FathersName" minOccurs="0"> <xs:simpleType> <xs:restriction base="form61a:nonEmptyString"> <xs:minLength value="1"/> <xs:maxLength value="125"/> </xs:restriction> </xs:simpleType> </xs:element> <xs:element name="PAN" minOccurs="0"> <xs:simpleType> <xs:restriction base="xs:string"> <xs:length value="10"/> <xs:pattern value="[A-Z][A-Z][A-Z][A-Z][A-Z]\d\d\d\d[A-Z]"/> </xs:restriction> </xs:simpleType> </xs:element> <xs:element name="AadhaarNum" minOccurs="0"> <xs:simpleType> <xs:restriction base="xs:string"> <xs:length value="12"/> <xs:pattern value="[0-9]{12}"/> </xs:restriction> </xs:simpleType> </xs:element> <xs:element name="Form60AckNum" minOccurs="0"> <xs:simpleType> <xs:restriction base="form61a:nonEmptyString"> <xs:minLength value="1"/> <xs:maxLength value="75"/> </xs:restriction> </xs:simpleType> </xs:element> <xs:element name="IdentificationType" type="enum:Identification_EnumType" minOccurs="0"/> <xs:element name="IdentificationNum" minOccurs="0"> <xs:simpleType> <xs:restriction base="form61a:nonEmptyString"> <xs:minLength value="1"/> <xs:maxLength value="100"/> </xs:restriction> </xs:simpleType> </xs:element> <xs:element name="DateOfBirthOrIncorp" type="xs:date" minOccurs="0"/> <xs:element name="NationalityOfIncorpDtls" type="iso:CountryCode_Type" minOccurs="0"/>  <xs:element name="BussOrOccupation" minOccurs="0"> <xs:simpleType> <xs:restriction base="form61a:nonEmptyString">


27

<xs:minLength value="1"/> <xs:maxLength value="100"/> </xs:restriction> </xs:simpleType> </xs:element> <xs:element name="AddressDtls" type="form61a:ShortAddressWithAddressTyp_Type" minOccurs="1” maxOccurs="unbounded"/> <xs:element name="PrimaryContactNo" type="form61a:MobOrLandLineType" minOccurs="0"/> <xs:element name="OtherContactNo" type="form61a:MobOrLandLineType" minOccurs="0"/> <xs:element name="Email" type="form61a:EmailType" minOccurs="0"/> <xs:element name="Remarks" minOccurs="0"> <xs:simpleType> <xs:restriction base="form61a:nonEmptyString"> <xs:minLength value="1"/> <xs:maxLength value="500"/> </xs:restriction> </xs:simpleType> </xs:element> </xs:sequence> </xs:complexType>



NameOfPerson Name of the individual or entity. Validation

TypeOfPerson The permissible values are:

IN - Individual

SP- Sole Proprietorship

PF- Partnership Firm

HF - HUF

CR - Private Limited Company

CB - Public Limited Company

SO - Society

AO - Association of persons/Body of individuals

TR - Trust

LI - Liquidator

LL - LLP

ZZ - Others

XX – Not Categorised

Validation

CustomerID Customer ID/Number allotted by the reporting entity.

It depends on the type of the reporting entity. For example, in case of banking customerID is mandatory


Gender For individuals only.


M - Male

Validation


28


F - Female

O – Others

N – Not Applicable (for entities)

X – Not Categorised

FathersName For individuals only.

Name of the father (if available). Mandatory if element name = “PAN” is not reported.


PAN Permanent Account Number issued by Income Tax Department.

Rule 114B of the Income Tax specify the transactions in which PAN is mandatory.

In case the person doesn’t have PAN, he has to furnish form 60 to reporting entities


AadhaarNum For individuals only.

Aadhaar number issued by UIDAI (if available).

If PAN is missing, then it is mandatory to provide AadhaarNum.


Form60AckNum Form 60 Acknowledgment number

(In case the person doesn’t have PAN (refer rule 114B), form 60 will be furnished to reporting entity)


IdentificationType In case “element name= PAN” is not reported a document submitted as proof of identity of the individual.


A - Passport

B - Election Id Card

C - PAN Card

D - ID Card issued by Government/PSU E - Driving License

G - UIDAI Letter / Aadhaar Card

H - NREGA job card

Z – Others


IdentificationNum Number mentioned in the identification document

Mandatory if element name = “PAN” is not reported.


DateOfBirthOrIncorp Individual: Actual Date of Birth; Company: Date of incorporation; Association of Persons: Date of formation/creation; Trusts: Date of creation of Trust Deed; Partnership Firms: Date of Partnership Deed; LLPs: Date of



29


incorporation/Registration; HUFs: Date of creation of HUF and for ancestral HUF date can be 01-01-0001 where the date of creation is not available.

The data format is YYYY-MM-DD


NationalityOfIncorpDtls 2 character Country Code (ISO 3166). Mandatory if element name = “PAN” is not reported.


Nationality 2 character Country Code (ISO 3166). Mandatory if element name = “PAN” is not reported.


BussOrOccupation Business or occupation (if available) Optional

AddressDtls Complete address of the person consisting of house number, building name, street, locality, city, state, Postal Code and country.

Validation

Address Type Indicates the legal character of the address. Permissible values are:

1- Residential Or Business

2 - Residential

3 - Business

4 – Registered Office

5 – Unspecified

Optional

PrimaryContactNo Primary Telephone (STD Code-Telephone number) or mobile number (if available)


OtherContactNo Other Telephone (STD Code-Telephone number) or mobile number

Optional

Email Email Address (if available) (Optional) Mandatory

Remarks Remarks or any other information Optional

30

15. ComplexType PersonDtl_type/ Address

diagram

source <xs:complexType name="ShortAddressWithAddressTyp_Type"> <xs:sequence>  <xs:element name="AddressFix"> <xs:simpleType> <xs:restriction base="form61a:nonEmptyString"> <xs:minLength value="1"/> <xs:maxLength value="300"/> </xs:restriction> </xs:simpleType> </xs:element> <xs:element name="City" minOccurs="0"> <xs:simpleType> <xs:restriction base="form61a:nonEmptyString"> <xs:minLength value="1"/> <xs:maxLength value="50"/> </xs:restriction> </xs:simpleType> </xs:element> <xs:element name="PostCode" type="form61a:PinCodeType"/> <xs:element name="State" type="iso:StateCode_Type"/> <xs:element name="CountryCode" type="iso:CountryCode_Type"/> </xs:sequence> <xs:attribute name="AddressType" type="enum:Address_EnumType"/> </xs:complexType>




2 - Residential

3 - Business


5 – Unspecified

Optional


31

AddressFix Complete address of the branch consisting of house number, building name, street, locality, city, state, Postal Code and country.


City Name of City, Town or Village (Optional) Mandatory

PostCode In case of India, the 6 digit Pin code as per India Posts has to be mentioned. In case of countries outside India, respective code may be used. If Pin code is not available, use XXXXXX.

Validation

State The two digit state code has to be mentioned as per Indian Motor

Vehicle Act 1988. If state code is not available, use XX.

Validation


Validation


32

16. ComplexType PersonDtl_type/ PrimaryContactNo

diagram

source <xs:element name="PrimaryContactNo" type="form61a:MobOrLandLineType" minOccurs="0"/>



PhoneNo Contain information of STD code and landline number


MobileNo Mobile Number of the person (Optional) Mandatory


33

17. ComplexType PersonDtl_type/ OtherContactNo

diagram

source <xs:element name="OtherContactNo" type="form61a:MobOrLandLineType" minOccurs="0"/>







34

18. ComplexType PersonDtl_type/ PhoneType

diagram

source <xs:complexType name="PhoneType"> <xs:sequence> <xs:element name="STDcode"> <xs:simpleType> <xs:restriction base="xs:unsignedLong"> <xs:totalDigits value="5"/> </xs:restriction> </xs:simpleType> </xs:element> <xs:element name="PhoneNo"> <xs:simpleType> <xs:restriction base="xs:normalizedString"> <xs:pattern value="[0-9]{1,10}"/> </xs:restriction> </xs:simpleType> </xs:element> </xs:sequence> </xs:complexType>



Validation


Validation


35

19. ComplexType FinanceTransSummary

diagram


<xs:complexType name="FinTransSumDtl_type">

<xs:sequence>

<xs:element name="ProductType" type="enum:Product_EnumType" minOccurs="0"/>

<xs:element name="AggtAmtRecdFrmPerson" type="form61a:UnsignedLong_Type" minOccurs="0"/>

<xs:element name="AggtAmtRecdInCash" type="form61a:UnsignedLong_Type" minOccurs="0"/>

<xs:element name="AggtAmtPaidToPerson" type="form61a:UnsignedLong_Type" minOccurs="0"/>

<xs:element name="Remarks" minOccurs="0">

<xs:simpleType>




</xs:restriction>

</xs:simpleType>

</xs:element>

</xs:sequence>



ProductType Type of product linked with the transaction. Permissible values are:

BD - Bonds or Debentures

CC- Credit Card

DD – Bank draft or pay order or banker's cheque

PI – Prepaid Instrument

FC - Foreign Currency sale

MF - Mutual Fund

SI – Shares issued



36


SB – Shares bought back

TD - Time Deposit

ZZ – Others

XX - Unspecified

AmtReceivdFrmPerson Aggregate gross amount paid by the person during the period


AmtReceivdinCash Aggregate gross amount paid by the person in cash during the period


AmtPaidToPerson Aggregate gross amount paid to the person during the period




37

20. ComplexType FinanceTransDtls

diagram


<xs:complexType name="FinTransDtl_type">

<xs:sequence>

<xs:element name="ProductIdentifier" minOccurs="0">

<xs:simpleType>




</xs:restriction>

</xs:simpleType>

</xs:element>

<xs:element name="LastDateOfTrans" type="xs:date" minOccurs="0"/>

<xs:element name="AggtAmtRecdFrmPerson" type="form61a:UnsignedLong_Type" minOccurs="0"/>

<xs:element name="AggtAmtRecdInCash" type="form61a:UnsignedLong_Type" minOccurs="0"/>

<xs:element name="AggtAmtPaidToPerson" type="form61a:UnsignedLong_Type" minOccurs="0"/>

<xs:element name="RelAcctNum" minOccurs="0">

<xs:simpleType>




</xs:restriction>

</xs:simpleType>

</xs:element>


38

<xs:element name="RelInstitutionName" minOccurs="0">

<xs:simpleType>


<xs:minLength value="1"/> <xs:maxLength value="125"/> </xs:restriction>

</xs:simpleType></xs:element>

<xs:element name="InstitutionRefNum" minOccurs="0">

<xs:simpleType>




</xs:restriction>

</xs:simpleType>

</xs:element>


<xs:simpleType>




</xs:restriction>

</xs:simpleType>

</xs:element>

</xs:sequence>



ProductIdentifier Unique identifier to identify the product. E.g. Time deposit number, credit card number etc.


AmtReceivdFrmPerson Aggregate gross amount paid by the person during the period

Depends on the type of transactions listed in rule 114E


AmtReceivdinCash Aggregate gross amount paid by the person in cash during the period



AmtPaidToPerson Aggregate gross amount paid to the person during the period



AccountNumber Account number (if available) from/to which funds was transferred.

Optional

InstitutionName Name of the institution (if available) from / to which funds were transferred.

Optional


39


InstitutionRefNum Institution reference number of the institution (if available) from /to which funds were transferred.

Optional



40

21. ComplexType PartCReportDtls_Type

diagram

source <xs:complexType name="PartCReportDtls_Type"> <xs:sequence> <xs:element name="ReportSpec" type="form61a:ReportSpec_Type"/> <xs:element name="AccountDtls" type="form61a:AccountDtl_type"/> <xs:element name="AccountSummary" type="form61a:AccountSummDtl_type"/> <xs:element name="Persons" type="form61a:PartCPersonDtl_type" maxOccurs="unbounded"/> </xs:sequence> </xs:complexType>



ReportSpec Captures the details of “element name=ReportSlNo” and “element name=OriginalRptSlNo”

Validation

AccountDtls Contains the details of the account Validation

AccountSummDtls Contains the summary of account details

Validation

PartCPersonDtls Contains the person details for each person related to the account.

Validation


41


diagram


<xs:complexType name="ReportSpec_Type">

<xs:sequence>

<xs:element name="ReportSlNo" type="xs:unsignedLong"/>

<xs:element name="OriginalRptSlNo" type="xs:unsignedLong"/>

</xs:sequence>




Validation



Validation


42

23. ComplexType AccountDtl_type

diagram


<xs:complexType name="AccountDtl_type">

<xs:sequence>

<xs:element name="AccountType" type="enum:Account_EnumType"/>

<xs:element name="AccountNumber">

<xs:simpleType>




</xs:restriction>

</xs:simpleType>

</xs:element>

<xs:element name="AccountHolderName">

<xs:simpleType>




</xs:restriction>

</xs:simpleType>

</xs:element>

<xs:element name="AccountStatus" type="enum:AccountStatus_EnumType"/>

<xs:element name="BranchDetails" type="form61a:BranchDtl_type"/>

</xs:sequence>

</xs:complexType>



AccountType Type of account. Permissible values are:

BS - Savings Account

Validation


43


BC - Current Account

ZZ - Other Account

XX - Not Categorised

AccountNumber Provide the account number used by the financial institution to identify the account. If the financial institution does not have an account number then provide the functional equivalent unique identifier used by the financial institution to identify the account.

Validation

AccountHolderName Name of first/sole account holder.

Validation

AccountStatus Status of the account. Permissible values are:

A – Active: Account is in regular use

C - Closed: Account is closed during the financial year

Z - Others: Not listed above

X - Not categorized: The information is not available.

Validation

BranchDetails Branch details include”element name=branchRefNo., BranchName and address”along with the “element name=postalCode, state and countryCode”.

Validation


44

24. ComplexType BranchDtl_type

diagram


<xs:complexType name="BranchDtl_type">

<xs:sequence>

<xs:element name="BranchRefNum">

<xs:simpleType><xs:restriction base="form61a:nonEmptyString">



</xs:restriction>

</xs:simpleType>

</xs:element>

<xs:element name="BranchName">




</xs:restriction>

</xs:simpleType>

</xs:element>

<xs:element name="Address" type="form61a:ShortAddress_Type"/>

<xs:element name="Phone" type="form61a:PhoneType"/>

<xs:element ref="form61a:MobileNo"/>

<xs:element name="Fax" type="form61a:PhoneType" minOccurs="0"/>

<xs:element name="Email" type="form61a:EmailType"/>






45

</xs:restriction>

</xs:simpleType>

</xs:element>

</xs:sequence>



BranchRefNum The unique number (IFSC code etc.) to uniquely identify the branch. Reporting Financial Institution can use self-generated numbers to uniquely identify the branch.

Validation

BranchName Name of Branch linked to the account. This could be the home or linked branch.

Validation

Address Complete address of the branch consisting of house number, building name, street, locality, city, state, Postal Code and country.

Validation


Validation

Email E-mail of the Branch head Validation

Remarks Remarks or any other information

Optional

46

25. ComplexType BranchDtl_type/Address

diagram

source <xs:complexType name="ShortAddress_Type"> <xs:sequence>  <xs:element name="AddressFix" minOccurs="0"> <xs:simpleType> <xs:restriction base="form61a:nonEmptyString"> <xs:minLength value="1"/> <xs:maxLength value="300"/> </xs:restriction> </xs:simpleType> </xs:element> <xs:element name="City" minOccurs="0"> <xs:simpleType> <xs:restriction base="form61a:nonEmptyString"> <xs:minLength value="1"/> <xs:maxLength value="50"/> </xs:restriction> </xs:simpleType> </xs:element> <xs:element name="PostCode" type="form61a:PinCodeType"/> <xs:element name="State" type="iso:StateCode_Type"/> <xs:element name="CountryCode" type="iso:CountryCode_Type"/> </xs:sequence> </xs:complexType>






PostCode In case of India, the 6 digit Pin code as per India Posts has to be mentioned. In case of countries outside India,

Validation


47


respective code may be used. If Pin code is not available, use XXXXXX.



Validation


Validation


48

26. ComplexType AccountSummDtl_type

diagram


<xs:complexType name="AccountSummDtl_type">

<xs:sequence>

<xs:element name="AmtCreditedToAcc" type="form61a:UnsignedLong_Type"/>

<xs:element name="AmtDebitedToAcc" type="form61a:UnsignedLong_Type"/>

<xs:element name="AmtCrToAccBfrDemonetization" type="form61a:UnsignedLong_Type"/>

<xs:element name="AmtCrToAccAftrDemonetization" type="form61a:UnsignedLong_Type"/>


<xs:simpleType>




</xs:restriction>

</xs:simpleType></xs:element></xs:sequence>



AmtCreditedToAcc Aggregate gross amount credited to the account in cash during the period.

Validation

AmtDebitedToAcc Aggregate gross amount debited to the account in cash during the period.

Validation

AmtCrToAccBfrDemonetization Aggregate gross amount credited to the account in cash from 1st day of

April, 2016 to 8th November, 2016

Validation

AmtCrToAccAftrDemonetization Aggregate gross amount credited to the account in cash from 9th day of November, 2016 to 30th

Validation


49


day of December, 2016

Remarks Remarks or any other information

Optional


50

27. ComplexType PartCPersonDtl_type

diagram


<xs:complexType name="PartCPersonDtl_type">

<xs:sequence>

<xs:element name="AcctRelationship" type="enum:AcctRelationhip_EnumType"/>

<xs:element name="PersonDtls" type="form61a:PersonDtl_type"/>

</xs:sequence>

</xs:complexType>



AcctRelationship Permissible values for Relationship type are: F - First/Sole Account Holder

S - Second Account Holder

T - Third Account Holder

A - Authorised Signatory C - Controlling Person

Z - Others

X - Not Categorised

Validation

PersonDtls Complete details of each person associated with the transaction

Validation


51

28. ComplexType PartCPersonDtl_type/ personsDtls

diagram

source <xs:complexType name="PersonDtl_type"> <xs:sequence> <xs:element name="NameOfPerson"> <xs:simpleType> <xs:restriction base="form61a:nonEmptyString"> <xs:minLength value="1"/> <xs:maxLength value="125"/> </xs:restriction> </xs:simpleType> </xs:element> <xs:element name="TypeOfPerson" type="enum:NamePerson_EnumType"/> <xs:element name="CustomerID" minOccurs="0"> <xs:simpleType> <xs:restriction base="form61a:nonEmptyString"> <xs:minLength value="1"/> <xs:maxLength value="125"/>

52

</xs:restriction> </xs:simpleType> </xs:element> <xs:element name="Gender" type="enum:Gender_EnumType"/> <xs:element name="FathersName" minOccurs="0"> <xs:simpleType> <xs:restriction base="form61a:nonEmptyString"> <xs:minLength value="1"/> <xs:maxLength value="125"/> </xs:restriction> </xs:simpleType> </xs:element> <xs:element name="PAN" minOccurs="0"> <xs:simpleType> <xs:restriction base="xs:string"> <xs:length value="10"/> <xs:pattern value="[A-Z][A-Z][A-Z][A-Z][A-Z]\d\d\d\d[A-Z]"/> </xs:restriction> </xs:simpleType> </xs:element> <xs:element name="AadhaarNum" minOccurs="0"> <xs:simpleType> <xs:restriction base="xs:string"> <xs:length value="12"/> <xs:pattern value="[0-9]{12}"/> </xs:restriction> </xs:simpleType> </xs:element> <xs:element name="Form60AckNum" minOccurs="0"> <xs:simpleType> <xs:restriction base="form61a:nonEmptyString"> <xs:minLength value="1"/> <xs:maxLength value="75"/> </xs:restriction> </xs:simpleType> </xs:element> <xs:element name="IdentificationType" type="enum:Identification_EnumType" minOccurs="0"/> <xs:element name="IdentificationNum" minOccurs="0"> <xs:simpleType> <xs:restriction base="form61a:nonEmptyString"> <xs:minLength value="1"/> <xs:maxLength value="100"/> </xs:restriction> </xs:simpleType> </xs:element> <xs:element name="DateOfBirthOrIncorp" type="xs:date" minOccurs="0"/> <xs:element name="NationalityOfIncorpDtls" type="iso:CountryCode_Type" minOccurs="0"/>  <xs:element name="BussOrOccupation" minOccurs="0"> <xs:simpleType> <xs:restriction base="form61a:nonEmptyString">


53

<xs:minLength value="1"/> <xs:maxLength value="100"/> </xs:restriction> </xs:simpleType> </xs:element> <xs:element name="AddressDtls" type="form61a:ShortAddressWithAddressTyp_Type" maxOccurs="unbounded"/> <xs:element name="PrimaryContactNo" type="form61a:MobOrLandLineType" minOccurs="0"/> <xs:element name="OtherContactNo" type="form61a:MobOrLandLineType" minOccurs="0"/> <xs:element name="Email" type="form61a:EmailType" minOccurs="0"/> <xs:element name="Remarks" minOccurs="0"> <xs:simpleType> <xs:restriction base="form61a:nonEmptyString"> <xs:minLength value="1"/> <xs:maxLength value="500"/> </xs:restriction> </xs:simpleType> </xs:element> </xs:sequence> </xs:complexType>




TypeOfPerson The permissible values are: IN - Individual



HF - HUF

CR - Private Limited Company CB - Public Limited Company SO - Society


TR - Trust

LI - Liquidator

LL - LLP

ZZ - Others


Validation

CustomerID Customer ID/Number allotted by the reporting entity.

It depends on the type of the reporting entity. For example, in case of banking customerID is mandatory


Gender For individuals only.

Permissible values are: M - Male

F - Female

O – Others

N – Not Applicable (for entities) X – Not Categorised

Validation


54


FathersName For individuals only.

Name of the father (if available). Mandatory if element name = “PAN” is not reported.


PAN Permanent Account Number issued by Income Tax Department.




AadhaarNum For individuals only.

Aadhaar number issued by UIDAI (if available).

If PAN is missing, then it is mandatory to provide AadhaarNum.


Form60AckNum Form 60 Acknowledgment number

(In case the person doesn’t have PAN (refer rule 114B), form 60 will be furnished to reporting entity)


IdentificationType In case “element name= PAN” is not reported a document submitted as proof of identity of the individual.


A - Passport


C - PAN Card



H - NREGA job card

Z – Others


IdentificationNum Number mentioned in the identification document



DateOfBirthOrIncorp Individual: Actual Date of Birth; Company: Date of incorporation; Association of Persons: Date of formation/creation; Trusts: Date of creation of Trust Deed; Partnership Firms: Date of Partnership Deed; LLPs: Date of incorporation/Registration; HUFs: Date of creation of HUF and for ancestral HUF date can be 01-01-0001 where the date of creation is not available.

The data format is YYYY-DD-MM



55



NationalityOfIncorpDtls 2 character Country Code (ISO 3166). Mandatory if element name = “PAN” is not reported.


Nationality 2 character Country Code (ISO 3166). Mandatory if element name = “PAN” is not reported.


BussOrOccupation Business or occupation (if available) Optional


Validation



2 - Residential

3 - Business


5 – Unspecified

Optional




Optional




56

29. ComplexType PartCPersonDtl_type/ personsDtls / Address

diagram





2 - Residential

3 - Business


5 – Unspecified

Optional


57





Validation



Validation


Validation


58

30. ComplexType PartCPersonDtl_type/ personsDtls / PrimaryContactNo

diagram








59

31. ComplexType PartCPersonDtl_type/ personsDtls / OtherContactNo

diagram








60

32. ComplexType PartCPersonDtl_type/ personsDtls / PhoneType

diagram




Validation


Validation


61

33. ComplexType PartDReportDtls_Type

diagram

source <xs:complexType name="PartDReportDtls_Type"> <xs:sequence> <xs:element name="ReportSpec" type="form61a:ReportSpec_Type"/> <xs:element name="PropTransDtls" type="form61a:PropTransDtl_type"/> <xs:element name="Persons" type="form61a:PartDPersonDtl_type" maxOccurs="unbounded"/> </xs:sequence> </xs:complexType>



ReportSpec Captures the details of “element name=ReportSlNo and OriginalRptSlNo”.

Validation

PropTransDtls Contains the details of the transactions. Validation

Persons Contains the person details for each person related to the transaction.

Validation


62


diagram


<xs:complexType name="ReportSpec_Type">

<xs:sequence>

<xs:element name="ReportSlNo" type="xs:unsignedLong"/>

<xs:element name="OriginalRptSlNo" type="xs:unsignedLong"/>

</xs:sequence>




Validation



Validation


63

35. ComplexType TransacDtl_type

diagram

source <xs:complexType name="PropTransDtl_type"> <xs:sequence> <xs:element name="TransDate" type="xs:date"/> <xs:element name="TransID" minOccurs="0"> <xs:simpleType> <xs:restriction base="form61a:nonEmptyString"> <xs:minLength value="1"/> <xs:maxLength value="125"/> </xs:restriction> </xs:simpleType> </xs:element> <xs:element name="TransType" type="enum:Transaction_EnumType"/> <xs:element name="TransAmt" type="form61a:UnsignedLong_Type"/> <xs:element name="PropertyType" type="enum:Property_EnumType"/> <xs:element name="PropMuncipalLimit" type="enum:PropMunicLimit_EnumType"/> <xs:element name="Address" type="form61a:ShortAddress_Type"/> <xs:element name="StampValue" type="form61a:UnsignedLong_Type"/> <xs:element name="Remarks" minOccurs="0"> <xs:simpleType> <xs:restriction base="form61a:nonEmptyString"> <xs:minLength value="1"/> <xs:maxLength value="500"/> </xs:restriction> </xs:simpleType> </xs:element> </xs:sequence> </xs:complexType>



64


TransacDate Date of transaction. The data format is YYYY-DD-MM

Validation

TransactionID Unique ID to identify transaction, if available



TransacType Permissible values are: SP – Sale

GF - Gift

AG - Agreement to Sell

PR - Partition

ST - Settlement

RL - Relinquishment

ER - Extinguishment of any right in the asset

CA - Compulsory acquisition

TP - Transfer as per the section 53A of the Transfer of Property

Act, 1882(4 of 1882).

SH - Transfer by acquisition of shares

ZZ - Others

XX - Not Categorized.

Validation

TransactionAmt Amount of transaction as per registered deed. The amount should be rounded off to nearest rupee without decimal. If this amount is not in Indian Rupees, then convert to Indian Rupees.

Validation

PropertyType The asset underlying the transaction. Permissible values are:

A - Agricultural land

N - Non-agricultural land C - Commercial property R - Residential property

I - Industrial

Z - Others

X - Not Categorized.

Validation

PropMuncipalLimit Whether property is within municipal limits.

Permissible values are: Y - Yes

N - No

X - Not Categorized.

Validation

Address Complete address of property (Optional) Mandatory

StampValue The value for stamp valuation is to be provided.

Validation


65

36. Element PropTransDtl_type/Address

diagram

namespace http://incometaxindiaefiling.gov.in/Form61A

type form61a:ShortAddress_Type

properties content complex

children form61a:AddressFix form61a:City form61a:PostCode form61a:State form61a:CountryCode

source <xs:complexType name="ShortAddress_Type"> <xs:sequence>  <xs:element name="AddressFix" minOccurs="0"> <xs:simpleType> <xs:restriction base="form61a:nonEmptyString"> <xs:minLength value="1"/> <xs:maxLength value="300"/> </xs:restriction> </xs:simpleType> </xs:element> <xs:element name="City" minOccurs="0"> <xs:simpleType> <xs:restriction base="form61a:nonEmptyString"> <xs:minLength value="1"/> <xs:maxLength value="50"/> </xs:restriction> </xs:simpleType> </xs:element> <xs:element name="PostCode" type="form61a:PinCodeType"/> <xs:element name="State" type="iso:StateCode_Type"/> <xs:element name="CountryCode" type="iso:CountryCode_Type"/> </xs:sequence> </xs:complexType>



AddressFix (Optional) Mandatory

CityOrTown Name of City, Town or Village (Optional) Mandatory


66


Validation



Validation


Validation


67

37. ComplexType PartDPersonDtl_type

diagram


<xs:complexType name="PartDPersonDtl_type">

<xs:sequence>

<xs:element name="TransacRelation" type="enum:TransacRelation_EnumType"/>

<xs:element name="TransactionAmt" type="form61a:UnsignedLong_Type" minOccurs="0"/>

<xs:element name="PersonDtls" type="form61a:PersonDtl_Immovable_type"/>

</xs:sequence>



TransacRelation Relation of the person to the transaction.


S - Seller/Transferor

B - Buyer/Transferee

C - Confirming Party

P - Power of Attorney holder

Z - Others

X - Not Categorized

Validation

TransactionAmt Amount of transaction related to the person.

The amount should be rounded off to nearest rupee without decimal. If this amount is not in Indian Rupees, then convert to Indian Rupees.


PersonDetailsDtls Contains the details of person related to the transaction.

Validation


68

38. ComplexType PersonDtl_Immovable_type

diagram

source <xs:complexType name="PersonDtl_Immovable_type"> <xs:sequence> <xs:element name="NameOfPerson"> <xs:simpleType> <xs:restriction base="form61a:nonEmptyString"> <xs:minLength value="1"/> <xs:maxLength value="125"/> </xs:restriction> </xs:simpleType> </xs:element> <xs:element name="TypeOfPerson" type="enum:NamePerson_EnumType"/> <xs:element name="Gender" type="enum:Gender_EnumType"/> <xs:element name="FathersName" minOccurs="0"> <xs:simpleType> <xs:restriction base="form61a:nonEmptyString"> <xs:minLength value="1"/>

69

<xs:maxLength value="125"/> </xs:restriction> </xs:simpleType> </xs:element> <xs:element name="PAN" minOccurs="0"> <xs:simpleType> <xs:restriction base="xs:string"> <xs:length value="10"/> <xs:pattern value="[A-Z][A-Z][A-Z][A-Z][A-Z]\d\d\d\d[A-Z]"/> </xs:restriction> </xs:simpleType> </xs:element> <xs:element name="AadhaarNum" minOccurs="0"> <xs:simpleType> <xs:restriction base="xs:string"> <xs:length value="12"/> <xs:pattern value="[0-9]{12}"/> </xs:restriction> </xs:simpleType> </xs:element> <xs:element name="Form60AckNum" minOccurs="0"> <xs:simpleType> <xs:restriction base="form61a:nonEmptyString"> <xs:minLength value="1"/> <xs:maxLength value="75"/> </xs:restriction> </xs:simpleType> </xs:element> <xs:element name="IdentificationType" type="enum:Identification_EnumType" minOccurs="0"/> <xs:element name="IdentificationNum" minOccurs="0"> <xs:simpleType> <xs:restriction base="form61a:nonEmptyString"> <xs:minLength value="1"/> <xs:maxLength value="100"/> </xs:restriction> </xs:simpleType> </xs:element> <xs:element name="DateOfBirthOrIncorp" type="xs:date" minOccurs="0"/> <xs:element name="NationalityOfIncorpDtls" type="iso:CountryCode_Type" minOccurs="0"/>  <xs:element name="AddressDtls" type="form61a:ShortAddressWithAddressTyp_Type" maxOccurs="unbounded"/> <xs:element name="PrimaryContactNo" type="form61a:MobOrLandLineType" minOccurs="0"/> <xs:element name="OtherContactNo" type="form61a:MobOrLandLineType" minOccurs="0"/> <xs:element name="Email" type="form61a:EmailType" minOccurs="0"/> <xs:element name="Remarks" minOccurs="0"> <xs:simpleType> <xs:restriction base="form61a:nonEmptyString">


70

<xs:minLength value="1"/> <xs:maxLength value="500"/> </xs:restriction> </xs:simpleType> </xs:element> </xs:sequence> </xs:complexType>




TypeOfPerson The permissible values are: IN - Individual



HF - HUF

CR - Private Limited Company

CB - Public Limited Company

SO - Society


TR - Trust

LI - Liquidator

LL - LLP

ZZ - Others


Validation

Gender Only for individuals.

Permissible values are: M - Male

F - Female

O – Others

N – Not Applicable (for entities) X – Not Categorised

Validation

FathersName Name of the father

Mandatory if “element name= PAN” is not reported.


PAN Permanent Account Number issued by Income Tax Department




AadhaarNum Aadhaar number issued by UIDAI (if available). Mandatory if “element name= PAN” is not reported.


Form60AckNum Form 60 Acknowledgment number, if applicable

(In case the person doesn’t have PAN (refer rule 114B), form 60 will be



71


furnished to reporting entity)

IdentificationType Mandatory if “element name= PAN” is not reported.

Document submitted as proof of identity of the individual. Permissible values are:

A - Passport


C - PAN Card



H - NREGA job card

Z – Others


IdentificationNum Number mentioned in the identification document.

Mandatory if “element name= PAN” is not reported..


DateOfBirthOrIncorp Individual: Actual Date of Birth; Company: Date of incorporation; Association of Persons: Date of formation/creation; Trusts: Date of creation of Trust Deed; Partnership Firms: Date of Partnership Deed; LLPs: Date of incorporation/Registration; HUFs: Date of creation of HUF and for ancestral HUF date can be 01-01-0001 where the date of creation is not available.

The data format is YYYY-MM-DD Mandatory if “element name= PAN” is not reported.


NationalityOfIncorpDtls 2 character Country Code (ISO 3166)



Nationality 2 character Country Code (ISO 3166)




Validation




Optional



72




73

39. ComplexType PersonDtl_Immovable_type/ Address

diagram






2 - Residential

Optional


74

3 - Business


5 – Unspecified





Validation



Validation


Validation


75

40. ComplexType PersonDtl_Immovable_type/ PrimaryContactNo

diagram








76

41. ComplexType PersonDtl_Immovable_type/ OtherContactNo

diagram








77

42. ComplexType PersonDtl_Immovable_type/ PhoneType

diagram





Validation


Validation

income tax department - clean money · the income-tax department will publish ... assessmentyear...

Documents