Form 32 Agreement Of Depository

Use a Form 32 Agreement Of Depository template to make your document workflow more streamlined.

What Form 32 Agreement Of Depository does

Form 32 Agreement Of Depository is a document used to record an arrangement involving the deposit, custody, or handling of identified property or records. Its exact legal purpose, required fields, issuing authority, and filing rules depend on the jurisdiction and transaction behind the form. Before signing, confirm the parties, deposited items, delivery conditions, release instructions, and applicable state law. signNow can help you upload the form, identify fillable fields, route it to authorized signers, and preserve the completed copy with an audit trail, but it does not determine whether the underlying agreement is legally sufficient.

Business counterparties

Businesses and counterparties use the agreement to document who holds specified property, records, or transaction materials and what happens after delivery.

Custody administrators

Law firms, escrow teams, and operations staff use it when custody instructions must be signed, shared, and retained for later reference.

Document fidelity

Upload the exact agreement, preserve its wording, and route designated fields without recreating custody terms manually.

Field assignment

Assign signatures, initials, dates, and acknowledgments to the parties responsible for the depository arrangement.

Audit trail

Capture signer actions, timestamps, and completion details alongside the executed Form 32 record.

Reusable template

Use reusable templates when the same depository terms recur, while reviewing transaction-specific details each time.

Record access

Keep the signed agreement and completion evidence together for later operational or legal review.

System connections

Connect signing activity with systems such as NetSuite, Salesforce, Google Drive, or Box.

Complete Form 32 in signNow

Prepare the depository terms first, then use signNow to route the exact agreement to its authorized parties.

Upload form:
Upload the completed Form 32 file.
Check fields:
Review auto-detected fields and add missing fields.
Assign signers:
Assign each field to the correct signer.
Send agreement:
Send the agreement for electronic signature.
Store records:
Store the signed copy and completion certificate.

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	Email verification with SMS OTP
Signature type	Electronic signature with signer intent
Audit trail	Retain completion certificate and action log
Document retention	Follow the governing transaction’s retention rule
Encryption	Use TLS 1.2/1.3 and AES-256

Authenticate signer:

Records the signer identity and authentication event for the agreement.

Capture timestamps:

Captures the exact time each agreement action occurs.

Hash document:

Associates the completed Form 32 file with a document hash.

Log actions:

Logs field completion, signature placement, and signer actions.

Seal record:

Seals the completed record against undetected post-signing changes.

Export evidence:

Allows authorized users to retrieve or export the audit trail.

Security for the signed agreement

Transport encryption:

TLS 1.2/1.3 in transit

Storage encryption:

AES-256 at rest

Security reporting:

SOC 2 Type II certification

Information security:

ISO 27001 certification

U.S. eSignature:

ESIGN and UETA compliance

Signer verification:

Two-factor authentication available

Platform requirements for signing

Form 32 Agreement Of Depository can be uploaded and signed through signNow using Chrome, Firefox, Safari, or Edge on Windows and macOS, with mobile apps available for iOS and Android.

Web browsers Chrome, Firefox, Safari, Edge
Operating systems Windows, macOS, iOS, Android
Mobile signing signNow mobile apps

Organizations should confirm that managed devices permit document upload, signer authentication, and access to the completed record. Teams using Salesforce, NetSuite, Microsoft 365, Google Drive, Box, or an API should also review administrator permissions and retention controls before deployment.

Connect the agreement to business systems

Named signNow integrations can connect Form 32 Agreement Of Depository workflows with CRM, ERP, collaboration, and storage systems.

Best practices for Form 32 records

Accurate custody terms and complete evidence matter more than simply collecting an electronic signature on Form 32.

Verify every custody term

Before uploading, compare the source document against the transaction instructions. Confirm the depository name, deposited property or records, delivery conditions, release events, and every required signature. Do not let auto-detected fields replace a review of the agreement’s substantive terms.

Map fields to authorized parties

Assign each signature, initial, date, and acknowledgment field to the person authorized under the underlying transaction. Use signer order when one party must act before another, and confirm that any exhibit or schedule requiring execution is included in the same envelope.

Archive the executed record

After completion, download the signed agreement and completion evidence together. Store the files in an access-controlled repository, preserve the original file format, and apply the retention period required by the transaction, industry rule, or state law governing the record.

Test before sending

Test the completed workflow with a non-production copy before sending Form 32. Check signer identity controls, field visibility, notifications, audit-trail access, and export behavior so the final record can be reproduced for the parties or a later legal review.

Challenges when completing the agreement

Unclear deposit description can create disputes about which property, records, or original documents the agreement actually covers.
Missing release instructions may leave the depository unsure when, to whom, or under which condition deposited materials may be returned.
Unsigned exhibits or schedules can weaken the connection between the signed agreement and the items identified for deposit.
Using an unverified template may omit state-specific acknowledgments, notices, or signature requirements applicable to the underlying transaction.

Troubleshooting Form 32 signing

Resolve the specific field, signer, consent, plan, and compliance questions that can interrupt a Form 32 Agreement Of Depository workflow.

If a signer cannot open Form 32, confirm the invitation address, resend the request, and check whether the document remains active. Business plan users can use signNow’s standard sending workflow; the signer does not need the sender’s account to review the assigned document.

If auto-detection misses a field, open the uploaded document in the editor and place the missing signature, date, initial, or text field manually. Review every page, exhibit, and schedule before sending because field detection does not interpret the agreement’s legal requirements.

A completed e-signature record can support attribution and intent under ESIGN and UETA when the parties consent and the record remains reproducible. Those laws do not decide whether this specific depository arrangement requires notarization or additional state-law formalities.

If the agreement contains consumer-facing electronic records, review the ESIGN consumer-disclosure requirements in 15 U.S.C. §7001(c), including paper-record rights and electronic-access capability. Obtain any required consent before routing Form 32 for signature.

Business Premium is listed at $15 per user per month when billed annually and includes bulk send. Business is listed at $8 per user per month annually. Choose bulk sending only when repeated Form 32 transactions justify that workflow.

For sensitive custody records, signNow states that HIPAA compliance requires a BAA, while ESIGN and UETA compliance supports U.S. electronic-signature workflows. Confirm whether the deposited material contains protected health information before relying on a HIPAA workflow.

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.