As others have reported, this change was *meant* to be more strict in
interpretation of reconcile *statement_date* (which eventually becomes the
split's *reconciled date*). My suspicion is that your first successful
reconciliation used an incorrect *statement_date* which led to the second
reconcili
Please reply to the list or use reply all
On Sun, Apr 12, 2020, 5:22 PM Art Chimes wrote:
> David,
> Thanks for the quick reply. I will see what others have to say before
> I decide whether to go forward or revert!
>
> Meantime, I'll peruse the developers' mailing list to see what I can learn.
>
Art,
Are you using GnuCash V3.9 If you are please either revert to 3.8 or upgrade
to the newly released 3.10 version which reverts changes in 3.9 if the
following is causing your problem.
The problem I encountered in 3.9 was that the starting balance did not
include reconciled transactions which
There is a big discussion going on in the developer arena about what is
wrong with the reconciliation process in release 3.9 I suspect that you
may being an artifact of that. They have released 3.10 in an attempt to
fix that, but if you are conservative you may want to revert to 3.8 instead.
Per
Strange to me, anyway.
I have a long-closed U.S. mutual fund account (call it ABCDX) that was
never reconciled since I started using GnuCash a year ago. Now I want
to reconcile it, and I'm tackling it year-by-year.
I reconciled the first year closing balance, 5,898.936 shares, without issue.
Pro
