CIBIL Guide

CIBIL%20Guide

User Manual: Pdf

Open the PDF directly: View PDF .
Page Count: 84

Download
Open PDF In Browser	View PDF

Consumer Credit Information System
Guide to Enquiry Input and Response File Format

June 03, 2013
Version 2.12 (TUEF 12)

CREDIT INFORMATION BUREAU (INDIA) LIMITED
In Association with Dun & Bradstreet and TransUnion

© 2013 TransUnion LLC
All Rights Reserved
No part of this publication may be reproduced or distributed in any form or by any means, electronic or otherwise,
now known or hereafter developed, including, but not limited to, the Internet, without the explicit prior written consent
from TransUnion LLC.

Requests for permission to reproduce or distribute any part of, or all of, this publication should be mailed to:
Law Department
TransUnion
555 West Adams
Chicago, Illinois 60661
The “T” logo, TransUnion, and other trademarks, service marks, and logos (the “Trademarks”) used in this publication are registered
or unregistered Trademarks of TransUnion LLC, or their respective owners. Trademarks may not be used for any purpose
whatsoever without the express written permission of the Trademark owner.
transunion.com

Guide to Enquiry Input and Response
File Format
Table of Contents
1.

Overview............................................................................................................................... 1
1.1. Who Should Use This Guide ............................................................................................... 1
1.2. Understanding the Tables in This Guide ............................................................................. 1

Enquiry Record ................................................................................................................... 3
2.1. Required and When Available Segments ............................................................................ 4
2.2. Formatting an Enquiry Record ............................................................................................ 4
2.3. Things to Remember............................................................................................................ 6
2.4. Enquiry Header Segment (TUEF) ....................................................................................... 8
2.5. Name Segment (PN) .......................................................................................................... 11
2.6. Identification Segment (ID) ............................................................................................... 14
2.7. Telephone Segment (PT) ................................................................................................... 17
2.8. Address Segment (PA) ...................................................................................................... 20
2.9. Account Number Segment (PI) ......................................................................................... 23
2.10. End Segment (ES)............................................................................................................ 24

Response Record................................................................................................................ 25
3.1. Reading a Response Record .............................................................................................. 28
3.2. TUEF Response Header Segment...................................................................................... 30
3.3. Name Segment (PN) .......................................................................................................... 31
3.4. Identification Segment (ID) ............................................................................................... 33
3.5. Telephone Segment (PT) ................................................................................................... 34
3.6. Email Contact Segment (EC)............................................................................................. 35
3.7. Employment Segment (EM) .............................................................................................. 36
3.8. Enquiry Account Number Segment (PI) ............................................................................ 38
3.9. Score Segment (SC) ........................................................................................................... 39
3.10. Address Segment (PA) .................................................................................................... 42
3.11. Account Segment (TL) .................................................................................................... 44
3.12. Enquiry Segment (IQ)...................................................................................................... 54
3.13. Consumer Dispute Remarks Segment (DR) (Future Use Segment) ................................ 55
3.14. End Segment (ES)............................................................................................................ 56

Error Record...................................................................................................................... 57
4.1. Error Segment (ERRR) ...................................................................................................... 58
4.2. User Reference Error Segment (UR) ................................................................................. 59
4.3. End Segment (ES).............................................................................................................. 62

Appendix A – Account Type and Enquiry Purpose Table ....................................................... 63
Appendix B – Allowed and Disallowed Characters .................................................................. 65
Appendix C – State / Union Territory Codes ............................................................................ 66
Appendix D – PIN Code Validation Table................................................................................. 67

Consumer Credit Information System / Overview

Appendix E – Classification of Secured and Unsecured Loans ............................................... 69
Appendix F – Score Reason Codes ............................................................................................. 71
Appendix G – Error Codes ......................................................................................................... 73
Appendix H – Error/Dispute Remarks Codes ........................................................................... 77
Appendix I – CIBIL Remarks Codes ......................................................................................... 78
Annexure B ................................................................................................................................... 79

June 03, 2013

Consumer Credit Information System / Overview

1. Overview
This guide describes how to create an Enquiry Record and receive a response from Credit
Information Bureau (India) Limited (CIBIL). The Enquiry Input and Response File Format is
used by members using CPU-to-CPU and Tape-to-Tape modes of transmission to request and
receive Credit Information Reports (CIRs), Individual Information Reports (IIRs), Portfolio
Review Reports, Locate Plus Reports (LP), and Locate Plus for Insurance Reports (LPI). CIBIL
uses the information in the Enquiry Record to generate a response. The response is returned to the
member either as a Machine-Readable Formatted Response Record or as a Print Image Report.
If a member requests the Output Format as Machine-Readable Formatted Response Record and
an error occurs, CIBIL returns an Error Record; a user-friendly error message is returned in case
of a Print Image Report.

1.1. Who Should Use This Guide
This guide must be used by all the people involved in using or developing the Enquiry Format
and understanding or decoding the Response Record received from CIBIL. For the purpose of
this guide, we assume that the reader is familiar with basic computer programming concepts and
terminology.

1.2. Understanding the Tables in This Guide
The tables in this guide describe the segments that make up the Enquiry and Response File
Format. These tables contain all the fields that can make up each segment. The column headings
in these tables are consistent throughout the guide. Each of these column headings is explained in
the following bullet points:
Position
The starting position of a field in a fixed-length segment.
Field Tag
The two-byte tag that identifies each field in a variable-length segment.
Field Name
The name of each field.
Field Type
Fields are classified as one of the following:
Required: Information in these fields must be furnished. Missing or invalid information
in these fields in any of the segments will cause the entire record to be rejected.
When Available: Information in these fields must be furnished when available with the
member. In case the information is not available, members are encouraged to capture the
same information for new accounts and update existing accounts in their database.
See Comments: Special circumstances separate this type of field from the above
classifications. The Comments column in the table explains the special conditions.

June 03, 2013

Consumer Credit Information System / Overview

Character Type
Identifies the type of character appearing in a field. The values that appear in this column are:
A: Alphabetic – only letters are used.
N: Numeric – only whole numbers are used, unless otherwise specified for signed
numeric.
D: Decimal – only one or more digits, followed by “.” (decimal point), then one or more
digits as specified (e.g. 99.27).
A/N: Alphanumeric – letters and numbers can be used.
A/N*: Alphanumeric with space – letters, numbers and spaces can be used.
P: Printable – any printable characters can be used (specifically, ASCII [32-126],
“space”, “–”, “~”).
Length Type
Identifies whether the field is of a fixed length or a variable length. The values that appear in
this column are:
F: Fixed Length – the field must be of the specified byte length.
V: Variable Length – the number of bytes contained in this field is variable, but cannot
exceed the maximum length of the field.
Maximum Length
If the length of a field is fixed, this column shows the number of bytes that the field must
contain. If a field’s length is variable, this column shows the maximum number of bytes that
the field may contain.
Comments
This column contains special instructions and/or specific values (highlighted in bold type)
that can appear in a field. When specific values appear in this field, only those values are
valid.
Date Field
All dates have the format: DDMMYYYY.

June 03, 2013

Consumer Credit Information System / Enquiry Record

2. Enquiry Record
All segments in the Enquiry Record are variable in length except the TUEF and ES segments,
which have fixed lengths. Each segment has a maximum length and minimum and maximum
number of entries.
The following table describes the different segments that make up an Enquiry Record.
These segments appear in an Enquiry Record in the following order: TUEF, PN, ID, PT, PA, PI,
and ES. This order must be followed for every enquiry. Of these, five segments are Required:
TUEF, PN, ID or PT, PA and ES.
Segment
Tag

Segment
Name

Segment
Length

Segment
Type

Number of Entries
Minimum

Maximum

TUEF

TUEF
Enquiry
Header

Fixed

Required

115

Name

Variable

Required

1
++

174

47 each

Identification

Variable

Required

Telephone

Variable

Required++

0++

51 each

Address

Variable

Required*

259 each

Account
Number

Variable

Required**
When
Available

1
0

4
4

36 each

End Segment

Fixed

Required

Note

Maximum
Length

* The current address is always Required, and the Permanent address should be
provided When Available.
** When the Enquiry Purpose (Positions 94-95 of the TUEF Enquiry Header
Segment) is “Account Review”, “Retro Enquiry” or “Locate Plus” then PI is also
a Required segment.
++ At least one of the valid Identification (ID) segment with either Income Tax
ID Number, Passport Number, Voter ID Number or Driver’s License Number, or
valid Telephone (PT) segment should be present except when the Enquiry
Purpose (Positions 94-95 of the TUEF Enquiry Header Segment) is “Account
Review”, “Retro Enquiry” or “Locate Plus”.
Refer to the tables that describe the fields in each segment to determine if a field
is Required, When Available, or See Comments.

June 03, 2013

Consumer Credit Information System / Enquiry Record

2.1. Required and When Available Segments
A segment is either Required or When Available. Required segments must be present in an
Enquiry Record. In the absence or rejection of any of the Required segments, the entire Enquiry
Record is rejected.
When Available segments must be furnished if information is available in the credit application
form/internal system. They provide information that the system can use in conjunction with
Required segments to generate a more accurate and complete response.
For example, Mr. Haren Patel receives his mail at two different addresses, and an enquiry for
Haren Patel contains both of these addresses. The response generated from that Enquiry Record
would logically be more accurate than a response generated from only one address. Refer to the
Maximum Number of Entries column in the preceding table to determine how many times each
segment can occur. When Available segments that exceed the maximum number allowed are
ignored.

2.2. Formatting an Enquiry Record
Fixed length segments contain only fixed-length fields. To format a fixed-length segment, place
the data specified in each field in the correct position.
At the end of each fixed-length segment description, a total byte counter indicates the required
segment length. A fixed-length segment must contain the number of bytes associated with it. This
means that each field in this type of segment is of a specific, fixed length, and not of a variable
length.
Variable-length segments contain both fixed-length and variable-length fields. To format a
variable length segment:
Supply the two-byte tag identifying the field (refer to the Field Tag column in tables of
variable-length segments).
Supply a two-byte length that indicates how many bytes (or characters) are in the field value.
Supply the field value.
For example, the name HAREN PATEL would appear as 0111HAREN PATEL in the Consumer
Name Field1 of the Name Segment (PN). In this example, 01 is the Field Tag and 11 is the Field
Length of the data in the field.
At the end of each variable-length segment description, a counter indicates its maximum possible
length. For example, the Name Segment (PN) can be up to 174 bytes if every field is supplied and
each data element in those fields is of the maximum length. The breakdown of the total 174 bytes
is:
Field

Size

8 two-byte tags (Field Tags PN to 08)

16 bytes

8 two-byte lengths

16 bytes

June 03, 2013

Consumer Credit Information System / Enquiry Record

Field

Size

Sum of all maximum field lengths

142 bytes

Total bytes in PN segment

174 bytes

June 03, 2013

Consumer Credit Information System / Enquiry Record

2.3. Things to Remember
The following information is crucial to properly formatting data and will be observed strictly. The
system will reject all fields that violate the following criteria. Remember that:
Rejected Required fields cause a default value, if any, to be assumed or the entire Enquiry
Record is rejected.
Rejected fields that are not classified as Required cause a default value, if any, to be assumed,
or the field is ignored.
Rejected fields do not help generate accurate credit reports, so please take the time to read and
use the following information:
Alphanumeric (A/N) and Alphabetic (A) fields of a fixed length must be left-justified. Any
open positions in a fixed-length field of these types must be filled with spaces.
Numeric (N) fields of a fixed length must be right-justified. Any open positions in a fixedlength field of this type must be filled with zeros.
If a field contains the wrong type of character, it will be rejected. For example, if an
alphabetic character is reported when the field requires a numeric character, the field is
rejected. The converse is also true.
When values appear in the Comments column, note that these are the only valid values for the
field. Other values will be rejected.
Some field tag numbers are intentionally skipped. For example, in the Name Segment (PN),
Tag 06 is skipped resulting in Tag 07 following Tag 05.
The Date of Birth (DOB) must be a valid calendar date in DDMMYYYY format. For
example, 16022000 is the equivalent of February 16, 2000. The DOB must contain eight
digits; if the field contains fewer than eight digits, the Enquiry Record will be rejected. The
DOB must be more recent than 01011900 and earlier than the system date.
Monetary amounts must be expressed in whole numbers (for example, 1, 51693, 309820).
If the member captures both Current and Permanent addresses for a consumer, then each
address must be reported.
Special edit checks are used to reject an Enquiry Record if any of the following conditions
are detected:
Incomplete or insufficient name and address data. For example, a person called MEHTA
who has an address with only MUMBAI in the Enquiry Record.
Non-individual records.
Overseas addresses.
Each Enquiry Record must begin with a TUEF Enquiry Header Segment (TUEF) and end
with an End Segment (ES), which marks the end of an Enquiry Record.

