Expense Policy
Expense Policy: Define how spending is recorded and approved. Review source ledger, period, policy, account mapping, materiality, and reviewer and produce an expense policy and exception process.
--- name: accounting-expense-policy description: Use for expense policy when asked to define how spending is recorded and approved; produce an expense policy and exception process. license: MIT metadata: author: Thrive category: accounting --- # Expense Policy ## When to use Use this skill for expense policy when you need to define how spending is recorded and approved. The expected result is an expense policy and exception process. ## Boundaries Work within the requested task and its stated acceptance criteria. Drafting an artifact does not authorize publishing it, spending funds, changing a live system, or contacting another person. Identify any such action separately before taking it. ## Inputs Inspect source ledger, period, policy, account mapping, materiality, and reviewer. Resolve missing information that would change the method; state lesser assumptions in the result. ## Method 1. **Diagnose.** Tie the question to ledger accounts, transaction dates, source documents, policy, materiality, and period close. 2. **Decide.** Reconcile entries before recommending classification or adjustment. 3. **Produce.** Build an expense policy and exception process from the inspected material; keep assumptions distinguishable from observed facts. ## Decision rules - Reconcile totals and investigate exceptions before recommending entries or classifications. - When sources or constraints conflict, record the conflict and choose the path supported by the user's goal and the strongest available evidence. If neither path can be supported, identify the missing decision before changing the artifact. ## Domain rules - Keep a reproducible audit trail for each adjustment. - Flag tax or standards interpretation for qualified review. ## Verification Check controls against actual workflow. Compare the result with the user's acceptance criteria and record any unverified boundary. Provide a traceable schedule with source links, calculations, unresolved items, and reviewer sign-off. ## Evidence and stop conditions - Verify current authoritative sources for rules, prices, clinical claims, or obligations that can change. Distinguish fact, interpretation, and assumption. - Stop before an external action or regulated judgment without the required authorization or qualified reviewer. - When evidence is materially missing or conflicting, state the uncertainty and the exact source or decision needed to proceed. ## Stop conditions If a material input, required authorization, or a safe way to verify the result is absent, stop the affected action. Return the specific blocker and the smallest fact or decision needed to continue. Do not report an unrun check as passed. ## Output Provide an expense policy and exception process. Include the decisive evidence and actual verification result. Name any artifact location and unresolved issue that affects its use. <!-- MIT License Copyright (c) 2026 Thrive Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. -->