Can the agreement be e-signed?

Yes. Electronic signatures meet U.S. legal standards when intent, consent, attribution, and retention are present per the ESIGN Act (15 U.S.C. ch. 96) and state UETA rules where applicable.

What if the account number is wrong?

If an incorrect account number is supplied, the bank cannot match and apply the block; incorrect data may delay protection and could expose the account to unauthorized entries until corrected and resubmitted.

How quickly does a bank implement the block?

Implementation timing varies by institution; banks commonly require one to three business days for internal processing and may test or confirm instructions before full enforcement.

Is notarization required?

Not generally required for ACH blocks, although some banks or corporate policies may request notarized signatures for high-value accounts or unfamiliar corporate entities.

Who enforces blocked entries?

The financial institution programs account filters and returns or rejects matching ACH items per the routing rules and internal procedures; originators receive return codes when items are blocked.

How do I cancel a block?

Submit a written revocation to the bank signed by an authorized representative; follow bank-specific procedures for timing and confirmation to ensure the revocation takes effect.

Electronic Signature
Templates
Finance
ACH Block Agreement

ACH Block Agreement

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

ACH Block Agreement

This ACH Block Agreement (Agreement) is entered into by and between Originator Name: and Depository Financial Institution Name: . The parties agree as follows.

1. Identification

Originator (Company) Legal Name Originator Address Originator ACH Company ID / Originating Company Identification Depository Financial Institution (ODFI) Address

2. Accounts and Identifiers

Account Number(s) Subject to Block Routing / ABA Number of Originating Bank (if applicable)

3. Block Instructions

The Depository Financial Institution shall block ACH entries as specified below. Block applies to entries presented to the account(s) listed above beginning Effective Date:

Block Type (select all that apply)

Block ACH debits (debit entries)
Block ACH credits (credit entries)
Block only entries matching criteria below

Specific Blocking Criteria (if applicable)

Duration of block: .

4. Fees and Charges

Originator acknowledges and agrees to pay fees associated with implementation, maintenance, and research of blocked items as set forth by the Depository Financial Institution. Fees may include per-item research charges, per-block setup fees, and monthly maintenance fees if applicable. Specify agreed fees or reference fee schedule:

5. Authority, Representations and Warranties

Originator represents and warrants that it has full authority to request the block(s) described in this Agreement and that the information provided herein is true and complete. Originator authorizes the Depository Financial Institution to implement blocking procedures in accordance with this Agreement and applicable ACH operating rules and laws. Originator further represents that it will notify the Depository Financial Institution promptly of any change in the account ownership or in the facts that formed the basis for this block instruction.

6. Depository Financial Institution's Obligations

The Depository Financial Institution will use commercially reasonable procedures to identify and block entries consistent with the instructions and criteria set forth in this Agreement. The institution's obligation is limited to actions within the ordinary course of its ACH processing operations and does not guarantee that all specified entries will be blocked under all circumstances. The institution will notify Originator of any items that are blocked, returned or investigated.

7. Originator Responsibilities

Originator shall provide complete and accurate identifying information and criteria necessary to effectuate the block. Originator shall maintain adequate records and shall cooperate with the Depository Financial Institution in any investigation, including providing supporting documentation for disputed entries. Originator remains responsible for monitoring account activity and is responsible for any loss resulting from failure to provide accurate or timely information.

8. Indemnification and Limitation of Liability

