Rectification of Reports

2018
 Overview

• Data Quality Management

• Download Data Quality Report
• Rectification of Reports
• RRC (Report Requiring Correction)

2
Data Quality Management
 Data Quality Management
Upload XML

Reporting
Entity Reporting Portal

• Manifest validation Execute DQR Rules

• File level validations

Generate
• Statement Defects DQR XML
• Report Defects
• Exceptions

Post in
Reporting portal

File Correction Statement

Reporting Portal

4
 Defects & Exceptions

• Defects
– Defects are those which render the record(s)/ statement
invalid
– The reporting entity would be required to file the
correction statement to rectify the defect
• Exceptions
– Exceptions are those which would not result in the
statement/report being rejected
– These only affect the quality of the data.
– However reporting entity should endeavour to rectify the
exceptions
5
 Manifest Level Validations
• Incorrect ITDREIN (40010)
• Incorrect Form Name (40020)
• Incorrect Original Statement ID for CB
(40030)
• Incorrect Original Statement ID for DB
(40031)
• Inconsistent Statement Type ND for
submitted reports (40040)
• Inconsistent Statement Type NB for nil
reports (40041)
• Inconsistent Original Statement ID for new
statement (40050)
• Inconsistent Original Statement ID for No
Data statement (40051)
• Inconsistent Reason for correction for NB
(40060)
• Inconsistent Reason for correction for ND
(40061)
• Inconsistent Reason for correction for CB
(40062)
• Inconsistent Reason for correction for DB
(40063)
• Inconsistent Reporting Period for NB
(40070)
• Inconsistent Reporting Period for CB
(40071)
• Inconsistent Reporting Period for DB
(40073)
• Inconsistent SFT code for CB (40080)
• Inconsistent SFT code for DB (40081)
• Inconsistent Report type - AF (40090)
• Inconsistent Report type – BA (40091)
• Inconsistent Report type - IM (40092)
6
 File Level Defects
• Failed Decryption (50002)
• Failed Decompression (50003)
• Failed Signature Check (50004)
• Failed Threat Scan (50005)
• Failed Virus scan (50006)
• Failed Schema Validation (50007)
• Failed Signature Upload (50011)
• Signature Expired (50012)

7
 Record level Defects
1. Failed Number of Reports for Statement type NB/ND (61A_60040)
2. Failed Original Report Serial Number in CB (61A_60031)
3. Failed Original Report Serial Number in NB (61A_60039)
4. Failed Account Number (61A_60034)
5. Failed Cash deposit addition value (61A_60033)
6. Failed PAN (61A_60047)
7. Failed Report type (61A_60042)
8. Failed Father’s Name (61A_60046)*
9. Failed Form 60 Acknowledgment Number (61A_60049)*
10. Failed Identification Type (61A_60050)*
11. Failed Identification Number(61A_60051)*
12. Failed DOB/DOI (61A_60052)*
13. Failed Birth Date (61A_60014)

* if PAN is not provided

8
 Data Quality Report (DQR) and
Reports Requiring Correction (RRC)
• Data Quality Report (DQR)
– Contains details of the data quality errors present in the
statement submitted by the Reporting Entity.
– Helps Reporting Entity(s) in identifying the errors in data
submitted.  

• Reports Requiring Correction (RRC)

– Number of original reports in the statement where defects
have not been corrected

9
Download Data Quality Report
Download Data Quality Report on
Reporting Portal

• DQR will be in XML format

11
 Download Data Quality Report
through Submission Utility

• User need to provide 15 digit statement Id to download

corresponding DQR.

12
Rectification of Reports
Import DQR & Original Statement in Report
Generation Utility

• Import data quality report and original statement which is to be

corrected in report generation utility
• Statement number mentioned in DQR should match with statement
number of original statement (which is being corrected)
14
 View the Errors

Errors from each report will be highlighted in the Validation Error Details
sidebar.
15
 Select Error to be Corrected

