Per diem virtual cards for business travel, a daily limit, not a stack of receipts.

Read summarized version with:

ChatGPT Claude Grok Perplexity Gemini

A Virtual Card Maker per diem card is a wallet-funded virtual Visa card set to a daily spend cap, not one lump amount for the whole trip. You pick a daily number, often using the federal GSA (General Services Administration) per diem schedule as a starting reference for the destination city. Where the card platform supports an automatic recurring reset, that amount becomes available again each day of the trip, whether or not the employee spent all of it the day before. A charge that would push the day's total over the cap is typically declined the moment it happens, not caught weeks later in an expense report. One exception: hotel and rental-car holds can authorize for an estimated amount before the final charge settles. Where the card platform supports it, you can also lock the card to hotel, restaurant, and transportation categories, and block things like cash advances. Label the card with the employee's name and the trip dates. Reconciliation then becomes reading the daily settled totals from a dashboard, not matching paper receipts against a spreadsheet after the trip is over.

If you run travel or operations for a company that sends people on the road, the expense report is usually the part everyone hates. The employee front-loads a card or their own money, keeps receipts in a bag, and files a report a week later. You approve it after the fact, once the money is already spent. A per diem card flips that order. The limit is set before the trip starts. The control happens at the moment of the swipe, not after the statement lands. For the broader setup around business travel cards, see our guide on setting up business travel cards without expense reports. This article stays focused on the per diem mechanic: how the daily amount is decided, and how the cap behaves day to day.

How a per diem virtual card works

You issue one virtual Visa card per traveling employee, funded from your company wallet. Instead of one number for the whole trip, you set a daily spend cap and an active window matching the trip's dates. The employee gets the card details, usually added to a phone wallet. They use it for hotel, meals, and local transportation while traveling. Once the cap is set, each charge checks against the day's remaining amount at the moment it is run.

That is the core loop: one card, one traveler, one daily number, set for as many days as the trip runs. The cap sits on the card itself, so you are not relying on the employee to track their own spend in their head. Where your card platform supports an automatic recurring reset, it handles that daily tracking for you. Otherwise, you will need to refresh the cap yourself at the start of each day.

Daily-reset cap vs one lump sum for the trip

A per diem card is not just a card with a limit. The difference is how that limit behaves over the trip. That's what trips people up the first time they set one up.

There are two ways to structure the cap. The first is a lump sum for the whole trip. You load the card with one total budget, say $720 for a four-day trip at $180 a day. The employee can then spend that $720 however they want across the trip. Nothing stops them from spending $500 of it on day one and running short by day three. The second is a daily-reset cap. Where the card platform supports it, the card's spend limit renews on a recurring interval, such as once every 24 hours, instead of staying fixed for the whole trip. Each calendar day, the available amount returns to the same number you set, no matter what was spent the day before. On a card configured this way, a $180 daily cap means the employee can spend up to $180 today. Tomorrow, the card allows up to $180 again, independent of today's total. Confirm with your card platform that automatic renewal is actually available before you rely on it for a live trip.

The mechanical difference matters because it changes what "over budget" looks like. On a lump-sum card, overspending shows up as the employee running out of money before the trip ends. That's awkward to fix mid-trip. On a daily-reset card, overspending shows up as a single declined charge on the day it happens. That's easier to catch, explain, and, if needed, override.

One setting is worth checking before the trip starts. Does unused amount from a light day carry into the next day, or does it reset to zero? Card platforms handle this differently, so confirm which behavior you want, and confirm the card is actually set that way. Assuming the wrong rollover rule is a common reason a card declines a charge it shouldn't.

How much per diem to set, using GSA rates as a reference

Picking a daily number out of thin air is the fastest way to either underfund a trip or overpay for one. A useful benchmark is the federal government's own per diem schedule, published by the U.S. General Services Administration (GSA) for federal employee travel. Zil Money is not affiliated with or endorsed by GSA; its rates are cited here for reference only. GSA sets a standard rate for most of the country, and higher, city-specific rates for places where hotels and meals cost more. For fiscal year 2026, the standard rate runs around $178 a day total, split roughly into $110 for lodging and $68 for meals and incidentals. High-cost cities run well above that. New York City's published rate can run well over $300 a day, and above $400 a day in peak months. San Francisco has run up to about $364 a day in the FY2026 schedule. These are ballpark figures to show the spread between a standard-cost city and a high-cost one. Pull the exact number for any destination from GSA's own per diem lookup tool for your travel dates. GSA republishes rates each October, so check the current schedule rather than relying on a number from a prior year.

None of this is something Zil Money checks or enforces for you. GSA publishes these numbers for federal employee travel, and they are a useful starting point for what a day of lodging and meals actually costs in a given city. Pull the reference number for your traveler's destination from the federal GSA per diem schedule. Then decide your own cap: match it, run below it, or pad it for your own company policy. The card itself has no idea what GSA publishes. It only enforces whatever amount you type in when you set the cap. This article is not tax advice: amounts set above the federal per diem rate may still need documentation to satisfy IRS accountable-plan rules, so check with your tax advisor before relying on a per diem card alone for recordkeeping.

Setting the trip window and locks per employee

Once you have a daily number, set the card's active window to match the trip: departure day through return day. That way, no charge can land before the employee leaves or after they are back. Label the card clearly. Employee name plus destination and dates works well, so a charge on a statement is easy to trace to one traveler and one trip, without opening the app to check.

Where the card platform supports it, add a category or merchant lock as a second layer behind the daily cap. Restrict the card to hotel, restaurant, and transportation categories, and block cash advances so the per diem cannot be pulled out as cash at an ATM. Treat this as a strong secondary control, not a guarantee. Category and merchant coding depends on data the vendor's payment processor passes through the network, and that data is not always complete or correctly labeled.

A worked example: a four-day trip on a per diem card

Here is a per diem trip walked end to end. Priya Chandran, a travel coordinator, is sending Marcus Webb, a field consultant, to Denver for a four-day site visit, August 3 through 6. Denver's published GSA per diem rate runs higher than the standard rate. But Priya's company policy caps travel spend at $180 a day regardless of destination. So she sets the card to that policy number, not to GSA's higher reference for Denver.

Issue your first per diem card →

Building a per diem program that scales

A single trip is easy to manage by hand. A travel program with dozens of trips a month is not. That is where standardizing the daily numbers pays off. Set a small number of per diem tiers: standard-cost, high-cost, and maybe a conference or trade-show tier. Map each tier to a reference range pulled from the GSA schedule. Coordinators then pick a tier by destination instead of deciding a fresh number for every trip. That keeps the program consistent without turning every booking into a policy debate.

Run it inside the same wallet that already funds your other virtual card programs. That way, travel doesn't turn into its own separate system with a separate login and a separate reconciliation process. One wallet, one login, and the daily totals are already there when you go looking for them.

Mistakes to avoid

People also ask