Welcome to the Sage 200 Evolution ideas Portal
Good Day
With AR AP Cashbook batches there is a setting under properties whether to allow duplicate reference numbers whilst filling the batch. This is fine, however Sage does not compare to transactions already posted on customer/suppliers/GL transactions.
Therefore this does not prevent the user from posting the same transaction twice. Ideally before posting the AR AP Cashbook Batch, Sage compares the refernces entered within the batch to those transactions already posted. If this is not found, well and good it's fine and can be posted, if there is the exact same reference posted in the Audit Trail Already, it would make sense to show a warning to the user saying 'the transaction with the same reference has already been posted'.
Thank you
What is the workaround for the problem today?
Presently no workaround, this just compares reference numbers within the Same AR AP Cashbook Batch. |
|
Your Designation/Role | Manager |
Email. |