A loan file stacking order is the fixed sequence documents follow when a file goes to underwriting. The usual order puts the submission sheet and application first, then credit, income, bank statements and assets, property documents, disclosures and finally any conditions. Following the receiving lender's order lets the underwriter read the file once without hunting for pages.
What is a loan file stacking order?
A loan file stacking order is a numbered list of document groups that tells the person assembling a submission which papers go first, second and last. The lender or investor receiving the file usually publishes it. Brokers and processors who send to many lenders often keep a house order and switch to the lender's version when one exists.
The point of the order is speed and trust. An underwriter who opens a file and finds the 1003 on top, the credit report next and the income package after it can start reading at once. A file sorted by upload date forces the reviewer to rebuild it, and that rebuild time adds to the queue. Reviewers who track how long underwriting turn times run and what drives them often find that poorly assembled files sit longer before anyone touches them.
The order is also a quiet checklist. When each group has a slot, an empty slot shows up before submission instead of as a condition three days later.
A sample loan file stacking order index
A workable index groups documents by the question each answers: who is borrowing, can they pay, what are they buying and what has been disclosed. The table below is an illustration, not any lender's required order. Section numbers and contents are examples you can adapt.
| Section | Documents (example) | Note |
|---|---|---|
| 1 | Submission cover sheet, loan summary, program and pricing lock | One page that states the ask |
| 2 | Signed loan application (1003) and borrower authorizations | Latest signed version only |
| 3 | Credit report, letters of explanation for inquiries or late payments | Explanations sit next to the item they explain |
| 4 | Income: pay stubs, W-2s, tax returns, or the bank statement income worksheet | Worksheet on top, sources behind it |
| 5 | Bank statements, oldest month first, each account kept together | All pages of each month |
| 6 | Assets and reserves: retirement, brokerage, gift letters, earnest money proof | Source large deposits here |
| 7 | Property: purchase contract, appraisal, title, insurance | Contract addenda in date order |
| 8 | Disclosures and compliance documents | Initial and revised sets |
| 9 | Conditions and responses | Each response labelled with its condition number |
Two habits make this index work. Put the summary or worksheet on top of each group, so the reviewer sees the conclusion before the evidence. Keep each group in one direction of time, so nobody has to guess whether page 3 is March or May.
Where do bank statements go in the loan file stacking order?
Bank statements usually follow the income section, because on a bank statement loan they are the income evidence, and on a full-documentation loan they back the assets. Keep each account together, place months from oldest to newest, and include every page of every month, even pages that say only "this page intentionally left blank."
A self-employed file with a business account and a personal account needs two runs of statements, each with a short cover note naming the account, the holder and the months covered. Put any letter explaining a large deposit or a transfer between the accounts directly after the statement that shows it. An underwriter reading month seven should find the explanation for month seven's deposit right there.
If the file uses a deposit analysis, place the summary in front of the statements. TrueBankFlow builds monthly deposit totals and averages from the statements, and each figure links back to the statement line behind it, which gives the underwriter a summary page and a way to check it.
Stacking order mistakes that send a file back
Most stacking order mistakes come from mixing versions or splitting a document across groups. They rarely cause a decline. They cause a suspense or a request to resubmit, which costs a review cycle and sends the file to the back of the line.
Watch for these:
- Old and new applications together. Only the latest signed 1003 belongs in section 2. Earlier drafts confuse which figures were used.
- Partial statements. Missing pages are the most common reason a statement month is rejected.
- Explanations filed far from the item. A letter about a gap in employment sitting behind the appraisal is easy to miss.
- Unlabelled condition responses. A response that does not name its condition may be read as new, unrequested material.
- Duplicates. Three copies of the same pay stub make the reviewer check whether they differ.
Who fixes these depends on how your team splits the work. The difference between a loan processor and an underwriter sets out who owns assembly and who owns the decision, and stacking order belongs firmly with the processor.
When the lender's stacking order replaces your own
A lender's published order always wins over a house order, because its underwriters are trained to read files that way. Wholesale lenders, investors and correspondent buyers often post their order with the submission forms. Before sending, compare your sections to theirs and move documents, rather than adding a cover note that explains the difference.
Business and SBA files are the main case where a mortgage-style order does not fit. They add business tax returns, entity documents, a debt schedule, projections and collateral details that have no slot in a home loan index. Lenders in that space tend to follow the agency's own forms. How SBA 504 loan underwriting reviews a project shows the documents that file is built around.
Changes after submission follow the same order. When an updated statement or a new condition response arrives, insert it into its section and note the date, instead of stacking it on top of the file. If your team wants a summary page for the statements section before its next submission, you can request early access to TrueBankFlow.