Is an e-signature valid for SEPA?

Yes. In the U.S., electronic signatures are legally enforceable under the ESIGN Act (15 U.S.C. ch. 96) and UETA where adopted; ensure intent, consent, signer attribution, and reliable record retention to meet the four-part legal test.

Do banks require notarization of mandates?

Generally no; SEPA direct debit mandates do not usually require notarization. Banks expect a signed mandate and matching bank records. Bank-specific acceptance rules vary, so verify with the creditor bank and document any additional authentication they request.

How long must businesses retain SEPA mandates?

Retain signed mandates per creditor bank and regulatory expectations. Common practice is at least 36 months after the last debit; retain supporting records longer when tax, audit, or dispute risks exist.

Can a payer revoke authorization?

Yes. Payers may revoke SEPA mandates according to SEPA rules and creditor terms; revocation typically requires notice to the creditor and bank. Reversals or chargebacks can follow. Document revocations and adjust future collection attempts accordingly.

What about refunds and returns?

Authorized debits may be subject to payer refund windows under SEPA rules; unauthorized debits have longer refund rights. U.S. creditors should mirror bank and SEPA return timelines in their terms and maintain documentation to resolve disputes with European banks.

What authentication is sufficient?

Strong authentication reduces chargebacks. Use bank-level verification, two-factor authentication, or digital bank-verified e-mandates where possible. Keep an audit trail (IP, timestamp, consent disclosure) and align authentication strength with the creditor bank’s acceptance policies and fraud risk profile.

Electronic Signature
Templates
Miscellaneous
Payment SEPA Agreement

Payment SEPA Agreement

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

PAYMENT SEPA AGREEMENT

Parties

Creditor (Payee):

Creditor Address

Creditor Identifier (if applicable):

Debtor (Payer):

Debtor Address

Recitals

WHEREAS Creditor provides goods and/or services to Debtor pursuant to the terms of this Agreement and the accompanying Scope of Work; and

WHEREAS Debtor authorizes creditor-initiated SEPA direct debits from Debtor's designated bank account by completing the mandate below and agrees to pay amounts as set out in Payment Terms; and

WHEREAS the parties wish to document the payment authorization, collection schedule and associated rights and obligations under this Payment SEPA Agreement.

Scope of Work

Services, deliverables or purpose of payments

SEPA Mandate Authorization

Debtor IBAN:

Debtor BIC:

Mandate Reference (to be used by Creditor):

Payment type: Recurring One-off

By signing this Agreement and the mandate, Debtor authorizes Creditor to initiate debits to the bank account specified above and instructs Debtor's bank to honor such debits. Debtor understands that rights to a refund or reversal are governed by the SEPA direct debit scheme and applicable bank rules.

Payment Terms

Amount per debit Currency Collection frequency / schedule

First collection date: Subsequent collections will occur according to the schedule above unless otherwise agreed in writing.

Late payment fee

If a debit is returned unpaid or a payment is not collected when due, Creditor may re-attempt collection and may charge reasonable administrative fees and interest as specified above. Creditor's right to suspend services for non-payment is reserved until outstanding amounts are settled.

Term and Termination

Agreement start date: Agreement end date (if any):

Notice of termination required

Either party may terminate this Agreement for material breach by the other party that remains uncured for the notice period above. Termination shall not affect obligations or liabilities accrued prior to termination, including the right to collect sums due under this Agreement.

Confidentiality

Each party shall maintain in confidence and not disclose to any third party confidential information received from the other party in connection with this Agreement, except as required by law or as necessary to perform its obligations hereunder. Confidential information excludes information that is publicly available without breach of this Agreement, independently developed without reference to the other party's confidential information, or rightfully received from a third party without restriction.

The obligations under this clause shall survive termination or expiration of this Agreement for a period of three (3) years.

Governing Law

This Agreement shall be governed by and construed in accordance with the laws of , without regard to conflicts of law principles. The parties submit to the exclusive jurisdiction of the competent courts in that jurisdiction for any disputes arising out of this Agreement.

Refund Rights and Consumer Notice

For authorized SEPA direct debits, Debtor retains any rights of refund and dispute provided under the applicable SEPA scheme rules and banking regulations. Debtor must notify its bank or Creditor promptly of any unauthorized or incorrect debits in accordance with applicable banking procedures.

Entire Agreement

This Agreement, including the SEPA mandate and any referenced Scope of Work, constitutes the entire agreement between the parties with respect to the subject matter hereof and supersedes all prior and contemporaneous agreements, understandings and representations, whether written or oral. Any amendment or waiver must be in writing and signed by both parties.

Miscellaneous Provisions

If any provision of this Agreement is held invalid or unenforceable, the remaining provisions shall remain in full force and effect. Neither party may assign this Agreement without the prior written consent of the other party, except that Creditor may assign receivables to a financing institution without Debtor's consent provided Debtor is given notice.

