File your TLR with confidence, not spreadsheets.

CDFI Transaction Level Report (TLR) reporting is the annual submission of loan-level data, including terms, borrower characteristics, project details, and geography, required from FA, NACA, CDFI RRP, and CDFI ERP award recipients. It’s typically due six months after an organization’s fiscal year end and is submitted through the CDFI Fund’s AMIS system. The Mortgage Office captures this data directly on each loan file so it’s ready to export when the deadline hits.

You must report all new loans and investments originated during the reporting period, not just those tied to a particular FA award. This is a common point of confusion that leads to incomplete filings. The Mortgage Office lets you flag any loan for TLR inclusion with a single checkbox, or set that flag by default through loan templates so new originations are never missed. 

Yes, the CDFI Fund allows CDFIs to use any software to track and compile TLR data, as long as the system captures all required AMIS data points. The Mortgage Office houses transaction identifiers, borrower and investor profiles, and impact data in a dedicated CDFI section on each loan file, then exports an AMIS-ready XML file in a couple of clicks.

The full-length TLR includes complete compliance and performance data, including program outcomes and impact metrics, while the abbreviated TLR excludes those outcome fields. Certified CDFIs can only use the abbreviated version if they have no active Assistance Agreement under FA, NACA, ERP, or RRP. Most CDFIs with active awards will need the full-length report, which is why The Mortgage Office captures impact data on every flagged loan by default. 

Each loan file has a dedicated CDFI section that houses transaction identifiers, borrower and investor profiles, transaction status, and project impact data. You flag a loan for TLR inclusion with a single checkbox, and reporting fields can be set by default through loan templates. This keeps every data point tied directly to the loan instead of scattered across spreadsheets.

Run the built-in validation export in The Mortgage Office, which generates an audit report flagging any missing or invalid fields before you file. This catches errors before the CDFI Fund does, reducing the risk of a rejected or incomplete submission. Correcting flagged records at this stage is far faster than reconciling issues after certification.

The Mortgage Office generates an AMIS-ready XML file for direct upload to the CDFI Fund’s system, or the same data as an Excel export for deeper analysis. The Excel option supports any date range, including multi-year lookbacks, which is useful for audits or historical review. Both exports pull from validated loan-level data, so the figures match what’s on file.

Common causes include decimal values in amount fields, missing or mismatched address records, incomplete borrower or geography data, and uncertified records after upload. Address mismatches are a frequent issue since every TLR entry needs a corresponding TLR Address record. Running a validation audit before export, as The Mortgage Office does, catches most of these issues before they reach AMIS.

If certification isn’t completed correctly, the CDFI Fund treats the report as not submitted, even if the data was uploaded. Only one certified TLR is required per fiscal year, so this step is critical to close out the filing. Keeping validated, exportable data on hand makes it easier to correct and re-certify quickly if this happens.

The Mortgage Office categorizes loans by program, grant, and grant year, and lets you filter your portfolio instantly using saved smart views. Each funding source is tracked separately with no commingling, which satisfies grant and audit requirements. This makes it possible to report program income and outstanding balances by fund, grant, or grant year on demand

Funders and auditors require that program income, balances, and activity be reportable by individual fund or grant, not blended together. Commingled data creates reconciliation headaches and can raise red flags during an audit. The Mortgage Office tracks each grant and funding source independently, so you can produce a clean, isolated report for any single fund on request.

Keep TLR data current on every loan throughout the year rather than compiling it manually before the deadline. Set reporting flags by default through loan templates so new originations are captured automatically, and run validation checks periodically instead of only right before filing. This turns TLR season from a multi-day fire drill into a few clicks in The Mortgage Office. 

Yes, every payment, edit, and change to a loan file is recorded in the events journal, creating a complete audit trail. This supports both CDFI Fund inquiries and internal or third-party audits, since you can show exactly when and how a data point changed. Combined with validation before export, this audit trail helps protect your certification status.

TLR data is now used both for annual compliance reporting and for the CDFI Fund’s revised certification assessments. Inaccurate or late filings can put your certification, and the funding tied to it, at risk. Because The Mortgage Office validates records before export, you reduce the chance of submitting data that could trigger certification review issues.

Yes, The Mortgage Office exports TLR data to Excel for any date range, including multi-year lookbacks, so historical records remain accessible. This is useful if the CDFI Fund requests clarification on a prior filing or if you need to rebuild a report during an audit. Since data lives on the loan file rather than a one-time spreadsheet, nothing is lost between reporting cycles.