You walk into March knowing tax season is coming, and you walk out of April having spent three weekends rebuilding the year from scratch. The receipts are in your inbox. The 1099s arrive in waves. The brokerage tax forms come late. The charitable donations were on a card you've since closed. The home-office expenses are spread across two folders and a vague memory of which conference you actually deducted last year.

The thing about tax prep is that almost none of the work is hard — it's just *findable*. The pieces all exist. You're not missing the receipts; you just can't find them when your accountant emails on March 18th asking for the dental expenses for the medical-deduction calculation. A vault that holds the year's tax-relevant material in one searchable shape — with the agent pulling specific things on demand — turns tax season from a multi-weekend rebuild into a couple of evenings.

## One vault, one parent page per tax year

In Docapybara, each tax year gets a top-level page: *Tax 2026*. Underneath sit child pages for *Income*, *Deductions*, *Receipts*, *Investments*, *Self-employment* (if relevant), *Charitable*, *Estimates*, and *CPA conversations*.

Pages nest indefinitely, OneNote-style. So *Tax 2026 > Deductions > Medical > [Provider name]* is a valid path. The agent searches across the whole tree regardless of how deep it goes.

For taxpayers with rental property, side hustles, multiple states, or business ownership, additional child pages get added as needed. For most W-2 employees with a few investments, the basic shape covers everything. (For the side-business angle specifically, the [Running a Side Hustle Out of Your Notes App](/guides/personal-life/side-hustle-management-ai-notes/) shape pairs with the tax-season approach — same vault, different lens.)

## Income — the running tally that doesn't surprise you in March

The *Income* page captures what you expect to receive vs. what's actually arrived. For W-2 employees, this is mostly your salary plus any bonuses, RSU vesting, ESPP purchases. For self-employed people, it's invoices paid. For investors, it's interest, dividends, capital gains.

An inline database via the `:::database:::` directive handles the running picture: source, type (W-2, 1099-NEC, 1099-MISC, 1099-INT, 1099-DIV, K-1, etc.), expected amount, received status, document filed.

The agent updates it as forms arrive. *"The K-1 from [partnership] arrived today — mark it received, the amount on box 1 is [X]."* Row updates. When you sit down with your CPA, the agent can pull: *"What income forms am I still waiting on, and what's already in?"* No more March 28th surprise that the brokerage 1099 hasn't shown up yet.

## Receipts — the part that always slips

Receipts are the single biggest leakage point in most people's tax prep. The deductible expenses exist, but they're scattered across email confirmations, paper receipts in a drawer, and the running app you charged the deductible CME to.

The vault shape for receipts is one inline database with date, vendor, amount, category (medical, charitable, business expense, home office, etc.), and a link or attachment to the receipt itself. Drop receipts as PDFs, screenshots, or photos. Docapybara converts uploaded PDFs to markdown via docstrange, so the agent can actually read them — the vendor name and amount are searchable.

For ongoing capture during the year, voice works for the small expenses you'd otherwise forget. End of week, walk for thirty seconds: *"This week, dental copay $80, parking at the conference $40, donation to [organization] $250."* Audio recording in-app gives you a transcript with speaker labels; agent files the entries into the receipts database.

The agent can pull totals at tax time: *"Sum my medical receipts for the year, broken out by category. Flag anything that doesn't have a receipt attached."* Comes back with the totals and the gaps.

## Deductions — the categories that need running notes

Some deductions are too qualitative for a database. The *Deductions* page tree handles them with running notes per category.

**Home office**: square footage of the office vs. the home, the percentage you'd deduct, utility bills (drop the PDFs), internet bills, repairs specifically to the office. The agent can total: *"Sum my home-office utility expenses for the year, applying the percentage I noted."*

**Vehicle**: business miles vs. personal miles, dates and purpose if you're tracking trips, the actual-expenses approach if you're using that. A *Vehicle* page with monthly summaries works.

**Education**: the conference fees, the books, the courses you took to maintain a professional credential. Drop the receipts; note the business purpose.

**Investment expenses**: advisory fees, the investment newsletter subscriptions, the relevant portion of your home office if you actively manage investments.

The agent can summarize at tax time: *"For the deduction categories I track, give me totals and flag anything that needs more documentation."*

## Investments — the cost basis problem and the K-1 wait

