"Dave Parrott +44 (0)171 542 9830" <[EMAIL PROTECTED]> writes:
> It would be really useful to be able to set up a list of recurring
> transactions that I don't have to enter manually every month. In
> the UK we have Direct Debits and Standing Orders that occur at
> fixed times each month and usually for fixed amounts, I'm sure there
> must be an equivalent in the US and elsewhere. I have 20 of these
> items on my main bank account and it currently takes a lot of typing!
Hold on for just a bit longer and I'll probably have the
infrastructure up to handle most of this. I'm actually working on the
GNOME register patch as we speak. Once that's done, the automatic
transaction stuff is near the top of my to-to list.
> 1. Each account should have associated with it a list of automatic
> transactions with default amounts and dates.
> 2. There should be an option to apply automatic transactions piecemeal
> as their target dates are reached or in batch mode for the whole
> month in advance. Batch mode is useful to provision-out all fixed
> liabilities at the beginning of the month.
> 3. It would be useful to be able to set a pivot date in the month
> (e.g., when salary is paid) so that batch-mode application of
> transactions occurs between pivot dates instead of on calendar
> month boundaries.
Initially at least, these transactions are going to be handled by just
editing a text file containing the scheme commands to register the
transactions. Later we'll probably have a GUI, but the text interface
will probably still be more flexible. There's no real way around
that, so we'll support both.
I want to get something up and running soon and then explain it and
get some feedback. If it needs to be changed (and it probably will),
then fine.
> 4. Automatic transactions should be editable to change the amount or
> date in exceptional circumstances. It should be possible to delete
> automatically applied transactions on a once-off basis while still
> leaving them in the transaction list.
Initially I'm going to have automatic transactions just create a
normal transaction when they "fire". You can do anything you want to
the new transaction after that.
> 5. Summary information should be provided per automatic transaction
> list (e.g., total liability).
Hmm. Not sure what you want here. Could you explain a little more?
--
Rob Browning <[EMAIL PROTECTED]> PGP=E80E0D04F521A094 532B97F5D64E3930
----- %< -------------------------------------------- >% ------
The GnuCash / X-Accountant Mailing List
To unsubscribe, send mail to [EMAIL PROTECTED] and
put "unsubscribe gnucash-devel [EMAIL PROTECTED]" in the body
