Most corporate card policies are written like a contract and read like a hostage note. The employee wants to know whether they can book the train. The policy gives them fourteen pages about allowable expenditure.
A useful policy can be thorough without being unreadable. Start with the short version—the rules someone should recall while standing at a register—and keep the detail close enough for finance to make consistent decisions.
Begin with five plain sentences
Try this structure and adapt it to your business:
- Use your company card for approved business purchases, not personal ones.
- Check that your purchase fits the card’s purpose and available limit.
- Get pre-approval for travel, exceptions, and purchases above your threshold.
- Add a receipt and business purpose within two business days.
- Tell finance immediately about fraud, a lost card, or an accidental personal charge.
Those sentences do not replace the detailed policy. They make the detailed policy possible to follow.
Explain the why where it changes behavior
“Receipts are mandatory” sounds like finance enjoys collecting them. “We need the itemized receipt to confirm tax and match the card charge” explains the work. People are more careful when the request has an operational reason.
Set thresholds people can understand
Use a small number of thresholds tied to real decisions. For example, team members can spend within an approved budget; a manager reviews travel before booking; and finance reviews any single purchase above $2,500. If your table has twelve bands, check whether they represent actual judgment or historical accumulation.
If the policy needs a flowchart for a $40 lunch, the policy is doing too much.
Make exceptions normal, not sneaky
A traveling employee will eventually face a closed merchant category, a split payment, or a client dinner that ran above plan. Give them a clear exception route and require a short reason. Do not force people to disguise an honest exception as a category that happens to pass.
Finance should review exceptions for patterns. Repeated exceptions may mean the limit is wrong, the merchant mapping is poor, or the budget no longer matches the work.
Decide what happens after a mistake
An accidental personal purchase is not the same event as deliberate misuse. Your policy should distinguish them. Explain how to report an accident, how repayment works, and when repeated or intentional misuse becomes a people-management issue. Consistency matters more than severe wording.
Put the policy where spending happens
The card name, limit, approval requirement, and submission checklist should be visible in the spend tool. Keep the complete policy in your normal company library, but do not expect someone to consult it before every purchase.
Review the policy twice a year with actual transaction data. Remove rules that create work without changing decisions. Add guidance for new spending patterns. A good policy is maintained like a process, not framed like a poster.