top of page

How Founders Set Up a Company Expense Policy

3 hours ago
4 min read

The first time someone on a five-person team books a flight, buys a laptop or expenses a client dinner, the founder usually approves it in a chat thread and moves on. That works until it does not. Receipts go missing, a charge looks off, or a new hire asks what is allowed and no one has a clear answer.


A written expense policy is not paperwork for its own sake. It tells the team how company money may be used, what needs approval and how to get reimbursed. Founders who set this up early spend less time answering the same questions and less time cleaning up messy books later.


Start With Principles, Then Rules


Begin with a short statement of intent. The company will pay for reasonable costs that help the business, and it will not pay for personal spending dressed up as work. That sentence gives everyone a standard when a request sits in a gray area.


Then set the categories you actually use: travel, meals with customers, software and tools, office supplies, equipment, and professional development. You do not need a policy that tries to imagine every future purchase. You need clear rules for the spending you already see, plus a way to handle anything new.


Write in plain language. If a new hire cannot understand the policy in one sitting, it is too long or too legal. A good first version can fit on two or three pages and still cover the decisions that matter.


Spell Out What Is Allowed and What Is Not


Be specific about the items that create friction. Say whether alcohol can be expensed, whether first class or premium economy is allowed, and whether rideshares, rental cars or mileage are preferred. Set a per person meal range that fits your market, and say that the company will not reimburse personal travel add-ons, traffic tickets or purchases that lack a business purpose.


Equipment deserves its own line. Laptops, phones and monitors should be company property, purchased through an approved vendor when you have one, and returned if someone leaves. Software subscriptions should go on a company card whenever possible, so the account does not walk out the door with an employee.


State the documentation you require. A receipt or invoice should show the vendor, the date, the amount and what was purchased. A credit card line with no detail is not enough. For meals, ask for the names of the people present and the business purpose. Those two fields turn a vague charge into something an accountant can explain later.


Set Approval Limits That Match the Size of the Team


A founder should not have to approve every $12 software charge. Set a threshold below which managers or individual contributors can spend within policy without a second signature, and a higher threshold that needs the founder or finance lead. As the team grows, you can add a second layer rather than rewriting the whole document.


Say how approval must be given. A spoken yes in a hallway is easy to forget. A written approval in your expense tool, email or a shared channel creates a record. Require approval before the purchase for anything above your limit, not after the card has already been charged.


Give one person, even if that person is still the founder, the job of reviewing submissions on a regular cadence. Weekly is better than monthly, because problems are easier to fix when the receipt is still fresh.


Roll It Out Without Slowing People Down


A policy that sits in a folder no one opens will not change behavior. Walk the team through it once, show them the tool they should use, and make the first submission together if needed. Put the document in a place people can find, and add it to onboarding so new hires do not have to guess.


Choose a simple process. Many early teams start with a shared company card for recurring vendors and a reimbursement form for out-of-pocket costs. If you use an expense app, set the categories and receipt rules there so the policy and the workflow match. The easier it is to comply, the less you will spend chasing missing paperwork.


Plan for exceptions. There will be a last-minute flight, a client dinner that runs past the meal range, or a tool the team needs before the next approval cycle. Allow a written exception from the founder or finance lead, and keep a short record of why it was granted. Exceptions should be rare and explained, not a quiet second policy.


Review It as the Company Changes


Revisit the policy at least once a year, and sooner if you hire quickly, enter a new market or raise a round that changes how you travel and spend. Limits that made sense at six people may be too tight, or too loose, at twenty.


Watch for patterns in the reviews. If the same kind of request is always an exception, the rule may be wrong. If one category is full of incomplete receipts, the documentation standard may need a clearer example. The policy should get simpler where it can and sharper where the company keeps getting surprised.


An expense policy will not make a young company look like a large one, and it should not try to. It should make spending predictable, fair and easy to explain. Write it while the team is still small, keep it short, and treat it as a working document. The goal is not control for its own sake. The goal is a company that can grow without losing track of where the money went.

Comments


Founder Podcast
Featured Founders
bottom of page