Expense Management

Expense Management helps define a claim form requiring receipt and amount details, with approvals routed by claim limits. It keeps finance reconciliation as a separate monthly step. The workflow moves from submission through manager approval and finance checking to reimbursement, followed by monthly reconciliation.

The skill separates advice, review, conversion and build requests before producing artifacts. Advice receives a short recommendation and an offer of a relevant build. An explicit build request proceeds once essential missing facts are resolved. It asks one question at a time, reuses answers already supplied and stops when further answers would not change the deliverable. Unknown information remains unknown rather than receiving invented values.

Use it for an expense tracker, claim form, reimbursement tracker or spend claim database. It fits starter-stage businesses clarifying receipt requirements and approval limits in an existing spreadsheet or app process.

It produces empty templates and does not pay reimbursements or connect to a bank or accounting system. The skill does not calculate payroll, tax, leave balances or KPIs. Automation, reminders and synchronization require an integration layer. Legal, tax and HR review is required before templates drive real decisions.

Inputs cover claim limits, receipt thresholds, category rules, first and second approvers, reimbursement method, tax recording, project or cost-centre tracking, currency and current rejection reasons. The outcome can be a form, approval structure or reconciliation view. Fields record claim, employee, department, amount, tax amount, currency, expense and submission dates, approver, approval level, category, project or cost centre, budget line, receipt attachment, reimbursement date, status, notes and expense ID. Approval levels include manager, finance, owner and auto-approved labels; their presence as options does not create automation. Claim statuses distinguish draft, submitted, approved, reimbursed and rejected records.

Requested artifacts can include CSV, SQL DDL, JSON Schema, Notion property mappings or an Excel workbook. The formats derive from one field list: CSV and JSON retain matching display names, while SQL uses normalized identifiers. Dates retain date types, money retains currency types and cross-table references retain relation types. Select options are a starting set that can be renamed to match the business.

One SQL example is:

CREATE INDEX idx_expense_management_status ON expense_management (status);

Templates are empty by default. Example rows are produced only on request and remain obviously synthetic. Sensitive identifiers should not be repeated unnecessarily during a requested review. Machine-readable data stays separate from explanatory prose and any material validation failures. Excel-compatible CSV uses UTF-8 with a byte order mark and accompanying guidance about number, date and currency columns. An XLSX workbook is a separate requested output rather than a renamed CSV.

The Notion output routes to notion-manual-import for CSV, property mappings, import steps and verification. Manual mappings require no connection. Requested live workspace changes require actual tool access, a verified target and authorization. Imported columns may initially be Text and need their mapped property types applied. Relation links resolve after both relevant databases are imported. A static mapping alone does not establish a completed workspace change.