Is a Bank Information Request legally valid if signed electronically?

Yes. Electronic signatures are legally enforceable under the federal ESIGN Act (15 U.S.C. ch. 96) and state UETA laws in most jurisdictions, provided intent, consent, attribution, and record retention requirements are met.

When should notarization or RON be used?

Notarization is rarely required for a bank info form itself, but use notarization or RON when the receiving institution or a contract explicitly demands a notarized authorization; RON rules vary by state and provider.

How should sensitive bank data be transmitted?

Use encrypted transmission channels (TLS 1.2/1.3), require strict access controls, and avoid unsecured email; mask stored account numbers and keep attachments in encrypted repositories.

What verification reduces fraud risk?

Require a voided check or bank letter, perform micro-deposit verification or bank validation services, and use multistep approvals in finance to confirm authenticity.

How long does verification typically take?

Verification often takes 1–3 business days with document review or micro-deposit confirmation; complex KYC checks can extend processing time.

How do I correct an error on a submitted form?

Void the original record, request a corrected submission from the payee, and document the change and approval in the audit trail to maintain a clear record for auditors.

Electronic Signature
Templates
Miscellaneous
Bank Information Request

Bank Information Request

This template is fully customizable. Edit the text, fill out the fields, and send it for signature. Give it a try!

BANK INFORMATION REQUEST

Requesting Company Name: Account Holder / Payee Name:

RECITALS

WHEREAS, Requesting Company requires banking details from Account Holder to facilitate electronic payments, direct deposits, reimbursements, or other financial transfers in connection with contractual obligations between the parties; and

WHEREAS, Account Holder is willing to provide accurate banking information and to authorize such transfers subject to the terms and conditions set forth in this Bank Information Request and Payment Authorization; and

WHEREAS, the parties intend that this document serve both as a request for banking details and as an authorization for specified payment activities under the Payment Terms below.

BANK INFORMATION

Bank Name Bank Address

Routing / ABA Number

Account Number

Account Type

Checking Savings Other:

International Banking (if applicable)

Additional Instructions or Reference (optional)

SCOPE OF WORK

The Requesting Company will use the account information provided solely for the purpose of initiating electronic transfers, deposits, or debits as expressly authorized in this document and any underlying agreement between the parties. Describe the services, obligations, or invoice references associated with transfers below.

Scope Description

PAYMENT TERMS

Amount Authorized per Transfer: Payment Schedule:

Late Payment Fee (if applicable):

The parties acknowledge that electronic transfers will be initiated in accordance with the schedule above, and that any debits or credits are subject to the receiving bank's processing rules. Requesting Company shall provide prior written notice to Account Holder for any change in amount or schedule not contemplated in this form.

TERM AND TERMINATION

This authorization is effective as of Start Date: and shall continue through End Date: unless earlier terminated pursuant to the terms below.

Either party may terminate this authorization for convenience upon written notice to the other party delivered at least days prior to the intended termination date. Termination shall not affect transfers already initiated in accordance with this authorization.

CONFIDENTIALITY

All banking information provided herein is Confidential Information. Requesting Company shall restrict access to such information to employees, agents, or service providers with a legitimate need to process payments and shall employ reasonable administrative, technical, and physical safeguards to protect against unauthorized disclosure. Disclosure is permitted only as required by law or with Account Holder's prior written consent.

AUTHORIZATION AND REPRESENTATIONS

By signing below, Account Holder certifies that the banking information provided is true and accurate and expressly authorizes Requesting Company to initiate electronic credits and debits to the account identified above in accordance with the Payment Terms. Account Holder represents that it is the legal owner of the account or is otherwise authorized to provide this information and to grant this authorization.

Account Holder agrees to indemnify and hold harmless Requesting Company from and against any claims, losses, damages, liabilities, or expenses arising from inaccurate information provided by Account Holder or from Account Holder's breach of this authorization, except to the extent caused by Requesting Company's gross negligence or willful misconduct.

Account Holder acknowledges that reversals or corrections may be processed in accordance with applicable banking rules and that Requesting Company may rely on the account identifiers provided. Account Holder shall notify Requesting Company promptly of any change to the account information.

Account Holder Certification

I certify that the information provided is accurate and that I am authorized to provide this authorization on behalf of the named account holder.

