Download signNow app
4.7 / 5 rating on

Security Agreement Covering Instruments And Investment Property Form

Use a Security Agreement Covering Instruments And Investment Property template to make your document workflow more streamlined.

What this security agreement does

A Security Agreement Covering Instruments And Investment Property Form records a debtor’s grant of security interests in specified financial assets to a secured party. It identifies the parties, describes instruments, investment property, accounts, proceeds, and related obligations, and documents consent to the transaction. In signNow, the sender uploads the agreement, reviews auto-detected fields, assigns the debtor and secured party, and sends the final version for electronic signature. ESIGN and UETA can support electronic execution when intent, consent, attribution, and record retention requirements are satisfied; state law and transaction documents still control collateral perfection and exclusions.

Businesses that use security agreements

The form is most useful where financing depends on clearly documented rights in financial assets and a reliable execution record.

  • Solo commercial lenders use the form to document a borrower’s grant of security interests in identified instruments, securities accounts, and investment property before preserving an executed financing record.
  • Regional banks and private-credit firms coordinate debtor, secured-party, and control-party signatures while maintaining a consistent agreement copy across loan-closing files and audit records.
  • Enterprise treasury and legal departments use reusable templates for recurring secured transactions, with administrators controlling access and delegated senders routing agreements to authorized signers.

These tasks are executed by both individual contributors and centralized administrators depending on organizational policy and required controls.

How the agreement moves to signature

A controlled sequence keeps the collateral description, signer roles, and completed agreement aligned from upload through archival.

  • Upload form: Upload the agreement PDF to signNow.
  • Check fields: Review auto-detected fields and add missing signature, date, and initials fields.
  • Route signatures: Assign the debtor and secured party as signers, then send the final version.
  • Archive record: Complete signing and store the executed agreement with its audit trail.

Steps to complete the agreement

Prepare the final collateral language first, then use signNow to route, execute, and preserve the signed agreement.

  • Upload agreement:

    Upload the Security Agreement Covering Instruments And Investment Property Form.
  • Review fields:

    Let signNow detect fillable fields, then verify collateral and party information.
  • Assign signers:

    Add the debtor, secured party, and any required additional signers.
  • Complete signing:

    Send the final agreement, monitor status, and download the completed record.

Best practices for this security agreement

Accurate collateral descriptions and controlled signing records reduce disputes over what the agreement covers.

Identify every party and collateral category

Name the debtor, secured party, collateral categories, and applicable payment obligations exactly as they appear in the underlying transaction. Describe instruments and investment property precisely enough to distinguish them from excluded or unrelated assets, and have counsel review jurisdiction-specific drafting requirements.

Describe instruments and investment property precisely

List account numbers, securities accounts, control agreements, proceeds, and governing financial institutions only where the transaction requires them. Avoid copying sensitive credentials into the form. Use defined terms consistently so the signed agreement matches related loan, pledge, and control documents.

Confirm roles before sending the agreement

Upload the completed agreement to signNow, check detected fields, and assign each signer’s role before sending. Require the debtor and secured party to review the same final version, then preserve the completed PDF and certificate of completion together.

Separate execution from perfection requirements

Compare the signed agreement against the financing documents and any required UCC filing or control arrangement. Electronic execution does not replace perfection steps, filing-office requirements, notarization, or legal review required by the transaction or state law.
be ready to get more
Get legally-binding signatures now!
  • 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.

Recommended signing setup

Use a controlled signing configuration that preserves signer identity, document integrity, and the agreement’s complete execution history.

SettingRecommendation
Authentication methodEmail link with SMS verification
Signature typeLegally binding electronic signature
Audit trailDetailed certificate of completion
Document retentionFollow transaction policy and state law
EncryptionTLS 1.2/1.3 and AES-256

What the audit trail records

The audit trail gives the executed security agreement a chronological record of identity, document integrity, signing activity, and retrieval.

01

Authenticate signer:

Records the signer’s authentication event before signature placement.
02

Capture timestamp:

Captures the exact time of each review and signature action.
03

Hash document:

Associates the completed document with an integrity record.
04

Seal record:

Seals the executed agreement and action history against later alteration.
05

