Expenses

Spend, filed where questions get answered.

Each expense is a record: what was spent, when, on what category, by whom, and where it stands — submitted, approved or rejected. The month's total sits in the header.

The table answers the recurring questions — what did we spend this month, what's waiting for approval — and so does your AI, from the same rows.

What it does

Amount, date, category and approval state per expense.
Approve or reject from the row.
A this-month total that follows the table.
Expenses link to the employee who spent.

What it stores

As ordinary objects in your workspace memory — readable by your AI over MCP, browsable like any memory.

expense — One expense — amount, spent_on, category, status (submitted|approved|rejected).
employee — A person employed by the company — job_title, start_date, salary, status (active|left).