In order to understand why there is an issue when you unfinalize a deposit that has had a void it is first important to understand what happens with iGovServices when a session is balanced and finalized.
When you click balance on a session in the balancing process a few things happen:
1. In the Receipt header table there is a flag that changes from 0 to 1. This means that it goes from zero which is unbalance, to one that is balanced.
2. When a payment is made an entry is made in the Pending Payments table.
3. When the deposit is finalized and after balancing the session, iGovServices moves the entry from the Pending Payments table to the Payment History table, as well as, making general ledger entries into the GL_Tran table.
4. When a deposit is unfinalized iGovServices does the process in reverse. The entries in the Payment History table are moved to the Pending Payments table. At this time if you wanted to unbalance the session you could and redo the balancing portion.
5. So let's think about this process if a receipt is voided. Now there are no entries in the Payment History table and when you try to unfinalize the deposit there is nothing to move back to the PendingPayment table. That is why an error is received letting the user know that they have to delete the receipt.
6. If you delete the receipt then you will be able to un-finalize the deposit.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article