Hi Sherlock, Thank you — that explanation matches exactly what I am seeing, and it is very helpful.
On the share count: the 20,000 shares is the current balance of the 2026 lot, not its opening balance. The 2026 lot opened on 1 January 2026 with 100,000 shares carried over from the 2025 closing entry. During 2026 I sold 80,000 shares in several tranches (the last one on 22 October), leaving 20,000 shares as of today. The 2025 lot itself did open at 32,000, and the movements I listed earlier sum to zero: 32,000 opening −2,000 sale before the split +90,000 stock split (30,000 → 120,000, no change in total cost) −20,000 sale after the split −100,000 year-end closing entry = 0 So in 5.16 the 2025 lot shows a zero balance and a closing date, which is what I expect. A few questions before I touch anything: 1. For books that already contain this kind of pre-5.17 lot, is the duplicate-then-delete procedure the recommended permanent fix, or is it better to stay on 5.16 until a later release handles these existing lots automatically? 2. Does duplicating and deleting the stock split transaction change the transaction's GUID or break its links to the year-end closing entry and the realised gain/loss entries? I would like to avoid disturbing the audit trail. 3. Is there any risk of the adjusted amounts being counted twice if the hidden share-adjustment split remains in the lot while the new transaction is also present? 4. I see the same pattern in four accounts holding the same ETF (mine and three family members'), all recorded with the Stock Split Assistant. Would the procedure need to be repeated lot by lot in each account? I have not modified the book in 5.17; I am still using 5.16 so the data stays consistent while we sort this out. Thanks again, Thomas Chen _______________________________________________ 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.
