#mm-julian-invoices

1 messages · Page 1 of 1 (latest)

fringe snow
#

I would say a better way to test this is to set trial_end to a few minutes in the future, when the trial ends it generates a draft recurring invoice

potent breach
#

Ok, thank you for helping me. I will have to use something else for setting additional fields though as invoices generated by setting the billing cycle anchor and upgrading/downgrading a subscription also need that additional information.

#

Is there another way of doing that except setting them on the customer?

fringe snow
#

you can only set custom fields on the Customer level or the Invoice(when it's not finalised) , so yeah, not really, setting it on the Customer is the way to go.

#

these immediate invoices do cause problems unfortunately which is a known problem with the design. I haven't tried it, but maybe if you pass payment_behavior=default_incomplete when making the update, the invoice is left unfinalised, but I don't think it works for resetting the anchor or the other cases in that doc.

potent breach
#

Yea I'm allready passing default_incomplete

#

I'll just keep the fields on the customer up to date when doing subscription changes then. Those fields contain information that is legally required to be on invoices in germany so setting them using the webhook would be prefferable.