Authorization to Debit Account Template

In plain language: Identifies the account holder authorizing the draw and the payee (company) receiving it, along with the account and routing numbers of the account to be debited.

Common mistake: Collecting only the last four digits of the account number for privacy, then being unable to process the transaction. The full account number is required by the ODFI to originate an ACH entry.

In plain language: States clearly whether the authorization covers a single draw or an ongoing series of debits, and specifies the frequency (weekly, monthly, quarterly) for recurring authorizations.

Common mistake: Leaving the scope ambiguous by checking neither box or failing to specify the recurrence frequency. A processor that initiates additional draws beyond what the account holder intended will face R10 returns and possible NACHA violation findings.

In plain language: Specifies the exact dollar amount of each draw, or for variable-amount authorizations, the method by which the amount will be calculated, along with the processing date.

Common mistake: Omitting the advance-notice requirement for variable-amount debits. NACHA requires at least 10 days' advance notice when the debit amount changes, and failure to provide it gives the account holder grounds to dispute the draw.

In plain language: Gives the account holder the option to receive a zero-dollar test entry or written notice before the first live draw, allowing them to confirm account details are correct.

Common mistake: Skipping pre-notification entirely for new account enrollments. A failed first draw due to incorrect account details generates a return fee, delays payment, and may trigger a NACHA reportable return-rate threshold.

In plain language: Tells the account holder how to cancel the authorization and how much advance notice is required before the next scheduled draw to stop it from processing.

Common mistake: Setting the revocation notice period to more than 3 business days for consumer ACH entries. NACHA Subsection 2.3.2 mandates a maximum of 3 business days for consumer accounts — a longer contractual requirement is unenforceable.

In plain language: Explains the account holder's right to dispute an unauthorized or incorrect draw and the timeframe within which the bank will process a return.

Common mistake: Stating a dispute window shorter than the NACHA standard of 60 calendar days from the settlement date for consumer accounts. Shortening this window in the authorization does not override the bank's obligation to honor a timely return request.

In plain language: The account holder confirms they are an authorized signer on the account, the account is in good standing, and they have the authority to grant this debit permission.

Common mistake: Omitting this clause and later being unable to recover funds from a draw disputed on the grounds that the signatory was not an authorized account signer — a defense that succeeds when the ODFI cannot show a valid authorization was in place.

In plain language: Sets out how changes to the debit amount, frequency, or schedule will be communicated to the account holder before taking effect.

Common mistake: Providing no modification clause at all and then changing the debit amount without notice. This generates R10 unauthorized-return codes, puts the ODFI's return rate at risk, and exposes the company to NACHA sanctions.

In plain language: States which jurisdiction's law governs the authorization and confirms that all draws will be processed in compliance with the applicable payment scheme rules.

Common mistake: Omitting the NACHA or scheme-rules reference entirely. Without it, the payee cannot invoke the scheme's dispute and return procedures if the account holder's bank challenges the authorization.

In plain language: Records the account holder's wet or electronic signature, printed name, and the date the authorization was executed — required by NACHA and all major direct debit schemes as proof of consent.

Common mistake: Accepting a typed name in an email as the authorization signature without an explicit agreement that electronic signatures are valid under E-SIGN or the applicable jurisdiction's electronic-signature law. A challenged draw with no valid signature record is effectively an unauthorized debit.

An authorization to debit account is a signed document in which a bank account holder gives a third party — typically a business — permission to withdraw funds directly from their bank account. It specifies whether the draw is one-time or recurring, the amount and schedule, and the account holder's rights to revoke the authorization. Without a valid, signed authorization on file, any debit initiated is considered unauthorized under NACHA rules, SEPA regulations, and most national payment scheme rules.

Yes, in virtually all major payment schemes. NACHA requires originators to obtain a signed or electronically authenticated authorization before initiating any ACH debit entry. SEPA mandates a signed mandate document before any SEPA Direct Debit can be processed. The UK Direct Debit scheme requires an Instruction to your bank before draws begin. In Canada, Payments Canada Rule H1 requires a written PAD agreement. Operating without one exposes the payee to unauthorized-return claims, ODFI sanctions, and potential liability for the full debited amount.

Both documents accomplish the same goal — written account-holder consent for direct bank draws — but under different rules. ACH authorizations are governed by NACHA and apply to US dollar transactions between US bank accounts. SEPA mandates are governed by the European Payments Council, apply to euro-denominated transactions across 36 countries, and require a unique mandate reference number on every draw. Disclosure language, notice periods, and revocation rights differ between the two schemes, so a single form cannot satisfy both.

Yes. Under NACHA rules, an account holder may revoke a consumer ACH authorization at any time by providing written notice to the payee at least 3 business days before the next scheduled draw. SEPA mandates can also be cancelled, typically with notice to both the creditor and the account holder's bank. Revocation does not, however, cancel any underlying payment obligation — it only removes the bank-draw mechanism. The payee must then seek payment through other means.

The account holder's bank can return the entry using return code R10 (customer advises not authorized) within 60 calendar days of the settlement date for consumer accounts. The ODFI is required to pass the return back to the originator, who must refund the amount. Repeated unauthorized returns above NACHA's 0.5% threshold can result in the ODFI suspending the originator's ACH access. In severe cases, the payee may also face regulatory action and civil liability.

NACHA requires originators to retain authorization records for 2 years from the date of the last entry processed under that authorization. SEPA mandates must be retained for 14 months after the last transaction under most national scheme implementations, though some creditor banks require longer. Best practice is to retain all signed authorizations for at least 3 years to cover audit cycles and any delayed dispute windows.

Generally yes, provided the signature was obtained through a method that meets the requirements of the applicable electronic-signature law — E-SIGN and UETA in the US, the Electronic Commerce Act in Canada, eIDAS in the EU, and the Electronic Communications Act in the UK. A typed name in an email, without an audit trail and explicit consent to electronic authorization, typically does not satisfy NACHA or SEPA requirements. Use a compliant e-signature platform that generates a timestamped audit log.

Under NACHA rules, an originator must provide at least 10 business days' advance notice to the account holder before drawing an amount that differs from the authorized amount. In Canada, Payments Canada Rule H1 requires at least 30 days' notice for changes to a personal PAD. SEPA requires advance notice of at least 14 calendar days before the due date of a modified draw under the Core scheme. Building this notice step into billing workflows before modifying any recurring draw is essential to avoiding unauthorized-return codes.

Not reliably. Each major payment scheme — NACHA, Payments Canada PAD, UK Direct Debit, and SEPA — requires specific disclosure language, revocation rights, and notice periods that differ from one another. A single form written to satisfy all four will almost certainly omit mandatory language for at least one jurisdiction, making it non-compliant. Businesses collecting from account holders in more than one country should maintain jurisdiction-specific authorization templates reviewed annually against current scheme rules.