PLEASE "add the new journal entry batch insert and duplicate feature where you want them" capability to RECURRING BATCHES!!!!! This feature is only available in Regular Batches. Currently the Recurring batches have no insert option, and the duplicate line option still adds it to the bottom of the journal entry.
I completely agree with this request! We have a lot of journal entries that change on a regular basis. Many things are the same, so using a recurring entry is helpful. HOWEVER, it is ridiculous that you are not able to insert a line where you want to. As was said below, the work seems like it has already been done. If you have a recurring entry with 500 rows (we have several), it is very helpful to have them in alphabetical order. Being able to edit and add rows where they are most helpful would be great. Please consider this request!
Additional information on this topic... I use edit function of journal entries to use the journal entries as recurring entry templates, to build the final result journal entries. Each month the accounts used varies by fund and situational need. Many of the line items stay the same, but not all. The ability to add lines within the EDIT function would be a game changer. I do this process with 50 entries every month. We got the functionality of adding lines where we want, but it doesn't work in the edit process/stage. Please think hard on this one.
If someone knows a workaround to this, please let me know.
It occurred to me that the work has already been done in reference to my request to add the Journal Entry line insert and duplicate capability. I could be wrong, but wouldn't it be a simple thing to add this already completed improvement to "Journal Entry's" close cousin, "Recurring Journal Entry"?
I use at least 50 Recurring Journal Entries monthly. Even though the entries are recurring, they are not identical. So, each one of these recurring entries is subject to needing lines inserted on the fly. Are there other users out there who have the same issue? If so, please vote so it stands a chance of being implemented. Thank you ☺