Combined with the variables, one could also use just 2 templates, set to
fire every 2 months (the minimum frequency - rather than every month),
but also set to not auto-create.
This would produce the following workflow:
1. Every 2 months, the Since Last Run feature would fire both transactions.
2. If this is good, then commit them using the variables to adjust as
needed.
3. If these need to be skipped, simply do not commit them.
-----
While certainly a single transaction can hit multiple accounts, if the
user employs the Description field for 'Payee' (as I do, and as was
fairly standard in pen & paper register days) then that won't work and
you'd still need 2 transactions, 1 per payee. (Federal & State)
Regards,
Adrien
On 6/2/26 1:50 PM, Mark Bourne wrote:
I don't know if it would ease the burden of editing the transactions,
but you can use variables in the template transactions and the "Since
Last Run" dialog will then prompt for the value(s) each time the
transaction is due. Where you would normally fill in debit/credit
amounts in the template transaction, instead enter a word such as
"estimate". Use the same word in both splits, and it'll prompt for the
value for "estimate" each time the transaction is due and use the value
you enter for the transaction.
That would avoid needing to go into each template transaction to edit
the amounts, at the expense of needing to manually enter the amount each
time.
Another workaround would be to schedule the transaction for every month,
and just select to skip entering the transaction in the "Since Last Run"
dialog when it comes up in the months you don't need it.
Neither of those options is perfect, more a matter of working out what's
least inconvenient ;)
_______________________________________________
gnucash-user mailing list
[email protected]
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
-----
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.
