When processing Direct Debits, you may occasionally see Bacs messages that need reviewing. Below are the most common scenarios and what they mean, along with the steps to take where needed.
No payments found for due date
On rare occasions, you may receive an ARUDD message from the bank showing 'No payments found for due date 'DATE', contract 'BANK REF' and amount 'DEBIT AMOUNT'.' This usually happens when an incorrect payment processing date is provided in the ARUDD message. Access PaySuite checks the date and may still apply the message, updating the payment to show as unpaid.
To confirm this:
Click the Direct Debits tab on the left hand side.
In the Customers/Contracts table, locate the relevant customer.
Click on the customer’s record to open their details.
Select the Payments tab.
Find the payment associated with the Bacs message.
Confirm that the payment status has changed from Paid to Unpaid.
If an ARUDD has been received but the payment is still showing as paid, please reach out to our support team and request to speak to an agent.
Duplicate Bacs messages received
Duplicate Bacs messages can occasionally be sent in error by a payer’s bank. No action is required when this happens. Access PaySuite processes the first message and automatically marks any duplicates as ignored in the Bacs tab.
If this happens frequently or impacts multiple Direct Debits, please reach out to our support team and request to speak to an agent.
Invalid DDI originator reference
You may see the message 'Contract cancelled because of Input Rejection Report 0N: REJECTED - Invalid DDI Originator Reference.'
This means there is an issue with the reference used when creating the Direct Debit Instruction. The reference must be at least six characters long and cannot contain spaces.
To resolve this, create a new contract for the payer using a reference that meets these requirements.