Expensify knows the merchant, the amount and the tag a cardholder chose. It doesn't know that the job behind the tag has $400 of its materials budget left, because that number lives in your project management or job-costing tool. A $900 charge goes through, gets coded correctly, reconciles cleanly, and blows the budget anyway. Someone finds out at month end.
The other blind spot is people leaving. If your HR system is one Expensify syncs with, check what removing a member actually does to their Card. If it isn't, nothing tells the card admin until someone remembers.
n-frames builds both checks. Each Card charge is compared with the remaining budget for its job or client as it posts, with an alert to the project owner before the number goes over. And a leaver marked in HR raises a task for the card admin that same day, listing that person's cards to freeze.