Christopher,
Those are all very good points. I do think that the goals are laudable, and I
think Dale's call for further analysis is a good approach. The question of what
reconciliation is supposed to be, and what it's supposed to do (beyond the most
rudimentary textbook descriptions) are not
I was not aware that AQbanking does a reconcile on the fly. I also use OFX,
CSV nad very occasionally QIF imports (but not from Quicken) but not that
heavily any more. I think it would be useful to have this information about
the reconcile marking process documented at least in the importing
The "purpose" for the "fix" was to allow future features:
1. allow manual reconciliation of an account, using past reconciled_date
and relevant past ending_balance. If my "fix" were applied, it would serve
*me* very well:
(a) If an account, properly reconciled, had an errant split hiding
Yes JR and DA
Nothing bad or sinister, rather a future opportunity to virtually
whiteboard the concepts and events surrounding "reconciliation", then
reviewing what gnucash currently does to see the gaps.
It's comforting to see that it works for so many scenarios, and the
discussion on this was
I just posted my first result and impression to the bug report, though I’m sure
you saw that already. (this is more for the benefit of list readers not
following the bug)
The signs aren’t making sense, and the amounts aren’t adding up correctly.
Regards,
Adrien
> On Apr 10, 2020 w15d101, at
Dale,
On Fri, April 10, 2020 12:37 pm, John Ralls wrote:
>
>
>> On Apr 10, 2020, at 8:22 AM, Dale Phurrough via gnucash-devel
>> wrote:
>>
>> This feels like a separation of accounting logic -- separate from
>> storage
>> field -- has broken down. From what you wrote, it seems each of these
>>
> On Apr 10, 2020, at 8:22 AM, Dale Phurrough via gnucash-devel
> wrote:
>
> This feels like a separation of accounting logic -- separate from storage
> field -- has broken down. From what you wrote, it seems each of these
> sources have direct access to core fields without any
Wow...this mix-match of reconcile date behaviors are good to log somewhere
as an design/architecture aberration/bug. Good for discussion on...
1. what *does* the concept of "reconciliation date" mean?
2. does that meaning change with the source of reconciliation/truth (qif,
quicken, AQBanking,
Some further findings. I don't think the "fix" needs to come back.
The reconciled_date field is not well defined in code
- during manual reconciliation (which I use heavily) it sets
reconciled_date to statement_date.
- during QIF import from Quicken, it can also set reconcile_status to
mirror
Next addendum: your existing budget data will behave well when reverse
balances=credit accounts, but the *featured* data will be stable with *any*
reverse balances global preference option.
On Fri, 10 Apr 2020, 11:28 am Christopher Lam,
wrote:
>
>
> On Fri, 10 Apr 2020, 10:20 am Christopher
Hi David,
Am 10.04.20 um 07:36 schrieb David Cousens:
> Gunter Kamp
> seemed to have a related but slightly different issue associated with
> AQbanking. Banks here haven't generally allowed any direct server access
> other than downloads from their web portals so i have no familiarity with AQ
>
11 matches
Mail list logo
