On 11/30/2025 2:59 PM, Patrick James via gnucash-user wrote:
Olly,
I just tested the Void Transaction and then Unvoid Transaction, and I am able
to unvoid the transaction. I'm not able to delete the voided transaction.
The not being able to delete a voided transaction is not a big issue (for me)
because the unvoid transaction feature works, and then the previously voided
transaction can be deleted.
Whether not being able to delete a voided transaction is a feature or a bug is
a separate question. Personally I'd consider it a bug, as having to restore the
transaction first seems like extra work, but maybe there is a good reason
behind the design.
Personally I'd consider it a feature, considering WHY a "void
transaction" would exist (rather than simply delete it).
Personally I would not use "void transaction" but that's because I
learned in pen and ink days and still follow formal rules. So for ME the
"void" word would be in the description of the correction transaction
(example voiding transaction of x1/y1/zzz1 -- which transact would have
ITS description altered to reflect the correcting/voiding entry. Full
audit trail.
So I'd say IF you were using VOID that would be in place of deleting
(which leaves NO audit trail). Once made VOID, should be locked. Remains
visible that the books were altered.
Michael D Novack
_______________________________________________
gnucash-user mailing list
[email protected]
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
-----
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.
