1. Have you tried to do a data dump and load into new SQL Database ID's and see if this make any difference?

2. Have you checked for any errors on the Restart Maintenance section related to this Transaction and Process?

3. Are there any errors on this module within the Data Integrity check?

4. Have you tried to run RVSpy?

5. When last was the client able to process the Bank Services - Reverse Transactions for the AP Module Payment?

6. Does this happen for all Creditors or just a specific one?

7. Does this happen for all users/pc's?

1. Have you tried to do a data dump and load into new SQL Database ID's and see if this make any difference?
[SeisaT] – I had just done a data dump of the live dataset and preparing to load into new databases on my laptop (but different version), when I decided to try the reversal one more time, and voilà, the transaction just went through.
2. Are you able to replicate this in Sample company [SAMINC]?
[SeisaT] – Yes, I am able to replicate in Sample Company
3. Have you checked for any errors on the Restart Maintenance section related to this Transaction and Process?
[SeisaT] – There are no restart records associated with the records/transactions in question.
4. Are there any errors on this module within the Data Integrity check?
[SeisaT] – There are no Data Integrity errors in Bank Services
5. Have you tried to run RVSpy?
[SeisaT] – It was actually when I had RVSpy turned on that I noticed the transaction posting through successfully. So, there was nothing unusual for RVSpy to pick up.
6. When last was the client able to process the Bank Services - Reverse Transactions?
[SeisaT] – This is the first time that the Client reverse transactions in Bank Services. They normally use Peresoft Cashbook to reverse transactions.
7. Does this happen for all Creditors or just a specific one?
[SeisaT] – Also using Sample Company data, I checked different Creditors with different Bank Accounts and the result is still the same – “Check/Payment No. cannot be blank”.
8. Does this happen for all Users/Pc's?
[SeisaT] – Yes, it happens to all Users with reversal rights as well as ADMIN on different PC’s.

1. Have you tried to do a data dump and load into new SQL Database ID's and see if this make any difference?
[SeisaT] – I had just done a data dump of the live dataset and preparing to load into new databases on my laptop (but different version), when I decided to try the reversal one more time, and voilà, the transaction just went through.
2. Are you able to replicate this in Sample company [SAMINC]?
[SeisaT] – Yes, I am able to replicate in Sample Company
3. Have you checked for any errors on the Restart Maintenance section related to this Transaction and Process?
[SeisaT] – There are no restart records associated with the records/transactions in question.
4. Are there any errors on this module within the Data Integrity check?
[SeisaT] – There are no Data Integrity errors in Bank Services
5. Have you tried to run RVSpy?
[SeisaT] – It was actually when I had RVSpy turned on that I noticed the transaction posting through successfully. So, there was nothing unusual for RVSpy to pick up.
6. When last was the client able to process the Bank Services - Reverse Transactions?
[SeisaT] – This is the first time that the Client reverse transactions in Bank Services. They normally use Peresoft Cashbook to reverse transactions.
7. Does this happen for all Creditors or just a specific one?
[SeisaT] – Also using Sample Company data, I checked different Creditors with different Bank Accounts and the result is still the same – “Check/Payment No. cannot be blank”.
8. Does this happen for all Users/Pc's?
[SeisaT] – Yes, it happens to all Users with reversal rights as well as ADMIN on different PC’s.