156.jsonl

{"text": "Introduction \nThese directions aim to establish a standardised framework for reporting and \ndissemination of credit information; safeguard the confidentiality and security of \nsensitive credit data; provide mechanisms for consumers to access their credit \ninformation and grievance redressal on matters related to credit information reporting. \nAccordingly, in exercise of the powers conferred by Section 11 of the Credit \nInformation Companies (Regulations) Act, 2005 (hereinafter referred to as CICRA), \nthe Reserve Bank of India (‘RBI’) being satisfied that it is necessary and expedient in \nthe public interest so to do, hereby issues the Directions hereinafter specified. \nChapter-I Preliminary \nA. Short title and commencement \n1. \nThese Directions shall be called the Reserve Bank of India (Commercial Banks \n– Credit Information Reporting) Directions, 2025. \n2. \nThese Directions shall come into force with immediate effect, unless otherwise \nspecified. \nB. Applicability \n3. \nThese Directions shall be applicable to Commercial Banks [hereinafter \ncollectively referred to as ‘Credit Institutions (CIs)’ and individually referred to as \n‘Credit Institution (CI)’]. \nFor the purpose of these Directions, ‘Commercial Banks’ means banking \ncompanies (other than Small Finance Banks, Payment Banks, and Local Area \nBanks), corresponding new banks, and the State Bank of India, as defined \nrespectively under clauses (c), (da), and (nc) of Section 5 of the Banking \nRegulation Act, 1949. \nC. Definitions \n4. \nIn these Directions, unless the context otherwise requires, the terms herein shall \nbear the meaning assigned to them below: \n(1) ‘Company’ means a company defined under section 3 of the Companies Act, \n1956 or corresponding section under the Companies Act, 2013. \n(2) ‘Credit Information Companies (CICs)’ means companies that have been"}
{"text": "granted a certificate of registration under section 5 of the CICRA. The CICs \nregistered with RBI under Section 5 of the CICRA are: \nSl. No. \nList of the CICs registered with RBI \nDate of issue of Certificate \nof Registration \n1. \nCRIF High Mark Credit Information \nServices Private Limited \nNovember 25, 2010 \n2. \nEquifax Credit Information Services \nPrivate Limited \nMarch 26, 2010 \n3. \nExperian Credit Information Company of \nIndia Private Limited \nFebruary 17, 2010 \n4. \nTransUnion CIBIL Limited \nMarch 05, 2012 \n(3) \n‘Specified User (SU)’ shall have the same meaning assigned to it under clause \n(l) of section 2 of CICRA and those notified under regulation 3 of the Credit \nInformation Companies Regulations, 2006, hereinafter referred to as “CIC \nRegulations” (as amended from time to time). \n5. \nWords or expressions used in these Directions and not defined herein, but defined \nin CICRA, 2005, the Credit Information Companies Rules, 2006 (hereinafter \nreferred to as ‘CIC Rules’) and the CIC Regulations, shall have the same \nmeanings as assigned to them in these Statute/ Rules/ Regulations. Any other \nwords or expressions used and not defined in these directions or aforesaid \nStatute/ Rules/ Regulations and defined in Reserve Bank of India Act, 1934 or \nBanking Regulation Act, 1949 or the Companies Act, 2013 shall have the same \nmeanings as assigned to them in these Acts."}
{"text": "Chapter-II Membership of CICs \n6. \nA CI shall become member of all the CICs registered with the RBI. \n7. \nOne-time membership fee charged by the CICs from a CI to become their \nmembers shall not exceed ₹10,000 each. \n8. \nThe annual fees charged by the CICs from a CI shall not exceed ₹5,000 each."}
{"text": "Chapter-III Credit Information Reporting and Dissemination \nA. Data formats \n9. \nThe reporting of credit information by a CI to the CICs, shall be undertaken in \nstandardised data formats as prescribed in Annex I. These standardised data \nformats would be a non-proprietary reporting format and shall be known as \n‘Uniform Credit Reporting Format’ (UCRF) as denoted below: \n(1) \nForm 1: Uniform Credit Reporting Format (Consumer) – for consumer segment.  \n(2) \nForm 2: Uniform Credit Reporting Format (Commercial) – for commercial \nsegment. \n(3) \nForm 3: Uniform Credit Reporting Format (MFI) – for microfinance segment. \nB. Reporting timelines and updation \n10. A CI shall adhere to following guidelines on reporting timelines and updation: \n(1) \nA CI shall submit data on credit information of its borrowers (including historical \ndata) to all CICs. \n(2) \n1A CI shall keep the credit information collected / maintained by it, updated \nregularly on the following basis or at shorter intervals as mutually agreed upon \nbetween the CI and CIC: \n(i) \nA CI shall submit credit information as on 9th, 16th, 23rd and last day of the month \n(hereinafter referred to as the reference dates) to CICs. \n(ii) \nA CI shall submit the full file containing credit information records as on the last \nday of the month to the CICs, by 5th day of the next month. Full file for this purpose \nshall include all active accounts in the books of the CI and the accounts wherein \nrelationship between the borrower and the CI has ended since the last reporting \nreference date.  \n(iii) For other submissions during the month, i.e., credit information records as on 9th, \n16th and 23rd day of the month, a CI shall only furnish ‘incremental accounts’ to CICs. \nThe CI shall submit such credit information to CICs within four (4) calendar days from \n \n1 Substituted with effect from July 01, 2026, vide Reserve Bank of India (Commercial Banks – Credit Information \nReporting) Amendment Directions, 2025 dated December 04, 2025."}
{"text": "the above-mentioned dates. Incremental accounts for this purpose shall include details \nin respect of the following accounts: \n(a) Accounts opened since the last reporting reference date;  \n(b) Accounts wherein the relationship between the borrower and the CI has ended \nsince the last reporting reference date; \n(c) Accounts where there is a change from the last reporting reference date \nbecause of any action/ transaction initiated by the borrower, and the same shall \ninclude instances of repayment, change in outstanding balance, updates in \ndemographic details, related party, guarantors, ownership of account, account \ntype; and  \n(d) Accounts where interest and / or instalment of principal is overdue \nExplanation: Accounts with change only in days past due from the last reporting \nreference date shall also form part of the reporting. \n(iv) An illustration on timelines for reporting is given in Annex-VI. \n(v) CICs shall report on the DAKSH portal, a list of CIs which fail to adhere to the \ndata submission timelines to Department of Supervision, Reserve Bank of India, \nCentral Office at half yearly intervals (as on March 31 and September 30 each \nyear) for information and monitoring purposes. \n(3) \nA CI shall ensure that the records submitted to CICs are updated regularly and \nthat no instances of repayment, including that of the last instalment, are left \nunreported. \nC. Reporting guidelines \n11. The CICRA provides statutory backing for sharing of credit information by a CI \nwith CICs, subject to conditions stipulated therein. Therefore, with CICRA \ncoming into force, the requirement of a ‘consent clause’ has become redundant \nand a CI need not insist upon obtaining such consent from borrowers. \n12. A CI shall adhere to, inter alia, the following guidelines when reporting credit \ninformation in the UCRF:  \n(1) \nIn the commercial reporting segment, corporate identification number (CIN) and \ncredit history of the directors of the company (based on DIN number) shall be"}
{"text": "reported. \n(2) \nA CI shall report cases where compromise settlements have taken place and \nthe reason for such compromise settlement, in the prescribed data formats to CICs. \n(3) \nWith respect to part instalment overdue, a CI shall submit data as it is, while \nqualitative information on what filters to apply based on amount and period would be \ndone by the SU and others who make use of the data. \n(4) \nA CI shall use 'settled' status for denoting only specific situations where due to \nfinancial inability to repay as per original terms and conditions, either a principal or an \ninterest waiver or both is provided to the customer.  \nExplanation: A CI needs to be aware of such a situation prior to extending fresh credit \nto such customers. Cases of wrong debits or contested charges shall not be reported \nas 'settled' but as 'disputed'. \n(5) \nThe information on Commercial Papers (CPs) issued by the companies shall be \nreported on a fortnightly basis to the CICs by a CI which has been designated as the \nIssuing and Payment Agent (IPA) for the particular CP issue. If there are multiple \nIPAs for a single CP issue, each IPA to such issue shall report to the CICs the details \npertaining to the portion of the issue which is with them. This information shall be \nreported in the commercial data format in the fields as mentioned in Annex II. The \nIPA shall also report any default in the redemption of the relevant CP issue to the \nCICs. In view of reporting requirement of IPA, it is clarified that an investing CI need \nnot report the information on CPs to the CICs. \n(6) \nThe information regarding Unhedged Foreign Currency Exposure (UFCE) of \nindividual borrowers shall be reported on a fortnightly basis to the CICs by the lending \nCI (in the case of solo lenders) / consortium leader (in the case of consortium \narrangements) / largest lender (in the case of multiple lending arrangements). \n(7) \nThe cases admitted with National Company Law Tribunal (NCLT) / National \nCompany Law Appellate Tribunal (NCLAT) under the Insolvency and Bankruptcy \nCode, 2016 shall be reported under the suit-filed cases in the Uniform Credit \nReporting Format, while reporting to the CICs. \n(8) \nThe reporting of Relationship Segment (RS) data by a CI to CICs is mandatory \nfor all accounts opened on or after July 01, 2018."}
{"text": "Explanations:  \n(a) The reporting of shareholders’ information under the ‘relationship’ field of the RS \nin the Commercial data format should be done only for those shareholders who are \n‘Beneficial Owners’ as defined under the Reserve Bank of India (Commercial Banks \n– Know Your Customer) Directions, 2025, as amended from time to time. \n(b) The RS details are important in establishing cross-linkages across the three \nmodules, viz., Consumer, Commercial and MFI, while providing comprehensive credit \ninformation of a borrower to CIs by CICs. \n(c) A timeline for reporting of the remainder legacy data would be reviewed by the \nTechnical Working Group (TWG) and the CIs would be advised in due course. CICs \nshall furnish the list of CIs not adhering to the instructions on reporting of RS data to \nthe Department of Supervision (DoS), Central office, on a monthly basis.   \n(9) \n Guidelines for cross reporting, e.g., where individual is borrower and corporate \nis co-borrower, or vice versa, shall be clearly intimated by CICs. The formats have \nfields to incorporate the data where consumer data will be reported in the consumer \ndata format and co-borrower will be reported in commercial data format. \n(10) 2A CI shall report Central KYC (CKYC) number of its borrowers to CICs, \nwherever the same is available with it or as and when CKYC number is made \navailable (in the case of fresh applicants for CKYC number). \n13. Data of Self Help Group (SHG) members \n(1) \nA CI financing SHGs shall report the SHG member level data to CICs in \nthe Uniform Credit Reporting Format (MFI) as mentioned in Annex I.  \n(2) \nThe structure of the credit information in respect of SHG members to be collected \nand reported by a CI to CICs is set out below: \nSl. No. \nParticulars \nAnnex III \n1 \nInformation to be collected by a CI from individual SHG \nmembers where the total amount of loan to be attributed to or to \nbe availed by the SHG member exceeds ₹30,000/- \nTable 1 \n \n2 Inserted with effect from July 01, 2026, vide Reserve Bank of India (Commercial Banks – Credit Information \nReporting) Amendment Directions, 2025 dated December 04, 2025."}
{"text": "2 \nInformation to be collected by a CI from individual SHG \nmembers where the total amount of loan to be attributed to or to \nbe availed by the SHG member is upto ₹30,000/- \nTable 2 \n3 \nInformation on all individual SHG members to be reported by a \nCI to CICs [included under the Uniform Credit Reporting (MFI) \nformat] \nTable 3 \n4 \nInformation on individual SHG members to be collected by \nbanks at the time of opening of new Savings Bank Accounts of \nthe SHG \nTable 4 \n(3) \nThe data tables are given in Annex III. As indicated above, a CI shall collect \ninformation from all SHG members in Tables 1 and 2 and report it to the CICs \nas set out in Table 3. The SHG member level data as mentioned in Table 3 shall \nbe subsumed in Form 3: Uniform Credit Reporting format (MFI) of Annex I for \nreporting to CICs. The tables have been designed based on the following \nconsiderations:  \n(i) \nSome of the information (Item number 17 of Tables 1 and 2) is related to \nthe existing exposures of the SHG members including that of the SHG \ngroups with whom they might have been previously associated. This is \nintended to help CIs make informed credit decisions with regard to the SHG \nmembers. This information may be collected by CIs directly from the CICs \nbased on lead information provided by the SHG members. Hence, there \nwould be no need for CIs to include this information in the dataset reported \nto the CICs as per Table 3. \n(ii) \nThe collection and reporting of credit information in respect of SHG \nmembers will be restricted to the members of those SHGs that take loans \nexceeding ₹1,00,000/-. However, the members of all SHGs, regardless of \nthe amount of group loan, shall report the non-credit information to CIs \nthrough the SHG Group at the time when the SHG approaches the CI for a \nloan. \n(iii) The non-credit information requirements have been designed both from the \nperspective of identification of the individual borrowers and supplementing \nthe information requirements of banks, regulatory and government \ndevelopment agencies for the purpose of evaluating the flow of credit to"}
{"text": "various sub-segments of the SHG members and designing suitable credit \npenetration strategies keeping in view the socio-economic profile of the sub-\nsegments. The information shall be reported by CIs to the CICs in a manner \nthat allows the CICs to identify all members associated with a particular SHG \nand a particular person to be identified with all SHGs with whom he/she \nis/was associated. \n(4) \nA CI shall put in place necessary systems and procedures including making \nnecessary changes to their system software for collections of the relevant \ninformation from the SHG members and reporting the required information to the \nCICs. \n(i) \nA CI shall have the option to collect and report the SHG member level data \neither themselves or by outsourcing it to other entities. However, it shall \nfollow all general instructions on outsourcing set out in the Reserve Bank of \nIndia (Commercial Banks – Managing Risks in Outsourcing) Directions, \n2025, as amended from time to time, to the extent applicable and shall \ncontinue to be responsible for the correctness of the data submitted by the \noutsourced agencies to the CICs. A CI must put in place appropriate \ncontrols to ensure the correctness of the data submitted by the entities to \nwhich it is outsourced. \n(ii) \nA CI shall monitor the NPA levels in the SHG segment on an ongoing basis \nand collect detailed information from SHG members availing loans \nexceeding a lower threshold of ₹20,000, if the Gross NPA in the SHG \nsegment exceeds 10% or is higher than the gross NPA of the CI by 5 \npercentage points. \n(iii) Non-adherence to the instructions by a CI shall result in exclusion of non-\ncompliant SHG loan accounts from the loan portfolios eligible to be \nreckoned for the purpose of complying with the priority sector lending (PSL) \ntargets. \n(5) \nOther operational instructions \n(i) \nAt this stage, it is envisaged to capture details of only the credit facilities \navailed by the SHG members from the CIs. Therefore, any information \nrelating to inter-loaning among the SHG members out of their own savings"}
{"text": "will not be covered. However, in order to know the overall indebtedness of \na SHG member it may be necessary to know their exposures to the SHGs \nwith regard to inter-loaning as well. As part of the continued endeavour to \nimprove the quality of information of a SHG member, the need for capturing \nthe inter-loaning would be reviewed in due course. \n(ii) \nGiven significant challenges in monitoring and reporting the performance of \nindividual loans availed by the SHG members out of the amounts lent by \nCIs to the SHGs, it is not envisaged to extend the credit reporting system to \nthe monitoring of repayment and recovery of these loans. However, this \nwould be considered in due course. \n(iii) With a view to building up the adequate information base of the potential \nSHG member borrowers and expediting the process of collection and \nreporting of KYC compliant information relating to the members of the SHGs \nwhen the SHGs are credit- linked, banks are encouraged to offer Small \nAccounts / Basic Savings Bank Deposit Account to the SHG members when \nan SHG approaches them for opening a Savings Account. In cases where \nthe SHG members agree to open such accounts, the information in Table 4 \nmay be collected and kept on record to be used at the time when the SHG \napproaches the bank for a loan. However, it must not be made a pre-\ncondition for opening the Savings Account of the SHG. \n(iv) None of the data requirements specified in paragraph 13 should be made a \npre- condition for extending loans to the SHGs, though CIs must make \nsincere efforts to comply with these requirements. \n(v) \nA CI may encourage the SHGs to keep written records of loans distributed \nto their members out of the loan availed including the digitisation scheme \nfor SHGs of NABARD, where applicable, and may consider introducing \nappropriate incentives in this regard. \n(vi) A CI shall develop appropriate policies to deal with applications for credit \nfacilities from members of SHGs / SHGs on whom default is reported by the \nCICs. Care needs to be taken that the SHGs / individual members are not \ndenied loans merely because of such defaults and CIs should appropriately \nevaluate the credit history of the members themselves and take into account"}
{"text": "the economic viability of their activities and the Groups’ capacity to service \nthe loan proposed to be taken by considering their loan applications. \n(vii) The credit information relating to individual SHG members shall be \ncollected, reported, and disseminated as per the provisions of the CICRA \nand the extant RBI directions on credit information reporting. \n14. Reporting mechanism after cancellation of licence \n(1) \nIn case of cancellation of licence of a CI by RBI, either through voluntary \nsubmission or supervisory action, CICs shall insert a suitable disclaimer in the \nrecords of the CI’s borrowers to reflect non-updatability of the record due to \nclosure of the CI in their CIR. \n(2) \nIn order to address the challenges in updating credit information of borrowers of \nCI whose licence has been cancelled, CICs and CIs shall implement a credit \ninformation reporting mechanism subsequent to cancellation of licence as under \n(i) \nA CI, whose licence has been cancelled by RBI shall be categorised ‘Credit \nInstitution’ under Section 2(f)(vii) of CICRA. \n(ii) \nSuch a CI shall continue to report credit information of the borrowers on-\nboarded and reported to CICs prior to cancellation of their licence to all the \nfour CICs till the loan lifecycle is completed or the credit institution is wound \nup, whichever is earlier. \n(iii) Such a CI shall have access to Credit Information Reports pertaining to only \nthose borrowers which were onboarded and reported to CICs before the \ncancellation of their license. \n(iv) CICs shall not charge the annual and membership fees from such a CI. \n(v) \nThese instructions shall also be applicable to those entities whose licence \nhas been cancelled by the Reserve Bank of India prior to issuance of these \ninstructions. \n(vi) All other instructions regarding credit information reporting by CIs to CICs \nshall remain unchanged"}
{"text": "D. Rectification of rejected data and review of Data Quality Index (DQI) \n15. \n3A CI shall rectify the rejected data shared by CICs and re-submit the same to \nCICs before/ along with submission of data of subsequent reporting reference \ndate. \n16. CICs shall prepare and provide Data Quality Index (DQI) for Consumer, \nCommercial and Microfinance segments, as provided in Reserve Bank of India \n(Credit Information Companies) Directions, 2025, for assessing the quality of \ndata submissions by CIs to CICs and improving the same over a period of time. \n17. A CI shall undertake half yearly review of the DQI for all segments to improve \nthe quality of the data being submitted to CICs.  A report consisting of issues \nidentified and corrective steps taken shall be placed before its top management \nby each CI for review within two months from the end of that half-year. \nE. Correction of Credit Information Report \n18. A CI shall abide by the time periods stipulated under CICRA and the Rules and \nRegulations framed thereunder in respect of updation, alteration of credit \ninformation, resolving disputes, etc. Procedure prescribed under Rules 20 and \n21 of the CIC Rules, 2006 in this regard shall be adhered to. Deviations from \nstipulated time limits shall be monitored and commented upon in the periodical \nreports/reviews put up to the Board / Committee of Board on customer service. \n19. A CI shall have arrangements in place to receive customer requests for \nrectification of data in CIRs. In order to maintain high data quality, all \nerroneous data shall be corrected at the source by the CI that originally \nsubmitted the data. \nF. Use of credit information reports in credit appraisal \n20. A CI shall include in their loan policies / credit appraisal processes, suitable \nprovisions for obtaining CIRs from one or more CICs so that the credit decisions \nare based on credit information available in the system. \n \n3 Substituted with effect from July 01, 2026, vide Reserve Bank of India (Commercial Banks – Credit Information \nReporting) Amendment Directions, 2025 dated December 04, 2025."}
{"text": "G. Display of information \n21.    A CI which is a secured creditor as per the Securitisation and Reconstruction of                        \nFinancial Assets and Enforcement of Security Interest (SARFAESI) Act, 2002, shall \ndisplay, on its website, information in respect of the borrowers whose secured assets \nhave been taken into possession by the CIs under the SARFAESI Act, 2002 as per \nthe format given in Annex IV. The list consisting of this information shall be updated \non monthly basis. \n(1) \n The following clarifications in this regard need to be noted by the CIs: \n(i) \nSecured assets possessed by a CI under the SARFAESI Act, 2002 on or \nafter September 25, 2023 should be disclosed on its website. \n(ii) \nThe assets possessed and already sold under SARFAESI Act, 2002 need \nnot be displayed on the website. \n(iii) The secured assets possessed by a CI shall be removed from the website \nin the event of the following circumstances: \n(a) \nwhen the secured asset is sold; or \n(b) \nwhen the secured creditor receives the outstanding amount (which \nincludes the principal, interest and any other dues payable by the \nborrower to the secured creditor) or after payment of the agreed \nsettlement amount from the borrower. \n(iv) The SARFAESI Act, 2002 does not classify possession as symbolic or \nphysical. Accordingly, a CI shall display information on secured assets \npossessed under Section 13 (4) of the SARFAESI Act, 2002. This includes \nthe display of both symbolically and physically possessed assets on the \nwebsite. \n(v) \nBoth movable and immovable secured assets possessed under Section \n13 (4) of the SARFAESI Act, 2002, on which the information is already \npublished in the newspapers in terms of Rule 3 (1) or Rule 6 (2) of the \nSecurity (Enforcement) Rules of 2002 in case of movable property, and \nRule 8 (2) ibid in case of immovable property, shall be displayed on the \nwebsite of a CI."}
{"text": "(vi) The ‘outstanding amount’ to be displayed on the website of a CI shall be \nas per definition provided under Section 13 (9) (b) of the SARFAESI Act, \n2002 i.e. it shall include principal, interest and any other dues payable by \nthe borrower to the secured creditor in respect of secured asset as per the \nbooks of account of the secured creditor. \n(vii) The ‘outstanding balance’, ‘asset classification’ and ‘date of asset \nclassification’ of the secured assets possessed under Section 13 (4) of the \nSARFAESI Act, 2002, shall be as per the information published in the \nnewspapers in terms of Rule 3 (1) or Rule 6 (2) of the Security \n(Enforcement) Rules of 2002 in case of movable property, and Rule 8 (2) \nin case of immovable property. \n(viii) The ‘State’ column of the Annex IV corresponds to that of the branch, as \nthe borrower's address column inherently captures the State to which the \nborrower belongs. \n(ix) Details in the ‘Guarantor Name (wherever applicable)’ column of the \nAnnex IV should be limited to guarantors who have created a security \ninterest in favour of the CI and whose assets are possessed under the Act. \n(x) \nThe monthly updates mentioned above specifically relate to the inclusion \nof new secured assets possessed by a CI, and the removal of the secured \nassets that have been sold or resolved by the CI. \n(xi) While the lead lender as per the consortium agreement may initiate \nSARFAESI proceedings, all consortium members are required to \nindividually display on their website the details of assets taken into \npossession, including outstanding amount and other details as per the \npari-passu charge and consortium agreement ensuring transparency. \nH. Applicability of other instructions issued by Department of Regulation \n22. A CI shall ensure compliance with the applicable instructions on credit \ninformation reporting, as prescribed in the following Directions/ Circulars: \n(1) \nReserve Bank of India (Commercial Banks – Credit Cards and Debit Cards: \nIssuance and Conduct) Directions, 2025, as amended from time to time. \n(2) \nReserve Bank of India (Commercial Banks – Classification, Valuation and"}
{"text": "Operation of Investment Portfolio) Directions, 2025, as amended from time to time. \n(3) \nReserve Bank of India (Commercial Banks – Credit Facilities) Directions, 2025  \n(4) \nReserve Bank of India (Commercial Banks – Transfer and Distribution of Credit \nRisk) Directions, 2025  \n(5) \nReserve Bank of India (Commercial Banks – Undertaking of Financial Services) \nDirections, 2025"}
{"text": "Chapter-IV Technical Working Group \nA. \nInstructions on Technical Working Group \n23. In order to institutionalize a continuing mechanism for reviewing and making \nchanges where necessary in the data formats, a Technical Working Group \n(TWG) shall be formed. The TWG shall carry out the following functions:  \n(1) \nReview the data reporting formats, at least once a year, and make \nrecommendations, if any, to the Reserve Bank in this regard.  \n(2) \nFrame rules on data fields for all data reporting formats, viz., consumer, \ncommercial, micro finance (MFI) segments. The data formats after finalisation \nby the Group will be submitted to RBI for approval. \n(3) \nAny other matter relating to collection and dissemination of credit \ninformation as the Reserve Bank may assign from time to time. \n24. The TWG shall comprise of representatives from Public Sector Banks, Private \nSector Banks, Foreign Banks, Primary (Urban) Cooperative Banks (UCBs), \nRegional Rural Banks (RRBs), All India Notified Financial Institutions (AIFIs), \nNon-Banking Financial Companies (NBFCs), Housing Finance Companies \n(HFCs), Asset Reconstruction Companies (ARCs) India Banks’ Association \n(IBA), Micro Finance Institutions Network (MFIN), Sa-Dhan and CICs.  \n25. Meetings of the TWG shall be held at least once in a calendar year. The four \nCICs shall act as convenor of the TWG by rotation (for each calendar year), in \nalphabetical order of the name.  \nB. \nStanding Sub-Group of TWG \n \n26. A Standing Sub-Group of TWG shall be constituted to function as an advisory \nand collaborative body to offer expert insights and make recommendations on \ntechnical aspects of credit information reporting. Its purpose would be to support \nin-depth discussions regarding challenges encountered by CIs and CICs in \nrelation to credit information reporting. This includes necessary modifications, \nincluding changes in the IT systems, that may be required in the data reporting \nformats. The Sub-Group shall work to support the broader TWG to ensure a \nholistic approach to strengthening the credit information reporting ecosystem."}
{"text": "27. The Sub-Group of TWG would consist of representatives from Public-Sector \nBanks, Private Sector Banks, Foreign Banks, Small Finance Banks, Regional \nRural Banks, Urban Cooperative Banks, Non-Banking Financial Companies, \nAsset Reconstruction Companies, Self-Regulating Organizations (SROs), viz., \nMFIN and Sa-Dhan, and all CICs.  \n28. Members of the Sub-Group shall be selected by the convenor with prior \napproval of the Reserve Bank. To enhance the overall expertise and \neffectiveness of the discussions, members of the Sub-Group shall nominate \nsubject matter experts to its meetings.  \n29. The Sub-Group of TWG shall meet at least on a half yearly basis to discuss \ncredit information reporting issues and seek potential resolutions.  \n30. To ensure effective coordination, the CIC that assumes the role of TWG \nconvenor for a specific year shall also act as convenor of the Sub-Group in that \nparticular calendar year.  \n31. To ensure proper preparation and informed discussions, the convenor shall \nsend the meeting agenda and notes at least fifteen (15) days before the \nscheduled meeting. Additionally, if members desire to introduce a new issue or \nitem for discussion, they should send a note outlining the points of discussion \nand proposed solutions to the convenor.  \n32. Action points emanating from discussions of the Sub-Group shall contain \nspecific timelines required for their implementation by CICs and CIs.  \n33. Recommendations of the Sub-Group of TWG shall be forwarded to the \nDepartment of Regulation, Central Office, Reserve Bank of India for perusal. If \nrequired, RBI may seek TWG’s opinion on these recommendations. \nChapter-V Customer Service and Grievance Redressal \nA. Strengthening of customer service  \n34. In order to strengthen and improve the efficacy of the grievance redress \nmechanism and customer service provided by the CIs, the following measures \nshall be put in place by a CI: \n(1) \nUpdation of credit information with CICs"}
{"text": "(i) \nA CI shall send alerts through SMS / email to customers while submitting \ninformation to CICs regarding default / days past due (DPD) in existing \ncredit facilities, wherever the mobile number/email ID details are available. \n(ii) \nTo enable sending of alerts through SMS / email, the Uniform Credit \nReporting Format for reporting credit information by a CI to CICs has been \nmodified as detailed in Annex V. \n(iii) A CI shall organize special awareness campaigns to sensitise its \ncustomers about benefits of submission of their mobile numbers / email \nIDs. \n(2) \nSetting up of nodal points / officials \n(i) \nA CI shall have a dedicated nodal point / official of contact for CICs for \nredress of customer grievances. Details of the nodal point / official along \nwith email ID and telephone / mobile number shall be furnished by the CI to \nCICs. \n(ii) \nA CI shall inform CICs of any changes in the nodal points / official within \nfive calendar days of such a change. \n(3) \nReasons for rejection of requests for data correction \n(i) \nA CI shall inform the customers the reasons for the rejection of their request \nfor data correction, if any, to enable such customers to better understand \nthe issues in the CIR. \n(ii) \nA CI shall use the list of reasons for rejection of requests circulated by CICs, \nwhile communicating the rejections of the request for data correction made \nby customers / CICs during the grievance redress process. \n(4) \nRoot Cause Analysis of complaints \n(i) \nA CI shall undertake Root Cause Analysis (RCA) of the customer \ngrievances at least on a half yearly basis. CIs shall also use, inter alia, \ninformation on data rejected by the CICs and DQI provided by CICs as \nsources of information for carrying out RCA. \n(ii) \nThe RCA shall be reviewed by the top management at least on an annual \nbasis."}
{"text": "B. Framework for compensation to customers \n35. A CI shall implement the following compensation mechanism for delayed \nupdation/ rectification of credit information: \n(1) \n Complainants shall be entitled to a compensation of ₹100 per calendar day in \ncase their complaint is not resolved within a period of thirty calendar days from the \ndate of the initial filing of the complaint by the complainant with a CI / CIC. \nExplanation: \n(i) \nSection 21 (3) of CICRA, 2005 provides that a complainant may request a \nCIC or CI to update the credit information by making an appropriate \ncorrection, addition or otherwise, and on such request the CI or CIC shall \ntake steps to update the credit information within 30 days after being \nrequested to do so. \n(ii) \nRule 20 (3) (c) of CIC Rules, 2006 provides that the CI shall forward the \ncorrected particulars of the credit information to the CIC or complainant \nwithin a period of 21 days from the date when the CI was informed of the \ninaccuracy in the credit information. \n(iii) The combined reading of Section 21(3) of CICRA, 2005 and Rule 20 (3) \n(c) of CIC Rules, 2006 provide the CI and the CIC, collectively, an overall \nlimit of thirty (30) days to resolve/ dispose of the complaint. In effect, this \nwould mean that a CI would get 21 days and CICs would effectively get \nthe remainder of nine days for complete resolution of the complaint. \n(2) A CI shall pay compensation to the complainant if it has failed to send updated \ncredit information to the CICs by making an appropriate correction or \naddition or otherwise within 21 calendar days of being informed by the \ncomplainant or a CIC. \n(3) The complainant shall be advised by the CI / CIC of the action taken on the \ncomplaint in all cases, including the cases where the complaint has been \nrejected. In cases of rejection, the reasons for rejection shall also be provided \nby CI and CIC. \n(4) \nCompensation to be provided by the CICs / CIs to the complainant (for delayed \nresolution beyond 30 calendar days of filing the complaint) shall be apportioned"}
{"text": "among the CIs / CICs concerned proportionately.  \nIllustrations: \n(i) \nComplaints registered with CIC by the complainant \nCIs have maximum 21 days’ time and CICs have the remaining period, within the \noverall time period of 30 days from the date of receipt of the complaint for its \nresolution. Compensation payable by the CICs/ CIs shall be calculated under \nvarious scenarios as illustrated below: \nCase 1 \n• \nComplaint registered with a CIC on January 1, 2022. \n• \nThe CIC seeks confirmation from the CI (for e.g. Bank A) on January 12, 2022. \n• \nBank A provides confirmation to the CIC on February 2, 2022 (21st day would \nbe February 2, 2022) – no delay by Bank A. \n• \nThe CIC resolves and provides rectified CIR to the complainant on February \n3, 2022. \n• \nCompensation of ₹300/- shall be provided by the CIC to the complainant for \ndelay of three (3) days beyond the permissible period of 30 days (i.e. in this case \nby January 31, 2022).  \nCase 2 \n• \nComplaint registered with a CIC on January 1, 2022. \n• \nThe CIC seeks confirmation from Bank A on January 5, 2022. \n• \nBank A provides confirmation to the CIC on January 26, 2022 (i.e. within 21 \ndays) – no delay by Bank A. \n• \nThe CIC resolves and provides rectified CIR to the complainant on February 3, \n2022. \n• \nCompensation of ₹300/- shall be provided by the CIC to the complainant for \ndelay of three (3) days beyond the permissible period of 30 days (i.e. in this case \nby January 31, 2022)."}
{"text": "Case 3 \n• \nComplaint registered with a CIC on January 1, 2022 \n• \nThe CIC seeks confirmation from Bank A on January 5, 2022. \n• \nBank A provides confirmation to the CIC on January 28, 2022 (21st day would \nbe January 26, 2022) – 2 days delay by Bank A \n• \nIf CIC resolves and provides rectified CIR to the complainant on February 2, \n2022 - Compensation of ₹200/- shall be provided by the Bank A to the complainant \nfor a delay of two (2) days beyond the permissible period of 30 days (i.e. in this \ncase by January 31, 2022). \n• \nIf CIC resolves and provides rectified CIR to the complainant on February 3, \n2022 – Total compensation of ₹300/- (₹200/- by Bank A and ₹100/- by CIC) shall \nbe provided to the complainant for delay of three (3) days beyond the permissible \nperiod of 30 days (i.e. in this case by January 31, 2022). \nCase 4 \n• \nComplaint registered with a CIC on January 1, 2022 \n• \nThe CIC seeks confirmation from Bank A, Bank B, Bank C, Bank D, Bank \nE on January 5, 2022 – i.e. the CIC has taken 4 days to seek confirmation.  \n• \nFor Bank A, B, C, D and E – (21st day would be January 26, 2022)  \n• \nIf Bank A provides confirmation to CIC on January 26, 2022 – No delay  \n• \nIf Bank B provides confirmation to CIC on January 31, 2022 – 5 days delay \n• \nIf Bank C provides confirmation to CIC on February 2, 2022 – 7 days delay \n• \nIf Bank D provides confirmation to CIC on February 4, 2022 – 9 days delay \n•   If Bank E provides confirmation to CIC on February 6, 2022 – 11 days delay \n• \nTherefore, total delay in resolution of complaint is as follows: \n• \nIf the CIC resolves and provides rectified CIR to the complainant on February \n6, 2022 – Total compensation of ₹600 shall be provided to the complainant, on a \nweighted average basis, as under, for a delay of 6 days beyond the permissible \nperiod of 30 days (i.e. in this case by January 31, 2022): \n32 \ndays"}
{"text": "Explanation: The delay of six days shall be apportioned by the CIs/CICs on \nweighted average of the extent of delay by each CIs/CICs. In the above case, the \noverall delay is 6 days and therefore the complainant shall be entitled for total \ncompensation of ₹600. This needs to be apportioned between all the defaulting \nbanks (in this case Bank B, C, D and E). Cumulatively, the delay of all the defaulting \nbanks put together is 32 days (5+7+9+11 days). Therefore, the compensation \namount of ₹600 shall be apportioned on weighted average of the delay by each CIs \nin relation to the overall delay of 32 days in this case. \n Bank A = No compensation \n Bank B = (5*600)/32 = ₹93.75 \n Bank C= (7*600)/32 = ₹131.25 \n Bank D = (9*600)/32 = ₹168.75 \n Bank E = (11*600)/32 = ₹206.25 \n CIC = No compensation \n• \n If the CIC resolves and provides rectified CIR to the complainant on \nFebruary 11, 2022, total days taken by CIC would be 9 days (i.e. 4+ 5 days). Total \ncompensation of ₹1100 shall be provided to the complainant, on a weighted \naverage basis, as under, for delay of 11 days beyond the permissible period of 30 \ndays (i.e. in this case by January 31, 2022): \n \nBank A = No compensation \n \nBank B = (5*1100)/32 = ₹171.88 \n \nBank C = (7*1100)/32 = ₹240.62 \n \nBank D = (9*1100)/32 = ₹309.38 \n \nBank E = (11*1100)/32 = ₹378.12 \n \nCIC = No compensation (as CIC has taken overall 9 days) \n• \nIf the CIC resolves and provides rectified CIR to the complainant on \nFebruary 15, 2022. CIC has taken 13 days (i.e. 4 days + 9 days) to provide a final \nrectified CIR. Total compensation of ₹1500 shall be provided to the complainant,"}
{"text": "on a weighted average basis as under, for the delay of 15 days beyond the \npermissible period of 30 days (i.e. in this case by January 31, 2022): \n \nBank A = No compensation \n \nBank B = (5*1500)/36 = ₹208.34 \n \nBank C = (7*1500)/36 = ₹291.66 \n \nBank D = (9*1500)/36 = ₹375.00 \n \nBank E = (11*1500)/36 = ₹458.34 \n CIC = (4*1500)/36 = ₹166.66 \nCase 5 \n• Complaint registered with a CIC on January 1, 2022 \n• The CIC seeks confirmation from Bank A on January 5, 2022 \n• Bank A provides confirmation to the CIC on January 28, 2022 (21st day would be \nJanuary 26, 2022) – 2 days delay \n• If, CIC resolves and provides rectified CIR to Bank A on January 31, 2022 (i.e. \nresolution done within 30 days of receiving the complaint) - No case for \nCompensation. \nHowever, the CI would be liable for penal action as deemed fit by the Reserve \nBank of India as per provisions of CICRA, 2005 and Rules and Regulations farmed \nthereunder. \n(ii) \nComplaints registered with CIs by the complainant \nCase 6  \n• Complaint registered with a CI (for e.g. Bank A) on January 1, 2022 \n• Bank A provides rectified details to CIC on January 22, 2022 (21st day would be \nJanuary 22, 2022) – no delay by Bank A. \n• If the CIC resolves and provides rectified CIR to Bank A on January 31, 2022 and \nBank A provides the rectified CIR to the complainant on January 31, 2022 – No \ncase for compensation. \n32 + 4 = 36 \ndays"}
{"text": "• If the CIC resolves and provides rectified CIR to Bank A on January 31, 2022 and \nBank A provides the rectified CIR to the complainant on February 1, 2022 – A \ncompensation of ₹100 shall be provided by the Bank A to the complainant for delay \nof 1 days beyond the permissible period of 30 days (i.e. in this case by January \n31, 2022). \n• If the CIC resolves and provides rectified CIR to Bank A on February 1, 2022 and \nBank A provides the rectified CIR to the complainant on February 1, 2022 - A \ncompensation of ₹100 shall be provided by the CIC to the complainant for delay of \n1 day beyond the permissible period of 30 days (i.e. in this case by January 31, \n2022). \n• If the CIC resolves and provides rectified CIR to Bank A on February 1, 2022 and \nBank A provides the rectified CIR to the complainant on February 2, 2022 - Total \ncompensation of ₹200 shall be provided [₹100 by the CIC and ₹100 by Bank A] to \nthe complainant for delay of 2 day beyond the permissible period of 30 days (i.e. \nin this case by January 31, 2022). \nNote: Where the grievance/ complaint involves inaccurate credit information of \nmore than one (1) CI, the complaint shall be registered by the customer with the \nconcerned CIC. The CIC shall coordinate with all CIs concerned, and furnish to \nthe customer a comprehensive resolution of grievance. \nCase 7 \n• Complaint registered with a CI (for e.g. Bank A) on January 1, 2022 \n• Bank A resolves and provides rectified details to the CIC on January 25, 2022 \n(21st day would be January 22, 2022) – 3 days delay by Bank A. \n• If the CIC resolves and provides rectified CIR to Bank A on January 31, 2022 and \nBank A provides rectified CIR to complainant on January 31, 2022 - No case for \nCompensation. \n• If the CIC resolves and provides rectified CIR to Bank A on February 3, 2022 (i.e. \nthe CIC takes 9 days after being informed by Bank A) and Bank A provides rectified \nCIR to the complainant on February 3, 2022 – A compensation of ₹300 shall be \nprovided by Bank A to the complainant for delay of 3 days beyond the permissible \nperiod of 30 days (i.e. in this case by January 31, 2022)."}
{"text": "• If the CIC resolves and provides rectified CIR to Bank A on February 3, 2022 and \nBank A provides rectified CIR to the complainant on February 4, 2022 – A \ncompensation of ₹400 shall be provided by Bank A to the complainant for delay of \n4 days beyond the permissible period of 30 days (i.e. in this case by January 31, \n2022). \n• If the CIC resolves and provides rectified CIR to Bank A on February 4, 2022 and \nBank A provides rectified CIR to the complainant on February 4, 2022 – Total \ncompensation of ₹400 [₹100 by the CIC and ₹300 by Bank A] shall be provided to \nthe complainant for delay of 4 days beyond the permissible period of 30 days (i.e. \nin this case by January 31, 2022). \n• If the CIC resolves and provides rectified CIR to Bank A on February 4, 2022 and \nBank A provides rectified CIR to the complainant on February 5, 2022 – Total \ncompensation of ₹500 [₹100 by CIC and ₹400 by Bank A] shall be provided to the \ncomplainant for delay of 5 days beyond the permissible period of 30 days (i.e. in this \ncase by January 31, 2022). \n(5) Where the grievance / complaint involves inaccurate credit information provided \nby more than one CI, the complaint shall be registered by the complainant with \nthe concerned CIC. The CIC shall coordinate with all the CIs concerned and \nfurnish the complainant with a comprehensive resolution of the grievance. \n(6) Where the complaint has been received and registered by a CI and there has \nbeen a delay in the resolution of the complaint, the CI shall inform the concerned \nCIC(s) and the complainant after the final resolution, regarding total delay (in \ncalendar days) and the amount of compensation to be paid by the CI and/ or \nCIC(s). \n(7) The date of the resolution of the grievance shall be the date when the rectified \nCIR has been sent by the CIC or CI to the postal address or email ID provided \nby the complainant. \n(8) A CI shall make appropriate provision in their complaint submission format (both \nonline and offline) for enabling the complainant to submit the contact details, \nemail ID, and bank account details/ Unified Payment Interface (UPI) ID for \ncrediting the compensation amount. The onus of providing accurate details will"}
{"text": "lie with the complainant and the CIs will not be held responsible for any incorrect \ninformation provided by the complainant. \n(9) The compensation amount shall be credited to the bank account of the \ncomplainant within five working days of the resolution of the complaint. \n(10) The complainant can approach RBI Ombudsman, under the Reserve Bank - \nIntegrated Ombudsman Scheme, 2021, in case of wrongful denial of \ncompensation by CIs or CICs. \n(11) In case of wrongful denial of compensation by a CI which is yet to be covered \nunder the Reserve Bank - Integrated Ombudsman Scheme, 2021, the \ncomplainant can approach Consumer Education and Protection Cell (CEPC) \nfunctioning from Regional Offices (ROs) of RBI. \n(12) The compensation framework shall not be applicable in the following cases: \n(i) \ndisputes for which remedy has been provided under Section 18 of CICRA, \n2005. The Section 18 of CICRA, 2005 provides that for disputes arising \namongst, CICs, CIs, borrowers, and clients on matters relating to the \nbusiness of credit information and for which no remedy has been provided \nunder CICRA, 2005, such disputes shall be settled by conciliation or \narbitration as provided in the Arbitration and Conciliation Act, 1996. \n(ii) \ncomplaints / references relating to (a) internal administration, (b) human \nresources, (c) pay and emoluments of staff, and (d) references in the nature \nof suggestions and commercial decisions of the CI. \n(iii) complaints that have been decided by or are already pending in other fora \nsuch as Consumer Disputes Redressal Commission, Courts, Tribunals, etc. \nC. Reserve Bank- Integrated Ombudsman Scheme, 2021 \n36. A CI covered under the Reserve Bank – Integrated Ombudsman Scheme, 2021 \n(RBIOS, 2021) shall comply with the directions provided under the said \nScheme. \nD. Appointment of Internal Ombudsman \n37. A CI covered under the Internal Ombudsman framework shall adhere to the \ninstructions issued vide Master Direction – Reserve Bank of India (Internal"}
{"text": "Ombudsman) Directions, 2023 dated December 29, 2023 (as amended from \ntime to time)."}
{"text": "Chapter-VI Best Practices \n38. A CI shall take into account the best practices as detailed below, while \nformulating or reviewing its policies and procedures under the CICRA with the \napproval of their Board of Directors: \n(1) \nInstances of non-updation of repayment information could be avoided by \ncentralising the issue of no objection certificates (NOCs) and providing information \nto CICs. \n(2) \nCustomer grievance redressal should be given top priority especially in respect \nof complaints relating to updation / alteration of credit information. \n(3) \nGrievance redressal in respect of credit information should be integrated with the \nexisting systems for grievance redressal. Aspects relating to customer grievances \npertaining to credit information may also be an integral part of customer service \npolicy of a CI. \n(4) \nA CI shall give full customer information to the CICs. For instance, identifier \ninformation like PAN number, Voters ID Card number, etc. is not provided by CIs \nfor all records. \n(5) \nFirst time borrowers’ loan applications should not be rejected just because they \nhave no credit history. \n(6) \nWith a view to decreasing court cases involving CIs and CICs, complaints need \nto be addressed by them on an urgent basis. A CI shall have a structured process \nof complaint redressal including the setting up of Consumer Protection \nCommittee of the Board."}
{"text": "Chapter-VII Repeal and Other Provisions  \n \nA. Repeal and saving \n39. With the issue of these Directions, the existing Directions, instructions, and \nguidelines relating to credit information reporting as applicable to Commercial \nBanks stand repealed, as communicated vide circular DOR.RRC.REC.302/33-\n01-010/2025-26 dated November 28, 2025. The Directions, instructions and \nguidelines repealed prior to the issuance of these Directions shall continue to \nremain repealed. \n40. Notwithstanding such repeal, any action taken or purported to have been taken, \nor initiated under the repealed Directions, instructions, or guidelines shall \ncontinue to be governed by the provisions thereof. All approvals or \nacknowledgments granted under these repealed lists shall be deemed as \ngoverned by these Directions. Further, the repeal of these directions, instructions, \nor guidelines shall not in any way prejudicially affect: \na) any right, obligation or liability acquired, accrued, or incurred thereunder;  \nb) any, penalty, forfeiture, or punishment incurred in respect of any \ncontravention committed thereunder;  \nc) any investigation, legal proceeding, or remedy in respect of any such right, \nprivilege, obligation, liability, penalty, forfeiture, or punishment as aforesaid; \nand any such investigation, legal proceedings or remedy may be instituted, \ncontinued, or enforced and any such penalty, forfeiture or punishment may \nbe imposed as if those directions, instructions, or guidelines had not been \nrepealed. \nB. Application of other laws not barred \n41. The provisions of these Directions shall be in addition to, and not in derogation \nof the provisions of any other laws, rules, regulations, or directions, for the time \nbeing in force."}
{"text": "C. Interpretations \n42. For the purpose of giving effect to the provisions of these Directions or in order \nto remove any difficulties in the application or interpretation of the provisions of \nthese Directions, the RBI may, if it considers necessary, issue necessary \nclarifications in respect of any matter covered herein and the interpretation of \nany provision of these Directions given by the RBI shall be final and binding. \n \n(J P Sharma) \n \nChief General Manager"}
{"text": "Annex I \nUniform Credit Reporting Format \n \nForm 1: Uniform Credit Reporting Format (Consumer) \n \nSegments \nFields \nHeader \nReporting \nMember / \nProcessor \nUser ID \nReporting Member \n/ Processor Short \nName \nCycle \nIdentification \nDate \nReported \nand \nCertified \nReporting \nPassword \nAuthentication \nMethod \nMember Data \nName \nConsumer Name \nDate of Birth \nGender \nID \nID Type \nID Number \nIssue Date \nExpiration Date \nTelephone \nTelephone Number \nTelephone Extension \nTelephone Type \nEmail \nE-Mail ID \nAddress \nConsumer Address \nState Code \nPIN \nCode \nAddress Category \nResidence Code \nAccount \nCurrent/New \nReporting \nMember \nCode \nCurrent/New \nMember Short \nName \nCurrent / New \nAccount \nNumber \nAccount Type Ownership \nIndicator \nDate Opened/ \nDisbursed \nDate of Last \nPayment \nDate Closed \nDate Reported and \nCertified \nHigh Credit/ \nSanctioned \nAmount \nCurrent \nBalance \nAmount \nOverdue \nNumber of Days \nPast Due \nOld Reporting \nMember Code \nOld Member \nShort Name \nOld Account \nNumber \nOld Account \nType \nOld \nOwnership \nIndicator \nSuit Filed/ Wilful \nDefault \nCredit Facility \nStatus \nAsset \nClassification \nValue of \nCollateral \nType of Collateral \nCredit Limit \nCash Limit \nRate of Interest \nRepayment \nTenure \nEMI Amount \nWritten-off \nAmount \n(Total) \nWritten-off \nAmount \n(Principal) \nSettlement \nAmount \nPayment \nFrequency \nActual \nPayment \nAmount \nOccupation Code \nIncome \nNet/Gross Income \nIndicator \nMonthly/Annual \nIncome Indicator \n \nNote: The reporting fields of the Consumer reporting format to incorporate among \nothers the following catalogue values: \nField Name \n \n \nRemarks \nAccount Type \nInclusion of additional catalogue values: \n• \nShort term personal loan \n• \nPriority Sector – Gold loan \n• \nTemporary Overdraft (account should be considered \nclosed by CICs when it is not reported in subsequent \nmonths by CIs in view \nof credit balance in the said account)"}
{"text": "Credit Facility Status \nInclusion of additional catalogue values: \n• \nRestructured due to COVID-19 \n• \nPost Write Off Closed \n• \nRestructured and Closed \n• \nAuctioned and Settled \n• \nRepossessed and Settled \n• \nGuarantee Invoked \nOwnership Indicator \nInclusion of additional catalogue value: \n• \nDeceased \nType of Collateral \nInclusion of additional catalogue value: \n• \nMultiple Securities and \nOthers \nID Type \nInclusion of additional catalogue values: \n• \nNREGA card number \n• \nCKYC \nPayment frequency \nInclusion of additional catalogue values: \n• \nBullet payment \n• \nDaily \n• \nHalf yearly \n• \nYearly \n• \nOn Demand \nAddress Category \nInclusion of additional catalogue value: \nMortgage Property address \nHigh \nCredit/ \nSanctioned Amount \nThe reporting field to be mandatory"}
{"text": "Form 2: Uniform Credit Reporting Format (Commercial) \n \nSegments \nFields \nHeader \nMember ID \nPrevious \nMember ID \nDate of Creation \n& Certification of \nInput File \nReporting / \nCycle Date \nInformation Type Filler \nBorrower \nMember \nBranch Code \nPrevious \nMember \nBranch Code \nBorrower s Name \nBorrower Short \nName \nCompany \nRegistration \nNumber \nDate of \nIncorporation \nPAN \nCIN \nTIN \nService Tax \nnumber \nUdhyam \nRegistration \nNumber \nBorrower s \nLegal \nConstitution \nBusiness \nCategory \nBusiness / Industry \nType \nClass of \nActivity 1 \nClass of \nActivity 2 \nClass of Activity 3 SIC Code \nSales Figure \nFinancial Year \nNumber of Employees \nCredit Rating \nAssessment \nAgency \n/ Authority \nCredit Rating As \nOn \nCredit Rating \nExpiry Date \nFiller \nAddress \nBorrower \nOffice \nLocation \nType \nBorrower \nOffice \nDUNS \nNumber \nAddress \nLine 1 \nAddress \nLine 2 \nAddress \nLine 3 \nCity/Town \nDistrict \nState/Union Territory \nPin Code \nCountry \nMobile \nNumber(s) \nTelephone Area \nCode \nTelephone \nNumber(s) \nFax Area Code \nE-mail ID \nFiller \nRelationship \nRelationship \nDUNS \nNumber \nRelated Type Relationship Business \nEntity Name \nBusiness \nCategory \nBusiness / \nIndustry \nType \nIndividual Name Prefix \nFull Name \nGender \nCompany \nRegistration \nNumber \nDate of \nIncorporation \nDate of Birth \nPAN \nVoter ID \nPassport Number \nDriving \nLicense ID \nUID \nRation Card No \nCIN \nDIN \nTIN \nService Tax number \nCKYC \nPercenta\nge of \nControl \nAddress Line 1 \nAddress Line 2 \nAddress Line 3 \nCity/Town \nDistrict \nState/Union \nTerritory \nPin Code \nCountry \nMobile \nNumber(s) \nTelephone \nNumber(s) \nTelephone Area \nCode \nFax Number(s) \nFax Area Code \nFiller \nSegments \nFields \nCredit Facility \nAccount \nNumber \nPrevious \nAccount \nNumber \nFacility / \nLoan \nActivation \n/ \nSanction \nDate \nSanctioned \nAmount/ \nNotional \nAmount of \nContract \nCurrency \nCode \nCredit Type \nTenure / \nWeighted \nAverage \nmaturity \nperiod of \nContracts \nRepayment \nFrequency \nDrawing Power Current \nBalance / \nLimit Utilized \n/Mark to \nMarket \nNotional \nAmount of \nOut- \nstanding \nRestructur\ned \nContracts \nLoan Expiry / \nMaturity Date \nLoan Renewal \nDate \nAsset \nClassification / \nDays Past Due \n(DPD) \nAsset Classification \nDate \nAmount \nOverdue / \nLimit Overdue \nOverdue \nBucket 01 (1 – \n30 days) \nOverdue \nBucket 02 \n(31 – 60 \ndays) \nOverdue Bucket 03 \n(61 – \n90 days) \nOverdue \nBucket 04 \n(91 – 180 \ndays) \nOverdue Bucket \n05 (Above 180 \ndays)"}
{"text": "High Credit \ninstalment \nAmount \nLast Repaid \nAmount \nAccount Status Account \nStatus \nDate \nWritten Off \nAmount \nSettled Amount \nMajor reasons for \nRestructuring4 \nAmount of \nContracts \nClassified as \nNPA \nAsset based \nSecurity \ncoverage \nGuarantee \nCoverage \nBank \nRemark \nCode \nWilful \nDefault \nStatus \nDate \nClassified \nas Wilful \nDefault \nSuit Filed Status \nSuit Reference \nNumber \nSuit Amount in \nRupees \nDate of Suit \nDispute ID No. \nTransaction \nType \nCode \nOther_BK \nUFCE (Amount) \nUFCE Date \nGuarantor \nGuarantor \nDUNS \nGuarantor \nType \nBusiness \nCategory \nBusiness \n/ \nIndustry \nType \nGuarantor \nEntity \nName \nIndividual \nName \nPrefix \nFull Name \nGender \nCompany \nRegistration \nNumber \nDate of \nIncorporation \nDate of Birth \nPAN \nVoter ID \nPassport Number \nDriving License ID \nUID \nRation Card No CIN \nDIN \nTIN \nService Tax \nnumber \nOther ID \nAddress Line 1 Address Line 2 Address Line 3 City/Town \nDistrict \nState/Unio\nn Territory \nPin Code \nCountry \nMobile \nNumber(s) \nTelephone \nArea \nCode \nTelephone \nNumber(s) \nFax Area Code Fax Number(s) \nGuarantee Invocation Date \nSecurity \nValue of \nSecurity \nCurrency Type Type of \nSecurity \nSecurity \nClassificati\non \nDate of \nValuation \nFiller \nDishonour of Cheques Date of \nDishonour \nAmount \nInstrument \n/ Cheque \nNumber \nNumber of \ntimes \ndishonoured \nCheque \nIssue \nDate \nReaso\nn for \nDishon\nour \nFiller \nFile Closure \nNumber of \nBorrower \nSegments \nNumber of \nCredit \nFacility \nSegments \nFiller \n \nNote: The reporting fields of the Commercial reporting format to incorporate among others the \nfollowing catalogue values: \n \nField Name \nAdditional catalogue values \nAccount Status \nInclusion of additional catalogue value: \n• \nRestructured and Closed \n \n4 This field would help in understanding whether the restructuring of loan of the borrower was due to external/ extraneous \nfactors such as external environment, general downturn in economy, etc., or company/ borrower specific issues such as \nchange in management, performance of promoters, etc."}
{"text": "Credit Type \nInclusion of additional catalogue values: \n• \nMudra term loan \n• \nMudra working capital \n• \nTemporary Overdraft (account should be considered closed \nby CICs when it is not reported in subsequent months by CIs \nin view \nof credit balance in the said account) \nMajor \nreasons \nfor \nrestructuring \nInclusion of additional catalogue value: \n• \nRestructured due to COVID-19 \nSanction Date \nThe reporting field to be mandatory \nLocation Type \nInclusion of additional catalogue value \n• \nMortgage Property address \nRelationship \nInclusion of additional catalogue value \n• \nKarta (HUF) \nAsset Classification/ \nDays Past Due \nRemoval of catalogue values: \n• \nSpecial Mention Accounts \n• \nDoubtful \nBorrower’s Legal \nConstitution \nRemoval of catalogue value: \n• \nNot Classified \nClass of Activity \nTo be reported as per Basic Statistical Returns 1 and 2"}
{"text": "Form 3: Uniform Credit Reporting Format for MFIs (Including SHG) \nThis document provides description of the file format for Microfinance data to be \nreported to CICs. This format follows Group, Consumer, Account structure – Multiple \nGroups, Each Group with Multiple Consumers and Each Consumer if taken credit has \nan account. It is recommended that a separate file is shared with CIC for SHG \naccounts and JLG + Individual accounts. All Microfinance borrowings in the names of \nthe individuals, regardless of the purpose, should be included in this format. The data \nshould contain all live loan accounts during the relevant period, all accounts which \ngot closed during the period and all accounts which opened during the period. \nIrrespective of the frequency of data sharing, the format of data sharing remains the \nsame. \nA. Segments in Input File Format \nThe following table describes the different segments that make up the Data Input File \nFormat \n \n# \nSegment \nSegment Tag \nOption \nOccurrences \nField Separator \n1 \nHeader \nHDR \nRequired \nOccurs once for a file Fixed length \nseparation \n2 \nGroup \nSegment \nGRPCRD \nRequired \nOccurs \nmultiple \ntimes, \nas \nmany \nGroups \nin \nthe \nportfolio \n(only \nfor \nSHG \nGroups) \nSeparated (¬ or ~ or \nPipe ‘|’) \n3 \nMember/ \nConsumer \nSegment \nCNSCRD \nRequired \nOccurs multiple times, \nas many customers in \nthe Portfolio. Multiple \nMembers exist under \none Group \nSeparated (¬ or ~ or \nPipe ‘|’) \n4 \nAddress \nSegment \nADRCRD \nRequired \nOne or more for every \nConsumer \nSeparated (¬ or ~ or \nPipe \n‘|’) \n5 \nAccount \nSegment \nACTCRD \nRequired \nOne or more for every \nAccount \nSeparated (¬ or ~ or \nPipe ‘|’) \n6 \nTrailer \nTRL \nRequired \nOccurs once for a file Fixed length \nNote: ¬ is ASCII Character 170."}
{"text": "B. Header Segment (HDR) \nThe Header Record is the first segment of the data submission file. It is a required \nsegment, only one Header segment is reported for each file and it is reported at the start \nof the File. It contains information necessary to identify the Member Institution and the \nReporting date. It is a fixed length segment. \n# \nField Name \nOption \nType \nLength \nDescription \n1 \nSegment \nIdentifier \nRequired \nAN \n3 \nMust contain the value ‘HDR’ to \nidentify \nthe Header Segment. \n2 \nName of \nSubmission \nFile \nRequired \nAN \n5 \nContains the name of the \nsubmission \nfile, e.g. ‘HMMFI’ which indicates \nCRIF High Mark Microfinance Input \nFile. \n3 \nLayout Version \nNumber \nRequired \nAN \n3 \nIndicates \nInput \nfile \nformat \nversion number. Contains the value \n‘3.2’ \n4 \nSubmitting \nMEMBER ID \nRequired \nAN \n10 \nMust contain the unique member \nID \nassigned by the CIC to the \nMember Institution. \n5 \nSubmitting \nMEMBER Name \nRequired \nAN \n30 \nMust contain the name of \nMember \nInstitution submitting the file \n6 \nSubmitting \nBranch ID \nRequired \nWhen \npresent \nAN \n30 \nUnique Branch ID assigned by \nCRIF High Mark to the Institution’s \nBranch for a decentralized data \nsubmission. Could be left blank, 30 \nspaces to be added if \nBLANK. \n7 \nReported Date \nRequired \nD \n8 \nMust contain the date ‘AS OF \nWHICH’ the data is being reported \nto the CIC. If records in the file are \nupdated on different dates, use the \nmost recent date. \nValid \ncalendar \ndate \nin \nthe \nDDMMYYYY format"}
{"text": "# \nField Name \nOption \nType \nLength \nDescription \n8 \nFile Creation \nDate/ Extraction \nDate \nRequired \nD \n8 \nThe date when the file was created, \nwhich must be equal to or later than \ndate in the Date Reported Field. \nValid calendar date in DDMMYYYY \nformat. \nFor example, Date Reported is \nAugust 31, 2007. If the file was \nextracted on September 7, 2007 \nand submitted to CRIF High Mark \non September 8, 2007, then the \nfile \ncreation \ndate \nwill \nbe \nSeptember 7, 2007, i.e. 07092007. \n9 \nOrganization \nData Structure \nIndicator \nRequired \nAN \n3 \nContains the organization's \naccount or Customer structure. \nSHG for SHG data \nJLG for JLG + Individual Data \n10 \nPassword \nRequired \nAN \n30 \nMust \ncontain \nthe \nencrypted \npassword assigned by CICs to the \nMember Institution \n11 \nSystem \nVendor \nIdentifier \nRequired \nwhen \navailable \nAN \n30 \nA unique identifier agreed upon to \nidentify the vendor of Member \nInstitution, furnishing the data, in \ncase Vendor system is being used. \nFor in- house developed system, \nspecify ‘INHOUSE ‘. \nCould be left blank, 30 spaces to be \nadded if BLANK \n12 \nVendor \nSystem \nVersion \nIdentifier \nRequired \nwhen \navailable \nAN \n10 \nThe version of the system used to \nfurnish the data in case Vendor \nsystem is being used. For In-house \ndeveloped \nsystem, \nspecify \n‘INHOUSE’. \nCould be left blank, 10 spaces to be \nadded if BLANK \n13 \nReserved for \nFuture Use \nAN \n20 \nReserved for Future Use"}
{"text": "C. Group Segment (GRPCRD) \nThe Group Segment is the second segment in the data submission file. It contains the \ninformation necessary to identify the Group (only for SHG). It is present once per Group. \nEach Group can have many customers/members within it. This is a required segment if \nLoan Category is T04 or T05 or T06 or T07. \n \n# \nField Name \nType \nLen\ngth \nOption \nDescription \n1 Segment Identifier \nA/N \n6 \nRequired \nMust contain the value ‘GRPCRD’ \nto \nidentify the Member/Consumer Segment. \n2 Group Identifier \nA/N \n50 \nRequired \nUnique Group Identifier used by the \nMember Institution to identify the Group \nuniquely. \n3 Group Name \nA/N \n200 \nRequired \nName of the SHG Group \n4 Group Loan \nAccount Number \nA/N \n30 \nRequired \nLoan Account Number of the Group as \nin the Bank’s records \n5 Disbursed Amount \n(Rs) \nN \n9 \nRequired \nTotal Disbursed amount for this loan \n(in \nRupees) \n6 Outstanding \nBalance \n(Rs) \nN \n9 \nRequired \nTotal outstanding principal for this loan \n(in \nRupees) \n7 Date \nOpened/Disbursed \nD \n8 \nRequired \nValid calendar date in DDMMYYYY \nformat \n8 Date Closed (if \nclosed) \nD \n8 \nRequired \nwhen \npresent \nValid calendar date in DDMMYYYY \nformat \n9 Date of last \npayment \nD \n8 \nRequired \nwhen \npresent \nValid calendar date in DDMMYYYY \nformat \n10 Number of \nInstalments \nN \n3 \nRequired \nWhen \npresent \nOriginal number of instalments at the time \nof disbursement"}
{"text": "# \nField Name \nType \nLen\ngth \nOption \nDescription \n11 Repayment \nFrequency \nA/N \n3 \nRequired \nEnumeration: \nF01- Weekly  \nF02 - Biweekly  \nF03 - Monthly  \nF04- Bimonthly  \nF05- Quarterly \nF06- Semi-annually  \nF07-Annually \nF08-Single Payment Loan (bullet / balloon) \nF10-Other \n12 Instalment Amount \nN \n9 \nRequired \nInstalment Amount for the Loan (Rs.) \n13 Amount Overdue \n(Rupees) \nN \n9 \nRequired \nAmount which is due past the payment \nDate \n14 DPD (Days past \ndue) \nA/N \n3 \nRequired \nEnumeration: \n000 = 0 payments past due (current \naccount) with Positive Balance 001 \nto 999 = Number days past due. If an \naccount is above 999 days, mark as 999 \nXXX = No payment history available for \nthis month \n15 Loan Cycle ID \nN \n3 \nRequired \nWhen \npresent \nRenewal cycle number of the Group \n16 Loan Type (Term or \nCash Credit) \nA/N \n10 \nRequired \nC01-Term \nLoan C02-\nCash Credit \n17 Write Off Amount \n(Rupees) \nN \n9 \nRequired \nWhen \npresent \n18 Date Write-Off \n(if written-off) \nD \n8 \nRequired \nWhen \npresent \n19 Write-off reason (if \nwritten off) \nA/N \n20 \nRequired \nWhen \npresent \nEnumeration: \nX01- First Payment \nDefault  \nX02-Death"}
{"text": "# \nField Name \nType \nLen\ngth \nOption \nDescription \nX03-Wilful Default Status \nX04-Suit Filed, Willful Default \nStatus  \nX09-Untagged \nX10 - Not Applicable \n20 Groups’ \nCommunication \nAddress \nA/N \n200 Required \nwhen \npresent \nCommunication Address for the Group - \nas per address proof document \n(Number, \nVillage/Taluk, Landmark, District) \n21 State Code \n(Groups’ \nCommunication \nAddress) \nN \n2 \nRequired if \nAddress is \nprovided \nMust be a state code as defined \nunder Catalogues \n22 Pin Code (Groups’ \nCommunication \nAddress) \nN \n10 \nRequired if \nAddress is \nprovided \nValid 6 digit PIN Code \n23 Telephone Number \n1 type Indicator \nA/N \n3 \nRequired \nWhen \npresent \nTelephone / contact information details \nEnumeration: \nP01-Residence \nP02-Company \nP03- Mobile  \nP04-Permanent \nP07-Other \nP08-Untagged \n24 Group \nTelephone \nNumber 1 \nA/N \n15 \nRequired \nWhen \npresent \nGroup’s telephone number (contact) \n25 Group’s Bank \nAccount - Bank \nName \nA/N \n50 \nRequired \nName of the Bank where the group has \na savings bank account \n26 Group’s Bank \nAccount - \nBranch Name \nA/N \n50 \nRequired \nIFSC Code (preferred) or Name of the \nBank Branch where the group has a \nsavings bank account \n27 Group’s Bank \nAccount - \nAccount \nNumber \nA/N \n35 \nRequired \nAccount Number of group’s savings \nbank account"}
{"text": "# \nField Name \nType \nLen\ngth \nOption \nDescription \n28 Group’s Bank \nAccount - \nAccount \nBalance \nN \n10 \nRequired if \navailable \nAccount Balance (in Rupees) of group’s \nsavings bank account \n29 First Created Date \nD \n8 \nRequired if \navailable \nDate when the Group was formed \n30 First Linkage Date \nD \n8 \nRequired if \navailable \nDate when the Group was first linked for \ncredit \n31 Group Identifier \n(Govt) \nA/N \n30 \nRequired if \navailable \nIdentifier for the Group as captured with \nGovernment \n32 Linked to a Govt \nprogram \nA/N \n20 \nRequired if \navailable \nU01-NRLM \nU02-NULM \nU03-SRLM \nU04-MEPMA \nU99-Others \n33 SHPI/NGO Identifier \nA/N \n30 \nRequired if \navailable \nIdentifier for the NGO/SHPI as \ncaptured \nwith the Member Institution \n34 SHPI/NGO Name \nA/N \n100 Required if \navailable \nName of NGO/SHPI involved in Group \nFormation \n35 SHPI/NGO Officer \nName \nA/N \n100 Required if \navailable \nName of NGO/SHPI Personnel involved \nin \nGroup Formation/Linkage \n36 SHPI/NGO \nAddress (with \nState and Pin \ncode) \nA/N \n100 Required if \navailable \nAddress of NGO/SHPI involved in Group \nFormation \n(Street, \nVillage/Locality, \nTaluk, District, State, Pin Code)"}
{"text": "D. Member/Consumer Segment (CNSCRD) \nThe Member/Consumer Segment is the third segment in the data submission file. It \ncontains the information necessary to identify the Customer like name, date of birth, the \nidentification numbers like Voters ID, Aadhaar (UID), Driving License and so on. It is \npresent once per Customer. For group loans, Customer means Individual Member \nwithin the group. \nIt is a good practice that the key demographic details of the individual member (name, \naddress, father/spouse name, age, Date of Birth) are captured exactly from one of the \nstandard KYC Identifiers, preferably from UID/Aadhaar, Voter ID, Ration card or \nMNREGA Job Card. \n \n \n# \nField Name \nType Length \nOption \nDescription \n1 \nSegment Identifier \nA/N \n6 \nRequired \nMust \ncontain \nthe \nvalue \n‘CNSCRD’ \nto \nidentify \nthe \nMember/Consumer Segment. \n2 \nMember Identifier \nA/N \n35 \nRequired \nUnique customer identification \nnumber used by the Member \ninstitution \n3 \nBranch Identifier \nA/N \n30 \nRequired \nwhen \npresent \nUnique branch code of the \nMember Institution where the \ncustomer \nwas \noriginally \nenrolled. \nCould be left blank if not\navailable \n4 \nKendra/Centre Identifier \nA/N \n30 \nRequired \nwhen \npresent \nUnique centre \ncode of the \nMember Institution where the \ncustomer \nwas \noriginally \nenrolled \nCould be left blank if not\navailable \n5 \nGroup Identifier \nA/N \n50 \nRequired \nWhen \npresent \nUnique group Identifier used by \nthe Member Institution where \nthe Customer had originally \nenrolled. Or Group Name to be \nprovided here. If both are \npresent, then Group ID^Group \nName (separator as ^) \nThis is a required field if Loan \nCategory is T01 or T02 or T04 \nor T05 or T06 or T07 \n6 \nMember Name 1 \nA/N \n100 \nRequired \nName o f   the  Customer  (First\nName)"}
{"text": "# \nField Name \nType Length \nOption \nDescription \n7 \nMember Name 2 \nA/N \n50 \nRequired \nWhen \npresent \nName \nof \nthe \nCustomer \n(Middle Name) \n8 \nMember Name 3 \nA/N \n50 \nRequired \nWhen \npresent \nName of \nthe \nCustomer \n(Last Name) \n9 \nAlternate Name of Member \nA/N \n30 \nRequired \nWhen \npresent \nIf any ‘alias’ or maiden name \nof the Customer is captured. \n10 \nMember Birth Date \nD \n8 \nRequired \nDate of birth of Customer. Valid \nCalendar date in DDMMYYYY \nformat. Could be left blank if \nAge \n& Age as on is captured \n11 \nMember Age \nN \n3 \nRequired \nIf instead of DOB, age is \ncaptured then the age as \ncaptured \nat \nthe \ntime \nof \nmembership. Could be left \nblank if DOB is captured. \n12 \nMember's age as on date \nD \n8 \nRequired \nDate on which the age was \nrecorded - to identify the current \nage \nValid \nCalendar \ndate \nin\nDDMMYYYY \nformat. Could be left blank if \nDOB is captured \n13 \nMember Gender Type \nA/N \n1 \nRequired \nEnumerated: \nF - Female M – \nMale \nT - Third/Transgender \n14 \nMarital Status Type \nA/N \n3 \nRequired \nwhen \npresent \nEnumerated: \nM01 - Married  \nM02 - Separated \nM03- Divorced  \nM04 - Widowed  \nM05 - Unmarried  \nM06 - Untagged \nCould be left blank if not \navailable \n15 \nKey Person's name* \nA/N \n100 \nRequired \nwhen \npresent \nGuardian's name. Either Key \nPerson/Member \nRelationship/Nominee details \nneed to be filled \n16 \nKey Person's relationship \nA/N \n3 \nRequired \nwhen Key \nPerson’s \nName is \npopulated  \nEnumerated: \nK01 – Father \nK02 - \nHusband  \nK03- Mother \nK04 -Son \nK05 -\nDaughter"}
{"text": "# \nField Name \nType Length \nOption \nDescription \nK06-Wife \nK15 –Other \n17 \nMember relationship \nName 1* \nA/N \n100 \nRequired \nRelative name. Either Key \nPerson/Member \nRelationship/Nominee details \nneed to be filled. \n18 \nMember relationship Type 1 A/N \n3 \nRequired \nwhen \nMember \nRelations \nhip Name \n1 is \npopulated  \nEnumerated: \nK01 – Father \nK02 -Husband  \nK03- Mother  \nK04 -Son \nK05 -Daughter \nK06-Wife \nK15 -Other \n19 \nMember relationship Name \n2* \nA/N \n100 \nRequired \nwhen \npresent \n \n20 \nMember relationship Type 2 A/N \n3 \nRequired \nwhen \nMember \nRelations \nhip Name \n2 is \npopulated  \nEnumerated:  \nK01 – Father \nK02 - Husband  \nK03- Mother \nK04 -Son \nK05 -Daughter \nK06-Wife \nK15 –Other \n21 \nMember relationship Name \n3* \nA/N \n100 \nRequired \nwhen \npresent \n \n22 \nMember relationship Type 3 A/N \n3 \nRequired \nwhen \nMember \nRelations \nhip Name \n3 is \npopulated  \nEnumerated:  \nK01 - Father  \nK02 - Husband  \nK03- Mother \nK04 -Son \nK05 -Daughter \nK06-Wife \nK15 -Other \n23 \nMember relationship Name \n4* \nA/N \n100 \nRequired \nwhen \npresent \n \n24 \nMember relationship Type 4 A/N \n3 \nRequired \nwhen \nMember \nRelations \nhip Name \n4 is \npopulated \n \nEnumerated: \nK01 - Father  \nK02 - \nHusband  \nK03- Mother \nK04 -Son \nK05 -\nDaughter \nK06-Wife \nK15 -Other"}
{"text": "# \nField Name \nType Length \nOption \nDescription \n25 \nNominee Name* \nA/N \n100 \nRequired \nwhen \npresent \nNominee \nfor \ninsurance \npurposes if defined. Either Key \nPerson/Member \nRelationship/Nominee details \nneed to be filled \n26 \nNominee relationship \nA/N \n3 \nRequired \nwhen \nNominee \nName is \npopulated  \nEnumerated: \nK01 - Father  \nK02 - Husband  \nK03- Mother  \nK04 -Son \nK05 -\nDaughter \nK06-Wife \nK15 -Other \n27 \nNominee Age \nN \n3 \nRequired \nwhen \nNominee \nName is \npopulated \n \nIn years as of today \n28 \nVoter's ID* \nA/N \n20 \nRequired \nWhen \npresent \n \n29 \nUID* \nA/N \n40 \nRequired \nWhen \npresent \nAadhaar \n30 \nPAN* \nA/N \n15 \nRequired \nWhen \npresent \n \n31 \nRation Card* \nA/N \n20 \nRequired \nWhen \npresent \n \n32 \nMember Other ID 1 Type \ndescription \nA/N \n20 \nRequired \nWhen \npresent \nReserved for NREGA ID. If \nNREGA ID is captured, then \nput ‘NREGA’ in this field \n‘CKYC’ to be reported, if value\nof \nCKYC is available \n33 \nMember Other ID 1* \nA/N \n30 \nRequired \nWhen \npresent \nIf NREGA ID is captured, then \nIdentifier Number to be \ncaptured here \nCKYC value to be reported \n34 \nMember Other ID 2 Type \ndescription \nA/N \n20 \nRequired \nWhen \npresent \nIf any other id is captured, then \ninformation about such id \n35 \nMember Other ID 2* \nA/N \n30 \nRequired \nWhen \npresent \nIf any other id is captured, then \ninformation about such id"}
{"text": "# \nField Name \nType Length \nOption \nDescription \n36 \nOther ID 3 Type \nA/N \n20 \nRequired \nWhen \npresent \nIf any other id is captured, then \ninformation about such id \n37 \nOther ID 3 Value* \nA/N \n30 \nRequired \nWhen \npresent \nIf any other id is captured, then \ninformation about such id \n38 \nTelephone Number 1 type \nIndicator \nA/N \n3 \nRequired \nWhen \npresent \nTelephone / contact \ninformation details \nEnumeration:  \nP01-Residence \nP02-Company \nP03- Mobile  \nP04-Permanent \nP07-Other \nP08-Un tagged \n39 \nMember Telephone \nNumber 1 \nA/N \n15 \nRequired \n \n40 \nTelephone Number 2 type \nIndicator \nA/N \n3 \nRequired \nWhen \npresent \nEnumeration\n:  \nP01-\nResidence \nP02-Company \nP03- Mobile \nP04-\nPermanent \nP07-Other \nP08-Un \ntagged \n41 \nMember Telephone Number \n2 \nA/N \n15 \nRequired \nWhen \npresent \n \n42 \nMember’s Educational \nQualification \nA/N \n3 \nRequired \nEducational Qualification of the \nCustomer (Individual Member) \nEnumeration:  \nY01: Illiterate \nY02: Passed 5th class  \nY03: Passed 8th class. \nY04: Passed 10th class \nY05: Above 10th \n43 \nAsset ownership \nindicator/Poverty Index \nA/N \n3 \nRequired \nWhen \npresent \nIf the customer has any assets, \nthen mark Y \nEnumeration: \nY-Yes \nN- No \nIf Poverty Index is available, \nthen it is to be directly"}
{"text": "# \nField Name \nType Length \nOption \nDescription \nsupplied. \nProvide poverty index (if \ncalculated internally by the \nMember Institution) or related \ndetails such as BPL, etc \n44 \nNumber of Dependents \nN \n2 \nRequired \nWhen \npresent \nDependent family members \n45 \nBank Account - Bank Name A/N \n50 \nRequired \nName of the Bank where \nthe customer has a savings  \nbank \nAccount \n46 \nBank Account - Branch \nName \nA/N \n50 \nRequired \nIFSC Code (preferred) or Name \nof the Bank Branch where the \ncustomer  has  a  savings \nbank \nAccount \n47 \nBank Account - Account \nNumber \nA/N \n35 \nRequired \nAccount Number of \ncustomer’s savings bank \naccount \n48 \nOccupation \nA/N \n50 \nRequired \nWhen \npresent \nOccupation/Profession of the \nCustomer \nEnumeration: \n \nZ01- Home Maker \nZ02- Landless labourer  \nZ03- Marginal \nFarmer  \nZ04- Small farmer \nZ05- Non-farming  \nZ06- Others \n49 \nTotal Monthly Family \nIncome \nN \n9 \nRequired \nIn Rupees, no decimal \nErroneous/ Non- submission of \ndata in this field will lead to \nrejection of the record. \n50 \nMonthly Family Expenses \nN \n9 \nRequired \nIn Rupees, no decimal \n51 \nMember's Religion \nA/N \n3 \nRequired \nWhen \npresent \nCustomer’s \nReligion \nEnumeration: \nR01 - Hindu  \nR02 - Muslim  \nR03 - Christian  \nR04 - Sikh \nR05 - Buddhist  \nR06 - Jain \nR07 - Bahai"}
{"text": "# \nField Name \nType Length \nOption \nDescription \nR08 -Others \nR09 - Religion not stated \n52 \nMember's Caste or Social \nStrata \nA/N \n30 \nRequired \nCustomer’s Caste \nEnumeration:  \nV01 – SC \nV02 - ST  \nV03 - OBC \nV04 - NT/VJ (Vimukta Jati and \nNomadic Tribes) \nV05 - General  \nV08 - Others \nV09 – Untagged \n53 \nMember’s Role \nA/N \n3 \nRequired \nWhen \npresent \nIndicator for the role of \nCustomer within the group \nEnumeration: \nL01- Leader/President/Office- \nbearer \nL02-Associate/ Secretary  \nL03-Member \nL04- Untagged \n54 \nCentre Leader indicator \nA/N \n1 \nRequired \nwhen \npresent \nIs the customer a centre leader \nEnumeration:  \nY- Yes \n N- No \nU- Untagged \n55 \nMember’s Status \nA/N \n3 \nRequired \nwhen \npresent \nIndicator for the engagement \nstatus of the Member within the \nGroup \nEnumeration: \nW01- Active (Loanee Member) \nW02-Inactive/Dormant\n \n(Non- loanee member) \nW03-Exited  \nW04-Untagged \n* One of Relationship details (Key Person’s Name, Member Relationship Name, Nominee \nName) or KYC IDs (Voter’s ID, UID/Aadhaar, Ration Card, PAN, Other IDs) is required. For the \nMicrofinance customers, UID/Aadhaar, Voter’s ID, Ration Card Number and NREGA ID are \nmost widely used identifiers."}
{"text": "E. Address Segment (ADRCRD) \nThe Address Segment is the fourth segment in the data submission file. It contains the \naddresses of the customer - permanent address and present address for a customer \nalong with state code and PIN code. One address segment is mandatory per Member \nsegment. \n \n# \nField Name \nType \nLength \nOption \nDescription \n56 Segment Identifier \nA/N \n6 \nRequired \nMust contain the value ‘ADRCRD’ \nto identify the Address Segment. \n57 Member's \nPermanent Address \nA/N \n200 \nRequired \nwhen \npresent \nPermanent address of the \nCustomer- as per address \nproof \nDocument \n58 State Code (Permanent \nAddress) \nN \n2 \nRequired \nif \nPermane\nnt \nAddress \nis \nprovided \nMust be a state code as defined \nunder Catalogues \n59 Pin Code (Permanent \nAddress) \nN \n10 \nRequired \nif \nPermane\nnt \nAddress \nis \nprovided \nValid 6-digit PIN Code \n60 Member's \nCurrent Address \nA/N \n200 \nRequired \nPresent or Communication \naddress of the Customer - if not \nresiding in permanent address. \nIf \nonly \n1 \naddress \nis \navailable, \nprovide \nthe \nsame as current address \n61 State Code (Current \nAddress) \nN \n2 \nRequired \nMust be a state code as defined \nunder Catalogues \n62 Pin Code (Current \nAddress) \nN \n10 \nRequired \nValid 6-digit PIN Code \n63 E-mail ID \nA/N \n30 \nRequired \nWhen \npresent \nNote: It is advisable to capture the address exactly from one of the KYC Identifiers"}
{"text": "F. Account Segment (ACTCRD) \nThe Account Segment is the fifth segment within the data submission file. It contains \nthe financial information related to account such as account number, type of credit \nproduct, original and current terms and repayment information. More than one Account \nsegment can be present for one Customer segment. \n# \nField Name \nType \nLength \nOption \nDescription \n64 \nSegment Identifier \nA/N \n6 \nRequired \nMust contain the value \"ACTCRD\" to \nidentify the Account Segment. \n65 \nUnique Account \nReference number \nA/N \n35 \nRequired \nThis field will not change even if the \nAccount number changes, it can\nhave customer ID. \nThis field must be consistent on each \nsubmission basis to avoid duplication\nof information. \nIn case of a branch split or branch \njoin where the account number \nchanges within the tenor of the loan,\nthe original loan account number \nshould be shown \nhere. \n66 \nAccount Number \nA/N \n35 \nRequired \nAccount number of the loan account. \nWill be same as previous field if no\nsplit or branch combination has \nhappened \nduring the tenor of the loan. \n67 \nBranch Identifier \nA/N \n30 \nRequired \nwhen \npresent \nUnique branch code where the loan \naccount is held currently. \nCould be left blank if not available \n68 \nKendra/Centre \nIdentifier \nA/N \n30 \nRequired \nwhen \npresent \nUnique center code where the loan \naccount is held currently \nCould be left blank if not available \n69 \nLoan Officer \noriginating the \nloan \nA/N \n30 \nRequired \nwhen \npresent \nEmployee Code of Officer originating\nthe loan \nCould be left blank if not available \n70 \nDate of Account \nInformation \nD \n8 \nRequired \nDate on which Account was last\nupdated. \nValid calendar date in DDMMYYYY \nformat"}
{"text": "# \nField Name \nType \nLength \nOption \nDescription \n71 \nLoan Category5 \nA/N \n3 \nRequired \nEnumeration:  \nT01- JLG Group \nT02- JLG Individual  \nT03 – Individual \nT04 - SHG Group  \nT05 - SHG Individual \nT06 - SHG Group - Govt  \nT07 - SHG Intra-Group \nT08 – Others \n72 \nGroup Identifier \nA/N \n50 \nRequired \nWhen \npresent \nRequired field if Loan Category is \nT01 or T02 or T04 or T05 or T06 or \nT07 \nThis is the unique group code \nassigned by the Member Institution. \nGroup Name to be provided here. If \nboth are present, then provide it as \n“Group ID^Group \nName” \n73 \nLoan Cycle-id \nA/N \n30 \nRequired \nWhen \npresent \nRenewal cycle number of the \ncustomer with the Member \nInstitution \n74 \nLoan Purpose \nA/N \n20 \nRequired \nPurpose of the loan \n75 \nAccount Status \nA/N \n3 \nRequired \nEnumeration: \nS01 - Loan Submitted \nS02 - Loan Approved - Not yet \ndisbursed S03 - Loan Declined \nS04 - Current  \nS05 - Delinquent S06 - Written Off \nS07 - Account Closed \nS08- Restructured due to COVID-19 \nS09-Restructured & Closed \nS10-Settled \nS11-Post Write Off Settled S12-Post \nWrite Off Closed \nS15 – Cancelled \n76 \nApplication date \nD \n8 \nRequired \nWhen \npresent \nValid calendar date in DDMMYYYY \nformat \n \n5 JLG-Individual: JLG loan where lending is being tracked at individual level; JLG-Group: JLG loan where lending \nis being tracked at group level; Individual: Individual Microfinance loan (not JLG or SHG) – this loan should either \nbe reported in this format or in the consumer data format but not in both formats; SHG Individual: where the \namount of lending is being tracked at individual level; SHG – Group: where the lent amount is being tracked at \nGroup level only; SHG Group Govt: same as SHG Group but linked to a Government program; SHG-Group-\nIntra: same as Group covering intra group lending"}
{"text": "# \nField Name \nType \nLength \nOption \nDescription \n77 \nSanctioned Date \nD \n8 \nRequired \nWhen \npresent \nValid calendar date in DDMMYYYY \nformat \n78 \nDate \nOpened/Disburse \nD \nD \n8 \nRequired \nValid calendar date in DDMMYYYY \nformat \n79 \nDate Closed (if \nclosed) \nD \n8 \nRequired \nWhen \npresent \nRequired if account status is S07. \nValid calendar date in DDMMYYYY \nformat \n80 \nDate of last \npayment \nD \n8 \nRequired \nWhen \npresent \nValid calendar date in DDMMYYYY \nformat \n81 \nApplied For \namount \nN \n9 \nRequired \nWhen \npresent \nAmount applied for in the \napplication \n82 \nLoan amount \nSanctioned \nN \n9 \nRequired \nCould be replicated with value under \nTotal Amount Disbursed (Rupees) \n83 \nTotal Amount \nDisbursed \n(Rupees) \nN \n9 \nRequired \nAmount disbursed \n84 \nNumber of \nInstalments \nN \n3 \nRequired \nOriginal Number of instalments at \nthe time of disbursement \nErroneous/ Non- submission of data \nin this field will lead to rejection of \nthe record. \n85 \nRepayment \nFrequency \nA/N \n3 \nRequired \nEnumeration: \nF01- Weekly  \nF02 - Biweekly F03 - Monthly F04- \nBimonthly F05- Quarterly \nF06- Semi-annually F07-Annually \nF08-Single Payment Loan (bullet / \nballoon) \nF10-Other \nErroneous/ Non- submission of data \nin this field will lead to rejection of \nthe record. \n86 \nMinimum Amount \nDue/Instalment \nAmount \nN \n9 \nRequired \nInstalment Amount for the Loan \nErroneous/ Non- submission of data \nin this field will lead to rejection of \nthe record. \n87 \nCurrent \nBalance \nN \n9 \nRequired \nOnly principal outstanding on the \nloan"}
{"text": "# \nField Name \nType \nLength \nOption \nDescription \n(Rupees) \n88 \nAmount Overdue \n(Rupees) \nN \n9 \nRequired \nAmount which is due past the \npayment \nDate \n89 \nDPD (Days past \ndue) \nA/N \n3 \nRequired \nEnumeration: \n000 = 0 payments past due (current \naccount) with Positive Balance \n001 to 999 = Number days past due. \nIf an account is above 999 days, \nmark as 999 XXX = No payment \nhistory available for \nthis month \n90 \nWrite Off Amount \n(Rupees) \nN \n9 \nRequired \nWhen \npresent \nRequired if account status is S06 \n91 \nDate Write-Off (if \nwritten-off) \nD \n8 \nRequired \nWhen \npresent \nRequired if account status is S06. \nValid calendar date in DDMMYYYY \nformat \n92 \nWrite-off reason \n(if written off) \nA/N \n20 \nRequired \nWhen \npresent \nEnumeration: required if account \nstatus is S06 \nX01- First Payment Default X02-\nDeath \nX03-Wilful Default Status \nX04-Suit Filed, Wilful Default Status \nX09-Untagged \nX10 - Not Applicable \n93 \nNo. of meetings \nheld \nN \n3 \nRequired \nWhen \npresent \nNumber of center meetings held \nsince the loan disbursement \n94 \nNo. of meetings \nmissed \nN \n3 \nRequired \nWhen \npresent \nNumber of center meetings out of \nthe above which the customer has \nnot attended \n95 \nInsurance \nIndicator \nA/N \n1 \nRequired \nWhen \npresent \nEnumeration:  \nY- Yes \nN- No \n96 \nType of Insurance \nA/N \n3 \nRequired \nWhen \npresent \nEnumeration: \nL01 - Life Insurance  \nL02 - Credit Insurance \nL03 - Health/Medical Insurance  \nL04 - Property Insurance \nL05 - Liability Insurance \nL10 – Other \n97 \nSum \nAssured/Coverage \nN \n10 \nRequired \nWhen \npresent \nSum Assured for the Insurance"}
{"text": "# \nField Name \nType \nLength \nOption \nDescription \n98 \nAgreed meeting \nday of the week \nA/N \n3 \nRequired \nWhen \npresent \nEnumeration:  \nMON - Monday  \nTUE - Tuesday  \nWED - Wednesday  \nTHU - Thursday  \nFRI - Friday \nSAT - Saturday SUN - Sunday \n99 \nAgreed Meeting \ntime of the day \nA/N \n5 \nRequired \nWhen \npresent \nShould be in HH:MM format \n100 \nDummy \nA/N \n30 \nRequired \nWhen \npresent \nReserved for future use"}
{"text": "G. Trailer Segment (TRL) \nThe Trailer Record is the last segment of the credit reporting file. This segment is a \nrequired segment, appears only once per file and indicates end of the file. It is a fixed \nlength segment. \n \n \n# \nField Name \nOption \nType \nLength \nDescription \n1 Segment Identifier \nRequired \nAN \n3 \nMust contain the value ‘TRL’ to \nidentify the Trailer Segment. \n2 Layout Version \nNumber \nRequired \nAN \n3 \nIndicates Input file format \nversion number. Contains the \nvalue ‘3.0’ \n3 Submitting \nMember ID \nRequired \nAN \n10 \nMust contain the unique Member \nID assigned by CRIF High Mark \nto the Member Institution. \n4 Reserved for \nFuture Use \nAN \n20 \nReserved for Future Use"}
{"text": "Glossary \n \nTerm \nDescription \nD \nDate \nN \nNumeric data \nA/N \nAlphanumeric \n \nCatalogues \nA: State \n \nCode \nDescription \nCode \nDescription \nAN \nAndaman and Nicobar Islands \nLD \nLakshadweep \nAP \nAndhra Pradesh \nMH \nMadhya Pradesh \nAR \nArunachal Pradesh \nML \nMaharashtra \nAS \nAssam \nMN \nManipur \nBR \nBihar \nMP \nMeghalaya \nCG \nChandigarh \nMZ \nMizoram \nCH \nChhattisgarh \nNL \nNagaland \nDD \nDadra and Nagar Haveli \nOR \nOrissa \nDL \nDelhi \nPB \nPunjab \nDN \nDaman and Diu \nPY \nPuducherry \nGA \nGoa \nRJ \nRajasthan \nGJ \nGujarat \nSK \nSikkim \nHP \nHaryana \nTN \nTamil Nadu \nHR \nHimachal Pradesh \nTR \nTripura \nJH \nJammu and Kashmir \nTS \nTelangana State \nJK \nJharkhand \nUK (Formerly \nUA) \nUttarakhand \nKA \nKarnataka \nUP \nUttar Pradesh \nKL \nKerala \nWB \nWest Bengal"}
{"text": "Sample Structure \nHeader Segment \nSegment \nIdentifier \nHDR \nName of \nSubmission File \nHMMFI \nLayout \nVersion Number \n3.2 \nSubmitting \nMEMBER ID \nXXXXXXXXXX \nSubmitting MEMBER \nName \nXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX \nSubmitting \nBranch ID \nXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX \nReported \nDate \n31032016 \nFile Creation Date/ Extraction \nDate \n12042016 \nOrganization Member \nStructure Indicator \nXXX \nPassword \nXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX \nSystem Vendor \nIdentifier \nXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX \nVendor System Version \nIdentifier \nXXXXXXXXX \nReserved for \nFuture Use \nXXXXXXXXXXXXXXXXXXXX \n \nTrailer Segment \n \nSegment Identifier \nTRL \nLayout Version Number \n3.0 \nSubmitting Member ID \nXXXXXXXXXX \nReserved for Future Use \nXXXXXXXXXXXXXXXXXXXX"}
{"text": "Data Segment \n \nSegment Identifier \nA/N \nCNSCRD \nMember Identifier \nA/N \n12345678 \nBranch Identifier \nA/N \n9003 \nKendra/Centre Identifier \nA/N \n039003 \nGroup Identifier \nA/N \n039001^INDIRA SHG \nMember Name 1 \nA/N \nANITA JAYANT NATH \nMember Name 2 \nA/N \nMember Name 3 \nA/N \nAlternate Name of Member \nA/N \nMember Birth Date \n(DDMMYYYY) \n01011975 \nMember Age \nN \n39 \nMember's age as on date \n(DDMMYYYY) \n31012015 \nMember Gender Type \nA/N \nF \nMarital Status Type \nA/N \nM01 \nKey Person's name \nA/N \nJAYANT NATH \nKey Person's relationship \nA/N \nK02 \nMember relationship Name 1 \nA/N \nMember relationship Type 1 \nA/N \nMember relationship Name 2 \nA/N \nMember relationship Type 2 \nA/N \nMember relationship Name 3 \nA/N \nMember relationship Type 3 \nA/N \nMember relationship Name 4 \nA/N \nMember relationship Type 4 \nA/N \nNominee Name \nA/N \nJAYANT NATH \nNominee relationship \nA/N \nK02 \nNominee Age \nN \nVoter's ID \nA/N \nUID \nA/N \nPAN \nA/N \nRation Card \nA/N \nMember Other ID 1 Type description A/N \nVOTER ID \nMember Other ID 1 \nA/N \nValue1 \nMember Other ID 2 Type description A/N \nMember Other ID 2 \nA/N \nOther ID 3 Type \nA/N"}
{"text": "Other ID 3 Value \nA/N \nTelephone Number 1 type Indicator A/N \nP03 \nMember Telephone Number 1 \nA/N \n8754698XXX \nTelephone Number 2 type Indicator A/N \nMember Telephone Number 2 \nA/N \nMember’s Educational Qualification A/N \nAsset ownership indicator/ Poverty \nIndex \nA/N \nNumber of Dependents \nN \n2 \nBank Account - Bank Name \nA/N \nBank Account - Branch Name \nA/N \nBank Account - Account Number \nA/N \nOccupation \nA/N \nTotal Monthly Family Income \nN \nMonthly Family Expenses \nN \nMember's Religion \nA/N \nR08 \nMember's Caste \nA/N \nMember’s Role \nA/N \nL01 \nCentre Leader indicator \nA/N \nY \nMember’s Status \nA/N \nW01 \nSegment Identifier \nA/N \nADRCRD \nMember's Permanent Address \nA/N \nLAING PART, LAING, \nRAJGANGPUR, SUNDARGARH \nState Code (Permanent Address) \nN \nOR \nPin Code (Permanent Address) \nN \n770017 \nMember's Current Address \nA/N \nLAING PART, LAING, \nRAJGANGPUR, SUNDARGARH \nState Code (Current Address) \nN \nOR \nPin Code (Current Address) \nN \n770017 \nAddress \nA/N \nSegment Identifier \nA/N \nACTCRD \nUnique Account Reference number A/N \n039000012 \nAccount Number \nA/N \n123456 \nBranch Identifier \nA/N \n9003 \nKendra/Centre Identifier \nA/N \n039003 \nLoan Officer for Originating the loan A/N \nABC XYZ \nDate of Account Information \nD (DDMMYYYY) \n03102015 \nLoan Category \nA/N \nT04 \nGroup Identifier \nA/N \n039001^INDIRA SHG \nLoan Cycle-id \nA/N \n1"}
{"text": "Loan Purpose \nA/N \nSEA \nAccount Status \nA/N \nS04 \nApplication date \n(DDMMYYYY) \n04022014 \nSanctioned Date \n(DDMMYYYY) \n28022014 \nDate Opened/Disbursed \n(DDMMYYYY) \n28022014 \nDate Closed (if closed) \n(DDMMYYYY) \nDate of last payment \n(DDMMYYYY) \n08032016 \nApplied For amount \nN \n15000 \nLoan amount Sanctioned \nN \n15000 \nTotal Amount Disbursed (Rupees) \nN \n15000 \nNumber of Instalments \nN \n24 \nRepayment Frequency \nA/N \nF03 \nMinimum Amt Due/Instalment \nAmount \nN \n808 \nCurrent Balance (Rupees) \nN \n4599 \nAmount Overdue (Rupees) \nN \n0 \nDPD (Days past due) \nA/N \n0 \nWrite Off Amount (Rupees) \nN \nDate Write-Off (if written-off) \n(DDMMYYYY) \nWrite-off reason (if written off) \nA/N \nNo. of meetings held \nN \n45 \nNo. of meetings missed \nN \n22 \nInsurance Indicator \nA/N \nType of Insurance \nA/N \nSum Assured/Coverage \nN \nAgreed meeting day of the week \nA/N \nAgreed Meeting time of the day \nA/N \nDummy \nA/N"}
{"text": "Annex II \n \nFormat for reporting information on Commercial Papers to Credit Information \nCompanies \n \n‘CP’ proposed Fields \nAvailable Field in Commercial \nData Submission format \nUpdate in the description \ncolumn of the format, in \ncase of commercial paper \nName of CP issuer \nBS Segment - Field No. 4. Field \nName: Borrower's Name \n‘Name of the CP Issuer’ \nCP Amount \nCR Segment - Field No. 5. Field \nName: \nSanctioned \nAmount/ \nNotional Amount of Contract \n‘Amount of CP’ to be given \nIssue Date \nCR Segment - Field No. 4. Field \nName: Facility / Loan Activation / \nSanction Date \n‘Issue Date’ to be given \nMaturity Date \nCR Segment - Field No. 13. Field \nName: Loan Expiry / Maturity Date \n‘Maturity Date’ to be given \nName of CRA \nBS Segment- Field No. 24. Field \nName: \nAssessment \nAgency / \nAuthority \n‘Name of CRA’ to be reported \nRating Agency \nBS Segment - Field No. 23. Field \nName: Credit Rating \n‘Rating \nAssigned’ \nto\n \nbe \nReported \nAmount of Default \nCR Segment - Field No. 17. Field \nName: Amount Overdue / Limit \nOverdue \n‘Amount of Default’ to be \ngiven"}
{"text": "Annex III  \nIndicative Data Formats for collection of individual SHG members6 \nTable 1: Information to be collected from individual SHG members where the total \namount of loan to be attributed to or to be availed by the SHG member exceeds ₹30, 0007 \n \nParticulars required \nParticulars provided \nBasis \nI. Non-Credit information \n \n \n1. Name of the SHG \n \nTo be provided by the SHG member \n2. Savings Bank Account Number of \nthe SHG \n \nTo \nbe \nprovided \nby \nthe \nSHG member \n \n3. Loan Account Number of the SHG \n \nTo be assigned by the bank \n4. Name of the SHG member \n \nAs it appears on the identity \ndocument accepted by the CI or \nin the records of the CI \n5. The identity document accepted \nby the bank \n \nAadhaar \nCard \nNo. \n/Voter \nID/PAN/Driving \nlicence/NREGA \nCard /Passport8 \n6. Unique number of the identity \ndocument accepted by the bank, \nif available \n \nDocumentary proof needed \n7. Father’s /Husband’s Name \n \nAs \nmentioned \nin \nthe \nidentity \ndocument accepted by the CI \n8. Male or Female \n \nAs declared by the SHG \nMember \n9.    Date of birth (if printed on the \nidentity document) \n \nDD/MM/YYYY \n10. Address (Complete address with \nState Code and PIN Code) \n \nDeclaration basis9 \n11. Information about other existing \nbank accounts \n \nDeclaration basis \n \n6 The forms set out in this are meant to indicate the information requirements and could be digitized in any format, \nsubject to all the particulars and details indicated herein being collected. \n7 To be collected at the time of sanctioning a loan to new SHGs or at the time of renewal of existing loans or granting \nadditional loans to the existing SHGs. With the approval of their boards, the banks with Gross NPA ratio exceeding \n10% in the SHG loan segment may fix a lower threshold for collecting the information/data indicated in this Table and \nthe next one. This amount will not include any subsidy or margin out of the member’s own savings that goes towards \nfunding the activity or the purpose for which the loan is taken (both either back end or front end). \n8 The banks may specifically see if any of the SHG members would fall within the purview of Reserve Bank of India \n(Commercial Banks – Know Your Customer) Directions, 2025 (as amended from time to time) relating to introduction \nof simplified measures for proof of identity by RBI and offer Small Deposit Accounts/Basic Saving Bank Deposit \nAccount to them. Wherever a SHG member is willing to open such an account, the KYC should be done as per RBI \ncircular and reported to the Central KYC Registry and the CICs. No document to be collected if the KYC has already \nbeen done at the time of opening of the Savings bank Account of the SHG member, or otherwise. \n9 The CI to pull out information from Central KYC registry."}
{"text": "12. Educational level \nCodes to be used \nIlliterate:                  1 \nPassed 5th class:  2  \nPassed 8th class:  3  \nPassed 10th class: 4  \nAbove 10th  class:  5 \nDeclaration basis \n13. Occupation \nCodes to be used \nHome maker:          1  \nLandless labourer:  2 \nMarginal Farmer:    3  \nSmall Farmer:      4 \nDeclaration basis \n14. Monthly Family income (in Rs.) \n \nDeclaration basis \n15. Social strata \nCodes to be used \nSC: \n1 \nST: \n2 \nOBC: \n3 \nGeneral :               5 \nDeclaration basis \n16. Mobile Number (if available) \n \nDeclaration basis \nII. \nCredit related information10 \n17. Information about existing loans \n– through other SHGs where \nthe individual is a member \n \nBased on the CIC report obtained by \nthe CI or a CI report (in the absence \nof a CIC report) \n17.1 Status of the SHG Account \n□ \nName of the SHG \n□ \nSHG’s loan Account Number \n□ \nName of the lending bank \n□ \nAmount borrowed \n□ \nAmount outstanding \n□ \nStatus of the account \n□ \nRegular \n□ \nDefaulter \n□ \nSettled  \n□ \nSub-judice \n \nBased on the CIC report obtained by \nthe CI, if available \n17.2 If in default, status of the SHG \nmember’s loan account if the \nSHG loan was distributed to \nhim/her11 \n• \nName of the SHG \n• \nName of the lending bank \n• \nAmount borrowed \n• \nAmount outstanding \n \nBased on CIC report, if \navailable; in other cases a \nletter from the SHG to be \nrelied upon \n18. The amount of loan proposed to \nbe taken out of the group loan \n \nLetter from \nthe \nPresident/Secretary of the SHG. To \n \n10 Not applicable, if the group loan is up to ₹1,00,000/-. \n11 Until the data base of individual SHG members is available with the CICs, this information may be collected and \nrelied upon based on a letter provided by the SHG concerned. 17.2 will not be applicable if the SHG account is \nregular."}
{"text": "granted by the CI to the SHG12 \nbe verified by the CI later on. \n19. The loans taken by the member in \nindividual capacity from other \nsources \n \nThis information may be collected \nbased on CIC reports, if available. \nIf \nnot \navailable \nwith \nCICs, \nindividual CI’s reports may be \nsought once the member declares  \nhis    previous \nborrowings. \n \n \n \n \n12 All SHGs must decide upfront how they propose to utilize the SHG loan. The actual distribution of the loan to \nindividual members wherever it was agreed to be above Rs. 30,000 or where the actual amount disbursed exceeded \nRs.30000 though not agreed at the time of taking loan from the CI, must be reported to the CI by the SHG office \nbearers. Non-adherence to this condition may be taken into account while extending further loan to the SHG or \nrenewing its cash credit limit next time. The CIs need to incorporate suitable clauses in the loan agreements relating \nto penal provisions for providing wrong information regarding the amount of loans taken out of the group loans. \nDepending upon their experience, CIs may also insist on maintenance of verifiable record of the amounts distributed \nout of CI loans in cases where the average amount of loan availed by the SHG per member exceeds Rs.20,000/."}
{"text": "Table 2: Information to be collected from individual SHG members where the total \namount of loan to be attributed to or to be availed by the SHG member is upto \n₹30,00013 \nParticulars required \nParticulars \nprovided \nBasis \nI. Non-Credit information \n1. Name of the SHG \nTo be provided by the SHG\nmember \n2. Savings \nBank \nAccount \nNumber of the SHG \nTo be provided by the SHG\nmember \n3. Loan Account Number of \nthe SHG \nTo be assigned by the CI \n4. Name of the SHG member \nAs it appears on the identity \ndocument accepted by the \nbank or record of the CI \n5. The \nidentity \ndocument \naccepted by the CI \nAadhaar Card No. / Voter \nID/PAN/Driving \nlicence \n/ \nNREGA No. /Passport14 \n6. Unique number of the identity \ndocument accepted by the \nCI, if available \nDocumentary proof needed \n7. Father’s /Husband’s Name \nAs mentioned in the identity \ndocument accepted by the CI \n8. Male or Female \nAs \ndeclared \nby the SHG\nmember \n9. Date of birth (if printed on \nthe identity document) \nDD/MM/YYYY \n10. Address (Complete address \nwith State Code and PIN \nCode) \nDeclaration basis15 \n11. Information \nabout \nother \nexisting bank accounts \nDeclaration basis \n12. Educational level \nCodes to be used \nIlliterate: 1 \nPassed 5th Class: 2 \nPassed 8th Class: 3 \nPassed 10th class: 4 \nAbove    10\nth: 5 \n \n \n \n \n \n3\n4\n5\nDeclaration basis \n \n13 To be collected at the time of sanctioning a loan to new SHGs or at the time of renewal of existing loans or granting \nadditional loans to the existing SHGs. With the approval of their boards, the banks with Gross NPA ratio exceeding 10% \nin the SHG loan segment may fix a lower threshold for collecting the information/data indicated in this Table. This amount \nwill not include any subsidy or margin out of the member’s own savings that goes towards funding the activity or the \npurpose for which the loan is taken (both either back end or front end). \n \n14 The banks may specifically see if any of the SHG members would fall within the purview of Reserve Bank of India \n(Commercial Banks – Know Your Customer) Directions, 2025 (as amended from time to time) relating to introduction of \nsimplified measures for proof of identity by RBI and offer Small Deposit Accounts/Basic Saving Bank Deposit Account \nto them. Wherever a SHG member is willing to open such an account, the KYC should be done as per RBI circular and \nreported to the Central KYC Registry and the CICs. No document to be collected if the KYC has already been done at \nthe time of opening of the Savings bank Account of the SHG member, or otherwise. \n \n15The CI to pull out information from Central KYC."}
{"text": "13. Occupation \nCodes to be used \nHome maker:         1 \nLandless Labourer: 2 \nMarginal farmer:     3 \nSmall Farmer:        4 \n  \nDeclaration basis \n \n14. Monthly Family income  \n(in ₹) \nDeclaration basis \n15. Social strata \nCodes to be used \nSC:         1 \nST:          2 \nOBC:       3 \nGeneral:  5 \nDeclaration basis) \n16. Mobile Number (if available) \nDeclaration basis \nII.  Credit information16 related \n17. Information about existing \nloans – through other SHGs \nwhere the individual is a \nmember \nBased on the CIC report \nobtained by the CI or a CI \nreport (in the absence of a CIC \nreport) \n17.1 \nStatus of the SHG Account \n□ \nName of the SHG \n□ \nSHG’s loan Account \nNumber \n□ \nName of the lending bank \n□ \nAmount borrowed \n□ \nAmount outstanding \n□ \nStatus of the account \n□ \nRegular \n□ \nDefaulter \n□ \nSettled \n□ \nSub-judice \nBased on the CIC report \nobtained by the CI, if available \n18. The amount of loan \nproposed to be taken out of the \ngroup loan granted by the CI to \nthe SHG \nBased \non \nCIC \nreport, \nif \navailable \n19. The loans taken by the \nmember in individual capacity \nfrom other sources \nThe amount of loan to be \nverified by the CI from the \nSHG records. \n \n \n16 Not applicable, if the group loan is up to ₹1,00,000/-."}
{"text": "Table 317: Information on individual SHG members to be reported by CIs to CICs \nas part of the Uniform Credit Reporting Format (MFI) \n \nParticulars to be reported \nCorresponding Field in the MFI Reporting \nFormat \nI. \nNon-credit related information \n1.  Name (as it appears on the identity \ndocument) \nMember Segment -Field No. 6,7,8 for Name of \nthe Customer \n2. The \nnature \nof \nthe \nidentity \ndocument accepted by the bank \nMember Segment – Field No. 32, 34,36 for Other \nID Type Description \n3. Unique number of the identity \ndocument accepted by the bank, if \navailable \nMember Segment - Field No. 33, 35, 37 for Other \nID Value; \nMember Segment – Field No. 28 to 31 should be \nused for fields such as UID (Aadhaar), Voter’s ID, \nRation Card Number \n4.  Date \nof \n(DD/MM/YYYY) \nbirth Member Segment - Field No. 10 for Member Birth \nDate \n5.  Father’s /Husband’s Name \nMember Segment - Field No. 17,18,19,20 for \nMember Relationship Details \n6. Address (Complete address with \nState Code and PIN Code) \nAddress Segment – Field No. 60, 61, 62 for \nAddress, State Code and PIN Code \n7.  Male or Female \nMember Segment - Field No. 13 for Member \nGender Type \n8. Name of the SHG of which the \nperson is a member \nMember Segment - Field No. 5 for Group \nIdentifier The field has been modified to capture \n‘Group Unique ID^Group Name’ \n9. Savings Account Number of the \nSHG \nMember Segment - Field No. 45,46, 47 for \nMember’s Savings Bank Details (Bank Name, \nBranch Code, Account) \n10. Loan Account Number of the SHG Account Segment - Field No. 66 for Account \nNumber \n11. Reference number of any other \nidentity document that has been \nrelied upon by the bank \nMember Segment - Field No. 28-31 and 35, 37 \nfor Other ID Value \n12. Educational level \nmember \nof the SHG Member Segment - Field No. 42 on Member’s \nEducational Qualification \n13. Monthly Family income (in Rs.) \nMember Segment - Field No. 49 for Total Monthly \nFamily Income \n14. Occupation \nMember Segment - Field No. 48 for Occupation \n15. Social strata \nMember Segment - Field No. 52 for Member’s \nCaste \n16. Mobile No. \nMember Segment - Field No. 39, 41 for Member’s \nPhone Number \nII. Credit related information18 \n17. Amount of loan availed by the \nmember from the SHG loan \nAccount Segment - Field No. 83 for Total Amount \nDisbursed \n \n17 RBI has set up a Technical Working Group comprising representatives from various CIs and CICs to \ninstitutionalise a continuing mechanism for reviewing and making changes where necessary to the data \nformats. This Group shall suitably adapt Table 3 for the purpose of reporting of data by CIs to the CICs \nelectronically. \n \n18 Not applicable, if the group loan is up to ₹1,00,000/-."}
{"text": "Table 4: Information on individual SHG members to be collected at the time \nof opening of new SHG Savings Bank Accounts of the SHG \n \nParticulars required \nParticulars \nprovided \nBasis \n1. Name of the SHG \nTo be filled in by the SHG \nmember \n2. Savings Bank Account \nNumber of the SHG \nTo be assigned by \nthe bank \n3. Name of the SHG member \nAs it appears on the identity \ndocument accepted by the CI \n4. The identity document accepted \nby the bank \nAadhaar Card No. /Voter \nID/PAN/Driving licence/NREGA \nCard /Passport19 \n5. Unique number of the identity \ndocument accepted by the bank, if \navailable \nDocumentary proof Needed \n6. Father’s /Husband’s Name \nAs mentioned in the identity \ndocument accepted by the bank \n7. Male or Female \nAs declared by the SHG member \n8. Date of birth (if printed on \nthe identity \ndocument) \nDD/MM/YYYY \n9. Address (Complete address \nwith State Code and PIN Code) \nDeclaration basis20 \n10. Information about other \nexisting bank accounts \nDeclaration basis \n11. Educational level \nCodes to be used  \nIlliterate:             1  \nPassed 5th class:  2 \nPassed 8th class:  3 \nPassed 10thclass  : 4 \nAbove 10th :             5 \nDeclaration basis \n12. Occupation \nCodes to be used \nHome maker         :  1 \nLandless Labourer: 2 \nMarginal Farmer  :  3  \nSmall Farmer \n:  4 \nDeclaration basis \n13. Monthly Family income (in Rs.) \nDeclaration basis \n14. Social strata \nCodes to be used  \nSC:             1 \nST: \n2 \nOBC: \n3 \nGeneral :     5 \nDeclaration basis \n15. Mobile Number (if available) \nDeclaration basis \n \n19  A bank may specifically see if any of the SHG members would fall within the purview of Reserve Bank of India \n(Commercial Banks – Know Your Customer) Directions, 2025 (as amended from time to time) relating to introduction of \nsimplified measures for proof of identity by RBI and offer Small Deposit Accounts/Basic Saving Bank Deposit Account to \nthem. Wherever a SHG member is willing to open such an account, the KYC should be done as per RBI circular and \nreported to the Central KYC Registry and the CICs. \n \n20   The bank will pull out information from Central KYC registry."}
{"text": "Annex IV  \n \nInformation on secured assets possessed under the SARFAESI Act, 2002 \n \n \nSl. \nNo \nBranch  \nName \nState \nBorrower  \nName \nGuarantor \nName \n(wherever \nApplicable) \nRegistere\nd  \naddress  \nof the \nBorrower \nRegistered \naddress  \n of the \nGuarantor \n(wherever \napplicable) \nOutstanding \namount  \n(in ₹) \nAsset \nClassification \nDate of \nAsset \nclassification  \nDetails of \nsecurity  \npossessed \nName of \nthe Title \nholder of \nthe security  \npossessed"}
{"text": "Annex V \nModifications in the Uniform Credit Reporting Format \n \n1. The nomenclature of the field ‘Fax Number’ shall be changed to ‘Email ID’ in \nthe Commercial Bureau reporting format. \n2. The nomenclature of the field ‘dummy’ shall be changed to ‘Email ID’ under the \nMFI Bureau reporting format. \n3. The above fields shall continue to be categorised as ‘when available’."}
{"text": "Annex-VI \n \nIllustration on the timelines for reporting credit information  \n \nCredit \nInformation to be \nreported as on \ndate \nCIs to share \ndata with \nCICs by \nCICs to ingest and \nshare rectification \nreport with CIs by \nCIs to share \nrectification in \nrejected data with \nCICs by \nDay of \nthe \nmonth \n9th \n13th  \n16th  \n20th  \n16th \n20th  \n23rd  \n27th \n23rd  \n27th  \n30th \n5th of the next month \nLast day of month \n5th of the \nnext month \n8th of next month \n13th of the next \nmonth"}