Record events:

Preserves signer, IP, and event details in the completion history.
06

Export trail:

Allows authorized users to retrieve or export the audit trail.

Security controls for signed agreements

Encrypted protection:

Protects agreement data during transfer and storage.

SOC 2 Type II:

Independent assurance for security controls and processes.

ISO 27001:

Certified information-security management framework.

GDPR compliance:

Supports privacy obligations for personal information.

HIPAA compliance:

Helps protect health information when a BAA applies.

ESIGN and UETA:

Supports legally recognized electronic transactions.

Privacy and disclosure pitfalls

  • Collateral schedules may expose account identifiers or ownership information when the completed agreement is shared beyond the transaction team.
  • A signer may approve the agreement without reviewing whether instruments, investment property, proceeds, and exclusions match the financing documents.
  • Consumer-facing signing may require electronic-record consent disclosures under 15 U.S.C. §7001(c), including access and paper-copy information.
  • Overbroad workspace permissions can let unauthorized users download the signed agreement or its audit trail.

State rules and document exclusions

State requirement

Notarization

Excluded documents

Wills and codicils

Excluded documents

Family-law decrees

State recording

Real-estate deeds

Special instruments

UCC exclusions

Retention periods for related records

Retention depends on the transaction and any regulated record category connected to the agreement; apply the controlling rule rather than a single universal period.

01

Contract-specific period

Retain the signed security agreement according to the transaction’s governing contract and applicable state law; no universal period applies.
02

Three years for tax records

If the agreement supports tax records, retain relevant records three years from filing under IRC §6501(a).
03

Six years for HIPAA records

If a covered healthcare workflow includes protected health information, retain required documentation six years under 45 CFR §164.530(j).
04

Later of three years or one year

If the record supports an employment-related file, apply the later of three years after hire or one year after termination under 8 CFR §274a.2(b)(2)(i)(A).
05

Policy-defined archival record

Document the organization’s approved retention rule and preserve the completed PDF, certificate, and audit trail together.

Integrations for agreement workflows

Connect the agreement workflow with CRM, ERP, cloud-storage, and project-management systems used to organize secured transactions.

Salesforce
Procore
Zapier
Microsoft Teams
Hub spot
Box
Microsoft

Platform requirements for signing

The agreement can be prepared and signed through supported desktop browsers using TLS-protected connections, or through signNow mobile apps on iOS and Android devices.

  • Desktop systems Windows 10 and macOS 12 or later
  • Supported browsers Chrome, Firefox, Safari, and Edge
  • Mobile apps iOS and Android signNow apps

Organizations should manage access through approved devices, workspace permissions, and any required SSO or API controls. Test the completed PDF and audit-trail export before adopting the workflow for secured transactions involving sensitive financial information.

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

Questions about signing this agreement

These answers address execution, plan selection, audit records, and legal limits specific to a secured financial agreement workflow.

The Business plan includes legally binding eSignatures, templates, audit trails, and mobile apps at $8 per user per month when billed annually. It includes 100 signature invites per user per year; additional invites may incur overage fees. The agreement remains subject to applicable transaction and state-law requirements.

ESIGN and UETA recognize electronic signatures when intent, consent, attribution, and record retention or reproduction are established. For consumer-facing records, 15 U.S.C. §7001(c) requires disclosures about paper records, electronic access, and withdrawing consent.

Use the Business Premium plan when bulk send is needed for repeated agreement packages; it is listed at $15 per user per month billed annually. Confirm that every generated agreement contains the correct collateral description before sending.

An electronic signature does not itself perfect a security interest or replace a required UCC filing, control agreement, possession arrangement, or state-law formality. Review the transaction structure and applicable jurisdiction separately from the signNow execution workflow.

The Site License is listed at $1.50 per signature invite and adds SSO, full API, and optional HIPAA, 21 CFR Part 11, and QES capabilities. Select those controls only when the transaction’s compliance requirements call for them.

If the form contains protected health information, signNow identifies HIPAA compliance as requiring a BAA. Limit access, confirm the BAA and organizational safeguards, and apply the six-year documentation rule in 45 CFR §164.530(j) where it governs.

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.