GOVERNING LAW

This Bank Information Request and Payment Authorization shall be governed by and construed in accordance with the laws of the jurisdiction specified by Requesting Company at the time of execution. The parties submit to the exclusive jurisdiction of the competent courts of that jurisdiction for any dispute arising out of or relating to this authorization.

ENTIRE AGREEMENT

This document, together with any referenced payment terms or underlying contracting documents between the parties, constitutes the entire agreement with respect to the subject matter hereof and supersedes all prior and contemporaneous agreements, understandings, negotiations and discussions, whether oral or written. No amendment shall be effective unless in writing and signed by both parties.

Requesting Party Printed Name:

By:

Date:

Account Holder Printed Name:

By:

Date:

What a Bank Information Request Is and when it’s used

A Bank Information Request is a standardized document used to collect a payee’s account details for ACH transfers, direct deposit, vendor onboarding, or wire payments. It typically asks for bank name, routing number, account number, account type, and payee verification data so payers can set up electronic payments. The form reduces back-and-forth email exchanges, creates a consistent record for finance and audit teams, and helps establish payment controls. When sensitive account data is requested, the requester should combine the form with secure transmission, retention, and access controls to limit exposure.

Why using a consistent Bank Information Request matters

A clear, consistent request ensures accurate payment setup, reduces payment delays, and creates an auditable trail for compliance and reconciliation. It also helps reduce duplicate inquiries and the risk of incorrect deposits caused by transposed numbers.

Who typically completes or receives this form

The Bank Information Request is used by finance teams, HR/payroll, vendor managers, and external payees during onboarding or payment changes.

Accounts payable and treasury teams manage collection and verification of banking details before authorizing electronic payments.
Payroll or HR departments collect direct deposit details from employees for salary payments and reimbursements.
Vendors, contractors, and service providers provide their bank details to receive invoices and reimbursements.

Use consistent routing and authentication steps to protect the payer and the payee while creating a repeatable process for internal controls.

Step-by-step: Collecting bank details securely

Follow a short, repeatable process to collect, verify, and store bank information for payments while minimizing exposure of sensitive data.

01

Prepare Request: Use a standardized form and require verification documents.
02

Authenticate Requester: Confirm identity of the person providing the bank details.
03

Verify Account: Match routing and account numbers to attached voided check or bank letter.
04

Record & Secure: Store encrypted records and restrict access to finance staff.

How to configure an online Bank Information Request workflow

Define fields, verification steps, and recipient routing so the form integrates with payment and accounting systems without manual rekeying.

Field	Configuration
Routing Number Field	Numeric only; 9 digits; required
Account Number Field	Alphanumeric allowed; required; masked
Attachment	Require voided check or bank letter upload
Approval Step	Finance approval required before record activation

Typical submission and approval flow

A simple arrowed flow clarifies who supplies data, who verifies it, and where it is stored for payments and audit.

Request Issued: Payer sends secure request to payee
Payee Responds: Payee completes fields and attaches proof
Finance Verifies: AP team confirms numbers and approvals
Payment Enabled: Account activated for ACH or wire disbursements

Digital delivery and security essentials

Choose a platform that supports field validation, access controls, audit trails, and strong transport security when collecting bank data.

Field Validation: Enforce numeric routing fields and required attachments
Audit Trail: Capture timestamps, IP, and user actions
Transport Security: TLS 1.2/1.3 and AES-256 encryption

Essential elements of a professional Bank Information Request

A well-designed request balances clarity, minimal data collection, and verification to reduce risk while enabling reliable payment setup.

Minimal Data

Collect only required fields: name, bank name, routing number, account number, account type, and required attachments to limit exposure.

Clear Instructions

Provide formatting examples such as 'Routing: 9 digits (xxxxxxxxx)' and request a voided check for verification to reduce errors.

Verification Evidence

Require an uploaded voided check, bank letter, or micro-deposit confirmation to substantiate account ownership before enabling payments.

Approval Controls

Include an approval step for AP or payroll that must be completed before setting up the payee in the ERP or payroll system.

Audit Logging

Record who submitted, who approved, and what changed with timestamps and stored attachments for audit readiness.

Data Protection

Ensure storage is encrypted at rest and in transit, and restrict access to authorized finance and payroll personnel only.

