The client can schedule transactions in the future, either in the form of a reminder that they will have to confirm on the due date, or as a scheduled transfer that will be automatically executed on the indicated date. They can also provide their account details (IBAN or card) for a merchant to debit them in the future, as is the case for recurring subscription payments.

These transactions can be created and viewed from the "Scheduled and Upcoming" screen, accessible in the "Payments" section of the application (by clicking here from a mobile device).

Transactions are executed only subject to the availability of funds in the account concerned and the absence of regulatory or technical blockages.

When a detected upcoming debit date approaches, an indicator informs the client. This indicator is based on Sumeria’s known data and does not constitute a guarantee of execution.
Sumeria tries to detect upcoming debits via IBANs and cards as accurately as possible, but the available detection methods do not guarantee that all will be detected.
Consequently, Sumeria cannot be held liable for an undetected transaction.
The client is encouraged to use the advanced Fixed Charges feature for this.

Schedule an upcoming transaction

When to schedule a transfer

The "schedule a transfer" option allows scheduling a bank transfer, or an internal transfer between two of the client’s Sumeria accounts, in the future.

The recipient account, the amount, the account to be debited, and the transaction title must first be defined, then on a second screen, the frequency (single or recurring payment) and the execution date must be set.

By default, a scheduled transfer is automatic, but the client can enable the "Confirmation before transfer" option. In this case, a reminder requiring their confirmation will be sent on the due date.

Automatically scheduled transfers are sent at 7:00 AM (Paris time zone, GMT+1) on the agreed day, subject to the availability of funds.

Schedule a new payment request

The "schedule a request" option allows scheduling a Lydia payment request, either one-time or recurring. Sending a request does not guarantee its receipt or acceptance by the recipient and does not result in a debit until it has been validated by them.

Learn more about Lydia payment requests ->

Manage upcoming transactions

Direct debits

The "Direct debits" tab displays subscriptions by detected cards, followed by direct debit mandates.

Mandates are created automatically but are never deleted automatically. It is the client’s responsibility to do so for those they know should no longer exist. For example, at the end of a commercial relationship with a merchant.
An upcoming card transaction is a prediction. This does not mean that the client will necessarily be debited on the announced date. If the client cancels their card subscription, with the merchant’s agreement, then it should not be debited, despite the "upcoming" label.

Sumeria cannot guarantee the cancellation of a debit initiated by a merchant as long as the latter holds a valid authorization.

Transfers

It is possible to cancel a deferred or scheduled transfer up until the end of the business day preceding its execution date, and a standing transfer at any time, but no later than one day before the next due date.

However, once the transfer has been executed, it can no longer be canceled: the funds are definitively transferred, even in case of an error in the IBAN, the beneficiary’s name, or the amount.

Nevertheless, starting from October 9, 2025, a tool has been implemented to automatically verify the match between the beneficiary’s name and IBAN before confirming a transfer (European regulation of March 13, 2024). This tool aims to prevent errors, but if the client confirms the transfer despite a warning, it can no longer be canceled.

Lydia transfers scheduled via Sumeria are also displayed in this section

Payment requests (To receive)

The "To receive" tab displays scheduled Lydia payment requests. They can be modified or deleted.

Notifications

If the client has enabled push notifications, they will receive one each time an action is required on their part.

Otherwise, they will receive transaction notifications as for each of their operations, whether scheduled in advance or not, according to their account and communication preferences.

Notifications sent are for informational purposes and do not constitute proof of execution or acceptance of the payment order.

Do you have any other question ?
Great !
Back to home
What do you want to do ?
Contact the support Back to home