The expense report is a strange little ritual. A person flies across a country to win a contract, then returns home to spend Friday afternoon explaining a sandwich. Mesh Payments has built its case around ending that ritual. Its software links cards, bookings, receipts, approval rules and accounting records, then tries to infer the story of a transaction before an employee is asked to type it. For global finance teams with several entities and a mixed pile of cards and travel agencies, that is a real proposition. For a five-person shop that only needs a debit card and a receipt inbox, it may be a rather elaborate sandwich solution.
Who should put Mesh on the shortlist?
Start with the finance team that can draw its current expense process as a plate of spaghetti. Mesh is most persuasive when a company has employees in several countries, more than one legal entity, multiple currencies, an ERP that must remain clean, and travel bookings arriving through different channels. Controllers, travel managers and budget owners get the control surface. Employees get physical or virtual cards, mobile receipt capture and, increasingly, the option to do the awkward bits through Slack or WhatsApp.
Mesh is less obviously suited to a very small business with simple domestic spending. There is a free Pro tier for up to three users, but the product’s distinctive value appears when workflows become complicated. Premium is listed at $13 per user per month; Enterprise is quoted. Cashback requires at least $50,000 in monthly eligible spend. The arithmetic should include implementation time, card coverage in your countries and the cost of keeping a second travel or accounting tool.
From cardless cards to context
Mesh began in 2018 with a corporate-payments thesis and founders who knew the pipes. Zehavi had worked at PayPal and Payoneer; in one interview he cheerfully described himself as a “payment plumber.” The early product centered on virtual cards for individual vendors and subscriptions. A card could carry its own limit and merchant lock, which moved policy closer to the moment money left the building.
Remote work widened the brief. Spending escaped headquarters, SaaS multiplied, and the monthly close became a scavenger hunt conducted over email. Mesh added physical cards, reimbursements, accounts payable, ERP links and travel. In 2022, the company raised a $60 million Series C, taking total disclosed funding to $123 million. At the time it reported more than 1,000 customers and nearly $1 billion in annualized payment volume.
The new trick: assemble the whole trip
The 2026 Orchestration Layer is the clearest expression of where Mesh is going. It is designed to see bookings from tools such as Navan, Spotnana, CTM Lightning and Altour Connect; transactions across Visa, Mastercard, American Express, stablecoin rails and Mesh cards; plus clues in calendars, email, itineraries, HR records and prior spending. The aim is to turn scattered events into one auditable object.
Consider a client dinner. The calendar names the prospect, Uber supplies the ride, a card supplies the restaurant charge and policy defines the limit. Mesh says its layer can match those pieces, apply the policy, code the project and handle reconciliation. A more tangled trip might combine a TMC-booked flight on a corporate Visa with a hotel booked directly on a personal card. Mesh’s pitch is that the context survives those boundaries.
“The visibility is probably my favorite part, as someone who is in charge of cash and cash forecasting.”Sean Doheny, Treasury Director, in a Mesh customer story
Cards with guardrails
Physical and virtual cards can carry budgets, merchant rules and approval logic. Subscription cards can be dedicated to a vendor.
Receipts meet context
Receipt processing, automatic coding and matching reduce the little omissions that turn close into detective work.
Booking without one gate
The orchestration approach connects preferred booking tools and direct channels instead of demanding a single walled garden.
Accounting stays in the loop
ERP and HRIS connections carry transactions, people, entities and policies into the systems finance already operates.
Mia moves into the group chat
Mia, Mesh’s expense assistant, has no separate app to download. It lives in Slack and WhatsApp. Send a receipt and it can draft an out-of-pocket expense, read merchant, date, amount and currency, suggest a category and memo, then ask for missing information. Employees can check a card balance, request a new card, find missing receipts or ask where a trip request is stuck. Approvers can review pending expenses, card requests and trips in chat.
That placement is smart. Expense software fails when the tiny action required now becomes a Friday pile. A receipt sent from the restaurant is easier than a receipt remembered after four flights. Mia also respects the user’s existing Mesh permissions and does not reveal a full card number in chat. The risk is familiar: automatic coding must be checked, particularly when tax, client billing or unusual merchants are involved.
The ratings tell two stories
Business-software reviewers broadly like the platform. At the time of research, G2 showed 4.6 out of 5 from 1,066 reviews; Capterra showed 4.8 from 19. Reviewers praised coding, visibility, controls and faster close. A 2025 Capterra reviewer also found specific transactions hard to search and the response slow. That is exactly the sort of operational friction worth testing with your own data volume.
The employee-facing mobile picture is harsher. Apple’s listing showed 3.7 from 23 ratings, including praise for real-time visibility alongside complaints about slow loading and reliability. Google Play showed 1.9 from 32 reviews and 10,000-plus downloads; recent criticism mentioned biometric setup, horizontal scrolling and slowness. Small samples can swing, and app reviews may lag product changes. Still, a travel-and-expense system lives or dies in the taxi, hotel lobby and airport queue. Buyers should treat mobile testing as procurement, not polish.
What to test before signing
- Run one real trip from request to booking, card swipe, receipt, approval and ERP reconciliation.
- Verify card issuance, currencies, reimbursements and regulated partners for every country you operate in.
- Import enough transactions to judge search speed, coding accuracy and exception handling under realistic volume.
- Give the Android and iOS apps to ordinary travelers, including someone who ignores training documents on principle.
- Map which integrations are native, which need configuration, and who owns failures between Mesh, your TMC and your ERP.
| Plan | Public price | Likely fit | Question to ask |
|---|---|---|---|
| Pro | No cost for up to 3 users | Very small evaluation or simple team | Which modules and card services are included in our region? |
| Premium | $13 per user / month | Growing finance operation | How are inactive, approver and employee seats counted? |
| Enterprise | Custom | Multi-entity global company | What is the implementation scope, support model and SLA? |
Competitively, Mesh sits in a busy neighborhood with Ramp, Brex, Navan, Airbase, Rho, PayEm, Expensify and SAP Concur. Its most interesting distinction is the refusal to pretend every company will consolidate onto one card and one booking path. The Orchestration Layer instead promises to interpret activity across a mixed estate. That should appeal to global businesses whose regions have already made local choices. A company ready to standardize everything may prefer a vendor whose strongest argument is consolidation.
And now the finance data talks back
Mesh’s newest technical move is an MCP server that lets assistants including Claude, ChatGPT and Gemini query live company spend. A finance manager can ask for unreconciled transactions over $500, compare quarterly SaaS spending or find cards idle for 60 days. Existing Mesh roles still govern what each person can see. The first release is focused on querying and analysis; Mesh says actions such as submitting expenses and routing approvals are planned rather than currently available.
This is a sensible use of conversational software because the source data is structured and permissioned. It also deserves the same care as any finance interface: validate totals, retain traceability and keep approval authority explicit. A fluent answer can save ten minutes of filters. It should not get ten minutes of unearned trust.
The verdict
Mesh is worth a close look for finance teams managing global complexity, especially those unwilling or unable to force every employee onto one travel and payment stack. The product’s direction is coherent: understand the transaction early, gather context automatically and let humans handle exceptions. The controls, integrations and chat-based workflows answer genuine annoyances rather than decorating a card with AI.
The caveat sits in your pocket. Mobile reliability and search performance are ordinary details with extraordinary power to spoil adoption. Test them with skeptical employees, real receipts and ugly itineraries. If Mesh can survive that week, its promise becomes compelling: fewer Friday confessions about sandwiches, and a finance team that already knows the story.