Can a SEPA mandate be e-signed in the U.S.?

Yes. U.S. e-signature laws (ESIGN Act, 15 U.S.C. ch. 96) and UETA permit electronic signatures where parties consent. Ensure the electronic workflow captures intent, attribution, consent, and retention to meet ESIGN and UETA requirements.

How does a debtor revoke a mandate?

A debtor may revoke authorization by notifying their bank and the creditor; process and timing depend on the bank and SEPA rules. Document the revocation, stop future debits, and reconcile any outstanding transactions promptly.

What if the IBAN is wrong?

Incorrect IBANs commonly cause failed debits and bank return fees. Validate IBAN format before submission and maintain a remediation workflow to obtain corrected details from the debtor.

Do I need a notary or witness?

Most states do not require notarization or witnesses for payment mandates. If an agent signs on behalf of a company, retain proof of signing authority; check state or contractual rules if in doubt.

How long should I keep signed mandates?

Retain mandates for business needs plus applicable regulatory periods. For tax-related retention follow IRC §6501(a) and for healthcare records follow 45 CFR §164.530(j) where PHI is involved.

Which authentication method should I use?

Use email plus SMS or stronger identity verification for higher-risk or high-value mandates. Maintain an audit trail showing authentication steps to reduce dispute risk.

Payment SEPA Mandate

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

Payment SEPA Mandate

WHEREAS

Whereas Creditor: (Creditor Identifier: ) intends to collect payments by SEPA Direct Debit.

Whereas Debtor: authorizes the Creditor to initiate debits from the Debtor's bank account identified below under the SEPA Core Direct Debit scheme.

Whereas the parties wish to record the terms of that authorization, including the mandate reference, amounts and payment schedule, and the Debtor's rights in relation to refunds and revocation.

Creditor Details

Creditor Legal Name Creditor Identifier Creditor Address

Debtor (Payer) Details

Debtor Full Legal Name Debtor Address IBAN BIC (optional)

Mandate Details

Mandate Reference:

Purpose / Scope of Collections

Type of Payment: Recurrent One-off

Payment Terms

Amount to be Debited Currency Payment Schedule / Frequency

First Collection Date: Final Collection Date (if any):

Late Payment Fee / Charge (if applicable)

Mandate Authorization

By signing this mandate the Debtor authorises the Creditor to send instructions to the Debtor's bank to debit the account identified above and the Debtor's bank to debit the account in accordance with the instruction. The Debtor acknowledges that rights to a refund exist under the terms of the SEPA Core Direct Debit scheme where applicable and that such rights are subject to the conditions set out in this mandate and applicable law.

Refunds and Revocation

The Debtor may request a refund from their bank under the rules of the SEPA Core Direct Debit scheme. Such a request must be made within the timeframe established by the applicable scheme rules and local law. The Debtor may revoke this mandate by providing a written notice to the Creditor; revocation will not affect debits already lawfully initiated under this mandate prior to the Creditor's receipt of such notice.

Confidentiality

Each party shall keep confidential all non-public information obtained in connection with this mandate and shall not disclose such information except to the extent required by law, a competent authority, or for the purpose of executing the SEPA direct debit instructions and related reconciliations.

Governing Law

This mandate shall be governed by and construed in accordance with the laws governing the SEPA scheme and, where not pre-empted by scheme rules, by the laws of the jurisdiction in which the Debtor's bank is located. Any disputes arising from this mandate shall be resolved by the competent courts of that jurisdiction unless otherwise required by mandatory law.

Entire Agreement

This mandate, together with any documents expressly referred to herein, constitutes the entire agreement between the parties in respect of the subject matter and supersedes all prior agreements, understandings and negotiations, whether written or oral.

Debtor Printed Name:

Signature:

Date:

What the Payment SEPA Mandate Is and when it’s used

A Payment SEPA Mandate is an authorization that a payer (debtor) gives to a creditor to collect euro-denominated direct debits under the Single Euro Payments Area (SEPA) scheme. The mandate records the payer’s IBAN, mandate reference, creditor identification, and explicit consent for recurring or one-off debit instructions. While the mandate is a European payment instrument, U.S.-based organizations collecting euros or managing European customers use the mandate form as a contracting and authorization document; e-signature and recordkeeping rules in the United States (ESIGN, UETA) govern the validity of a U.S.-executed electronic mandate.

