경비 처리 기준 문서 쓰는 프롬프트
매번 묻는 항목을 기준으로 만듭니다. 애매한 경계를 명시적으로 정합니다.
| 분류 | 사무 › 재무·경리 |
|---|---|
| 태그 | 초안작성템플릿직장인 |
Write an expense policy. **Start from the questions I keep getting.** Those are where the policy is missing, and they are worth more than any template. Per category, state: 1. What is covered, specifically. 2. **The boundary.** Not "reasonable" — an amount, a condition, or a rule. *"Reasonable" is what a dispute is made of.* 3. What is not covered, named. The absent list prevents more arguments than the present one. 4. What documentation is required, and what to do when it is unavailable. 5. Approval: who, before or after, above what threshold. Cover the cases that actually generate questions: meals with clients versus with colleagues, travel where personal and business overlap, equipment that stays with the person, subscriptions, gifts, anything paid personally and claimed later. Then: - **Edge cases with no answer yet.** List them as decisions to make rather than leaving them for the first dispute. - Where the policy will be perceived as unfair, and whether that is worth the saving. - What to do when someone spends outside policy — having this written prevents it being handled inconsistently. Rules: - ⚠️ **Tax treatment and what is deductible depend on jurisdiction and change.** Do not state any tax position as fact. Mark every one as requiring confirmation from the responsible party. - *Do not invent amounts.* Where I did not give a threshold, write `[amount to be decided]`. - Plain language. A policy people cannot parse is a policy they ignore.
붙여 넣으면 맨 아래에 채울 칸(현재 관행·기준 · 자주 나오는 질문 · 회사 규모·업종)이 나옵니다
어떤 프롬프트인가
경비 규정이 분쟁이 되는 건 경계가 안 적혀 있어서다. 이 프롬프트는 "이건 되나요" 소리가 나오는 항목을 먼저 찾아 그 경계를 문장으로 못 박는다.
같은 분류의 프롬프트
| 회계사 역할을 맡기는 프롬프트 | |
| 은행 거래 분석 프롬프트 | |
| 예산 요청서 쓰는 프롬프트 | |
| 월 마감 점검표 만드는 프롬프트 | |
| 청구서 검토 항목 짚는 프롬프트 |