If a direct debit run has not completed and has its transactions sitting within Current, rather than History. It is likely locked by an imbalance. If this is the case, it is best to identify what transaction has caused the imbalance.
The transaction will be locked by the Allocation Session created by the direct debit run so you will not be able to match the transaction off.
To resolve this issue Support will need to run some scripts on the database. Therefore please contact us, reference the title of this article and please include the Direct Debit run number and the transaction reference for the imbalance.