June 03, 2013

Consumer Credit Information System / Enquiry Record

Joint accounts applicants must be enquired upon separately, as two distinct enquiries. For
example, Mr. Atul E Patel and Mrs. Veena A Patel should be enquired upon as two separate
enquiries – Enquiry 1 - “MR. ATUL E PATEL” and Enquiry 2 - “MRS. VEENA A PATEL.”
This rule is also applicable to enquiries on “Authorised User” or the “Guarantor” to a
consumer.
Annexure B should accompany input files each time when enquiries are submitted to CIBIL.
Incomplete or non-submission of Annexure B can cause a delay in processing.
Input file name should conform to this format:
- .tuef

June 03, 2013

Consumer Credit Information System / Enquiry Record

2.4. Enquiry Header Segment (TUEF)
The TUEF Enquiry Header Segment marks the beginning of the Enquiry Record, and:
It is a Required segment.
It is of a fixed size of 115 bytes.
It can appear only once per Enquiry Record.
All the fields must be provided; otherwise the entire Enquiry Record is rejected.
All fields must be valid.
Position

Field Name

Character
Type

Fixed
Length

Comments

Segment Tag

Must contain the value TUEF.

Version

Must contain the value 12.

Member
Reference
Number

The Member should specify the value to be returned
on the Response Record or the Print Image Report.
Typically, it could be a unique credit
application/reference number.
Any non-printable characters will be replaced by
spaces.

Future Use

Fill with blanks.

Enquiry
Member User
ID

Must contain the Enquiry Member User ID assigned
by CIBIL to the Member.

Enquiry
Password

A/N

Must contain the Enquiry Password assigned by
CIBIL to the Enquiring Member User ID. Any
password with less than 30 characters should be
padded with trailing blanks.

Enquiry Purpose

Please refer to the Account and Enquiry Type values
in Appendix A.

Enquiry Amount

This amount must be a whole number.
If the Enquiry Purpose is other than “Account
Review”, “Retro Enquiry”, “Locate Plus”, or “Locate
Plus for Insurance” then it must be greater than zero.
Zero is permissible for Account Review, Retro
Enquiry, Locate Plus, and Locate Plus for Insurance.
If the Enquiry Purpose is “For Individual”, the
Enquiry Amount will be always reset to 000000000.

105

Future Use

Fill with blanks.

June 03, 2013

Consumer Credit Information System / Enquiry Record

Position

Field Name

Character
Type

Fixed
Length

Comments

108

Score Type

Possible values are:
00 = Not requesting a score.
01 = Requesting the CIBIL TransUnion Score
Version 1.0 (CIBILTUSCR) only.
02 = Requesting the Person Loan Score (PLSCORE)
only.
03 = Requesting both the CIBILTUSCR and
PLSCORE scores.
04 = Requesting the CIBIL TransUnion Score
Version 2.0 (CIBILTUSC2) only.
06 = Requesting both the CIBILTUSC2 and
PLSCORE scores.
Defaults to 00 if none of the available scores is
selected.
If the Enquiry Purpose (Positions 94-95 of the TUEF
Enquiry Header Segment) is “Retro Enquiry” and the
Score Type is 00 or invalid, the Score Type will be
reset to 04.
If the Enquiry Purpose (Positions 94-95 of the TUEF
Enquiry Header Segment) is “Locate Plus”, “Locate
Plus for Insurance” or “For Individual”, the Score
Type will be ignored and always reset to 00.

110

Output Format

Specify the type of response CIBIL should return.
Valid values are:
01 = Machine-Readable Formatted
Response Record
02 = Print Image Report
04 = Tab-delimited Report (This option is currently
not available. If 04 is populated in the input TUEF
string, the system defaults it to 01.)
Defaults to 01 if an invalid value is provided.

112

Response Size

Must contain the value 1.
Defaults to 1 if an invalid value is provided.

113

Input/Output
Media

Specify the input and output media used for the
enquiry. Valid values are:
CC = CPU-to-CPU
TT = Tape-to-Tape
PP = PC(Web)-to-PC(Web)
Account Review, Retro, Locate Plus and Locate Plus
for Insurance Enquiries can use only TT.
When Enquiry Purpose is “For Individual”, PP is the
only acceptable value.

June 03, 2013

Consumer Credit Information System / Enquiry Record

Position

Field Name

Character
Type

Fixed
Length

Comments

115

Authentication
Method

Specify the way to authenticate the Enquiry Member
User ID and the Enquiry Password fields.
Valid values are:
L = Legacy
A = Advanced
Any invalid value provided in this field will be reset
to the value of L.

Total bytes:

June 03, 2013

115

Consumer Credit Information System / Enquiry Record

2.5. Name Segment (PN)
The PN Segment contains information about the consumer applying for credit, and:
It is a Required segment.
It is variable in length and can be a maximum of 174 bytes.
It can appear only once per Enquiry Record.
Tag 06 is reserved for future use.
Field Field
Tag
Name

Field
Type

Character
Type

Length Maximum
Type
Length

Comments

Segment Tag

Required

A/N

Must contain the value N01.

Consumer
Name Field1

Required

Consumer
Name Field2

See
Comments

Consumer name is Required. Use
as many Consumer Name fields as
necessary to provide the complete
consumer name.

Consumer
Name Field3

See
Comments

Consumer
Name Field4

See
Comments

June 03, 2013

The Consumer Name fields must
contain the full name of the
consumer and must have at least
two words. Members are

Consumer Credit Information System / Enquiry Record

Field Field
Tag
Name

Field
Type

Character
Type

Length Maximum
Type
Length

Comments

See
Comments

encouraged to capture and provide
full, expanded names instead of
initials.

Consumer
Name Field5

Disallowed Characters, as
specified in Appendix B, Numbers,
and Commercial Names should not
be entered in any of these fields.
This will lead to a rejection of the
Enquiry Record.
Please refer to the list of Allowed
and Disallowed Characters in
Consumer Name Field1 to Field5
in Appendix B.
Salutations are not considered to be
part of a valid name, though they
may be present.
Do not split name words between
two fields. For example, do not put
“PAT” in Consumer Name Field1
and “EL” in Consumer Name
Field2 to complete the word
PATEL.
When a name word will not fit in
its entirety in one Consumer Name
field, put that word in the next
available Consumer Name field.
In case of the consumer name
consists one word,
father/mother/husband’s name
must be submitted with S/O, W/O
and D/O (e.g. AMIT S/O SUNIL).
Do not truncate names.
07

Date of Birth

See
Comments

Is a Required field for all enquiries,
except when the Enquiry Purpose
(Positions 94-95 of the TUEF
Enquiry Header Segment) is
“Account Review”, “Retro
Enquiry” or “Locate Plus”.
Must contain a valid date in
DDMMYYYY format.
The date in this field must be more
recent than 01011900 and must be
16 years earlier than the system
date.

June 03, 2013

Consumer Credit Information System / Enquiry Record

Field Field
Tag
Name

Field
Type

Character
Type

Length Maximum
Type
Length

Comments

See
Comments

Is a Required field for all enquiries,
except when the Enquiry Purpose
(Positions 94-95 of the TUEF
Enquiry Header Segment) is
“Account Review”, “Retro
Enquiry” or “Locate Plus”.

Gender

Valid values are:
1 = Female
2 = Male
Sum of all maximum byte lengths:

142

Sum of all two-byte tags and two-byte lengths:

Maximum byte size of segment:

174

June 03, 2013

Consumer Credit Information System / Enquiry Record

2.6. Identification Segment (ID)
The ID Segment contains identification information about the consumer applying for credit, and:
This is a Required segment (with ID Type of 01, 02, 03, or 04) when no valid Telephone (PT)
segment is provided except when the Enquiry Purpose (Positions 94-95 of the TUEF Enquiry
Header Segment) is “Account Review”, “Retro Enquiry” or “Locate Plus”.
It is variable in length and can be a maximum of 47 bytes.
This can occur maximum of 8 times per Enquiry Record.
The ID Type(s) should be unique within the same Enquiry Record.
Field
Tag

Field
Name

Field
Type

Character
Type

Length
Type

Maximum
Length

Comments

Segment
Tag

Required

Must contain the value I01.

ID Type

Required

If multiple ID segments are to be
provided the first segment
contains I01, the second contains
I02 and so on up to I08.
N

Indicates the type of ID.
Possible values are:

01 = Income Tax ID Number
(PAN)
02 = Passport Number
03 = Voter ID Number
04 = Driver’s License Number
05 = Ration Card Number
06 = Universal ID Number (UID)
(For Future Use)

07 = Additional ID #1 (For Future
Use)

08 = Additional ID #2 (For Future
Use)

June 03, 2013

Consumer Credit Information System / Enquiry Record

Field
Tag

Field
Name

Field
Type

Character
Type

Length
Type

Maximum
Length

Comments

ID Number

See
Comments

For ID Type 01, Income Tax ID
Number
Permanent Account Number (PAN)
as defined by the Income Tax
department.
For example, ABCPD1234E
If present, must be a minimum of 10
characters (excluding delimiters such
as space, hyphen, etc.).
The first five characters must be
letters, followed by four numbers,
and followed by a letter. The fourth
letter must be either P or H;
otherwise, the PAN will be ignored.
______________________________
For ID Type 02, Passport Number
As defined by the India Security
Press.
For example, A-9388067
If present, must be a minimum of 7
and a maximum of 10 characters
(excluding delimiters such as space,
hyphen, etc.).

The first character must be a
letter, and the remaining
characters must be numbers.
00

June 03, 2013

For ID Type 03, Voter ID Number
Elector’s Photo Identity Card (EPIC)
number, as issued by the Election
Commission.
If present, must be a minimum of 9
characters (excluding delimiters such
as space, hyphen etc.).
Old format:
For example, MT/08/039/0060725
New format:
For example, AAA/999999/0
At least the first two, and no more
than the first three characters must be
letters, and the remaining must be
numbers.
______________________________
For all other ID Types
Is Required when the field is present
in the member’s internal system.
No validation will be performed.

Consumer Credit Information System / Enquiry Record

Field
Tag

Field
Name

Field
Type

Character
Type

Length
Type

Maximum
Length

Sum of all maximum byte lengths:

Sum of all two-byte tags and two-byte lengths:

Maximum byte size of segment:

June 03, 2013

Comments

Consumer Credit Information System / Enquiry Record

2.7. Telephone Segment (PT)
The PT Segment contains the known phone numbers of the consumer, and:
This is a Required segment when no valid Identification (ID) segment with either Income Tax
ID Number, Passport Number, Voter ID Number or Driver’s License Number is provided
except when the Enquiry Purpose (Positions 94-95 of the TUEF Enquiry Header Segment) is
“Account Review”, “Retro Enquiry” or “Locate Plus”.
It is variable in length and can be of a maximum size of 51 bytes.
This can occur maximum of 4 times per Enquiry Record.
Field
Tag

Field
Name

Field
Type

Character
Type

Length
Type

Maximum
Length

Comments

Segment
Tag

Required

