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 Invoice numbering, Invoice Exports and payment reminders.... | Event Espresso - Staging Server
Hi,
I am in the process of locating an event management system for a customer.
Event Espresso seems to tick most boxes, but I have a couple of concerns.
1. There is no unique invoice number on the PDF invoices, this is a legal requirement for the UK.
2. Is there an export of the invoices, so they can be imported into say Quickbooks?
3. If someone has not paid for a booking, does the system send out periodic reminders?
1) There isn’t in EE3, though you could translate the Primary Attendee ID and use that as an invoice number (they never repeat). EE4 has a Transaction ID, which again could be translated into Invoice number, should wording be important.
2) Invoices can be exported to PDF. You can also export data to CSV (spreadsheet) file which can then be subsequently imported into your CRM.
EE4 currently does not have any export options.
3) No. Those would need to be done manually via the admin.
No problem, let me know if you have any further questions.
Viewing 3 reply threads
The support post ‘Invoice numbering, Invoice Exports and payment reminders….’ 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.
Post any questions about the language files, translating Event Espresso, or issues with our GlotPress site for translations here.