[GNC-dev] About 3.9 and reconciliation balances

[Adrien Monteleone]

I concur.

It is not unusual for a transaction to be made in one period and clear in the next, even in modern times. This is highly probable with issuing a paper check. Lower date bounds are going to be a problem.

While I don’t think there is much case (though one user reported so) for a future date (beyond ’today’) there is a case for including a transaction dated past the statement date.

If you need to enter a balancing or correcting transaction some users may prefer the date of that transaction be the day it was made, not ‘as of the closing date’. Sticklers for using correcting transactions (as opposed to editing transactions) are likely to prefer such dating. This date can very likely be more than ’closing +1’.

Regards,
Adrien

> On Apr 17, 2020 w16d108, at 9:27 AM, Dale Phurrough via gnucash-devel <gnucash-devel at gnucash.org> wrote:
> 
> As an attempt for clarity, I don't globally agree with what David wrote
> "The dates in a statement will all fall between the end date of the last
> statement +1 (the start date of the current statement) and the end date of
> the current statement as the statement dates are inclusive."
> 
> I believe in the global (as in all scenarios all possibilities) that the
> dates for transactions in a statement would be on or before the end date of
> the current statement. However, such transactions could also be before the
> end date of the last statement. I have countless examples of this where I
> caused/made a payment before the end of month and that payment wasn't
> booked by a bank until the next month. In this scenario, the date that one
> wants in GnuCash might be the causation date or the booking date.
> 
> I believe it is the user's choice of which date to save into GnuCash:
> either the date the transaction was caused (e.g. data entry into GnuCash)
> or the date the bank finally booked it. So the date should not be lower
> bounded by the end date of the last statement. Instead, only upper bounded
> by the end date of the current statement.
> 
> Follow my thinking?
> 
> --Dale