Must contain the value T01.

June 03, 2013

If multiple PT segments are to be
provided, the first segment
contains T01, the second contains
T02 and so on.

Consumer Credit Information System / Enquiry Record

Field
Tag

Field
Name

Field
Type

Character
Type

Length
Type

Maximum
Length

Comments

Telephone
Number

Required

Is Required when the field is present
in the member’s internal system and
when the ID segment is not present.
If present, must be a minimum of five
digits.
Telephone numbers must not start
with “1”.
Any Indian mobile telephone number
starting with “6”,”7”,“8” or “9”
requires a minimum of 10 digits.
An International Standard Dialing
(ISD) number requires a minimum of
nine digits.
Multiple telephone numbers are
allowed only if Telephone Type is 00.
If more than one telephone number is
entered when Telephone Type is 00,
they must be separated by delimiters
such as backward slash (\), forward
slash (/), comma (,), colon (:),
semicolon (;) or ampersand (&) sign.

The telephone number identified
in this field with straight
descending/ascending sequence
(e.g., 876543/234567) or same
digits (e.g., 222222) will be edited
out from the input field. Also
when multiple telephone numbers
are provided, a truncated
telephone number at the end of the
field would be edited out as well
(e.g., 5436734,645231,012 3. The
last no. "012 3" is clearly a
truncated no. and this would be
edited out from the input.). Only
the edited Telephone number
would be used for further field
validation.
02

Telephone
Extension

When
Available

A/N

Telephone
Type

Required.

June 03, 2013

Valid types are:
00 = Not Classified
01 = Mobile Phone
02 = Home Phone
03 = Office Phone
Invalid type will be defaulted to 00.

Consumer Credit Information System / Enquiry Record

Field
Tag

Field
Name

Field
Type

Character
Type

Length
Type

Maximum
Length

Sum of all maximum byte lengths:

Sum of all two-byte tags and two-byte lengths:

Maximum byte size of segment:

June 03, 2013

Comments

Consumer Credit Information System / Enquiry Record

2.8. Address Segment (PA)
The PA Segment(s) contain(s) the known address(es) of the consumer, and:
It is a Required segment.
It is variable in length and can be a maximum of 259 bytes.
It occurs at least once, but no more than twice per Enquiry Record. Where possible, enter the
Current Address in the first Address Segment and the Permanent Address in the second
Address Segment.
Field
Tag

Field
Name

Field
Type

Character
Type

Length
Type

Maximum
Length

Comments

Segment
Tag

Required

A/N

Must contain the value A01. If two PA
segments are entered, the first segment
(Current Address) must contain A01,
and the second segment (Permanent
Address) must contain A02 in this
field. If no Current Address is
available, then the Permanent Address
should be entered twice.

Address
Line1

Required

Address
Line2

See
Comments

Address
Line3

See
Comments

Address
Line4

See
Comments

Consumer address is Required. Use as
many Address Line fields as necessary
to provide the complete consumer
address.
It must be a complete address, which
includes within Address Line1 to
Address Line5, the following:
Location, City/Town, and/or District,
State, and PIN Code.

June 03, 2013

Consumer Credit Information System / Enquiry Record

Field
Tag

Field
Name

Field
Type

Character
Type

Length
Type

Maximum
Length

Comments

Address
Line5

See
Comments

Must be a minimum length of 3 for
Address Line1.
Do not split words between two fields.
For example, do not put “FLA” in
Address Line1 and “T” in Address
Line2 to complete the word FLAT.
When a word will not fit in its entirety
in one address line field, put that word
in the next available address line field.
Do not truncate addresses.

Overseas addresses are not
acceptable.
For all enquiries requested except when
the Enquiry Purpose (Positions 94-95
of the TUEF Enquiry Header Segment)
is “Account Review”, “Retro Enquiry”
or “Locate Plus”.
State and PIN Code are Required
within Address Line1 – Line5, if they
are not provided separately in fields
State Code (Field Tag 06) and PIN
Code (Field Tag 07), respectively.
06

State Code

June 03, 2013

Required

Is a Required field, except when the
Enquiry Purpose (Positions 94-95 of
the TUEF Enquiry Header Segment
(TUEF)) is “Account Review”, “Retro
Enquiry” or “Locate Plus”.
For APO address, if this field is a
Required field, then the State Code
must be provided. If the State Code is
not known, then it should be set to 99.
Please enter the 2-digit code for the
State / Union Territory as specified in
Appendix C.
State Code will take precedence over
the State name in the Address Line1 to
Address Line5, if both are provided.

Consumer Credit Information System / Enquiry Record

Field
Tag

Field
Name

Field
Type

Character
Type

Length
Type

Maximum
Length

Comments

PIN Code

Required

Is a Required field, except when the
Enquiry Purpose (Positions 94-95 of
the TUEF Enquiry Header Segment
(TUEF)) is “Account Review”, “Retro
Enquiry” or “Locate Plus”.
If present, all characters other than the
digits 0-9 shall be stripped out. The
remaining value must be exactly 6
digits long, and the last three digits
must not be all zeroes (“000”).
However, for APO address, if this field
is a Required field, then the PIN Code
must be provided. If the PIN Code is
not known, then it should be set to
900000.
For example, all of the following are
valid PIN codes: “604002”, “604002”,
“604-002”, “900000”, “900 000”.
The following are NOT valid PIN
codes: “604”, “604000”,
“6040020000”, “0000604002”,
“901234”.
Please refer to Appendix D for
additional information on PIN Code
validation.
PIN Code provided in this field will
take precedence over the (free-format)
PIN Code provided in the Address
Line1 to Address Line5, if both are
provided.

Address
Category

Required

Valid values are:
01 = Permanent Address
02 = Residence Address
03 = Office Address
04 = Not Categorized

Invalid value will be defaulted to 04.
09

Residence
Code

When
Available

Sum of all maximum byte lengths:

219

Sum of all two-byte tags and two-byte lengths:

Maximum byte size of segment:

259

June 03, 2013

Valid values are:
01 = Owned
02 = Rented

Consumer Credit Information System / Enquiry Record

2.9. Account Number Segment (PI)
The PI Segment(s) contain(s) the account number(s) of account(s) that the consumer has with
other member(s) and/or the Enquiring Member itself, and:
It is a Required segment if the Enquiry Purpose (Positions 94-95 of the TUEF Enquiry
Header Segment) is “Locate Plus”, “Account Review” or “Retro Enquiry,” for all other
enquiries it is a When Available segment.
It is variable in length and can be of a maximum size of 36 bytes.
It occurs no more than 4 times per Enquiry Record.
Field Field
Tag
Name

Field
Type

Character
Type

Length
Type

Maximum
Length

Comments

Segment
Tag

Required

A/N

Must contain the value I01. If two,
three, or four account segments are
entered, the first segment tag must
contain I01, second must contain I02,
the third I03, and the fourth I04.

Account
Number

Required

Must contain only account number of
loans/advances or credit card numbers
and not current/savings/deposit account
numbers.
Please note that when the Enquiry
Purpose (Positions 94-95 of the TUEF
Enquiry Header Segment (TUEF)) is
“Account Review”, “Retro Enquiry”, or
“Locate Plus”, the account number must
be provided and should be the same as
provided to CIBIL during data
submission.

Sum of all maximum byte lengths:

Sum of all two-byte tags and two-byte lengths:

Maximum byte size of segment:

June 03, 2013

Consumer Credit Information System / Enquiry Record

2.10. End Segment (ES)
The ES Segment marks the end of the Enquiry Record, and:
It is a Required segment.
It is of a fixed size of 15 bytes.
It can appear only once per Enquiry Record.
Position

Field Name

Character
Type

Fixed
Length

Comments

Length of
Record

A/N

Must contain the value ES05NNNNN, where NNNNN is
the total length of the Enquiry Record (including the End
Segment (ES)), left-padded with zeros.

End Characters

Must contain the value 0102 followed by two asterisks
(**).

Total bytes

June 03, 2013

Consumer Credit Information System / Response Record

3. Response Record
The Response Record is a variable length Machine-Readable Formatted Response Record and is
generated only when the value in the Output Format Field (Positions 110-111 of the TUEF
Enquiry Header Segment) in the Enquiry Record is 01.
The following table describes the segments that make up the Response Record. All segments are
variable in length except the TUEF and ES Segments, which have fixed lengths. Each segment
has a maximum length, and a minimum and maximum number of entries. These segments appear
on a Response Record in the following order: TUEF, PN, ID, PT, EC, EM, PI, SC, PA, TL, IQ,
DR and ES.
Segment
Tag

Segment
Name

Segment
Type

No. of Entries

Maximum
Length

Minimum

Maximum

TUEF

TUEF
Response
Header

Fixed

Name

Variable

253

Identification

Variable

76 each

Telephone

Variable

56 each

Unlimited***
EC

Variable

EM**

Employment

Variable

127

PI*

Enquiry
Account
Number

Variable

36 each

SC**

Score

Variable

476 each

Address

Variable

1
0***

4
Unlimited***

296 each

TL**

Account

Variable

Unlimited

516 each

Enquiry

Variable

Unlimited

59 each

Consumer
Dispute
Remarks

Variable

463 each

End

Fixed

Note

June 03, 2013

Email
Contact

81 each

Unlimited***

* When the Enquiry Purpose (Positions 94-95 of the TUEF Enquiry Header
Segment) is “Locate Plus” then PI is also a Required segment. When the Enquiry
Purpose is "Locate Plus for Insurance" then PI is returned if it is submitted in the
request with valid value. This segment is not applicable to all other enquiry
purposes.

Consumer Credit Information System / Response Record

** These segments (EM, SC and TL) are not applicable to “Locate Plus” or
"Locate Plus for Insurance" enquiries. The SC segment is not applicable to “For
Individual” enquiries.
*** When the Enquiry Purpose (Positions 94-95 of the TUEF Enquiry Header
Segment) is “Locate Plus” or "Locate Plus for Insurance" then the maximum no.
of entries for these segments is unlimited and the minimum is 0 (when it is a nohit report). For all other enquiry purposes the maximum no. of entries is 4 and the
minimum is 1.
For a Portfolio Review Response Record, the Account Segment (TL) is divided into five parts:
Account Segment (Details for Own Accounts, if available)
Account Segment Summary (Summary for Other Live Accounts)
Account Segment Details (Details for Other Live Accounts, if available)
Account Segment Summary (Summary for Other Closed Accounts)
Account Segment Details (Details for Other Closed Accounts, if available)
The following table describes the Account Segment (TL) components in Portfolio Review.
Segment Segment
Tag
Name

Segment
Type

Number of Entries

Maximum
Length

Minimum

Maximum

Own Accounts

Variable

Unlimited

516 each

Summary of
Other Live
Accounts

Variable

106 each

Details of Other
Live Accounts

Variable

Unlimited

300 each

Summary of
Closed Live
Accounts

Variable

106 each

Details of Other
Closed Accounts

Variable

Unlimited

300 each

It is important to remember the following for the purpose of Portfolio Review:
Own Accounts: Details of accounts reported by the Enquiring Member. For example, when
XYZ Bank is doing a Portfolio Review, the details of all the accounts reported by XYZ Bank
for that borrower will be displayed in the same format as displayed in the Credit Information
Report.
Other Accounts: Details of accounts not reported by the Enquiring Member. The details of
other accounts are provided in two parts: live accounts and closed accounts. The live and
closed accounts are further classified into Secured and Unsecured Loans.
Live Accounts: All accounts that do not have a value reported in the field Date Closed (Field
Tag 10, TL Segment).

June 03, 2013

Consumer Credit Information System / Response Record

Closed Accounts: All accounts that have a value reported in the field Date Closed (Field Tag
10, TL Segment).
Classification of Secured and Unsecured Loans: In case of accounts not reported by the
Enquiring Member, “loan types” would be reported as Secured or Unsecured Loans as
classified in Appendix E.
Account Segment Summary: The summary segment will contain a count and summation of
the High/Credit Sanctioned Amount and Current Balance of Secured and Unsecured Loans.
This summary will be shown separately for Live and Closed accounts.

