Expensify vs Concur: what SAP Concur vs Expensify pricing actually meters

Look again at the two Control rows. Annual charges $18 for every member inside the size you committed to, regardless of activity. Pay-per-use charges $36, but only for members who were active that month. So the annual price is half the pay-per-use price, and the annual headcount is your whole committed size while the pay-per-use headcount is only the people who did something.

Write that out. Annual costs 18 times N, where N is your committed size. Pay-per-use costs 36 times A, where A is your active members. Annual is cheaper only when 18N is less than 36A, which is the same as saying A is more than half of N.

The Expensify Card discount does not move that line. It halves both sides, taking annual from $18 to $9 and pay-per-use from $36 to $18, so the break-even stays at 50 percent activity. That is a useful thing to know, because it means you can decide the card question and the commitment question independently instead of treating them as one bundle.

The commitment also only moves one way. You can increase your subscription size at any time, but you cannot reduce it until the term ends, and Expensify offers an auto-increase setting that raises the size for you when your member count passes it. If you turn that on and then have a hiring quarter followed by a quiet one, you are carrying the peak until renewal.

The interesting row is the third one. In the wide and quiet company, the plan with no commitment and the higher sticker price is the cheaper plan, by about a thousand dollars a month. That happens because a per-member meter charges you for organizational structure while a per-activity meter charges you for work, and a company with a lot of members who rarely expense is paying for structure.

It also explains why the Concur comparison is so hard to make cleanly. If the licensing advisories are right that Concur meters transactions, then the wide and quiet company is exactly the shape Concur prices well and Expensify prices badly, and the narrow and busy company is the reverse. Ask any vendor for the meter before you ask for the number. The number without the unit is not information. We run the same exercise across six vendors on expense report software.

Here is the thing worth saying plainly, including against our own interest: if your complaint about Concur is that it is expensive and slow to configure, switching to Expensify solves that. If your complaint is that you found out about a charge three weeks late, switching does not solve it, because both products are built around the same cycle. Something is bought. Eventually somebody files it, or a card feed imports it overnight. Then it queues for approval. Then it closes at month end.

That cycle is correct for accounting and useless for control. Nobody has ever prevented an overspend by reading a well-formatted report about it in the second week of the following month. The duplicate SaaS subscription that two teams both bought, the vendor that quietly moved from annual to monthly billing at a higher rate, the contractor invoice that arrived twice: those are all visible on the day they hit, and invisible until close.

That is the gap Spendnotify sits in. It watches the same card and account feeds your expense system already reads, applies budget thresholds you set, and messages a human the same day a threshold breaks. It does not replace Expensify or Concur, it does not want your expense reports, and it does not care which of these two you picked. Run the simulator above against your own numbers and see which charges from last quarter would have paged someone. If the answer is none, you do not need us, and we would rather you knew that now.