AutoFileEmail
    IntegrationsSolutionsComparePricingFAQBlog
    Sign inConnect Drive
    1. Blog
    2. Stripe + AWS + Notion Receipts: The Founder's Tax-Time Checklist
    On this page
    The 15 vendors a typical solo founder paysWhere each receipt actually arrives in GmailWhy Gmail buries themWhat sender-domain extraction doesThe printable checklistThe quirky senders that trip people upThe 30-day preview that catches mistakesWhy this matters for actual taxesTL;DR

    Stripe + AWS + Notion Receipts: The Founder's Tax-Time Checklist

    MMitchel Kelonye
    •
    Jun 16
    •
    Startups
    Saas
    Tax Preparation
    Stripe
    Aws

    Stripe, AWS, and Notion receipts: a founder's tax-time checklist in a cozy Studio Ghibli style

    It's the second Saturday in March. You sit down to do the founder version of taxes. You're solo, you're an LLC or sole prop, you take Stripe revenue, and you pay for 15 things every month that all live in your Gmail.

    You start a list. Stripe. AWS. GitHub. Vercel. You get to seven and your brain stalls. Was it Loom or Riverside? Was the Notion bill on the personal card or the business card? Did Anthropic charge you twice in February?

    This is the moment most founders give up and just guess.

    This post is the antidote. The 15 vendors most solo SaaS founders actually pay, the exact email addresses those receipts come from, and how to make sure every single one ends up in a real folder before the next tax season.


    Table of Contents

    • The 15 vendors a typical solo founder pays
    • Where each receipt actually arrives in Gmail
    • Why Gmail buries them
    • What sender-domain extraction does
    • The printable checklist
    • The quirky senders that trip people up
    • The 30-day preview that catches mistakes
    • Why this matters for actual taxes
    • TL;DR

    The 15 vendors a typical solo founder pays

    I pulled this from looking at my own credit card statement and three founder friends' statements. Yours will overlap by 80%.

    Revenue side (1099-K territory):

    1. Stripe - your payouts and fees

    Infra and dev tools: 2. AWS - hosting, S3, RDS 3. Cloudflare - DNS, Workers, CDN 4. Vercel - frontend hosting 5. GitHub - private repos, Actions minutes

    Product and design: 6. Notion - docs, the second brain 7. Linear - issue tracking 8. Figma - design files

    Comms: 9. Slack - if you have a community or contractors 10. Zoom - calls 11. Loom - async video

    AI and APIs: 12. OpenAI (ChatGPT Plus or API) 13. Anthropic (Claude API) 14. ElevenLabs - voice generation, if you make videos

    Email and transactional: 15. Resend or Postmark - sending email from your app

    That's the spec. Fifteen vendors. Roughly $400 to $1,200 in monthly recurring spend if you're a real-deal solo SaaS. Every one of them sends you a receipt by email. Every one of them buries it somewhere.

    Where each receipt actually arrives in Gmail

    This is the thing nobody tells you. Every vendor sends from a slightly different address, and Gmail doesn't group them.

    VendorSender addressSubject pattern
    Stripebilling@stripe.com, noreply@stripe.com"Your invoice from Stripe"
    AWSaws-receipts@amazon.com, no-reply-aws@amazon.com"Amazon Web Services Invoice"
    GitHubsupport@github.com, noreply@github.com"Your GitHub receipt"
    Vercelinvoice+...@vercel.com"Your Vercel Invoice"
    Cloudflarebilling@cloudflare.com"Your Cloudflare Invoice"
    Notionteam@makenotion.com"Receipt from Notion Labs"
    Linearsupport@linear.app"Linear Invoice"
    Figmareceipts@figma.com"Your Figma receipt"
    Slackfeedback@slack.com"Slack invoice"
    Zoomno-reply-zoom@zoom.us"Zoom invoice"
    Loomteam@loom.com"Your Loom receipt"
    OpenAIreceipts+ac_...@stripe.com"Your receipt from OpenAI"
    Anthropicnoreply@anthropic.com"Your Anthropic receipt"
    ElevenLabsteam@elevenlabs.io"ElevenLabs invoice"
    Resendbilling@resend.com"Resend Invoice"

    Two things to notice. First, OpenAI bills through Stripe, so the receipt looks like it's from Stripe but it's an OpenAI charge. Second, Anthropic uses a generic noreply@anthropic.com because they handle billing in-house. Third, AWS uses both aws-receipts@amazon.com and no-reply-aws@amazon.com interchangeably, and they often switch without warning.

    If you've ever tried to set up Gmail filters for these vendors, you've felt the pain. The address strings change. The subject lines change. The display name flips between "Stripe" and "Stripe Billing" and "Stripe, Inc."

    Why Gmail buries them

    Gmail's threading model assumes you want to read emails. Receipts aren't reads. They're file-and-forget.

    When AWS sends you 14 receipts in 14 months, Gmail threads 13 of them under one subject if the subject is identical, hides 12 of them in the collapsed view, and shows you the most recent one only. Your filter that says "label as Receipts" works, but the inbox view still says "Inbox (1) - AWS Receipt" because of the thread collapse.

    Then you search from:aws-receipts has:attachment in March and Gmail returns 9 results when there should be 12. Three are missing because the sender address changed for two months when AWS migrated their billing system. You don't notice until your CPA asks where the August invoice went.

    This isn't theoretical. It's why founders consistently undercount their AWS spend by one or two months at tax time.

    What sender-domain extraction does

    AutoFileEmail flattens all of this. Every email gets reduced to its registrable domain. The folder name is the domain. End of story.

    Some examples of how the extraction handles real-world cases:

    • noreply@aws.amazon.com -> folder amazon.com
    • aws-receipts@amazon.com -> folder amazon.com
    • billing.us@stripe.com -> folder stripe.com
    • receipts+ac_xyz@stripe.com -> folder stripe.com (the OpenAI-via-Stripe charges land here too, which is correct, since the legal vendor on the receipt PDF is OpenAI but the email sender is Stripe; the PDF inside the folder shows OpenAI)
    • noreply@anthropic.com -> folder anthropic.com
    • invoice+12345@vercel.com -> folder vercel.com
    • team@makenotion.com -> folder makenotion.com (Notion's actual corporate domain; the folder name is verbatim)

    Subdomains, prefixes, plus-addressing - none of it matters. The registrable domain wins. Twelve months of AWS bills land in /AutoFileEmail/amazon.com/2026/. Twelve months of Stripe land in /AutoFileEmail/stripe.com/2026/. The thread-collapse problem is gone because every receipt is now a file, not an email.

    The printable checklist

    When March arrives, walk through this list. For each vendor you actually use, click into the corresponding Drive folder and count files. If the count matches your card statement, you're done.

    [ ] /AutoFileEmail/stripe.com/2026/ - count = 12 (monthly fees)
    [ ] /AutoFileEmail/amazon.com/2026/ - count = 12 (AWS)
    [ ] /AutoFileEmail/cloudflare.com/2026/ - count = 12
    [ ] /AutoFileEmail/vercel.com/2026/ - count = 12
    [ ] /AutoFileEmail/github.com/2026/ - count = 12
    [ ] /AutoFileEmail/makenotion.com/2026/ - count = 12
    [ ] /AutoFileEmail/linear.app/2026/ - count = 12
    [ ] /AutoFileEmail/figma.com/2026/ - count = 12
    [ ] /AutoFileEmail/slack.com/2026/ - count = 12
    [ ] /AutoFileEmail/zoom.us/2026/ - count = 12
    [ ] /AutoFileEmail/loom.com/2026/ - count = 12
    [ ] /AutoFileEmail/openai.com/2026/ - count = 12 (or in stripe.com if billed via Stripe)
    [ ] /AutoFileEmail/anthropic.com/2026/ - count = variable (usage-based)
    [ ] /AutoFileEmail/elevenlabs.io/2026/ - count = 12
    [ ] /AutoFileEmail/resend.com/2026/ - count = 12
    [ ] /AutoFileEmail/stripe.com/2026/ - count = 12 (monthly fees)
    [ ] /AutoFileEmail/amazon.com/2026/ - count = 12 (AWS)
    [ ] /AutoFileEmail/cloudflare.com/2026/ - count = 12
    [ ] /AutoFileEmail/vercel.com/2026/ - count = 12
    [ ] /AutoFileEmail/github.com/2026/ - count = 12
    [ ] /AutoFileEmail/makenotion.com/2026/ - count = 12
    [ ] /AutoFileEmail/linear.app/2026/ - count = 12
    [ ] /AutoFileEmail/figma.com/2026/ - count = 12
    [ ] /AutoFileEmail/slack.com/2026/ - count = 12
    [ ] /AutoFileEmail/zoom.us/2026/ - count = 12
    [ ] /AutoFileEmail/loom.com/2026/ - count = 12
    [ ] /AutoFileEmail/openai.com/2026/ - count = 12 (or in stripe.com if billed via Stripe)
    [ ] /AutoFileEmail/anthropic.com/2026/ - count = variable (usage-based)
    [ ] /AutoFileEmail/elevenlabs.io/2026/ - count = 12
    [ ] /AutoFileEmail/resend.com/2026/ - count = 12

    If any folder is missing files, two things to check. First, did you sign up for that vendor mid-year? An eight-month count is correct for a vendor you started using in May. Second, did the vendor change their billing email address? If your amazon.com folder has 9 files and you know AWS billed you 12 times, search Gmail for "AWS invoice" directly and see if any landed at a different sender address. Forward them to AutoFileEmail's address and they'll re-file correctly.

    The quirky senders that trip people up

    A few vendors deserve special mention because their setup confuses people.

    Anthropic. Sends from noreply@anthropic.com for both API billing and Claude Pro subscriptions. The receipts are clean PDFs. Domain extraction nails it: anthropic.com, no prefix gymnastics needed.

    OpenAI via Stripe. OpenAI's API billing routes through Stripe, so the email comes from a Stripe-owned address. The PDF attachment shows OpenAI as the vendor, but the email sender is Stripe. AutoFileEmail files by sender domain, so these end up in stripe.com. If you want them in their own folder, you can manually move the PDFs once a year. Most founders just leave them in stripe.com because the PDFs are clearly labeled OpenAI inside.

    Vercel. Vercel uses plus-addressing (invoice+abc123@vercel.com) so each invoice has a unique sender for tracking. Gmail filters break on this; you'd need a wildcard. Domain extraction strips the plus part and lands everything in vercel.com. No filter setup needed.

    AWS. AWS sends from at least three different addresses depending on which service is billing you (EC2, S3 standalone, Marketplace). All of them are *.amazon.com and all collapse to amazon.com. So your AWS folder has the bill from your main account, the bill from your Marketplace subscription, and the standalone S3 invoice from that side project, all together.

    GitHub. Sometimes GitHub sends invoices, sometimes payment confirmations. Both go to github.com folder. Sponsorships and Actions minutes also land here.

    Notion. Filed under makenotion.com, not notion.so. This is correct - their billing entity is Notion Labs, Inc., and their billing domain is makenotion.com. Verbatim domain wins.

    The 30-day preview that catches mistakes

    When you sign up, AutoFileEmail runs a 30-day historical preview for free. This is the moment to spot vendors you forgot about. Open the preview folder. If it's empty for cloudflare.com and you definitely pay Cloudflare, two possibilities: their billing email goes to a different inbox (work vs personal Gmail), or your Cloudflare receipts don't have PDF attachments (they sometimes link to a download instead).

    Either way, you find out before paying for a Backfill Pack. The preview is the smoke test.

    If the preview catches all 15 vendors, the Tax Year Pack at $29 will catch 12 months of historicals in an afternoon. If it misses three vendors, fix those first - usually it's a forwarding rule or a different inbox - then run the backfill.

    Why this matters for actual taxes

    Schedule C deductions for a solo SaaS founder are dominated by these 15 vendors. Software, hosting, contractor tools. The IRS doesn't ask for them upfront - you just deduct the total - but if they ever do ask, you need the PDFs.

    Founders who hand their CPA a vendor-organized folder save hours of CPA billable time. Founders who hand their CPA "here's my Gmail" end up with the CPA either guessing the totals or charging an extra $200 in admin time to dig through the inbox.

    Either way, the math favors filing.

    TL;DR

    Fifteen vendors. Fifteen folders. One Drive root.

    Connect Gmail and Google Drive once. The folder structure builds itself. Sender domains collapse correctly even for the weird ones (noreply@aws.amazon.com becomes amazon.com, plus-addressed Vercel invoices become vercel.com).

    Print the checklist above, run it once in March, and you'll know in 90 seconds whether your tax-time filing is complete.

    Free for one inbox. No subscription, no per-receipt fees. Two clicks to set up. Then forget about it until you actually need the folders.

    15-vendors-solo-founders-receipts

    Gmail inbox and domain-based folders organizing receipts in a warm Studio Ghibli style

    Gmail thread buries receipts due to threading; a founder looks for receipts

    Printed checklist with 15 vendors checked off for tax-time

    The last time you'll dread tax season.

    Connect Gmail and Drive, watch the 30-day preview file itself, and never think about new email attachments again. Forward filing is free, forever. When tax season comes, grab a Backfill Pack and we'll sweep the rest of your history.

    Connect Drive — free See pricing

    Thanks for reading! If you want to see future content, subscribe to our RSS feed.

    ← Older
    Filing Emails Into Drive: Zapier vs IFTTT vs Purpose-Built
    Newer →
    Your Accountant Doesn't Need OCR. Your Accountant Needs Folders.
    AutoFileEmail

    We don't read your documents. We just file them. Receipts, invoices, statements — sorted into your cloud, automatically.

    Product
    • Pricing
    • FAQ
    • Blog
    • About
    Compare
    • AutoFileEmail vs. Receiptor AI
    • AutoFileEmail vs. Hubdoc
    • AutoFileEmail vs. Dext
    • AutoFileEmail vs. Zapier
    • AutoFileEmail vs. CloudHQ Save Emails to Drive
    Integrations
    • Auto-save Gmail attachments to Google Drive
    • Auto-save Gmail attachments to Dropbox
    • Auto-save Outlook attachments to OneDrive
    • Auto-save Outlook attachments to SharePoint
    • IMAP + Google Drive Integration
    Solutions
    • AutoFileEmail for Freelancers
    • AutoFileEmail for Bookkeepers
    • AutoFileEmail for Landlords — Schedule E ready by April
    • AutoFileEmail for Consultants
    • Tax-Time Receipt Organization
    Legal
    • Privacy policy
    • Terms
    • Security
    © 2026AutoFileEmail · We don't read your documents.PrivacyTerms