Are SEPA mandates valid when e-signed?

Yes. In cross-border contexts an electronic signature can demonstrate intent and consent; in the United States e-signatures must satisfy ESIGN (15 U.S.C. ch. 96) and applicable state UETA rules to be enforceable.

What happens if the IBAN is wrong?

An incorrect IBAN typically causes a failed transfer or return, triggering bank fees and reconciliation work; validate IBAN format before submission to avoid these costs.

Can a payer revoke a SEPA mandate?

Yes. Payers can revoke mandates per the creditor agreement and bank procedures; allow time for processing and notify the creditor promptly to avoid unauthorized debits.

Is notarization required for SEPA mandates in the U.S.?

Not usually. Most bank mandates do not require notarization, but some institutions or high-risk arrangements may request notarized acknowledgement or RON depending on internal policies.

How long should I keep signed mandates?

Retain mandates for the active term plus recommended retention (commonly at least three years); follow industry rules such as IRC §6501(a) and HIPAA 45 CFR §164.530(j) where applicable.

Which file formats are best for long-term storage?

Use PDF/A or standard PDF exports with embedded audit trails for long-term evidence. Keep a tamper-evident audit log and a reproducible copy for audits.

Payment SEPA Document

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

PAYMENT SEPA DOCUMENT

Parties and Mandate Identification

Creditor (Payee) - Full legal name Creditor Identifier / Creditor Reference Creditor Address Debtor (Payer) - Full legal name Debtor Address Mandate Reference (to be used by Creditor)

Recitals

WHEREAS, Creditor provides goods or services to Debtor;

WHEREAS, Debtor agrees to make payments to Creditor by SEPA direct debit in accordance with the terms of this Payment SEPA Document and an applicable invoice or payment schedule;

WHEREAS, the parties wish to set out a binding mandate authorising the Creditor to initiate debits and the Debtor's financial institution to debit the Debtor's account in accordance with SEPA rules and the terms below.

Scope of Work

The Creditor shall perform services or deliver goods as described below. The parties agree that payment for such services or goods will be effected by SEPA direct debit under the mandate set out in this document.

SEPA Direct Debit Mandate

Debtor authorises Creditor to initiate SEPA direct debits to the Debtor's bank account identified below and instructs the Debtor's bank to debit that account in accordance with Creditor's instructions. Debtor acknowledges that this mandate is subject to the terms below and the rules governing SEPA direct debits.

Debtor IBAN Debtor BIC (if required)

Payment type: One-off Recurring

For recurring payments, frequency: Next planned debit date:

Payment Terms

Amount to be collected per debit (if fixed): Currency:

Payment schedule and invoicing (describe schedule or reference invoices)

Late payment charge: Interest begins after days past due.

Term and Termination

This Agreement commences on and terminates on unless earlier terminated in accordance with this section.

Either party may terminate this Agreement for convenience upon written notice at least days prior to the effective termination date. Termination for cause may be immediate where a material breach remains uncured for a reasonable period following written notice.

Confidentiality

Each party shall maintain in confidence all non-public information disclosed by the other party in connection with this Agreement, shall not use such information other than to perform its obligations, and shall limit disclosure to its employees, agents or subcontractors on a need-to-know basis and subject to equivalent confidentiality obligations. Confidential information does not include information that is or becomes public through no breach by the receiving party, is rightfully received from a third party without restriction, or is independently developed.

Confidentiality obligations survive termination of this Agreement for a period of years.

SEPA-specific Covenants and Warranties

Debtor warrants that the bank account details provided are accurate and that Debtor is authorised to permit debits on that account. Creditor shall notify Debtor of the amount and date of each debit in accordance with the agreed schedule or with reasonable notice for variable amounts. Debtor has the right to request reimbursement from their bank in accordance with the applicable direct debit scheme rules within the permitted timeframe.

Governing Law

This Agreement and the SEPA mandate shall be governed by and construed in accordance with the laws of , without regard to its conflict of law rules.

Entire Agreement

This document, together with any incorporated schedules, invoices and referenced payment schedules, constitutes the entire agreement between the parties concerning the subject matter hereof and supersedes all prior agreements and understandings, whether written or oral. Any amendment must be in writing and signed by authorised representatives of both parties.

Additional Terms and Notices