June 03, 2013

Consumer Credit Information System / Response Record

3.1. Reading a Response Record
Reading a fixed-length segment in a Response Record requires finding each field’s specified
position in that segment. At the end of each fixed-length segment description, a total byte counter
indicates how long each of these segments must be. A fixed-length segment contains the specified
number of bytes associated with it. This means that each field in this type of segment is of a
specific, fixed length and not of a variable length.
Reading a variable-length segment requires finding each field’s tag and length in order to identify
the value in that field. For example, to find the Date Reported and Certified field in the Account
segment:
Locate the Account Segment Tag (TL) in the Response Record. The Account Segment
follows the last Address Segment (PA).
Locate Tag 11, the Date Reported and Certified field in the Account Segment (TL).
Immediately following the field tag is the field’s length. Because this is a date field, the
length is always 08. These two together appear as 1108, with 11 being the Field Tag and 08
being the Field Length.
The value of the field follows the field tag and field length. If the account was reported on
September 25, 2000 then the date would appear as 25092000.
The Date Reported and Certified field in the Account Segment (TL) appears as
110825092000.
At the end of each variable length segment description, a counter indicates the maximum length
of the segment. For example, the Account Segment (TL) can be a maximum of 516 bytes if every
field is supplied and each data element in those fields is the maximum length. The breakdown of
the total 516 bytes is:
Field

Size

36 two-byte tags (Field Tags TL to 99)

72 bytes

36 two-byte lengths

72 bytes

Sum of all maximum field lengths

368 bytes

Total bytes in TL segment

516 bytes

It is also important to remember that:
When the system does not find the enquired subject during the enquiry process, a no-hit
report is returned.
If the Enquiry Purpose (Positions 94-95 of the TUEF Enquiry Header Segment) is not
“Account Review”, “Retro Enquiry”, “Locate Plus”, or "Locate Plus for Insurance", then
the consumer is added as a new subject to the CIBIL database.
This enquiry made on the consumer is displayed in response to future enquiries made on
the same consumer. The details of the “no-hit” enquiry will be returned the next time a
credit report is requested for the consumer.

June 03, 2013

Consumer Credit Information System / Response Record

All dates in the Response Record are in DDMMYYYY format. For example, 16022000 is the
equivalent of February 16, 2000.
Some fields in the Response Record contain specific values. These values are listed in the
Comments column of the following tables.

June 03, 2013

Consumer Credit Information System / Response Record

3.2. TUEF Response Header Segment
The TUEF Response Header Segment marks the beginning of the Response Record, and:
It is of a fixed size of 94 bytes.
It can appear only once per Response Record.
Position

Field Name

Character
Type

Fixed
Length

Comments

Segment Tag

Contains the value TUEF.

Version

Contains the value 12.

Member
Reference
Number

A/N

Contains the value supplied by the Member in the TUEF
Enquiry Header Segment of the Enquiry Record. Filled with
blanks if the value was not supplied.

Future Use

Filled with blanks.

Future Use

Filled with zeros.

Enquiry
Member User
ID

Contains the Enquiry Member User ID supplied by the
Member in the TUEF Enquiry Header Segment of the
Enquiry Record.

Subject Return
Code

Valid values are:
0 = Not found
1 = Found

Enquiry
Control
Number

Contains a system-generated enquiry control number.

Date
Processed

Contains the date when the enquiry was made.
Format is DDMMYYYY.

Time
Processed

Contains the time when the enquiry was made.
Format is HHMMSS.

Total bytes:

June 03, 2013

Consumer Credit Information System / Response Record

3.3. Name Segment (PN)
The PN Segment contains information about the consumer applying for credit, and:
It is variable in length and can be of a maximum size of 253 bytes.
It can appear only once per Response Record.
Tag 06 is reserved for future use.
Field
Tag

Field Name

Character
Type

Length
Type

Maximum
Length

Comments

Segment Tag

A/N

Contains the value N01.

Consumer
Name Field1

Consumer
Name Field2

Consumer
Name Field3

Consumer
Name Field4

Consumer
Name Field5

Date of Birth

Format is DDMMYYYY.

Gender

Values are:
1 = Female
2 = Male

Date of Entry
for Error Code

Contains the date when the error code was
entered. Format is DDMMYYYY. (Future Use
Field)

Error Segment
Tag

Error segment tag registered within the
error/dispute resolution process.
This field will contain a value of “ZZ” in case if
there are errors/disputes across multiple
segments or if there are no errors/disputes.
Otherwise, the segment tag as per TUDF Guide
should be used (e.g. PA for the Address
segment). (Future Use Field)

Error Code

Error Code registered within the error/dispute
resolution process.
Refer to Appendix G for list of codes. (Future
Use Field)

Date of Entry
for CIBIL
Remarks Code

Contains the date when the CIBIL remarks code
was entered. Format is DDMMYYYY. (Future
Use Field)

CIBIL Remarks
Code

A/N

Refer to Appendix I for list of codes. (Future
Use Field)

June 03, 2013

Consumer Credit Information System / Response Record

Field
Tag

Field Name

Character
Type

Length
Type

Maximum
Length

Comments

Date of Entry
for
Error/Dispute
Remarks Code

Contains the date when the error/dispute
remarks codes were entered. Format is
DDMMYYYY. (Future Use Field)

Error/Dispute
Remarks Code
1

A/N

Contains up to 2 error/dispute remarks codes.
Refer to Appendix H for list of codes. (Future
Use Field)

Error/Dispute
Remarks Code
2

A/N

Sum of all maximum byte lengths:

189

Sum of all two-byte tags and two-byte lengths:

Maximum byte size of segment:

253

June 03, 2013

Consumer Credit Information System / Response Record

3.4. Identification Segment (ID)
The ID Segment(s) contain(s) the known identification numbers of the consumer applying for
credit, and:
It is variable in length and can be of a maximum size of 76 bytes.
It can occur up to 8 times per Response Record with maximum of one segment per ID Type.
Field
Tag

Field Name

Character
Type

Length
Type

Maximum
Length

Comments

Segment Tag

Contains the value I01. If multiple ID
segments are returned, the first segment
contains I01, the second contains I02, and so
on up to I08.

ID Type

Values are:
01 = Income Tax ID Number (PAN)
02 = Passport Number
03 = Voter ID Number
04 = Driver’s License Number
05 = Ration Card Number
06 = Universal ID Number (UID)
07 = Additional ID #1 (For Future Use)
08 = Additional ID #2 (For Future Use)

ID Number

Issue Date

Format is DDMMYYYY.

Expiration Date

Format is DDMMYYYY.

Enriched
Through Enquiry

Only the value of Y is returned when
applicable. (Future Use Field)

Sum of all maximum byte lengths:

Sum of all two-byte tags and two-byte lengths:

Maximum byte size of segment:

June 03, 2013

Consumer Credit Information System / Response Record

3.5. Telephone Segment (PT)
The PT Segment(s) contain(s) the known telephone numbers of the consumer applying for credit,
and:
It is variable in length and can be of a maximum size of 56 bytes.
It can occur up to 4 times per Response Record for all enquiries except when enquiry purpose
is “Locate Plus” or “Locate Plus for Insurance”.
Field
Tag

Field Name

Character
Type

Length
Type

Maximum
Length

Comments

Segment Tag

Contains the value T01. If multiple PT
segments are returned, the first segment
contains T01, the second contains T02, and
so on up to T04.

Telephone
Number

Telephone
Extension

A/N

Telephone Type

Types are:
00 = Not Classified
01 = Mobile Phone
02 = Home Phone
03 = Office Phone

Enriched
Through Enquiry

Sum of all maximum byte lengths:

Sum of all two-byte tags and two-byte lengths:

Maximum byte size of segment:

June 03, 2013

Only the value of Y is returned when
applicable. (Future Use Field)

Consumer Credit Information System / Response Record

3.6. Email Contact Segment (EC)
The EC Segment(s) contain(s) the known email addresses of the consumer applying for credit,
and:
It is variable in length and can be of a maximum size of 81 bytes.
It can occur up to 4 times per Response Record for all enquiries except when enquiry purpose
is “Locate Plus” or “Locate Plus for Insurance”.
Field
Tag

Field Name

Character
Type

Length
Type

Maximum
Length

Comments

Segment Tag

Contains the value C01. If multiple EC
segments are returned, the first segment
contains C01, the second contains C02, and
so on up to C04.

E-Mail ID

Sum of all maximum byte lengths:

Sum of all two-byte tags and two-byte lengths:

Maximum byte size of segment:

June 03, 2013

Consumer Credit Information System / Response Record

3.7. Employment Segment (EM)
The EM Segment(s) contain(s) the known employment related information of the consumer
applying for credit, and:
It is variable in length and can be of a maximum size of 127 bytes.
It can occur once per Response Record.
The employment segment is not applicable to Locate Plus or Locate Plus for Insurance enquiries.
Field
Tag

Field Name

Character
Type

Length
Type

Maximum
Length

Comments

Segment Tag

Must contain the value E01.

Account Type

Please refer to the Account and Enquiry
Type values in Appendix A.

Date Reported and
Certified

This is the most recent date the Reporting
Member reported and certified information
about the employment related information to
CIBIL.
Format is DDMMYYYY.

Occupation Code

Codes are:
01 = Salaried
02 = Self Employed Professional.
03 = Self Employed
04 = Others

Income

Net/Gross Income
Indicator

Values are :
G = Gross Income
N = Net Income

Monthly/Annual
Income Indicator

Values are :
M = Monthly
A = Annual

Date of Entry for
Error Code

Contains the date when the error code was
entered. Format is DDMMYYYY. (Future
Use Field)

Error Code

Error Code registered within the
error/dispute resolution process.
Refer to Appendix G for list of codes.
(Future Use Field)

Date of Entry for
CIBIL Remarks
Code

Contains the date when the CIBIL remarks
code was entered. Format is DDMMYYYY.
(Future Use Field)

June 03, 2013

Consumer Credit Information System / Response Record

Field
Tag

Field Name

Character
Type

Length
Type

Maximum
Length

Comments

CIBIL Remarks
Code

A/N

Refer to Appendix I for list of codes.
(Future Use Field)

Date of Entry for
Error/Dispute
Remarks Code

Contains the date when the error/dispute
remarks codes were entered. Format is
DDMMYYYY. (Future Use Field)

Error/Dispute
Remarks Code 1

A/N

Error/Dispute
Remarks Code 2

A/N

Contains up to 2 error/dispute remarks
codes.
Refer to Appendix H for list of codes.
(Future Use Field)

Sum of all maximum byte lengths:

Sum of all two-byte tags and two-byte lengths:

Maximum byte size of segment:

127

June 03, 2013

Consumer Credit Information System / Response Record

3.8. Enquiry Account Number Segment (PI)
The PI Segment(s) contain(s) the account number(s) of account(s) provided by the TUEF request,
and:
It is a Required segment if the Enquiry Purpose is “Locate Plus”. It is a When Available if the
Enquiry Purpose is "Locate Plus for Insurance". This segment is not applicable to all other
enquiries.
It is variable in length and can be of a maximum size of 36 bytes.
It can occur up to 4 times per Response Record.
Field Field
Tag
Name

Field
Type

Character
Type

Length
Type

Maximum
Length

Comments

Segment
Tag

Required

A/N

Contains the value I01. If multiple
Enquiry Account Enquiry segments
are returned, the first segment
contains I01, the second contains I02,
the third contains I03, and the fourth
I04.

Account
Number

Required

Contains the account no. as provided
in the PI segment in the TUEF
request.

Sum of all maximum byte lengths:

Sum of all two-byte tags and two-byte lengths:

Maximum byte size of segment:

June 03, 2013

Consumer Credit Information System / Response Record

