Filetype Excel XLSX | Posted on 10 Aug 2022 | 4 years ago
Authentication
digital resources
136x Filetype XLSX File size 0.09 MB Source: www.nedfi.com
Sheet 1: Scoring Criteria
| RFP No.: NEDFi/RFP/IT/01/2022-23 Date: 21/06/2022 REQUEST FOR PROPOSAL (RFP) RFP for Selection of LLMS & General Accounting Solution Provider in SaaS Model | ||||
| Fully Compliant (F) | Customization W/O Cost (C ) | Non- Compliant (N) | ||
| Scores | 5 | 3 | 0 | |
| Note: Bidders must mark their response as F/C/N against each of the technical & functional specifications. If any point not marked, considered as Non-Compliant | ||||
| RFP No.: NEDFi/RFP/IT/01/2022-23 Date: 21/06/2022 REQUEST FOR PROPOSAL (RFP) RFP for Selection of LLMS & General Accounting Solution Provider in SaaS Model | |||
| Minimum Functional Specifications for LLMS | |||
| Sl no. | Functional Requirement | Bidder's Response (F/C/N) |
Bidder's Comments |
| General Features/Requirement | |||
| 1 | System should have realtime integretation with Accounting/CFSS/ Document Management System, CRM/ Budget Forecasting /Other Interfaces etc for functionalities including but not limited to Loan Disbursement, Loan Receipt, Loan Adjustement, Interest Accural, NPA provisioning, Fee & Charges, Writeoff etc. | ||
| 2 | System should have provision for capturing Land Mortgage deeds/Land Details/Other Collateral /Security details etc. | ||
| 3 | The proposed LLMS application should have facility to accept the loan application with required documents through Mobile App & Web Portal | ||
| 4 | The proposed application should be capable to allocate the loan application to the respective Departments / Branches/BC/DSA | ||
| 5 | Customer should be able to view/download the loan application/Balane Outstanding/ Loan Account Statement/ Ineterst Certificate etc status through Mobile App & Web Portal. Also at any point of time, customer should be able to check the loan outstanding balance, Current Dues as well the make payment through Mobile App & Web Portal. | ||
| 6 | Customer should be able to lodge the complaint / raise a query | ||
| 7 | The proposed LLMS application system should have facility to communicate with SMS gateway and send required SMS . The SMS templates should as per NEDFi's requirement | ||
| 8 | The proposed LLMS application system should be capable to integrate with NEDFi's partner Banks (four Banks). | ||
| 9 | The proposed LLMS application system should have facility to accept bulk upload and download facility of files (SFTP / any other automated mechanism) received from Sponsored Banks / Govt subsidies and the financial transaction should be posted to the respective account without any manual intervention. | ||
| 10 | The proposed Solution should have capability to interfacing with API banking facility of NEDFi's Partner Bank | ||
| 11 | The system should have facility to store the relevant documents (KYC / Credit Bureau / MCA / GST / ITR the actual documents will be decided at the time of BRD with the final selected vendor) with specific areas for a particular loan account holder of NEDFi. The NEDFi Users should be able to view the relevant documents as per requirement on screen. | ||
| 12 | The System should read Optical Character Recognition (OCR)/Quick Response Code (QR Codes) in the documents and auto-fill the relevant fields in the system (e.g. Aadhaar, PAN, DL, Voter ID etc.) | ||
| 13 | The proposed solution system should have Single sign-On facility and the same shall be available for use of other applications of NEDFi (present & future such as General Accounting, DMS, CRM, VPN, Collection, Mobile Apps etc). | ||
| 14 | The proposed LLMS application solution should be capable with IVR system for Contact Center from day one. | ||
| 15 | The proposed LLMS application system should be parameterized and capable enough to define, manage and support any loan product and workflow (present/future) during the project tenure introduced by NEDFi | ||
| 16 | System should have ability to add certain actions/ condition if the application is not fully up to the mark for approval like addition of co-borrower, collateral, etc. Ability to re-route the case to appropriate officers in case of amendments Ability to re-route the case of any data change based on which decision was taken Ability to reject the application with reasons Ability to re-open the rejected applications |
||
| 17 | The Proposed solution should have provision for generation of Online Documents: 1) Credit Memo/Customer Appraisal Memo(CAM)/Detailed Appraisal Note(DAN) 2) Executive Summary. 3) Facility Offer Letter/Letter of Sanction/Letter of Intent etc. 4) Generation of Decline/Rejection Letter 5) Control Sheet 6) Pre disbursement Compliance Sheet/ certificate 7) Any other document as needed by NEDFi |
||
| 18 | System should have provision related to Fee & charge such as but not limited to: • define different charges, fees and taxes to be collected for various credit product type and customer type • facility for commission/ fee management/ payments for BC,RO, DSAs, Valuers, BF, lawyers and other third parties • waive or defer charge |
||
| 19 | The system should be capable of Integartion with third party BI tools for carrying out various reports with analytical data. | ||
| 20 | System should capture details and print standard loan documents in the prescribed format as desired by the NEDFi such as: • Demand Promissory note • All types of loan agreement as desired by NEDFi • Detail Appraisal Note (DAN) as desired by NEDFi • Disbursement request letter as desired by NEDFi • Sanction letter along with customer acknowledgement as desired by NEDFi • CA certificate as desired by NEDFi • Site visit report as desired by NEDFi • Disbursement Note as desired by NEDFi • Disbursement advice as desired by NEDFi • Screening Note as desired by NEDFi • Data entry format for minutes of meeting as desired by NEDFi • Security acceptance letter as desired by NEDFi • Letter of repayment as desired by NEDFi • Letter of guarantee as desired by NEDFi • Hypothecation agreement as desired by NEDFi • Memorandum of title deeds as desired by NEDFi • Any other standard documents as desired by NEDFi • Pledged Supply Bills as desired by NEDFi • Letter of continuity as desired by NEDFi • Letter of Interest variation as desired by NEDFi • Power of Attorney as desired by NEDFi • Letter of renewal as desired by NEDFi • Letter of revival as desired by NEDFi • Consortium Advance Letter as desired by NEDFi • Credit Memo • Facility Offer Letter • Executive Summary • Decline Letter • Control Sheet • Pre disbursement compliance Sheet/ Certificate • Loan Account Review document as desired by NEDFi |
||
| 20 | The system should have the ability to generate/print blank application form(s), filled up application(s) form with unique reference numbers and mandate form(s) to be completed based on defined business rules. | ||
| 21 | The system should have provision for configurable rule De-dupe feature at various level such as Customer, Product, Asset, Collateral, individual borrower, Business units, Coporate applicant etc. and as defined by NEDFi. | ||
| 22 | System should be able to define and modify the segment as per the MSME classification advised by Reserve Bank of India time to time | ||
| 23 | System should have capability to display turnaround time for approval for each approved application. TAT for each process should be defined during set up of Process flow. | ||
| 24 | System should have provision to route applications forward or backward (as per flow) depending on its conditions. In case the application is sent back to requestor, system should recalculate TAT | ||
| 25 | System should have provision for graphical representation of account details including history transactions of customer. | ||
| 26 | System should be capable to integrate with external agencies for data for validation and authenticity check with appropriate security controls. | ||
| 27 | System should capture all data required by the NEDFi for the particular type of loan. The system should also have the capability to allow the user to define additional fields than those available with ease for additional data capturing | ||
| 28 | System should have provision for capturing site/field visit with photos, Documents, Data, Geo Locations etc. | ||
| 29 | System should have provision of configurable Document Checklist (Product Wise) | ||
| 30 | Recovery of principal at one frequency and recovery of interest in a different frequency (e.g. recovery of principal in every six months but recovery of interest on a monthly basis) | ||
| 31 | System should segregate the loan installment received on the basis of interest, principal, penalties, charges etc. | ||
| 32 | Define and view help with updated version of the software against each item | ||
| 33 | System should provide for search facilities across the screens with various filters in various modules during various stages of processing and should not be any impact on performance. | ||
| User Management | |||
| 1 | The system shall support definition of Users, Groups and Roles relation in the system |
||
| 2 | The system shall support access permissions on granular level | ||
| 3 | The system shall support multiple levels of access rights (Delete/ Edit/ View/ Print/ Copy or Download) |
||
| 4 | The system shall support secure login id and passwords along with multi factor authentication for each user and passwords shall be stored in encrypted format in database | ||
| 5 | The system should have profivsion of changing and resetting password by user and admin. | ||
| 6 | The system should have provision for configurable password policy | ||
| 7 | The system should have provision for creating use for channel partners (BC/DSA/RO etc.) | ||
| 8 | The system should have configurable RBAC feature. | ||
| 9 | The system should have provision for disabling, reenabling and archieving users | ||
| Master Data Management and Configuration | |||
| 1 | As part of Origination Platform, master management module will be required for the business user where user can create master data from front end which will be used at the time of transaction. | ||
| 2 | Platform to support setup of any master required from a third party component | ||
| 3 | User should be able to create, modify and delete/deactivate master data from front end | ||
| 4 | Masters to be synchronized with external and internal systems at a defined frequency | ||
| 5 | Ability to define various masters e.g. Calendar Master, Business Partners, Deviation reason master, Delegation level master (Value), Product master (including pricing etc.), Customer master (With ID details etc.), Policy criteria master, Profession master, Company master, Customer service master, Collateral detail master, Interest Rate Master, Other Masters as relevant for the software/as required by NEDFi. | ||
| Integration Capability | |||
| 1 | System should support Integration with Govt. initiated portals such as PSBloansin59minutes.com, National Common Portal for Credit Linked Government Schemes, NeSL etc. | ||
| 2 | System should have the ability to integrate with various third party applications like, CRM, CFSS for acepting deposit, Risk Rating Models, Chatbots, Scoring Models, Digilocker, Credit Bureaus, UIDAI, Income Tax, D&B, MCA website/data, CRILIC, Market Reports, CERSAI, GST site, Insurance portal, Defaulter list, cKYC, eKYC, OCR etc. The application should be able to handle API based request from various application | ||
| 3 | Integration for Bank Statement Analysis, Penny Drop verification, Bank Reconcillation etc. | ||
| 4 | Platform should have ability to integrate with India stack, API Setu etc. | ||
| 5 | Shall support integration with various External Systems through straight through processing (STP) | ||
| 6 | System would be modular in nature and should support other products as plug-ins | ||
| 7 | System should support integraton with API banking & Cash management system/service facility of partner banks | ||
| 8 | For e-Mandate integration, System should be able to integrate directly with respective banks or with a third party solution vendors. | ||
| 9 | System should be able to integrate with Bureau and Fintech services to perform Go No-Go decisions | ||
| 10 | Sysem should have provision to integrate eSign API & eStamping API | ||
| 11 | Pre-screening Check from Internal & External database (Dedupe,Blacklist, AML Check Negative list,World Check etc.) | ||
| Product Configuration/Management | |||
| 1 | System should have provision of multi-level hierarchy for defining financials loan product. | ||
| 2 | Ability to Support for multiple interest rate type such as fixed, Float, index based and mixed | ||
| 3 | Ability to define repayment variations like EMI, non EMI, balloon, moratorium, step up/down, Others as pecified by NEDFi | ||
| 4 | System should be able to define, edit and view products like tenor which can be in days, weeks, months or years with maximum, minimum and interval restrictions, fees & commissions which can be of different types e.g. Processing Fee, Commitment fees, commissions etc. | ||
| 5 | Ability to support Interest and principal moratorium | ||
| 6 | The platform should support loan products such as term loan, composite loan, working capital loan, working capital revolving limit,subsidy loan products / schemes etc. as per NEDFi policy. | ||
| 7 | System should be able to process and provide support for all loan products like Project finance, Micro small enterprises, micro finance, industrial loans, Working Capital Revolving Limit Loan,Corporate Loans, CC, working capital loan, business loan, Loan for NEDFi Employee(Car Loan, House Loan, Personal Loan, Consumer Loan etc.) and or any other new products implemented by NEDFi within the project tenure. | ||
| 8 | System should define products / schemes where margin amounts need to be collected from the customer before disbursal of the loan amount | ||
| 9 | System should have provision to specify Start date & End date for various loan products. | ||
| 10 | System should define rebate rates for particular types of loan products / schemes for early settlement. | ||
| 11 | System should globally maintain the minimum / maximum margin amounts for each type of loan product / scheme and automatically calculate and apply the same. | ||
| 12 | System should automatically calculate and display the applicable subsidy amount as per the loan product / scheme selected | ||
| 13 | System should have the ability to allocate automatically to each user based on role and also to a pool/ team so that the available users can select case to work on if needed. | ||
| 14 | System should have facility to put applications on hold till pending actions are completed. | ||
| 15 | Define and manage different origination channel | ||
| 16 | Configurable to support product features • Regular Product Parameters • Special campaign or category parameters • Exceptions (approved through a defined process) |
||
| 17 | Ability to calculate Turn Around Time (TAT) | ||
| 18 | Ability to define and handle front – end and back end subsidies | ||
| 19 | Ability to define and handle subventions | ||
| 20 | For loans given under subsidy system should provide information on those loans where subsidy amount is outstanding from government | ||
| 21 | System should provision to calculate Penal interest on default principal or booth (Default princial+interest) as per parameterized by NEDFi. | ||
| 22 | System should be able to define, edit and view products like tenor which can be in days, weeks, months or years with maximum, minimum and interval restrictions, fees & commissions which can be of different types e.g. Processing Fee, Commitment fees, L/c, commissions etc | ||
| 23 | The fair value calculation of all the loans should be captured product wise | ||
| 24 | The EIR calculation of all the loans should be captured product wise | ||
| 25 | The actual value of the collaterals should be captured product wise | ||
| 26 | System should be able to support derecognition and modification of the loans and gains and losses arising thereof product wise | ||
| 27 | Financial model of Project/Corporate Investment is required | ||
| 28 | System should automatically pick up and apply charges / commission to the particular account under this product / scheme as per configuration | ||
| 29 | System should automatically adjust the loan amount outstanding against the subsidy amount with the NEDFi. | ||
| 30 | System should able to update comprehensive stock statement, book debts, tangible and intangible securities for calculating initial working capital limit, drawing power, loan limits etc. | ||
| Workflow Management | |||
| 1 | System should be highly workflow (BPM Standard)driven with configurable and parameterized workflow design capabilities to meet the current and future business and functional requirements of NEDFi. | ||
| 2 | Platform should have the inbuilt functionality to design processes using easy drag and drop GUI functionality of the process modeler and manage all processes in a single view | ||
| 3 | Platform should support STP process for customer on boarding based on integration call received from other systems like CRM, chatbot, IB, MB, external partners etc. | ||
| 4 | Platform to have the provision to resume the customer journey from the last drop-off point | ||
| 5 | Platform to have the capability to continue a DIY initiated journey (customer) in assisted mode and vice versa | ||
| 6 | Platform should support Advanced Deviation & Exception Approval Matrix · Define deviations based on rules for pricing, demographics and other parameters | ||
| 7 | Platform to support Maker checker process for all process including deviation, deferral and exception approval | ||
| 8 | Extensive workflow, parametrization and configurable rules • Allocate application to specific approvers • Skill based allocation of work items • Queuing system to allocate based on preset logic • Define role, profile, level, branch, location based rules for users • Define workflows for credit lines based on current process of NEDFi • Dynamic interaction between rules engine and queuing system • Define rules using customer level elemental data • Define customer eligibility rules based on different parameters |
||
| 9 | The system should allocate particular application to specific approvers. Further, there should be a queuing system that should allocate based on pre-set logic. Approval process can be defined as single approver/multiple approvers | ||
| 10 | System should be able to create/edit/assign underwriting limits profile to each credit underwriting workflow | ||
| 11 | System should provide facility to define complete workflow process steps of credit proposal. | ||
| 12 | Process of approval may have defined sequential and parallel (like committee based approval etc.) movements. It should be possible to have both in workflow simultaneously. | ||
| 13 | The system should facilitate to track the automated underwriting workflow for monitoring of TAT of each step and each processing Official | ||
| 14 | System should provide Fast track processing feature whereby a single user (duly designated) to process an application from start to finish or may have limited access to a specific task. | ||
| 15 | System should support sanctioning workflow based upon defined business rules as desired by the NEDFi | ||
| 16 | Escalation matrix to be configured as part of the workflow based on business rules e.g. automatic escalation of case from Branch to NEDFi HO if action is not taken within pre-defined time or it should be possible to automatically forward case to separate queues for ‘non-starters’, ‘broken promises’ etc. i.e. the system should identify such cases & queue them separately for each cycle, city and team. |
||
| 17 | System should provide - ability to define role, profile, level, branch, location based allocation rules for each user along with holidays. - ability to reallocate or reassign cases from one user to another. |
||
| 18 | System should provide multiple to & fro movement of workflow items possible. Comprehensive Reports for workflow. | ||
| 19 | System should provide ‘queuing feature’ which should include the ability for escalation to higher supervising authority in case the application has remained pending without any activity for a specified period. | ||
| 20 | Should define Service Level and TAT rules for each activity in the workflow | ||
| 21 | System should have the capability whereby the user can view all previous notes exchanged and remarks made by other users with respect to the application under consideration and also seek clarification on the same. | ||
| 22 | Ability to have multi-level sanctioning matrix | ||
| 23 | Ability to allow authorized personnel to override credit approval or rejection recommendation | ||
| 24 | Ability to route the case for committee approval in case of higher loan amounts" | ||
| 25 | Ability to define credit deviation matrix for a hierarchy of reviewers and approvers, credit committee, or a hierarchy of credit committees as decided by NEDFi | ||
| 26 | System should provide facility for application deviation due to incomplete documents for selected documents - to allow application to continue to be processed. But Deviation Memo must be created attached to it. This application will proceed to the supervisor for the next step. | ||
| 27 | System should be able to process loans without physical file movements and the total work flow along with time must be captured. | ||
| 28 | Application can be returned to any earlier stage in the workflow if required. | ||
| Customer Prospecting / Lead Management | |||
| 1 | Manual Lead Creation through front | ||
| 2 | Bulk Lead Creation through Excel sheet upload | ||
| 3 | Lead Creation through integration with website, Mobile apps, Business Correspondents (BC), Business Facilitator(BF), Direct Selling Agent (DSA), online lead providers such as psbloansin59minutes.com, BankBazar etc. | ||
| 4 | Automatic/ Manual lead assignment to users/branches based on pre-defined logic like PIN code, type of lead etc. | ||
| 5 | Manual Lead Assignment/Re-assignment | ||
| 6 | Lead De-duplication | ||
| 7 | Capture Detailed information of the lead | ||
| 8 | Add and modify lead details | ||
| 9 | Attach, scan documents | ||
| 10 | Initiate leads for multiple products through single application | ||
| 11 | Unique Lead ID generation and communication to customers. System should enable searching based on the Unique Lead ID or other defined parameters with full/ partial matching. Full/partial matching option should be configurable | ||
| 12 | General Features • Unique Lead ID generation • Lead Tracking • Monitor Lead status, define SLAs, TATs, Escallation Matrix • Automatic reminders for follow-up • Automatic internal and external notifications based on different events • 360 degree view of the lead details • Upfront/Processing fees / charges reminder |
||
| 13 | System should have the ability to capture details of the source of the application with details like Relationship manager/ Front line manager, BC, DSA, BF, Credit Managers, branch, sourcing location etc. | ||
| 14 | System should have provision for capturing Audit Trail of Leads | ||
| Customer on Boarding/Customer General Information | |||
| 1 | System should have provsion for digital customer onboarding facility (DIY/Assisted/Own Official) | ||
| 2 | System should have provision for performning KYC documentation process (DIY/Assisted/Own official) | ||
| 3 | System should have provision for capturing of multiple Co-applicant / Individual & corporate Guarantors / Obligors / Other Stakeholders Information | ||
| 4 | System should have provision for capturing Customer General Information & other Detail as specified by NEDFi during BRD preparation | ||
| 5 | System should support following attributes/fields and as desired by NEDFi during BRD preparation: a) Customer Constitution b) Customer Name & Address c) PAN, Aadhar etc, d) Directors/Partners etc. e) Contact Person DEtails f) GST, Incorporation Date g) Bank Details etc. |
||
| 6 | System should be capable to capture/fetch financial data of the customer both current and projections through user input/bulk upload/3rd party API integration, as needed. Equity / capital details, Credit facility sanctioned/availed by/ from other Banks/ institutions, profit and loss statements, balance sheet statements, Income Tax return, GST return, projected cash flows for carrying out loan apprisal and comparison between estimated and actual achieved at the time of review etc. | ||
| 7 | System should have provision to capture and display Guarantee Cover against the loan such as (CGFMU for Mudra loan, CGTMSE, NCGTC for all types of MSME loans, ECLGS etc. | ||
| 8 | System should be able to capture and validate various data for KYC norms as per Statuatory, regulatory, semi-reglatory guidelines from time to time like Customer Type, Customer Profile, Customer Address etc. | ||
| 9 | System should be able to Create/ Update / View customer Information at defined stages of application processing | ||
| Customer Portal | |||
| 1 | Login/Sign up through Mobile OTP | ||
| 2 | My Profile/Account | ||
| 3 | Apply for Loan (Customer journey should be based on workflow defined in LLMS for Product/Customer Type/Ticket Size etc.) | ||
| 4 | Display of linked loan applications with its status and facility to upload additional document if any | ||
| 5 | Display of exisiting loan accounts with balance outstanding with account statement (drill down) | ||
| 6 | Display current Due against Loan accounts and payment option through UPI/Payment gateway | ||
| 7 | Display of Previous payment and receipt history | ||
| 8 | Provision for updation of mobile number/email | ||
| 9 | EMI calculator for loan product | ||
| 10 | Downloading of loan balance confirmation | ||
| 11 | Provision for upload covenent such as Balancesheet, Insurance etc. | ||
| 12 | Provision of request for Loan Disbursement | ||
| 13 | Download option for Statement of Interest Calcultion and Account Statement | ||
| 14 | Notification section | ||
| 15 | Download Payement Receipt | ||
| 16 | E-mandate configuration | ||
| 17 | Customer Dashboard | ||
| 18 | Customer should be able to lodge the complaint / raise a query | ||
| 19 | Capturing Disbursement/ Repayment Drawdown schedule | ||
| Loan Application Processing | |||
| 1 | Single Loan Application to process Single/multiple Facilities for single / multiple borrowers (Funded & Non-Funded). | ||
| 2 | System should have provision to indetify and autofill useful information such as PAN, DOB, Name, Addhaar, DL No etc. through OCR/ICR features | ||
| 3 | Platform to re direct the lead to the appropriate user/level if the applicant drops out during the DIY journey | ||
| 4 | Platform to support capture of customer detail and perform dedupe/negative checks | ||
| 5 | System should support CREDIT Bereau check through API Integration | ||
| 6 | Platform to support capture of bank statements, Integration with ITR, GST, MCA etc APIs for getting various data | ||
| 7 | Checks (Credit / preliminary Checks) based on defined eligibility parameter | ||
| 8 | Platform to support calculation of total sanctioned amount, insurance premium (if applicable), Processing fee, ST, Stamp Duty and other relevant fees etc. | ||
| 9 | Platform to support e-mandate integration | ||
| 10 | Platform to support integration with the payment aggregators and payment gateways for making payment by the applicants | ||
| 11 | System should provide ‘queuing feature’ which should include the ability for escalation to higher supervising authority in case the application has remained pending without any activity for a specified period | ||
| 12 | System should support consortium, Multiple bank and syndication facilities as desired by NEDFi | ||
| 13 | System should have provision to capture/fetch various data through user input/bulk upload/API integration related to loan application but not limited to the followings: 1)Customer profile, constitution, address,demographic details etc. 2)Customer KYC details, 3)Customer detailed History/Business & Industry 4)Group(connection) Structure definition, fetching group exposure, 5)Employment Details, 6)Loan details, 7)Guarantor/ Co-applicant details 8)Management Profile 9)Employee Detail 10)Customer exposure with other Banks, 11)Land Holding Details, 12)Developmental Impact 13)Company Future Plan & Justification of Facility 14)Relationship Plan 15)SWOT analysis 16)Asset & liability details 17)Date of appraisal initiation 18)Registering the application details in a user defined format 19)Borrower Master data 20)Customer Follow Up reports 21)Write Up Details 22)Financials /CMA DATA 23)Facility Details 24)Pricing Details 25)Security Details 26)Standard Terms &Conditions 27)Credit Rating/scoring results 28)Ratios and calculation from rating input/output sheets 29)Document checklist |
||
| 14 | Provision to add/change new Co applicant/ Guarantor before/after Final sanction of application | ||
| 15 | System should automatically distribute tasks to processors/credit officer by: Considering load of the processing Officer/credit officer, Production line, Customer Type, Group of the processing Officer, Authority of the processing Officer/approver/Branch Head | ||
| 16 | Each user in the workflow has To-do/To-track queues. User will receive Loan Application from their To-do queue. Others will be able to view Loan Application and its status from there To-track queue | ||
| 17 | Moratorium period and start of Repayment date should be interlinked to enable user to input only one value | ||
| 18 | The system should have a provision for processing of loan applications based on the percentage allocation region wise as advised by the NEDFi. | ||
| Credit Appraisal | |||
| 1 | Risk Information | ||
| 2 | Decision and Remarks | ||
| 3 | System should have the ability to define the customer eligibility rules based on different parameters. Ability to arrive at eligible loan amount for a customer based on these rules and data entered for application. System should support financial analysis based on parameters like : - Turnover - Liquidity - Profitability - Leverage - Debt Service Coverage ratios/Interest coverage ratio. - Balance sheet and Profit and Loss analysis - Cash flow and fund-flow analysis - Ratio Analysis as per ratio formula given by NEDFi etc. - Ability to customize so to compute ratios like NPV, IRR, sensitivity, or other similar tools. |
||
| 4 | System should allow defining ratios like operating profit margin, etc. based on formulae and data obtained in financial statements. System should support details like Average and benchmark ratios | ||
| 5 | System should capture any Number of years for which the financial projections/ cash flow/ loan /covenants data can be recorded & processed | ||
| 6 | Based on the data uploaded by the borrower, system should compute the financial ratios as per the configuration in the masters. The system should be able to perform comparison of selected key ratios, financial parameters across borrowers within the industry and against bench marks. Ratios like debt/equity ratio, current ratio, ICR/DSCR etc. and additionally (but not limited to) following: ‒ Paid up capital ‒ Reserves and Surplus ‒ Unsecured Loan ‒ Intangible assets ‒ Revaluation reserve ‒ Tangible net worth ‒ Long-term liabilities ‒ Capital employed ‒ Net block ‒ Investments ‒ Non-current assets ‒ Net working capital ‒ Current assets ‒ Current liabilities ‒ Net sales ‒ Other income ‒ Net profit after tax ‒ Depreciation ‒ Intangible assets ‒ Cash accruals ‒ ROCE (Return on capital employed) - Drawing Power of the applicant |
||
| 7 | System should have provision for carrying out credit rating of the customer as per NEDFi policy | ||
| 8 | System should have provision to capture/update External credit rating from time to time | ||
| 9 | System should provide a clear and concise summary screen of all details on the facility requested as applicable for an underwriting review. | ||
| 10 | System should able to only capture various financial/not financial data but not limited to the following for credit apprisal: a) Peer Group Analysis b) Internal Audit Comments c) External Auditor Remarks d) Stock Market Performance e) Single Obligor Limit Prudential (Borrower & Group) f) Credit Policy Check g) Internal Risk Rating Engine (Borrower) h) External Risk Rating (Through Integration) i) Risk Identification & Mitigation j) Associate Concern Analysis |
||
| 11 | System should support assessment of loan proposal based on various industry standard method such as Nayak Committee, Tondon Committee, Bill Discounting , Turn over method, Cash budget method, MPBF etc. | ||
| Sanctioning/Processing & Sanctions | |||
| 1 | System should have provision for handling Loan revalidation process with subsequent changes in related modules. | ||
| 2 | System should support intermediate queries from recommending and sanctioning authorities. Such queries should not be editable in future | ||
| 3 | The system should be able to take care of the provisions relating to the Credit Policies of NEDFi. A suitable pop up messages be displayed (in case of any deviation from the NEDFi’s policies and guidelines). | ||
| 4 | Credit committee/Loan approving authority should be able to take decisions on proposals while sitting in different locations and contents of this meeting should be captured in the system like in case committee members are working from different locations and having committee meeting through video conferencing the system should have provision to record the proceedings of meeting. | ||
| 5 | All the documents related to proposal should be available in the system along with proposal form for -reference. | ||
| 6 | Scorecard should be generated if defined. Parameters, which are used for evaluating Credit Scoring should be defined in the configuration module by the system administrator. | ||
| 7 | If approver chooses one application to be approved, system should allow approver to query all information of the application (such as Loan detail, collateral data, applicant details). | ||
| 8 | The system should have the facility to check for the customer / Guarantor's existing account information like Previous facilities information (Sanctioned amount ,outstanding balance etc. | ||
| 9 | System should have calculator to automatically compute for borrower's paying capacity, loan value vs. appraised value, monthly amortization/ repayment schedules, loan to collateral ratios, debt service ratio, income multiplier, aggregate exposure of borrower and other ratios/ values as required by the NEDFi | ||
| 10 | System should provide facility to differentiate different modes of routing operation e.g. amending a Loan Application, Returning an incomplete/ unsatisfactory Loan Application, Appealing against a Declined Loan Application, Aborting an on-going Loan Application, Transforming an Approved Loan Application into an Effective Loan Application etc. | ||
| 11 | System should lock Loan application once it is approved. | ||
| 12 | System should have provision to generate, modify, update screening note and link to account. | ||
| 13 | System should have provision to access, generate the Detail Appraisal Note (DAN) and accord on line approval by the delegated authority. Approval authority matrix, deviation matrix and requisite approving authority to be defined in the master, drop down to be available for the credit officer to select from. | ||
| 14 | System should have provision to capture Minutes of Meeting and this should be linked to account. | ||
| 15 | The system should have provision of conveying sanction/rejection of the loan from the HO to the respective BC/RO/Branch. | ||
| 16 | There should be provision for immediate sanction of selected loan products( As defined by NEDFi) based on pre-determined data | ||
| 17 | Provision of Sanction Expiry Date as per NEDFi’s Norms | ||
| 18 | The system should support processing of loans on priority as per criteria defined by the NEDFi | ||
| 19 | The system should support approving of loan entries individually or batch wise | ||
| 20 | System shouldf have facility to capture NEDFi Committee details such as Meeting Date, Committee Name, Resolution Number, Details etc. | ||
| Primary & Collateral Security Management | |||
| 1 | The system should provide for a facility to add collaterals in the offering stage in case NEDFi requires the customer to do so due to a lower finance to value ratio. | ||
| 2 | System should able to link the same primary/collateral security to the top-up loan account in case of any top-up loan given to existing loan account. | ||
| 3 | Should generate unique collateral ID for the asset/collateral. In case of extension, if any, existing collateral ID number to be captured for subsequent applications. | ||
| 4 | System should define different collaterals and attributes in the systems which have to be captured for a collateral | ||
| 5 | System should capture collaterals for an application. | ||
| 6 | Workflow based valuation process - Initiate valuation request, Valuation report details, Accept valuation and Attach collateral. Multiple instances of a single valuation request can be generated. |
||
| 7 | System should calculate eligibility based on collateral value and Net Present Value (NPV) | ||
| 8 | System have facility to upload, display and print valuation documents/legal reports into the system. | ||
| 9 | System should have Ability to configure single/ multiple collateral at application level | ||
| 10 | Collateral processes like entry, valuation and attachment should be supported as workflow activities | ||
| 11 | Platform should support attaching multiple collaterals for a single loan application | ||
| 12 | Platform should be able to capture collateral data basis the collateral type | ||
| 13 | Platform should support de-dupe of collateral based on the predefined set of rules/logic | ||
| 14 | Platform should support margin setup basis the type of collateral. This is should be configurable and should be modifiable basis GUI or backend master sync | ||
| 15 | Platform should be able to handle the insurance of the assets and keep all details regarding the insurance. | ||
| 16 | System should auto generate the list and alerts for renewal of insurance as per the configured time | ||
| 17 | Platform to capture property details and check whether property is pre-approved or not from master list | ||
| 18 | Platform should be generate input for CERSAI and able to link with CERSAI through STP for charge creation and verification. | ||
| 19 | System should at least capture the following security details (primary and collateral) for each type of security such as: • Item (share, raw material, book debt etc.) • Description • Margin • sub – limit • valuation periodicity • insurance required (y/n) • insurance extent • next review date • insurance expiry period • type of insurance • periodicity of inspection etc. |
||
| Covenant Monitoring | |||
| 1 | System should support to view/ input financials & non-financial covenants based on pre-defined configurable rules | ||
| 2 | System should have ability for monitoring of covenants with automated alert notification. | ||
| 3 | System should have option for Covenant Expiry Monitoring | ||
| 4 | Report generation on compliance/ non- compliance of Covenants | ||
| 5 | System should have provision for configuring fee/penalty for lapses in covenant submission | ||
| Disbursement | |||
| 1 | System should provide facility to support part release/ multiple disbursement of the loan amount. Disbursements should be linked to the sanction terms, e.g. Limit, interest rates, tenure, pricing etc. | ||
| 2 | System should have provision to capture Disbursment Draw down schedule | ||
| 3 | In case of part disbursement, system should provide the details of the disbursement; Amount already disbursed, Interest accrued, balance disbursement etc. | ||
| 4 | System should have provision for online disbursment request along with relevant documents from Borrower/Customer as well as capturing Disbursement request of borrrower by NEDFi Officials | ||
| 5 | System should have provision to generate Disbursement letter /Loan Statement and ability to send it through email/whatsapp etc. from the system. | ||
| 6 | System should have provision for configurable disbursement checklist as per loan product etc. | ||
| 7 | System should have provision for capturing Disbursement Detail and track history | ||
| 8 | System should have provision for marking full and final disbursement | ||
| 9 | System should have provision for releasing disbursement as per disbursement process of NEDFi on electronic mode through integration with partner bank platform | ||
| 10 | Working Capital Disbursement - API Banking, DP setting, Uploading of Stock statement, Penalty, CMA data, Insurance data & policy | ||
| 11 | System should automatically calculate the drawing power/Loan Limit/Working Capital Limit based upon defined rules imposed by NEDFi based upon the details of the documents/Security entered | ||
| 12 | System should have a functionality of dispatch/ acknowledgment of security documents from the customer and within the expected date for obtaining pending documents, and instructions for disbursements. | ||
| 13 | System should provide facility for disbursement automatic routing; define disbursement approval authority, disbursement documentation. | ||
| 14 | System should link the customer information file / account to a particular branch say x and disbursed, service of the customer through another branch/HO say y. Further the system should be able to treat the exposure to either branch x / y as parameterized. | ||
| 15 | System should link disbursal for any type of loan / advance based upon progress reports / documentations submitted by the borrower | ||
| 16 | The system should support • Setting up of a Loan Disbursal account from where the loans would be disbursed (Through partner Bank) • Follow the unique serial numbers allocated to each loan case and disburse as per the queue serial number order wise • Match the amount available in the partner Bank account and disburse loan up to that amount only • Pick up the cases from the queue based on the amount available in the partner bank account" |
||
| 17 | System should globally maintain margin amounts to be collected by the NEDFi for all types of loans and advances as : • Flat amounts • Percentage • tiered slab - wise amounts / percentages • Combination |
||
| 18 | System should automatically calculate and display the applicable margin amount as per the loan product / scheme selected | ||
| 19 | System should automatically release the margin amount collected by the NEDFi on full payment of the loan by the customer. | ||
| 20 | System should automatically adjust the loan amount outstanding against the margin amount with the NEDFi. | ||
| 21 | System should display alert messages of the existence of any margin amounts with NEDFi in the event of the account being transferred to doubtful, sub -standard, loss etc. | ||
| 22 | System should define the means for collection of margin amount for each type of product / scheme (user defined). The system should at least support the following means • Cash • Account transfers • Cheques (clearing) • Combination of the above • Any other means for collection as desired by the NEDFi |
||
| 23 | System should charge interest only on the loan amount and not on the subsidy amount | ||
| 24 | System should automatically calculate and display the EMI table based upon the total exposure to the NEDFi | ||
| 25 | System shiuld have provision for capturing COD and also should have facility to revision of COD along with subsequent change in different modules | ||
| 26 | System should support adjustment disbursement features i.e. disbursement against interest dues etc. | ||
| Loan Management & Servicing | |||
| 1 | System should have provision for handling subsidy adjustement as per guidelines issuesd by NABARD and other relevant authorities. | ||
| 2 | System should have provision for handling Technical and prudential writeoff functionalities as per RBI guideline and NEDFi policy | ||
| 3 | System should have provision for handling Compromised Settlement/One Time Settlement process as per applicable policies and procedures of NEDFi | ||
| 4 | System should have provision to handle changes in commercial operation date and support to subsequent change in other related modules. | ||
| 5 | System should have provision for restructuring/rescheduling loans e.g. change in category of interest rates, repayment frequency, installment amounts, moratorium period etc. with appropriate levels of authority as per regulatory authority guideline | ||
| 6 | System should have provision to link to the credit monitoring module for review warnings, asset classification etc. | ||
| 7 | System should capture the risk weightage category based upon user definable parameters for each type / category of loan / advance | ||
| 8 | System should maintain rescheduling information of a customer for future reference | ||
| 9 | System should be able to calculate the provision for sacrifice in case of restructured accounts | ||
| 10 | System should be able to mark accounts as sensitive sector and track and monitor the accounts marked under sensitive sector | ||
| 11 | System to group NPA, sub - standard, loss etc. under particular account heads. The system should be able to give a consolidated view of all accounts grouped along with the details | ||
| 12 | NPA & Defaulter Loans Follow up Requirements | ||
| 13 | System should have classification of NPA, SMA and auto marking of NPA ,SMA etc. as per RBI guideline | ||
| 14 | Facility to define NPA buckets/Provisioning for different Loan Products & / or Industry & Purpose of Loan, defined as per the governing body | ||
| 15 | Facility to classify Loans as Standards, SMA0/1/2, Sub-standard, Watch, Doubtful, Loss etc. based on levels of defaults. | ||
| 16 | Facility to define separate provisioning percentage for secured & unsecured portion of NPA loans within each buckets | ||
| 17 | System should have the facility of loan recovery through E-Mandate,Standing order etc. at any branch of NEDFi | ||
| Re-Payment / Collection & Regular Follow-up | |||
| 1 | System should be able to generate reminders on over due, and reminder letters. | ||
| 2 | System should facilitate to provide for input of repayment instructions. Following repayment modes are anticipated but not limited To: • Standing Order • PDC • Cash • Cheque • Direct deduction • ECS • UPI • Netbanking • RTGS/NEFT • and or any other payment gate way as desired by NEDFi" |
||
| 3 | System should have flexible recovery date option(Recovery date may be changed as pere NEDFi specific, E.g: 10th May changed to 30th) | ||
| 4 | System should have provision to calculate installment both on sanctioned amount as well as disburse amount. | ||
| 5 | System should display a screen to summarize all closing costs, fees, and cost of borrowing with notes of any fee waivers for any fee category, including state tax fees. | ||
| 6 | System should have facility for different repayment systems like EMI, Non-EMI, Interest+ Equal rate of Principal or defined principal etc. as defined by NEDFi | ||
| 7 | System should allow users to define parameters of interest and principal for EMI and repayment calculations. | ||
| 8 | The system should support triggering of SMS / mail alerts in case default of EMI | ||
| 9 | System should generate a repayment schedule for loans as per type of loan for example Equated Monthly / quarterly installments, staggered payments (part payments over a period of time), balloon payments (final settlement installment usually large sum) etc. | ||
| 10 | System should support part or pre – payment and readjust the loan payment schedules as per payments . | ||
| 11 | System should generate letter on closure/Overdue/Installment arrears through system and trigger SMS/Email alerts | ||
| 12 | System should adjust payments made (loan recovery) against : • Interest first • Principal First • Charges / Penalties First • Against tier / slab carrying higher or lower rate of interest. • Recovery of principle at one frequency and recovery of interest in a different frequency (e.g. recovery of principle in every six months but recovery of interest on a monthly basis) • System should able to maintain different moratorium period for principal as well as interest. • Any order (to be decided at the time of transaction) • Custom defined ad hoc repayment schemes. For example recovery of 20% or X amount of the loan in 3 months, recovery of another 35% or Y amount in 8 months and the balance to be recovered in 13 months • System should define a grace / moratorium period and recover (during moratorium / grace period) • Only interest • Only principal • Equated installment • Combination of the abov |
||
| 13 | System should have provision for Excess/Advance Repayment parking in suspense account and posting it against future dues when such due arises | ||
| 14 | System should maintain a log of Post Dated Cheques collected against a particular loan. | ||
| 15 | System should recover all charges / taxes to be recovered before / after adjusting interest. | ||
| 16 | System should charge the customer a penal rate / flat rate for repayment of the loan before X number of days, delay installments etc. (parameterizable) | ||
| 17 | System should have facility to waive off the charges with appropriate on-line approval/authorisation | ||
| 18 | System should define rebate rates for particular types of loan products / schemes for early settlement. | ||
| 19 | System should automatically compute taxes and charges applicable on recovery of loan installment | ||
| 20 | Based on defined parameters such as the loan product, branch code, customer type, year of transaction etc., a running loan reference number to be generated on processing of a new loan. | ||
| 21 | System should capitalize interest as per parameter set for a defined loan product / scheme. | ||
| 22 | Facility for providing financial leasing facilities to customer. The system to have facility to capture key information such as capital amount, rate of advance, lease period in years, number of rentals, effective rate of interest, number of prepaid installments etc. On capturing the above information, the system should compute the Leasing facility amount (capital + interest), Monthly net rental, monthly gross rental (net rental + Tax, Tax, Prepayment amount and other charges and flat rate of interest. | ||
| 23 | System should able to send SMS/Mail for increase and decrease of Drawing power limit. | ||
| 24 | System should able to send/generate show cause notice only on default amount (when loan is default) | ||
| 25 | System should able to send/generate recall notice on total O.S amount (if the loanee not recognize the show cause notice) | ||
| 26 | On repayment, the relevant loan limit of the customer should get updated. | ||
| 27 | User-defined watch-lists · Tag loan accounts to watch-lists · Ability to define specific actions to be taken on loan accounts |
||
| 28 | Record all follow-up actions with date and time and alert users of next actions | ||
| 29 | Provision for inputting collector(DSA/ BC/RO) capacity each month based on leave schedules, new hiring, attrition etc. | ||
| 30 | Provision for inputting the maximum ACR (account per collector ratio) acceptable, based on collector vintage and/or efficiency. | ||
| 31 | Allocation should be possible to the level of not just an external collection agency, but to a team leader/field collector /tele-caller at the Agency itself. | ||
| 32 | Availability of productivity/ efficiency reporting • Agency level • Team level • Collector level • Others |
||
| 33 | Mandate ordering of queues allocated to a specific collector • Collection Strategy • Queue Prioritization Example: ensuring that all collectors call “Broken promise’ queued accounts first, before moving on to other queues." "Feasible built in controls such as ‘no promises can be taken beyond x days’ or ‘minimum promise amount = EMI / Non EMI’ etc." |
||
| 34 | Back-up of the daily delinquency status | ||
| 35 | Assessment of agency & agent level productivity | ||
| 36 | Variable Compensation structures for DSA/BC/RO | ||
| 37 | Before system assignment of delinquent accounts, the delinquent accounts/case should be sequenced by the overdue days and Delinquent amount (from the most to the less). | ||
| 38 | After the collector could make Promise to Pay, this system should automatically calculate the penalty fee and GST for penalty to inform the customers. | ||
| 39 | Customer and delinquent accounts/cases search (Inquiry relevant information) by products or by the collectors • Customer Inquiry • Account Inquiry • Statement Inquiry • Payment Inquiry • Note, Message etc. |
||
| 40 | Ability to transfer or assign a single case to another business unit(eg agency) | ||
| 41 | Provision for Allocation of the case to the teams and different collection agencies in different regions | ||
| 42 | Escalation of work items | ||
| 43 | Multiple Relationship screens - Ability to show all products for a customer on one screen to accommodate the collector to handle multiple relationship for the same customer. | ||
| 44 | Team inquiry for a supervisor monitoring screen which provide a complete view of: • collection team • cases which were assigned to the collectors |
||
| 45 | Provision for future action and follow up prioritization | ||
| 46 | Provision for Work List (account assigned to collector) | ||
| 47 | Provision for Priority List which shows accounts scheduled for current day and backlogs, if any | ||
| 48 | Support provision for Work flow mechanism for the decision required at different levels. | ||
| 49 | Perform bulk actions on a group of loan accounts and automatically post the activity to individual accounts & maintain audit trail Eg. Reminder letters to be sent to bulk loan accounts can be generated from a common interface." Updation of master customer data (e.g. current address) through the recovery interface with appropriate authorizations "Capture the correspondence address preference • Property Address • Work location • Guarantor • Others |
||
| Other Functionalities | |||
| 1 | System should provide facility to support various EMI calculators (monthly, quarterly, half yearly, yearly, etc.) | ||
| 2 | System should have the option to open bullet loans(for Loans with Gestation/moratorium period) | ||
| 3 | System should be able to define multiple business Partners, Creation of user groups under each business partner and creation of users under each group. Subscription will be based on the number of NEDFi Branches only | ||
| 4 | System should be capable of validating data at entry as well as during "Save" level. | ||
| 5 | System should maintain a master list of legal vendors, verification vendors and other external agencies region / city wise | ||
| 6 | System should have a provision to capture Sector/sub-sector, Borrower category, Occupation code and other NEDFi Specifi Requirement details as required by statutory authorities. | ||
| 7 | System should have provision to capture vital data (including Financial Documents Type of Organization, Business registration number, Place of incorporation, Number of years in business Equity Structure, Ownership structure, Contact Information, Directors & Key Management, Business operations etc.) as required for Non-Individual Customers, Risk rating and MIS | ||
| 8 | KYC documents and compliance are to be based on Constitution of the applicant or other criteria as to be decided by the NEDFi. | ||
| 9 | System should deny further data entry if it does not fit preliminary requirements as per defined parameters for the product, customer type etc. However preliminary data may be saved in the system for future use and for making a Cross offer | ||
| 10 | System should support error / warning / action messages for doubtful / wrong entries | ||
| 11 | System should be able to edit and view prospect/customer details during defined stages of Application processing and to process the application, eligibility and other processing parameters based on new data. | ||
| 12 | System should be able to capture the date and time details of application like date of receipt, date of Login, date of entry and other dates as will be defined by the NEDFi | ||
| 13 | System should have ability to send Emails /SMS to the partners/customer/employees to initiate the required process immediately. | ||
| 14 | System should keep history of each of parameters change. | ||
| 15 | System should have ability to track the Staff with whom and for how long the customer's application is pending. Date and Time associated with TAT should be non-editable | ||
| 16 | System should be able to support and take care of interest calculation and accrual methods like….Daily, Weekly, Monthly, Quarterly, yearly or any other method defined by user | ||
| 17 | System should be able to capture standard compliance checklist devised by NEDFi from time to time | ||
| 18 | System should have provision for Borrower wise details of various documents executed along with date of the execution. | ||
| 19 | System should be able to create/save/amend/ abort/ appeal/ recreate Loan applications. | ||
| 20 | System should be able to accept details of valuation certificate from approved values periodically. | ||
| 21 | While completing the data entry the system should be able to give an alert in case any expired document is entered | ||
| 22 | Facility of document tracking across the life cycle of the loan application. | ||
| 23 | All e-mail/electronic communications (external and internal for recommendations, concurrence etc.) should be stored electronically as a part of all loan documentations. | ||
| 24 | System should support both decentralized and centralized operations. | ||
| 25 | The NEDFi users should be allowed to follow up with the customer using built in decision scripts, capture follow up results, easily access customer contact information and manage follow up through reminders. | ||
| 26 | System should have provision for defining and modifying eligibility norms and other key features without support from Software Vendor | ||
| 27 | Supervisor should be able to override the distribution of the tasks to processors and reroute to other processors. | ||
| 28 | System should have provision to generate alerts from each stage – normal alerts and exceptional alerts. | ||
| 29 | System should be able to define various hierarchies:- Defining the organization hierarchy but not limited to following list, a) Define the roles performed in the organization, b) Co-relating the role of employee and his area of work, c) Co-relating business partners with products offered, d) Define hierarchies based on type of deviation (for e.g. Credit for exposure, Delegation of Power |
||
| 30 | System should be able to customize the screen based on user’s hierarchy in the organization. Restricted viewing or viewing of related fields only. | ||
| 31 | Ability to handle substitution (Assign/Reassign) due to leave/ Emergency/ Transfer/ Improvement of TAT(Turn Around time). Only Authorized Officials should be allowed for this job. | ||
| 32 | The system should be able to interface with the CRM solution for information on the prospects | ||
| 33 | The system should have a complete module for Channel partners (BC/Direct Sales Agent/RO etc.) Management and Monitoring | ||
| 34 | Credit Scoring model is required | ||
| 35 | System should have facility to provide real time API interface with partner Banks. NEDFi may add / change partner Banks, bidder is required to provide APIs through out the tenure without any additional cost to NEDFi | ||
| 36 | System should have ability to send Reminder Emails and SMS to designated higher Officials of the NEDFi which can be scheduled in the system as online mode/batch mode. | ||
| 37 | System should be auto-routing and control based on parameters set for each product/group of products as defined in the process flow. | ||
| 38 | The system should provide a facility to User to raise and clear exceptions at different stages of the loans process with user comments. | ||
| 39 | Should be able to classify loans as per RBI or any regulatory authority norms | ||
| 40 | System should have the facility to assign relationship managers for identified corporate accounts | ||
| 41 | System should maintain and track follow-ups of relationship managers / NEDFi officers | ||
| 42 | System should arrive at a compromisable amount across multiple schemes given the interest details for NPA accounts / any other method of calculation as desired by the NEDFi. Further the system should be able to capture the compromised/OTS amount and the details of the compromise/OTS for multiple schemes | ||
| 43 | System should to handle the subsidy given by Government and various other public bodies such as NABARD etc. and calculate the EMI and interest based on that. | ||
| 44 | The system should support the generation of statistical and management reports like: • Number of proposals assigned • Number of proposals completed • Time taken to complete each proposal • Process History Report • User Performance Report • Average proposal Time Report |
||
| 45 | System should define due dates for each limit and track the same | ||
| 46 | System should have the provision for switch over from Non EMI to EMI and vice versa with retrospective effect | ||
| 47 | System should have the facility to capture the total value of the security plus the NEDFi’s share in case of consortium loans. Further the system should be able to maintain the percentage share and amount of security held with the lead NEDFi and consortium member NEDFis | ||
| 48 | System should have facility to capture number of employees against each project | ||
| 49 | System should automatically release the subsidy amount collected by the NEDFi on full payment of the loan. | ||
| 50 | Sytem should send noitifications to customers on any change of dynamic sanction term on real time basis | ||
| 51 | Real estate Project Case need NOC certificate on pre determined criterias as per the format provided by NEDFi | ||
| 52 | In Account Master there should have provision of Offset interest rate | ||
| 53 | Exposure Norms checking during loan sanction (Product wise/Industry wise etc.) | ||
| Reports | |||
| 1 | Report on pending documents after disbursement, system should provide report on daily basis automatically as well as user should be able to generate as and when required for all the documents pending from customer proposal wise. Specific Documents received / Pending (as per checklist) should be a part of account opening process | ||
| 2 | Report should be available for follow up with clients on Offer letter issued and not acknowledged with details like Relationship Manager name, client details, Product, Date of application, date of issuance of offer letter and days pending for acknowledgement. | ||
| 3 | Report should be available from the system on the proposals approved but not accepted by the customer. | ||
| 4 | Report should be available for follow up with clients on Sanction letter issued and not acknowledged with details like Relationship Manager name, client details, Product, Date of application, date of issuance of sanction letter and days pending for acknowledgement. | ||
| 5 | The Loan Processing System (LPS) system should support the generation of statistical and management reports like Number of proposals assigned, Number of proposals completed, Time taken to complete each proposal, Process History Report, User Performance Report, Average proposal Time Report, MIS reports as decided by NEDFi from time to time | ||
| 6 | The Loan Processing System (LPS) module should support definition of new customized reports based on existing data and other calculated logic. | ||
| 7 | MIS should be available through system like branch/BC/RO wise exposure, industry wise exposure etc. any statutory reports, user wise report, loan expiry report, etc. | ||
| 8 | System should provide comprehensive audit trail report on all actions performed on the system including modification of data. | ||
| 9 | System should generate a report which gives the category-wise application received, approved, Pending during particular period. | ||
| 10 | System should provide employee wise detail report for ascertaining TAT and quality of work performed by the employee | ||
| 11 | Complete advances and loans portfolio sector wise and product wise report should be available from the system | ||
| 12 | Report on operative accounts linked to the loan accounts. | ||
| 13 | Should be able to handle Excess EMI to the loan account to enable the user to trace and refund the excess EMI easily. | ||
| 14 | Exception reports/ Deviation Reports to be available to Authorized users only | ||
| 15 | System should be able to receive various reports in predefined form from authorized vendors through internet, email, and other electronic media in a secured manner. | ||
| 16 | Facility to generate online reports. Ability to drill down into the information provided in the reports. | ||
| 17 | Reports on Credit Risk Analysis should be available along with proposal and other related documents of the proposal | ||
| 18 | Credit Reference Report /Other report- system should provide report with interfacing from Credit Bureau and or any other agencies as required by NEDFi. | ||
| 19 | Report on commitment fees charged | ||
| 20 | System should provide a report on the credit and debit summations | ||
| 21 | System should be able to generate a report on based on the sanctioning authority and further also based on the status of the account as on the date of the date | ||
| 22 | System should be able to generate a report of all EMI on any date division wise/ Branch wise/BC wise/RO wise bill unit wise or as per user defined requirements. | ||
| 23 | System should enable generation of demand of EMI report | ||
| 24 | System should enable generation of detailed report of all loan products offered by NEDfi. | ||
| 25 | Facility to generate slab wise NPA related reports | ||
| 26 | Executive Dashboard on Document TAT overdue, Application Tracking, Other Alerts (Contract overdue, Expired date, Surveyor, Appraiser.) | ||
| 27 | Separate analysis model for mortgage loan is required | ||
| 28 | System should have facility to provide service based feedback mechanism from client through SMS and email both. After completion of any loan application, an SMS and mail should go to customer for their feedback anonymously. Customer should be able to give the feedback through SMS to logging in the portal. | ||
| Audit | |||
| 1 | Solution should have the feature of defining an audit (Eg: Type of audit, Audit Period, Start/End Date, Auditors, Expiry Date of audit comments, Due date for next audit) | ||
| 2 | Solution should have the feature of defining the audit formats based on audit definition Customer data (Eg: limits, facilities, sanction order conditions) relevant for audit to be made available in the solution |
||
| 3 | Solution should able to display the brought forward comments of previous audits with appropriate tagging (customer name, year, categorization etc.) | ||
| 4 | Solution should be able to band the comments into different categories (Eg: Serious, Major, Moderate & Minor) based on risk, priority etc. | ||
| 5 | Solution should be able to intelligently prompt vulnerable areas based on past observations The solution should have a appendable & configurable comments pertaining to above types of audits (Eg: Stock due and not done, Sanction order conditions not complied with, Party did not submit financial statements) |
||
| 6 | Solution should have an integrated case management/workflow for audit comments | ||
| 7 | Solution should generate audit reports with the required details as per NEDFi | ||
| 8 | Solution should generate dashboards on comments with required details | ||
| 9 | Solution should provide for risk categorization of branch & customer based on audit comments | ||
| 10 | The solution should have a appendable & configurable alerts pertaining to above types of audits | ||
| 11 | Solution should be able to display the banding of comments inherited from the audit module | ||
| 12 | Solution should be able to assign pre-fixed resolution time for audit comments | ||
| 13 | Solution should be able to mark with status for the comments (Eg: Resolved, Unresolved, Partly resolved) | ||
| 14 | Solution should be able to give alerts based on risk, priority or resolution status | ||
| 15 | Solution should have an option to carry-forward of comments to subsequent periods | ||
| 16 | Recording of adverse comments noted in multiple/consortium banking accounts/meetings | ||
| 17 | Solution should be able to give individual and consolidated dashboards on the status | ||
| 18 | Solution should have an integrated case management for alerts | ||
| Legal /Litigation Data Requirements | |||
| 1 | Integration with legal data sources for civil suits and court cases | ||
| 2 | integration with e-stamping / e-sign (single and multiple user) solution for document execution | ||
| 3 | integration with digital signature platform such as Adhaar based/DSC etc. | ||
| 4 | Provision for digital loan agremeent genration and execution | ||
| 5 | Integration with CERSAI | ||
| 6 | Integration with NESL | ||
| 7 | The system should have facility to create Advocate / Lawyer/Legal Officers/Recovery Agent master with address, email, mobile number etc. and to assign multiple branches and multiple cases at HO,BO and RO levels | ||
| 8 | The system should allow to create comprehensive court master for different jurisdictions and levels. | ||
| 9 | The system should allow to create comprehensive expense master. | ||
| 10 | System should have ability to generate standard notice / legal notice etc. | ||
| 11 | The System should provide Work-flow based management for pre-suit approval from business, legal and management authorities for the permission for filing suit / application, the higher level user can be informed of pending Permission / approval | ||
| 12 | System should have master data to capture Panel Advocate Data | ||
| 13 | System should have facility to capture fees paid / unpaid to Advocate with the case id | ||
| 14 | System should have ability to generate standard notice / legal notice etc. | ||
| 15 | Require a due date diary for recovery and legal (pre and post) with alert mechanism. | ||
| 16 | The system should have the facility to capture comprehensive data pertaining to a case - Borrower and Co-Borrower's information, Guarantor's information, Any other interested party information, Collateral information with valuation and any such other data that NEDFi may need e.g Mortgage Deeds, Try Party Agreements etc.. | ||
| Suit / Application Proceeding details | |||
| 1 | In case, suit is filled as a follow up of SARFAESI action, there should be linkage of suit details with SARFAESI details / Cooperative / Civil court / District Court | ||
| 2 | The system should have the functionality to input Suit Stay details and Withdrawal details, restoration petition, writ petition etc. | ||
| 3 | The system should support One-time settlement process. | ||
| Operational Requirements/Reports | |||
| 1 | The system should be able to provide entire historical record including current status. | ||
| 2 | The system should allow to capture each stage wise, expense head wise and advocate/lawyer wise expenses such as court fees, notary fees, conveyance, etc. | ||
| 3 | The system should have facility to record & report the number of briefs each advocate/lawyer is handling. | ||
| 4 | The system should be capable to store details of multiple possessions | ||
| 5 | The system should provide for sending alerts for upcoming court dates to concerned nodal officers/dealing advocates/Regional Offices/Branch Managers | ||
| 6 | The system should also have facility to record the details of all winding up cases . | ||
| 7 | The system should provide details of the legal cases on weekly/monthly basis which includes case status, recovery performance, expense per case/advocate etc. | ||
| 8 | Required following various reports:- Statement of Total Pending Court Cases [HO / Branch] Payment Register of Legal Department [HO] TDS Register [HO] Advocate Payment Fees Register [HO] Case Summary Statement of Suits Statement of Suits coming up for Hearing Statement of Top Suits filed by Amount Statement showing recovery made in Suit filed Accounts Statement of claims against NEDFi “Not Acknowledged as Debt ” System should provide Loan Product wise Legal cases |
||
| The above list are not exhaustive. If there is a change in requirements without impacting the overall proposed solution then it will be identified and designed during BPR and SRS stages and the same will be implemented during implementation stage | |||
| Summary | Count | ||
| Total "F" Count = | 0 | ||
| Total "C" Count = | 0 | ||
| Total " N" Count = | 0 | ||
| RFP No.: NEDFi/RFP/IT/01/2022-23 Date: 21/06/2022 REQUEST FOR PROPOSAL (RFP) RFP for Selection of LLMS & General Accounting Solution Provider in SaaS Model | |||
| Minimum Functional Specifications for General Accounting Solution | |||
| Sr. No. | Functional Requirement | Bidder's Response (F/C/N) |
Bidder's Comments |
| A | Master Configuration | ||
| 1 | The Accounting system should support IND AS standard Accounting system | ||
| 2 | The proposed System shall have provision to define accounting periods (Financial Year) along with Opening and Closing feature | ||
| 3 | All the functionalities and features of the proposed System should be accessible from a secure web interface which shall be user friendly and based on modern UI/UX design principles | ||
| 4 | The Proposed System shall have provision to define an user definable numeric or alpha numeric GL codes as per industry best practices. | ||
| 5 | System shall have provision to define any number of sub – ledgers/sub heads as per the requirements of NEDFi within the General Ledger or Sub-General Ledger based on profit centre and cost center | ||
| 6 | Main General ledger with the facility to generate sub-general ledgers based on profit centre | ||
| 7 | The proposed System shall have provision to define accounts e.g. accounts with only debit balances, accounts with credit balances, nil balances etc. | ||
| 8 | Facility to define account relationships | ||
| 9 | Facility to create General Ledgers under the following categories which can have further different levels. The categories are as follows: •Asset •Liability •Income •Expenses •Contingent Asset •Contingent Liability |
||
| 10 | System to support defining accounting entries to be generated at various stages etc. (e.g. entry stage, modification stage, deletion stage, reversal etc.) for all system / customer initiated transaction / events | ||
| 11 | System should support creation of cost centres for all expenses / losses based on NEDFi policy | ||
| 12 | System should have provision for separate payment method assigned to each expense code | ||
| 13 | System to automatically transfer the amounts to a particular general ledger head based on user definable parameters I.e. matured deposits over "x" period, NPA accounts etc. | ||
| 14 | System to automatically retransfer the amounts from the respective general ledger heads once the accounts have been re- classified as normal / regular accounts | ||
| 15 | System to update the GL's maintained for different business units / branches through an automated interface with those systems. | ||
| 16 | System to support creation for provisioning (e.g. expense, loss etc.) as per provision norms defined by NEDFi (parameterisable) based on user definable parameters e.g. x percentage of standard loan, y percentage of sub-standard loan, z percentage of doubtful loan, any combination etc. There should be no limit on user definable parameters as well as provision norms. Further the system should be able to permit the user to define the provision norms branch - wise, region- wise etc. as desired by NEDFi The provisioning for Loan account shall be integrated with LLMS system to avoid manual intervention |
||
| 17 | System should have provision to accept encrypted and decrypted files for payment acceptance and generate encrypted files for bulk payment facilities | ||
| 18 | System should be able to handle accounts receivable process including generation of vouchers, invoices, credit note and getting receipts against its on actual and accrual basis both. Various types of receivables could be rent, interest among others, advisory & consultancy service etc. Details of this need to be pull from concerned modules of the proposed Accounting System. | ||
| 19 | System should be able to handle accounts payable process including generation of PR/PO, vouchers, entering invoice, Debit Note and making payments both for operating and capital expenditure. | ||
| 20 | The system shall have provision to interface with LLMS system to capture the data related to loan disbursement, loan receipt, loan interest accural, Asset Classification, provisioning, waiver, writeoff etc with an automated mechanism | ||
| 21 | The proposed system should have provision to integrate with NEDFi's Banking Service provider through API banking/CMS/file upload features for making payments. | ||
| 22 | System should have provision to capture ledgers for Employee/Vendor/Customer/supplier etc. | ||
| B | Transaction/Payment | ||
| 1 | The proposed Accounting system should have provision to accept effective date of posting (entry) from the LLMS system | ||
| 2 | System should provide facility for context sensitive updated on-line help for various GL heads / Sub-heads and P& L heads to be debited / credited at the time of posting and authorizing. | ||
| 3 | The system should be able to freeze the accounts after adoption of accoutns (user definable). | ||
| 4 | System to support GLs where manual intervention is required and certain GLs where all the entries would be posted by the System. | ||
| 5 | System to restrict direct posting to defined accounts | ||
| 6 | System to define accounts as closed accounts with appropriate authorization | ||
| 7 | System should support where the accounting activity is | ||
| 7.1 | completely centralized | ||
| 7.2 | completely decentralized | ||
| 7.3 | partial centralization | ||
| 8 | Facility to support provisional closure (provisional freezing of accounts till adoption of the Financial Statements) and rollover to the next financial year. | ||
| 9 | System to automatically update the respective account heads as defined for any particular transaction | ||
| 10 | System should have automatic bank reconciliations features. | ||
| 11 | Bank reconciliation should support the following: | ||
| 11.1 | The system should facilitate autometically upload or fetched directly the bank statements received in electronic media (through file/API) in the format shared by banks with minimum manual intervention. | ||
| 11.2 | The system should facilitate both automatic and manual intervention of the bank reconciliation process | ||
| 11.3 | System should knock off the matched items depending on the variables defined by NEDFi and leave the residual unmatched entries for bank reconciliation open items | ||
| 11.4 | Once the Bank reconciliation is done through the system then the same has to be locked and unlocked with the permission of given role. | ||
| 12 | System to handle value date facility unless the accounts is freezed. | ||
| 13 | The system should have facility to access budgeting and forecasting module/data/reports as and when required. | ||
| 14 | The system should have support interfaces/API with other external 3rd party systems and have the ability to upload / download information to and from other systems. | ||
| 15 | Remittance of TDS by nature of payments in Department of Income Tax . TDS module should be part of the accounting software | ||
| 16 | The system should be capable of interfacing with all other functions within the organization | ||
| 17 | The system should be able to manage pay and allowence and other employee related expenses by integration with HR & Payroll system | ||
| 18 | Full compliance with income tax rules (Parametarized) | ||
| 19 | Payment can made by:: • Electonic Fund Transfer • Cheque • Online Payment (through payment gateway/API Banking/CMS) • Fund transfer (through payment gateway/API Banking/CMS) • Cash payment |
||
| 20 | Configurable frequency of payments e.g. daily, monthly | ||
| 21 | Pay advances and automatically reclaim them, or deduct from expenses claim. The System should generate debit note and credit note autometically. | ||
| 22 | Provision for directing exceptional transactions to system pointing account for smooth day end process with statement of exceptional transactions to be attended to on the succeeding day. A history file of such transactions to be available account wise/GL code wise/Branch wise for supervisory purpose | ||
| 23 | Entries on blocked and closed/dormant accounts are only allowed to specific user role | ||
| 24 | General provision requirements | ||
| 25 | Recovery of taxes and other charges from members for a given period against the actual amount paid by NEDFi | ||
| 26 | System should be capable to interface with deposit module (CFSS) in future during the project tenure as per RBI guidelines. Currently NEDFi is not accepting the deposit but in future as per RBI guideline if starts acceptance of deposit then the same module (CFSS) should be interfaced with the accounting software. The software should be scalable enough to interface. | ||
| 27 | System should capable to interface with NEDFi's HR&Payroll application and disburse the salaries and other allowences | ||
| 28 | GST module should be part of Accounting software | ||
| 29 | The proposed accounting system should be capable enough to manage NEDFi's all vendors with required information and their ledgers | ||
| 30 | System should process any Invoice and flow of automatic entry for payments & approvals | ||
| 31 | To release part payment against an invoice and balance payment process on a subsequent date | ||
| 32 | to facilitate statutory compliance related to GST/TDS at the time of capturing the expense data entry. The tax slab/rates are parameterised. | ||
| 33 | Tracking of funds Utilization, Preparation of utilization Reports | ||
| 34 | Ability to customize / generate various report as prescribed by RBI based on prescribed format | ||
| 35 | Generation/ creation of statutory reports.. | ||
| 36 | Ability to customised report for MIS as per the management. | ||
| 37 | System should facilitate audit trail of transactions/ record/ entry | ||
| 38 | Separate login access right to auditor, to audit the transaction/ Books of accounts | ||
| 39 | The System should have a fixed asset module with depreciation calculation method as per Statutory and Regulatory Guideline. | ||
| 40 | The System should have facility to integrate with Budget & Forecasting Software | ||
| 41 | The System should have provision for managing different investments in multiple segments by NEDFi (other bank investment in the form of FD, MF, Equity etc.). | ||
| C | Report | ||
| 1 | System should generate Trial Balance, P & L A/c & Balance Sheet, Cashflow statement, schedules forming part of Balance Sheet and consolidate the same at profit centre level and at corporate level. | ||
| 2 | System to collate various types of information for the purpose of various analysis of deposits/investments, advance, expenses, income and taxes | ||
| 3 | System to provide for Off balance sheet items e.g. contingent liabilities, bills for collections, outstanding Purchase orders, Bank Guarantee etc.) | ||
| 4 | Facility to have GL consolidation at different branch levels such as: • Branches • Head Office |
||
| 5 | Facility to have final consolidation of the GL at Head Office | ||
| 6 | System to generate Accounting Trial Balance such as: • standard trial balance as on date, • trial balance with date range, and • trial balance with opening balance for with opening, transactions summery and closing balance. |
||
| 7 | System should be able to genetae sub trial report. | ||
| 8 | System to generate financial statements along with notes to financial statements as per GAAP (Generally Accepted Accounting Principals) and IFRS (Indian Financial Reporting Standards). | ||
| 9 | System should be able to generate trial balance with additional information such as fair value, revaluation, etc. required by the IFRS. | ||
| 10 | System should be able to generate any ledger reports at any time and at any level. | ||
| 11 | System to generate statement of provisions as per user defined date / period at branch level as well as Head office level. | ||
| 12 | System to support generation of Bank reconciliation statement related reports, Bank Statement report etc. | ||
| 13 | System to generate a report at user definable time intervals for all transactions done in suspense (Sundry) accounts at the branch and head office account along with details of the transactions and outstanding from date range and amoun wise | ||
| 14 | System to support generation of schedule of open items lying unreconciled in the Suspense GLs / Assets / Liabilities with full details at predefined intervals specified by NEDFi | ||
| 15 | System to provide reports as specified by NEDFi as on a particular date / range of dates including at least the following: • Trial balance by reporting currency, by branch, Head Office and consolidated at Organization level • Balance sheet by branch, by profit centre and consolidated • Profit and loss by branch, by profit centre and consolidated • Cash flow statement by branch, by profit centre and consolidated • Detailed journal • List of accounting entries by batch • Listing of profit and charges entries posted • Age analysis of suspense accounts • Total credit and debits gone to GL account during a user specified period • Statement of maturity analysis of loans, advances, leasing, etc. on a time scale with values. - LLMS, need to be discussed for leasing option • Movement of user specified GL accounts for reserves and provisions • Deposit analysis by branch, by age, by rate - not clear • Advances analysis by branch, by age, by rate |
||
| 16 | System to at least consolidate: • Annually • Monthly / bi monthly • Half yearly • Weekly • Daily • As specified |
||
| 17 | System to generate management information reports as specified by the NEDFi, as on a particular date / range of dates including at least the following: • Highlights of changes in deposits investment, advances, availability of lending funds, loans etc. in the form of an auto alert • Statement of breakeven rates for different advance schemes - not clear (Report) • Statement of interest received from the customers • Comparison of profit and loss of all accounting entities against the plan • Statement of cost allocation to cost centres and variance analysis • Schedule of fixed assets for all accounting entities • System to generate the monthly progress report branch – wise and consolidate the same for various branches at the head office based on parameters defined by NEDFi. not clear (Branch performance) • System to generate performance monitoring reports for branches on the basis of actual v/s budgeted and list variances in terms of amounts and percentages - needs to be discussed (Performance report linked with Budget and forecasting) • Effective rate of interest on advances classified in terms of different advances • Bucket - wise particulars of outstanding advances based on user definable criteria (e.g. unexpired period, slab - wise, maturing within x months etc.) for computation of structural an interest rate sensitivity statements as per user definable frequency. - not clear (ALM related report) • Yield on advances |
||
| 18 | System to consolidate the GL balances in INR | ||
| 19 | System to view Closed GL Account details | ||
| 20 | System to generate Cash Book on a particular date | ||
| 21 | The system should support generation of P&L statement period - wise I.e. for current quarter as well as cumulative quarter | ||
| 22 | Should be able to generate reports such as, Trial balance, subtrial, ledger reports, Financial Statements along with Notes to Financial statement | ||
| 23 | System to generate a report for each general ledger account, sub - account, product / scheme for reconciliation. The system should generate warning messages in event the individual account / product totals do not match the GL totals | ||
| 24 | Should be able to generate certificate for DIT and TDS based on the prescribed report format at any point of time, eg. instantly, annually, etc | ||
| 25 | Suite of standard expenses reports including: • expenses listing • analysis of expenses by code, employee, date, location • receipt and claim reconciliation reports • trend analysis • audit reports • information to identify potential tax dispensations • standard letter templates to cover common travel bookings, queries |
||
| 26 | Generation/ creation of statutory reports. including ALM report etc | ||
| 27 | Ability to customised report for MIS as per the management. | ||
| 28 | Analysis e.g.: • analysis of expenses and travel expenditures • comparing planned travel / trip costs versus actual costs • monitoring employee's travel and expense accounts • analysis of data to streamline processes further • identifying spending trends and patterns (and then using the information to negotiate better supplier discounts and / or form strategic relationships) • System to generate a report with the date of lodging of claim, approval date and payment date • System should generate depriciation report |
||
| D | Statistics and volumes - Current and Forecast | ||
| 1 | Number of employees claiming expenses | ||
| 2 | Number of types of expenses claimed | ||
| 3 | State expenses types | ||
| 4 | Claims processed per week / month: | ||
| 5 | System should have drill down facility from Balance Sheet, Profit & Loss & Trial Balance | ||
| E | GSTN Requirement | ||
| 1 | Data capturing of State wise GSTIN Number for NEDFi | ||
| 2 | Data Capturing of GSTIN Number for the customer | ||
| 3 | Data Capturing of GSTIN Number for the vendors | ||
| 4 | Tagging of Income & Expenditure Heads within the Profit & Loss Accounts in NEDFi | ||
| 5 | Transactions for the charges to enable the GST Transaction for the customer | ||
| 6 | Tagging of transactions for the GST. | ||
| 7 | Invoicing of the customer for the transactions. | ||
| 8 | Data generation for Submission into format required by Tax Authorities. | ||
| 9 | Direct Interface to GST Solution as and when implemented by Government. | ||
| 10 | Reversal of tax for specific customer | ||
| 11 | Returns for GST for the customer / NEDFi’s Data. | ||
| 12 | Manual Transaction for GST collection | ||
| 13 | Manual tagging / de tagging of the GST transaction within the Transactions. | ||
| 14 | Dynamic Dashboards for the real time updates & statistics | ||
| 15 | Real Time MIS Reports for Statistics of GST Collected. | ||
| 16 | Reports to customers for the GST IN Submission for customers who have not submitted the GSTIN. | ||
| 17 | Statement of GST Accounts with appropriate details for the transactions. | ||
| 18 | Audit trail of all data stored for Customer & transactions. | ||
| 19 | System should have facility for User to able to tag the income & Expenditure Accounts for GST | ||
| 20 | System should have facility to define GST in the System. | ||
| F | GST Reports | ||
| 1 | List of Accounts / Customers which attract GST and GST IN not submitted | ||
| 2 | Summary for Customer with Transaction Amount and Tax | ||
| 3 | Report for reversal of GST input - Eligible, ineligible etc. | ||
| 4 | Reverse charge details | ||
| 5 | Detailed report for transaction done during period and tax collected (HSN/SAC wise etc.) | ||
| 6 | Detailed report for transaction done during period and tax collected (HSN/SAC wise etc.) | ||
| 7 | System should have all other reports required as per Statutory/Regulatory authorities | ||
| The above list are not exhaustive. If there is a change in requirements without impacting the overall proposed solution then it will be identified and designed during BRD and SRS stages and the same will be implemented during implementation stage | |||
| Summary | Count | ||
| Total "F" Count = | 0 | ||
| Total "C" Count = | 0 | ||
| Total " N" Count = | 0 | ||
no reviews yet
Please Login to review.
