How Agencies Can Use Business Virtual Cards With a Per-Client Card Policy

The safest way to manage client-funded advertising, software, and supplier spend is to give each client a clearly defined card policy before issuing or assigning a card. Use one card or card profile per client where practical, document what the card may pay for, set spending and merchant controls, require approval for exceptions, and reconcile every transaction to the correct client account.

Business virtual cards can make this structure easier because they separate payment credentials from a team member’s personal card and create a cleaner boundary around client spending. The card itself is only part of the system, however. The policy must explain ownership, funding, permissions, recurring charges, evidence requirements, and what happens when a contract ends.

Build the policy around client ownership and accountability

A per-client card policy should answer one basic question: who is responsible for every transaction made with this card? The answer should be the agency or business that controls the account, not an employee, contractor, or media buyer acting informally on the client’s behalf.

Start by assigning each card a unique internal name. A practical format is client name, service line, market, and purpose, such as ACME-UK-Meta-Ads or Northstar-SaaS-Subscriptions. Avoid putting sensitive information in the card label, and do not use a generic name such as Main Marketing Card. Generic labels create confusion during reconciliation and increase the chance that a card is reused for the wrong client.

The policy should also identify the commercial relationship. Record the client account owner, the agency account owner, the approved budget period, the currencies involved, and whether the client has authorized the agency to fund spend directly or expects to reimburse it. If the agreement is silent, pause before issuing a card. A payment control cannot fix an unclear contract.

Define four roles in writing:

Card owner: the person accountable for the card profile and its business purpose.
Requester: the person who asks for a new card, limit increase, or merchant exception.
Approver: the person who confirms that the spend is within the client’s authorization.
Reconciler: the person who matches transactions with invoices, platform reports, and the client ledger.

One person may hold more than one role in a small business, but the policy should still name each responsibility. That makes handoffs possible when someone leaves or a client changes account managers.

Choose the right card structure for each client

Not every client needs the same payment arrangement. Compare the operational risk and billing pattern before choosing a card type.

Use a dedicated card for a single platform when the client has predictable spending on one advertising network or software provider. This is the cleanest setup for attribution and troubleshooting. If the platform rejects the card, the issue is usually isolated to one client and one merchant.

Use a broader client card when several approved vendors support one defined project and the business can reliably reconcile each transaction. This reduces administrative overhead but requires stricter merchant and category controls. It is not a good choice when many employees can add vendors without review.

Use a reloadable arrangement when funding needs to be replenished during a campaign or operating cycle. Review the details of a reloadable vcc before choosing this structure, including funding procedures, limits, supported merchants, expiry behavior, and any account-level controls. Reloadability is useful for controlled budgets, but it is not a substitute for approval.

Use a fixed-limit or single-use arrangement when the payment is one-off, the vendor is unfamiliar, or the exposure should end after one transaction. This can be safer for a test campaign, a contractor invoice, or a short supplier engagement.

The decision rule is straightforward: choose the narrowest card scope that still allows the client work to run smoothly. If a card can pay for everything, it is difficult to determine whether it was used correctly. If it can pay for only one approved purpose, investigation is faster when something goes wrong.

Set controls that match the actual client risk

A useful policy turns vague instructions into controls that someone can verify. Set controls at the card, account, and workflow levels rather than relying on a message in a team chat.

At minimum, define the following:

Purpose: the exact services or expenses the card may cover.
Limit: the maximum daily, weekly, monthly, or campaign amount.
Currency: the permitted billing currency and the process for foreign exchange costs.
Merchant scope: approved platforms, vendor categories, countries, or merchant identifiers.
Users: named employees or approved systems that may access the card details.
Evidence: the invoice, receipt, campaign report, or approval record required for every charge.
Review date: when the limit and purpose must be reassessed.

Do not set limits based only on the client’s total budget. A client may approve a large campaign budget while expecting the agency to release funds in stages. A better approach is to set an operating limit that covers the next approved period, then require a documented top-up or increase after performance and spend are reviewed.

