Live data from Hacker News

My Stripe Tax Story

gist.github.com

41–50 of 299 posts

Re: My Stripe Tax Story

#41
My dad owns a successful chain of bicycle stores in Texas. He’s been in business for almost 51 years and he’s one of the largest bike dealers by volume in the country. He has nearly a hundred employees and a bookkeeper. Despite having a proverbial dozen balls in the air at any time and despite having people on the payroll to do bookkeeping, he sits down at his computer every night at home, logs into the ERP system, and reviews sales and receipts. He catches all kinds of crazy things. Credit card fraud (before the chargeback even comes), internal theft, mis-priced items, mistakes, you name it. He has great employees but even the best make mistakes and he’s learned this habit over the decades the hard way. I remember sitting next to him as a kid, watching him pour over cash register journal tapes that were yards long, looking for problems.

My point: if you let this kind of fuck-up go undetected for over three months, you have to at least assume some of the blame and acknowledge that you probably could have caught it if you scrutinized transactions. Every good business owner does it.

Re: My Stripe Tax Story

#42
post #13

This is why you need a good bookkeeper who will catch things like this when doing monthly reconciliation. There are so many ways that billing can fail and they all result in cash flow problems which is incredibly stressful.

Depends on how the integration’s set up, and whether draft invoices in Stripe sync to whatever accounting package as open invoices.

Re: My Stripe Tax Story

#43

I'm not quite understanding the need to put them on blast here. Yes, they should have been more apologetic and they should certainly have escalated your ticket more quickly. But they made the changes you wanted seen: better documentation & better process, and reaching out to customers proactively when they see this problem.

(I work at Stripe but don’t in any way speak for the company. This purely personal.)

I don’t mind them publishing this. It doesn’t feel unfair or dramatizing or in bad faith (etc.)

At the end of the day we build things to try and make other humans’ lives easier; to wrap the complexities of “global financial internet infrastructure” so business owners like the OP can focus on things that are not “collecting Canadian taxes”.

Whether Stripe ended up making the “right” changes in this case or not, we didn’t hit that bar.

And as “someone who works for Stripe but absolutely in no way speaks for Stripe”, it’s a productive reminder of the downstream effects of what we build. What we build has real world implications, ones people at Stripe take very seriously.

It hurts to read about the misses, but I would 10000% rather read about it on the front page of HN than us not know about it. And in this case, again, what they wrote doesn’t feel like it’s in bad faith, so it’s useful feedback.

Re: My Stripe Tax Story

#44
That sequence of events is exactly what I'd expect for a "we screwed up, but not in a way to incur any legal liability"

1. Generic answer that "yep, it's not working, here's how to fix it" 2. Updating documentation to make it better. 3. Somebody saying "what should we do about all the other customers in the same situation? can we just shut up about it?" leading to the last email.

And then... yeah, you can't directly apologize and take responsibility because that would cost you a fortune (and really, back billing is the right answer, though maybe he could in turn offer his customers a month's discount or something). Maybe Stripe could waive some fees for a while or something, but you have to have some limits on hard to use but technically correct situations.

Re: My Stripe Tax Story

#46

My dad owns a successful chain of bicycle stores in Texas. He’s been in business for almost 51 years and he’s one of the largest bike dealers by volume in the country. He has nearly a hundred employees and a bookkeeper. Despite having a proverbial dozen balls in the air at any time and despite having people on the payroll to do bookkeeping, he sits down at his computer every night at home, logs into the ERP system, a…

One more thing to add to this: scrutinizing transactions isn’t just for catching bad stuff. It’s also a way to spot the good. For my dad, it’s a way to spot up-and-coming salespeople who are punching above their weight, for noticing high-dollar sales to repeat customers and making sure that those folks are well cared-for. It also tells him what bikes are selling well and helps him make strategic decisions for buying.

For your SaaS, it might be noticing patterns across your customer base and using these patterns to refine your product to cater to a certain facet of customer that seems to like your product, or spotting potential transactional issues before they cause a churn.

Re: My Stripe Tax Story

#47
Sad to see Stripe fall to the bean counters instead of staying focused on customers. They were coming out with some cool innovations a few years ago. Even "don't be evil" Google is moving in this direction. Not sure why companies always evolve this way. Boeing is another prime example. Apple has maintained its focus on the customer and thrived, bucking the trend, which seems like it would be motivation for others to stay focused on the customer. Especially given when Apple hired the Pepsi guy to run things in the bean counter way, the company nearly died.

Re: My Stripe Tax Story

#48

I also had issues with stripe's automatic tax. We use stripe's subscriptions with free trials but don't collect credit card details up front, preferring to make sign up simple and low friction. Automatic tax is charged at 0.5% of each transaction, and apparently a trial ending is considered a transaction even if the user has no payment method, so we were hit with automatic tax fees for every trial end even if we rece…

Could you email me at edwin@stripe.com and we can dig a bit more into this?

Re: My Stripe Tax Story

#49

My dad owns a successful chain of bicycle stores in Texas. He’s been in business for almost 51 years and he’s one of the largest bike dealers by volume in the country. He has nearly a hundred employees and a bookkeeper. Despite having a proverbial dozen balls in the air at any time and despite having people on the payroll to do bookkeeping, he sits down at his computer every night at home, logs into the ERP system, a…

> if you let this kind of fuck-up go undetected for over three months, you have to at least assume some of the blame and acknowledge that you probably could have caught it if you scrutinized transactions.

I work in eCommerce and occasionally there will be something like a script or config gets messed up and an issue with billing will happen. And being the "expert" I'm usually the one called to fix it.

I wish I could count the number of tense discussions I have had that are along the lines of:

  Them: We haven't been charging tax in Canada for three months because the config was wrong. Fix it!
  Me: (some more polite variant of) So just to confirm, this has been wrong in your ERP... hundreds of thousands of CAD of uncollected VAT... for 3 months and you're just now noticing?
It is, unfortunately, an extremely common discussion. That or some close variant of.

Re: My Stripe Tax Story

#50
post #3

(I work at Stripe.) This was a painful read. I'm sorry. We could have done a lot better. We're working on remediations now, and we're sending another, corrected email tonight with the updated CSV file of failed invoices as of March 1st.

I respect Stripe for responding in some way. When I had an issue with Square they just terminated my account and left me stranded, rather than fix their product.
Post reply on HN