Acknowledgement

The undersigned represent and warrant that they are duly authorized to enter into this Agreement on behalf of the named party and that the information provided in this Agreement and the SEPA mandate is accurate and complete.

Creditor:

By:

Date:

Debtor:

By:

Date:

What a Payment SEPA Agreement Covers

The Payment SEPA Agreement is a written authorization that permits a creditor to initiate SEPA direct debits from a debtor’s Euro-denominated bank account (IBAN). It documents the debtor’s consent, identifies the parties, specifies the mandate reference, and records the agreed terms for timing and amounts. U.S.-based organizations use this agreement when collecting payments from European customers or vendors under the Single Euro Payments Area scheme. The document supports electronic signature and can be integrated into digital collections workflows, provided applicable e-signature laws and banking rules are observed.

Why this agreement matters for cross-border collections

Provides a standardized mandate that proves payer authorization for SEPA direct debits, reduces dispute risk, and documents banking details required by creditor banks. It simplifies cross-border euro collection for U.S. businesses while creating an auditable record for compliance and reconciliation.

Who typically completes a Payment SEPA Agreement

Finance, treasury, accounts receivable, and international sales teams commonly prepare or request Payment SEPA Agreements when onboarding euro-paying counterparts.

Treasury managers handling cross-border collections and bank mandate setup processes.
Accounts receivable staff who send mandates and track SEPA returns and reconciliations.
International sales or billing teams onboarding European customers and negotiating payment terms.

Legal, compliance, and merchant bank operations should review completed mandates for legal sufficiency and bank acceptance before initiating debits.

Core components every professional Payment SEPA Agreement should include

Key elements of a professional Payment SEPA Agreement ensure clarity of authorization, banking details, mandate identification, and conditions for future debits and revocation.

Parties

Identify creditor and debtor by legal name, address, and contact information. Use the entity name that matches bank records to prevent processing errors and ensure enforceability.

Bank Details

Specify debtor IBAN and, if required, BIC/SWIFT. Confirm formatting without spaces and verify details against a bank validation service to reduce returns and failed debits.

Mandate ID

Assign a unique mandate reference and creditor identifier to be used on transaction reports and communications; this links each debit to the signed authorization record.

Authorization Text

Include clear language stating the debtor authorizes direct debits and permit recurring or one‑off transactions. Reference SEPA direct debit type (Core or B2B) and any limits.

Timing & Notices

State when pre-notification will occur before the first debit and the settlement schedule. Typical pre-notification is 14 calendar days unless parties agree otherwise in writing.

Revocation

Describe how the debtor may withdraw authorization and the notice required. Specify any consequences for revocation, including final settlement, future collections handling, and related fees.

Security, encryption, and compliance highlights

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

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

HIPAA: HIPAA compliant; BAA required

FDA Compliance: 21 CFR Part 11 support available

Legal Frameworks: ESIGN and UETA compliant

Accessibility: WCAG 2.0 Level AA

Step-by-step: preparing and collecting a SEPA mandate

Follow these sequential steps to prepare and collect a valid Payment SEPA Agreement electronically and in print.

01

Prepare Document: Include creditor, debtor, IBAN, mandate reference, and terms.
02

Confirm Identity: Collect ID or use bank-level authentication before signing.
03

Send for Signature: Provide pre-notification and deliver the mandate for e-signature.
04

Record & Store: Save signed mandate, audit trail, and bank confirmation.

Typical digital workflow settings for collecting mandates

Configure your digital collection workflow to capture SEPA mandates, authenticate signers, and archive signed records for bank verification.

Field	Configuration
Authentication	SMS OTP, bank-auth, or KBA per bank rules
Mandate Type	SEPA Core or B2B selection
Storage Location	Encrypted cloud storage with audit trail
Notifications	Pre-notification and settlement messages to payer

End-to-end process for electronic mandate collection

Typical online workflow for collecting and processing a signed Payment SEPA Agreement from upload to bank submission.

Upload: Sender uploads mandate template and fields.
Place Fields: Add name, IBAN, mandate ID, and signature fields.
Authenticate: Use email, SMS, or bank verification before signing.
Archive: Store signed mandate with audit trail and export options.

Platform requirements and integrations to support mandates

Use platforms that support PDF, DOCX imports, bank verification integrations, and exportable audit trails for mandates.

Integrations: Salesforce, NetSuite, Microsoft 365
Formats: PDF, DOCX, HTML, XLSX supported
Security: TLS 1.2/1.3; AES-256 at rest

Typical vendor pricing and capability snapshot for eSignature

Comparison of typical vendor pricing and core capabilities relevant when collecting signed Payment SEPA Agreements.

	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 (BAA required)	Yes	Yes	No	No

Timelines and expected processing windows

Key timing considerations and processing expectations for SEPA mandate execution and disputes in cross-border euro payments.

Pre-notification:

