Hey everyone! 👋 I've been playing with Stripe's new Expense feature for the last couple of weeks, integrating it with a small project's workflow. On paper, it looks like a dream—consolidating payments, receipts, and reporting right inside a platform many of us already use.
But is it ready to compete with dedicated tools like Ramp or Brex? Here's my quick take:
**The Good:**
* The setup is, unsurprisingly, super smooth if you're already in the Stripe ecosystem. Issuing virtual cards for subscriptions is a breeze.
* The automatic receipt matching via email parsing works pretty well for common vendors.
* The reconciliation view is clean, and seeing everything next to revenue data is powerful for a holistic view.
**The Hurdles I'm Seeing:**
* The accounting sync feels a bit limited compared to specialists. It supports QuickBooks Online and NetSuite, but the depth of mapping and customizability seems v1.0.
* Approval workflows are functional but pretty basic right now—lacking the multi-tier or conditional logic I've set up elsewhere.
* International expense handling (multi-currency, VAT) doesn't feel as robust as some other players.
So, my big question for the community: **Are any of you using it as your primary expense tool yet, especially for a growing team?** I'm curious about:
* Real-world sync reliability with your GL (any weird lag or mismatches?).
* How you're handling more complex approval chains.
* Whether you've managed to build any clever automations around it using Stripe's own no-code tools or webhooks.
I'm excited by the potential of having everything in one dashboard, but I'm wondering if it's a "set it and forget it" solution yet, or more of a promising beta for the very lean.
You've nailed the main trade-off. The integration view with revenue data is Stripe's unique advantage, but they're giving up a lot of feature depth for it.
> The accounting sync feels a bit limited
This was my exact impression. In our testing, the mapping for non-standard general ledger accounts was too rigid. It works if your chart of accounts aligns perfectly with their defaults, but any complexity breaks it. The specialist platforms have spent years building those flexible mapping engines.
For a company already deep in Stripe payments, it can make sense as a unified system of record. But if your primary need is sophisticated expense control, the dedicated tools are still ahead.
Your bill is too high.
Spot on about the GL mapping rigidity. I hit that wall trying to categorize some niche SaaS tools. The workaround was to create catch-all accounts in our books first, but that defeats the purpose of clean automation.
It's that classic "platform feature" vs "dedicated tool" gap. They've built the 80% solution for Stripe-native shops. For anyone with complex departmental budgets or advanced approval chains, you'll feel the missing 20% immediately.
Might be enough for a startup running lean, but I wouldn't migrate an existing Ramp setup over yet.
Automate the boring stuff.