Select the validation error to be rectified and make required changes.

16
 Rectify the Errors

• Save the changes.

17
 Generate Correction Statement
• Update “Part A” by selecting Statement Type as
“CB - Correction statement containing correction
for previously submitted information”.
• Mention the statement ID of the original
Statement which is being corrected in the
“Original Statement ID” field.
• Generate correction XML
• Submit correction statement on reporting portal

18
Reports Requiring Correction
(RRC)
Report Requiring Correction (RRC)
• Report requiring correction (RRC) field will display
the number of reports which are yet to be rectified in
original statement.
• RRC field and count can be viewed under
“Statements Pending for Correction” tab on
reporting portal.
• Reporting entity need to ensure to reduce RRC
(Report Requiring Correction) count to zero by
rectifying all the defective reports.

20
 Correction Logic to Reduce RRC
(Report Requiring Correction) Count
Original Statement
Total Reports : 100 Refer DQR of Original
Accepted Reports : 80 Statement
RRC : 20; Reduced to 10 after
Reference of original 1st Correction; Reduced to 0
statement id (Correction 1) after 2nd Correction

First Correction Statement

Total Reports : 20
Accepted Reports: 10 Refer DQR of First
RRC : 10; Reduced to 0 after Correction
2nd correction

Second Correction Statement

Reference of original statement Total Reports : 10
id (Correction 2) Accepted Reports : 10
RRC : 0
• “Original Statement Id” field of each correction statement should always refer to statement id of
original statement.
• Data Quality Report (DQR) generated on last filed statement (original or correction) should be
referred
• Please refer annexure for use case of “Correction logic to reduce RRC count”. 21
Thank You!!

22
Frequently Asked Questions

23
How many correction statements can
be filed for an original statement?
Multiple correction statements can be
filed for an original statement until the
RRC count reduced to zero. However it is
advised to rectify all the defects in first
correction statement only.

24
Which Statement Id should be
provided in “Original Statement Id”
field while filing correction statement?
In case first ‘Correction’ or sequential
‘Correction’ statement is being filed,
“Original Statement Id” field of each
correction statement should always refer
to statement id of original statement.

25
While rectifying the errors which
DQR should be referred in case of
multiple correction are being filed?
While preparing correction statement,
Data Quality Report (DQR) generated on
respective last filed statement (original or
correction) should be referred.

26
How can file level defects be rectified?

In case statement is rejected due to file

level defects, Reporting entity need
correct and re-submit the entire secure
statement package again.

27
What if reporting entity does not
have PAN of reported person
(defect reported in DQR)?
Reporting entity can rectify this defect by
providing date of birth/ incorporation,
father’s name and any other
identification document of reported
person.

28
Annexure

29
 Correction Logic Explained Through
Use Case
• Let’s assume a reporting entity files an original statement
(Statement Id is 123) which contains total 100 reports (Refer the
table in next slide). However in DQR, 20 reports are found with
defects and this count is posted on reporting portal as RRC
(Reports requiring Correction).
• Reporting entity files first correction statement (Id - 456) to rectify
defects in original statement by giving the reference of the original
statement (Id-123). Reporting entity only rectifies 10 reports and
the other 10 are still found to be defective. Hence update RRC
count will be reduced to (20-10 = 10).
• Reporting entity files second correction statement (Id-789) by
giving the reference of original statement (Id-123) for these 10
defective reports. This time Reporting entity rectifies all 10 reports
as per DQR of this correction statement. RRC count would reduce
to zero. 30
Correction Logic Explained Through
Use Case
Statement Statement Original Total Number of Number of RRC (Reports
Type ID Statement Reports in a accepted Reports Requiring
ID Statement in a Statement Correction)

Original 123 0 100 80 -> 90 ->100 20 -> 10 ->0

(count is updating (RRC count is

after each updating after each
correction is filed) correction is filed)
First 456 123 20 10 10
Correction
Second 789 123 10 10 0
Correction

31