We currently allow seasonal fees for some organizations, but the system bills them for each date they submit which creates very large invoices that we then have to manually fix. If the peewee football team puts in 50 practice dates, the system will charge them the daily rate for each practice which makes the invoice come to $5,000. If we had a seasonal option for that group, the system could then charge the seasonal fee of $500, and my staff wouldn't have to go back in and erase the individual fee for all of the dates they requested.
Hi @Guest
I like this idea. How would you manage "seasons" inside of ML schedules? This topic comes up occasionally, and I'm curious about your approach.
Should seasonal rates be applied to certain groups only? Or at the classification level?
-
Your team is approaching the workaround correctly. It sounds like a better option would be to put that group in a classification that doesn't get charged. Then, you can still invoice them when you're ready via bulk invoice and add an additional charge for the seasonal fee.