PelicanPay accepts, validates and processes files containing Customer Direct Debit Collection Request messages (pain.008) from the corporate back-office and sends out valid files to the bank using the following SEPA compliant process:
Collections import and capture
PelicanPay accepts files containing Direct Debit Collection Request messages (pain.008) from the corporate back-office.
If files are not presented in the SEPA pain.008 format, they are converted to the ISO 20022 XML pain.008 format and enrichment is applied where required.
PelicanPay performs comprehensive validations on the collection requests:
Syntactische en semantische validatie
PelicanPay controleert of het formaat en de structuur van de incasso-instructies correct is.
SEPA EPC Rulebook validatie
PelicanPay controleert of de herstelincasso voldoet aan de validatie zoals beschreven in het SEPA EPC Rulebook.
Syntactical and semantic Validation
PelicanPay checks if the format and structure of the direct debit collection is correct.
SEPA EPC Rulebook validation
PelicanPay checks if the direct debit satisfies validations mentioned in SEPA EPC Rulebook.
Check for the validity of Creditor Identification code used in the instruction.
Check to identify if the instruction was already processed before. This works on either the entire contents of the instruction OR key parameters of the instruction.
Mandate check including recurrence check
If mandate information is available with PelicanPay, the direct debit instruction is checked against the mandate to ensure it is consistent and in agreement with the terms of the mandate and also that the mandate is still active. This will cover the check against the recurrence information as well.
PelicanPay checks if the direct debit collection falls within the EPC timelines guidelines
IBAN BIC check
PelicanPay checks whether the Debtor Agent BIC corresponds or is consistent with the IBAN of the Debtor.
SEPA Direct Debit scheme check
If applicable, PelicanPay checks whether the Debtor Agent is a participant in the B2B scheme.
Requested collection date check
PelicanPay checks whether the requested collection date is a valid business day and not a holiday.
Additional country and bank specific checks
The message is validated against any relevant country or bank specific validations.
Linking to mandates
PelicanPay matches the instructions to their respective mandates and links them so that they are visible while performing a drill-down to transactions from the mandates.
Scheduling and routing and warehousing
PelicanPay will move the direct debit to the appropriate queue for manual intervention if it happens to be future value-dated or has exceptions. It will also check if their respective cut-offs and holiday calendars of the destination banks are complied with.
PelicanPay moves the credit transfers to the appropriate queue for manual intervention if they fail any of the validation checks or the duplicate check.
Translation and country and bank specific enrichment
If required, instructions will be translated into a format required by the destination bank. PelicanPay will enrich the direct debit instruction with additional information as required by the destination country and the bank.
Authorization and Control
PelicanPay will route the credit transfers requiring authorization to the appropriate queues where user can authorize the file to be sent out to the destination bank.
PelicanPay will securely transmit the final instruction to the destination bank.
A detailed description of how PelicanPay implements each individual process is available in the downloadable functionality specification CLICK HERE