Required data elements and minimum protections

Payee Name: Exact legal name

Bank Name: Full institution name

Routing Number: 9-digit ABA

Account Number: Full account number

Account Type: Checking or Savings

Verification: Voided check or bank letter

Common mistakes when preparing a Bank Information Request

Accepting image-only submissions without verification increases misrouting risk and can delay payments by days or weeks.
Allowing free-text for routing numbers leads to transposed digits; enforce numeric, fixed-length validation to prevent errors.
Storing unencrypted bank details in shared drives exposes sensitive data to unauthorized access and compliance violations.
Skipping an approval or verification step can result in incorrect deposits and time-consuming recovery procedures.

Consequences of incorrect or insecure bank-data handling

Payment Loss: Incorrect deposits may be irrecoverable or require legal action

Regulatory Risk: Data breaches can trigger state breach notification laws

Operational Delay: Reconciliation and recovery consume staff time

Financial Penalties: Bank fees or ACH return charges may apply

Reputational Harm: Vendor relations can be damaged by payment errors

Contract Risk: Incorrect payments may breach vendor agreements

Timing considerations and response expectations

Set clear deadlines for payee responses and internal verification to avoid payment cycle delays; align response times with payroll or invoice cycles.

Payee Response:

Request return within 5–10 business days

Verification Window:

Allow 1–3 business days for finance verification

Payroll Cutoff:

Collect prior to payroll cutoff to affect next pay run

Change Processing:

Allow 2–5 business days to update payment files

Record Retention:

Retain completed forms per retention policy

Who can sign or authorize a Bank Information Request

Accounts Payable Manager

An AP manager or authorized finance officer approves bank details for vendor setup and confirms verification steps before enabling payments in the ERP.

Vendor/Payee Signatory

An authorized representative of the vendor—owner, officer, or designated signatory—provides and certifies account information and attaches proof of account ownership.

Real-world examples of how organizations use a Bank Information Request

These brief examples show common, practical uses of the form across different payment scenarios.

Optica Ventures example

Optica required a voided check for new vendors to reduce misdirected ACH payments.

Verification cut setup errors by half in three months.
The company maintained a single encrypted vendor file and logged approvals for audit preparedness and faster reconciliations.

Payroll direct deposit

A mid-size employer moved employee banking collection online to centralize direct deposit.

Employees uploaded a voided check or bank letter.
Centralized verification and automated masking reduced payroll exceptions and improved confidentiality handling for employee bank details.

Comparison: signNow and common eSignature providers for collecting bank details

Feature and pricing comparison to evaluate basic plan costs and compliance features relevant to sensitive payment data collection.

	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 trial	Varies	Varies	Varies	Varies
Bulk Send	Yes	Yes	Yes	Yes	No
Audit Trail	Yes	Yes	Yes	Yes	Yes
HIPAA Compliant	Yes	Yes	Yes	No	No
Envelope Cap	No cap	100 envelopes/user/year	Varies	Varies	Varies

Frequently asked questions about Bank Information Requests

Answers to common operational and legal questions when collecting bank account information for payments and payroll.

Need help? Contact support

Is a Bank Information Request legally valid if signed electronically?
Yes. Electronic signatures are legally enforceable under the federal ESIGN Act (15 U.S.C. ch. 96) and state UETA laws in most jurisdictions, provided intent, consent, attribution, and record retention requirements are met.
When should notarization or RON be used?
Notarization is rarely required for a bank info form itself, but use notarization or RON when the receiving institution or a contract explicitly demands a notarized authorization; RON rules vary by state and provider.
How should sensitive bank data be transmitted?
Use encrypted transmission channels (TLS 1.2/1.3), require strict access controls, and avoid unsecured email; mask stored account numbers and keep attachments in encrypted repositories.
What verification reduces fraud risk?
Require a voided check or bank letter, perform micro-deposit verification or bank validation services, and use multistep approvals in finance to confirm authenticity.
How long does verification typically take?
Verification often takes 1–3 business days with document review or micro-deposit confirmation; complex KYC checks can extend processing time.
How do I correct an error on a submitted form?
Void the original record, request a corrected submission from the payee, and document the change and approval in the audit trail to maintain a clear record for auditors.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now