Employee Spend Policy: What to Write and How to Set Limits

Use these headings as your outline, and keep each one to a paragraph or a short list:

• Purpose and scope: who the policy applies to, including contractors if they hold cards.
• Allowed and prohibited spend: business expenses in general, plus a short list of things that are never allowed, such as personal purchases and cash advances.
• Approval limits: who can approve what, by amount.
• Payment methods: company card first, reimbursement only when a card wasn't possible.
• Receipts and coding: what must be submitted, by when, and what account or project to code to.
• Travel, meals and client entertainment rules.
• Software and recurring subscriptions, which need their own approval path because they renew silently.
• Exceptions, violations and how the policy gets updated.

Write in the second person and use plain sentences, so a new hire can follow it on day one.

Start from the damage a single bad decision could do, then set limits by role and amount. For example, an employee might buy up to $250 without pre-approval, a manager might approve up to $2,500, the finance lead might approve up to $10,000, and anything above goes to a founder or a second signer. Your numbers should fit your cash and payroll size. A ten-person company and a hundred-person company shouldn't share thresholds.

Card limits are a separate lever. Give each card a monthly limit based on that person's actual needs, and lock cards to merchant categories where your tool allows it, so a marketing card can't be used at an airline unless travel is part of the job. Raise limits on request instead of setting them high just in case.

For recurring purchases, use the total cost. A 300 monthly tool is 3,600 a year, so it belongs in the same approval band as a one-time 3,600 purchase. Say so in the policy. For a companion document focused on cards, see the corporate card policy template.

These three areas generate most of the questions, so give each one a few concrete rules:

1. Travel: book through one channel, choose the fare class you allow (for example, economy for flights under a set length), cap nightly hotel rates by city type and say who approves exceptions.
2. Meals: separate team meals, client meals and travel meals, and require names of attendees and the business purpose on client meals.
3. Software and subscriptions: require approval before signing up, ask for an owner for each tool, and review the list every quarter for tools nobody uses.
4. Reimbursements: ask for receipts within a fixed number of days and pay on a set schedule, so staff aren't waiting on the founder's calendar.

Ask your CPA about an accountable plan for reimbursements. It sets out substantiation and return-of-excess rules that keep reimbursements from being treated as taxable pay.

Rely on the tool where you can. Corporate card and expense platforms can block a transaction above a limit, require a receipt before the next purchase and route approvals to the right manager automatically. Compare options in Brex vs Ramp vs Navan. Where a payment doesn't go on a card, run it through your accounts payable process so it gets the same approval.

Set a review rhythm as well. Once a month, have someone other than the cardholder scan the list for split purchases, weekend charges, duplicate subscriptions and missing receipts. Once a quarter, review the policy itself against real requests: if people ask for the same exception repeatedly, change the rule.

Say what happens when someone breaks the policy. A gentle first response, such as a reminder and a chance to fix the receipt, works for honest mistakes. Repeat or deliberate violations should lead to lost card privileges and, where appropriate, reimbursement to the company. For how long to keep receipts and expense records, follow your CPA's advice and the records retention policy guide.

Watch for these:

• Approval limits so low that everyone asks for permission all day, which trains people to route around the policy.
• Limits so high that the policy doesn't catch anything.
• No owner for recurring software, so licenses keep renewing after the team that wanted them has left.
• A policy that lives in a shared drive nobody opens. Put it in the onboarding checklist and link it from the card tool.
• Rules that differ between the card program and the reimbursement process, so employees pick whichever is looser.
• No process for urgent purchases, so people use personal cards and expense them later.

For the treasury side of controlling cash, the startup treasury policy guide covers who can move money between accounts and set up payments.