Who Should Get a Corporate Card, and How Should Limits Be Set?

Employees should qualify for a corporate card when they have recurring, approved business purchases that are better controlled on a company card than through reimbursements or ad hoc manager purchases. Good candidates include employees who buy recurring business services, travel for work, manage field purchases, handle event logistics, or regularly need approved low-dollar purchases that should not become reimbursements.

Seniority alone is a weak issuance criterion. Executives may need cards, but so might field managers, office managers, project leads, and employees who buy time-sensitive supplies. A clear corporate card policy should define eligibility by purchase pattern, not hierarchy.

A request-based corporate card issuance model usually works best because it connects every card to a documented business need. Issuing cards to everyone creates dormant accounts, offboarding risk, and subscriptions that keep renewing after ownership changes. Issuing cards only to travelers pushes non-travel purchases into reimbursements and personal cards.

The best request flow is lightweight but documented: the employee requests the card, the manager approves the business need, and finance sets the controls. A fast path can get cards to people who need them within a day while keeping the card census clean. If the request is for a one-time purchase, a controlled virtual card payment may be cleaner than a permanent card. Manager-card borrowing breaks accountability, and reimbursement shifts float to the employee.

Corporate card limits should be set from actual trailing spend plus controlled headroom, not from title, seniority, or negotiation. Pull six to twelve months of reimbursement history, existing card activity, and approved purchase requests for the employee or role. Use that history to estimate normal monthly need, then add a modest buffer.

For example, some finance teams use actual monthly spend plus 20% to 30% headroom as an internal starting point. That is a policy example, not a universal benchmark. The right headroom depends on role volatility, approval appetite, and how quickly temporary increases can be granted. New roles with no history should get starter limits that are reviewed after 60 to 90 days.

Spend data should lead, with role-based defaults used only as starting points. Individual contributors may need low monthly limits for tools, supplies, or travel incidentals. Managers may need mid-four-figure limits when they buy for teams or locations. Executives need larger limits only when they have genuine purchasing responsibility.

Avoid treating role ranges as industry benchmarks. They can be reasonable internal examples, but the stronger control is utilization. A card with 10% utilization for several quarters may be over-limited. A card consistently near its cap may need a higher limit, or it may show that invoice-able spend is leaking onto cards.

Common internal defaults run from the low hundreds to low thousands per month for individual contributors, mid-four figures for managers who buy for teams, and five figures only for roles with genuine purchasing responsibility. Treat those ranges as starting examples, not benchmark targets. Utilization is the metric to manage.

Corporate cards should have both monthly and per-transaction limits. A monthly cap controls total exposure, while a per-transaction cap pushes unusual purchases into a deliberate approval path. A card with only a monthly limit can still allow one large purchase that should have been reviewed first.

Temporary card limit increases should be tied to a specific purchase, business reason, amount, and expiration date. The approval record should show the requester, approver, reason, and reversion date.

If the purchase is predictable, require the request before the card is declined. If the request is urgent, grant the smallest increase that solves the problem and require post-purchase review. Limit changes should follow the same documented discipline as credit card request approval.

Corporate card limit policy holds when every raise follows the same fast, rule-based process, including escalations from sales or leadership. Publish the raise process, define the evidence it requires, and ask for the same facts every time: what was declined, why the higher limit is needed, and what business impact the decline created.

Limits collapse when raises become relationship-based. If a manager can bypass the process by escalating over finance, the written policy stops mattering. The cleaner pattern is to make legitimate increases easy to request and fast to decide, while still requiring the same approval record for every cardholder.

An emergency limit-raise process should define an after-hours path with a named backup approver, a hard cap on the raise, a short expiration window, and a mandatory post-event review. Emergency raises are sometimes necessary for travel, field work, and customer-facing situations, but they need guardrails.

Emergency raises should auto-expire within 48 to 72 hours when the platform supports it. If auto-expiration is not available, calendar the reversion before approving the increase. The post-hoc review keeps emergency access from becoming an unofficial bypass. If emergency raises happen repeatedly for the same cardholder, finance should revisit the base limit or move the spend into purchasing or AP.

Contractors and temporary workers should rarely receive permanent corporate cards. If they need buying access, prefer virtual cards with merchant locks, low limits, specific purchase scope, and end dates tied to the contract.

Their offboarding risk is higher and the accountability chain is weaker, so the controls must be structural rather than policy-based. If the business need is real, build the control into the payment method instead of relying only on policy language.

Finance should review corporate card limits at least quarterly. Compare each card's limit to its trailing 90-day peak utilization, lower limits with sustained underuse, investigate near-cap cards, and close or suspend dormant cards. A practical trigger is to review cards with under about 30% utilization and cards consistently near their cap.

Near-cap spend does not always mean the cardholder needs a higher limit. It may mean invoice-able spend is hiding on a card. Finance should either approve a rule-based raise or route that spend into purchasing, accounts payable, or a pre-approved request workflow.

A corporate card policy should define who qualifies, how limits are set, who approves changes, and how often finance reviews the card population.

• Issue cards based on recurring business spend need, not seniority.
• Require documented manager approval and finance configuration before issuance.
• Set both monthly and per-transaction limits from actual or expected spend.
• Use time-boxed approvals for temporary card limit increases.
• Review utilization, dormant cards, and near-cap cards every quarter.

A card request workflow should capture the business need before finance configures the card, and a limit-change workflow should preserve the same approval evidence. The employee should document the business need, expected spend type, and requested amount. The manager should confirm that the role, project, or location requires card spend. Finance should then set the limit, card type, merchant rules, alerts, and coding requirements before the card is used.

After issuance, the same workflow should preserve the transaction, receipt, coding, approval trail, and any later limit-change justification. Quarterly utilization reviews then give finance the evidence to lower, raise, suspend, or close cards based on actual business need. That record is what auditors ask for later.

Corporate card controls weaken when finance treats cards as convenience tools instead of governed payment methods. The most common mistakes are:

• Issuing cards to everyone because it feels efficient, then carrying dormant cards and unclear ownership.
• Setting limits by title instead of actual spend, which creates over-limited cards and under-supported employees.
• Approving temporary raises without an expiration date or calendar reminder.
• Letting card spend bypass coding, receipt capture, or expense management rules.
• Allowing card transactions to post without clean ERP integration and reconciliation discipline.

Stampli Card supports employee-initiated requests with finance-owned controls. Employees can request a card or a limit change in plain terms, while finance configures card type, limits, merchant category restrictions, usage alerts, and related controls before spend happens. Cardholders can request limit changes, suspend and unsuspend their own cards, and set usage alerts, so routine adjustments do not have to queue up in finance.

Stampli's position is that spend management should manage spend, not encourage it. The card should be part of the controlled workflow, not a shortcut around it: requests happen before spend, coding and controls stay attached to the transaction, and card activity remains visible for review, reconciliation, and policy enforcement.