Bulk FileFormat for Compensatory Fee Appeals

Description

Freddie Mac created the Default Fee Appeal System to enable Servicers to submit appeals for foreclosure time line compensatory fees. The system will permit submission of these appeals via a bulk upload. For each loan submitted in the file, the Servicer can report up to 15 delay reasons. The Servicer can submit appeals for 1 to 1,000 loans in each file. Use of the system to submit appeal data will eliminate the current email transmission method for servicer appeals of foreclosure time line compensatory fees and reduce overall response times for appeal decisioning.

Data Eligibility Criteria

  • All Freddie Mac loans with a pending compensatory fee that has not yet been billed as per Guide section 66.33(c)

File Format

The data file mustbe in Excel format (.xls or .xlsx)

Because the first twolinesare header, the loan data must start on the third line in the file. The detailed format of the data elements is listed in the table below.

No / Data Element / Description / Data Type/Size / Sample / Required/
Required if applicable
1 / FMAC Loan Number / Freddie Mac’s Mortgage loan number / Text(9) / 120393421 / Required
2 / Servicer Loan # / The Servicer’s mortgage loan number / Text(14) / 00012345678912 / Optional
3 / Servicer Family Number / The Servicer Family number associated with the loan / Text(6) / 123456 / Required
4 / Foreclosure Sale Date / The date that the foreclosure sale took place / Date (MM/DD/YYYY) / 11/13/2014 / Optional
5 / Fee Type / The fee type being appealed / Text(9) / Annual/Monthly / Optional
6 / Delay Type1 / The reason for the first reported delay for the loan / Selected from a list of available valid values (see Data Domain section of this document) / Court Delay / Required
7 / Delay Start Date / Date that the reported delayfor delay type 1 (data element6)started / Date (MM/DD/YYYY) / 10/01/2014 / Required
8 / Delay End Date / Date that the reported delay for delay type 1 (data element6)ended / Date (MM/DD/YYYY) / 11/30/2014 / Required
9 / Delay Comments / Servicer comments regarding delaytype 1 (data element 6) / Text (1000char limit) / The foreclosure sale was completed within the FHLMC time line. / Required
10 / Delay Type2 / The reason for the second reported delay for the loan / Selected from a list of available valid values (see Data Domain section of this document) / Court Delay
11 / Delay Start Date / Date that the reported delay for delay type 2 (data element 10) started / Date (MM/DD/YYYY) / 10/01/2014 / Required, if applicable
12 / Delay End Date / Date that the reported delay for delay type 2 (data element 10) ended / Date (MM/DD/YYYY) / 11/30/2014 / Required, if applicable
13 / Delay Comments / Servicer comments regarding delaytype 2 (data element 10) / Text (1000 char limit) / The foreclosure sale was completed within the FHLMC time line. / Required, if applicable
14 / Delay Type 3 / The reason for the third reported delay for the loan / Selected from a list of available valid values (see Data Domain section of this document) / Court Delay
15 / Delay Start Date / Date that the reported delay for delay type 3 (data element 14) started / Date (MM/DD/YYYY) / 10/01/2014 / Required, if applicable
16 / Delay End Date / Date that the reported delay for delay type 3 (data element 14) ended / Date (MM/DD/YYYY) / 11/30/2014 / Required, if applicable
17 / Delay Comments / Servicer comments regarding delaytype 3 (data element 14) / Text (1000 char limit) / The foreclosure sale was completed within the FHLMC time line. / Required, if applicable
18 / Delay Type4 / The reason for the fourth reported delay for the loan / Selected from a list of available valid values (see Data Domain section of this document) / Court Delay
19 / Delay Start Date / Date that the reported delay for delay type 4 (data element 18) started / Date (MM/DD/YYYY) / 10/01/2014 / Required, if applicable
20 / Delay End Date / Date that the reported delay for delay type 4 (data element 18) ended / Date (MM/DD/YYYY) / 11/30/2014 / Required, if applicable
21 / Delay Comments / Servicer comments regarding delaytype 4 (data element 18) / Text (1000 char limit) / The foreclosure sale was completed within the FHLMC time line. / Required, if applicable
22 / Delay Type5 / The reason for the fifth reported delay for the loan / Selected from a list of available valid values (see Data Domain section of this document) / Court Delay
23 / Delay Start Date / Date that the reported delay for delay type 5 (data element 22) started / Date (MM/DD/YYYY) / 10/01/2014 / Required, if applicable
24 / Delay End Date / Date that the reported delay for delay type 5 (data element 22) ended / Date (MM/DD/YYYY) / 11/30/2014 / Required, if applicable
25 / Delay Comments / Servicer comments regarding delaytype 5 (data element 22) / Text (1000 char limit) / The foreclosure sale was completed within the FHLMC time line. / Required, if applicable
26 / Delay Type6 / The reason for the sixth reported delay for the loan / Selected from a list of available valid values (see Data Domain section of this document) / Court Delay
27 / Delay Start Date / Date that the reported delay for delay type 6 (data element 26) started / Date (MM/DD/YYYY) / 10/01/2014 / Required, if applicable
28 / Delay End Date / Date that the reported delay for delay type 6 (data element 26) ended / Date (MM/DD/YYYY) / 11/30/2014 / Required, if applicable
29 / Delay Comments / Servicer comments regarding delaytype 6 (data element 26) / Text (1000 char limit) / The foreclosure sale was completed within the FHLMC time line. / Required, if applicable
30 / Delay Type7 / The reason for the seventh reported delay for the loan / Selected from a list of available valid values (see Data Domain section of this document) / Court Delay
31 / Delay Start Date / Date that the reported delay for delay type 7 (data element 30) started / Date (MM/DD/YYYY) / 10/01/2014 / Required, if applicable
32 / Delay End Date / Date that the reported delay for delay type 7 (data element 30) ended / Date (MM/DD/YYYY) / 11/30/2014 / Required, if applicable
33 / Delay Comments / Servicer comments regarding delaytype 7 (data element 30) / Text (1000 char limit) / The foreclosure sale was completed within the FHLMC time line. / Required, if applicable
34 / Delay Type8 / The reason for the eighth reported delay for the loan / Selected from a list of available valid values (see Data Domain section of this document) / Court Delay
35 / Delay Start Date / Date that the reported delay for delay type 8 (data element 34) started / Date (MM/DD/YYYY) / 10/01/2014 / Required, if applicable
36 / Delay End Date / Date that the reported delay for delay type 8 (data element 34) ended / Date (MM/DD/YYYY) / 11/30/2014 / Required, if applicable
37 / Delay Comments / Servicer comments regarding delaytype 8 (data element 34) / Text (1000 char limit) / The foreclosure sale was completed within the FHLMC time line. / Required, if applicable
38 / Delay Type9 / The reason for the ninth reported delay for the loan / Selected from a list of available valid values (see Data Domain section of this document) / Court Delay
39 / Delay Start Date / Date that the reported delay for delay type 9 (data element 38) started / Date (MM/DD/YYYY) / 10/01/2014 / Required, if applicable
40 / Delay End Date / Date that the reported delay for delay type 9 (data element 38) ended / Date (MM/DD/YYYY) / 11/30/2014 / Required, if applicable
41 / Delay Comments / Servicer comments regarding delaytype 9 (data element 38) / Text (1000 char limit) / The foreclosure sale was completed within the FHLMC time line. / Required, if applicable
42 / Delay Type10 / The reason for the tenth reported delay for the loan / Selected from a list of available valid values (see Data Domain section of this document) / Court Delay
43 / Delay Start Date / Date that the reported delay for delay type 10 (data element 42) started / Date (MM/DD/YYYY) / 10/01/2014 / Required, if applicable
44 / Delay End Date / Date that the reported delay for delay type 10 (data element 42) ended / Date (MM/DD/YYYY) / 11/30/2014 / Required, if applicable
45 / Delay Comments / Servicer comments regarding delaytype 10 (data element 42) / Text (1000 char limit) / The foreclosure sale was completed within the FHLMC time line. / Required, if applicable
46 / Delay Type11 / The reason for the eleventh reported delay for the loan / Selected from a list of available valid values (see Data Domain section of this document) / Court Delay
47 / Delay Start Date / Date that the reported delay for delay type 11 (data element 46) started / Date (MM/DD/YYYY) / 10/01/2014 / Required, if applicable
48 / Delay End Date / Date that the reported delay for delay type 11 (data element 46) ended / Date (MM/DD/YYYY) / 11/30/2014 / Required, if applicable
49 / Delay Comments / Servicer comments regarding delaytype 11 (data element 46) / Text (1000 char limit) / The foreclosure sale was completed within the FHLMC time line. / Required, if applicable
50 / Delay Type12 / The reason for the twelth reported delay for the loan / Selected from a list of available valid values (see Data Domain section of this document) / Court Delay
51 / Delay Start Date / Date that the reported delay for delay type 12 (data element 50) started / Date (MM/DD/YYYY) / 10/01/2014 / Required, if applicable
52 / Delay End Date / Date that the reported delay for delay type 12 (data element 50) ended / Date (MM/DD/YYYY) / 11/30/2014 / Required, if applicable
53 / Delay Comments / Servicer comments regarding delaytype 12 (data element 50) / Text (1000 char limit) / The foreclosure sale was completed within the FHLMC time line. / Required, if applicable
54 / Delay Type13 / The reason for the thirteenth reported delay for the loan / Selected from a list of available valid values (see Data Domain section of this document) / Court Delay
55 / Delay Start Date / Date that the reported delay for delay type 13 (data element 54) started / Date (MM/DD/YYYY) / 10/01/2014 / Required, if applicable
56 / Delay End Date / Date that the reported delay for delay type 13 (data element 54) ended / Date (MM/DD/YYYY) / 11/30/2014 / Required, if applicable
57 / Delay Comments / Servicer comments regarding delaytype 13 (data element 54) / Text (1000 char limit) / The foreclosure sale was completed within the FHLMC time line. / Required, if applicable
58 / Delay Type14 / The reason for the fourteenth reported delay for the loan / Selected from a list of available valid values (see Data Domain section of this document) / Court Delay
59 / Delay Start Date / Date that the reported delay for delay type 14 (data element 58) started / Date (MM/DD/YYYY) / 10/01/2014 / Required, if applicable
60 / Delay End Date / Date that the reported delay for delay type 14 (data element 58) ended / Date (MM/DD/YYYY) / 11/30/2014 / Required, if applicable
61 / Delay Comments / Servicer comments regarding delaytype 14 (data element 58) / Text (1000 char limit) / The foreclosure sale was completed within the FHLMC time line. / Required, if applicable
62 / Delay Type15 / The reason for the fifteenth reported delay for the loan / Selected from a list of available valid values (see Data Domain section of this document) / Court Delay
63 / Delay Start Date / Date that the reported delay for delay type 15 (data element 62) started / Date (MM/DD/YYYY) / 10/01/2014 / Required, if applicable
64 / Delay End Date / Date that the reported delay for delay type 15 (data element 62) ended / Date (MM/DD/YYYY) / 11/30/2014 / Required, if applicable
65 / Delay Comments / Servicer comments regarding delaytype 15 (data element 62) / Text (1000 char limit) / The foreclosure sale was completed within the FHLMC time line. / Required, if applicable
66 / Total Delay Days Requested / Calculated value – sums the number of days (start to end) for all delay types