Originator agrees to indemnify, defend and hold harmless the Depository Financial Institution and its affiliates, officers and employees from any and all claims, losses, liabilities, costs and expenses (including reasonable attorneys' fees) arising out of or related to implementation of this Agreement, including but not limited to claims resulting from blocked items, returned items, or errors attributable to Originator's instructions. Except for willful misconduct or gross negligence, the Depository Financial Institution's liability for any claim arising from this Agreement shall be limited to direct actual damages and shall not include consequential, special or punitive damages.

9. Termination and Modification

Either party may terminate or modify this Agreement upon written notice to the other party. Termination will be effective in a commercially reasonable time period to allow the Depository Financial Institution to process outstanding ACH files in its possession. Modifications to blocking criteria must be provided in writing and accepted by the Depository Financial Institution before they become effective.

10. Notices

Notices under this Agreement shall be sent to the contacts provided below. Notice is effective upon receipt by the receiving party.

Originator Contact Name Originator Contact Phone Originator Contact Email Depository Institution Contact Name Depository Contact Phone Depository Contact Email

11. Miscellaneous

This Agreement constitutes the entire agreement between the parties with respect to ACH blocking services and supersedes all prior agreements and understandings. If any provision of this Agreement is held invalid or unenforceable, the remaining provisions shall remain in full force and effect. This Agreement shall be governed by applicable law and the parties shall comply with applicable ACH operating rules and regulations.

Additional Terms or Notes

Originator:

By:

Date:

Depository Institution:

By:

Date:

What an ACH Block Agreement Is and when it applies

An ACH Block Agreement is a written instruction used to prevent Automated Clearing House (ACH) entries from being posted to a specified bank account or to limit ACH activity from particular originators. Typically executed between an account holder and their financial institution, the document identifies accounts, specifies the types of ACH debits or credits to block, and establishes effective dates and authorized signatories. Organizations use these agreements to manage fraud risk, implement NACHA rule-based controls, and document the bank's authorization to apply transaction filters or return routing instructions for blocked items.

Why an ACH Block Agreement matters for risk and control

An ACH Block Agreement reduces exposure to unauthorized debits, clarifies the bank's filtering obligations, and creates a record of consent and instructions for the financial institution.

Typical users and parties involved

These parties share responsibility for accurate account data, timely notifications, and documented authorizations to ensure the block functions as intended.

Banks and credit unions managing client account controls and ACH rule compliance.
Businesses with high-volume receivables or payroll teams seeking to prevent unwanted debits.
Third-party processors and treasury departments coordinating originator blocking and exception handling.

Step-by-step: completing an ACH Block Agreement

Follow a clear sequence to collect details, confirm identity, and deliver the instruction to the bank.

01

Gather details: Collect account and routing numbers, originator IDs, and block scope.
02

Specify block: Indicate debit/credit types, ACH classes, and explicit originators to block.
03

Authenticate: Attach ID, corporate resolution, or other bank-required verification documents.
04

Submit to bank: Send signed agreement to the bank’s ACH or treasury operations team.

Common questions and practical answers

Answers to frequent operational, legal, and timing questions about ACH Block Agreements.

Need help? Contact support

Can the agreement be e-signed?
Yes. Electronic signatures meet U.S. legal standards when intent, consent, attribution, and retention are present per the ESIGN Act (15 U.S.C. ch. 96) and state UETA rules where applicable.
What if the account number is wrong?
If an incorrect account number is supplied, the bank cannot match and apply the block; incorrect data may delay protection and could expose the account to unauthorized entries until corrected and resubmitted.
How quickly does a bank implement the block?
Implementation timing varies by institution; banks commonly require one to three business days for internal processing and may test or confirm instructions before full enforcement.
Is notarization required?
Not generally required for ACH blocks, although some banks or corporate policies may request notarized signatures for high-value accounts or unfamiliar corporate entities.
Who enforces blocked entries?
The financial institution programs account filters and returns or rejects matching ACH items per the routing rules and internal procedures; originators receive return codes when items are blocked.
How do I cancel a block?
Submit a written revocation to the bank signed by an authorized representative; follow bank-specific procedures for timing and confirmation to ensure the revocation takes effect.

Consequences and operational risks to watch for

Returned ACH Fees: Account and bank chargebacks

Service Disruption: Missed payments or payroll delays

Regulatory Exposure: Noncompliance with NACHA rules

Customer Disputes: Increased inquiries and chargebacks

Contract Breach: Supplier or vendor covenant risks

Implementation Delay: Operational and reconciliation burdens

Security and compliance controls to include

Encryption: TLS 1.2/1.3; AES-256 at rest

Audit Trail: Timestamps, IPs, action history

Access Controls: Role-based access and admin logs

Authentication: Multi-factor options and verify IDs

HIPAA BAA: Required for PHI workflows

Retention Export: Secure export and long-term storage

Common mistakes that cause delays or failures

Submitting incomplete account information such as truncated account numbers or missing routing digits, which prevents the bank from matching and applying the block.
Failing to define block scope precisely — omitting ACH class or originator IDs can lead to overbroad or ineffective blocking actions.
Not confirming the signatory's authorization or corporate resolutions, causing the bank to reject the instruction until proper authorization is provided.
Expecting immediate enforcement without accounting for bank processing windows, testing, or batch update cycles that can add several business days.

Operational flow: from agreement to enforced block

A straightforward workflow helps ensure the bank applies the requested ACH filtering correctly and on schedule.

Prepare agreement: Document account details and block parameters.
Verify identity: Provide IDs, corporate resolution, or bank-required proof.
Bank programs filter: Bank configures rules or return instructions.
Confirm enforcement: Bank sends confirmation and follow-up details.

Recommended digital workflow settings for ACH Block Agreements

Configure fields and routing so the bank receives a complete, auditable instruction set in a single submission.

Field	Configuration
Block Type	Debit \| Credit \| Both (choose precisely)
Effective Date	MM/DD/YYYY format; bank may require lead time
Authentication	Multi-factor or bank ID verification
Notification	Email and written bank confirmation

Digital submission and file format considerations

Confirm bank ingestion requirements and include an audit trail to show signature attribution and delivery for compliance and dispute resolution.

Integrations: Salesforce, NetSuite, Microsoft 365
File formats: PDF, DOCX, HTML, Excel
Authentication options: Email link, SMS code, KBA

Timing expectations and processing windows

Know typical timeframes so you set accurate expectations with the bank and internal stakeholders.

Preparation time:

Same day to several days depending on approvals

Bank processing window:

Often 1–3 business days to program or test

Notification period:

Bank may send confirmation within 1–5 business days

Effect on transactions:

Blocks apply to incoming clearing cycles after enforcement

Testing and validation:

Allow runs to confirm blocked items behave as expected

Key milestones from submission to active blocking

Track these sequential stages so internal teams and the bank align on responsibilities and timing.

01

Draft and approve

Internal review, obtain authorized signatures and supporting documents.

02

Submit to bank

Deliver signed agreement and identity verification to bank operations.

03

Bank verification

Bank confirms data and programs the ACH filter or return logic.

04

Block active

Bank begins returning or rejecting matching ACH entries.

How an ACH Block Agreement compares with a Stop Payment Order

Use this table to distinguish persistent account-level blocking from single-transaction stop payment actions.

Criteria	ACH Block Agreement	Stop Payment Order
Scope	account-level, ongoing	single item, one-time
Duration	indefinite until revoked	limited to specific item
Bank action	filter/return logic applied	return single item only
Use case	prevent repeated debits	stop an identified transaction

Typical eSignature vendor pricing and feature snapshot for ACH-related forms

Pricing and feature availability vary by vendor and plan; signNow appears first to reflect plan and cost options for electronic execution.

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

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now