Why a clear SEPA mandate matters for payments

A properly completed SEPA mandate provides a clear legal basis for debits, reduces the risk of bank chargebacks and disputes, and ensures both sides understand collection frequency and revocation rights. Proper documentation also streamlines reconciliation and audit processes for cross-border euro collections.

Who commonly completes Payment SEPA Mandates

Organizations and individuals who collect euro payments or manage European customer billing complete SEPA mandates; both creditor and debtor information is required.

European creditors and banks initiating direct debits in EUR.
U.S. exporters, SaaS providers, and marketplaces billing EU customers in euros.
Accountants and treasury teams reconciling recurring euro collections.

The mandate is used when a creditor initiates SEPA Direct Debit (core or B2B) collections and must be retained as proof of authorization.

Primary signer roles

Creditor — Authorized Representative

An employee or agent authorized to collect payments signs on behalf of the creditor and confirms Creditor ID and mandate reference; ensure contract authority and role are documented internally.

Debtor — Account Holder

The named bank account holder must provide name, IBAN, address, and signature; mismatches between account holder name and IBAN can cause rejections or bank returns.

Core elements to include on a professional SEPA mandate

A complete mandate combines identification, banking details, collection type, authorization text, and signature elements so banks and creditors can process direct debits and handle disputes.

Mandate Reference

A unique alphanumeric reference assigned by the creditor to identify this authorization across transactions and reconciliation reports; include consistent formatting for automated matching.

Creditor Name and ID

Full legal name of the creditor and, where applicable, the creditor identifier assigned by the bank or PSP; this ties the mandate to the collecting party.

Debtor IBAN and BIC

International Bank Account Number (IBAN) and optional BIC/SWIFT code for cross-border routing; accurate IBAN is essential to avoid failed debits and bank return charges.

Type of Collection

Specify whether the authorization covers recurrent debits, one-off debits, or both, and indicate SEPA Core or SEPA B2B where relevant to define refund and dispute windows.

Authorization Statement

Clear language reflecting the debtor’s consent to permit the creditor to initiate SEPA direct debits and to instruct the debtor’s bank to honor them.

Signature and Date

Signed by the account holder (or authorized agent) and dated; for e-signed mandates include evidence of intent, attribution, and retention to meet ESIGN/UETA criteria.

Step-by-step: filling and issuing a Payment SEPA Mandate

Follow these steps to create, capture, and store a valid SEPA mandate for recurring or one-off euro direct debits.

01

Prepare document: Populate creditor details, mandate reference, and authorization text.
02

Collect bank details: Obtain debtor IBAN and optional BIC; confirm account holder name.
03

Obtain signature: Get handwritten or e-signature from the account holder with date.
04

Store and reconcile: Keep mandate copy and use reference for each debit reconciliation.

Typical processing flow after mandate execution

After a mandate is signed, the creditor and bank use its data to authorize, submit, and reconcile SEPA direct debit transactions.

Authorization: Creditor assigns mandate reference and records consent.
Submission: Bank or PSP receives direct debit requests tied to the mandate.
Clearing: Payments settle through SEPA clearing mechanisms between banks.
Reconciliation: Creditor matches settled transactions to mandate reference for accounting.

Configuring an online SEPA mandate workflow

Set up fields, authentication, and automated reminders when digitizing the SEPA mandate to reduce errors and speed collections.

Field	Configuration
IBAN field	Validate format; use automatic detection or regex check
Mandate reference	Auto-generate unique code per customer
Signer authentication	Email + SMS code or stronger ID verification
Retention settings	Store signed PDF and audit trail for specified period

Technical needs for e-signing and e-submission

Ensure your e-signature platform supports required formats, authentication, and secure storage before issuing electronic SEPA mandates.

Supported formats: PDF and DOCX accepted by most banks and PSPs
Authentication: Email + SMS code or stronger methods recommended
Integrations: CRM and ERP connectors speed reconciliation

