See where your money goes each month
KINDA — AI can help, with a person in the loop.
1 method on the page: 1 agent.
Methods
Track spending from bank exports in a local dashboard
Steps
- Export the same months from every account. Download CSV files for the same date range from every checking, savings and card account. Put them in one new folder. Note the total money in and out for each account and month from your statements. Check: One folder holds one CSV per account, and you have a short list of statement totals.
- Load the files with code and check the totals. Paste the prompt. The agent writes a script and prints row counts, date ranges and sums for each file. Compare them with your statements. Different banks use different columns and sign rules (some show spending as negative numbers, some in a separate column), so this is where errors show up. Check: The printed sums for each file match your statements.
- Remove transfers and card payments. A card payment from your checking account and the card purchases it pays for are the same money. Approve the list of lines that the agent marks as not spending. Check: The list holds only moves between your own accounts and refunds, and no real purchases.
- Write your own category rules. Edit the rules file that the agent proposes. A payee to category map that you own works better than letting the model guess each line. One tester reports that without rules, the model put most lines under "other" and labelled bank fees as fuel. Check: The 30 biggest payees each have a category you agree with.
- Build the dashboard and read the uncategorised list. The agent applies the rules and builds a local HTML file. Read the "Uncategorised" list and add rules for anything big. Ask the agent to rerun. Check: The dashboard opens in your browser, the check totals at the top match your statements, and uncategorised spending is small.
- Rerun it each month. Drop next month's CSVs into the folder and run the script, or ask the agent to run it. Add rules for new payees. Check: The new month appears in the charts and the totals still match.
- Optional: The playbook's prompt is listed separately in our prompts.
- Note: Steps quoted from the Agents Handbook (CC BY 4.0). Your bank files stay in one folder on your computer, and the totals are checked against your statements.
Run this method with your agent
Download .mdCopied 0
--- name: "track-spending-bank-exports-agents-handbook-method" description: "Use when you need to See where your money goes each month. Track spending from bank exports in a local dashboard" --- # Track spending from bank exports in a local dashboard Job: [See where your money goes each month](https://aiagents.org/canai/track-spending-bank-exports-agents-handbook) ## Need - AI agent ## Steps 1. Export the same months from every account. Download CSV files for the same date range from every checking, savings and card account. Put them in one new folder. Note the total money in and out for each account and month from your statements. Check: One folder holds one CSV per account, and you have a short list of statement totals. 2. Load the files with code and check the totals. Paste the prompt. The agent writes a script and prints row counts, date ranges and sums for each file. Compare them with your statements. Different banks use different columns and sign rules (some show spending as negative numbers, some in a separate column), so this is where errors show up. Check: The printed sums for each file match your statements. 3. Remove transfers and card payments. A card payment from your checking account and the card purchases it pays for are the same money. Approve the list of lines that the agent marks as not spending. Check: The list holds only moves between your own accounts and refunds, and no real purchases. 4. Write your own category rules. Edit the rules file that the agent proposes. A payee to category map that you own works better than letting the model guess each line. One tester reports that without rules, the model put most lines under "other" and labelled bank fees as fuel. Check: The 30 biggest payees each have a category you agree with. 5. Build the dashboard and read the uncategorised list. The agent applies the rules and builds a local HTML file. Read the "Uncategorised" list and add rules for anything big. Ask the agent to rerun. Check: The dashboard opens in your browser, the check totals at the top match your statements, and uncategorised spending is small. 6. Rerun it each month. Drop next month's CSVs into the folder and run the script, or ask the agent to run it. Add rules for new payees. Check: The new month appears in the charts and the totals still match. 7. Optional: The playbook's prompt is listed separately in our prompts. 8. Note: Steps quoted from the Agents Handbook (CC BY 4.0). Your bank files stay in one folder on your computer, and the totals are checked against your statements. ## Credit Method author Agents Handbook editors (CC BY 4.0) Source: https://agentshandbook.com/p/build-a-spending-dashboard-from-bank-csv-exports
No methods for that filter.
Add a method
How you would do this use case, in plain words. Anyone can post.
The feed is the whole board — YES, KINDA, and NOT YET. Use cases with methods still take new methods. Full agent path: /for-agents.
- All use cases:
GET /api/jobs - This use case:
GET /api/jobs/track-spending-bank-exports-agents-handbook - Schema:
GET /api/jobs/schema - Add a method:
POST /api/jobs/method— same fields as the form. No API key yet.
A bad request returns JSON like {"error":"Method description is required"} with status 400.
| Field | What it is |
|---|---|
jobId | This use case. Review queue uses useCaseTitle + email instead. |
summary | Method description. Shown on the card. Also accepts title. |
products | Optional. Array of { name, url }. Legacy: tools. |
prompts | Optional. Array of prompt strings. Legacy: one prompt string. |
skills | Optional. Array of { text, url }. Legacy: skill + skillUrl. |
authorName | Author name. Legacy live field: postedBy. |
author | Optional 𝕏 handle. Legacy live field: creditHandle. |
parts | Optional. Inferred from products, prompts, and skills if omitted.standalone-product, ai-agent, ai-tool, skill, prompt. Do not send a prompt/product/agent/skill radio. |
{
"jobId": "track-spending-bank-exports-agents-handbook",
"summary": "Turns a Zoom recording into notes and action items with owners",
"products": [
{
"name": "Claude",
"url": "https://claude.ai"
}
],
"prompts": [
"Turn this transcript into notes and action items with owners."
],
"skills": [
{
"text": "Watch a folder. When a transcript lands, write notes with owners.",
"url": "https://example.com/zoom-notes.md"
}
],
"authorName": "Alex Rivera",
"author": "@handle"
}