3.9. Score Segment (SC)
The three major components of the Score segment are:
Score (Tag 04)
Reason Codes (Tags 25-29)
Exclusion Codes (Tags 05-14)
The score segment appears up to two per Response Record. For more information on the score,
please see the guides Understanding the CIBIL TransUnion Score (CIBILTUSCR and
CIBILTUSC2) and Understanding the CIBIL TransUnion Personal Loan Score (PLSCORE).
The score segment is not applicable to "Locate Plus", "Locate Plus for Insurance", and “For
Individual” enquiries.
The Output String contains the following format:
Field
Tag

Field Name

Character
Type

Length
Type

Maximum
Length

Comments

Score Name

A/N

CIBIL TransUnion Score Name.
Possible names are:
CIBILTUSCR for CIBIL TransUnion Score
Version 1.0
PLSCORE for Personal Loan Score
CIBILTUSC2 for CIBIL TransUnion Score
Version 2.0

Score Card Name

Values are:
01 for CIBILTUSCR
02 for PLSCORE
04 for CIBILTUSC2

Score Card
Version

Contains the value 10.

Score Date

Current date on which the score is generated.
Format: DDMMYYYY.

June 03, 2013

Consumer Credit Information System / Response Record

Field
Tag

Field Name

Character
Type

Length
Type

Maximum
Length

Comments

Score

For CIBIL TransUnion Score Version 1.0 Score range is between 300 and 900; two
zeroes (00) prefix the score, but in some
cases score can be 0 or -1. -1 for No-Hit or
subject with only enquiries and 0 for subjects
where the earliest open trade is less than six
months old across all channels or there is a
error code.
For CIBIL TransUnion Score Version 2.0 Score range is between 300 and 900 for
consumers with more than 6 months of credit
history*; for others (new to credit subjects
with less than 6 months credit history*) the
score range can be between 1 and 5.
Two zeroes (00) prefix the score when the
range is between 300 to 900.
A score of -1 is returned for subjects that are
new to credit or do not have enough
information to score*.
A score of 0 is returned for subjects when
there is an error.
Example: The score of 3 is returned as 00003
in the output string. The score 456 is
formatted as 00456 in the output string. The
value -1 is returned as 000-1 in the output
string.
*At least one live tradeline with information
updated, or closed date populated in the last
24 months is required.

Exclusion Code 1

A/N

One or more trades with suit filed status in
the past 24 months.
A value of 01 when this exclusion is applied.

Exclusion Code 2

A/N

Exclusion Code 3

A/N

One or more trades with wilful default status
in the past 24 months.
A value of 01 when this exclusion is applied.
One or more trades with suit filed (wilful
default) status in the past 24 months.
A value of 01 when this exclusion is applied.

Exclusion Code 4

A/N

One or more trades written off in the past 24
months.
A value of 01 when this exclusion is applied.

Exclusion Code 5

A/N

One or more trades with suit filed and written
off status in the past 24 months.
A value of 01 when this exclusion is applied.

Exclusion Code 6

A/N

One or more trades with wilful default and
written off status in the past 24 months.
A value of 01 when this exclusion is applied.

June 03, 2013

Consumer Credit Information System / Response Record

Field
Tag

Field Name

Character
Type

Length
Type

Maximum
Length

Comments

Exclusion Code 7

A/N

One or more trades with suit filed (wilful
default) and written off status in the past 24
months.
A value of 01 when this exclusion is applied.

Exclusion Code 8

A/N

No eligible trade for scoring.
A value of 01 when this exclusion is applied.
Please note that the Exclusion Code 8 is
applicable to Personal Score (PLSCORE)
only.

Exclusion Code 9

A/N

One or more trades with restructured debt in
the past 24 months.
A value of 01 when this exclusion is applied.

Exclusion Code
10

A/N

One or more trades with settled debt in the
past 24 months.
A value of 01 when this exclusion is applied.

Tags 15 - 24 are fixed and defined for additional Exclusion Codes (10) for future use.
25

Reason Code 1

A/N

Reason Code 2

A/N

Reason Code 3

A/N

Reason Code 4

A/N

Reason Code 5

A/N

A reason code is an explanation of a specific
credit factor that can be improved.
Up to five reason codes can be returned.
Refer to Appendix F for the list of reason
codes.

Tags 30 - 74 are fixed and defined for additional reason codes (45) for future use.
75

Error Code

Sum of all maximum byte lengths:

172

Sum of all two-byte tags and two-byte lengths:

304

Maximum byte size of segment:

476

June 03, 2013

This tag is only returned when error is
encountered. Possible values are:
00001 = FID Not Found
00002 = Duplicate FID
00003 = Error related to Consumer Data
Issue
00004 = Error related to Database Issue
00005 = Error during score calculation

Consumer Credit Information System / Response Record

3.10. Address Segment (PA)
The PA Segment(s) contain(s) the known address(es) of the consumer applying for credit, and:
It is variable in length and can be of a maximum size of 296 bytes.
Tag 11 is returned only when enquiry purpose is “Locate Plus” or "Locate Plus for
Insurance". This tag is not applicable to all other enquiry purposes.
It occurs at least once but no more than 4 times, per Response Record for all enquiries except
when enquiry purpose is “Locate Plus” or “Locate Plus for Insurance”.
For enquiry when enquiry purpose is “Locate Plus” or “Locate Plus for Insurance”, this
segment is not required when it is a no-hit report, otherwise it occurs with no limit.
Field
Tag

Field Name

Character
Type

Length Maximum
Type
Length

Comments

Segment Tag

A/N

Contains the value A01. If multiple PA
segments are returned, the first segment
contains A01, the second contains A02, and so
on up to A04.
When Enquiry Purpose is “Locate Plus” or
“Locate Plus for Insurance”, this field will
contain A99 for all PA segments beyond the
first 99 PA segments.

Address Line1

Address Line2

Address Line3

Address Line4

Address Line5

State Code

PIN Code

Address
Category

Values are:
01 = Permanent Address
02 = Residence Address
03 = Office Address
04 = Not Categorized

Residence Code

Values are:
01 = Owned
02 = Rented

Date Reported

The date when this address was first reported to
CIBIL by any Member.
Format is DDMMYYYY.

June 03, 2013

Please refer to the list of State/Union Territory
Codes appearing in Appendix C.

Consumer Credit Information System / Response Record

Field
Tag

Field Name

Character
Type

Length Maximum
Type
Length

Comments

Member Short
Name

A/N*

When Enquiry Purpose is “Locate Plus” or
“Locate Plus for Insurance”, this field contains
the member short name of this reported address.
For “Locate Plus” and “Locate Plus for
Insurance”, those members who request that
their name not be disclosed, the value returned
will be “Not Disclosed.”
For “Locate Plus” and “Locate Plus for
Insurance” it will only display the Short Name
of the member when the enquiry has been made
by the member itself.
For all other Enquiry Purposes, this tag is not
applicable.

Enriched
Through Enquiry

Only the value of Y is returned when
applicable. (Future Use Field)

Sum of all maximum byte lengths:

244

Sum of all two-byte tags and two-byte lengths:

Maximum byte size of segment:

296

June 03, 2013

Consumer Credit Information System / Response Record

3.11. Account Segment (TL)
The TL Segment contains the credit information of the consumer applying for credit, and:
It is variable in length and can be of a maximum size of 516 bytes.
It can appear unlimited number of times per Response Record.
Ordering of TL segments will be based on Account Group in descending order, then Account
Type in ascending order, and finally Date Opened/Disbursed in descending order (i.e. more
recently opened accounts first).
Tags 01, 06, 07 and 15-27 are reserved for future use.
The account segment is not applicable to Locate Plus or Locate Plus for Insurance enquiries.

Note

The following table also describes the Accounts Segment (Own Accounts)
segment of the Accounts Segment in a Portfolio Review Response Record.

Field
Tag

Field Name

Character
Type

Length
Type

Maximum
Length

Comments

Segment Tag

A/N

Contains the value T001. If multiple TL
segments are returned, the first segment
contains T001, the second contains T002, and
so on.
This field will contain T999 for all TL
segments beyond the first 999 TL segments.

Reporting
Member Short
Name

A/N*

This field will contain the Short Name of the
Reporting Member who reported this
Account.
For Reporting Members who request that their
names should not be disclosed, the value
returned will be “Not Disclosed.”
However, it will display the Short Name of
the member for accounts reported by itself.
If the enquiry purpose is “For Individual”, the
rules above will not apply and the Short Name
of the Reporting Member will always be
shown.

Account Number

This field will contain the Account Number of
the consumer if the credit has been obtained
from the Member itself or else the field will
be suppressed.
If the enquiry purpose is “For Individual”, the
account number will always be shown and
will be masked. The Account Number will
show "X" for all but the last four
alphabets/digits, i.e. "XXXX4321" for
account number "987654321". The account
number will be left-padded with zeros if less
than 4 digits, i.e. "XXXX0012" for account
number "12".

June 03, 2013

Consumer Credit Information System / Response Record

Field
Tag

Field Name

Character
Type

Length
Type

Maximum
Length

Comments

Account Type

Please refer to the Account and Enquiry Type
values in Appendix A.

Ownership
Indicator

Valid values are:
1 = Individual
2 = Authorised User (refers to
supplementary credit card holder)
3 = Guarantor
4 = Joint

Date
Opened/Disburse
d

This is the date of first disbursement of the
account.
For Credit/Fleet cards, this is the date the card
becomes active.
Format is DDMMYYYY.

Date of Last
Payment

This is the most recent date a payment was
made on the account.
Format is DDMMYYYY.

Date Closed

This is the date the account was closed.
Format is DDMMYYYY.

Date Reported
and Certified

This is the most recent date the Reporting
Member reported and certified information
about the account to CIBIL.
Format is DDMMYYYY.

High
Credit/Sanctioned
Amount

For Credit Card (Account Type 10) and Fleet
Card (Account Type 16), this field contains
the highest amount of credit used in the
history of the account.
For all other accounts, this field contains the
amount of loan sanctioned.
This amount is a whole number and is
assumed to be positive.

Current Balance

The entire amount of credit/loan outstanding,
including the current and overdue portion, if
any, together with interest last applied, as of
the date reported in the Date Reported and
Certified field.
This amount is a whole number and could be
either positive (+) with a debit balance or
negative (-) with a credit balance. If the
balance is zero, it will report as 0.
If a sign appears in this field, it will appear at
the beginning of the field. If no sign appears,
we assume it to be positive.

June 03, 2013

Consumer Credit Information System / Response Record

Field
Tag

Field Name

Character
Type

Length
Type

Maximum
Length

Comments

Amount Overdue

The amount past due as of the date reported in
the Date Reported and Certified field.
This amount is a whole number and is
assumed to be positive.

Payment History
1

A/N

The most recent 18 months of Payment
History. Each month displays the Number of
Days Past Due (NDPD)/Asset Classification
(AC) for that month. The first value in the
payment history string is the NDPD/AC, as of
the date reported in the Date Reported and
Certified field.
For accounts that are closed and where the
Date Closed field is provided, the first value
in the payment history string is the
NDPD/AC, as of the date reported in the Date
Closed field.
If the value for a month is reported as XXX, it
means the Reporting Member did not report
data for that account for that particular month.
If, instead of NDPD, AC is reported, the
following values will be displayed:
STD = Standard
SMA = Special Mention Account
SUB = Substandard
DBT = Doubtful
LSS = Loss
XXX = Not Reported

Payment History
2

A/N

Up to 18 remaining previous months in the
Payment History. Each month displays the
NDPD/AC for that month.

Payment History
Start Date

This is the date of the beginning of the
payment history.
Format is DDMMYYYY.

Payment History
End Date

This is the date of the end of the payment
history.
Format is DDMMYYYY.

Suit Filed / Wilful
Default

Status are:
00 = No Suit Filed
01 = Suit filed
02 = Wilful default
03 = Suit filed (Wilful default)

June 03, 2013

Consumer Credit Information System / Response Record

Field
Tag

Field Name

