General
In addition to the debits generated by the payment schedule (see Automatic generation of debits relating to a payment schedule), the creditor may send one or more debit applications to SEPA Payment Suite, specifying the mandate to which each applies. SEPA Payment Suite checks the validity of the application and, if successful, saves the debit in its database.
Debit applications can be made individually or by batch. The exchange methods supported for this operation are presented in this table.
Processing debit applications
For each debit application, SEPA Payment Suite performs the following checks:
the existence (for mandatory data) and the syntax of each piece of data in the debit application. Where appropriate, some data may enhanced by the application (end-to-end reference, creditor account, due date);
the uniqueness of the end-to-end reference (by creditor in relation to all applications received);
the existence of the associated mandate (through the Unique Mandate Reference or the Unique Internal Reference);
the consistency between the payment sequence type and the mandate payment type (if absent from the application, SEPA Payment Suite automatically determines it);
the existence of the account (in relation to creditor’s configuration) on which the SDD is credited;
the consistency of the due date in relation to issuing constraints configured on the creditor’s account);
the consistency between the payment sequence type on the one hand, and the payment due date and the other payments relating to the mandate on the other.
Following the checks on each debit application, if they are passed successfully, SEPA Payment Suite stores the corresponding SDD in the database. Its status is based on the status of the mandate to which it refers and to the configuration (see SDD status management). The generation of bank collections is made later on (see Collection Management).
If the checks fail, the debit application is placed in error status. Debit applications in error status are only displayed on the error debit search screen. They are not displayed on the SDD query screens or in the in the list of SDDs associated with a mandate, as they require a user action before being taken into account in any subsequent processing. The actions associated with debit applications in error status are querying, confirmation of the rejection, recycling and manual correction. Debit applications showing error status are purged after 5 days.
Irrespective of the result of the checks, SEPA Payment Suite generates a response to the issuer of the debit application, in accordance with its exchange method. If the application is rejected, the response contains a result code indicating the reason for rejection from among the following:
No associated mandate;
Creditor’s account number unknown;
Duplicate;
Incorrect due date;
Incorrect amount;
Application sent after the deadline.
A setting can also manage the mandate database from the debit applications sent to SEPA Payment Suite: if enabled, mandates are automatically created using the data in the debit application. The signature date of the created mandates will correspond to the debit due date. Debits with reference to existing mandates (based on the SCI + UMR pairing) update their data.