Are eSignatures valid on a PAD?

Yes. Electronic signatures are legally effective under the ESIGN Act (15 U.S.C. §7001) and UETA in most states if you document intent, obtain consent, attribute the signature to the signer, and retain an accessible record.

How can a payer revoke authorization?

A payer may typically revoke in writing or per the agreement’s stated procedure; specify notice period in the PAD. Banks may also require time to process revocation before debits stop.

What if a debit is returned for insufficient funds?

Follow processor and bank return protocols, notify the payer, attempt retries per your policy, and apply the stated NSF fee if permitted by the agreement.

When is notarization required?

Notarization is rarely required for PADs but may be required by state or contracting counterparties; check local practice and any lender or escrow requirements.

What records should I retain?

Keep the signed agreement, audit trail, verification evidence, and communication records. Retain per IRS and HIPAA minimums where applicable and longer for commercial disputes.

How to handle incorrect bank details?

Notify the payer, secure corrected information with verification, correct the PAD record, and document the change to maintain an unbroken audit trail.

Electronic Signature
Templates
Finance
Financial PAD Agreement

Financial PAD Agreement

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

FINANCIAL PAD AGREEMENT

Parties

Payee (Company):

Payee Address Payee Contact

Payer (Account Holder)

Payer Name Payer Address Payer Contact

Authorization

By executing this Financial PAD Agreement the Payer authorizes the Payee to initiate pre-authorized debits (PADs) from the bank account specified below for payment of amounts owing under the payment instructions set forth in this Agreement. The Payer acknowledges that this authorization is provided for the benefit of the Payee and the financial institution that processes debits in accordance with applicable clearing rules.

Authorization Type (select one)

One-time debit Recurring debits Debits as invoices become due

Payment Instructions

Payment Amount: Frequency:

Commencement Date: End Date (if any):

Maximum Cumulative Amount (optional) Reference / Invoice Number

Bank Account Details

Financial Institution Name

Account Number Account Holder (as shown on the account) Account Type

Chequing Savings

Notice, Cancellation and Changes

The Payer may revoke this authorization at any time by delivering written notice to the Payee. Revocation will be effective only after the Payee has had a reasonable opportunity to act on it. The Payer agrees to provide at least days' prior written notice for cancellation or change of the debit schedule unless otherwise agreed in writing.

Representations, Warranties and Indemnity

The Payer represents and warrants that it is the lawful account holder or is otherwise authorized to provide the bank account information and to authorize debits from the specified account. The Payer will promptly notify the Payee of any change in banking instructions and will indemnify and hold harmless the Payee from any loss, claim, or liability arising from inaccurate account information or failure to notify the Payee of changes.

Disputes and Liability

The Payer has certain recourse rights in the event a debit is not authorized or is incorrect. In the event of a dispute regarding a debit, the Payer will notify the Payee in writing and both parties will cooperate to resolve the matter in good faith. The Payee's liability for any erroneous debit shall be limited to correcting the error and reimbursing the Payer for fees charged by the financial institution resulting directly from the error.

Privacy and Confidentiality

The Payee will collect, use and disclose personal and financial information only as reasonably required to process debits under this Agreement and to comply with applicable financial institution requirements. Both parties agree to keep confidential account information except as required for processing or by law.

Additional Terms or Special Instructions

Certifications

By signing below the Payer certifies that the information provided in this Agreement is true and correct, that the Payer has authorized the Payee to debit the designated account in accordance with the terms above, and that the Payer will notify the Payee in writing of any changes to the account that may affect processing. The Payee certifies it will only process debits in accordance with the terms of this Agreement and applicable clearing rules.

A copy of this signed Agreement will be retained by the Payee and provided to the Payer upon request.

Payer (Account Holder):

Printed Name:

By:

Date:

Payee (Company):

Printed Name:

By:

Date:

What a Financial PAD Agreement Is and when it’s used

A Financial PAD Agreement (Pre‑Authorized Debit Agreement) documents a payer's authorization for recurring or one‑time electronic debits from a bank account or payment card. It names the payor and payee, specifies the account and routing details, sets payment frequency and amount, and explains cancellation and dispute rights. Properly executed, a PAD creates a clear record of consent, supports ACH or card processing, and supplies the evidence needed for banks and payment processors to apply debits according to NACHA rules. Electronic execution under ESIGN and UETA is generally acceptable when intent, consent, attribution and retention requirements are met.

Why using a clear Financial PAD Agreement matters

A well‑drafted PAD Agreement reduces billing disputes, documents explicit authorization, protects payers and payees, and streamlines recurring payment setup. It also supplies the audit trail needed for dispute resolution and regulator requests while aligning with ESIGN/UETA standards for electronic consent and retention.

Common users and signer roles for PAD agreements

Organizations and individuals who collect recurring payments rely on PAD Agreements to secure written authorization before initiating debits.

Utilities and subscription services collecting recurring monthly payments, scheduling ACH debits tied to invoices or memberships.
Financial institutions and lenders establishing automatic loan payments, interest charges, or payment plans tied to a customer account.
Healthcare and insurance providers setting up recurring co‑pays, premiums, or patient payment plans where bank authorization is required.

The agreement clarifies who may initiate debits, allowable amounts and dates, cancellation procedures, and record retention responsibilities for all parties.

Essential elements to include in a professional Financial PAD Agreement

Include precise authorization language, payment schedule, bank details, cancellation rights, error/dispute procedures, and compliance statements to make a PAD enforceable and operational.

Authorization clause

Clear, unambiguous consent to debit the specified account for stated amounts and frequencies, with language enabling ACH or card processor initiation.

Payment schedule

