Private lenders run the identity-verification framework on two primary frameworks — the manual verification framework and the automated verification framework. The choice runs against the lender’s boarding-cycle speed, the lender’s audit-trail framework, the lender’s compliance framework, and the lender’s loan-volume framework. This article walks the side-by-side framework against each.
Manual verification framework
The manual verification framework runs the identity-verification cycle against the lender’s loan-officer or boarding-coordinator framework on each borrower. The framework runs the document-collection framework against the lender’s email framework, the lender’s borrower-portal framework, or the lender’s in-person framework. The framework runs the document-review framework against the lender’s personnel framework on each verification step.
Automated verification framework
The automated verification framework runs the identity-verification cycle against the third-party identity-verification framework — the platform framework runs the document-authentication framework, the knowledge-based-authentication framework, the biometric framework, and the OFAC sanctions-screening framework against the borrower on the automated framework. The framework runs the IRS TIN-matching framework against the IRS framework on the automated cycle. The framework runs the entity-authority framework against the document-extraction framework on the platform framework.
Speed framework
The manual verification framework runs the boarding-cycle framework on a longer cycle against the lender’s personnel framework. The automated verification framework runs the boarding-cycle framework on a shorter cycle against the third-party platform framework. The lender that runs the loan-volume framework on a higher framework runs the automated verification framework on a faster boarding-cycle framework against the lender’s operations.
Accuracy framework
The manual verification framework runs the document-review accuracy framework against the lender’s personnel-training framework. The framework runs the document-tampering-detection framework on a thin discipline against the human-eye framework. The automated verification framework runs the document-authentication framework against the machine-vision framework on the third-party platform framework. The framework runs the document-tampering-detection framework, the photo-substitution-detection framework, and the data-extraction framework against the platform framework.
Audit-trail framework
The manual verification framework runs the audit-trail framework against the lender’s servicing-platform framework — the lender runs the verification-document framework, the verification-method framework, the verification-date framework, the verification-officer framework, and the exception-and-escalation framework on the manual recordkeeping framework. The automated verification framework runs the audit-trail framework on the third-party platform framework — the platform framework runs the recordkeeping framework against the verification cycle on the platform framework.
Compliance framework
The manual verification framework runs the compliance framework against the lender’s personnel-training framework on the Customer Identification Program framework, the FinCEN Beneficial Ownership framework, and the OFAC sanctions-screening framework. The automated verification framework runs the compliance framework against the third-party platform-certification framework on the same frameworks. The lender that runs the regulatory-examination framework on a higher cycle runs the automated verification framework on a thicker audit-trail framework against the regulatory framework.
Choosing the framework
The lender that runs the loan-volume framework on a higher framework runs the automated verification framework on the loan-boarding cycle. The lender that runs the loan-volume framework on a lower framework runs the manual verification framework on the loan-boarding cycle with the documented audit-trail framework against the lender’s servicing platform. The hybrid framework runs the automated verification framework against the document-authentication framework and the OFAC screening framework and runs the manual framework against the entity-authority framework on the loan-boarding cycle.
Related Topics
- Identity Verification at Loan Boarding
- Five Wire Fraud Defenses for Private Lenders
- Mortgage Fund Subservicing Done Right
- Multi-Lender Notes With Up to 10 Investors
- Fidelity Bonds for Trust Account Signatories
This article is educational and does not constitute legal, regulatory, or tax advice. The identity-verification framework runs against the Bank Secrecy Act framework. The framework runs against the USA PATRIOT Act §326 Customer Identification Program framework. The framework runs against the Corporate Transparency Act beneficial-ownership framework. The framework runs against the OFAC sanctions-screening framework and the IRS framework on the lender’s recurring compliance cycle. Consult qualified legal counsel and a tax adviser on the specific identity-verification framework against any private-lending operation.
Sources
- USA PATRIOT Act §326 — Customer Identification Program. Financial Crimes Enforcement Network.
- FinCEN Beneficial Ownership Information Reporting Rule. Financial Crimes Enforcement Network.
- Office of Foreign Assets Control — Specially Designated Nationals List. U.S. Department of the Treasury.
- IRS TIN Matching Program. Internal Revenue Service.
- FFIEC Bank Secrecy Act / Anti-Money Laundering Examination Manual. Federal Financial Institutions Examination Council.
