Individual skill
expense-policy
Drafts a clear, enforceable expense and approval policy - per-category spend limits, a dollar-tiered approval matrix, receipt and documentation rules, 30/90-day submission deadlines, and audit sampling. Use when someone says "write our expense policy", "who should approve what spend", "set reimbursement rules", or is onboarding a finance system or preparing for a compliance review. Do NOT use for building a departmental or personal budget - use budget-builder instead; do NOT use for the monthly close checklist - use month-end-close instead; do NOT use for general internal SOPs outside spend - use process-doc instead.
skills/expense-policy/SKILL.md
Source commit 97a13607d669157a4a16d5ba79b77f208319f7b9
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Not checked yet
- Last checked
- Nov 6, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 24
- Repository last updated
- Oct 13, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- claude Repository topic
- claude-skills Repository topic
- skill-me Repository topic
- finance Derived category
- legal Derived category
- operations Derived category
- security Derived category
- docs Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 7,486 bytes
Read excerpt
# Expense and Approval Policy
An expense policy that employees ignore is worse than no policy - it creates a false sense of control while spend leaks through exceptions. A good policy is short enough to read, specific enough to apply, and enforced consistently; the costly mistake this skill prevents is the prose-heavy policy nobody can apply at the moment of purchase, which converts every expense into a judgment call and every judgment call into precedent.
## Operating procedure
Order matters: limits must be calibrated to the company before the approval matrix is drawn, or the tiers will not match how spend actually flows.
1. Collect the inputs below.
2. Draft the five mandatory sections in order: what is reimbursable, spend limits by category, approval authority by amount, documentation requirements, submission deadlines. Each section is a table or short bulleted list - never prose paragraphs. An employee must be able to scan to any answer in under 30 seconds.
3. Calibrate the default numbers below to the company's size, geography, and travel intensity. Keep the structure even where the numbers move.
4. Add the enforcement section - a policy without stated consequences is a suggestion.
5. Close the catch-all: anything not listed is not reimbursable without explicit pre-approval.
6. Route the draft to finance and legal for sign-off before publication, and pair with the expense-tool configuration so approval tiers are enforced in software, not memory.