Most spend card programs on the market were designed for corporate expense management: control spending limits, capture receipts, reduce reimbursement requests. These are useful features for a corporate finance team. For a nonprofit managing multiple restricted grants, they solve only a fraction of the actual problem.
The nonprofit spend card problem is not primarily about expense controls. It is about fund integrity: making sure every dollar spent is charged to the right grant, documented to meet the standard that grant requires, and reconcilable to the grant budget without a manual reconciliation sprint at month-end. Evaluating a spend card program without asking whether it addresses fund integrity is evaluating the wrong thing.
Question one: can each card carry a specific grant designation?
This is the foundational question. A card that is designated for a single grant (or a specific program within an organization) means that every transaction on that card is, by design, charged to that grant. The bookkeeper reconciling the bank feed does not have to make a coding decision. The transaction is already associated with the correct fund.
Most corporate spend card programs allow you to assign cost centers or departments to cards. That is not the same as grant coding. A department tag tells you which team's budget was charged. A grant code tells you which restricted award the expense was allocated to, which matters for reporting to the federal agency or foundation that issued the award.
When evaluating any card program, ask specifically: can I issue a card tied to a named grant, with that grant's restrictions visible in the card configuration? If the answer is that you can assign categories or cost centers but not specific fund codes, you are looking at a corporate tool that you would have to adapt, rather than a purpose-built solution.
Question two: can you set allowable expense categories per card?
Restricted grants have allowability rules. A federal workforce development grant may prohibit purchases of food, entertainment, or certain categories of equipment. A foundation grant for after-school programming may restrict spending to direct service costs and prohibit administrative overhead charges.
A spend card program that lets you configure allowable merchant category codes (MCCs) per card means those restrictions are enforced at the point of purchase, not caught retroactively at reconciliation. The card declines or flags transactions in prohibited categories before the charge posts.
This matters for two reasons. First, it prevents violations from occurring in the first place. Second, it provides documentation that your organization had a control in place, which is relevant if a questioned cost comes up during audit. The fact that you had a card-level restriction demonstrates a functioning internal control environment, even if a violation somehow slipped through.
Not all programs support MCC-level restrictions. Some support merchant category groups (travel, dining, retail) but not the specific four-digit MCCs that map to real spending patterns. Get specific about the granularity before committing to a platform.
Question three: what does the transaction export look like?
You will need to get transaction data from the card platform into your accounting system, whether that is QuickBooks, Xero, or something else. The question is not whether export exists but whether the export format preserves the grant coding information in a form your accounting system can use.
Some card platforms export in a generic CSV that requires manual column mapping every time. Others have native integrations with QuickBooks or Xero that push transactions directly into the right accounts and classes. The difference in staff time over a year is significant.
Also ask about the export format for audit purposes. When a federal program officer or auditor requests documentation for a subset of transactions, you need to be able to produce a clean, grant-specific transaction report that shows the amount, date, merchant, business purpose, and grant designation for each line item. If the platform's export requires manual filtering and reformatting every time you need an audit-ready report, that is a real ongoing cost.
Question four: who controls the card policy, and how quickly can it be changed?
Grant requirements change. A grant amendment may add a new allowable category or remove one. A program officer may request that spending on a certain line item stop while they review a budget modification. You need to be able to update card policies quickly, without a support ticket to the card vendor and a 48-hour turnaround.
This is a practical operational question that often gets overlooked in product evaluations. Ask to see the card management interface and specifically test: how many clicks does it take to update the spending limit on a specific card? Can the finance director do it directly, or does it require a platform administrator? Can you turn off a specific merchant category on a specific card without affecting other cards?
The answer to these questions tells you something important about whether the platform was designed for organizations that need to manage card policies in response to real grant requirements, or whether it was designed for a corporate environment where card policies rarely change mid-cycle.
Question five: what is the actual all-in cost?
Corporate spend card programs often advertise free or low monthly fees, because their revenue model depends on interchange income from the transactions you process. This works at corporate scale. For a nonprofit processing $15,000 to $50,000 per month across five to ten grant cards, interchange income may not be the primary revenue source for the vendor, and the platform economics may look different.
Ask for a clear breakdown: is there a per-card fee? A transaction fee? A monthly platform fee? A fee for integrations or export formats? What happens to fees if you add more cards or grants mid-year? Is there a contract term, and what are the exit terms?
Compare the all-in cost against the staff time cost of your current workflow. A platform that costs $150 per month but eliminates four hours of monthly reconciliation work is cost-effective for most nonprofit finance teams. A platform that costs $800 per month and requires similar manual work is not.
One thing spend cards alone cannot solve
Spend cards control what happens at the point of purchase. They do not cover payroll allocations, vendor invoices paid by check or ACH, or grants that fund equipment purchased through a separate procurement process. A complete grant compliance approach includes card-level controls as one layer, alongside time tracking for salary allocations, purchase order controls for large acquisitions, and regular budget-versus-actual review processes.
We are not suggesting that cards solve all grant management problems. We are saying they solve a specific and significant part of it: the category of expenses made by cardholders in real time, which is also the category most prone to mischarges because the point of purchase is the farthest moment from the accounting system.
A spend card program purpose-built for nonprofits addresses the fund coding problem where it starts, at the card swipe, rather than expecting the accounting system to sort it out afterward. That distinction should be the starting point for any evaluation.