Comparing e-signature costs and core features for mandate capture

Basic vendor and plan comparisons help estimate recurring e-signature costs and feature availability for collecting and storing SEPA mandates; signNow appears first per vendor comparison rules.

	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	Yes	Yes	Yes	No
Audit Trail	Yes	Yes	Yes	Yes	Yes
HIPAA Compliant	Yes	Varies	Varies	Varies	Varies

Security and compliance considerations for electronic mandates

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

Audit Trail: Detailed timestamps, IPs, action logs

Authentication: Email, SMS code, or advanced methods

HIPAA BAA: Available when handling health information

Regulatory Certs: SOC 2, ISO 27001, PCI DSS, 21 CFR Part 11

Retention Controls: Configurable retention and export options

Common penalties and transaction risks to avoid

Bank Returns: Failed debit fees and return charges

Chargebacks: Debtor disputes can trigger refunds

Incorrect IBAN: Leads to rejected or misrouted payments

Insufficient Consent: Disputes if authorization is unclear

Data Protection: GDPR or privacy violations risk fines

Recordkeeping: Loss of mandate evidence impairs defenses

Frequent preparation errors to watch for

Typographical errors in IBAN or account holder name cause bank rejections and delays.
Missing or inconsistent mandate reference prevents automated reconciliation across debits.
Unclear collection frequency leads to customer disputes and refund requests.
Insufficient evidence of signer intent increases the likelihood of chargebacks.

Real-world examples of SEPA mandate use

These short examples show how different organizations use a mandate for recurring euro collections.

Export SaaS Billing

A U.S. SaaS company bills EU customers in euros and collects mandates to enable monthly direct debits.

They include unique mandate references per customer for reconciliation.
Retaining signed mandates and audit trails simplifies refund disputes and supports accounting for cross-border revenue recognition.

Property Management

A multinational property manager obtains mandates from tenants with euro accounts for rent.

Each lease number is recorded as the mandate reference.
Storing mandates centrally and validating IBANs before first debit reduces failed collections and administrative overhead.

Timing and processing expectations for mandates

Processing schedules vary by bank and PSP; set internal deadlines and alerts to ensure mandates are captured before the first scheduled debit.

Before First Debit:

Obtain signed mandate and validate IBAN prior to initiating the first collection

Recordkeeping Deadline:

Archive the signed mandate and audit trail immediately after signing

Revocation Handling:

Promptly log debtor revocation requests and notify the bank per its procedures

Bank Processing:

Allow bank-specific clearing and settlement times before reconciling

Dispute Window:

Track and respond to customer disputes within bank-defined timelines

Frequently asked questions about Payment SEPA Mandates

Answers to common questions about validity, e-signatures, revocation, and what to do if banking details are incorrect.

Need help? Contact support

Can a SEPA mandate be e-signed in the U.S.?
Yes. U.S. e-signature laws (ESIGN Act, 15 U.S.C. ch. 96) and UETA permit electronic signatures where parties consent. Ensure the electronic workflow captures intent, attribution, consent, and retention to meet ESIGN and UETA requirements.
How does a debtor revoke a mandate?
A debtor may revoke authorization by notifying their bank and the creditor; process and timing depend on the bank and SEPA rules. Document the revocation, stop future debits, and reconcile any outstanding transactions promptly.
What if the IBAN is wrong?
Incorrect IBANs commonly cause failed debits and bank return fees. Validate IBAN format before submission and maintain a remediation workflow to obtain corrected details from the debtor.
Do I need a notary or witness?
Most states do not require notarization or witnesses for payment mandates. If an agent signs on behalf of a company, retain proof of signing authority; check state or contractual rules if in doubt.
How long should I keep signed mandates?
Retain mandates for business needs plus applicable regulatory periods. For tax-related retention follow IRC §6501(a) and for healthcare records follow 45 CFR §164.530(j) where PHI is involved.
Which authentication method should I use?
Use email plus SMS or stronger identity verification for higher-risk or high-value mandates. Maintain an audit trail showing authentication steps to reduce dispute risk.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now