Submissions to lenders, tracked per lender

A submission package is the email and attachments a lender's ISO desk expects: the signed application, three to six months of statements, the month-to-date statement, the owner's ID and a voided check. Choose lenders from the match matrix, and the submission builder lays out one email per lender with that lender's template, the deal's merge fields and your signature.

Attachments are picked from the documents already on the deal. Templates are managed in settings, with a preview, so subject lines like "DBA, ask $50k, your shop name" are consistent across reps.

Lenders know your reps' addresses, so packages go out from your own email. Open the prepared email in your mail client, or copy it, then attach the files. If you used a lender's portal instead, mark the submission sent with a channel and a note. Either way the submission records when it went out and who sent it.

Each submission has its own status: queued, sent, in review, stips requested, approved, declined, no response, withdrawn, contract out, contract signed, funded or cancelled. Declines take one or more decline reasons, such as insufficient revenue, too many positions, excessive NSFs, industry or state restricted, or credit too low.

Notes on the submission capture what the lender's rep said. Offers are entered on the submission they came from, so the offer comparison always knows which lender each number belongs to.

Because every submission and decline reason is stored, the lender report and each lender's performance tab show approval rates and funded volume. Over time you see which lenders actually fund your kind of deal, and whether your stored criteria match what they decline. The submission checklist covers what to include before anything goes out.