Character
Type

Length
Type

Maximum
Length

Comments

Written-off and
Settled Status

Status are:
00 = Restructured Loan
01 = Restructured Loan (Govt. Mandated)
02 = Written-off
03 = Settled
04 = Post (WO) Settled
05 = Account Sold
06 = Written Off and Account Sold
07 = Account Purchased
08 = Account Purchased and Written Off
09 = Account Purchased and Settled
10 = Account Purchased and Restructured

Value of
Collateral

Type of Collateral

Values are:
00 = No Collateral
01 = Property
02 = Gold
03 = Shares
04 = Saving Account and Fixed Deposit

Credit Limit

To be shown when Account Type field is 10.

Cash Limit

To be shown when Account Type field is 10.

Rate Of Interest

Report numeric value without the percentage
sign.
One or more digits followed by the decimal
point, followed by one or more digits.
Maximum number of digits before the
decimal point is 4.
Maximum number of digits after the decimal
point is 3.

Repayment
Tenure

To be the count of number of months for
repayment.

EMI Amount

Written-off
Amount (Total)

To be reported when Written-off and Settled
Status field is reported as 02, 03, or 04.

Written-off
Amount
(Principal)

To be reported when Written-off and Settled
Status field is reported as 02, 03, or 04.

Settlement
Amount

To be reported when Written-off and Settled
Status field is reported as 03 or 04.

June 03, 2013

Consumer Credit Information System / Response Record

Field
Tag

Field Name

Character
Type

Length
Type

Maximum
Length

Comments

Payment
Frequency

Values are :
01 = Weekly
02 = Fortnightly
03 = Monthly
04 = Quarterly

Actual Payment
Amount

Date of Entry for
Error Code

Contains the date when the error code was
entered. Format is DDMMYYYY. (Future
Use Field)

Error Code

Error Code registered within the error/dispute
resolution process.
Refer to Appendix G for list of codes. (Future
Use Field)

Date of Entry for
CIBIL Remarks
Code

Contains the date when the CIBIL remarks
code was entered. Format is DDMMYYYY.
(Future Use Field)

CIBIL Remarks
Code

A/N

Refer to Appendix I for list of codes. (Future
Use Field)

Date of Entry for
Error/Dispute
Remarks Code

Contains the date when the error/dispute
remarks codes were entered. Format is
DDMMYYYY. (Future Use Field)

Error/Dispute
Remarks Code 1

A/N

Error/Dispute
Remarks Code 2

A/N

Contains up to 2 error/dispute remarks codes.
Refer to Appendix H for list of codes. (Future
Use Field)

Sum of all maximum byte lengths:

368

Sum of all two-byte tags and two-byte lengths:

148

Maximum byte size of segment:

516

3.11.1.
Account Segment Summary (TL) – Summary for Other
Live/Closed Accounts
The TL Segment Summary contains a count and summary (summation of the values reported in
High Credit/Sanctioned Amount and Current Balance) of the secured and unsecured loans. The
summary will be shown for live accounts and closed accounts of the consumer whose credit is
being reviewed, and:
It is variable in length and can be of a maximum size of 106 bytes.
It can appear only 4 times per Response Record.

Note

June 03, 2013

The following table is applicable only for the Account Segment Summary
(Summary for Other Accounts) part of the Portfolio Review Response Record.

Consumer Credit Information System / Response Record

Field
Tag

Field
Name

Character
Type

Length
Type

Maximum
Length

Comments

Segment Tag

A/N

Contains the value T001. If
multiple TL segments are
returned, the first segment
contains T001, the second
contains T002, and so on.
This field will contain T999
for all TL segments beyond
the first 999 TL segments.

Reporting
Member
Short Name

This field will always
contain
ACCTREVIEW_SUMM.

Number of
Accounts

This field will contain the
number of accounts of the
consumer, for that account
group.

Account
Group

Values are:
98 = Secured
99 = Unsecured
Please refer Appendix E for
classification of Account
Type into Secured and
Unsecured Loans.

Live/Closed
Indicator

Values are:
0 = Live Accounts
1 = Closed Accounts

Credit Limit /
High Credit /
Sanctioned
Amount

This field contains the sum
of all the amounts of loan
sanctioned.
For Credit Card and Fleet
Card, this field contains the
highest amount of credit
used in the history of the
account. For all other
accounts, this field contains
the amount of loan
sanctioned.
Credit Limit will take
precedence over High
Credit/Sanctioned Amount
when both amounts provided
in the account.
This amount is a whole
number and is assumed to be
positive.

June 03, 2013

Consumer Credit Information System / Response Record

Field
Tag

Field
Name

Character
Type

Length
Type

Maximum
Length

Comments

Current
Balance

This field contains the sum
of the entire amount of
credit/loan outstanding,
including the current and
overdue portion, if any,
together with interest last
applied for all the accounts.
This amount is a whole
number and could be either
positive (+) with a debit
balance or negative (-) with a
credit balance. If the balance
is zero, it will report as 0.
If a sign appears in this field,
it will appear at the
beginning of the field. If no
sign appears, we assume it to
be positive.

Sum of all maximum byte lengths:

Sum of all two-byte tags and two-byte lengths:

Maximum byte size of segment:

106

3.11.2.
Account Segment Details (TL) – Details for Other Live/Closed
Accounts
The TL Segment contains the credit information (others) of the consumer, whose account is being
reviewed, and:
It is variable in length and can be of a maximum size of 300 bytes.
It can appear an unlimited number of times per Response Record.

Note

The following table is applicable only for the Account Segment Summary
(Summary for Other Accounts) part of the Portfolio Review Response Record.

Field
Tag

Field Name

Character
Type

Length
Type

Maximum
Length

Comments

Segment Tag

A/N

Contains the value T001. If multiple TL
segments are returned, the first segment
contains T001, the second contains T002,
and so on.
This field will contain T999 for all TL
segments beyond the first 999 TL segments.

June 03, 2013

Consumer Credit Information System / Response Record

Field
Tag

Field Name

Character
Type

Length
Type

Maximum
Length

Comments

Account Group

Values are:
98 = Secured
99 = Unsecured
Please refer to Appendix E for classification
of Account Type into Secured and Unsecured
Loans.

Date Opened /
Disbursed

This is the date of first disbursement of the
account.
For Credit/Fleet cards, this is the date the
card becomes active.
Format is DDMMYYYY.

Date of Last
Payment

This is the most recent date a payment was
made on the account.
Format is DDMMYYYY.

Date Closed

This is the date the account was closed.
Format is DDMMYYYY.

Date Reported and
Certified

This is the most recent date the Reporting
Member reported information about the
account to CIBIL.
Format is DDMMYYYY.

Amount Overdue

The amount past due as of the date reported
in the Date Reported and Certified field.
This amount is a whole number and we
assume it to be positive.

June 03, 2013

Consumer Credit Information System / Response Record

Field
Tag

Field Name

Character
Type

Length
Type

Maximum
Length

Comments

Payment History 1

A/N

The most recent 18 months of Payment
History. Each month displays the Number of
Days Past Due (NDPD)/Asset Classification
(AC) for that month. The first value in the
payment history string is the NDPD/AC, as
of the date reported in the Date Reported and
Certified field.
For accounts that are closed and where the
Date Closed field is provided, the first value
in the payment history string is the
NDPD/AC, as of the date reported in the Date
Closed field.
If the value for a month is reported as XXX,
it means the Reporting Member did not report
data for that account for that particular
month.
If, instead of NDPD, AC is reported, the
following values will be displayed:
STD = Standard
SMA = Special Mention Account
SUB = Substandard
DBT = Doubtful
LSS = Loss
XXX = Not Reported

Payment History 2

A/N

Up to 18 remaining previous months in the
Payment History. Each month displays the
NDPD/AC for that month.

Payment History
Start Date

This is the date of the beginning of the
payment history.
Format is DDMMYYYY.

Payment History
End Date

This is the date of the end of the payment
history.
Format is DDMMYYYY.

Suit Filed / Wilful
Default

Status are:
00 = No Suit Filed
01 = Suit filed
02 = Wilful default
03 = Suit filed (Wilful default)

June 03, 2013

Consumer Credit Information System / Response Record

Field
Tag

Field Name

Character
Type

Length
Type

Maximum
Length

Comments

Written-off and
Settled Status

Date of Entry for
Error Code

Contains the date when the error code was
entered. Format is DDMMYYYY. (Future
Use Field)

Error Code

Error Code registered within the error/dispute
resolution process.
Refer to Appendix G for list of codes. (Future
Use Field)

Date of Entry for
CIBIL Remarks
Code

Contains the date when the CIBIL remarks
code was entered. Format is DDMMYYYY.
(Future Use Field)

CIBIL Remarks
Code

A/N

Refer to Appendix I for list of codes. (Future
Use Field)

Date of Entry for
Error/Dispute
Remarks Code

Contains the date when the error/dispute
remarks codes were entered. Format is
DDMMYYYY. (Future Use Field)

Error/Dispute
Remarks Code 1

A/N

Error/Dispute
Remarks Code 2

A/N

Contains up to 2 error/dispute remarks codes.
Refer to Appendix H for list of codes. (Future
Use Field)

Sum of all maximum byte lengths:

220

Sum of all two-byte tags and two-byte lengths:

Maximum byte size of segment:

300

June 03, 2013

Consumer Credit Information System / Response Record

3.12. Enquiry Segment (IQ)
The IQ Segment contains information on enquiries made on the consumer by other Member(s)
with CIBIL, and:
It is variable in length and can be of a maximum size of 59 bytes.
It does not display the enquiry that caused this Response, but thereafter can appear an
unlimited number of times per Response Record.
Tags 02 and 03 are reserved for future use.
Field
Tag

Field Name

Character
Type

Length Maximum
Type
Length

Comments

Segment Tag

A/N

Contains the value I001. If multiple IQ
segments are returned, the first segment
contains I001, the second contains I002, and so
on.
This field will contain I999 for all IQ segments
beyond the first 999 IQ segments.

Date of Enquiry

Contains the date when CIBIL received the
enquiry. Format is DDMMYYYY.

Enquiring
Member Short
Name

A/N*

Contains the Short Name of the Enquiry
Member who made this enquiry..
If the enquiry purpose is “For Individual”, the
Short Name of the Enquiry Member will always
be shown.
For all other enquiry purposes, members who
request that their name not be disclosed, the
value returned will be “Not Disclosed.”
However, it will display the Short Name of the
member when the enquiry has been made by the
member itself.

Enquiry Purpose

Contains the purpose of the enquiry.
Please refer to the Account and Enquiry Type
values in Appendix A.
For Portfolio Review (i.e. Enquiry Purpose =
90), this field will contain the values from 00 to
90 for enquiries made by the enquiring member
Otherwise this field will contain the values 98
and 99 for enquiries made by other members.

Enquiry Amount

Contains the amount of the enquiry.

Sum of all maximum byte lengths:

Sum of all two-byte tags and two-byte lengths:

Maximum byte size of segment:

June 03, 2013

Consumer Credit Information System / Response Record

3.13. Consumer Dispute Remarks Segment (DR) (Future Use
Segment)
The DR Segment contains information on dispute remarks entered by the consumer during the
dispute resolution process, and:
It is variable in length and can be of a maximum size of 463 bytes.
It can occur once per Response Record.
Field
Tag

Field Name

Character
Type

Length Maximum
Type
Length

Comments

Segment Tag

A/N

Contains the value D01.

Date of Entry

Contains the date when the consumer dispute
remarks was entered. Format is DDMMYYYY.

Dispute
Remarks Line1

Contains the consumer dispute remarks.

Dispute
Remarks Line2

Dispute
Remarks Line3

Dispute
Remarks Line4

Dispute
Remarks Line5

Dispute
Remarks Line6

Sum of all maximum byte lengths:

431

Sum of all two-byte tags and two-byte lengths:

Maximum byte size of segment:

463

June 03, 2013

