Expense Policy Best Practices
for Fast-Growing Startups
Most fast-growing startups have no expense policy at all — or have one that was written two years ago, lives in a Google Doc nobody opens, and bears no resemblance to how expenses are actually approved.
This is not a moral failure. It is a sequencing problem. In the early days, the founder approves everything informally and it works. But as the team grows, informal approval becomes a bottleneck. The policy gets written reactively — usually after a bad experience — and then never maintained. By the time a company hits 50 people, the gap between the written policy and actual approval behaviour can be significant.
This guide covers what a practical expense policy looks like for each stage of startup growth, what the essential components are, and how to actually enforce it without hiring a full-time finance controller.
How Expense Policy Breaks Down as You Grow
Understanding why your current approach is breaking down is the first step to fixing it. Here is the typical progression:
The founder approves everything
The policy is informal: "ask me first for anything over S$200." This works because the founder has full context on every decision. It breaks down the moment the founder cannot respond to every request within 24 hours.
Works fine until it doesn't — the breakpoint is usually around 10–15 people when approval requests start competing with actual work.
Delegation without documentation
The founder delegates approval authority to a team lead or CFO. But the policy is still verbal — "you know what's reasonable." Different approvers make different calls. Employees get inconsistent signals. Finance cannot forecast because spending is opaque.
Policy inconsistency creates friction and quiet resentment. The same expense gets approved for one person and queried for another.
Written policy but manual enforcement
Someone finally writes a policy document. But enforcement is still manual — approvers check policy from memory, violations slip through, and the policy document is never read again after the first week.
A policy that exists but isn't enforced is worse than no policy: it creates a false sense of control while the actual spending behaviour remains unconstrained.
The 6 Essential Components of a Startup Expense Policy
A good expense policy does not need to be long — it needs to be specific, consistent, and actually enforced. These six components cover the vast majority of decisions that come up in day-to-day expense approval.
Per-Category Spending Limits
Example Rule
Meals (internal): S$25/person. Client entertainment: S$80/person with manager approval. Hotel: S$250/night in Singapore, S$350/night international. SaaS tools: up to S$50/month self-serve; above requires Finance approval.
Why This Works
A single global cap fails for modern teams. The same S$200 limit that is restrictive for client dinners is permissive for office lunches. Category-specific limits reduce both rejection noise and overspending.
Required Documentation by Amount
Example Rule
Under S$50: no receipt required but recommended. S$50–S$500: receipt required. Above S$500: receipt plus business justification. Above S$2,000: two-level approval (manager + Finance).
Why This Works
Requiring receipts for everything creates friction on small purchases. Requiring nothing creates a documentation gap for large ones. A tiered approach matches oversight to risk.
Submission Deadline
Example Rule
All expenses must be submitted within 30 calendar days of the expense date. Exceptions require VP-level approval.
Why This Works
Late submissions create reconciliation problems, make it harder to verify receipts, and complicate budget period closings. A hard 30-day rule, enforced consistently, solves all three.
Pre-Approval for Large or Unusual Expenses
Example Rule
Any expense above S$1,000 must be pre-approved before being incurred. Conference registrations, team offsites, and equipment purchases always require pre-approval regardless of amount.
Why This Works
Post-hoc approval for large expenses puts managers in an awkward position: the money is already spent, making rejection painful. Pre-approval prevents the spend if it shouldn't happen.
Explicit Exclusions
Example Rule
The following are never reimbursable regardless of amount: alcohol purchased separately (only as part of a meal), personal grooming, gym memberships, family member expenses, fines and penalties.
Why This Works
Without a clear exclusion list, employees will submit anything they can rationalise as vaguely work-related. Being explicit about what is not covered saves everyone the awkward conversation.
Travel Policy
Example Rule
Economy class for flights under 4 hours. Business class requires VP approval. Book through the company travel tool where possible. Car rental requires Finance pre-approval.
Why This Works
Travel is typically the highest-spend category after payroll. Specific rules here have disproportionate impact on total expense costs.
From Policy to Enforcement
Writing a policy is the easy part. The hard part is making sure it is actually applied consistently — without requiring an approver to memorise dozens of rules and check each submission against them manually. That is where automated enforcement changes the game.
When your expense policy rules are encoded into an AI system like Kopi, every submission is automatically checked against your configured limits, documentation requirements, and approval thresholds before the approver ever sees it. Policy violations are surfaced with context — not just flagged, but explained. Approvers spend time on exceptions and judgement calls, not on checking whether a S$30 meal receipt is attached.
5 Tips for Keeping Your Policy Effective
Write the policy, then encode it
A policy document is not a control — it is documentation. Real enforcement requires the rules to be checked automatically, at the point of submission. Encode your limits and rules into an expense automation system so enforcement does not depend on an approver's memory.
Communicate before enforcing
When you update your expense policy, send a team-wide message explaining the changes and why. Employees who understand the reasoning comply more consistently than those who see the rules as arbitrary bureaucracy.
Review flag rates, not just exceptions
If your AI or approval system flags 20% of submissions as anomalous, something is wrong — either the policy limits are miscalibrated or the team has genuinely changed its spending patterns. High flag rates are a signal to review and adjust limits, not just to reject more claims.
Update the policy at least once a year
A policy written when the team was 15 people will not fit a 50-person team. Revisit limits annually: adjust for inflation, role changes, new categories of business spend (SaaS proliferation, remote work costs), and what your anomaly data tells you about actual spending patterns.
Be consistent with approvals
The fastest way to erode policy trust is inconsistency. If the same expense is approved for one team member and rejected for another, without clear explanation, the policy becomes a source of resentment rather than a shared standard. Automation helps here: consistent rules, consistently applied.
The Right Time to Set Up Your Policy Is Before You Need It
The most common mistake startups make with expense policy is treating it as a reactive measure — something to implement after a problem surfaces. By that point, bad habits are already established, and changing them requires both a policy change and a behaviour change.
Setting up a written, enforced expense policy at 15–20 people — before the informal approval model breaks — is one of the highest-leverage operational investments a fast-growing startup can make. It prevents the problem rather than solving it.
For Singapore startups using Lark, setting up automated expense policy enforcement takes under 10 minutes. Learn how in our step-by-step Lark setup guide, or start a free Kopi account to connect your workspace today.
Enforce your expense policy automatically in Lark
Kopi encodes your policy rules and checks every submission automatically. Free for Singapore SMBs in private beta.