Quick Links

  • More Links

Contact Us

Loan Data

Removing secure data from the REG-Loans or ALERT file before uploading

Unknown Comic As we've mentioned in previous posts we understand that the detail loan file format #1 contains sensitive customer data.  If you upload a file to us with customer sensitive data we delete this information right away, we don't want this information either.  Part of our agreement with you is to keep information confidential.

For those of you that are still concerned about about sending the data file we can offer you a new program utility that deletes the sensitive data from the RegLoans (or ALERT) file before you upload it to us.  We call it the "ALERT File Scrubber".  It's a simple program that you download and run on your computer.  It reads in your original data file, deletes (or scrubs) the sensitive data fields, and saves a new clean version of the file that you can upload to us.

Here is the URL:  (you should probably right-click and choose "Save Target as...")

http://www.olsonresearch.com/blogresources/ALERTFileScrubber.exe

The program will save a "scrubbed" version of your original loan file back into the same folder with the same name and a new extension ".ScrubbedForORA".  This is the file you'll want to upload.

If you have any questions about using this program please leave a comment here, email, or call us.  Contact information is in the margin.

Data File Specifications

Here are links to our suggested data file formats:

Once you have created a data file, you may upload it to us using our Secure file upload (sign-in required) area.

Wait!, there is sensitive data in this loan file!

Yes, if you are choosing to send us the "Format #1: Interagency (ALERT) format" there is indeed sensitive customer data in the file.  And to be blunt, we don't want you to send us the sensitive data either.  If you are going to send us this file please use the ALERT data scrubber program.  In fact, if you send us the ALERT file without the sensitive data cleaned from it, the first thing we're going to do is permanently DELETE the sensitive data because we don't want the security hassle.

If you can't send us the ALERT data file, then you will need to send us data in one of the other two formats.

The other "good-security" practice you should follow is to upload this file to us via our secure server.  Don't email us the file (many of you still try to!)  This quarter if you email us the file, you'll receive a polite email response back asking you to upload the file instead.

I know it's a change, but I think you'll agree, it's a change for the better.

Why are you requiring us to provide loan detail?

I've been asked this question by a handful of clients over the past month.  Starting with 4th quarter 2007 processing we are requiring clients to provide us with loan detail information (related blog post here).  Why the change?  After all we've been producing our A/L BENCHMARKS reports using call report data & supplementary assumptions for years.

The biggest reason for the change is examiner and auditor pressure.  Ever since "model validation" became a hot button issue in a/l modeling we've been asked include detail loan data in our analysis.  Until now it's something we did on a custom, as requested, basis.  But there has been mounting pressure to always include it.  Many thought it to be a logical next step because we're already including security detail data (from bond accounting systems).

But up until now we've lacked a specific standard file format to use.  We've always attempted to base our service on accepted modeling standards and data sources (hence the name "benchmarks").  Fortunately for us the FDIC, Fed, OTS and most states approved a standard loan data definition back in 2002 to be used for off site examinations.  This standard has had 5 years to "sink-in" and every bank is capable of producing such a file.

So now instead of allocating the maturity and repricing information from your call report to generate cash flow structures, we can model every loan individually (just like we do for your bond portfolio).  Examiners & auditors are happy...

Loan detail file FAQs

Here is some helpful FAQ regarding the loan data file.  This FAQ was originally published by the Louisiana Office of Financial Institutions addressing questions about the Interagency Loan File Format.

Are fields considered one row and terminated by 1 carriage-return line-feed sequence?
Yes.

Will all the fields on one line comprise one loan detail record?
Yes.

Should we include home equity loans in the file?
The file should contain all the bank’s loans regardless of type. This would include commercial as well as consumer loans.

Should we include zero-balance loans?
That depends upon the loan. We do want to see open lines of credit where the bank is obligated to advance funds in the future. These might show zero for an outstanding balance, but would show the full amount of the commitment in another field (undisbursed commitment availability). Examples of these types of loans that might be carrying a zero balance would credit card lines, commercial lines of credit, standby lines of credit and home equity lines. On the other hand, we do not want to see a zero-balance loan record that's simply an artifact from a loan that's been paid in full. If these were included in the file, they would show zero for both fields since there is no longer a legal obligation on the bank’s part to re-advance funds.

For the field called "charge off amount", do you want all old charged off loans in the interagency file?
If a loan has been charged off in full, it's a zero-balance loan as described in the answer above and it should not be in the file. We have seen some files where these loans show an outstanding balance and a like number in the charge-off amount. That creates a problem since at first glance these appear to be active
loans. It's important to understand that we will try to reconcile this trial balance to the amount shown for loans on the bank's general ledger using the total
from the outstanding balance field. Any loan that is listed in the file that isn't an active and current relationship that's properly carried as an asset of the bank should not be showing a current balance other than zero. In addition to inhibiting our ability to balance the ledger, these lines will distort the past due and summary reports built into our tools.  If the bank has a note with a partial charge off, the current balance net of the charge off would show up in the outstanding balance since that portion of the note is still active. The charge off amount would be listed in the "charge off" column. If you have already mapped and distributed the format to your customers and you have old charge offs in the file, no change is needed as long as the amount in "balance outstanding" for these notes is zero.

