What Is a Business Expense Card? How It Works and Who Needs One

Read summarized version with:

ChatGPT Claude Grok Perplexity Gemini

A business expense card is a payment card your company loads with its own funds and assigns to a specific employee or project. You set a dollar cap, restrict which merchant categories are accepted (where supported), and define a time window. When the employee swipes, the payment network checks those rules in real time and either approves or declines, before the merchant ever processes the charge. No credit line. No personal guarantee. No waiting for a statement to discover a problem.

What a business expense card actually is

System one: the shared company card. One card number, multiple employees, zero visibility into who spent what until the monthly statement arrives. You see a $340 charge at a hardware store and a $55 restaurant charge on the same account and have no idea which employee made which purchase. Your accountant flags the restaurant charge six weeks later. By then, the receipt is gone and the deduction is disallowed.

System two: expense reports and reimbursement. Employees pay out of pocket and submit receipts. You review, approve, and cut a check. This sounds orderly until you discover that half your team stops submitting reports after a while, that receipts disappear, and that the employee has been floating company expenses on their personal card for three weeks while waiting for reimbursement. The suspension of the employee deduction for unreimbursed business expenses under IRC Section 67 (initially enacted under the Tax Cuts and Jobs Act of 2017 and potentially extended by subsequent legislation; confirm current IRS guidance for your tax year) makes this problem worse for workers who were previously able to write off out-of-pocket costs.

A business expense card fixes the underlying structure: one card per person, controls set in advance, rather than adding another spreadsheet on top of a broken process. The policy stops living in spreadsheets and starts living in the card itself. Instead of reviewing spending after it happens, you define the spending policy before the card is ever used. The dollar cap, the category restrictions, the time window: all of these travel with the card number itself. The payment network enforces them automatically at the moment of every swipe.

Mechanically, here is what happens the moment your employee attempts a purchase:

This architecture, where controls are enforced at the network level rather than reviewed at the accounting level, is what separates an expense card from every post-purchase tool that came before it.

How expense cards differ from corporate credit cards

Both are Visa or Mastercard products accepted everywhere. The difference is structural, and it matters enormously for small businesses. This table shows which tool fits which situation. For a deeper look at the full range of virtual expense card options, see the hub guide.

The critical distinction for most small businesses: a corporate credit card extends a credit line. Your business qualifies based on credit history, and in most cases you sign a personal guarantee, meaning your personal credit and assets are on the line if the business cannot pay the bill. Most small businesses under two years old or without established business credit cannot qualify at all.

A wallet-funded expense card works the other way. You deposit money into a company wallet. The card draws from that wallet. If the wallet is empty, the card declines. There is no credit line to extend, no credit check to pass, and no debt to accumulate. In most cases, the card draws only from funds in the wallet, though offline transactions and certain pre-authorization patterns (common at fuel stations and hotels) may allow a charge to settle against an insufficient balance. Confirm how your provider handles these scenarios before relying on this as a hard guarantee.

Why businesses issue expense cards per person

One shared card for a whole team is the most common setup small businesses start with. It is also the most consistently harmful one. Here is why one card per person is not a premium feature but the minimum requirement for any defensible expense policy.

Visibility: When multiple employees use the same card number, there is no way to know who made which purchase at the transaction level. You see a charge. You do not see a name. Reconstruction requires comparing receipts that may not exist.

Individual limits: A shared card has one aggregate limit shared across everyone who holds it. You cannot set a $300 monthly limit for one employee and a $900 limit for another. Every person on the team has access to the full balance.

IRS substantiation: IRS Publication 463 requires that business expense reimbursements be substantiated by records showing the amount, date, place, and business purpose of each expense. A transaction on a shared card number cannot be attributed to a specific employee without additional documentation. Under an accountable plan, that attribution is required for the reimbursement to be excludable from employee income.

Audit trail: If an employee misuses a shared card, you cannot prove which employee made the charge without extensive investigation. If the same employee had their own card, the record is automatic.

The practical result of per-person issuance is that the card enforces the budget without a manager in the loop. The receipt is captured at the moment of the transaction. The record is complete by default.

The five controls that make an expense card useful

An expense card without controls is just a debit card with an extra step. The controls are the product. Build your expense policy around the spending cap first, since it is the only control that is always deterministic. Everything else is a secondary filter.

Here is what each control does and what you need to know about how reliably each one enforces your policy.

1. Per-card spending cap (deterministic)

The spending cap is the only control that is fully deterministic. When the card reaches its cap, it declines every subsequent charge regardless of merchant, category, or time. This control does not depend on how a merchant has categorized themselves. It depends only on the transaction amount relative to the balance. Set a $500 monthly cap on a maintenance card and that card cannot spend $501 in standard online transactions. Note that offline POS transactions, tip adjustments posted after authorization, and pre-authorization holds (common at fuel stations and hotels) can in some cases result in a posted amount that differs from the authorized amount. Confirm how your provider handles these edge cases.