Separate authorization from availability. A client may authorize up to a certain amount, but the card should not necessarily hold or expose that entire amount at once. This reduces the impact of a compromised credential, a platform billing error, or an accidental campaign setting.

Also specify what the card may not pay for. Typical exclusions include personal expenses, cash-like transactions, unapproved contractors, unrelated client work, gifts, political advertising unless expressly authorized, and any purchase that violates the platform’s terms or the agency’s contract.

Create an approval workflow before issuing the card

The policy should make approval fast enough to use and detailed enough to audit. A simple workflow is better than a complex process that staff bypass.

The account manager submits the client, purpose, platform, budget period, requested limit, and start date.
The finance or operations owner checks the contract, client authorization, and funding source.
The approver confirms the business purpose and any merchant or geographic restrictions.
The card administrator creates or assigns the card with the smallest practical limit.
The user confirms that the card works without storing it in an unauthorized password manager, spreadsheet, or chat.
The reconciler reviews the first transactions and confirms that receipts and platform records are being captured.

Require a second approval for exceptions such as a limit increase, a new merchant, a new country, a new advertising account, or a recurring charge. The exception record should state who approved it, what changed, the maximum amount, and when the exception expires.

For urgent campaign launches, allow an emergency path but make it temporary. For example, an operations lead may approve a short-duration limit increase if the request is recorded before the payment and reviewed by finance on the next business day. Emergency approval should not become the default route.

Manage recurring billing and reloads without losing control

Recurring charges are where many otherwise good card policies fail. A vendor may keep charging after a project ends, increase the amount, change the billing descriptor, or retry a failed payment against a different card.

Maintain a recurring-payment register for every subscription, advertising account, hosting service, and tool. Record the vendor, client, card identifier, billing frequency, expected amount, renewal date, cancellation owner, and notice period. Review the register at least monthly and whenever a client’s scope changes.

For teams managing subscriptions, the guidance on virtual card recurring payments can help frame the practical questions around recurring billing. The policy should still be tailored to your provider’s capabilities and the merchant’s rules. Some merchants may require a stable credential, may reject certain virtual cards, or may perform verification charges before accepting a subscription.

Use reloads only against an approved funding request. Every reload should include the client, amount, purpose, approved period, and person authorizing it. A reloadable virtual credit card may be useful for ongoing media or supplier spend, but the business should not treat available balance as permission to spend.

When a client pauses work, freeze the card before asking whether it is still needed. When the client terminates the engagement, stop reloads, cancel recurring charges, remove user access, export transaction records, and close or deactivate the card according to the provider’s process. Keep evidence of each step.

Reconcile each charge to the correct client record

Reconciliation is the control that proves the policy is working. Do not wait until month-end if the card is used heavily. High-volume advertising spend may need daily or twice-weekly review, while a low-volume software card may be reviewed weekly or monthly.

Each transaction should be matched to a client, vendor, service, date, amount, currency, invoice or receipt, and approval record. For advertising, also capture the platform account, campaign or account reference, and the relevant reporting period. If the merchant descriptor differs from the platform name, note that relationship in the ledger so another reviewer can understand it.

Set an exception status for missing evidence, duplicate charges, unexpected currency conversion, amount variance, unknown vendor, and spend outside the approved period. Exceptions should have an owner and a deadline. A transaction marked simply as pending review can remain unresolved indefinitely.

Consider a separate clearing account or ledger category for client-funded spend. This helps distinguish pass-through costs from agency revenue and makes it easier to prepare client invoices. Your accounting treatment should follow your own professional advice and contractual terms, especially where taxes, reimbursements, or foreign exchange are involved.

A reloadable virtual card can help maintain a defined funding boundary for a campaign or operating period. It does not eliminate the need to export records, retain receipts, or investigate disputed charges.

Use this implementation checklist and avoid common mistakes

Before activating a per-client card, complete this checklist:

