Can a SEPA mandate be signed electronically?

Yes. Electronic signatures are legally valid when they meet intent, consent, attribution, and retention standards under the ESIGN Act and UETA in the United States. Ensure the platform captures a reproducible audit trail and meets any EU data protection requirements when handling personal data.

What happens if the IBAN is wrong?

An incorrect IBAN typically results in a return from the debtor bank, possible return fees, and delayed reconciliation. Validate IBANs during capture and handle returned transactions per your PSP’s procedures.

How long does a mandate remain valid?

A mandate stays valid until the payer revokes it, a specified end date is reached, or scheme-specific conditions apply. Retain the mandate for the active term and a conservative post-termination period to support disputes.

Do I need a creditor identifier?

Yes for SEPA Direct Debit collections. The Creditor Identifier ties debits to your organization and is required in most SEPA schemes; obtain it through your bank or national authority.

Are there special privacy rules for SEPA mandates?

When collecting personal data from EU residents, comply with GDPR requirements for data processing, cross-border transfers, and data subject rights. Ensure lawful basis and adequate protections are documented.

How should disputes or refunds be handled?

Follow your PSP and bank procedures for reimbursements and return handling. Maintain the signed mandate, audit trail, and communications to respond to chargebacks or inquiries efficiently.

Payment SEPA Form

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

PAYMENT SEPA MANDATE AND SERVICE AGREEMENT

This Payment SEPA Mandate and Service Agreement (the "Agreement") is made on by and between Creditor Name: and Debtor Name: .

RECITALS

WHEREAS, Creditor provides goods and/or services to clients and requires authorization to collect payments by SEPA direct debit; and

WHEREAS, Debtor is the account holder authorizing the Creditor to initiate debits from the Debtor's bank account in accordance with the terms of this Agreement; and

NOW, THEREFORE, in consideration of the mutual covenants set forth below, the parties agree as follows.

CREDITOR INFORMATION

Creditor Legal Name Creditor Address Creditor Identifier (Creditor ID)

DEBTOR (PAYER) INFORMATION

Debtor / Account Holder Name Debtor Address IBAN BIC / SWIFT

MANDATE DETAILS

Mandate Reference

Type of Payment: Recurring direct debit One-off direct debit B2B scheme (if applicable)

Authorization: By signing this mandate the Debtor authorises the Creditor to send instructions to the Debtor's bank to debit the Debtor's account in accordance with the instructions of the Creditor. The Debtor also authorises the Debtor's bank to debit the Debtor's account in accordance with such instructions. The Creditor undertakes to provide a valid mandate reference for each collection and to retain the signed mandate. The Debtor acknowledges that the bank may require notice of individual debits in advance; such notice period shall be as set out in the Payment Terms below.

Refund Rights: The Debtor may claim a refund under the terms applicable to SEPA direct debits as between the Debtor and its bank. Any refund claim must be made in accordance with applicable banking rules and within the time limits agreed with the Debtor's bank.

SCOPE OF WORK

Scope of Work (describe services or goods for which payments are collected)

PAYMENT TERMS

Amount to be Collected Currency Payment Schedule / Due Date Payment Due Within (days) Late Fee / Interest on Overdue Amounts

The Debtor authorizes the Creditor to initiate direct debits for the amounts and on the schedule set forth above. The Creditor shall provide advance notice of variable debits where required by law or agreed schedule.

TERM AND TERMINATION

This Agreement commences on Start Date: and continues until End Date: unless earlier terminated in accordance with this Agreement.

Notice Period for Termination (days)

Either party may terminate this Agreement for material breach if the breach remains uncured after the notice period specified above. Termination shall not affect the Creditor's right to collect amounts due for services rendered prior to termination.

CONFIDENTIALITY

Each party shall hold in confidence and shall not disclose to any third party any non-public information received from the other party in connection with this Agreement, except as required by law or to perform obligations under this Agreement. This obligation shall survive termination of this Agreement for a period of two years.

GOVERNING LAW

This Agreement shall be governed by and construed in accordance with the laws of without regard to conflict of law principles.

ENTIRE AGREEMENT

This Agreement (including the SEPA mandate details and any schedules executed herewith) constitutes the entire agreement between the parties with respect to its subject matter and supersedes all prior proposals, negotiations, and communications, whether oral or written. Any amendment must be in writing and signed by authorized representatives of both parties.

CERTIFICATION

By signing below, the Debtor certifies that the information provided is complete and accurate, that the Debtor is the holder of the specified bank account, and that the Debtor authorises the Creditor to collect payments by SEPA direct debit as set out in this Agreement. The Creditor certifies that it will comply with applicable SEPA scheme rules and retain the signed mandate.