In those instances where the bank sells a portion of a note, should we report the balance as balance outstanding net of the sold amount?
Since we’re interested in balancing "outstanding balance" to the bank’s call report RC-C, it should be net of any amount sold. For example, if a bank makes a loan for 100,000 and then sells 25,000 to another institution, the record for that note should reflect the following subsequent to the sale:
balance outstanding = 75000.00
participation indicator=S
amount sold=25000.00
original amount sold=25000.00
Please note the "amount sold" will decrease as payments are made to the participating bank(s). If your system is incapable of linking the participation to an individual note, then you could report the amount sold as a negative note. In the example above, the amount in outstanding balance for the original note would be 100000.00, and the amount in outstanding balance for the “participation” note would be –25000.00.   In addition, you would need to populate the record for the negative note with some key information so that we could tie it to the underlying borrower. This would include:
Note number (this could be a dummy number, or a number tied to the participation) and Borrower ID.  Please do not populate other fields if you use the negative-note option.

Our loan products can have up to 10 rates, indices and margins. How do you want to address this in the field for interest rate, index and margin?
We envision that this file will be presenting information on a loan-by-loan basis (i.e., one loan per line). That being the case, we would like to see the information/indices related to each loan. While we understand there could be many indices in use, we don’t expect that more than one will apply to an individual note.

Please give further definition of field "Amortizing/Non-Amortizing status"
We’re looking to see if amortization has been suspended. This would be most common on consumer loans where there has been an agreement by the bank to suspend principle payments for specified period of time.

Several fields in the file format document have been identified so far as unavailable or null for our system, and they are not identified as required fields for population.  Do you have any tolerance for the number of fields that are not populated on the file?
A few of the fields are absolutely required (Note Number, Balance, Rate, Maturity Date).  If other fields are unavailable, please leave those fields blank.  Keep in mind though that missing data will impact your analysis (for example, not providing an index and spread for a variable rate loan)

Is the file to be sorted in any manner, i.e. branch, note type, officer, etc.?
Sort is not important to us since our tools will sort the data in the manner we need once we import the file.

Is there a particular method for transmission and data encryption that is expected?
Yes, you must upload this file via our secure (https://) server.  DO NOT EMAIL THIS FILE TO US.

What should we report in "next payment due" when the loan is delinquent?
Show the due date of the next payment. This will be in the past if the loan is delinquent.

What should we report in "payment frequency" when the note has a mixed payment structure (for example, interest monthly with principle quarterly)?
This is a 10-character alpha field. Please describe the payment structure as "mixed" or "variable."

On a related note, what should we report in "payment amount" for loans with mixed payments?
Report the amount of the next expected payment if known.

How should we report negatively amortizing loans in the "amortizing/non-amortizing" field?
Answer "no.”

What should we report in "date of last payment" if the last payment wasn't a full payment?
Report the date of the last payment even if it wasn't a full payment. We are looking for activity on the line.

How should we report non-valid dates?
In some systems, non-valid dates are used to identify a specific event (i.e., 6-31 for quarter end).  In those cases, please convert to a real date. Report all other non-valid dates as is, since they probably reflect a data integrity problem that we will want to investigate.

New detail loan data file

We've mentioned some new things coming this quarter (4th quarter 2007).  One of them is the new standard loan detail file.  For some time we've been under tremendous pressure from examiners and auditors to include in our model detail loan data.  We have always been able to accommodate this request.  We've able to accept loan detail data into A/L BENCHMARKS for the past seven years.  The difference is now we're going to require it.

While, many of you have provided us with additional maturity and repricing information about your portfolios via the Service Kit, we'll no longer accept this additional information.  In lieu of that, we're going to ask that you send us a detail loan data file in one of three different formats.  Having loan by loan detail will allow us to more effectively capture the nature your bank's interest rate risk exposure.  Click here to learn more about the file formats or you can click on any of the headlines listed on the right.

Loan detail file formats

You can provide loan detail data for A/L BENCHMARKS in one of three different formats:

Differences between file formats:






Contains:

Format #1: Interagency (ALERT)
DataIcon

Format #2: Basic

CSVIcon

Format #3: Expanded

CSVIcon

- sensitive customer info yes no no
- rate floor info no yes yes
- next reset date no yes yes
- interest only indicator no yes yes
- balloon date no yes yes

It should be pretty obvious that we would like you to send us the data using the #2 or #3 format.  These file layouts don't contain any sensitive customer data (like Social Security Numbers, etc.)  These formats also provide us with some very informative additional fields.  However, in order to make it easier on you, we can accept the "#1 - Interagency (ALERT) file" format.  You have probably already had to provide this type of file to your examiners so it should be easy to produce. 

If you send us the Interagency file don't forget to use the ALERT File Scrubber utility to remove sensitive data from the file!

Upload your loan file to us here.