Data Domain

The input file/data must contain exactly the same values as defined in the following data domain in order to be accepted.

Delay Type(Required for Data Element #6 and Required as applicable for Data Elements #10, 14, 18, 22, 26, 30, 34, 38, 42, 46, 50, 54, 58, 62) – User must select one of the values from the list below

  • Appeal of Loan Modification
  • Approved Short Sale
  • Attorney Delays
  • Attorney Termination Delays
  • Chapter 11 Bankruptcy
  • Chapter 12 Bankruptcy
  • Chapter 13 Bankruptcy
  • Chapter 7 Bankruptcy
  • Contested Fcl/Litigation
  • Court Delay
  • Designated Counsel Postponement
  • Designated Counsel Protection
  • Distressed Property
  • HAMP in Review
  • HAMP Trial Plan
  • Interim Servicing Delay
  • Legislative Change
  • Mediation
  • Military Indulgence
  • Other
  • Postponement of Referral to Foreclosure
  • Probate
  • Process Delay
  • REO Rollback
  • Repurchase
  • Restart Delay
  • Streamlined Mod Trial Plan
  • Standard Mod Trial Plan
  • Third Party Sales Sold for Total Debt
  • Title Issue
  • Transfer of Servicing
  • Unemployment Forbearance

Data File Naming Convention

The Servicer should use a unique file name for each file they transmit to Freddie Mac. The file name should not contain any of these special characters: \, /, *, ?, <, >, |

Appendix

Sample File*

A sample of a data file is copied below for reference.

*Mocked up data

Page 1 of 8