#Jonas-tax
1 messages ยท Page 1 of 1 (latest)
Hi! we cannot really help with this types of questions here. I would recommend to ask that directly to Stripe support here: https://support.stripe.com/?contact=true
And FYI you can find the list of Stripe apps and extensions on this page: https://stripe.com/partners/apps-and-extensions
๐ Thanks ๐
hi @opal dust
I've encountered two other questions regarding invoices.
I think nearly every company in the EU will have exactly the same questions:
-
Quite often customers want to change to the billing address / the contact person on an invoice. Is there a way of changing that info for "finished" invoices? Or how should we deal with that change request?
-
Quite often user forget to add their vat-id/company name (we offer the
tax_id_collection). Is there a way to add this vat/company info to a "finished" invoice?
Or also happened a few times in the past for (2): User had a typo in the vat_id and wanted to change it on the invoice
What do you mean by 'finished'? Paid? Draft? Open?
Paid or open
E.g. a user purchases a subscription. At the end of the month he checks his invoice because he has to send the invoice to his tax consultant.
Then he sees that he has a typo in the address/vat_id or anything and want a change there.
He will email us and aks: "Hey could you please update the XY on my invoice, because my tax consultant asked me".
The invoice is already paid. According to the documentation only draft invoices could be changed.
But how should we handle this common scenario?
Yeah, you can't unfortunately. Once open (finalised) or paid they're immutable
Ok. So the workaround is to refund the payment and request a new payment?
Or is there anything in the roadmap to offer such use cases?
I think refunding does not make that much sense, because we have to pay the transaction fees to stripe (which might be lot for high price products)...
I don't know I'm afraid!
I'd suggest double/triple checking invoice details before sending them
ok. Is there any stripe team which I can contact for support?
In regards to?
To ask
- how to handle such use cases
- if there is anything in the roadmap to support such use cases (e.g. function to create "Correction invoices")
The options are limited, I'm afraid:
Draft invoices are fully editable. Once an invoice is finalized, monetary values, as well as collection_method, become uneditable.
If paid then it's completely immutable AFAIK
It's a pain point for many users, but I'm not sure what is currently on the roadmap to address it
ok anyway. Thanks for your help...
Np!