[GNC] Scheduled Transactions: Monday before the 4th Wednesday

Stan Brown (using GC 4.14) stan+gc at fastmail.fm
Wed Nov 1 15:57:16 EDT 2023


Thanks for the suggestion, Kevin.

It's an interesting idea, but it looks like it would be more work than
I'm doing now. And also ... I could make a mistake in setting the dates
manually. With the present scheme -- 4th Wednesday of each month,
transaction posts two days early -- at least I can trust GC to get the
dates right.

Stan Brown
Tehachapi, CA, USA
https://BrownMath.com

On 2023-11-01 04:11, Kevin Buckley via gnucash-user wrote:
> On Wednesday, November 1st, 2023 at 03:32, Stan Brown <stan+gc at fastmail.fm> wrote:
>> Every month, I get a direct deposit two days before the fourth Wednesday
>> of the month. ...
> 
> Best I could come up with is to suggest that you define a set
> of Scheduled Transactions (SchedXn) that all start on a known
> Monday before the 4th Wednesday, and repeat every 28 days, but 
> start a new SchedXn once you hit a Monday before the 3rd Weds.
> 
> FWIW, some UNIX shell commands (apologies to all of the
> non-UNIX Shell users out there!) to generate a year's
> worth of 28-day apart dates, are
> 
> s=0
> for n in 0            28              56         \
>               84             112             140 \
>                      168             196         \
>              224             252             280 \
>                      308             336         \
>              364 ; do \
>   s=`expr $s + 1` ;
>   echo -n  $s " " ;
>   date +'%Y%m%d' --date="Mon Oct 23 2023 + $n day" ;
> done
> 
> (and, before anyone asks, it's merely a cut-down version of
>  something that generates a yearly set of fornightly dates,
>  given a starting date, but with the starting date changed)
> 
> Here's what that produced, starting with your Mon Oct 23 example:
> 
>   20231023
>   20231120
>   20231218  before 3rd Weds, start from next Monday
> 
>   20231225
>   20240122
>   20240219  before 3rd Weds, start from next Monday
> 
>   20240226
>   20240325
>   20240422
>   20240520
>   20240617  before 3rd Weds, start from next Monday
> 
>   20240624
>   20240722
>   20240819  before 3rd Weds, start from next Monday
> 
>   20240826
>   20240923
>   20241021
>   20241118  before 3rd Weds, start from next Monday
> 
> 
> I'd suppose that once you have passed the end of each SchedXn,
> you just change the start date to the correct date for the
> year after and see where you get to.
> 
> Cave: leap years may well stuff things up, but you should
> get the jist, of how to think about it, and to take account
> of the extra day, I'm sure.
> 
> 
> FWIW, each of the five SchedXn-s above would be defined as:
> 
> Start Date: 20231023, Freq:  Daily, Every: 28 days, Occurences: For 2 
> Start Date: 20231225, Freq:  Daily, Every: 28 days, Occurences: For 2 
> Start Date: 20240226, Freq:  Daily, Every: 28 days, Occurences: For 4 
> Start Date: 20240624, Freq:  Daily, Every: 28 days, Occurences: For 2 
> Start Date: 20240826, Freq:  Daily, Every: 28 days, Occurences: For 2 
> 
> HTH
> 
> 
> _______________________________________________
> gnucash-user mailing list
> gnucash-user at gnucash.org
> 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.


More information about the gnucash-user mailing list