Pinpointing Errors

A series of tests is to be performed on each direct debit mentioned in the statement:

1. Does the UMR exist in the mandate reference list?

If the answer is No, the statement is considered as with errors and indicates the suspicious direct debit reference with the reason: Mandate not referenced in Authorized list.

2. The UMR exists in the mandate reference list, but is it associated with the ICS of the file?

If the answer is No, the statement is considered as with errors and indicates the suspicious direct debit reference with the reason: Mandate not authorized for this ICS.

3. Is the UMR mentioned in the file?

If the answer is No, the statement is considered as with errors and indicates the reason: Mandate not specified in Statements file.

4. Is the ICS mentioned in the file?

If the answer is No, the statement is considered as with errors and indicates the reason: ICS not specified in Statements file.

5. Is it a SDD Multi-submission on One-off Mandate?

If the answer is Yes, the statement is considered as with errors and indicates the reason: SDD Multi-submission on One-off Mandate.

6. Is the Mandate used after its end date?

If the answer is Yes, the statement is considered as with errors and indicates the reason: Mandate used after End Date.

To access the list of Statements with Errors, open the Debits by Direct Debits tab from the Errors menu.

This list gathers all the statements for which at least one suspicious direct debit has been identified after the control on the mandate reference list. For each statement, you can access the elements that caused the pinpointing using the + sign next to the corresponding Statement No.