|
Emil
|
August 17, 2015 at 4:31 am
Hi,
We decided to use Transaction ID as our Invoice number. That means that when a registrant registers, an invoice with the ID identical with the Transaction number is issued to that registrant.
However, some of them might not pay eventually for the event. That leads us to the point where we have to mark some invoices as cancelled. That gives us some paperwor to do, because we anyway have to list the invoices, mark them as cancelled and file them in our accounting files.
Usually in business, to avoid that, we issue Proforma Invoices before payment, and Commercial Invoices (aka Invoices) only after the payment. Proforma invoices do not have to be filed anywhere in the accounting systems, so there is no need to track which one of them was paid or not.
Does EE4 support such an implementation? If not, can you suggest me some workarounds to get to this functionality?
Thank you.
Best regards,
Emil
|
|
Josh
|
August 18, 2015 at 3:32 pm
Hi Emil,
Would it work for your system to use the Event Espresso Invoice as the Proforma invoice (before payment), then use the Event Espresso Receipt as the Commercial Invoice (after payment)?
|
|
Emil
|
August 19, 2015 at 4:00 am
Hi Josh,
Looking at the way the templates for Receipt and Invoice are set up, it would probably better to use the Receipt as Proforma invoice, and the Invoice to remain Invoice. But the templates are interchangeable, so if you see any solution in which the Receipt cand be made to have a different ID from the Invoice, and that ID to be generated only for paid registrations (and able to be reset from year to year) that would be great.
What we need, as I’ve said, is to have a means of”:
– issuing the Invoice only for the paid registration
– having a field on the invoice for the invoice ID which is incremented only with each confirmed payment, and which can be reset yearly
– having the Date field on the invoice to be the date we’ve confirmed the payment, not the date when the registration in EE was made.
Thank you.
Best Regards,
Emil
|
|
Josh
|
August 19, 2015 at 5:15 pm
Hi Emil,
It turns out the custom ID and date fields are not something we can support at the moment, but we can recommend contracting with a developer to extend the basic functionality to meet your specifications. Here’s a list of developers that we can recommend:
https://eventespresso.com/developers/event-espresso-pros/
|
|
Emil
|
August 20, 2015 at 2:19 am
Hi Josh,
Thank you for your answer. We will probably change the name of Invoice to Proforma Invoice, and we will issue invoices either manually or using a third party invoicing software connected wwith EE4 via API. It will be probably cheaper to implement than to modify EE4.
If I may, I have a suggestion for you. It’s something similar with sponsoring a certain feature development you already have. Why don’t you create an open list of feature requests where each of EE users may add what feature they request, and what amount of money they are willing to offer to support the development of that feature. Each feature request will be listed only once, so when another user want the same feature, he only enters his data and the money he is willing to spend to support that development. When you see there is enough money promised for a certain feature, you let the potential donors know that you are ready to start developing it, we pay what we promised, and you make it happen.
Thanks again.
Best Regards,
Emil
|
|
Josh
|
August 21, 2015 at 7:12 am
Hi Emil,
It turns out we do have a publicly viewable new feature roadmap, but we reserve the right to only add features that we intend add. We generally do not add one off customization requests to our roadmap.
|
