Notion can model almost anything, including an HSA receipt tracker. The question is whether you want to maintain the thing you built for the next thirty years.
Short answer: A Notion build is a real option and some people will genuinely prefer it. Two caveats worth naming: exports of file-heavy databases are awkward, and the system only stays correct as long as you keep maintaining the schema you invented.
| Feature | SaveMyHSA | Notion |
|---|---|---|
| Purpose-built for HSA receipts | ✅ Yes | ❌ No |
| Structured fields (provider, patient, service date, amount) | ✅ Yes | ⚠️ You build it |
| Tracks reimbursed vs. unreimbursed | ✅ Yes | ⚠️ You build it |
| Works when you never swipe the HSA card | ✅ Yes | ✅ Yes |
| Survives changing HSA custodians | ✅ Yes | ✅ Yes |
| Built for 20+ year retention | ✅ Yes | ⚠️ Depends on Notion |
| Search by patient, year, or category | ✅ Yes | ✅ Yes |
| One-click export (files + CSV index) | ✅ Yes | ⚠️ Messy |
| Shows what unreimbursed receipts are worth later | ✅ Yes | ⚠️ You build it |
| Holds your HSA money and investments | ❌ No | ❌ No |
| If you… | Use |
|---|---|
| Live in Notion already and enjoy building | Build it there |
| Want it to just work | A purpose-built tool |
| Worry about a decades-long dependency | Whatever you use, export regularly |
Yes, as file attachments — though large archives get slow and exports get unwieldy.
What matters is the underlying documents, not the tool. Make sure you can actually export them.
Abandonment. Custom systems decay when the person maintaining them gets busy.