Joint Final Rule Customer Identification Programs For Broker Dealers Form

Use a Joint Final Rule Customer Identification Programs For Broker Dealers template to make your document workflow more streamlined.

What this broker-dealer form records

The Joint Final Rule Customer Identification Programs For Broker Dealers Form records how a broker-dealer establishes and applies its Customer Identification Program under the joint SEC and Treasury rule framework. It documents procedures for collecting identifying information, verifying customer identity, maintaining records, and responding to required notices or exceptions. The form is not a tax return or a universal federal filing form; its exact fields depend on the applicable broker-dealer workflow and compliance program. Review the source form and current SEC, FinCEN, and applicable FINRA requirements before execution.

Broker-dealer compliance

Broker-dealer compliance teams use the form to document Customer Identification Program procedures, assign review responsibility, and preserve evidence supporting identity verification and recordkeeping decisions.

Onboarding operations

Operations and onboarding teams use the form when coordinating customer data, verification steps, approvals, and signatures across offices, reviewers, and regulated workflows.

Users who manage this form

Compliance officers at broker-dealers use the form to align customer identification procedures, reviewer responsibilities, and retained evidence with the firm’s written CIP and regulatory recordkeeping controls.
Broker-dealer onboarding managers coordinate customer information, identity checks, signatures, and audit evidence across operations teams using a structured signNow template and controlled recipient routing.

Field preparation

Upload the broker-dealer form and place required fields without rebuilding the document, while retaining the original structure for review and signature routing.

Signer routing

Route customer-identification records to designated reviewers and signers in a defined order, reducing uncertainty about who must approve each section.

Audit trail

Capture timestamps, recipient actions, and completion evidence alongside the signed form for later compliance review and record reconstruction.

Signer authentication

Use SMS authentication and related controls when the firm’s customer-identification workflow requires stronger signer attribution than an email link alone.

Record preservation

Preserve completed forms and audit evidence in a controlled workspace, with retention decisions aligned to 17 CFR §240.17a-4 and state requirements.

Business integrations

Connect the workflow with approved business systems so customer-identification data and completed documents remain organized across onboarding and compliance operations.

How the form moves through signNow

Use a controlled workflow to prepare, review, sign, and preserve the broker-dealer identification record.

Upload form: Upload the Joint Final Rule Customer Identification Programs For Broker Dealers Form to signNow.
Review fields: Auto-detect fillable fields and review customer-identification entries.
Route for signature: Send assigned sections to authorized broker-dealer reviewers and signers.
Archive record: Store the completed record with its signNow audit trail.

be ready to get more

Get legally-binding signatures now!

Start free trial

Request a call

Best ROI. Our customers achieve an average 7x ROI within the first six months.
Scales with your use cases. From SMBs to mid-market, airSlate SignNow delivers results for businesses of all sizes.
Intuitive UI and API. Sign and send documents from your apps in minutes.

Setting	Recommendation
Authentication method	SMS authentication for external signers
Signature type	Electronic signature with completion certificate
Audit trail	Enabled with the signed record
Document retention	6 years under 17 CFR §240.17a-4
Encryption	TLS 1.2/1.3 and AES-256 encryption

Signer authentication:

Records the authentication event used before signing.

Timestamp capture:

Captures the exact time of each action.

Document hashing:

Associates the signed document with its integrity record.

Tamper-evident sealing:

Seals completed content against unnoticed changes.

Action history:

Lists views, edits, signatures, and recipient actions.

Audit export:

Exports evidence for controlled compliance review.

Connect broker-dealer identification workflows

Connect customer identification records with CRM, ERP, cloud storage, and collaboration tools to reduce rekeying and preserve organized transaction evidence.

Platform requirements for signNow

Complete the Joint Final Rule Customer Identification Programs For Broker Dealers Form in signNow using Chrome, Firefox, Safari, or Edge on Windows or macOS. signNow also provides mobile apps for iOS and Android, allowing authorized users to review and sign assigned records away from a desktop.

Browsers Chrome, Firefox, Safari, and Edge
Desktop systems Windows and macOS desktop access
Mobile apps iOS and Android signNow apps

