SF payroll firm Rippling has to delay payouts after Silicon Valley Bank collapse
sfgate.com
sfgate.com
https://mobile.twitter.com/GustoHQ/status/163424676119459433...
That would still be a disaster for me. But I guess that says more about me and my lack of financial stability, than it says about anyone else..
None of us should be. Not just to protect ourselves from weird situations from this.
Financial freedom is power in so many ways. (and peace of mind)
Ref: https://twitter.com/parkerconrad/status/1634315187837861889
Hi Rippling Customer,
Yesterday afternoon, Rippling learned that Silicon Valley Bank (SVB) had solvency challenges. We have been working with SVB to ensure timely payments to our customers’ employees. However, this morning we learned that the FDIC had stepped in and taken control of SVB.
We are reaching out to you because you have a payroll that has already been processed for 3/15/2023. Currently, these funds may be sitting with SVB. We are closely monitoring the FDIC takeover and what it means for this pay run. We ask that you please reach out to your bank and request that your bank return any ACH transactions debited from your account by Rippling into SVB under the premise that the transaction(s) are unauthorized, since the bank has ceased operations and is unable to honor the payments.
If the bank agrees to issue a return, you will then need to send a wire to Rippling for the full amount of the 3/15/2023 payroll run by Tuesday 3/14/2023 at 12 PM PST. This help center article has updated wire instructions. Your 3/15/2023 payroll will be marked as Non-sufficient Funds (NSF) on Rippling’s end, but as long as we have received the wire, Rippling will issue employee payments for 3/15/2023 via our new banking partner, JP Morgan Chase & Co.
If the bank does not agree to issue a return, we will follow up with additional instructions. If you have questions, please reach out to our support team.
Thanks, The Rippling Team
This seems a little ... odd. To be very clear, I'm not on the bank's side at all... but if the ACH is already debited, then your bank would absolutely be in the right to not return it as unauthorized, because the bank ceased operations _after_ the transaction.
Not a fun email to receive either way.
Just more that it's odd for Rippling to say that people should report the transaction as unauthorized, because on a strict technical timeline, it wasn't, until the bank was closed, so if it had already debited someone's account before then...
(seems like the flow of funds is customer bank -> SVB -> [maybe more] -> payroll payees)
Seems likely enough that those transfers will fail to clear in a couple days, not bad to get ahead of that if possible.
Hopefully banks will sympathize, but I don't know that you can say "the bank was forcibly closed the day after this ACH transaction, so it's unauthorized, because I intended to have those funds flow outbound later".
It would be unauthorized if the ACH debit was _initiated_ after the closure of the bank.
If Rippling can get their customers to somehow get that money out and wire it again, Rippling may not be on the hook for replacing the missing money.
Rippling should be working with FDIC to sort out these in-flight payments, not asking their customers this. When I reached their support team for what the additional instructions are, I couldn't get an answer. This situation sure doesn't look great.
If the money was sitting in an account at SVB, which it was, it’s at risk.
If I understand it correctly:
1. Businesses processing payroll through Rippling wired money to Rippling's account as SVB
2. Rippling would now normally use that money to pay the businesses employees.
3. Before that could happen, SVB went upside-down. Some of the money may be lost, the rest is frozen.
4. The businesses owe their employees their pay, but may not have enough money to simply pay for payroll a second time.
5. Rippling owes the money to the businesses (respectively, has an obligation towards the businesses to pay their payroll), but may not have the money to do so after some amount of funds just disappeared and another larger amount just got frozen for an unknown amount of time.
6. Employees of these businesses won't be receiving their pay on time, and may not be able to receive it at all if the money they're supposed to be paid with is gone and neither their employer nor Rippling can afford to cover the loss and goes bankrupt.
Edit: based on a tweet linked elsewhere in this thread, Rippling is putting up its own money to make sure payroll goes through, so it should indeed just be one business day of delay + possibly additional small delays because some companies didn't make the necessary adjustments to keep future payroll runs working.
Decent of Rippling to cover overdraft fees of those affected, at least.
"Hey, your paycheck won't be coming today and I need you drop what your doing and make an emergency change to our apis so that we can use JP Morgan Chase. We're going to have to skip all the usual test environments."
The delays in the article can just be the bank processing time post switch. Doesn't look like it provides the information to tell either way.
I would’ve been in tears if I was the dev but you have to pick yourself up and move on. If a single dev could’ve done this there’s a problem with the process and organization.
That's the kind of delay one expects from reading the headline and why it is clickbait. In actually the payouts are already on their way via JP Morgan Chase and will have arrived by Monday for everyone.
It's all circumstantial anyway. I don't think it's fair to call this a case of a "typical startup". Although it's definitely a stereotype of startups.
Especially +/- a whole week.
[0] https://www.thebalancemoney.com/paying-employees-in-a-year-w...
A non-clickbait would say what gp said.
The title is perhaps yes strictly speaking accurate, but it's still clickbait, it deliberately implies trouble pouring on an already flaming fire, when actually this sounds like an extremely minor symptom - some ash in the hair of the stoker.
All that said, Rippling is doing everything they reasonably can and I’m sure they’ll make their workers whole.
FedNow instant payments are supposed to go live this spring/summer. Feels like it should have been 10 years ago.
Though in searching for statistics, I found several payroll processing companies advertising that they would use the Faster Payments (instant) system. The business can keep the money for an additional couple of days, which is presumably an advantage if money is tight.
Oh? Okay, let's see, it starts with...
>SF payroll firm Rippling has to delay payouts...
And then you said...
>The only delay is because...
So, two sentences later you've confirmed the headline's accuracy yourself.
GP says that Rippling did not delay payouts. In fact, the payouts went out in time - they were delayed in transit, outside of Rippling's control, and Rippling immediately made another payout through a different bank.
The headline suggests that there were issues at Rippling, which meant that the payouts did not go out in time. That is a completely different scenario, so the headline would indeed be inaccurate.
Yes, the issue was caused by their bank and not Rippling themselves, but the purpose of the article is to highlight how a separate company is impacted by the SVB fallout. At the end of the day, it's still an issue Rippling has to deal with.
I mean, that's why the headline goes on to say, "after SVB collapse". It makes clear that Rippling is suffering because of SVB.
The new package, provided the driver doesn't eat it, will arrive delayed. But Amazon didn't delay it, nor do they "have to" delay sending packages.
"SF payroll firm Rippling finds some payouts delayed" would be accurate. "Has to delay" implies that they "had to" make a choice to delay payments, e.g. because they don't have the funds available.
Yes, it's a subtle change in wording, but it's a very different issue.
Yes, they did by their choice if provider. Services are end to end, you don’t get to pass off responsibility for things like that.
And neither did this bank have a history of breaking down.
If your car is on fire and then explodes, nobody would say "jen20 had to detonate their car", because it implies that you pushed a button to make it explode. "Well, they could have known that that brand of cars has a 1 in 1000000000 chance of blowing up, so they did it by choice of car" isn't something you'll hear.
Note I am NOT suggesting that every package must arrive on time, just that when they do not, it is Amazon who must perform the service recovery rather than a delivery company.
That is no different in this case.
Totally. But you wouldn't say that "Amazon chose to delay my package", you'd say "my package got delayed, UPS should really make sure not to use that package-eating driver or Amazon should stop using UPS".
"Amazon delayed my package" = "Amazon intentionally delayed my package so that it doesn't arrive on time". "My Amazon package got delayed" = "The package got delayed, but no intention is implied or expected". In both cases it's on Amazon to get you your package, but in one case Amazon is after you and is intentionally holding back packages instead of shipping them to you.
No, in if Amazon is standing in for Rippling here, you would say that Amazon normally ships with UPS but made a last-minute decision to switch carriers. This requires some last minute logistical adjustments resulting in your delayed package.
However, you are right from a customer's perspective. A third party cock-up is not an excuse - it may not be your fault, but it still is your problem.
The article makes it pretty clear that Rippling felt they "had to" switch banks upon SVB's failure Friday morning. Whether we agree on whether or not they truly had to doesn't change the fact that this was apparently a move they felt they needed to do immediately.
It's like everyone in this thread saying, "They didn't have to," was somehow magically privy to internal Rippling convos.
The headline is "Rippling has to delay payouts after..." though, which is completely different. They haven't delayed payouts. Some payouts are delayed, because they were in flight when the plane crashed. That's not "delaying payouts", that's "payouts are delayed". They'd would be "delaying payouts" if they said "we're only resuming payouts starting on Friday", but that's not what's happening.
It's like Amazon shipping a product. The product gets eaten by the courier. Amazon sends out a new product. Your shipment is delayed, but Amazon isn't delaying it. The eating delayed it, not Amazon.
Just because they "had to" do one thing doesn't mean a headline can claim they "had to" do other things. Like, a similar headline would be "Rippling had to defraud the government after...". Totally inaccurate, they didn't do that. It's not about the "had to", it's about the "did they actually delay payments", which is an active process and requires intent. They didn't, and that makes the headline inaccurate.
You mean like making the big decision to switch banks during a crisis like this knowing that payments would likely be delayed as a part of the process? Huh, would ya look at that.
If you're aware of the fallout that will occur when you make a decision, and you still make that decision, it's your fault. They knew what would, or could, happen and they said, "Do it".
If we really want to compare this to Amazon, the correct analogy would be, "This item ships to you every two weeks. It would normally arrive today, but Amazon chose to switch carriers at the last minute which requires package re-routing, so it will arrive in two days". There wouldn't have been a delay if Amazon (or Rippling) hadn't switched carriers (or banks).
> If you're aware of the fallout that will occur when you make a decision, and you still make that decision, it's your fault. They knew what would happen and they said, "Do it".
No, the delay is because of the failing of the bank they used. Certainly, if they had known that this bank would be taken over and not actually execute the orders and just cease to exist, and they still would have said "do it", then they'd be to blame. But they weren't aware that the bank would stop operating suddenly, just like everyone else (including the bank itself, apparently).
> There wouldn't have been a delay if Amazon (or Rippling) hadn't switched carriers (or banks).
Of course there would be. If they hadn't switched, the payments that were in flight when the bank shut down would still not be completed, and additional payments would also not go through until the situation at the bank is resolved in some way or another.
Like, if one plane crashes, and you want some cargo to arrive somewhere, of course you send a different plane, even though it can't arrive at the same time as the original plane. Not doing so would actually delay the whole thing, and that would've been a choice. But that's simply not what happened.
Accuracy alone is not an ironclad defense against clickbait.
It's CA Labor Code 210 if anyone is interested in looking it up.
so there are in fact delayed payouts.
> definitely still coming
aka delayed
or in summation
"payouts are delayed"
The point is that was not the best way to phrase it given the actual details of the situation and the surrounding context.
Technically correct is not always the best kind.
Even "SF payroll firm Rippling has to delay payouts by 1 day after Silicon Valley Bank collapse" is infinitely more clear and communicative.
This is literally clickbait. Y’all need to chill. It’s sensationalized and misleading relative to the severity of todays events.
The title is “technically correct” but it sensationalizes it for sure. Reading that title you expect Rippling to be going under or severely impacted. Which it sounds like so far they’re not (again relatively).
I'm also curious what about the headline sensationalizes the story. SVB caused a "ripple" in Rippling's operations, payments were delayed. Where's the sensation?
And is JP Morgan safe from having similar issues with SVB?
Eeeek! Talk about failing up!
https://techcrunch.com/2017/10/26/sec-fines-zenefits-nearly-...
I guess it depends on your bank whether this is readily visible, but if not, should be available through a simple phone call to a rep that’s allowed to see more than end-users are exposed to.
- Leviticus 19:13 - "You shall not leave [with you] the payment of a worker overnight until the morning..."
- Deuteronomy 24:15 - "On his day you should give his wages, the sun should not set on it, because he is a poor man and his life depends on it...”
And that's true whether you're a super-religious Chassid type or a super-socialist Workman's Circle Bundist type:
https://www.chabad.org/library/article_cdo/aid/1218800/jewis...
https://www.laborpress.org/workmen-s-circle-backs-fight-for-...
To the employee, the employer. To the employer, Rippling. It's wild that, as a payment processor, they didn't have redundant rails.
Two or more banks. Process through both on a regular basis. Switch if something goes wrong.
SV bank had the funds this morning and says the paychecks are going out, FDIC comes in at noon Rippling heard that checks haven't gone out in the afternoon, and now JPMorgan has the info and is overnight processing.
Not sure why everyone sticks to payroll on Fridays. It’s not the early/mid 1900s where you have to worry about workers going on payday benders.
Im not sure why anyone would want to report their employer for a minor delay when a bank is folding. Hopefully the DOL would ignore that.
It is basically the same as reporting your employer because for a late check because the mailman got shot on your doorstep.
I feel like it also does a disservice to people who have real late paycheck abuses.
And if this goes on for any length of time, you could sue your employer... but lack of payroll would only happen if the company no longer has any money - effectively making them bankrupt. Again you could name SVB in the lawsuit, or the FDIC... but good luck getting blood from the stone.
You could also sue the CEO directly. Failure to pay employee wages is one of the few things that can (somewhat) easily pierce the corporate veil.
Why are they using a regional bank to handle this?
Payroll being delayed a few days is indeed annoying, but it's not the end of the world.
I checked out their financial statements and they are pretty incredible.
They grew their HTM portfolio from ~10b to ~100b in two years. Then you had the Fed come out and say hey we are increasing rates and we aren't going to stop.
No one at these companies well like hey maybe this will become a problem and we should protect our cash.
Roku had 25% cash at this bank. Why?
I expect the email contains much more specific instructions and an actual process to follow. These things take time to write, even at SEV1 priority.
The CEO is biasing towards speed of notification, so they tweet some quick details out ASAP while the PR team gets moving.
That’s just my perspective tho. I am assuming many things