Create a document request script for self-employed borrowers

Self-employed borrowers often receive a document request that assumes they know which pages the lender needs. The borrower sends a full tax return, the processor finds the wrong schedule, and the request starts again. A written script reduces that loop by naming the documents and explaining why each one matters. The script also gives the processor a consistent way to explain the request when the borrower calls.

Start with the return, not the folder

Ask for the complete personal federal tax return for the most recent year, including all schedules and statements. A borrower may send only the Form 1040 and leave out the schedules that support the income. The script should say that every page is needed, even the pages that look blank. A page count or a checklist at the top of the request helps the borrower confirm that the packet is complete.

Explain that the lender may also need the prior year. Two years of returns are common for self-employed income, but the exact requirement depends on the loan program and the lender. The script should say which years are required for this file instead of asking the borrower to guess. Name the years explicitly in the request so the borrower does not send an older return that the lender cannot use.

Name the business returns and entity records

Ask for the business federal tax returns, including all schedules, forms, and statements. For a partnership or an S corporation, the borrower may need to provide the K-1s that connect the business income to the personal return. The script should name the entity type and the documents that match it. If the borrower owns more than one business, ask for the returns for each entity that supports the income used in the file.

Ask for the entity formation documents and any document that shows the borrower's ownership share. A name change, a merger, or a new operating agreement can explain a difference between the tax return and the application. The borrower should send the current version, not an old copy from a prior year. A short note about the ownership percentage helps the processor compare the application with the entity records.

Request a profit and loss statement when the file needs one

A profit and loss statement may be required when the most recent tax return is not recent enough or when the income changed after the return was filed. Ask for a statement that covers the period the lender requests and that shows revenue, expenses, and net income. The borrower should sign and date it. Ask the borrower to include the same period for the profit and loss statement and the bank statements used to support it.

Explain that the statement should match the business records. A statement prepared only for the loan can raise a question if it does not reconcile with the tax return or the bank statements. The script should invite the borrower to ask for help rather than create a document that looks convenient. A reconciliation note from the borrower can explain a one-time expense without forcing a new document request.

Use a checklist with a reason for each item

A list of document names is easy to ignore. A checklist that says why each document is needed is easier to complete. For example, the script can explain that the K-1 shows the borrower's share of business income and that the operating agreement shows who owns the entity. Keep the checklist to one page so the borrower can print it or read it on a phone.

Keep the reason short and free of jargon. The borrower does not need a course in underwriting. They need to know which page to send and why the page matters. A clear reason also reduces the chance that the borrower sends a substitute document that does not satisfy the request.

Put the request in plain language

Use short sentences and common words. Replace "provide executed entity formation documentation" with "send the signed papers that created your business." If a technical term is necessary, define it in the same sentence. The borrower should not need a glossary to answer the request. Replace the quoted instruction with a plain sentence such as: send the signed papers that created your business.

Read the script aloud before sending it. If a sentence is hard to say, it will be hard to read. Ask a colleague who does not work in mortgage to explain the request back. The explanation will show which part is unclear.

Offer one channel and one contact

Give the borrower one place to upload the documents and one person to call with questions. A request that lists three email addresses and a portal invites duplicate sends and lost attachments. The contact should be able to see the file and answer questions about the specific request. Put the upload link and the contact name in the same paragraph so the borrower does not have to search for either.

Set a response window and say what happens next. For example, tell the borrower that the processor will confirm receipt within one business day and list any missing pages. The confirmation is a small step that prevents the borrower from sending the same file twice. If the borrower cannot meet the window, ask for a short reply with the expected date instead of silence.

Check receipt against the request

When the documents arrive, compare them with the checklist before marking the condition complete. A full tax return may still be missing a schedule, and a profit and loss statement may be unsigned. The check should happen on the day of receipt so the borrower has time to send the missing page. If a page is missing, send one specific request rather than a new copy of the entire checklist.

Record what was received and what is still open. The note should name the document, the year, and the page or schedule. A note that says "tax returns received" is not enough for the next reviewer. The loan processing support team can use the note to avoid a second request.

Escalate unusual cases instead of improvising

Some self-employed files need a document the script does not cover, such as a trust return or a foreign entity record. The assistant should escalate that file to a processor instead of inventing a requirement. The escalation should include the document received, the question, and the lender guideline that may apply. Record the escalation in the file so the processor can see what was asked and what remains open.

The borrower communication support team can keep a short list of unusual cases and the approved response. The list helps the next assistant answer consistently without turning the script into a legal treatise. The IRS self-employed tax center is a useful reference for the forms borrowers may recognize, but the lender's requirement still controls the request. Update the list when a lender changes its requirement so the script does not preserve an outdated answer.