scheduled transactions, part deux

I agree. You can't memorize the form for the transaction, so you can't schedule a Group transaction that contains any transactions with forms.

Bummer. But at least I wasn't overlooking something staring at me on the screen.

OK, follow-on question. I started using the special form-related paycheck setup when it was introduced, simply because I wanted to try out the new feature. But is there really any advantage to using them vs. a simple split transaction that can be memorized and scheduled in a group? (I don't even try to set things up to get a direct import into TTax.)

I'd say that if you haven't answered that question for yourself in the affirmative, you probably won't miss the form at all.

But I thought that seeing only a plain split transaction in your Group generated transactions, instead of seeing the paycheck form, was a problem for you. If you don't mind getting plain split transactions, isn't that what you're getting now?

I think the Paycheck Wizard does make it easier to create the paycheck, so I'd use it for that reason.

[The Paycheck Wizard will set some things up for you that you might have to think about in order to get them right. But if you needed a guide, you could use the Wizard to setup a paycheck, enter one paycheck in some account register, create a transaction report showing all the split lines ... then create your own non-Wizard paycheck to match the one the Wizard created.]

I just re-read my initial reply to you, and I think I phrased it badly.

I said: "You can't memorize the form for the transaction, so you can't schedule a Group transaction that contains any transactions with forms."

The first part of the sentence is correct, you can't memorize the form when you memorize a transaction that has a form; you only get the split lines, not the form.

The second part of my sentence is misleading, at best.

As you already noted, you can include the memorized paycheck transaction (the one that has only the split lines, but not the form) in a Group Scheduled Transaction. The resulting register transaction will, like the memorized transaction, have no form.

Not a problem per se, just unexpected and I wanted to make sure I wasn't missing a trick.

From a purely functional standpoint, I don't mind using the split transaction but the forms are a bit nicer to work with.

Which is how I got to where I am now, and I did notice that the split created by memorizing the form did do some 'tricks' on the employee match of the 401k - something that, as you say, I would have had to think about a bit to get right.

Thanks for the feedback, John. I don't come here often, but you are always helpful when I ask.

- Ed