[GNC] Scheduled transactions: Why create in advance?

Stephen M. Butler kg7je at arrl.net
Tue Jul 9 19:00:46 EDT 2019


On 7/7/19 12:46 AM, AEG via gnucash-user wrote:
> Having found that the only way to see the future effects of scheduled
> transactions on my account balances is to "Create in advance", I went
> through the tedious process of individually setting all 60+ of my scheduled
60!!  Wow.
> transactions to create 14 days in advance, then later going through the
> whole process again to change this to 7 days in advance. (A global setting
> would have saved a lot of time!)


So:  Edit - Preferences - Scheduled Transactions  and set the Create in
Advance # of days didn't work for you? 

>
> Although creating in advance is not a problem for some transactions,
> undesirable consequences with others have persuaded me to abandon this
> feature entirely and rely on AceMoney to provide the information I seek. (I
> had hoped to discontinue use of AceMoney in favour of GnuCash). The problem
> I refer to is as follows...
>
> Two of my scheduled transactions, which were set to create 14 days in
> advance, turned out to have errors or lacked information that I wanted to
> enter on those and all future transactions. This meant that, not only did I
> have to edit the future transactions in Transaction Editor but to also
> individually edit the ones that had already been created.


Yup, I make typos also.  Easy to fix.  A couple of my transactions (one
being the mortgage payment, change every month.  Thankfully I get
advanced notice of the real values and can modify the scheduled
transaction before it is created.  Missed doing that a couple of times. 
My fault.

>
> If the transactions were just made visible in the account registers but not
> created, I would have been able to spot the errors and change the scheduled
> transactions before any of them were created, which is something I can
> easily do in AceMoney. This leaves me wondering how/why others use the
> "Create in Advance" feature because I'm finding it difficult to understand
> why it exists.


Because it works for me for the handful of scheduled transactions that I
have -- most of which don't change or might change once a year.

If it doesn't fit your style, find something that does.  Or jump in and
submit code to add an enhancement.

Maybe create yourself a spreadsheet, convert to a csv transaction file,
import it.

>
> Alan
--Steve

-- 
Stephen M Butler, PMP, PSM
Stephen.M.Butler51 at gmail.com
kg7je at arrl.net
253-350-0166
-------------------------------------------
GnuPG Fingerprint:  8A25 9726 D439 758D D846 E5D4 282A 5477 0385 81D8




More information about the gnucash-user mailing list