By signing below, Debtor authorises the Creditor to initiate SEPA direct debits as specified in this mandate and warrants that the account specified belongs to the Debtor. Creditor shall provide the Mandate Reference to Debtor and to Debtor's bank as required for processing.

Creditor

Print Name:

By:

Date:

Debtor

Print Name:

By:

Date:

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

A Payment SEPA Document is a standardized mandate or instruction used to authorize euro-denominated credit transfers or direct debits under SEPA (Single Euro Payments Area) rules. It records payer and payee bank details (IBAN, BIC/SWIFT), mandate reference, and explicit authorization for recurring or one-off transfers. Organizations use it to establish standing authorizations, trigger collections, or confirm payment routing. Although SEPA is a European payments framework, U.S.-based entities that transact in euros use SEPA documents to meet bank and creditor requirements and to reduce reconciliation and return-event risk.

Why a clear, complete Payment SEPA Document matters

A correctly completed Payment SEPA Document reduces failed transfers, minimizes bank return fees, and provides legal evidence of payer consent. For cross-border euro payments it helps meet creditor bank onboarding requirements and supports automated processing.

Typical users and roles that complete Payment SEPA Documents

Teams and individuals who interact with euro payments complete SEPA mandates to authorize transfers and maintain payment records.

Treasury / Finance teams managing inbound/outbound euro flows and bank reconciliation.
Accounts Payable / Accounts Receivable teams collecting recurring euro payments from customers.
International vendors, subsidiaries, or in-house operations that require direct debit or credit transfer authorization.

Proper role assignment helps ensure accuracy, auditability, and timely processing of international collections or payouts.

Core parts of a professional Payment SEPA Document

A compliant SEPA document groups identity, banking, mandate, and authorization details so banks and clearing systems can route and validate payments reliably.

Payer identification

Full legal name and address of the account holder as shown on bank records; must match bank KYC data.

Creditor identification

Name and address of the beneficiary (creditor) and their creditor identifier used in SEPA schemes.

Bank account data

IBAN for the payer's account and optional BIC/SWIFT for cross-border routing; digits must be exact to avoid returns.

Mandate reference

Unique identifier assigned by the creditor to the mandate; used to match collections and track revocations.

Authorization statement

Clear, dated language authorizing single or recurring transfers and describing timing or amount parameters if needed.

Signature and date

Handwritten or e-signed authorization with signer name and execution date to document consent.

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

Follow these sequential steps to create, validate, and deliver a SEPA mandate so bank processing proceeds without avoidable delays.

01

Prepare details: Gather payer legal name, IBAN, BIC, and creditor identifier
02

Draft mandate: Include authorization language, mandate reference, and execution date
03

Obtain signature: Collect handwritten or e-signed authorization with timestamp
04

Submit to bank: Provide creditor bank or payment processor with the signed mandate and supporting data

How to customize the online SEPA mandate workflow

Configure fields and authentication so electronic SEPA mandates meet bank requirements and your internal audit rules.

Field	Configuration
IBAN validation	Enable regex or built-in IBAN checks to prevent invalid entries
Mandate reference	Auto-generate unique IDs for reconciliation and audit
Signer authentication	Require email + SMS OTP or stronger ID verification for high-value mandates
Audit record	Enable timestamped audit trails and downloadable certificates

Typical processing flow for a completed Payment SEPA Document

This sequence shows how a signed mandate moves from originator to bank and into the payments system.

Create: Sender prepares mandate with payer and creditor details
Sign: Payer reviews and signs electronically or on paper
Submit: Creditor or payment processor sends mandate data to the creditor bank
Process: Bank validates IBAN/BIC and stores mandate for future debits or one-off transfers

Digital signing and format considerations for SEPA mandates

Choose a platform that supports PDF and DOCX formats, audit trails, and the authentication level required by your bank.

Supported formats: PDF, DOCX, and structured exports for reconciliation
Authentication: Email, SMS OTP, or higher-strength verifier options
Integrations: CRM/ERP connectors for automated posting and tracking

Security and compliance basics for storing SEPA mandates

Encryption transit: TLS 1.2 / 1.3

Encryption rest: AES-256 encryption

Certifications: SOC 2 Type II, ISO 27001

HIPAA: BAA required where PHI present

Audit trail: Timestamped IP and action logs