Regulated deployments should use managed Windows, macOS, iOS, or Android devices, approved identity controls, and defined access permissions. Teams connecting the form to internal systems should confirm API, SSO, certificate, and long-term validation requirements against their signNow plan and broker-dealer information-security policy before production use.

Security controls for this form

Transport encryption:

TLS 1.2/1.3 protects data in transit

Stored encryption:

AES-256 protects stored document data

Security certification:

SOC 2 Type II report available on request

Information security:

ISO 27001 certification supports information security

Privacy compliance:

HIPAA compliance requires a BAA

Electronic signature law:

ESIGN and UETA compliance supports electronic signatures

Best practices for this form

Accurate identity data, controlled approvals, and preserved evidence make this broker-dealer record easier to review and defend.

Reconcile the written program

Identify the broker-dealer entity, responsible compliance officer, customer categories, and verification procedures before uploading the form. Compare every populated field with the firm’s written Customer Identification Program and resolve discrepancies before sending it for signature.

Separate preparation and approval

Limit editing and signing permissions to personnel assigned to the broker-dealer’s Customer Identification Program. Use role-based access, named recipients, and a review sequence that separates preparation from final approval.

Keep the evidence together

Preserve the signed form, completion certificate, and audit trail together. Record the applicable retention policy and review SEC, FinCEN, and FINRA requirements before deleting or transferring compliance records.

Match authentication to risk

Use the strongest authentication appropriate for the customer-identification workflow, especially when the document contains personal information. Capture required consent and provide consumer disclosures when ESIGN Section 101(c) applies.

Retention rules for broker-dealer records

Classify the completed form and related communications before assigning a retention period under the applicable broker-dealer recordkeeping rule.

6 years for broker records

Broker-dealer books and records generally follow 6-year retention under 17 CFR §240.17a-4; confirm the record category.

6 years for account records

Brokerage account records generally require 6 years under 17 CFR §240.17a-4; preserve accessible copies and related evidence.

3 years for communications

Broker-dealer communications generally require 3 years under 17 CFR §240.17a-4; classify communications separately from the form.

First 2 years accessible

The first 2 years of covered records must remain easily accessible under 17 CFR §240.17a-4.

State rules may extend retention

State retention rules may exceed federal periods; verify the applicable state and record classification before destruction.

Privacy and disclosure pitfalls

Uploading customer-identification data without restricting recipient access can expose sensitive personal information through email links, downloads, or shared workspaces.
Omitting evidence of electronic consent can weaken the record when consumer-facing disclosures under ESIGN Section 101(c) apply to the transaction.
Granting every team member editing rights can obscure who changed the broker-dealer form and whether an authorized reviewer approved it.
Storing the signed form separately from its audit trail makes later reconstruction of identity verification and approval events more difficult.

28M+Documents signed

13+Years in business

4.6/5Average G2 rating

Troubleshooting this form workflow

Resolve field, authentication, consent, plan, and retention questions before the broker-dealer record is finalized.

Upload the source PDF again, then check signNow’s detected fields before sending. Auto-detection can miss unusual labels or scanned areas, so place required text, date, initials, and signature fields manually where needed.

Business includes templates, audit trails, and mobile apps at $8/user/month when billed annually. Business Premium is $15/user/month and adds bulk send, while Enterprise is $30/user/month and adds advanced signer authentication.

Use signNow’s audit trail and completion certificate to preserve timestamps, recipient actions, and signing history. ESIGN and UETA recognize electronic records when intent, consent, attribution, and reproducible retention requirements are satisfied.

For customer-facing electronic records, provide the ESIGN Section 101(c) disclosure, demonstrate electronic access, and explain withdrawal procedures when required. Configure signNow’s recipient experience to support the disclosure before signing.

Use signNow’s SMS authentication or stronger available signer controls when the broker-dealer’s risk assessment requires more than email access. Confirm the chosen method matches internal CIP procedures and applicable regulatory expectations.

Do not treat the form as a substitute for the firm’s written Customer Identification Program or regulatory analysis. Verify the record category, applicable 17 CFR §240.17a-4 period, and state requirements before archiving.

BE READY TO GET MORE

Get this form now!

If you believe that this page should be taken down, please follow our DMCA take-down process.