Creditor:

By:

Date:

Debtor (Payer):

By:

Date:

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

A Payment SEPA Form (Single Euro Payments Area mandate) is a standardized authorization customers provide to enable Euro-denominated direct debits across SEPA-participating banks. It identifies the payer, the payee, the debtor account (IBAN), and the mandate reference, and it documents the payer’s explicit consent for recurring or one-off debits. Although SEPA mandates originate in the EU and EEA, U.S.-based organizations that bill or collect in euros use the form when working with European bank partners, payment service providers, or multinational clients to ensure consistent authorization and to reduce return rates and reconciliation friction.

Why a clear Payment SEPA Form matters

A complete, properly signed SEPA mandate reduces payment failures, shortens reconciliation cycles, and provides a clear audit trail for refunds, chargebacks, and regulatory review across cross-border euro collections.

Who typically completes or receives a Payment SEPA Form

The form bridges payer consent, bank processing, and merchant records; accuracy and retention support dispute resolution and compliance.

European customers and account holders who provide IBANs and authorize debits in euros.
U.S. finance teams operating cross-border collections for subsidiaries, vendors, or international customers.
Payment service providers and banks that need standardized authorizations for processing SEPA Direct Debits.

Essential sections to include on a professional Payment SEPA Form

A professional SEPA mandate groups identification, bank details, authorization specifics, collection frequency, signature and date, and a clear mandate reference. Each section should be unambiguous to prevent returns, enable automated reconciliation, and support audit-ready recordkeeping.

Payer Details

Full legal name, billing address, and contact information for the account holder to match bank records and support identity verification.

Debtor Bank Data

IBAN and BIC (when required) entered exactly as shown by the bank; incorrect digits cause SEPA returns or delays.

Creditor Identification

Creditor name and Creditor Identifier (CI) used in SEPA Direct Debit schemes to identify the collecting party.

Mandate Reference

Unique mandate reference assigned by the creditor; used to reconcile debits, handle refunds, and support debtor inquiries.

Authorization Terms

Scope (one-off or recurring), pre-notification timing, and any maximum amounts or billing cadence required for transparent consent.

Signature and Date

Signed consent (wet signature or compliant electronic signature) plus date; signature method must meet legal-evidence requirements.

Step-by-step: how to prepare and submit a SEPA mandate

Complete the form in order to avoid missing data and to make bank processing predictable.

01

Collect payer data: Gather legal name, address, and IBAN from the payer and verify accuracy.
02

Assign mandate reference: Generate a unique reference for this mandate before saving or sending the form.
03

Choose authorization type: Specify one-off or recurring and the pre-notification interval in writing.
04

Obtain signature: Capture a handwritten or compliant eSignature and date the document.

How to configure an online SEPA mandate workflow

When deploying the form digitally, set up field validation, authentication, and storage to match bank and internal controls.

Field	Configuration
IBAN validation	Enable format checks and country-code validation to block incorrect entries.
Required fields	Make payer name, IBAN, and signature mandatory to prevent incomplete mandates.
Signer authentication	Use email plus SMS or knowledge-based checks for stronger signer attribution.
Audit trail	Record timestamps, IP, and user actions to support dispute handling.

Digital signing and eSubmission: platform capabilities to consider

Ensure the platform supports secure export, long-term storage, and searchable audit logs to meet regulatory and operational needs.

File formats: PDF, DOCX, or HTML input and ISO-compatible signed PDF output.
Integrations: Connectors for ERP, CRM, and cloud storage simplify reconciliation and recordkeeping.
Authentication options: Email, SMS OTP, or advanced signer authentication for higher assurance.

Where a completed SEPA mandate goes — routing and processing

Routing depends on whether you use a bank, payment service provider, or an aggregator for SEPA Direct Debit collections.

Send to PSP: Submit mandates to your payment service provider for tokenization and collection setup.
Store with creditor: Keep a copy in creditor records for reconciliation and disputes.
Share with bank: Provide mandates to the collecting bank when required for batch submission.
Retain audit log: Preserve audit trail and signed PDF for chargeback defense and regulator review.

Timing and pre-notification expectations for SEPA collections

SEPA schemes specify pre-notification and submission windows; follow your PSP or bank rules and the SEPA Core or B2B scheme requirements.

Pre-notification timing:

Typically at least 14 calendar days before first collection unless agreed otherwise.

One-off collection submission:

Submit per bank cutoff times; same-day processing may not be available.

Recurring debit schedule:

Establish cadence and include it in the mandate and pre-notice communications.

Return windows:

Debtor banks typically allow 8 weeks for authorized returns and up to 13 months for unauthorized claims.