Define dates, frequency, amount ranges, and start/end conditions so both parties understand timing and variability of debits.

Bank account details

Collect routing number, account number, account type, and verification method (voided check or micro‑deposits) to reduce return risk.

Cancellation and revocation

Specify how a payer can revoke authorization, required notice period, and the effect of revocation on future debits.

Dispute and error process

Describe time limits for disputing a debit, steps to notify the payee, and return procedures per NACHA and bank policy.

Legal and compliance language

Include ESIGN/UETA consent language, data privacy references, and any required consumer disclosure for electronic records.

Stepwise process to complete and activate a PAD Agreement

Follow this four‑step sequence to collect authorization, verify account data, and enable processing.

01

Prepare agreement: Populate payer/payee details, payment terms, and retention clauses.
02

Collect bank details: Gather routing/account numbers and a voided check or perform micro‑deposit verification.
03

Obtain consent: Have the payer sign and date the PAD; capture electronic consent if using eSignature.
04

Activate and record: Transmit to processor, schedule debits, and retain the executed record for audits.

Configuring an online PAD workflow

Key settings to configure for secure, auditable eSubmission and recurring payment automation.

Field	Configuration
Authentication method	Email link, SMS code, or stronger KBA per risk appetite
Payment verification	Micro‑deposits or instant account verification (ACH tokenization)
Retry and failure logic	Set retry attempts, retry intervals, and notification steps
Notification settings	Email receipts, upcoming debit alerts, and failed payment notices

Operational flow from agreement to debit

A typical operational sequence from signed authorization to completed payment and record capture.

Send agreement: Deliver PAD for signature via secure link or in person.
Signer authenticates: Signer verifies identity and provides bank details.
Processor initiates debit: ACH or card processor schedules and executes the payment.
Record retention: Store signed agreement and audit trail for dispute resolution.

Technical and integration considerations for eSubmission

Ensure the signing platform supports secure authentication, audit trails, and required file formats before eSubmitting PADs.

Integrations: Salesforce, NetSuite, Microsoft 365, Google Workspace
File formats: PDF, DOCX, HTML accepted
Security protocols: TLS in transit; AES‑256 at rest

Confirm the platform can produce a tamper‑evident signed record with timestamps, IP data, and signer attribution for regulatory audits.

Security, encryption, and compliance checkpoints

Transport encryption: TLS 1.2/1.3

Data at rest: AES‑256 encryption

Audit trail: Complete timestamped event log

Regulatory compliance: ESIGN | UETA

Industry standards: SOC 2 Type II | ISO 27001

Healthcare BAA: HIPAA available with BAA

Key penalties and risks to avoid with PAD Agreements

Bank return fees: Variable; subject to bank policy

Backup withholding: 24% if missing or incorrect TIN

Unauthorized debit liability: Potential payer claims and reversals

Regulatory fines: Compliance penalties for poor retention

Contract disputes: Ambiguous amounts invite litigation

Processor chargebacks: Possible additional fees and holds

Timing, effective dates and notice periods to include

Define effective dates, authorization windows, and statutory or contractual notice periods to reduce disputes.

Effective date:

Date when debits may begin; use MM/DD/YYYY.

Cancellation notice:

Specify payer notice period, commonly 3–30 days.

Dispute window:

State time allowed to contest a debit.

Authorization duration:

Fixed term or until revoked by payer.

Record retention:

Specify how long signed records will be retained.

eSignature vendor pricing and capability snapshot for PAD workflows

Compare base starting prices and core features relevant to recurring payment authorizations and secure PAD handling.

	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	Varies by plan	Varies by plan	Varies by plan	Varies by plan
Bulk Send	Yes (Business Premium)	Yes	Yes	Yes	Yes
Audit Trail	Yes	Yes	Yes	Yes	Yes
HIPAA Compliant	Yes (BAA available)	Yes	Yes	No	No

Practical tips for accurate and efficient PAD completion

Adopt these practices to reduce returned payments, disputes, and manual reconciliation work.

Verify account data

Confirm routing and account numbers with a voided check or micro‑deposit verification before initiating the first debit to avoid NSF returns and bank fees.

Record consent clearly

Capture and retain a dated, signed authorization with explicit language about amounts, frequency, and cancellation rights to support dispute defense.

Use secure authentication

Implement at least email plus an additional verification step (SMS code or KBA) for higher‑risk payments to strengthen signer attribution.

Define failure procedures

Document retry attempts, notification cadence for failed debits, and how fees or interest will be handled to set payer expectations.

Frequently asked questions about Financial PAD Agreements

Common operational and legal questions about PADs, electronic signatures, revocation, and dispute handling with concise answers.

Need help? Contact support

Are eSignatures valid on a PAD?
Yes. Electronic signatures are legally effective under the ESIGN Act (15 U.S.C. §7001) and UETA in most states if you document intent, obtain consent, attribute the signature to the signer, and retain an accessible record.
How can a payer revoke authorization?
A payer may typically revoke in writing or per the agreement’s stated procedure; specify notice period in the PAD. Banks may also require time to process revocation before debits stop.
What if a debit is returned for insufficient funds?
Follow processor and bank return protocols, notify the payer, attempt retries per your policy, and apply the stated NSF fee if permitted by the agreement.
When is notarization required?
Notarization is rarely required for PADs but may be required by state or contracting counterparties; check local practice and any lender or escrow requirements.
What records should I retain?
Keep the signed agreement, audit trail, verification evidence, and communication records. Retain per IRS and HIPAA minimums where applicable and longer for commercial disputes.
How to handle incorrect bank details?
Notify the payer, secure corrected information with verification, correct the PAD record, and document the change to maintain an unbroken audit trail.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now