Duplicate checks on Bacs 3-day files |
 |
Submission file checks
When transmitting to the Bacs 3-day service, Experian Payments Gateway raises:
-
Errors if a submission file sent today has the same processing date, Service User Number and Submission Serial Number. The file cannot be transmitted to the payment service
-
Warnings if a submission file sent in the last 31 days has the same processing date, Service User Number and Submission Serial Number. The submission can still be transmitted.
Note: If the Submission Serial Number is not imported from the header, Experian Payments Gateway generates a unique Submission Serial Number when you import the file. This means that if you import the same file twice using this custom format, it will not be marked as a duplicate.
Payment file checks
When transmitting to the Bacs 3-day service, Experian Payments Gateway raises:
-
Warnings if the payment file contains Direct Debit Instructions and another payment file sent in the last 31 days has a matching checksum and Service User Number. The submission can still be transmitted.
-
Warnings if the payment file does not contain Direct Debit Instructions and another payment file sent in the last 31 days has a matching Service User Number, Processing Date, File Number, debit count, credit count, debit total and credit total. The submission can still be transmitted.
Note: If the file number is not imported from the header, Experian Payments Gateway sets it to 000.
For multi-file submissions, Experian Payments Gateway applies these checks to each payment file within the submission to make sure the submission does not contain duplicate payment files.
For multi-processing date files, only the processing date and file number are checked.
Applies to
Rate this article