Investment-related tax docs arrive in waves and often need cross-referencing. The *Investments* page tree handles the picture: one child per brokerage, one per IRA, one per crypto exchange, one per K-1-issuing partnership.

For each, drop the year-end statements as PDFs. Note any specific-lot identification you did during the year (selling specific shares to manage tax basis). For dividend-reinvestment, the cost-basis tracking matters — note any details your brokerage doesn't capture cleanly.

The agent can pull at tax time: *"For [brokerage], summarize what's in the year-end statement — total interest, total dividends, total capital gains short and long, and any wash sales flagged."* Useful for double-checking the form's numbers and for explaining anything weird to your CPA.

For multi-state or international situations, drop relevant docs on a separate child page so the agent can pull the state-specific picture.

## Self-employment — the Schedule C build

For self-employed work — freelance, side consulting, the LLC you run — *Self-employment* gets its own page tree. Income tracked separately from W-2 income (the database mentioned above just gets a *type* column). Expenses tracked by Schedule C category: advertising, contractors, supplies, professional services, travel, meals, utilities, etc.

For each expense category, an inline database row with date, vendor, amount, and link to the receipt. The agent can total by category: *"Give me the Schedule C expense totals for the year, by category."* That's most of what your CPA needs to file the schedule.

For the home-office and vehicle calculations specifically, the *Deductions* notes feed into Schedule C if you're self-employed. Cross-cutting query: *"For my Schedule C, pull the home-office and vehicle calculations along with the direct business expenses."* The agent assembles the picture.

(For the broader business-side workflow, [How to Use AI Notes for Side Hustle Management](/guides/personal-life/side-hustle-management-ai-notes/) covers the full shape.)

## Estimates, quarterlies, and the charitable trail

Charitable donations need substantiation, especially for non-cash gifts and donations over specific thresholds. The *Charitable* page captures it: organization, date, amount, type (cash, check, credit card, securities, in-kind), receipt or acknowledgment letter (drop the PDF). For donor-advised funds, separately track the contribution year (when you funded the DAF) vs. the grant year (when the DAF distributed to charities) — the deduction year is the contribution year, regardless of distribution timing. The agent can pull the running total: *"What's my charitable giving total for the year, broken out by cash vs. non-cash?"*

For self-employed people, retirees taking RMDs, or anyone with significant non-W-2 income, quarterly estimated tax payments matter. Miss one and the penalty starts running.

The *Estimates* page captures the four quarterly deadlines, the calculated amount, the actual amount paid, the confirmation number, and the safe-harbor calculation. The agent can flag: *"What's the next estimated tax deadline and what amount did I plan to pay?"*

For the safe-harbor calculation specifically, note last year's total tax (the basis for the 100% or 110% safe harbor). The agent can pull: *"Based on last year's tax and this year's income trajectory, am I on track for safe harbor?"*

## A starter shape for the year

A page worth naming before the list: *CPA conversations*. If you work with a CPA, this captures the year-round thread, not just the March panic. Email summaries, phone-call notes, the questions they asked and the answers you sent. After every CPA call, drop a quick voice note. The agent can summarize: *"What's the current state of the Roth conversion conversation, and what's still open?"* Useful when you can't remember what you decided in October. Same shape as the planning conversations in [Planning Your Retirement: A Vault for the Next 30 Years](/guides/personal-life/plan-retirement-ai-notes/) — the conversation-tracking carries directly.

If you're moving from "scattered across email and folders" to a vault, this is what we'd suggest:

- **Tax [year]** — top-level parent
- **Income** — running database
- **Receipts** — running database, drop receipts as they come
- **Deductions** — page tree by category
- **Investments** — page tree by account
- **Self-employment** — Schedule C structure (if relevant)
- **Charitable** — running list with substantiation
- **Estimates** — quarterly tracker
- **CPA conversations** — running thread

That's it. Set up in March, populated as the year goes. By the next March, the year's pre-built. Your accountant emails you with a question, you ask the agent, you have the answer in two minutes instead of two days.

The point isn't to turn taxes into a hobby. It's to make the once-a-year scramble into a small monthly habit. (For the broader work-and-life-in-one-vault case, [Why Your Notes App Should Be the Same App for Work and Life](/guides/personal-life/same-app-work-and-life/) covers it.)

[Try Docapybara free](/accounts/signup/) — start with the *Receipts* database and the *Income* database, and the next time April approaches, the rebuild won't take three weekends.