Rafsark

13 ms·

121.
by Rafsark 4y ago
Couldn't agree more on this. Even if finance, sales, marketing or other deps are involved, billing is an engineering thing! Back in 2016, while building the billing system for qonto.com (european fintech unicorn), we were surrounded by
122.
by Rafsark 4y ago
Ahah so sorry. Hope this is because of the substance, not about the form ;)
123.
by Rafsark 4y ago
What are the top 3 things you learned that every company should be aware of? Could be interesting to have an experienced view on this :)
124.
by Rafsark 4y ago
For sure; I do think an event based solution working as a source of truth for the billing is the right solution. However it still creates engineering difficulties (making sure you don't ingest the event twice for instance). The ledger-
125.
by Rafsark 4y ago
I think it's easier for billing systems to have 1 subscription for 1 customer. The reason behind this is mainly because you can apply several prices to the same feature belonging to two different subscriptions. Stripe does not work on
126.
by Rafsark 4y ago
For simple subscription-based billing, it's somehow not this hard, you are right. It also depends on how much plans you provide to your customers, and you still need to scratch your head for upgrades and downgrades. I truly believe in
127.
by Rafsark 4y ago
Yep, fortunately in Europe we can issue credit notes, making our job easier. I do think giving the possibility to send charges information to a webhook is a great way to start: this data can be plugged to any invoicing system (or any tax, p
128.
by Rafsark 4y ago
Hi! We decided to aggregate all costs of a "billable period". Imagine you bill your customers monthly (the billable period), all the charges (usage-based features + subscription) will appear as line items of a single invoice. This
129.
Billing systems are a nightmare for engineers(getlago.com)
777 points by Rafsark 4y ago|359 comments