I need this feature. Can’t be that hard to fix!
+1 Currently this is manual labor made after notice from bookeeping. It should be automatic or why to use computers when should do this kind on manual labor. 
+1
I’m a finance admin. We have three accounts. For the love of god OpenAI, this is 5 min configuration max! Pleeeease
+1 . This feature would save me 5 min of work
+1 for this request! This feature is really need it for many of users!
Always very disappointing when a company gets so large and holds such a monopoly that they don’t respond to base-level user requests.
+1 for this implementation, though I’m doubtful that OpenAI cares enough to prioritise this over other parts of the business.
Seems funny that OpenAI - a company so devoted to increasing human efficiency in innovative ways - is so unwilling to optimise this blatantly manual process that every other company has automated …
2 Likes
+1 such as basic feature that would save so many people quite a bit of time and hassle
1 Like
Definitely +1 for this feature which should be self-evident.
+1. Please prioritize this feature.
With all the talk about AI, it’s frustrating to see legacy companies ignore clear customer feedback.
How long would it really take to implement this with today’s tools? Not long.
And that says a lot — not about their capabilities, but about their culture.
+1
Very frustrating that this does not work
1 Like
+1
Please enable this as soon as possible.
someone else suggested sending an email to support@openai.com asking for a copy of the invoice. i sent one with “Please send me my latest invoice and receipt.” and it replied with the date, amount, invoice number, and a link to download the receipt. I will admit this was much easier than trying to dig through the UI do get to the receipt which was then just one more click and it contains the info that my accounting department needs.
so i’m going to automate this monthly email request. i’d still prefer an auto email option from openai themselves but this will suffice.
7 Likes
+1 yes, please! It could be so simple.
+1 It´s a must have feature.
+1
Absolutely needed feature! World top AI company and unable to implement this smallest feature. Shame on you!
1 Like
+1 This is so tedious work. Please send me an email with the invoice. Stripe got this feature built in so why on earth have this not been enabled.
User number 177 requesting the feature
1 Like
+1 As said above, please enable the Stripe feature to have the invoice sent. We have multiple accounts and it is tedious. Thanks!
ENOUGH of all this “please” and “would you be so nice to consider” …
Guys, I’m completely out of patience … for YEARS you let your users spend millions of minutes every month, billions of minutes every year to manually download those stupid invoices! Why?!
If there’s an actual reason, at least explain why it’s so difficult. You use stripe! What’s the problem?
Wondering what chatGPT says about this.
Answer from ChatGPT
Thought for a couple of seconds>
With the PDF-generation and “Invoices” page already in place, you’re really only adding:
- A scheduled job that runs once a month
- Email-sending logic that pulls each user’s latest PDF and hits your SMTP/ESP
- (Optionally) Link security if you don’t want to rely on your normal login flow
Here’s a lean breakdown:
| Phase | Tasks | Effort |
|---|---|---|
| 1. Hook up email preferences (½ day) | • Verify each user’s “notification email” is stored and validated | 0.5 day |
| 2. Scheduler & job scaffolding (½ day) | • Add a monthly cron/queue trigger (e.g. Sidekiq Cron, Celery Beat, EventBridge) | 0.5 day |
| 3. Email integration (1 day) | • Write code to fetch each user’s latest invoice PDF URL | |
| • Plug in your ESP/SMTP SDK, handle retries & bounces | 1 day | |
| 4. Template & link handling (½ day) | • Build a simple HTML/text template with a “Download your invoice” link | |
| • Decide if you want signed URLs (expires) or rely on existing login checks | 0.5 day | |
| 5. Testing & QA (1 day) | • Unit tests for fetching PDFs & email payload | |
| • Manual send test in staging; verify inbox, link clicks, login gating | 1 day | |
| 6. Deployment & monitoring (½ day) | • Roll out scheduler, set ENV vars/credentials | |
| • Add logging/alerts if sends fail | 0.5 day | |
| Total | 4 days |
TL;DR: Roughly 4 work-days for a single mid-level engineer to build, test, and deploy an automated “send invoice PDF” email every month. If you want extra polish (rich email designs, unsubscribe controls, analytics dashboard), bump to 1 calendar week.
Me: Is only one developer needed?
The “4 days” (or “1–2 weeks” for a more full-featured rollout) estimate is indeed for a single mid-level engineer carrying the work end-to-end. If you bring more people in, you can parallelize:
- 2 engineers could split: one builds the scheduler & email logic, the other handles testing/QA and deployment hooks, potentially cutting the calendar time to ~2–3 days—but you’ll incur coordination overhead (syncs, code reviews).
- 3+ engineers can further carve up UX (email template design), observability (logging/alerts), and edge cases (unsubscribe handling), but you’ll hit diminishing returns unless the scope grows.
So yes—those estimates assume one developer. Add more, and you speed it up proportionally (minus some overhead), or you can keep the same timeline and build a richer feature set.