I posted a few weeks back on a random econnect AP integration error #305, upon drilling down I found a Steve Endow article that was very accurate on the issue within eConnect ( design flaw). Logic needs to change on the stored procedure, however it is from SQL 08 and is encrypted, we either modify and lose our rollback ability or we decrypt, backup and then modify.
Here is the article
http://dynamicsgpland.blogspot.com/2015/10/econnect-error-voucher-number-already.html
Any thoughts?
Mark