Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-sales domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the better-click-to-tweet domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-amazon domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-stats domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Batch Invoicing? | Event Espresso - Staging Server

Support

Home Forums Event Espresso Premium Batch Invoicing?

Batch Invoicing?

Posted: September 21, 2012 at 11:56 am

Viewing 1 reply thread


Melissa

September 21, 2012 at 11:56 am

Our site has dozens of events, and hundreds of registrations per month. It is currently set so that people can register online and still choose to pay later if they wish.

I understand the only way to invoice someone is finding their name, opening the payment record and clicking the Send Invoice button. It would take hours to do this one-by-one for each person who has not paid. I need a way to batch invoice all individuals for a certain class who have not completed payment. What are my options here?

It seems like there should be more reporting options available with EE in general. Just to be able to run different queries from within EE itself instead of having to export to Excel and parse data manually.


Dean

  • Support Staff

September 24, 2012 at 10:32 am

Hello Melissa,

The current system does not allow for batch invoicing as it wasnt designed for large numbers of attendees to register and pay later. It certainly is an interesting idea thought and I will add it to our feature request.

I will do the same with the report functionality, but did you have some reports in particular that you feel would be beneficial?

Viewing 1 reply thread

The support post ‘Batch Invoicing?’ is closed to new replies.

Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.

Event Espresso - Staging Server