CloudFiles is the October AppExchange Amplified partner. Live build with Talent Stacker, Tue 27 Oct, 1:00 PM ET. Details
Mortgage document automation

CloudFiles for mortgage

Loan processors chase pay stubs, appraisals and title work for each application, and one missing page holds the file. CloudFiles files each document, verifies income and builds the closing package in Salesforce, so loans close on time.

A house with keys and a loan document, illustrating mortgage document automation
Trusted by Salesforce teams across industries
Mortgage documents, before and after

From a missing pay stub to a closed loan

Lenders run every borrower and residential loan application in Salesforce, yet pay stubs, appraisals and closing documents arrive by email and are read page by page. CloudFiles files, collects, checks and produces them on the loan itself.

The manual way

  • Loan processors build each mortgage file by hand, saving pay stubs, appraisals and title documents from email into shared drives and the loan application. Across a full pipeline, filing outpaces underwriting and pages go missing.
  • Loan officers send checklists to borrowers by email and save each reply of pay stubs, W-2s and bank statements to the loan application by hand. Underwriting waits for the last statement, often for days, while the rate lock keeps running.
  • Post-closing teams email each closed loan's note, disclosures and appraisal to the investor or servicer as attachments, one loan at a time. Once the files leave, the lender cannot show which were opened or recall a superseded version.
  • Underwriters compare each pay stub with the W-2 and tax return line by line, then key income and employer details into each loan applicant. A mismatch found late sends the application back a step and moves the closing date.
  • Closers rebuild the note, deed of trust and lender disclosures from the loan details for every closing, then route each document to the borrowers separately for signature. One missing signature pushes back the funding date for the whole closing table.

The CloudFiles way

  • CloudFiles gives every residential loan application a ready-made mortgage file from the day it is created. A structured folder with sub-folders for income, assets, property and closing appears on the record, so each document lands in place without filing.
  • CloudFiles ends the borrower email chase by giving each loan application its own secure upload space. Borrowers send every checklist document with no Salesforce account, every upload lands in the loan's folder, and underwriting opens a complete file.
  • CloudFiles hands each closed loan to its investor or servicer from the loan record. The loan folder is shared through one secure link open only to the investor's domain, each opening is recorded by viewer email, and access closes after the transfer.
  • CloudFiles cross-checks every borrower's income documents before an underwriter opens them. W-2s, pay stubs and 1040s are grouped into one set and compared, only figures that disagree go to review, and the rest are mapped onto the loan applicant's records.
  • CloudFiles builds the closing package from the residential loan application and returns it signed. The note, deed of trust and disclosures use the loan's own data and reach the borrowers in one e-signature envelope, with signed PDFs filed on the application.
Mortgage use cases in Salesforce

Every mortgage document, handled from application to closing

The six jobs below run in Salesforce Flow on the residential loan application, the borrower's account and the opportunity, with CloudFiles doing the document work.

Loan file folder automation

CloudFiles creates a structured mortgage file for every residential loan application in Salesforce, inside the borrower's account folder, so pay stubs, appraisals and closing documents have a place before they arrive.

  • Saving a loan application triggers a flow that runs the create folder flow action, with a fixed set of sub-folders for every loan
  • Each loan's folder lives within the borrower's folder, so a loan officer sees every past and current mortgage for that borrower together
  • When a lead converts, the move resource flow action carries the prospect's early documents into the borrower's new account folder

SharePoint integration for mortgage files

CloudFiles links Salesforce with SharePoint and any other storage a lender runs, so every mortgage file stays in the lender's storage while loan teams open, search and manage it from the Salesforce record.

  • The copy Salesforce files flow action sends each attachment added in Salesforce to the loan's SharePoint folder, giving every file one home
  • Each file carries its loan number, borrower name and document type as SharePoint metadata, so any document in the loan book is searchable by tag
  • Closed loans move into their own library at closing, and a flow can grant or revoke access with the update permissions flow action

Borrower and third-party document collection

CloudFiles collects mortgage documents from borrowers, appraisers and title companies through secure links or the lender's Experience Cloud portal, and files every upload in the loan application's folder.

  • Borrowers see exactly which pay stubs and statements to send, because the create file request flow action lists each one in their data room
  • Appraisers and title companies return reports through links limited to their domain, switched off by the update link settings flow action at closing
  • Borrowers who log in to the lender's Experience Cloud portal see their own loan folder and upload into it from the CloudFiles widget

Mortgage document checklist automation

CloudFiles automates the mortgage document checklist in Salesforce. Every borrower upload is split, classified and filed, and the residential loan application's matching checklist item changes to received.

  • The split document using AI flow action breaks a scanned packet into separately named pay stubs, bank statements and tax returns
  • Each document is classified as it arrives, filed into the right sub-folder, and its document checklist item is set to received
  • Loan processors see every missing document from the checklist on the record, and a new file request can go to the borrower for each gap

Income verification for mortgage underwriting