Confirm the client contract or written authorization covers the intended spend.
Assign a unique card name, client code, purpose, owner, and review date.
Set the lowest practical limit and define the approved funding period.
List permitted merchants, platforms, countries, currencies, and users.
Record the approval and evidence requirements in the team’s operating system.
Test the first payment and confirm the transaction appears in the correct ledger.
Schedule recurring-charge and access reviews before the first renewal date.
Document the freeze, cancellation, and offboarding procedure.

Common mistakes are usually process failures, not card failures:

Using one shared card for several clients: This makes attribution difficult and increases the impact of a compromised credential.
Giving a card a vague purpose: A label such as Marketing Spend does not tell a reviewer whether a charge was allowed.
Setting a high limit for convenience: Convenience can create unnecessary exposure and weakens the approval trail.
Ignoring retries and verification charges: Small authorization or retry transactions can signal a billing issue or an unmonitored subscription.
Allowing contractors to store card data permanently: Access should be limited, documented, and removed when the assignment ends.
Failing to review merchant changes: A platform may add a new billing account or payment descriptor that falls outside the original approval.
Closing the client relationship without offboarding payments: Deactivating a user does not necessarily cancel recurring billing or stop all retries.

For teams that specifically need a Visa-branded funding option, compare the operational fit of a virtual visa reloadable product with the merchant acceptance and controls required by the client’s platforms. Product availability, verification requirements, limits, and supported use cases can vary, so confirm the current details before committing a campaign to it.

FAQ about per-client card policies

Should every client receive a separate virtual card?

Not always. A separate card is usually worthwhile when the client has material advertising spend, multiple stakeholders, strict reimbursement requirements, or a higher risk of billing confusion. For a low-volume client with one predictable subscription, a dedicated card can still be useful but may create unnecessary administration. If several clients share one card, use a documented allocation and reconciliation process and keep the merchant scope narrow.

Who should approve a card limit increase?

The approver should be someone who can verify both the client authorization and the business need, usually the account owner plus a finance or operations lead. The person requesting the increase should not be the only approver. Record the old limit, new limit, reason, effective period, and approval time. Temporary increases should have an automatic review or expiry date rather than remaining open-ended.

Can a reloadable card replace a client deposit or retainer?

No. A reloadable card is a payment-control tool, not a contract, deposit account, or guarantee of funding. It may help release approved spend in stages, but the engagement should separately define who funds the balance, when funds are available, how unused amounts are handled, and what happens if a payment is disputed. Never use card availability to infer that a client has approved additional work.

What should happen when a card transaction has no receipt?

Mark it as an exception immediately and assign an owner. Ask the vendor or platform for a replacement invoice, check the account billing history, and obtain written confirmation from the person who made the purchase. If evidence cannot be recovered, classify the transaction according to your internal accounting and client-billing policy. Do not silently assign an unsupported charge to a client simply because the card was client-specific.

Is a virtual Visa reloadable card suitable for every advertising platform?

No. Acceptance can depend on the platform, country, merchant verification process, billing history, card type, and whether the merchant permits virtual or prepaid-style payment methods. Test the card with a small approved transaction before moving a live campaign. Keep a fallback payment method that is authorized for the same client, but do not bypass a platform’s payment or identity-verification rules.

Take these steps in the next seven days

In the first two days, inventory every card, client, platform, recurring charge, and person with access. On days three and four, rename cards, remove obsolete users, and write the purpose, limits, merchant scope, and evidence rules for each active client relationship.

On days five and six, test the approval and reconciliation workflow with one live client. Review the first transactions, confirm that receipts are captured, and identify any recurring charge that lacks an owner or cancellation date. On day seven, freeze or deactivate cards that have no current business purpose and schedule a monthly policy review.

If you need a Visa-branded option for a defined client use case, you can also compare a reloadable virtual visa card with other business virtual card structures. The right choice is the one that supports the merchant, budget, evidence, and offboarding requirements without making control harder than the work itself.