Re:Stripe data is messy – is it for profit maximisation?
by maxisaurus on Thursday October 26, 2023 @09:57AM
(#38025621)
Same for Chargebee lol.
Was an analytics lead at a fintech company. We computed our revenues in our data warehouse based on Chargebee data. It was a nightmare because:
#1 - raw data is indeed very messy.
#2 - MRR can be theoretically be computed on either the invoice or the subscription table. Using invoice: sum the subscriptions fees by month. Using subscription: sum the subscription fees for the period where the subscription was active . Well, does not really work that way. In practice, invoice table holds a lot of noisy information not useful for MRR and get the active period for a subscription is not straightforward (involves snapshots and scd).
#3 — Discounts and offers. Chargebee's coupons and discount pretty much are a blackbox with some pecking order.
Long story short: we never had the same number as Chargebee UI.
#1 - raw data is indeed very messy.
#2 - MRR can be theoretically be computed on either the invoice or the subscription table. Using invoice: sum the subscriptions fees by month. Using subscription: sum the subscription fees for the period where the subscription was active . Well, does not really work that way. In practice, invoice table holds a lot of noisy information not useful for MRR and get the active period for a subscription is not straightforward (involves snapshots and scd).
#3 — Discounts and offers. Chargebee's coupons and discount pretty much are a blackbox with some pecking order.
Long story short: we never had the same number as Chargebee UI.