Consumer Credit Information System / Response Record

3.14. End Segment (ES)
The ES Segment denotes the end of the Response Record, and:
It is of a fixed size of 17 bytes.
It can appear only once per Response Record.
Position

Field Name

Character
Type

Fixed
Length

Comments

Length of
Transmission

A/N

Must contain the value ES07NNNNNNN, where
NNNNNNN is the total length of the Response Record
(including the End Segment (ES)), left-padded with
zeros.

End Characters

Must contain the value 0102 followed by two asterisks
(**).

Total bytes

June 03, 2013

Consumer Credit Information System / Error Record

4. Error Record
Members receive an Error Record, instead of a Response Record, when a fatal error occurs during
the enquiry process. The segments that make up the Error Record appear in the following table.
These segments appear in an Error Record in the following order: ERRR, UR, and ES.
Segment
Tag

Segment Name

Segment
Length

Maximum No.
of Entries

Maximum Length

ERRR

Error

User Reference Error

Unlimited

End

June 03, 2013

Consumer Credit Information System / Error Record

4.1. Error Segment (ERRR)
The ERRR Segment marks the beginning of the Error Record, and:
It is of a fixed size of 18 bytes.
It can appear only once per Error Record.
Position

Field Name

Character
Type

Fixed
Length

Comments

Segment Tag

Contains the value ERRR.

Date Processed

Format is DDMMYYYY.

Time Processed

Format is HHMMSS.

Total bytes

June 03, 2013

Consumer Credit Information System / Error Record

4.2. User Reference Error Segment (UR)
The UR Segment describes the non-recoverable condition(s) that caused the CIBIL system to
return an Error Record, rather than a Response Record. Also:
The UR segment is variable in length and has no maximum length.
It can appear only once per Error Record.
Tag 02 is reserved for future use.
Field
Tag

Field Name

Character
Type

Length
Type

Maximum
Length

Comments

Segment Tag

A/N

Contains the value U01.

Member
Reference
Number

A/N

Contains either the value entered in positions
7-31 of the TUEF Enquiry Header Segment,
or is filled with blanks.

Invalid Version

A/N

Contains invalid value entered in positions 56 of the TUEF Enquiry Header Segment.

Invalid Field
Length

A/N

Contains the segment identifier, segment tag,
field tag, and field length for the first segment
containing the error.
For example, if the State Code in the second
Address Segment (PA) has a length of 5
(0605), then this field would contain
0409PAA020605.
If the error occurs in the ES Segment, this
field would contain only ES05.

Invalid Total
Length

A/N

Contains the value ES05 followed by the
Enquiry Record’s invalid length. This error
occurs when the total length of the Enquiry
Record entered does not correspond to the
length calculated by the system.

Invalid Enquiry
Purpose

Contains the value entered in positions 94-95
of the TUEF Enquiry Header Segment.

Invalid Enquiry
Amount

Contains the value entered in positions 96104 of the TUEF Enquiry Header Segment.

Invalid Enquiry
Member User
ID/Password

Contains the value entered in positions 64-93
of the TUEF Enquiry Header Segment.

Required
Enquiry
Segment
Missing

Contains the two-byte tag of the missing,
Required segment. If more than one segment
is missing, only the first missing segment
appears in this field.

June 03, 2013

Consumer Credit Information System / Error Record

Field
Tag

Field Name

Character
Type

Length
Type

Maximum
Length

Comments

Invalid Enquiry
Data

Contains the segment identifier, segment tag,
field tag, and field tag length, plus up to 40
bytes of data from that field.
For example, if Address Line1 in the second
Address Segment (PA) contains an error, this
field would contain 1034PAA020125,
followed by 25 bytes of data from that field.
If the error occurs in the ES Segment, this
field contains only ES05.
If another enquiry of the same (i.e. duplicated
enquiry) is still being processed, an error is
returned with this field contains only TUEF.
This field can appear as many times as errors
occur.

CIBIL System
Error

Contains the value Y. The member should
contact CIBIL if this error condition is
encountered.

Invalid Segment
Tag

The system stops processing and returns an
Error Record when an invalid segment tag is
found. This field would contain that invalid
segment tag.

Invalid Segment
Order

If the order of segments in an Enquiry Record
is not correct, this field is set to Y. The valid
order of the Enquiry Record is TUEF, PN,
ID, PT, PA, PI, and ES (PI Segment is When
Available except when the Enquiry Purpose
(Positions 52-53 of the TUEF Enquiry
Header Segment (TUEF)) is “Account
Review”, “Retro Enquiry” or “Locate Plus”).

Invalid Field
Tag Order

A/N

This field is used when the tags within an
Enquiry Record segment are out of order (or
repeated). Contains the segment identifier,
and the tag of the first field out of order.
For example, if the second Address Segment
(PA) has Tag 03 coming after Tag 06, this
field would contain the value 1407PAA0203.

Missing
Required Field

A/N

Contains the segment identifier and the tag of
the first Required field the system does not
find.
For example, if the first Address Segment
(PA) does not contain Address Line1, this
field would contain the value 1507PAA0101.
This field can appear up to 10 times.

Requested
Response Size
Exceeded

Contains the value Y if there is an error.

June 03, 2013

Consumer Credit Information System / Error Record

Field
Tag

Field Name

Character
Type

Length
Type

Maximum
Length

Comments

Invalid
Input/Output
Media

Contains the value sent in positions 113-114
of the TUEF Enquiry Header Segment.

Sum of all maximum byte lengths:

Unlimited

Sum of all two-byte tags and two-byte lengths:

Unlimited

Maximum byte size of segment:

Unlimited

June 03, 2013

Consumer Credit Information System / Error Record

4.3. End Segment (ES)
The ES Segment is the last segment in the Error Record, and:
It is of a fixed size of 15 bytes.
It appears once per Error Record.
Position

Field Name

Character
Type

Fixed
Length

Comments

Length of
Transmission

A/N

The value ES07 followed by NNNNNNN, where
NNNNNNN is the total length of the transmitted Error
Record (including the End Segment (ES)), left-padded
with zeros.

End Characters

The numbers 0102 followed by two asterisks (**).

Total bytes

June 03, 2013

Consumer Credit Information System / Appendix A – Account Type and Enquiry Purpose Table

Appendix A – Account Type and Enquiry Purpose Table
Value

Acronym

Use

Account Type

Current

Auto Loan (Personal)

Current

Housing Loan

Current

Property Loan

Current

Loan Against Shares/Securities

Current

Personal Loan

Current

Consumer Loan

Current

Gold Loan

Current

Education Loan

Current

Loan to Professional

Current

Credit Card

Current

Leasing

Current

Overdraft

Current

Two-wheeler Loan

NFCF

Current

Non-Funded Credit Facility

LABD

Current

Loan Against Bank Deposits

Current

Fleet Card

Current

Commercial Vehicle Loan

Future

Telco – Wireless

Future

Telco – Broadband

Future

Telco – Landline

Current

Secured Credit Card

Current

Used Car Loan

Current

Construction Equipment Loan

Current

Tractor Loan

Current

Corporate Credit Card

Current

Microfinance – Business Loan

Current

Microfinance – Personal Loan

Current

Microfinance – Housing Loan

Current

Microfinance – Other

Current

Business Loan – General

BLPS-SB

Current

Business Loan – Priority Sector – Small Business

BLPS-AGR

Current

Business Loan – Priority Sector – Agriculture

June 03, 2013

Consumer Credit Information System / Appendix A – Account Type and Enquiry Purpose Table

Value

Acronym

Use

Account Type

BLPS-OTH

Current

Business Loan – Priority Sector – Others

BNFCF-GEN

Current

Business Non-Funded Credit Facility – General

BNFCF-PS-SB

Current

Business Non-Funded Credit Facility – Priority Sector –
Small Business

BNFCF-PS-AGR

Current

Business Non-Funded Credit Facility – Priority Sector –
Agriculture

BNFCF-PS-OTH

Current

Business Non-Funded Credit Facility – Priority SectorOthers

BLABD

Current

Business Loan Against Bank Deposits

Current

Business Loan – Director Search

60
80

Future

Microfinance Detailed Report (Applicable to Enquiry
Purpose only)

Future

Summary Report (Applicable to Enquiry Purpose only)

Current

Locate Plus for Insurance (Applicable to Enquiry Purpose
only)

Reserved

VB OLM Retrieval Service (Applicable to Enquiry
Purpose for VB OLM Request only)

Current

Account Review (Applicable to Enquiry Purpose only)

Current

Retro Enquiry (Applicable to Enquiry Purpose only)

Current

Locate Plus (Applicable to Enquiry Purpose only)

Current

For Individual (Applicable to Enquiry Purpose only)

Future

Indicative Report (Applicable to Enquiry Purpose for CRS
Request only)

Current

Consumer Disclosure Report (Applicable to Enquiry
Purpose only)

Future

Bank OLM Retrieval Service (Applicable to Enquiry
Purpose for CRS Request only)

Current

Adviser Liability (Applicable to Enquiry Purpose only)

Current

Other

Current

Secured (Account Group for Portfolio Review response)

Current

Unsecured (Account Group for Portfolio Review
response)

Note

Print Image Report: Either the acronym, if present, or the first 30 characters of
the full name as mentioned in the column “Account Type,” will appear.
Machine Readable Formatted Response Record: The two-digit code as
mentioned in the column “Value” will appear.

June 03, 2013

Consumer Credit Information System / Appendix B – Allowed and Disallowed Characters

Appendix B – Allowed and Disallowed Characters
Following are the allowed and disallowed special characters in the Consumer Name Fields 1-5:
Allowed

Disallowed

;

(

)

[

]

{

}

/
\

Note

June 03, 2013

The front slash (/) and the back slash (\) are allowed only when used with SON
OF, WIFE OF, and DAUGHTER OF in any of the following ways: S/O, S\O,
W/O, W\O, D/O, and D\O. In all other situations, their appearance will lead to a
rejection of the Enquiry Record.

Consumer Credit Information System / Appendix C – State / Union Territory Codes

Appendix C – State / Union Territory Codes
Following is the list of State/Union Territory Codes as defined by Indian Census 2001:
Code

State / Union
Territory

Code

State / Union
Territory

Code

State / Union
Territory

Jammu & Kashmir

Himachal Pradesh

Punjab

Chandigarh

Uttaranchal

Haryana

Delhi

Rajasthan

Uttar Pradesh

Bihar

Sikkim

Arunachal Pradesh

Nagaland

Manipur

Mizoram

Tripura

Meghalaya

Assam

West Bengal

Jharkhand

Orissa

Chhattisgarh

Madhya Pradesh

Gujarat

Daman & Diu

Dadra & Nagar
Haveli

Maharashtra

Andhra Pradesh

Karnataka

Goa

Lakshadweep

Kerala

Tamil Nadu

Pondicherry

Andaman &
Nicobar Islands

June 03, 2013

APO Address

Consumer Credit Information System / Appendix D – PIN Code Validation Table

Appendix D – PIN Code Validation Table
This table represents the minimum and maximum digits allowed in the first two-digits of the sixdigit PIN Code:
State
Code

State

First two-digit
PIN prefix (Min)

First two-digit
PIN prefix (Max)

Jammu & Kashmir

Himachal Pradesh

Punjab

Chandigarh

Uttaranchal

Haryana

Delhi

Rajasthan

Uttar Pradesh

Bihar

Sikkim

Arunachal Pradesh

Nagaland

Manipur

Mizoram

Tripura

Meghalaya

Assam

West Bengal

Jharkhand

Orissa

Chhattisgarh

Madhya Pradesh

Gujarat

Daman & Diu

Dadra & Nagar Haveli

Maharashtra

Andhra Pradesh

Karnataka

Goa

June 03, 2013

Consumer Credit Information System / Appendix D – PIN Code Validation Table

State
Code

State

First two-digit
PIN prefix (Min)

First two-digit
PIN prefix (Max)

Lakshadweep

Kerala

