Establishing secure connection…Loading editor…Preparing document…

Payment EFT Page

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

PAYMENT EFT PAGE — GENERAL BUSINESS AGREEMENT

This General Business Agreement (the Agreement) is entered into by and between Client Name: and Service Provider Name: , with an effective date of .

WHEREAS

WHEREAS, Service Provider is engaged in the business of providing the services described in this Agreement and possesses the expertise, personnel and resources necessary to perform those services; and

WHEREAS, Client desires to retain Service Provider to perform such services under the terms and conditions set forth in this Agreement and to authorize electronic funds transfer (EFT) for payment; and

WHEREAS, the parties intend that payments due under this Agreement shall be remitted by automated clearing house (ACH) debit/credit to the banking account designated below, subject to the terms of the EFT Authorization contained herein.

SCOPE OF WORK

PAYMENT TERMS

Contract Amount: $    Payment Schedule:

EFT Processing: Payments shall be processed by electronic funds transfer to the Account designated below. Client consents to the transmission of payment instructions electronically and authorizes Service Provider and its processor to initiate credits or debits to the designated account.

Late Fee: Amounts not paid when due shall incur a late fee of % per month (or the highest lawful rate), calculated monthly on the unpaid balance until paid in full.

TERM AND TERMINATION

Term Commencement Date:    Term Expiration Date:

Either party may terminate this Agreement for convenience upon written notice to the other party at least days prior to the effective termination date. Termination for cause may be immediate where a material breach is not cured within thirty (30) days after written notice of such breach.

CONFIDENTIALITY

Each party shall maintain the confidentiality of Confidential Information disclosed by the other party and shall not disclose such information to any third party except as required by law or as necessary to perform its obligations under this Agreement. "Confidential Information" includes proprietary business information, financial data, trade secrets, customer lists and any non-public technical or business information. Confidential Information does not include information that: (a) is or becomes generally public through no breach by the receiving party; (b) is rightfully obtained from a third party without confidentiality obligations; or (c) is independently developed without use of the disclosing party's Confidential Information.

EFT AUTHORIZATION

Banking Information for Electronic Payments

Account Type:

Routing Number:    Account Number:

Authorization Effective Date:

By signing below, Account Holder certifies that the account information provided above is accurate and that Account Holder is an authorized signer on the designated account. Account Holder authorizes Service Provider, and its designated payment processor, to initiate ACH entries to debit and/or credit the designated account for amounts due under this Agreement and to correct any erroneous transactions by initiating reversing entries as necessary. This authorization remains in effect until Service Provider receives written notice of revocation at least business days prior to the next scheduled transfer.

If a payment is returned for insufficient funds or closed account, Client shall be responsible for any bank charges and a return fee of $ in addition to any late fees specified above.

GOVERNING LAW; ENTIRE AGREEMENT

This Agreement shall be governed by and construed in accordance with the laws of the jurisdiction of , without regard to its conflict of law principles. Any dispute arising under this Agreement shall be resolved in the state or federal courts located in that jurisdiction.

Entire Agreement: This Agreement, together with any exhibits and the EFT Authorization contained herein, constitutes the entire agreement between the parties concerning the subject matter hereof and supersedes all prior and contemporaneous agreements, proposals and communications, whether written or oral. No amendment shall be effective unless in writing and signed by both parties.

REPRESENTATIONS AND WARRANTIES

Each party represents and warrants that it has the full right, power and authority to enter into and perform this Agreement, and that the person signing on behalf of a party is duly authorized to bind that party.

Client Name (Print):

By:

Date:

Service Provider (Print):

By:

Date:

Enter text✕

What the Payment EFT Page Is and When It’s Used

The Payment EFT Page is a standardized authorization and information form used to collect bank account details and explicit consent to send or receive electronic funds transfers (EFT/ACH). It captures account holder and bank routing/account numbers, account type, effective date, and a clearly worded authorization statement. When combined with an auditable electronic signature and system logs, the Payment EFT Page documents intent, consent, and attribution consistent with ESIGN and UETA requirements and supports secure eSubmission to banks, payroll providers, and accounts payable systems.

Why a Proper Payment EFT Page Matters

A complete Payment EFT Page reduces payment exception rates, documents legal consent for ACH debits or credits, and creates an auditable record for reconciliations and compliance. It helps prevent misdirected transfers and supports automated processing by banks and payment platforms.

Why a Proper Payment EFT Page Matters

Who Typically Prepares and Signs a Payment EFT Page

Common users include accounts payable, payroll teams, treasury, and vendors who must send or receive electronic payments.

  • Accounts payable departments — centralize vendor EFT setup and reduce check issuance.
  • Payroll administrators — collect employee direct-deposit data securely and record consent.
  • Vendors and contractors — provide routing numbers and explicit authorization for electronic payments.

The form fits both B2B and B2C contexts where a clear, retained authorization for ACH/EFT activity is required.

Essential Elements Every Professional Payment EFT Page Should Include

