This sounds like a time zone issue. Long after 2.6.12, at least one bug was discovered where some transactions ended up with an 'internal' date different than the displayed date due to certain code with respect to time zone interpretation. You might have more transactions off than just those on the 1st of the month, but those are illustrating the issue.

It will not hurt, if you have not done so, (which *should* have been part of your upgrade procedure) to run Actions > Check & Repair > Check & Repair all on your file. (make a backup first, just to be safe)

If that doesn't work, or you have already done so, then maybe one of the devs with more intimate knowledge and better memory of this particular issue can offer advice.

Regards,
Adrien

On 12/28/23 1:19 PM, Leo Braga via gnucash-user wrote:
Hi,

I'm a long time home user (for personal finances) and I was "stuck" in
2.6.12 for a long time, until deciding to upgrade to 5.4 last month.
Everything was looking good, but now I found a very strange bug in my
Reports (Expense or Income Charts to be precise).

What happens is that some entries dated the 1st of the month are reported
in the previous month! So an entry dated Nov 1st is computed in the Expense
Over Time report for October, for instance.

I don't think this is affecting all entries dated on the 1st of a month,
but maybe yes? What I tested is that if I go to such an entry, change it to
the 2nd day of the month for instance, *then change back to the 1st*, and
then refresh the report, the reporting is now correct!

Any help would be greatly appreciated, as it will be crazy to go through
all entries for 2023 to fix this (for 2022 and earlier I have different
back-ups and thus don't care so much).

_______________________________________________
gnucash-user mailing list
gnucash-user@gnucash.org
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.

Reply via email to