2. Merchant category lock (where supported)

Every merchant has a Merchant Category Code (MCC) assigned by Visa. Issuers can instruct the payment network to decline transactions where the merchant's MCC does not match an approved list. If you lock a card to hardware stores (MCC 5251) and fuel (MCC 5541), an attempt at a restaurant (MCC 5812) will decline at the terminal where MCC-based controls are supported. Note that merchant categorization is not always precise. Some merchants operate across multiple categories or are miscoded at setup. Treat category locks as a strong probabilistic filter, not a deterministic guarantee, and confirm how your provider handles edge cases.

3. Merchant-level lock (where supported)

Some platforms allow you to lock a card to a single approved merchant or a list of approved merchants. This is more precise than category-level locking because it targets the specific vendor rather than the category. Where supported by your provider and the payment network, a merchant-locked card can only process charges from that named merchant.

4. Time window control (where supported)

Time controls restrict when the card can be used. A card set to business hours only cannot process charges at 11 PM on a Saturday. A card set to a specific project window expires automatically when that window closes. Time controls are useful for project cards, contractor cards, and any situation where spending should be bounded by a calendar constraint. Where supported by your provider, these controls travel with the card at the network level.

5. Location restriction (where supported)

Some providers support geographic restrictions that flag or block charges originating outside a defined area. This control is the most variable in implementation across providers. Confirm the technical specifics with your provider before relying on location controls as a primary enforcement mechanism.

How Virtual Card Maker issues expense cards

Virtual Card Maker, powered by Zil Money, lets you issue virtual Visa expense cards from a company wallet without calling a bank or filling out a credit application. The process does not require a credit check or a personal guarantee.

Here is how the issuance process works:

1. Fund your company wallet. Transfer funds to your Virtual Card Maker wallet balance. This is the pool from which all card balances draw. No credit line is extended at any point.
2. Create cards individually or in bulk. You can issue a single card through the dashboard or upload an Excel spreadsheet to issue cards for an entire team at once. An API option is also available for businesses that manage card issuance programmatically.
3. Assign each card to one employee. The card is linked to a named employee. This creates the per-person record required for IRS substantiation under an accountable plan.
4. Set spend controls for each card. Configure the dollar cap, and set category, time, or location locks where supported by your setup. The spending cap is always deterministic. All other controls operate where supported.
5. The card is emailed to the recipient. The employee receives their virtual Visa card by email and can add it to their phone wallet for tap-to-pay or use the card number directly online.
6. Receipts are captured at the point of use. Employees attach a photo of the receipt to each transaction through the platform. The record is created when the charge happens, not reconstructed afterward.
7. Cancel from the dashboard anytime. Canceling a card stops future charges immediately. Pending charges that were authorized before cancellation may still settle. No physical card to collect.

Because all cards are virtual, there is no plastic to mail out, no card to collect when an employee leaves, and no waiting period for a physical card to arrive. The card is created in your dashboard and delivered by email.

Who should use expense cards (and who should not)

Expense cards are the right tool for a specific set of situations. Understanding both sides of that line prevents you from deploying them where they will not deliver value.

Not the right fit first

Businesses that want rewards on large spend volumes. Wallet-funded expense cards do not carry rewards programs the way corporate credit cards do. If your primary goal is earning points or cash back on a large, controlled spend volume and you have a trusted setup already, a business credit card may serve that goal better.

Situations where the employee genuinely needs a credit float. If your business model requires employees to commit expenses before you have loaded the wallet, a wallet-funded card will not solve that timing problem. The card only spends what is in the wallet. If the wallet balance is zero, the card declines.

Good fits

Field crews with fixed project budgets. A landscaping company with a 12-person crew, a construction firm with multiple job sites, a property management company with maintenance technicians: any business where employees buy materials in the field against a defined project budget is a natural fit. The card's spending cap maps directly to the project budget. When the project budget is spent, the card declines. The manager does not need to track it.

Small businesses that cannot qualify for corporate credit. A business under two years old or without established business credit history typically cannot get a corporate credit card. A wallet-funded expense card requires no credit qualification because no credit is extended. The business qualifies by having money in the wallet.

Teams where shared cards created tracking problems. If your current situation involves a shared card with multiple users and you are regularly finding charges you cannot attribute, expense cards fix the underlying structure: one card per person, controls set in advance.

Project-based payments to contractors. A virtual card issued for a specific contractor engagement, locked to the project scope and set to expire at project close, gives you a clean record without opening a standing credit line to a third party.

Accounts payable with recurring vendor payments. For businesses that pay the same vendors on a predictable schedule, a dedicated card per vendor provides a clean audit trail and prevents any single vendor from having access to your broader payment account. See also: virtual cards for accounts payable.

Frequently Asked Questions