Default Reporting Application (DRA)

The Default Reporting Application (DRA) is where foreclosure and bankruptcy attorneys report case events on Fannie Mae loans. Quandis built DRA and runs it for Fannie Mae. It accepts the same default reporting event files that firms already produce for Fannie Mae’s legacy system, so a firm can usually start reporting without changing what its case management system exports.

Four ways to submit

Channel	Best for	What you send
Drag-and-drop upload	Firms that export an events file and upload it by hand	A legacy events file, dropped on the DRA landing page
sFTP	Scheduled, hands-off delivery from your own systems	The same events files, placed in your firm’s sFTP folder
API	Case management systems that report as events happen	Event rows (delimited text or XML) in an HTTPS POST
Web data entry	One-off events, corrections, and small firms	Individual events, entered in the DRA web interface

Every channel ends in the same place: an import file that is queued, processed in near-real time, and kept with a row-by-row log. Files submitted by sFTP, upload, or API all appear on the Import Files tab, so you can always see what came in and what failed.

Key concepts

Concept	What it means
Event	One reported fact about a case, identified by a Fannie Mae business event code. For example, E0130 is Foreclosure Referral Package received by Attorney.
Foreclosure and bankruptcy	DRA groups events into the foreclosure or bankruptcy they belong to, keyed by your firm, the Fannie Mae loan, and your attorney file number (foreclosure) or bankruptcy case number.
Delay	An event that starts or ends a delay on a loan, with a delay type, start date, projected end date, and details.
Legacy events file	A file in Fannie Mae’s legacy default reporting layout: one EVENT row per event, with up to 110 columns. HEADER and FOOTER rows are optional in DRA.
Import file	One submission, from any channel. It records the file you sent, the number of events, and a log of any rows that failed.
Derived status	The current status of a foreclosure or bankruptcy, worked out from the dates on its events rather than the order the rows arrived in.

Loan and servicer details come from Fannie Mae’s own data feeds. If you send servicer fields such as the servicer code, name, or loan number, DRA keeps them on the event but shows Fannie Mae’s values on the loan summary.

Environments

Environment	Purpose
UAT	User acceptance and integration testing. Prove your files, sFTP connection, or API calls here first.
Production	Live reporting to Fannie Mae.

sFTP delivery uses one host for both environments, with a separate account for each. Host names are in the Developer view.

Getting an account

Fannie Mae, not Quandis, grants access to DRA:

1. User accounts. Fannie Mae provisions one or more user administrators at your firm, who then add and manage your firm’s users. This is the same Technology Manager process firms use for other Fannie Mae applications such as P360. A user who already has a Technology Manager account can be granted DRA access by your user administrator.
2. No user administrator yet? Email the DRA team at Fannie Mae, dra_support@fanniemae.com, with your firm name, two main points of contact (name, direct phone number, and email for each), and the ways you plan to submit: sFTP, API, spreadsheet upload, or direct entry.
3. Automating (sFTP or API)? Request an automation account from the same address. Add the automation user name you want (for example, integrations@yourlawfirm.com) and, for sFTP, the IP address ranges you will connect from. See Get an automation account.

For UAT access and sFTP setup, contact Quandis at fannie.support@quandis.com.

Choose your view

Use the buttons under the page title. End user covers uploading events files, entering individual events, and reading import results in the web interface. Developer covers sFTP delivery, file naming rules, the events file layout, and API submission.

For a summary of DRA and how it compares with ADR for Freddie Mac loans, see the DRA product page. DRA imports run on the same engine described in Imports.