Parties
Identify each contracting entity by full legal name, entity type, address, and authorized signers; include tax identification numbers and contact details for notices and compliance communications.
Using a Financial Bank Agreement clarifies obligations, reduces transactional risk, and documents consent for electronic communication and signatures. It establishes enforceable terms for fees, security interests, and dispute resolution while helping institutions meet regulatory requirements for recordkeeping and consumer disclosures.
Typical users include banks, credit unions, corporate treasury teams, lenders, and commercial clients who need formal account or credit terms.
The agreement is also useful for legal counsel and compliance officers documenting obligations and electronic consent across banking workflows.
Identify each contracting entity by full legal name, entity type, address, and authorized signers; include tax identification numbers and contact details for notices and compliance communications.
Describe banking services provided such as account maintenance, deposit handling, lending facilities, payment processing, wire and ACH transfers, and any value-added services with applicable limits and service levels.
State fee schedules, including periodic maintenance fees, transaction fees, interest rates, default interest, late fees, and the method and timing of fee assessment and notice to the customer.
If applicable, list secured obligations, collateral descriptions, perfection steps (filing UCC-1 financing statements), valuation, insurance requirements, and procedures for sale or disposition upon default to comply with UCC provisions.
Define events of default, cure periods, cross-default clauses, acceleration remedies, notice requirements, and lender rights to enforce collateral or suspend services after required notices and reporting.
Include consent for electronic records and signatures consistent with ESIGN and UETA, describe acceptable e-signature methods, authentication levels, and how executed records will be retained and reproduced.
| Field | Configuration |
|---|---|
| Primary document format and handling | PDF preferred; convert Word to PDF before upload. |
| Signer authentication level and verification method | Email and SMS two-factor recommended for high-value transactions. |
| Field mapping and validation rules | Use required fields and format masks for dates and account numbers. |
| Automated routing, reminders, and escalation settings | Set sequential routing, automatic reminders, and SLA-based escalations. |
Typical integration and file format requirements for electronic signing and eSubmission workflows, including supported file types and common enterprise integrations.
Use MM/DD/YYYY; controls obligations and interest accrual.
W-9 provided to payers to avoid backup withholding.
Distribute signed copies to all parties and retain originals.
Check state rules; some states require notary or witnesses.
IRS, HIPAA, or SEC timelines may dictate retention periods.
Draft terms, exchange redlines, and reconcile commercial points.
Legal counsel reviews clauses and compliance teams verify regulatory controls.
Obtain signatures, apply authentication, and notarize if needed.
Distribute executed copies, update systems, and enforce retention schedules.
| signNow | DocuSign | Adobe Sign | PandaDoc | HelloSign | |
|---|---|---|---|---|---|
| Starting Price | $8/user/mo | $15/user/mo | $14/user/mo | $19/user/mo | $15/user/mo |
| Free Trial | 7-day free trial, no credit card required | Varies by plan and region | Varies by plan and region | Varies by plan and region | Varies by plan and region |
| Bulk Send | Yes (Business Premium) | Yes (plan dependent) | Yes (plan dependent) | Yes (offers bulk send) | No (limited capability) |
| Audit Trail | Yes, full audit trail | Yes, full audit trail | Yes, full audit trail | Yes, full audit trail | Yes, full audit trail |
| HIPAA Compliant | Yes (BAA available) | Yes (BAA available) | Yes (BAA available) | No | No |