Tamil Nadu

Pondicherry

Andaman & Nicobar Islands

APO Address

June 03, 2013

Consumer Credit Information System / Appendix E – Classification of Secured and Unsecured Loans

Appendix E – Classification of Secured and Unsecured Loans
Account Type

Loan Type

Auto Loan (Personal)

Secured

Housing Loan

Secured

Property Loan

Secured

Loan Against Shares/Securities

Secured

Personal Loan

Unsecured

Consumer Loan

Unsecured

Gold Loan

Secured

Education Loan

Unsecured

Loan to Professional

Unsecured

Credit Card

Unsecured

Leasing

Secured

Overdraft

Unsecured

Two-wheeler Loan

Secured

Non-Funded Credit Facility

Secured

Loan Against Bank Deposits

Secured

Fleet Card

Unsecured

Commercial Vehicle Loan

Secured

Telco – Wireless

N/A

Telco – Broadband

N/A

Telco – Landline

N/A

Secured Credit Card

Secured

Used Car Loan

Secured

Construction Equipment Loan

Secured

Tractor Loan

Secured

Corporate Credit Card

Unsecured

Microfinance – Business Loan

Unsecured

Microfinance – Personal Loan

Unsecured

Microfinance – Housing Loan

Secured

Microfinance – Others

Unsecured

Business Loan – General

Secured

Business Loan – Priority Sector – Small Business

Secured

Business Loan – Priority Sector – Agriculture

Secured

June 03, 2013

Consumer Credit Information System / Appendix E – Classification of Secured and Unsecured Loans

Account Type

Loan Type

Business Loan – Priority Sector – Others

Secured

Business Non-Funded Credit Facility – General

Secured

Business Non-Funded Credit Facility – Priority Sector – Small Business

Secured

Business Non-Funded Credit Facility – Priority Sector – Agriculture

Secured

Business Non-Funded Credit Facility – Priority Sector – Others

Secured

Business Loan Against Bank Deposits

Secured

Business Loan – Director Search

Secured

Other

Unsecured

June 03, 2013

Consumer Credit Information System / Appendix F – Score Reason Codes

Appendix F – Score Reason Codes
Code

Applicable To

Explanation

CIBILTUSCR

Too many tradelines 91+ days delinquent in the past 6 months

CIBILTUSC2

Not enough credit card debt experience

CIBILTUSCR

Presence of a tradeline 91+ days delinquent in the past 6 months

CIBILTUSC2

Length of time since most recent account delinquency is too short

CIBILTUSCR

Credit card balances are too high in proportion to High Credit Amount

CIBILTUSC2

Too many two-wheeler accounts

CIBILTUSCR

Too many tradelines with worst status in the past 6 months

CIBILTUSC2

Too many business loans

CIBILTUSCR

Presence of severe delinquency in the past 6 months

CIBILTUSC2

Credit card account balances too high in proportion to high credit
amount

CIBILTUSCR

Presence of a minor delinquency in the past 6 months

CIBILTUSC2

Maximum amount on mortgage loan is low

CIBILTUSCR

Presence of a tradeline with worst status in the past 6 months

CIBILTUSC2

Total amount past due is too high

CIBILTUSCR
PLSCORE

Credit card balances are high in proportion to High Credit Amount

CIBILTUSC2

Not enough mortgage debt experience

CIBILTUSCR

High number of trades with low proportion of satisfactory trades

CIBILTUSC2

Too much change of indebtedness on non-mortgage trades over the past
24 months
Low proportion of satisfactory trades

CIBILTUSCR
PLSCORE
CIBILTUSC2

Insufficient improvement in delinquency status

CIBILTUSCR

No presence of a revolving tradeline

CIBILTUSC2

Too much increase of indebtedness on non-mortgage trades over the
past 12 months

CIBILTUSCR

Presence of a tradeline 91+ days delinquent 7 to 12 months ago

CIBILTUSC2

Too many enquiries

CIBILTUSCR,
PLSCORE

Low average trade age

CIBILTUSC2

Too many accounts with a balance

CIBILTUSCR

Presence of a tradeline 91+ days delinquent 13 or more months ago

13
14

June 03, 2013

Consumer Credit Information System / Appendix F – Score Reason Codes

Code

Applicable To

Explanation

CIBILTUSC2

Length of time accounts have been established is too short

CIBILTUSCR

Presence of a minor delinquency 7 to 12 months ago

CIBILTUSC2

Not enough debt experience

CIBILTUSCR

Presence of a severe delinquency 7 to 12 months ago

CIBILTUSC2

Too many credit card accounts

CIBILTUSCR
PLSCORE

Presence of a high number of enquiries

CIBILTUSC2

Presence of a high number of enquiries

PLSCORE

Over due amount too high

CIBILTUSC2

Number of active trades with a balance too high in proportion to total
trades
Not enough available credit

PLSCORE
19

PLSCORE

Too much change of indebtedness on credit cards over the past 24
months
Too few satisfactory bankcard accounts

CIBILTUSC2

Credit card balance too high

PLSCORE

Total balance of delinquencies is too high

CIBILTUSC2

Proportion of delinquent trades too high

PLSCORE

Presence of delinquency

PLSCORE

Total high credit of delinquencies is too high

PLSCORE

Presence of a minor delinquency on personal loan

June 03, 2013

CIBILTUSC2

Consumer Credit Information System / Appendix G – Error Codes

Appendix G – Error Codes
List of Error Segment Tags and Error Codes for the Name (PN) response segment:
Error
Error
Segment Code
Tag

Explanation

001

Consumer Name in Dispute

007

Date of Birth in Dispute

008

Gender in Dispute

001

ID Type in Dispute

002

ID Number in Dispute

003

Issue Date in Dispute

004

Expiration Date in Dispute

001

Telephone Number in Dispute

002

Telephone Extension in Dispute

003

Telephone Type in Dispute

001

E-Mail ID in Dispute

001

Address Line (except State Code and PIN Code) in Dispute

006

State in Dispute

007

PIN Code in Dispute

008

Address Category in Dispute

009

Residence Code in Dispute

006

Enquiry Amount in Dispute

888

Enquiry Ownership Error

Miscellaneous
ZZ

000

No Dispute

999

Multiple Disputes in Name (PN) Segment

999

Multiple Disputes in Identification (ID) Segment

999

Multiple Disputes in Telephone (PT) Segment

999

Multiple Disputes in Email Contact (EC) Segment

999

Multiple Disputes in Address (PA) Segment

999

Multiple Disputes in Enquiry (IQ) Segment

999

Multiple Disputes

List of Error Codes for the Employment (EM) response segment:

June 03, 2013

Consumer Credit Information System / Appendix G – Error Codes

Error
Code

Explanation

000

No Dispute

003

Occupation Code in Dispute

004

Income in Dispute

005

Net/Gross Income Indicator in Dispute

006

Monthly/Annual Income Indicator in Dispute

999

Multiple Disputes

List of Error Codes for the Account (TL) response segment:
Error
Code

Explanation

000

No Disputes

003

Account Number in Dispute

004

Account Type in Dispute

005

Ownership Indicator in Dispute

008

Date Opened/Disbursed in Dispute

009

Date of Last Payment in Dispute

010

Date Closed in Dispute

011

Date Reported and Certified in Dispute

012

High Credit/Sanctioned Amount in Dispute

013

Current Balance in Dispute

014

Amount Overdue in Dispute

030

Payment History Start Date in Dispute

031

Payment History End Date in Dispute

032

Suit Filed / Wilful Default in Dispute

033

Written-off and Settled Status in Dispute

034

Value of Collateral in Dispute

035

Type of Collateral in Dispute

036

Credit Limit in Dispute

037

Cash Limit in Dispute

038

Rate Of Interest in Dispute

039

Repayment Tenure in Dispute

040

EMI Amount in Dispute

041

Written-off Amount (Total) in Dispute

042

Written-off Amount (Principal) in Dispute

June 03, 2013

Consumer Credit Information System / Appendix G – Error Codes

Error
Code

Explanation

043

Settlement Amount in Dispute

044

Payment Frequency in Dispute

045

Actual Payment Amount in Dispute

101

Payment History 1 in Dispute

102

Payment History 2 in Dispute

103

Payment History 3 in Dispute

104

Payment History 4 in Dispute

105

Payment History 5 in Dispute

106

Payment History 6 in Dispute

107

Payment History 7 in Dispute

108

Payment History 8 in Dispute

109

Payment History 9 in Dispute

110

Payment History 10 in Dispute

111

Payment History 11 in Dispute

112

Payment History 12 in Dispute

113

Payment History 13 in Dispute

114

Payment History 14 in Dispute

115

Payment History 15 in Dispute

116

Payment History 16 in Dispute

117

Payment History 17 in Dispute

118

Payment History 18 in Dispute

119

Payment History 19 in Dispute

120

Payment History 20 in Dispute

121

Payment History 21 in Dispute

122

Payment History 22 in Dispute

123

Payment History 23 in Dispute

124

Payment History 24 in Dispute

125

Payment History 25 in Dispute

126

Payment History 26 in Dispute

127

Payment History 27 in Dispute

128

Payment History 28 in Dispute

129

Payment History 29 in Dispute

130

Payment History 30 in Dispute

June 03, 2013

Consumer Credit Information System / Appendix G – Error Codes

Error
Code

Explanation

131

Payment History 31 in Dispute

132

Payment History 32 in Dispute

133

Payment History 33 in Dispute

134

Payment History 34 in Dispute

135

Payment History 35 in Dispute

136

Payment History 36 in Dispute

888

Account Ownership Error

999

Multiple Disputes

June 03, 2013

Consumer Credit Information System / Appendix H – Error/Dispute Remarks Codes

Appendix H – Error/Dispute Remarks Codes
Code

Explanation

000001

Disputed accepted – under investigation

June 03, 2013

Consumer Credit Information System / Appendix I – CIBIL Remarks Codes

Appendix I – CIBIL Remarks Codes
Code

Explanation

000001

One or more Members have not responded to your Dispute

000002

Dispute accepted – pending correction by the Member

June 03, 2013

Consumer Credit Information System / Annexure B

Annexure B
To be sent to CIBIL with each Enquiry file.
Annexure B
Enquiry Member ID:

Date:

Member Name:
Member Address:

Type of Enquiries: (Tick the applicable one)
Commercial

No. of
Tapes/C
Ds:

Consumer

ENQUIRY SUBMISSION DETAILS
N
o
.
S
r
.

M
e
d
i
a

File Name
N
o
.

Type

o
f
B
r
a
n
c
h
e
s

No. of Enquiries

Comments (if any):
* No. of Branches for which enquiries have been submitted.
Note: In the interest of security, we will process only those Enquiry Input files that are accompanied with
this Annexure.
This Annexure has to be separately submitted:
For Commercial enquiries and Consumer enquiries
When input file is submitted through FTP
The Enquiry Input file name should conform to the format:
Consumer:
June 03, 2013

Consumer Credit Information System / Annexure B

- - .tuef
Commercial:
- - .blk
(Signature)
Name: _________________
Designation: ____________

June 03, 2013

Source Exif Data:

File Type                       : PDF
File Type Extension             : pdf
MIME Type                       : application/pdf
PDF Version                     : 1.3
Linearized                      : No
Page Count                      : 84
Title                           : TUEF Guide - CIBIL
Author                          : TransUnion
Subject                         : CIBIL, TUCRS
Producer                        : Mac OS X 10.10.5 Quartz PDFContext
Creator                         : Microsoft® Word 2010
Create Date                     : 2017:04:05 06:26:41Z
Modify Date                     : 2017:04:05 06:26:41Z
Keywords                        : TUEF Guide for CIBIL, TransUnion
Apple Keywords                  : TUEF Guide for CIBIL, TransUnion

EXIF Metadata provided by EXIF.tools

CIBIL Guide

CIBIL%20Guide

CIBIL%20Guide

Navigation menu

Versions of this User Manual:

Views

Navigation