Mandate lifetime:

Mandates typically remain valid until revoked or until specified end date in the mandate.

Key milestones from mandate issuance to first debit

Track milestones closely to ensure timely first debit and to maintain clear payer communication.

01

Mandate issued

Payer signs and returns the mandate to the creditor.

02

Pre-notification sent

Creditor notifies payer of first debit date and amount window.

03

Setup with bank/PSP

Creditor or PSP registers mandate and tokenizes account for collection.

04

First debit execution

Debt is submitted to the collecting bank and processed per scheme timing.

Common mistakes that delay or invalidate SEPA mandates

Incorrect IBAN entry causing immediate bank returns and reconciliation delays.
Missing or ambiguous mandate reference that prevents matching debits to invoices.
Using an unsigned or improperly signed mandate lacking clear consent evidence.
Failing to send pre-notification per agreed timeframe, causing payer disputes.

Risks and operational consequences of an incorrect SEPA form

Return fees: Banks may charge fees for rejected debits.

Chargebacks: Payer-initiated reversals increase processing costs.

Mandate invalidation: Technical or signature errors can void authorization.

Delayed cash flow: Processing failures postpone collections and reconciliation.

Dispute exposure: Lack of audit trail weakens defense on claims.

Additional operational costs: Manual remediation consumes staff time and resources.

Data protection and compliance considerations for electronic mandates

Encryption in transit: TLS 1.2/1.3

Encryption at rest: AES-256

Audit trail: Timestamped events and signer attribution

Data privacy: GDPR considerations for EU personal data

Regulatory compliance: ESIGN and UETA for U.S. eSign validity

Certifications: SOC 2 Type II, ISO 27001, PCI DSS

Comparing eSignature platforms for SEPA mandates (signNow first)

Cost and feature comparisons help determine which eSignature vendor matches your volume, compliance, and integration needs without implying endorsement.

	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	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

Real-world examples of SEPA mandate use

These concise examples show how different organizations use Payment SEPA Forms to collect euro payments and manage authorization.

Subscription Service

A SaaS vendor collects monthly euro fees via SEPA mandates to automate recurring billing and reduce failed payments.

Mandate tokenized by PSP for security and reconciliation.
Resulting process lowered manual collections, improved cash flow predictability, and provided clear audit records for customer inquiries and chargeback disputes.

International Supplier

A U.S.-based importer obtains SEPA mandates from European suppliers to pay recurring logistics fees.

Bank verifies IBAN and mandate reference before settlement.
This supported predictable outbound payments, simplified cross-border reconciliation, and reduced bank reconciliation time between currencies.

Practical tips to reduce errors and disputes with SEPA mandates

Adopt consistent controls and communication practices to limit returns and ensure clear payer consent.

Validate IBAN and payer name before submission

Use software or built-in field validation to block incorrect IBAN formats and enforce exact name matching to bank records to avoid chargebacks.

Provide clear pre-notification

Send a written notification in advance of the first debit that includes amount, date window, and contact details to reduce disputes.

Keep an auditable record

Store signed PDF mandates, audit trails, and correspondence for the retention period required by your industry and any applicable regulations.

Use consistent mandate references

Apply a predictable reference scheme to connect mandates to invoices and improve automated reconciliation processes.

Frequently asked questions about the Payment SEPA Form

Answers to common questions about completing, signing, and storing SEPA mandates in cross-border collections.

Need help? Contact support

Can a SEPA mandate be signed electronically?
Yes. Electronic signatures are legally valid when they meet intent, consent, attribution, and retention standards under the ESIGN Act and UETA in the United States. Ensure the platform captures a reproducible audit trail and meets any EU data protection requirements when handling personal data.
What happens if the IBAN is wrong?
An incorrect IBAN typically results in a return from the debtor bank, possible return fees, and delayed reconciliation. Validate IBANs during capture and handle returned transactions per your PSP’s procedures.
How long does a mandate remain valid?
A mandate stays valid until the payer revokes it, a specified end date is reached, or scheme-specific conditions apply. Retain the mandate for the active term and a conservative post-termination period to support disputes.
Do I need a creditor identifier?
Yes for SEPA Direct Debit collections. The Creditor Identifier ties debits to your organization and is required in most SEPA schemes; obtain it through your bank or national authority.
Are there special privacy rules for SEPA mandates?
When collecting personal data from EU residents, comply with GDPR requirements for data processing, cross-border transfers, and data subject rights. Ensure lawful basis and adequate protections are documented.
How should disputes or refunds be handled?
Follow your PSP and bank procedures for reimbursements and return handling. Maintain the signed mandate, audit trail, and communications to respond to chargebacks or inquiries efficiently.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now