#steve_17024

1 messages · Page 1 of 1 (latest)

abstract emberBOT
sour lion
#

Good questions. Tackling new users first, I actually don't think there is a way to have a recurring per-seat price that bills at the end of the month with out current system. Only usage-based prices bill at the end of the month. There are a couple of options for doing that (repeatedly adding one-off invoice items, another usage-based product where the usage is always 1) but unfortunately they don't handle proration automatically so I think that would have to be calculated on your end to be able to always have that fee billed at the end of the month.

#

For #2, can you tel me about how your current users are billed and how you would ideally like this transition to look like from their side?

high aurora
#

recurring per-seat price
by this do you mean the flat fee?

sour lion
#

Correct

high aurora
#

isn't there an option where flat fee gets charged only if usage hits x threshold?

#

or another idea... if we instead change the flat fee to another metered price, where usage is always 1.
would that work?

sour lion
#

Good questions, looking in to those options and will get back to you.

high aurora
#

got it.
so then in general, all flat fee are always billed at the beginning of the month?

the other thing we saw was backdate_start_date = Sept 1 AND billing_cycle_anchor = Sept 30
and the option to set proration_behavior: 'none'

does proration only apply to the flat fee?

so if we have:

  • we create a subscription for a customer on September 15
  • backdate_start_date = Sept 1, billing_cycle_anchor = Sept 30, proration_behavior: 'none'
  • we report metered usage, 2 units on September 20
  • what invoice will show up on Oct 1st? and would there be any invoice before that?
sour lion
#

Not immediately sure on either of those now that I look at the docs again. Will try to test in a minute, if you already have a price like that set up in test mode you can try creating/updating a subscription with that price to see

high aurora
#

no worries, we can test this out in our sandbox environment
we were ambitiously hoping that this was a solved problem already and that we might have doing things in a wacky way🤞