Expense reports with receipt photos, built by Claude Code on Elements
Expenses with receipt photos, reports that approvers approve or send back with a comment, monthly totals, and email, all live.
How it's built
Slipjar needed expenses with receipt photos, reports that move from draft to approved or sent back, emails at each step, monthly totals and pages that stay current for both employees and approvers. Each of those is a part of Elements, so the agent spent its 22 minutes on the workflow itself.
- Reports that update in place. A channel carries each report's new summary whenever it changes. An employee's list, the approver's queue, the report page and the monthly totals all listen, so a decision shows up on every open screen as it happens.
- Receipt photos from the form. An employee adds an expense with its receipt photo straight from a form, and the image is stored with the expense in one transaction and shown only to its owner and approvers.
- An approval workflow. A draft is submitted, then approved or sent back with a comment. Exactly one approver decides, and each report goes to an approver other than its owner.
- Background work. Jobs email the approvers when a report is submitted and the employee when it is decided.
- Server calls as function calls. Adding expenses, building reports, submitting, deciding and the monthly totals call server functions straight from the page with
@rpc. Totals count approved spending by category, with submitted amounts shown as pending. - Data and roles from SQL. Migrations define the workflow and seed two approvers, five employees and reports in every status, with receipts. Sessions and roles keep the queue with the approvers.
Why Elements
Elements is an integrated full-stack app framework and a project server. The project server checks the agent's work as it builds: it type-checks the server and browser code, analyzes the program, applies migrations and runs the tests, then reports the results to the agent. A security mistake, such as calling a server-only function from the browser, is a compile error. The agent reads the report and fixes its own mistakes before it tells you a feature is done. The same checks run on every feature you ask for next.
Run it yourself
- 1 Sign up
Already have an account? Sign in
- 2 Install and run the demo One prompt to paste into your agent.
The prompt
What Claude was given to build this app.
Build an expense report app named slipjar for a company of about thirty people. Two kinds of accounts: employee and approver. An approver can also submit. EMPLOYEE - Add an expense: date, merchant, amount, category (travel, meals, software, supplies, other), a note, and a photo of the receipt. - Group expenses into a report and submit it. - See each report's status and any approver comments. APPROVER - Queue of submitted reports. - Open a report, see each receipt image, approve or send it back with a comment. - Monthly totals by category and by person. Email the employee when a report is approved or sent back, and approvers when one is submitted. Seed two approvers, five employees, and a dozen reports across statuses with receipt images. Show the seeded logins on the sign-in page. Report status updates in real time.