Provide at least 14 calendar days' notice before the first debit.

Processing lead time:

Allow one to five business days for bank processing.

Refund window:

Authorized debits: up to eight weeks for payer refund requests.

Mandate retention:

Keep mandate at least thirty-six months after last successful debit.

Dispute timeframe:

Respond to bank inquiries within required timelines to avoid penalties.

Common preparation and execution pitfalls to avoid

Incorrect IBAN formatting, including spaces or mistyped characters, is a leading cause of immediate transaction failure and bank returns that delay reconciliation.
Failure to provide clear pre-notification timing or to document consent can increase the likelihood of payer disputes and refund claims under SEPA rules.
Using weak signer authentication or relying solely on email click-throughs may not satisfy bank or legal standards for proof of authorization.
Neglecting to align mandate language with creditor bank requirements can result in rejection, processing delays, or inability to link debits to the signed authorization.

Risks and possible financial consequences

Return Fees: Bank charges and processing costs.

Chargebacks: Potential reversal and merchant liability.

Delayed Cash Flow: Late or failed collections.

Regulatory Fines: Noncompliance with data or banking rules.

Tax Exposure: Backup withholding or reporting issues.

Contract Disputes: Legal costs and enforcement delays.

Practical examples of SEPA mandates in use

Two practical examples showing how U.S. organizations use Payment SEPA Agreements for euro collections in invoicing and recurring rent.

Financial Services

A U.S.-based payment processor needed standardized SEPA mandates to collect recurring subscription fees from European customers across multiple banks.

Reduced returns and simplified reconciliation.
By embedding mandates into the online onboarding flow and validating IBANs at entry, the processor reduced manual follow-ups, shortened settlement timelines, and preserved audit trails required by creditor banks for dispute resolution and regulatory compliance.

Real Estate

An international landlord collected euro rents using SEPA mandates to automate monthly debits and minimize tenant payment late cycles.

Improved cash flow predictability and fewer late payments.
The landlord attached mandate references to lease accounts, provided timely pre-notification notices, and stored signed mandates with audit trails; this reduced administrative overhead and helped resolve chargebacks with bank documentation when disputes occurred.

Best practices to reduce disputes and speed reconciliation

Practical tips to reduce errors, accelerate collections, and protect against disputes when using Payment SEPA Agreements.

Always validate IBAN at entry

Use automated IBAN and BIC validation to catch typos before signature. Prompt the signer to correct errors inline and revalidate to prevent bank rejections and costly return processing that interrupts cash flow.

Provide clear pre-notification timing to payers

State the exact date the first debit will occur and any subsequent schedule. Document delivery of pre-notification and keep copies; inconsistent notices are a common basis for payer disputes and bank refunds under SEPA rules.

Always use bank-level signer authentication

Where available, use bank-verified e-mandates or multi-factor authentication to link the signer to the bank account. Strong authentication reduces refund risk, increases bank acceptance, and strengthens enforceability in dispute resolution.

Archive complete audit trails securely

Store signed mandates with timestamps, IP addresses, authentication logs, and consent disclosures in encrypted storage. Retain copies according to retention policy and make them available for bank or regulatory inquiries during the mandated retention period.

Frequently asked questions about Payment SEPA Agreements

Answers to common questions about validity, revocation, bank returns, and electronic signature use for Payment SEPA Agreements in U.S. workflows.

Need help? Contact support

Is an e-signature valid for SEPA?
Yes. In the U.S., electronic signatures are legally enforceable under the ESIGN Act (15 U.S.C. ch. 96) and UETA where adopted; ensure intent, consent, signer attribution, and reliable record retention to meet the four-part legal test.
Do banks require notarization of mandates?
Generally no; SEPA direct debit mandates do not usually require notarization. Banks expect a signed mandate and matching bank records. Bank-specific acceptance rules vary, so verify with the creditor bank and document any additional authentication they request.
How long must businesses retain SEPA mandates?
Retain signed mandates per creditor bank and regulatory expectations. Common practice is at least 36 months after the last debit; retain supporting records longer when tax, audit, or dispute risks exist.
Can a payer revoke authorization?
Yes. Payers may revoke SEPA mandates according to SEPA rules and creditor terms; revocation typically requires notice to the creditor and bank. Reversals or chargebacks can follow. Document revocations and adjust future collection attempts accordingly.
What about refunds and returns?
Authorized debits may be subject to payer refund windows under SEPA rules; unauthorized debits have longer refund rights. U.S. creditors should mirror bank and SEPA return timelines in their terms and maintain documentation to resolve disputes with European banks.
What authentication is sufficient?
Strong authentication reduces chargebacks. Use bank-level verification, two-factor authentication, or digital bank-verified e-mandates where possible. Keep an audit trail (IP, timestamp, consent disclosure) and align authentication strength with the creditor bank’s acceptance policies and fraud risk profile.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now