Download signNow app
4.7 / 5 rating on

Fully Disclosed Clearing Agreement Of Pershing, LLC Sec Gov Form

Use a Fully Disclosed Clearing Agreement Of Pershing, LLC SEC gov template to make your document workflow more streamlined.

What the Pershing agreement form does

The Fully Disclosed Clearing Agreement Of Pershing, LLC Sec Gov Form records an authorized relationship in which Pershing, LLC may provide clearing and related securities-account services under the agreement’s terms. The form should be completed with the correct firm, account, representative, and authorization information before signature. A sender can upload the document to signNow, use auto-detection or place fields, assign signers, and send it electronically. signNow records signer actions and produces an audit trail. Applicable securities, tax, privacy, and state requirements still determine approval, retention, and any required disclosures.

Platform requirements for signing securely

Use signNow through Chrome, Firefox, Safari, or Edge on Windows or macOS. The signNow mobile apps support iOS and Android access for reviewing and signing the Pershing agreement. Connections use TLS 1.2 or TLS 1.3 for data in transit.

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

Regulated firms should manage access through approved devices and internal identity controls. Enterprise deployments may require SSO provisioning, API access, and documented retention procedures. Configure signer authentication and certificate requirements according to the firm’s compliance policy, Pershing workflow, and applicable securities obligations.

How signNow handles this Pershing form

The workflow connects the original Pershing document to assigned fields, signer actions, and the completed audit record.

  • Upload document: Upload the Pershing PDF into signNow and confirm the source document.
  • Map fields: Auto-detect fillable areas or place fields for each authorized participant.
  • Route agreement: Assign signing roles, review routing, and send the agreement securely.
  • Archive record: Collect signatures, then store the completed file with its audit trail.

How the Pershing audit trail works

The audit trail documents the technical events that connect the Pershing agreement, its signers, and the completed electronic record.

01

Verify signer:

 Authentication records the signer’s selected verification event.
02

Capture timestamps:

 Timestamp capture records delivery, viewing, and signing events.
03

Hash document:

 Document hashing helps identify changes to the signed file.
04

Seal record:

 Tamper-evident sealing links the completed record to its evidence.
05

Review activity:

 The audit trail lists signer actions, access details, and completion history.
06

Export evidence:

 Export the completed agreement and audit evidence for controlled archival.
be ready to get more
Get legally-binding signatures now!
Start free trialRequest 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.

Choose a signing method for this agreement

  1. Use the signNow web app when reviewing the full Pershing agreement on a desktop, mapping account information, and checking every required signature field before delivery.
  2. Use the signNow mobile app when an authorized representative must review or sign the Pershing agreement from an iOS or Android device away from the office.
  3. Use kiosk mode for supervised, in-person completion when a branch representative controls the device and guides the signer through the agreement without sharing credentials.
  4. Use a shareable signing link when the firm distributes the same Pershing agreement to authorized signers through a controlled channel and needs a reusable access point.

Recommended Pershing agreement workflow setup

Configure the Pershing agreement around authenticated signing, traceable activity, controlled access, and the firm’s documented retention policy.

SettingRecommendation
Authentication methodSMS two-factor authentication
Signature typeIntent-based electronic signature
Audit trailDetailed signer activity history
Document retentionFirm-approved securities retention schedule
Encryption and provisioningAES-256 storage with controlled user access

Security controls for Pershing agreements

Transport encryption:

 TLS 1.2/1.3 in transit

Storage encryption:

 AES-256 at rest

Security reporting:

 SOC 2 Type II certified

Information security:

 ISO 27001 certified

Electronic signatures:

 ESIGN and UETA compliant

Signer protection:

 Two-factor authentication available

Pershing agreement completion challenges

  • Entering account or representative details into the wrong field can create an incomplete Pershing agreement that requires correction and renewed signatures.
  • Sending the agreement before assigning every required signer can leave authorization evidence incomplete and delay account processing.
  • Using an outdated template can omit current disclosures or signature fields required by the firm’s Pershing onboarding procedure.
  • Saving the signed PDF without its audit trail can weaken the record’s evidence of delivery, intent, signer attribution, and completion.

Retention periods for signed Pershing records

Select the retention period based on the record’s actual regulatory classification, then preserve the completed agreement and audit evidence together.

01

Six years for broker-dealer records

FINRA 4511 governs applicable broker-dealer books and records; confirm the exact class and schedule with compliance counsel.
02

Six years under SEC Rule 17a-4

SEC Rule 17a-4 requires six-year retention for applicable books and records; preserve required records in an approved system.
03

Three years for federal tax records

Tax-related records follow the applicable IRS rule; IRC §6501(a) generally allows three years from filing, with longer periods for stated exceptions.
04

Six years for HIPAA records

If the agreement contains protected health information, HIPAA requires six years from creation or last effective date under 45 CFR §164.530(j).
05

Firm schedule when longer

Firm policies may require longer retention than federal baselines; document the selected period and review state securities requirements.

Record-keeping practices for Pershing agreements

Preserve the completed form with evidence of signing, apply the correct securities-record classification, and restrict access throughout the retention period.

Archive the agreement with evidence

Keep the signed Pershing agreement, completion certificate, and audit trail together in the firm’s controlled repository. Apply the retention period associated with the actual record class, and document any longer period required by SEC, FINRA, tax, or state rules.

Verify audit evidence before filing

Export the audit trail after completion and verify that signer names, timestamps, delivery events, and document identifiers correspond to the Pershing agreement. Restrict edits and preserve the exported evidence in a location covered by the firm’s records policy.

Review the approved template version

Use a controlled template containing the approved Pershing wording and required fields. Before sending, compare the template version with current firm instructions, then confirm account information, representative details, signer order, and required acknowledgments.

Control preparation and signing access

Limit access to personnel assigned to preparation, review, or signature administration. Use signNow roles or firm identity controls, require stronger authentication when policy demands it, and remove access when responsibilities change.

Fully disclosed agreement signing questions

Use these answers to resolve field, authentication, plan, and enforceability questions before completing the Pershing agreement.

Upload the original PDF into signNow, then use auto-detection or place required fields manually. Confirm every account, representative, and signature field before sending the Pershing agreement.

The signNow Business plan includes templates, audit trails, and legally binding eSignatures. Business Premium adds bulk send, while Enterprise adds advanced signer authentication and conditional fields for more complex workflows.

For financial-services records, configure retention according to your firm’s applicable obligations. signNow supports audit trails and document history; legal retention periods come from SEC, FINRA, tax, and state requirements, not the platform itself.

ESIGN supports electronic signatures when intent, consent, attribution, and record reproduction are established. UETA generally governs intrastate transactions, while ESIGN covers interstate commerce under 15 U.S.C. chapter 96.

Use signNow’s SMS authentication or another configured signer-authentication method when the firm requires stronger attribution. Review the audit trail for timestamps, signer actions, and delivery details before accepting the completed agreement.

Business and Business Premium plans include 100 signature invites per user annually, with overage fees. The Site License uses $1.50 per signature invite and is designed for usage-based, high-volume workflows.

ROI at a Glance

Key performance indicators that demonstrate SignNow's proven track record.

28M+Documents signed
13+Years in business
4.6/5Average G2 rating

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.