TUEF Guide CIBIL12 V2.50
TUEF Guide CIBIL12 V2.50
System
Guide to Enquiry Input and Response File
Format
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 “tu” 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
Table of Contents
Overview............................................................................................................................................... 7
Document History
2.21 Aug 27, 2015 Added UR Tag 19 to return reason for reason why the request is
rejected.
2.22 Sep 17, 2015 Revised the description for the ES segment and the Length of
Transmission when it exceeds 9999999.
2.23 Sep 24, 2015 Revised to allow PIN Code from 900000 to 999999 for APO address
(or State Code = 99).
Added a gender type for Transgender.
Added two new account types and enquiry purposes for Loan on Credit
Card and Business Loan – Unsecured.
Added a status flag “Restructured due to Natural Calamity” to Written-
Off & Settled Status.
2.24 Oct 22, 2015 Removed Business Loan – Director Search from account types,
enquiry purposes and loan types.
2.26 Jan 15, 2016 “Rolled Back” Version 2.25 with contained invalid account types and
enquiry purposes.
Added Secondary Response Record Section
2.27 Mar 3, 2016 Added account types and enquiry purposes of:
38 - Prime Minister Jaan Dhan Yojana - Overdraft
39 - Mudra Loans – Shishu / Kishor / Tarun
44 - Pradhan Mantri Awas Yojana - Credit Link Subsidy Scheme MAY
CLSS
50 - Business Loan – Secured
2.28 Mar 14, 2016 Revised the handling of consumer name presented as a single name
word.
2.29 Apr 21, 2016 Revised to include Universal ID (UID) Number as of the the required ID
types.
2.30 Jun 9, 2016 Updated Min/Max PinCode for state Pondicherry in Appendix D.
2.31 Dec 21, 2016 Revised the SC segment to include CreditVision Demonetisation
Algorithms.
2.32 Jun 15, 2017 Revised the SC segment to include CreditVision Algorithms.
2.34 Jun 30, 2017 Used the reserved field at positions 32-33 as GST State Code in the
request Header segment.
Added Account Types 31 and 35 to Tag 12 of the TL segment.
2.35 Jul 27, 2017 Revised the field name and comments for Tags 34-40 of the SC
segment.
2.36 Feb 18, 2018 Added P2P Enquiry Purposes
2.38 Jan 15, 2019 Updated CreditVision Risk Score Reason Codes
2.43 May 29, 2019 Revised the Score Options and Output formats for Income Estimator
2.44 Feb 04, 2020 Revised the Score Options, Output formats and Score Response for
Income Estimator 2.
2.45 Mar 16, 2020 Modified Score Response to remove Point Estimate Income
2.46 Mar 30, 2020 Incorporated UAT comments and remove CIBILTUIE1 reference
2.47 Mar 31, 2020 Remove all references to CIBILTUIE1 for response and combo scores
2.48 May 29, 2020 Added iSPIRIT Enquiry Purpose and Account Type codes
2.49 Jun 25, 2020 Added GECL Loan Enquiry Purpose and Account Type codes
2.50 Mar 31, 2021 Field Name is changed from “Written-off and Settled Status” to “Credit
Facility Status”
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.
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:
See Comments: Special circumstances separate this type of field from the
above classifications. The Comments column in the table explains the special
conditions.
Character Type
Identifies the type of character appearing in a field. The values that appear in this
column are:
Length Type
Identifies whether the field is of a fixed length or a variable length. The values that
appear in this column are:
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.
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.
++ 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.
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.
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.
Supply a two-byte length that indicates how many bytes (or characters) are in 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
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
fixed-length 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.
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.
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.
<ENQUIRY MEMBER ID> - <Date of file creation in DDMMYYYY format> - <File creation time in
HHMMSS format>.tuef
32 GST State P 02 The member should specify the GST state code
Code of the member branch / office making the enquiry.
Please refer to the State / Union Territory Codes
values in Appendix C.
The state code (99) for APO Address is not
allowed and any invalid state code provided will
be ignored.
110 Output Format N 02 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.)
113 Input/Output A 02 Specify the input and output media used for the
Media enquiry. Valid values are:
CC = CPU-to-CPU
TT = Tape-to-Tape
Account Review, Retro, Locate Plus and Locate
Plus for Insurance Enquiries can use only TT.
Income Estimator Score could be requested only
through CC.
Total bytes 15
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.
ES End Fixed 1 1 17
** 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 no-hit 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.
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).
Closed Accounts: All accounts that have a value reported in the field Date Closed
(Field Tag 10, TL Segment).
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.
Which members receive secondary files and the maximum number of secondary subjects
returned is dependent upon configurations specific to the member. When multiple response
records are returned, only the first response record contains the enquiry control number in the
Enquiry Control No field; any subsequent response records that have a an enquiry control
number of zero should be considered as secondary subjects.
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
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.
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.
Total bytes: 94
03 Consumer P V 26
Name Field3
04 Consumer P V 26
Name Field4
05 Consumer P V 26
Name Field5
80 Date of Entry N F 08 Contains the date when the error code was
for Error Code entered. Format is DDMMYYYY.
87 Error/Dispute A/N F 06
Remarks Code
2
02 ID Number P V 30
01 Telephone P V 20
Number
02 Telephone A/N V 10
Extension
01 E-Mail ID P V 70
04 Income N V 09
80 Date of Entry for N F 08 Contains the date when the error code
Error Code was entered. Format is DDMMYYYY.
The score segment appears up to three per Response Record. For more information on the
score, please see the guides Understanding the CIBIL TransUnion Score (CIBILTUSCR),
Understanding_the_score_2.0 (CIBILTUSC2), Understanding_CV_Score (CIBILTUSC3),
Understanding the Income Estimator Score (CIBILTUIE2) 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.
1 0 - **2.4L
2 2.4L – **4.8L
3 4.8L – **7.2L
4 7.2L – **9.6L
5 9.6L – **12L
6 12L – **15L
7 15L – **18L
8 18L – **21L
9 21L – **24L
05 Exclusion Code 1 A/N V 02 One or more trades with suit filed status
in the past 24 months.
A value of 01 when this exclusion is
applied.
Exclusion codes are not relevant for
CreditVision® Score and Income
Estimator Score
06 Exclusion Code 2 A/N V 02 One or more trades with wilful default
status in the past 24 months.
A value of 01 when this exclusion is
applied.
07 Exclusion Code 3 A/N V 02 One or more trades with suit filed (wilful
default) status in the past 24 months.
A value of 01 when this exclusion is
applied.
Tags 41 - 74 are fixed and defined for additional reason codes (34) for future use.
01 Address Line1 P V 40
02 Address Line2 P V 40
03 Address Line3 P V 40
04 Address Line4 P V 40
05 Address Line5 P V 40
07 PIN Code P V 10
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.
02 Reporting Member A/N* V 16 This field will contain the Short Name of
Short Name 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.
34 Value of Collateral N V 09
40 EMI Amount N V 09
45 Actual Payment N V 09
Amount
80 Date of Entry for N F 08 Contains the date when the error code
Error Code was entered. Format is DDMMYYYY.
Note The following table is applicable only for the Account Segment Summary
(Summary for Other Accounts) part of the Portfolio Review 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.
80 Date of Entry for N F 08 Contains the date when the error code
Error Code was entered. Format is DDMMYYYY.
03 Dispute P V 70
Remarks
Line2
04 Dispute P V 70
Remarks
Line3
05 Dispute P V 70
Remarks
Line4
06 Dispute P V 70
Remarks
Line5
07 Dispute P V 70
Remarks
Line6
Total bytes 17
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.
ERRR Error F 1 18
ES End F 1 17
Total bytes 18
14 Invalid Field A/N F 07 This field is used when the tags within an
Tag Order 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.
Total bytes 17
11 - Current Leasing
12 - Current Overdraft
00 - Current Other
Allowed Disallowed
. ~
` !
' #
; $
: %
" ^
- &
_ *
( =
) |
[ ?
] +
{ ,
} @
< /
> \
The front slash (/) and the back slash (\) are allowed only when used with
Note 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.
99 APO Address v v v v
02 Himachal Pradesh 17 17
03 Punjab 14 16
04 Chandigarh 14 16
05 Uttaranchal 24 26
06 Haryana 12 13
07 Delhi 11 11
08 Rajasthan 30 34
09 Uttar Pradesh 20 28
10 Bihar 80 85
11 Sikkim 73 73
12 Arunachal Pradesh 78 79
13 Nagaland 79 79
14 Manipur 79 79
15 Mizoram 79 79
16 Tripura 72 79
17 Meghalaya 79 79
18 Assam 78 79
19 West Bengal 70 74
20 Jharkhand 81 83
21 Orissa 75 77
22 Chhattisgarh 46 49
23 Madhya Pradesh 45 48
24 Gujarat 36 39
27 Maharashtra 40 44
28 Andhra Pradesh 50 56
29 Karnataka 53 59
30 Goa 40 40
31 Lakshadweep 67 68
32 Kerala 67 69
33 Tamil Nadu 53 66
34 Pondicherry 53 67
36 Telangana 50 56
99 APO Address 90 99
Leasing Secured
Overdraft Unsecured
Pradhan Mantri Awas Yojana - Credit Link Subsidy Scheme MAY CLSS Secured
Other Unsecured
01 CIBILTUSCR Too many tradelines 91+ days delinquent in the past 6 months
CIBILTUSC2 Length of time since most recent account delinquency is too short
03 CIBILTUSCR Credit card balances are too high in proportion to High Credit
Amount
04 CIBILTUSCR Too many tradelines with worst status in the past 6 months
CIBILTUSC2 Credit card account balances too high in proportion to high credit
amount
CIBILTUSC3 SUPPRESS
08 CIBILTUSCR Credit card balances are high in proportion to High Credit Amount
PLSCORE
CIBILTUSC3 SUPPRESS
CIBILTUSC3 SUPPRESS
CIBILTUSC3 SUPPRESS
CIBILTUSC2 Too much change of indebtedness on credit cards over the past 24
months
CIBILTUSC3 INCREASE IN NON-MORTGAGE INDEBTEDNESS IN LAST 12
MONTHS
20 PLSCORE Too few satisfactory bankcard accounts
CIBILTUSC3 SUPPRESS
34 CIBILTUSC3 SUPPRESS
43 CIBILTUSC3 SUPPRESS
44 CIBILTUSC3 SUPPRESS
47 CIBILTUSC3 SUPPRESS
48 CIBILTUSC3 SUPPRESS
50 CIBILTUSC3 SUPPRESS
51 CIBILTUSC3 SUPPRESS
PA 001 Address Line (except State Code and PIN Code) in Dispute
Miscellaneous
ZZ 000 No Dispute
000 No Dispute
205 Net/Gross Income Indicator - Dispute accepted - Pending corrections by the Member
000 No Disputes
209 Date of Last Payment - Dispute accepted - Pending corrections by the Member
211 Date Reported and Certified - Dispute accepted - Pending corrections by the Member
212 High Credit/Sanctioned Amount - Dispute accepted - Pending corrections by the Member
230 Payment History Start Date - Dispute accepted - Pending corrections by the Member
231 Payment History End Date - Dispute accepted - Pending corrections by the Member
232 Suit Filed / Wilful Default - Dispute accepted - Pending corrections by the Member
233 Credit Faciity Status - Dispute accepted - Pending corrections by the Member
241 Written-off Amount (Total) - Dispute accepted - Pending corrections by the Member
242 Written-off Amount (Principal) - Dispute accepted - Pending corrections by the Member
245 Actual Payment Amount - Dispute accepted - Pending corrections by the Member
887 Account Ownership Error - Dispute accepted - Pending corrections by the Member
PN0001 Certain information under Personal / Contract / Enquiry information section has been disputed
by the consumer.
EM0001 Certain information under Employment information section has been disputed by the
consumer.
PA1001 Address Line (except State Code and PIN Code) in Dispute
Code Explanation
TL0001 Certain information for this account has been disputed by the consumer.
Code Explanation
Code Explanation
Miscellaneous
Annexure B
To be sent to CIBIL with each Enquiry file.
Annexure B
Member Name:
Member Address: Type of Enquiries: (Tick the applicable one) No. of Tapes/CDs:
Commercial
Consumer
Sr. No. File Name Media Type No. of Branches No. of Enquiries
Note: In the interest of security, we will process only those Enquiry Input files that are accompanied with
this Annexure.
Consumer:
<ENQUIRING MEMBER ID> - <Date of file creation in DDMMYYYY format> - <File creation time in
HHMMSS format>.tuef
Commercial:
<ENQUIRING MEMBER ID> - <Date of file creation in DDMMYYYY format> - <File creation time in
HHMMSS format>.blk
(Signature)
Name: _________________
Designation: ____________