-
Notifications
You must be signed in to change notification settings - Fork 95
Allow ticket buyers to download their invoice #103
Comments
+100 |
https://wordpress.slack.com/archives/community/p1417798076002376 It seemed to me like everyone who was interested in this wanted it for slightly different reasons, and there were several different ways suggested for how it would be implemented. So, before we build anything, I think it'd be helpful if everyone who wants it could get together and nail down what the underlying need for it is, and hash out the exact features and how it should work. Without that, I think we risk wasting a lot of time building the wrong thing. |
@iandunn True. Should we post expectations right here, or in separate issues? |
Here is fine, but it'd probably be better to have a chat in #community, and then post the link here, so that more people will see it and participate. |
I think one and probably the easiest way to 'batch' a group of tickets together for a company would be by expanding the discount code system. It would allow a company to 'sponsor' the event in a different sort of way form the traditional single donation scheme. They could apply for a group savings code where they agree to pay x% of the full ticket price for a group of tickets. Then at a specified cutoff date the company would be invoiced for that amount. I see this working in basically two scenarios.
Each scenario has a specific cutoff date and all tickets not allocated by that date are nulled. The cuttoff is to ensure that the company makes good on their commitment. I know from chasing down sponsors at WCNYC it is important to have the $ in before the event. |
This is a bit different to what I'm requesting. What we need is an automated way to provide invoices. We get asked for them all the time. What I envisage is this: User end
Organiser end
|
More discussion: https://wordpress.slack.com/archives/community/p1418127998000044 |
After reading the slack discussion I want to add one question which I don't find answered there or here: |
It'd be better to ask the Foundation that. |
We had over 60 people at WordCamp Sydney ask for a proper invoice which we could not generate. They need tax rates to show so they can properly claim back purchases as a business expense. The purchase acknowledgement is just not enough. We tell them to login to PayPal and print out the transaction but ideally if we could set up a tax name and %, then generate a proper invoice email rather than just a purchase confirmation that would do the trick. Doesn't need to be fancy. |
Andrea has been looking into VAT issues for European camps, which might end up with the site having access to rate data, etc. I don't think that'll be ready in the near term, though, since there's lots of financial, legal, and technical obstacles to overcome. In the mean, time, the idea I suggested in #149 (comment) might work, since organizers could enter their own percentage. That would still be cumbersome if different attendees needed different percentages, based on their physical location, though. |
Further discussion here: https://make.wordpress.org/community/2016/07/12/automated-ticket-invoicing/ |
Hello, As camptix users, our team of organizers make a separate Camptix Addon to send Invoices to attendees. The plugin also permit to edit custom invoices (for sponsors). Feel free to contribute or use it the way you want : https://bitbucket.org/willybahuaud/camptix-invoices (this plugin is also waiting for approval on the wordpress plugins repository) |
As suggested by Siobhan on the Community Slack: "Could there be something whereby, after someone buys a WC ticket, they can click a "Request Invoice" link and an invoice is auto-generated and emailed to them?"
And as Andrea said: "European organizers would thank you forever and ever and ever" I agree :)
Also, from Mikel King: "it would be helpful for companies that want to buy a batch of tickets for their employees if they could select each one or group by domain name email addie and invoice the total group."
The text was updated successfully, but these errors were encountered: