FNMA 3.2 Files Explained: Moving 1003s Into Calyx Point Without Re-Keying
Short answer: An FNMA 3.2 file (.fnm) is a fixed-width text format for 1003 loan applications that Calyx Point, Encompass, and most LOS platforms import directly — borrower, employment, assets, and liabilities included. PathIQ collects the 1003 once and exports .fnm, so you move applications between systems without re-keying a single field.
If you've ever re-typed a borrower's SSN, employer, and asset accounts from a PDF into Calyx Point at 9pm because the LOS doesn't import PDFs, this post is for you.
What is an .fnm file?
The FNMA 3.2 file format (.fnm) is a fixed-width text format Fannie Mae standardized in the 1990s for transmitting 1003 loan applications between systems. It is, technically, a text file. Open it in Notepad and you see records like:
TXX 0001003 ...
ENV 0001
LAP 0001 ...
BIO 0001 SMITH JOHN A 123-45-6789 ...
Each line is a record type, each character position is a known field, and the whole file represents one or more loan files. Calyx Point, Encompass, and most LOS platforms will import a 3.2 file directly — borrower data, co-borrower data, employment, assets, liabilities, the works.
Why does the .fnm export save you time?
The two LO time-sinks for a wholesale multifamily LO are:
- Underwriting the deal.
- Re-keying the 1003 into the LOS.
PathIQ removes both. You collect the 1003 once — either via the in-app wizard with the borrower in the room, or via a shared client link (single-use, MFA-gated) the borrower fills out themselves. You then export .fnm and import directly into Calyx Point. Zero re-keying.
What fields PathIQ writes
Our .fnm exporter populates the records most LOS platforms care about: TXX (transmittal), ENV (envelope), LAP (loan application primary), BIO (borrower), CBI (co-borrower), EMP (employment), INC (income), AST (assets), LIA (liabilities), PRO (property), and the demographic / declarations records. Optional records for HMDA reporting are included when the borrower completes the demographics step.
What it doesn't replace
The .fnm file is a starting state. Your LOS still owns:
- AUS submission (DU/LP)
- Disclosures
- Appraisal ordering
- Closing disclosure preparation
- Funding
It's a hand-off, not a replacement. The point is to skip the typing, not the licensed work.
Sanity check after import
After you import into Calyx, always sanity-check four things: (1) borrower SSN, (2) employer name spelling, (3) liabilities count and balance, (4) subject property address. If those four match, the rest of the import is reliable.
Frequently asked questions
What is an FNMA 3.2 (.fnm) file?
It's a fixed-width text format Fannie Mae standardized in the 1990s to transmit 1003 loan applications between systems. Each line is a record type and each character position is a known field, so an LOS can read borrower, employment, asset, and liability data directly.
Can Calyx Point import a .fnm file directly?
Yes. Calyx Point, Encompass, and most LOS platforms import a 3.2 file directly, pulling in borrower, co-borrower, employment, assets, and liabilities without manual entry. That's the whole point — you skip re-keying the application.
What fields does PathIQ write to the .fnm export?
PathIQ populates the records most LOS platforms care about: TXX, ENV, LAP, BIO, CBI, EMP, INC, AST, LIA, PRO, and the demographic/declarations records. Optional HMDA reporting records are included when the borrower completes the demographics step.
Does the .fnm export replace my LOS?
No. The file is a starting state, not a replacement. Your LOS still owns AUS submission (DU/LP), disclosures, appraisal ordering, closing disclosure prep, and funding. It's a hand-off that skips the typing, not the licensed work.
What should I check after importing?
Sanity-check four things: borrower SSN, employer name spelling, liabilities count and balance, and the subject property address. If those four match, the rest of the import is reliable.