Core components make the Payment EFT Page both operational and legally robust for electronic payment workflows, enabling bank validation, consent capture, and auditability.

Account Holder

Enter the full legal name as it appears on bank records; mismatched names commonly cause returns or delay recovery and may trigger backup withholding investigations.

Bank Details

Collect the ABA routing number and account number, and validate them; incorrect digits are a leading cause of failed ACH transactions and reconciliation issues.

Account Type

Specify checking, savings, or business account. Some processors and banks apply different ACH rules or settlement timelines by account type.

Authorization

Include an explicit authorization statement describing permitted debits/credits, recurrence, limits, and revocation steps to document intent and consent.

Effective Date

Record the date authorization begins in MM/DD/YYYY format; this governs when transfers may commence and affects cancellation windows.

Verification

Attach proof such as a voided check, bank letter, micro-deposit confirmation, or API-based bank validation to reduce return risk and support audits.

Step-by-Step: Completing and Submitting a Payment EFT Page

Complete the form, verify bank details, capture signature, and route the signed copy to the responsible payor and your records for settlement and audit.

  • 01
    Collect Information: Gather names, routing number, account number, and account type.
  • 02
    Attach Proof: Upload a voided check, bank letter, or micro-deposit confirmation.
  • 03
    Obtain Signature: Signer signs electronically or on paper; notarize or use RON if required.
  • 04
    Submit to Bank: Send the completed page via secure channel to the payor or bank for ACH initiation.

Configuring an Online EFT Authorization Workflow

Set up validations, signer authentication, and routing to integrate the Payment EFT Page with your finance systems.

Field Configuration
Verification Method Bank API verification or micro-deposit confirmation for account validation.
Authentication Email OTP or multi-factor authentication to link the signer to the authorization.
Routing Automatically send signed PDF to AP system, bank portal, or secure storage.
Retention Store signed copy in a secure archive for audit and retrieval.

How a Completed Payment EFT Page Moves Through Your Process

A typical flow starts with upload, continues through signer validation and bank verification, and ends with ACH initiation and audit capture.

  • Sender Upload: Originator uploads the form and supporting proof.
  • Signer Review: Payee reviews details and signs electronically.
  • Verification: Bank or processor validates routing and account data.
  • Settlement: ACH network processes authorized debit or credit.

Technical Requirements for Electronic EFT Authorizations

Payment EFT Pages require secure transport, AES-256 encryption at rest, TLS 1.2/1.3 in transit, and reliable integration with banking or accounts payable systems.

  • AES Encryption: AES-256 at-rest encryption
  • Transport Security: TLS 1.2 and TLS 1.3
  • Enterprise Integrations: NetSuite, Salesforce, Google Workspace integrations

Required Data Elements to Include on the Payment EFT Page

Account Holder Name: Full legal name
Bank Name: Depository institution name
Routing Number: 9-digit ABA routing number
Account Number: Numeric account identifier
Account Type: Checking or savings
Authorization Statement: Signed consent for EFT

Common Preparation Errors to Avoid

  • Entering an incorrect routing number can send funds to the wrong institution and require lengthy recovery procedures with potential fees.
  • Using informal names instead of full legal names frequently causes bank validation failures and backup withholding triggers.
  • Failing to store signed authorizations securely increases exposure to fraud and noncompliance with audit requirements.
  • Relying on email-only authentication without an audit trail weakens proof of consent under ESIGN and state UETA laws.

Immediate Risks and Financial Consequences

Misrouted Funds: Bank return fees
Unauthorized Transfers: Fraud risk
Backup Withholding: 24% withholding
Regulatory Fines: Civil penalties possible
Late Payments: Interest and fees
Recordkeeping Failures: Compliance risk

Timing and Processing Expectations for EFT Authorizations

Key timelines include when authorizations take effect, how long account verification typically requires, and expected ACH settlement windows.

Authorization Effective Date:

The form date governs when debits or credits may begin and sets cancellation timing.

Verification Window:

Micro-deposit or bank API validation typically completes in 1–3 business days.

Authorization Cancellation:

Allow several business days for cancellation to propagate to the payor and bank.

Bank Processing Time:

ACH settlement commonly takes 1–2 business days after initiation.

Document Retention:

Keep signed records according to applicable retention schedules for audit.

eSignature Pricing and Feature Comparison Relevant to EFT Pages

Compare baseline pricing and common features that affect Payment EFT Page workflows, such as bulk send, audit trails, HIPAA support, and envelope limits.

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 No Yes, limited Yes, limited
Bulk Send Yes Yes Yes Yes No
Audit Trail Yes Yes Yes Yes Yes
HIPAA Compliant Yes Yes Yes No No

Frequently Asked Questions About Payment EFT Pages

Answers to common questions about validity, errors, notarization, revocation, HIPAA, and record retention for Payment EFT Pages.


Need help? Contact support

be ready to get more
Join over 28 million airSlate SignNow users