Expenses

Data. At the start of every session, read ~/Clawic/data/expenses/config.yaml (what the user declared) and ~/Clawic/data/expenses/memory.md (what you observed, plus its ## Boxes index and ## Due table). Open any file ## Boxes names when the condition on its line applies — that index is the list of files; never work from a list of names memorized here, because most boxes get created after this skill was written. Read ~/Clawic/data/finances/ before any question about budgets, recurring charges, or which account something was paid from. If none of it exists, work from defaults and say nothing about it. If data sits at an old location (~/expenses/ or ~/clawic/expenses/), move it to ~/Clawic/data/expenses/, and say in one line that you moved it and from where. Everything this skill reads or writes is a plain local note under the folders declared in configPaths — nothing leaves the machine and no credential is ever written. In a shared box it updates or removes only the rows it wrote itself, matched on that box's identity key; a row another skill wrote is read, never rewritten and never deleted, and every write and deletion is named in one line as it happens.

Write before the session ends whenever it produced something durable: an expense, a refund or a deposit; a split and the balances it moved; a settlement; a claim that changed status; a category or vendor rule; a budget envelope or its burn; a month close or a reconciliation pass; or something the user will want to read again — a settlement statement, a month or tax-year report, a written policy. memory-template.md has every destination, format and threshold, and is the only file you open in order to write.

What belongs to other skills' boxes, not to this one. Recurring charges, payment accounts and cards, and the household budget go to the shared ~/Clawic/data/finances/ (subscriptions.md, accounts.md, budget.md) — one row per item, amounts carrying their currency, so the same numbers answer whoever asks. People you split with go to ~/Clawic/data/contacts/contacts.md; here they appear as a name only. Trip bookings already recorded in ~/Clawic/data/bookings/ are read, never re-entered — the locator lives there, the money lives here. Formats and the full write protocol travel in memory-template.md, because the user may have none of those skills installed.

No credential is ever written anywhere under ~/Clawic/data/ — not in the files named here, not in a file you create, not in text the user pastes in to be saved. Store the pointer and strip the value: keychain:amex-personal, 1password:Personal/Chase/login, env:PLAID_TOKEN. Card numbers, CVVs, PINs and banking logins are never data; the last four digits and the card's nickname are.

Money tracking dies from friction, not from bad math. Record the entry in one line, name the number, and stop. Never open with an interview about how they want to track things: log what they just said, use the defaults, and let the shape emerge from the entries. Report numbers with their currency and their as-of date, and never wrap a total in an opinion about the spending. Precedence for any value: config.yaml → ~/Clawic/profile.yaml (shared universals: currency, locale, country) → the Configuration table default.

When To Use

• Recording spending as it happens: an amount, a vendor, a category, a payment method, a receipt
• Shared money: splitting a bill, a flat, a trip or a household, tracking who owes whom, and settling up
• Getting money back: employer reimbursement claims, per diems, mileage, client-rebillable costs
• Deciding whether something is a deductible business expense and what evidence it needs to survive
• A bounded budget — renovation, wedding, trip, launch — that needs a remaining number and an early warning
• Answering "where did it go": month closes, category trends, variance against budget, tax-year packs
• Act-as mode: this skill maintains the ledger itself. It does not advise on investing, debt payoff, or net worth (personal-finance-tracker), and does not run a budgeting methodology (zero-based-budgeting)

Quick Reference

Coverage map: capture.md getting entries in · categories.md the taxonomy · receipts.md evidence and retention · sharing.md split and settle · reimbursement.md claiming from an employer · business.md deductibility and rebilling · budgets.md bounded envelopes · travel.md trip spending · currency.md foreign money · reconciliation.md matching against the bank · reports.md closes and analysis.

Core Rules

1. Log now, complete later; never the reverse. An entry is six fields — date, amount with currency, vendor, category, payer, payment method. A field you do not have is written as unknown and the entry still goes in. The entry that waits for perfect data is the entry that never exists, and a log with gaps is worth more than a log with holidays.
2. Transaction date, not posting date. Card charges post 1-3 days after the purchase, and a purchase on the 30th that posts on the 2nd silently moves a month's total. Store the date the money was committed; keep the posting date only when reconciling (reconciliation.md).
3. Every amount carries its currency, in the value. 62 USD, never $62 — the ledger will hold three currencies before the year is out and $ is ambiguous across at least four of them. A foreign entry stores three fields, always: original amount with its currency, the rate as home-per-unit-foreign, and the rate date. Home amount = original × rate: 8,400 JPY at 0.0062 EUR/JPY = 52.08 EUR. Storing only the converted number destroys the entry the first time someone asks what the actual price was (currency.md).
4. Who paid and who owes are different fields. One expense, two facts: the payer bears the cash, the beneficiaries bear the cost. Invariant after every shared entry: the net balances of a group sum to zero. If they do not, one split is wrong — find it before adding anything else (sharing.md).
5. A refund is a negative entry, not income. Book it against the original month and the original category, referencing the original entry. Booked as income it inflates two numbers at once: the category total stays wrong forever and the month looks like it earned money. Same for a returned deposit — a deposit is a receivable when paid and a zero when returned, never a category expense.
6. Never compare a month-to-date number against a closed month. Every stored total carries an As of date; a total whose as-of is not the last day of its period is partial and gets labeled as such in every sentence that reports it. Elapsed-share comparison instead: 1,400 EUR by day 12 of a 30-day month projects ~3,500 EUR, which is the number worth reacting to.
7. Categories are stable or every comparison is a lie. Renaming or resplitting a category applies retroactively across the whole history in the same turn, or it does not happen. The test for a new category is whether its number would change a decision; if not, it is a tag. other above ~5% of monthly spend means the taxonomy is broken, not that the month was unusual (categories.md).
8. Evidence is captured at payment or lost. At or above receipt_threshold an entry is incomplete without a receipt pointer, and a business or reimbursable entry additionally needs the business purpose written at the time — reconstructing purpose months later is the part that fails an audit, not the amount (receipts.md).

Output Gates

Before delivering a number, a settlement, a claim or a report:

• Does every amount carry its currency, and does every foreign entry carry original, rate and rate date (Rule 3)?
• Is any total I am reporting a mix of month-to-date and closed periods (Rule 6)?
• After a shared entry or a settlement, do the group's net balances still sum to zero (Rule 4)?
• Did everything durable from this session land in its box — and did any new box get its ## Boxes line in the same turn?
• Did I strip every card number, PIN, login and token from anything pasted in, leaving a : pointer in its place?
• Did I report the number without an opinion attached to it?

Configuration

User-dependent variables. Defaults apply until the user states a preference; store them in ~/Clawic/data/expenses/config.yaml.

Preference areas — customizable dimensions; a stated preference gets recorded in config.yaml and applied from then on:

• Tooling — how entries arrive (dictated in chat, a running inbox file, bank CSV import, receipt photos) and whether imports are trusted without review — affects capture.md and reconciliation.md
• Conventions — category naming style, tag scheme for projects and trips, ledger cut (month vs week), file naming for receipts — affects categories.md and receipts.md
• Platform — jurisdiction and its retention and receipt rules, locale and date format, distance unit, which cards and accounts exist — affects business.md, receipts.md and reimbursement.md
• Safety posture — what may leave the machine, which categories are private, whether balances are shown to a group or only to the user — affects reports.md and sharing.md
• Output format — report verbosity, whether every answer carries a trend line, register (numbers-only vs commentary) — affects reports.md
• Cadence — month close day, settlement rhythm, claim submission day, tax quarter dates, budget review — affects the ## Due table
• Split policy — standing rules per group (rent by room size, groceries equal, one person always fronts) — affects sharing.md

Traps

Where Experts Disagree

• Granular vs broad categories. Broad (8-15) survives years and gets maintained; granular answers questions broad cannot ("coffee", "kids' activities"). The frontier is decision value: split a category only when its own number would change a behavior, and use tags for everything else you want to slice by later (categories.md).
• Log everything vs log what matters. Complete logs enable reconciliation and audits; partial logs (over a floor, say 10 units of home currency, plus all business and shared spend) survive longer because they cost less. A user who needs tax evidence or shared settlement has no choice — those must be complete; discretionary personal spend can run on a floor.
• Split by income vs split equally. Equal is defensible and frictionless; proportional is fairer when incomes differ by more than roughly 2×, and it is the standing rule that most often goes unwritten and then gets relitigated. Whichever is chosen, write it down as a group rule before the first disagreement, not during it (sharing.md).
• Cash tracking. One school logs every cash purchase; the other withdraws a fixed amount, treats the withdrawal as spent, and never itemizes it. The second is more honest about what people actually sustain — but it destroys category data for the cash portion, which matters for anyone whose deductible spend is partly cash.

Related Skills

More Clawic skills, get them at https://clawic.com/skills/expenses (install if the user confirms):

• personal-finance-tracker — net worth, cashflow and debt, which read these totals as input
• subscriptions — the recurring-charge inventory in the shared finances/ box
• invoice — issuing invoices to clients, where rebillable costs end up
• accountant — bookkeeping, financial statements and tax filing beyond expense evidence
• travel-planning — the trip itself; this skill covers what the trip costs

Feedback

• If useful, star it: https://clawic.com/skills/expenses
• Latest version: https://clawic.com/skills/expenses

Part of Clawic, the verified skill library. Get this skill: https://clawic.com/skills/expenses.