Access controls: MFA and SSO available

Common mistakes to avoid when preparing a SEPA payment mandate

Entering an incorrect IBAN or transposing digits, which leads to failed transfers and bank return fees.
Using informal payer names that do not match bank KYC records, causing verification delays or mandate rejection.
Omitting a clear mandate reference or authorization wording, creating reconciliation or dispute difficulties.
Failing to record signer attribution, timestamp, or consent method, weakening enforceability of an electronic mandate.

Consequences and financial risks of an incorrect Payment SEPA Document

Returned transfer: Bank fees and delay

Chargebacks: Reversal and potential penalties

Compliance gap: KYC or audit findings

Reputational risk: Customer disputes escalate

Data breach exposure: Fines and notification costs

Contract disputes: Longer resolution timelines

Timing and processing expectations for SEPA payment mandates

Allow time for bank validation and pre-notification; processing windows vary by bank and the type of transfer or direct debit.

Bank validation window:

Allow 1–5 business days for account verification

Pre-notification:

Provide pre-notice timing per creditor agreement (commonly days before debit)

One-off debit processing:

Typically 2–5 business days to clear

Recurring debit setup:

Allow one initial cycle plus bank verification time

Revocation lead time:

Follow creditor terms; allow bank processing time

eSignature vendor comparison for signing Payment SEPA Documents

Platform choice affects authentication, storage, and cost. The table shows starting pricing and common capability indicators; confirm vendor terms for bank or regulatory requirements.

	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	Varies	Varies	Varies	Varies
Audit Trail	Yes	Yes	Yes	Yes	Yes
Envelope Cap	No cap	100 envelopes/user/yr	Varies	Varies	Varies

Practical tips for accurate and efficient SEPA mandate completion

Adopt consistent validation, authentication, and storage practices to reduce errors and support audits.

Validate bank details

Use structured IBAN checks and BIC validation before sending the mandate to avoid immediate rejections and reconciliation effort.

Record consent clearly

Include unambiguous authorization language, a mandate reference, and a signed date to ensure clarity around payment scope and revocation.

Choose appropriate authentication

Match signer authentication strength to risk: use SMS OTP or higher for large or recurring debit mandates to reduce dispute risk.

Integrate reconciliation

Automate posting of mandate references into accounting or ERP systems to speed collections and reduce manual matching.

Real-world examples from verified customers

Organizations handling international payments use e-signing platforms to streamline mandate capture and reconciliation while preserving compliance records.

Optica Ventures LLC

Optica reduced processing complexity for cross-border payments by digitizing mandate capture.

Simpler customer experience enabled faster authorizations.
"The interface is simple and easy-to-use for our team; more importantly, it is just as easy for our customers."

Tech Data

Tech Data centralized payment authorizations for global suppliers and customers.

Centralized records improved reconciliation across business units.
"Tech Data uses airSlate SignNow to improve our internal and external customer service while increasing our speed to revenue."

Frequently asked questions about Payment SEPA Documents

Answers to common operational, legal, and technical questions when preparing or storing SEPA mandates.

Need help? Contact support

Are SEPA mandates valid when e-signed?
Yes. In cross-border contexts an electronic signature can demonstrate intent and consent; in the United States e-signatures must satisfy ESIGN (15 U.S.C. ch. 96) and applicable state UETA rules to be enforceable.
What happens if the IBAN is wrong?
An incorrect IBAN typically causes a failed transfer or return, triggering bank fees and reconciliation work; validate IBAN format before submission to avoid these costs.
Can a payer revoke a SEPA mandate?
Yes. Payers can revoke mandates per the creditor agreement and bank procedures; allow time for processing and notify the creditor promptly to avoid unauthorized debits.
Is notarization required for SEPA mandates in the U.S.?
Not usually. Most bank mandates do not require notarization, but some institutions or high-risk arrangements may request notarized acknowledgement or RON depending on internal policies.
How long should I keep signed mandates?
Retain mandates for the active term plus recommended retention (commonly at least three years); follow industry rules such as IRC §6501(a) and HIPAA 45 CFR §164.530(j) where applicable.
Which file formats are best for long-term storage?
Use PDF/A or standard PDF exports with embedded audit trails for long-term evidence. Keep a tamper-evident audit log and a reproducible copy for audits.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now