Created attachment 372957 [details] snapshots showing credit-note bug in 2018-08-29 build Ver 3.2 has a bug where a Credit Note has the opposite effect, causing a Charge rather than Credit. About a month ago Geert acknowledged this and said the fix would be in ver 3.3. I just tested using the 2018-08-29 Maint build for Windows. NEW Credit Notes enter correctly but an old BAD Credit Note is still bad but cannot be fixed. The attachment has several snapshots and descriptions showing the problem.
The discussion on IRC (https://wiki.gnucash.org/logs/2018/08/30.html#T18:43:13) had a bit more detail that might be helpful.
There was a bug specifically for the opposite effect of credit notes: but 796766. The issue of ending up with two post transactions for one invoice may have been related but was already reported in a previous bug as well: bug 796054. As the primary issue of this particular bug is also the inability to clean up duplicate post transactions, I'll mark this as a duplicate of bug 796054 (which - incidentally I have fixed minutes ago. More details on the other bug) *** This bug has been marked as a duplicate of bug 796054 ***
Forgot to mention: the fixes will appear in tomorrow's nightly build.
This was marked Resolved Duplicate and Geert's 08-31 comment said it the fix would be in the next night's build. I'm sorry, but as of the gnucash-3.2-2018-09-02-git-3.2-177-gd07f759ca+ build, on 09-02, it is NOT FIXED. I think it was explained pretty well in the attachment, but I would also be happy to send you my actual .gnucash file if that would help. If so, please give me an email address to which to send it.
Have you tried to - run check & repair on your A/R account and then - tried to remove the duplicate credit note transaction ?
@rassrq.misc@outlook.com Do you still have this bad credit note in your books and can't get rid of it following my suggestions in comment 5 ? If so, you can send me your data file to the e-mail address of my bugzilla account and I'll check it in more detail.
