We process payroll donations bi-weekly and many of our donors are casual employees, meaning they do not give every pay period. I use a recurring batch that I have to edit every two weeks, but the batch template still saves me a ton of work!

We need this for our monthly payroll that is processed at the end of the month. As well as eft gifts processed directly through our bank account. We just modify the date, make adjustments as needed to designation or updated amounts and process the batch. Please don’t make us enter this from scratch each month. I’ve said this on other ideas. But unified view should do everything database view does. Then once all the functionality of database view is available you can provide enhancements.

Recurring batches save me so much time and without it - it would cause me a lot more work and stress.

Recurring batches have become essential for me to process certain monthly giving like corporate payroll campaigns. Use case: a single Benevity disbursement may contain 300 rows of transactions from different donors and companies but for our needs are consolidated into ~100 gifts (consolidating by donor payroll and by employer matches) on a recurring batch. The recurring payroll gifts need small tweaks each month (e.g., changing the gift date & ACH disbursement reference number on each transaction, accounting for a few people who had 3 pay periods during the month instead of their usual 2, or appending a few one-time payroll donations, etc), but having the correct constituent soft credits, event or proposal links, pledge credits, employer notes, etc already lined up on the recurring payroll transactions has been a game-changer. It has been the difference between an hour of work to tweak and QA/QC a recurring batch before committing it versus--due to inevitable increases in interruptions the longer a task takes-- a day or more of QA/QC and data entry if trying to create a new batch each time (even with a template and defaults).