Credit risk data reports

credit risk data reports intro as a cross river credit bin sponsorship partner, we need you to send us a monthly summary of specific credit risk metrics that are not visible to us to make things easy, we’ve got a common data exchange format ( csv comma separated values) for you to use this page will walk you through the metrics you need to share with us, the data exchange format, and how to send the file our way before you begin ensure you’ve submitted the complete ip access request for crb sftp services form get this form from your cross river implementation or relationship manager when cross river gets your completed form, we begin the process of setting up your sftp access learn more about set up sftp setup once you are set up for sftp, ensure you have a /clientcredit subfolder in your cross river sftp folder this is where you’ll put your csv file cross river provides you with the full path when you get your access credentials contact your relationship manager with any questions file structure the credit risk metrics file must be formatted in a specific way to prepare the credit risk metrics file use this file naming convention creditriskmetrics partnerabbreviation datetimestamp csv use a 3 to 6 character string for the partnerabbreviation that clearly refers your organization, and that cross river will understand file names should be unique use the date time stamp from when the file is created this does not need to match the date of the records within the file format the datetimestamp as yyyymmddhhmm if the date and time stamp is automated, the format can include seconds for file renaming, update the datetimestamp or append 'update' or ' v2' after the datetimestamp to avoid duplicate names of previous files sent use this file format/delimiter csv (comma separated values) file header use these and only these column names in your file cospartnerid , metricmonth , metricabbrev , metricvalue , subpartnerid file footer do not include a footer build the file each row/record in the csv represents a single monthly credit risk metric value each record you send must include entries each of these 4 columns cospartnerid , metricmonth , metricabbrev , metricvalue , and subpartnerid the table below explains the expected column records in further detail note the only optional field is subpartnerid as this might not apply to your program no specific order is required for the metric records submitted if, on a row, the metricmonth , metricabbrev , metricvalue , and subpartnerid is not unique within the file, the first metricvalue listed in the file will persist as the metric of record required metrics the required metrics for cross river bin sponsor card programs may vary depending on your specific program include only the applicable metrics in your file submission and omit any that are not required if you have questions about which metrics apply, please contact your relationship manager sequence/ position column description format 1 cospartnerid your cross river partner id supplied to you by us this id acts as a unique identifier for your program guid (36 characters) 2 metricmonth t he month the credit risk metric record is for this value must be entered as the last day of the month the report covers failing to use the last day of the month might require a resubmission yyyy mm dd (last day of the month) 4 metricvalue the actual credit risk metric supplied as a number (either a count of a metric or a dollar ($) amount) must be a number 5 subpartnerid (optional) identifier for partners who aggregate mulitple programs under them program specific string metric abbreviation catalog metric abbreviation description metric type ($ amount or count) calculation method total apps received tar number of completed applications (number of pending, declined, and approved together should equal the number of total apps received) count monthly total total apps pending tap number of completed applications that are pending count monthly total total apps incomplete tai number of incomplete applications count monthly total total apps declined tad number of declined applications count monthly total total approvals taa number of approved applications count monthly total total subprime approvals (if applicable to your program) tsa number of subprime approvals (less than 660 fico or equivalent) count monthly total total application declines overridden/exceptions tado number of applications initially declined and later judgmentally reviewed and approved (bank may request for exception/overridden reason) count monthly total average limit assigned ala average of all customers' credit limit amounts at end of month $ amount monthly total $ total credit limit/exposure tcl total of all credit limit amounts at end of month $ amount monthly total $ highest credit limit hcl highest credit limit amount at end of month $ amount monthly total $ month end balance (total outstanding/account receivables) meb total balance at end of month $ amount monthly total $ first pay default fpd sum of past due balances from cardholders who failed to make their first payment on or before their scheduled due date and continues to miss that payment (straight roller) $ amount cumulative rolling outstanding value $ balances 30 dpd b3dpd sum of balances 30+ days past due $ amount monthly total $ balances 60 dpd b6dpd sum of balances 60+ days past due $ amount monthly total $ balances 90 dpd b9dpd sum of balances 90+ days past due $ amount monthly total $ balances charged off bco sum of charged off balances $ amount monthly total $ fraud losses tfl sum of fraud losses $ amount monthly total # of total cardholders ntc number of cardholders regardless of status count monthly total number of open cards noc number of open cards (exclude lost or stolen, fraud, closed, or charged off cards) count monthly total number of cards issued nci number of cards issued (both reissued and new cardholders) count monthly total number of auth prohibited cards napc number of cards with status authorization prohibited count monthly total # first pay default nfpd number of cardholders who failed to make their first payment on or before their scheduled due date and continues to miss that payment (straight roller) count cumulative rolling outstanding value # cardholders 30 dpd c3dpd number of cardholders 30+ days past due count monthly total # cardholders 60 dpd c6dpd number of cardholders 60+ days past due count monthly total # cardholders 90 dpd c9dpd number of cardholders 90+ days past due count monthly total # cardholders charged off cco number of cardholder charge offs count monthly total # of reages nor number of re ages (if your program practices re aging, supply the number of re aged accounts completed) count monthly total # of hardship/forbearance enrollments noh number of hardship/forbearance enrollments count monthly total # overlimit cardholders nocl number of accounts over assigned credit limit count monthly total $ all balances overlimit bocl sum of balances over assigned credit limit $ amount monthly total requested credit limit increases approved clia total approved credit limit requests by cardholders count monthly total voluntary credit limit decreases approved clda total approved credit limit decrease requests by cardholder count monthly total requested credit limit increases declined clid number of declined credit limit requests by cardholder count monthly total involuntary credit limit decreases cldd number of declined credit limits conducted by program manager count monthly total proactive credit line increase approved pclia number of approved credit limits initiated by program manager count monthly total # primary account cardholder closures nacl number of primary account cardholder closure requests by cardholder count monthly total # involuntary account closure nicl accounts involuntarily closed due to bad behavior/adverse action count monthly total # total inactive accounts tia accounts without a balance in current and prior cycle count monthly total # pricing changes (increases/decreases) npc number of pricing changes made to an account(s) count monthly total # total monthly refunds nmr number of monthly refunds count monthly total $ total monthly refunds tmr sum of monthly refunds $ amount monthly total # total monthly sales nms number of monthly purchase transactions count monthly total $ total monthly sales tms sum of monthly purchase transactions $ amount monthly total $ total cardholder payments in month tcp sum of all monthly payments $ amount monthly total $ interchange income tii sum of interchange income $ amount monthly total $ fee income tfi sum of fee income (if applicable to program) $ amount monthly total $ interest income tiin sum of monthly interest $ amount monthly total number of cardholder sent to external collection agency coll number of accounts reported to an external collection agency count monthly total funding direct utilized (= on program manager balance sheet) fdu sum of receivables on your program’s balance sheet $ amount monthly total funding partner utilized (= on funding partner’s balance sheet) fpu sum of receivables on any third party balance sheet $ amount monthly total total partner(s) funding utilized $ tpfu sum utilized for all card receivables on a third party balance sheet $ amount monthly total funding partner available $ fpa total presently available on a third party balance sheet for card receivables $ amount monthly total $ recoveries tamr amount recovered from charged off/write off $ amount monthly total # disputes tnd number of disputed transactions count monthly total $ disputes tamd total balance from disputed transactions $ amount monthly total # chargeback tnc number of chargeback transactions count monthly total $ chargeback tamc total balance from chargeback transactions $ amount monthly total sample files partner abcd, inc (no sub partners) the sample below presents the monthly credit risk metric report from a fictitious cross river partner, abcd, inc , partner id 7632bce6 5602 4e2b b7e1 78b6017dc4b2 , for the month of january 2025 file name creditriskmetrics abcd 202503101750 file format csv file name includes partner abbreviation abcd to identify which partner the files belongs to date time stamp 202503101750 refers to the time the file was generated, in this case, march 10th at 17 50, irrespective of the date of the data included (january 2025) this partner has no need to report sub partner data, therefore that optional column is not included partner wxyz, inc (reporting data with sub partners) the sample below presents the monthly credit risk metric report from a fictitious cross river partner, wxyz, inc partner id 65faef45 5602 4e2b b7e1 ae75017dc4b2 , for the month of january 2025 wxyz, inc has two unique sub partners to report data for subp01 and subp02 file name creditriskmetrics wxyz 202503101750 file format csv file name includes partner abbreviation wxyz to identify which partner the files belongs to date time stamp 202503101750 refers to the time the file was generated, in this case, march 10th at 17 50, irrespective of the date of the data included (january 2025) this partner needs to report sub partner data , so they must include the subpartnerid for each record the subpartnerid is a text string the value used must be unique and consistent duplicate value handling duplicate value handling if a new metric file is submitted for a reporting month that has already been received for that month, cross river will rely on the most recently provided version file share method share the csv file monthly upload the file using set up sftp to your /clientcredit subfolder in the sftp site assigned to you if you do not yet have an sftp folder with cross river, contact your cross river, refer to the credit risk data reports /#before you begin section of this page troubleshooting issue resolution you don't know your partner id request your partner id form your {{relationshipmanager}} you are notified by cross river that there's a problem with the csv file if your csv file has problems, cross river will let you know what they are and how to fix them in general, before sending, check these values for validity filename is formatted correctly for each record cos partnerid is correct metricmonth (month end date) is correct and in the correct format metricabbreviation is a valid one from provided list metricvalue is expressed as a number subpartnerid , when applicable, contains a header and value expressed as strings