CloudFiles automates mortgage income verification in Salesforce. Each borrower's W-2s, pay stubs and 1040s form one dataset, cross-checked for employer and income, then mapped onto each loan applicant's records.

  • The create dataset flow action groups a borrower's income documents, so year-to-date pay, the W-2 and the 1040 are compared as one set
  • A CloudFiles Document AI workflow sends any figure that disagrees to an underwriter, shown beside the page it came from
  • Agreed figures become loan applicant income and employment records through the document mapper flow action, one for each employer

Closing document generation and e-signature

CloudFiles produces closing documents, pre-approval letters and commitment letters from the residential loan application and opportunity in Salesforce, routes each for e-signature and stores the signed PDF on the loan.

  • The get doc-gen templates flow action picks the template for each loan program, so one flow serves conventional, FHA and VA loans alike
  • Borrower, property and loan terms fill every document straight from the residential loan application and its loan applicants
  • Through the generate document (batch) flow action, borrowers sign all closing documents in one envelope, and the signed set returns to the application
Document types

Key documents we handle for mortgage

Six of the documents mortgage teams handle most. CloudFiles also files, reads and produces every other document a lender keeps on a loan in Salesforce.

Pay stubs and W-2s

Income documents for each loan applicant, kept in the loan's income folder with the residential loan application for underwriting and later audit.

Bank and asset statements

Statements that show a borrower's down payment and reserves, with balance questions answered across every statement on the loan application.

Appraisal reports

The appraiser's valuation of the property, received through a secure link and stored in the loan's property folder for the underwriter.

Title and homeowners insurance documents

Title commitments and insurance binders from third parties, gathered by file request and filed on the residential loan application before closing.

Pre-approval and commitment letters

Letters a lender issues as the loan advances, generated from the loan application's current terms and saved to the borrower's file.

Closing packages

The note, deed of trust and lender disclosures, generated together from loan data and returned to the record with every signature in place.

Security & compliance

Stay industry compliant

CloudFiles is independently audited for SOC 2 Type II, certified to ISO 27001, and compliant with HIPAA and GDPR. Data residency is supported in the US, EU, UK and AU. Your files stay in your own storage. CloudFiles never re-hosts them, and they are not used to train our AI models.

SOC 2
Type II
HIPAA
Compliant
ISO 27001
Certified
GDPR
Compliant

Frequently asked questions

CloudFiles builds a mortgage folder for each loan application in Salesforce as soon as the residential loan application is created, inside the borrower's account folder. Sub-folders for income, assets, property and closing come with it, and the folder opens from the record page. Admins build this once with the create folder flow action, triggered when the application is created.

Yes. CloudFiles keeps mortgage files in the storage the lender already uses, whether SharePoint, Google Drive, Azure Blob, Amazon S3 or another provider, and opens each loan's folder from the residential loan application. Anything a loan officer attaches in Salesforce is copied into the loan folder, so there is one home per document, and storage permissions stay exactly as the lender set them.

Borrowers send mortgage documents into Salesforce from a secure CloudFiles upload link, with no Salesforce account needed. Each residential loan application has its own upload space listing one request for every checklist document, such as a pay stub or bank statement, and every upload is saved to the loan's folder. The create file request flow action turns each checklist item into a request.

CloudFiles shares loan documents from the residential loan application through a data room or secure link rather than email attachments. Links can ask for email verification, a password or a specific email domain, can stop downloads, and the lender can turn them off at closing. Each view and download is logged on the application, so processors know which party has opened what.

In Salesforce, every document a mortgage needs is tracked as a checklist item on the residential loan application, and its status moves from new to pending to accepted. With CloudFiles, each borrower packet can be split, every upload sorted as it lands and the matching item set to received, so processors spot gaps without opening files. The split document using AI flow action does the splitting.

CloudFiles automates mortgage income verification inside Salesforce by grouping each borrower's W-2s, pay stubs and 1040s into one dataset. From there, a CloudFiles Document AI workflow compares employer, year-to-date pay and annual income across them, sends any mismatch to an underwriter, and maps agreed figures onto the income and employment records under each loan applicant.

Yes. CloudFiles runs the whole mortgage document process in Salesforce. A CloudFiles Document AI workflow sorts each incoming document by type, pulls out the fields underwriting needs, finds the matching loan application and loan applicant, chooses the next step and updates the records. Changes the lender wants checked wait for an underwriter's approval, and each run is audited step by step.

CloudFiles builds mortgage closing documents from the residential loan application in Salesforce, and the signed copies come back to the same application. Templates for the note, deed of trust and lender disclosures fill with borrower, property and loan terms, and the whole package reaches the borrowers in one e-signature envelope. Admins run it with the generate document (batch) flow action.

Yes. CloudFiles generates a mortgage pre-approval letter from the residential loan application in Salesforce, using the borrower's details and the loan terms held on the record. A loan officer creates it from the record in one click, or a flow creates it automatically once the application's status changes, and the letter is saved to the borrower's loan folder.

Yes. CloudFiles runs on the Financial Services Cloud mortgage objects, including the residential loan application, loan applicant and document checklist item. It is a managed package on AppExchange that runs on every standard and custom object, so lenders build document steps into their existing record-triggered and screen flows, and each loan's files open on its record page.

Book your personalized demo

Bring a residential loan application and its documents, and watch CloudFiles file, check and close it in your Salesforce org.