notKate-invoice-retroactively

[smoky flower]

This is not really possible unless you generate a $0 Invoice

You can create invoices and immediately void them, I believe, which will make sure they don't get paid, though I hesitate to recommend that: https://stripe.com/docs/invoicing/overview#void

[fallow dew]

yeah i think that would generate an invoice id but break the rest of the modelling

i suppose if we are joining on ids we could keep it in draft?

still wouldn't be able to join on payment intent etc

because it would be a different payment intent id

could we use auto_advance false?

[smoky flower]

Yeah, if you create an Invoice that does not auto-advance and make sure to void it after all the necessary updates have been made to associate it with the already paid invoices, then that could work. You might want to add all the details from the paid Invoice as metadata on the new voided Invoice though.

https://stripe.com/docs/api/invoices/object#invoice_object-metadata

[fallow dew]

wait but the paid invoice doesn't exist? or is there always an invoice object in the background?

[smoky flower]

Err, sorry. I meant "paid Payment Intent"

I assume that's what you meant at the beginning when you said Invoices were paid but not generated.

[fallow dew]

aside from the fact its not the actual intent of a voided invoice, what are your hesitations with using void?

[smoky flower]

I was mainly just concerned because I thought you were creating them via the Dashboard at first (not sure why)

[fallow dew]

would you say these are the main options:

also is this accurate?

[grave ivy]

Hey two-shoes had to step out for a bit. I am catching up on this thread and will be able to help soon

Those would be valid options for what you are looking to do