https://autofile.email Auto-save every receipt and invoice from Gmail or Outlook into your own Drive folder. Organized by vendor and date. No OCR. No AI. Just files. Thu, 01 Oct 2026 08:50:10 GMT https://validator.w3.org/feed/docs/rss2.html https://github.com/jpmonette/feed en 2026 https://autofile.email/blog/save-gmail-attachments-to-google-drive-automatically https://autofile.email/blog/save-gmail-attachments-to-google-drive-automatically Tue, 05 May 2026 00:00:00 GMT support@autofile.email (Mitchel Kelonye) https://autofile.email/blog/save-outlook-attachments-to-onedrive-automatically https://autofile.email/blog/save-outlook-attachments-to-onedrive-automatically Thu, 07 May 2026 00:00:00 GMT AutoFileEmail, and your CPA gets a clean per-vendor breakdown. That's the whole workflow. Diagrammatic representation of the AutoFileEmail workflow behind the scenes Setup, end to end The actual click-by-click for Outlook + OneDrive: Sign up at autofile.email with your Microsoft account. 30 seconds. Click "Connect Outlook." Microsoft consent screen. Approve Mail.Read (we read mail and download attachments, that's it). Click "Connect OneDrive." Second consent screen. Approve "Have full access to the application's folder." Done. AutoFileEmail starts polling within 30 seconds of you finishing onboarding. If you signed up today, you also get a 30-day historical preview free. Last month's receipts file themselves retroactively without you doing a thing. If you want the last full tax year filed too, buy the $29 Tax Year Pack. One-time payment, no subscription. Backfill runs in the background; you can close the tab. The full setup walkthrough lives on the Outlook + OneDrive integration page. Onboarding steps for AutoFileEmail: sign up, connect Outlook, connect OneDrive, done App folder mode: we cannot see anything else This part matters more than people realize. OneDrive has a permission scope called Files.ReadWrite.AppFolder. It's the narrowest scope Microsoft offers for OneDrive. Translated: AutoFileEmail can create, read, update, and delete files inside /Apps/AutoFileEmail/. We cannot see, list, or touch anything else in your OneDrive. The Microsoft Graph API will refuse if we try. Your family photos, your work docs, your half-finished pitch decks, the Documents folder, the desktop sync, the Personal Vault - all invisible to us. Not "we promise not to look." Literally not in the API surface we have access to. Compare that to Hubdoc, Dext, or any of the OCR-based receipt tools. They want broad inbox access AND broad file access. They scrape every receipt, send it through GPU-backed OCR, and store the parsed line items. The trade is "give us your data, we give you searchable receipts." We don't make that trade. We just file the PDFs Stripe sent you, in the folders your accountant wants to see them in. The /Apps/ prefix in OneDrive is a real-world consequence of this sandbox. If you've ever connected another Files.ReadWrite.AppFolder app, you've already got an Apps folder; AutoFileEmail just adds a sibling subfolder. OneDrive AppFolder mode highlighted with a calm, privacy-focused scene What about M365 work accounts? If your inbox is at a Microsoft 365 work account (yourname@yourcompany.com), there's an extra step: many enterprise tenants block third-party apps by default. The consent screen will say "Approval required" and the connection fails until your IT admin grants tenant or per-user consent. The good news is the scopes we ask for are narrower than what tools like Power Automate, Zapier, or Hubdoc request. Most IT teams approve Mail.Read + Files.ReadWrite.AppFolder without much pushback because the footprint is genuinely small. For solo founders running a single-user M365 tenant (you're the admin), this is just one extra "Consent on behalf of your organization" checkbox during onboarding. Tick it. Done. What we don't do A few things worth being explicit about, because the receipt-filing category is full of tools that quietly do more than you'd expect: No OCR. The PDF in your OneDrive folder is the same PDF Stripe sent. We don't parse line items. We don't extract amounts. We don't categorize. Your accountant's software does that better than any of these tools, and we're not reading your receipts - we're just filing them. No outbound mail. Mail.Read only. We can't send, reply, forward, or mark as read. No per-email metering. The free tier files unlimited new attachments going forward. The Backfill Packs are the only paid product, and they're one-time, not subscription. No Cash App Pay. Standard checkout, Stripe-backed. If you want OCR, your accountant's software does it better than any of these tools. Filing is the part that's actually missing for most people. TL;DR Outlook's native "Save to OneDrive" is a one-click flat dump. Doesn't scale past 50 receipts. Outlook rules can't save attachments. Microsoft's official fix is Power Automate. Power Automate's free tier (750 actions/day) runs out in busy months; Premium is $15/user/month. Vendor-domain routing requires custom expressions that nobody enjoys writing. AutoFileEmail's Outlook + OneDrive setup: two OAuth screens, files land under /Apps/AutoFileEmail/{vendor}/{YYYY}/{MM}/, free for one inbox. App folder mode means we literally cannot see anything else in your OneDrive. Free for one inbox + one cloud. 30-day historical preview included. The $29 Tax Year Pack covers a full year of backfill if you want April's receipts already filed. We don't read your receipts. We just file them. Try it - worst case, you save an hour next April. ]]> support@autofile.email (Mitchel Kelonye) https://autofile.email/blog/how-freelancers-actually-file-receipts https://autofile.email/blog/how-freelancers-actually-file-receipts Fri, 08 May 2026 00:00:00 GMT support@autofile.email (Mitchel Kelonye) https://autofile.email/blog/save-gmail-attachments-to-onedrive-automatically https://autofile.email/blog/save-gmail-attachments-to-onedrive-automatically Fri, 08 May 2026 00:00:00 GMT support@autofile.email (Mitchel Kelonye) https://autofile.email/blog/save-gmail-attachments-to-dropbox-automatically https://autofile.email/blog/save-gmail-attachments-to-dropbox-automatically Mon, 11 May 2026 00:00:00 GMT support@autofile.email (Mitchel Kelonye) https://autofile.email/blog/receipts-for-taxes-3-folders-survive-audit https://autofile.email/blog/receipts-for-taxes-3-folders-survive-audit Tue, 12 May 2026 00:00:00 GMT support@autofile.email (Mitchel Kelonye) https://autofile.email/blog/auto-file-icloud-mail-attachments-via-imap https://autofile.email/blog/auto-file-icloud-mail-attachments-via-imap Wed, 13 May 2026 00:00:00 GMT support@autofile.email (Mitchel Kelonye) https://autofile.email/blog/why-we-dont-ocr-your-receipts https://autofile.email/blog/why-we-dont-ocr-your-receipts Fri, 15 May 2026 00:00:00 GMT support@autofile.email (Mitchel Kelonye) https://autofile.email/blog/gmail-attachments-tax-time-landmine https://autofile.email/blog/gmail-attachments-tax-time-landmine Tue, 19 May 2026 00:00:00 GMT support@autofile.email (Mitchel Kelonye) https://autofile.email/blog/auto-file-pdfs-email-drive-folders https://autofile.email/blog/auto-file-pdfs-email-drive-folders Fri, 22 May 2026 00:00:00 GMT support@autofile.email (Mitchel Kelonye) https://autofile.email/blog/hubdoc-receipt-bank-dext-overkill-solo-founders https://autofile.email/blog/hubdoc-receipt-bank-dext-overkill-solo-founders Tue, 26 May 2026 00:00:00 GMT $25K is non-trivial - what they want is also boring. Original PDF, original sender, date received. The IRS does not care about your line-item extraction. They care that the receipt is genuine and matches the deduction. CPA wants a well-organized Drive folder of receipts The cheaper option We built AutoFileEmail because the gap between "Gmail filters" and Hubdoc is enormous and we kept falling into it. The shape: connect Gmail, connect Drive, every PDF that lands in your inbox files itself into /AutoFileEmail/{vendor}/{YYYY}/{MM}/. No OCR. No accounting integration. No chart of accounts. No line items. It is just a filer. Cost: free for one inbox, forever. Backfill the last few years for $29-99 one-time, depending on how far back you go. That's it. There is no monthly bill. What you give up: line-item extraction. Auto-publish to Xero. Bank feed reconciliation. Things you don't do today and weren't going to start. What you get: a Drive folder you can hand to a CPA. The same Drive folder you'd build manually if you had three weekends to spare. When you actually do need Hubdoc or Dext Honest take. Don't replace these tools with us if: You run an accounting firm. Hubdoc/Dext are correct. Stay there. You manage books for 5+ businesses. Same. You already pay for QuickBooks Online or Xero, you're disciplined about reconciling, and you genuinely want OCR in your workflow. The marginal cost is small for you and the integration is nice. You have 1,000+ receipts a month and need bulk processing. If any of those describe you, this article is not for you and you should keep using what works. When you don't Replace them with a filer (or with us specifically) if: You're solo. Or a 2-3 person team without a dedicated bookkeeper. Your "accounting software" is a spreadsheet plus a CPA in March. You have under ~500 receipts a year, mostly SaaS subscriptions and SaaS payouts. You don't open Hubdoc weekly. You log in twice a year, panic, and click around. Your CPA gets a Drive folder, not a QuickBooks login. That last bullet is the litmus test. If your CPA asks for a Drive folder, you don't need Hubdoc. You need the folder. Where the money buys you? What the trade actually costs you The honest cost of switching from Hubdoc/Dext to a filer is: No more line-item OCR. (You weren't using it.) No more auto-categorization. (Your CPA does this.) No more "the dashboard says I spent $487 on software last month" widget. (Your bank feed already shows that.) You go from a recurring subscription down to $0, or a one-time $29-99 if you want the back years filed. To put real numbers on it: Dext Business lists at $302.50 billed annually, and AutoEntry starts at $13 a month for 50 credits. Hubdoc needs a Xero plan underneath it. (Prices read from each vendor's pricing page on 23 September 2026.) So the saving is somewhere between a couple hundred and several hundred a year, depending which one you are on. Not life-changing. Not nothing either. Roughly a CPA's hourly rate. There's also a privacy angle worth knowing: by not OCRing, we're not building a database of your line items. Why we don't OCR your receipts is a longer story for another day. The bottom line Hubdoc, Dext, and Receipt Bank are well-built tools solving the bookkeeper's problem. The bookkeeper's problem is not your problem. Your problem is: PDFs land in Gmail, they need to live in Drive, organized so a CPA can find them. That is a filer's job, not an accounting platform's job. If you are weighing up the specific tools, there is a full list of Dext alternatives, a Dext vs AutoEntry breakdown with current pricing, and a side-by-side against Dext. And if the actual pain is that Gmail loses your receipts, that is the tax-time landmine. If you're a freelancer or solo founder, the tax-time workflow is built around exactly this pattern. Connect Gmail in 30 seconds. Free for one inbox. No per-receipt fees. No monthly bill. Try it. If you decide later you do want OCR and a chart of accounts, Hubdoc will still be there. They have lots of customers. None of them are you. ]]> support@autofile.email (Mitchel Kelonye) https://autofile.email/blog/receipt-apps-data-privacy-ranked https://autofile.email/blog/receipt-apps-data-privacy-ranked Fri, 29 May 2026 00:00:00 GMT support@autofile.email (Mitchel Kelonye) https://autofile.email/blog/drive-folder-structure-accountant-wants https://autofile.email/blog/drive-folder-structure-accountant-wants Tue, 02 Jun 2026 00:00:00 GMT Bank fees (or fee revenue offset, depending) aws.amazon.com/ -> Cloud hosting notion.so/, linear.app/, figma.com/, cursor.so/ -> Software & subscriptions delta.com/, marriott.com/ -> Travel doordash.com/, ubereats.com/ -> Meals (with caveats) legalzoom.com/, gusto.com/ -> Professional services Five minutes, the CPA has a category total. Versus 45 minutes opening 200 files in a flat folder to figure out which vendor each one came from. That 40-minute delta is what you're paying for when you pay your CPA hourly. Or what you're forcing them to eat if you have a flat-rate engagement, which they remember next year when they quote you. When the structure breaks down A few honest edge cases. Vendors with subdomains. noreply@billing.stripe.com and notifications@stripe.com are the same vendor. AutoFileEmail collapses both to stripe.com so the folder count stays sane. If you build this manually, do the same thing. Receipts with no PDF. Some vendors send receipts as inline HTML in the email body. We don't catch those today (no attachment to file). For those, your options are: forward to a dedicated label and screenshot to PDF later, or pester the vendor to email actual PDFs. Joint personal and business. If you use one Gmail for both, expect a personal-vendor.com folder mixed in with the business ones. Worth setting up a rule (or a separate inbox) before you backfill years of data and discover your Netflix receipts in your tax folder. Vendors that change names. AWS sends from amazon.com. Apple sends from apple.com. Google sends from a few subdomains, all collapsing to google.com. If a vendor rebrands (Twitter to X, Receipt Bank to Dext) the folder name will reflect whichever domain they used. Your CPA can handle this; they've seen worse. What your CPA does NOT want Things to skip: A spreadsheet alongside the folder, especially one you made the night before. Your categorizations will be wrong (per the chart of accounts they actually use). They will ignore the spreadsheet. Every receipt in one giant folder, even if it's named neatly. Sub-folders by category ("Software", "Travel"). Useful for you, in your way. Not useful for the CPA. Annotated PDFs with your handwritten notes. Pristine originals are what survives an audit. A Hubdoc dashboard login. They have their own software. They don't want yours. If you've been [paying for Hubdoc or Dext and your CPA still asks for a folder anyway, that's the signal that the OCR was for somebody else. How to get there from here If you're starting from a graveyard folder, two paths: Path 1: Manually. Pick a free Saturday. Sort by sender. Drag files into vendor folders. Sort by date. Drag into month folders. It will take 4-8 hours per tax year. Doable for a single year if you're organized. Path 2: Automatically. Connect Gmail and Drive to AutoFileEmail. Forward filing handles the future. The Backfill Pack ($29 for one tax year, $59 for three years, $99 lifetime) walks the inbox and produces this exact structure for years past. The 3-Year Pack typically catches what an audit letter asks for. (Detailed walkthrough: backfill 3 years in an afternoon.) Either way, the destination is the same. The folder structure is the deliverable. The bottom line Your accountant doesn't want OCR. They don't want a dashboard. They don't want your spreadsheet. They want a Drive folder, organized by year, then by vendor, then by month, with the original PDFs inside. That's it. You can build that folder by hand once a year, hating it. Or you can wire up auto-filing and have the folder maintain itself. If you're a freelancer, the tax-time workflow is built around exactly this. Connect Gmail, get the folder structure, hand it to your CPA. Free for one inbox. The folder is yours forever, even if you cancel. Try it. Worst case you save your accountant 40 minutes and yourself a passive-aggressive email. ]]> support@autofile.email (Mitchel Kelonye) https://autofile.email/blog/gdpr-one-person-businesses-receipts https://autofile.email/blog/gdpr-one-person-businesses-receipts Fri, 05 Jun 2026 00:00:00 GMT support@autofile.email (Mitchel Kelonye) https://autofile.email/blog/backfill-3-years-receipts-afternoon https://autofile.email/blog/backfill-3-years-receipts-afternoon Tue, 09 Jun 2026 00:00:00 GMT stripe.com). Compute the target Drive path: /AutoFileEmail/stripe.com/2024/03/. Create the folder if it doesn't exist (cached, so we don't re-create on every file). Upload the attachment with a date-prefixed filename. Record (account_id, message_id, filename) in our metadata table for dedup. Move on. The dedup index is the part that matters when forward-filing is also running. If a backfill job and a forward-filing job both encounter the same email, only one writes the file. No duplicates. Step-by-step setup for the 3-Year Backfill Pack workflow The IRS angle If you're reading this article because of an IRS letter, a few things to know: The IRS does not care about your folder structure. They care that the receipt is genuine, matches a transaction in your bank or card statement, and corresponds to the deduction you took. What they want to see: original PDFs from the vendor, with the vendor's name and date visible. The PDFs we file are bit-for-bit identical to what the vendor sent. They're as audit-ready as the originals. What they want NOT to see: edited PDFs, "summary" spreadsheets in place of receipts, OCR'd text without the original. The original PDF is the receipt. Anything derived from it is supplementary. You don't need to print these. You don't need to physically organize anything. A Drive folder shared with your accountant (who shares it with the IRS via their portal, if requested) is the modern audit-response format. The bottom line Three years of receipts is a one-afternoon problem if you have the right tool and a $59 budget. It's a three-day problem if you do it manually. The receipts already exist in your Gmail. You don't have to find them - they're already there. You just need them to land in the right folders. That's a filing job, not an extraction job, not an OCR job. If you're staring at an audit letter, or just at January's "this is the year I'll be organized" feeling, pick a Backfill Pack and run it. It's $29 for one tax year, $59 for three years, $99 for everything to ever exist. For the ongoing job after the backfill finishes: forward filing is free for one inbox, keeps the structure current as new receipts arrive. The freelancer workflow is built around this loop. Worst case: it's an afternoon. Best case: it's the difference between a calm IRS response and a panic. ]]> support@autofile.email (Mitchel Kelonye) https://autofile.email/blog/filing-emails-drive-zapier-ifttt-vs-purpose-built https://autofile.email/blog/filing-emails-drive-zapier-ifttt-vs-purpose-built Fri, 12 Jun 2026 00:00:00 GMT "Upload File in Google Drive" action. This works. For one folder. The problem: Zapier's Drive action requires you to pick a folder. A specific folder. By name. So one Zap files everything to the same folder. To file by sender domain, you need: A trigger that filters by sender (or you handle all senders in one Zap). A Code or Formatter step that extracts the registrable domain from the email address. Another step that builds the folder path. A Find/Create Folder step (multiple, one per folder level). The upload step. That's a 5-7 step Zap. Per attachment processed. Zapier pricing (May 2026): Free: 100 tasks/month, 5 Zaps. A "task" is each step that fires. Starter: $19.99/mo, 750 tasks. ~1 user. Professional: $49/mo, 2,000 tasks. Multi-step Zaps unlocked at full feature parity. Team: $69/mo+, more tasks. Math: A 6-step Zap processes 100 attachments and burns 600 tasks. At Professional pricing, you've used 30% of your monthly tasks for 100 receipts. A solo founder with 50 receipts/month is at the Starter tier minimum, more realistically Professional once you have multiple Zaps for different jobs (CRM, Slack, etc.). Annual cost: $239-588. What it actually does well: Once configured, runs reliably. Zapier's reliability is excellent. They've solved the "what if a step fails halfway through" problem. What it doesn't: Auto-discovery of new vendors. If a vendor you've never received from sends a receipt, your Zap either dumps it in a default folder, fails silently, or you've coded the domain-extraction logic well enough to handle it. Most users don't. Studio Ghibli-inspired scene of a person evaluating automation options to file Gmail attachments into Drive by domain and date Option 2: IFTTT Same shape, different package. IFTTT's "Gmail attachment to Drive" applet works for the simple case. The complex case (sender-domain folder hierarchy) is harder than Zapier because IFTTT's filter logic is weaker. Pricing (2026): Free: 2 applets. Yes, two. The free tier was deprecated. Pro: $3.99/mo, 20 applets, faster polling. Pro+: $14.99/mo, unlimited applets, custom queries. Annual: $48-180. What it does well: Dirt cheap. Good for simple "if X then Y" automation. What it doesn't: Limited filter logic. No "extract domain from email address" without external scripting. No "build folder path" without help. You'll end up with everything in one folder again. For receipt filing specifically, IFTTT's ceiling is too low. Skip. Zapier workflow planning for Gmail-to-Drive with multi-step logic in a warm Studio Ghibli style Option 3: Microsoft Power Automate If you're an M365 user, this is the "free with your existing subscription" option. Power Automate has a Gmail connector and a Drive connector. (Also OneDrive, naturally.) You can build a "when new email arrives" flow with attachment handling, condition logic, and folder routing. Pricing: Free with M365 Business plans (capped at certain action types, called "premium connectors"). Per-user plan: $15/mo for premium connectors. The free tier actually does cover most receipt-filing scenarios if you're routing to OneDrive. Annual: $0-180. What it does well: Real conditional logic. You can write a flow that extracts the domain, builds a path, creates folders, and uploads. It's possible. What it doesn't: Building that flow takes 2-4 hours. The flow editor is powerful but the UX is corporate-Microsoft, not consumer-friendly. You will spend an evening on this. Once built, runs well. But you're maintaining a flow that breaks if Microsoft renames an action (which they do). For people already in the M365 ecosystem and willing to spend a Saturday, Power Automate is legit. For everyone else, it's overkill. Power Automate flow diagram for Gmail attachments to Drive with domain-based folders Option 4: Google Apps Script Free. Powerful. Yours forever. Apps Script lets you write JavaScript that runs against Gmail, Drive, and most Google APIs. You can write a script that: Searches Gmail for messages with attachments (filter by date, sender, label, whatever). Iterates each message. Pulls attachment metadata. Computes the target folder path. Creates folders as needed. Saves the attachment. Logs what it did. In about 80 lines of JS. Genuinely. Pricing: $0. What it does well: Free, deeply customizable. If you're a developer, this is the "right" answer for ad-hoc filing. What it doesn't: 6-minute execution timeout per run. If you trigger on a backlog, you have to chunk. Quota limits on Drive API (1 billion calls/day across all Google users, per-user limits much lower). For a working inbox, fine. For a backfill of 10,000 emails, you'll hit per-user quotas mid-run and have to retry. Trigger reliability. The "every 5 minutes" trigger can silently stop firing. You won't notice until tax time. OAuth refresh tokens expire if the script doesn't run for 6 months. You'll come back to "your script needs reauthorization" emails. No UI. You're maintaining code in Google's editor. For a developer with 4 hours and willingness to maintain it: legitimate option. For everyone else: a slow-motion abandonment in 8 months. Illustration of a purpose-built filer AutoFileEmail filing receipts automatically Option 5: A purpose-built filer (us, but also the category) A purpose-built filer is built around exactly this job. It knows what an "email attachment" is, it knows what a "registrable domain" is, it knows that you want a hierarchical folder structure, and it doesn't make you wire up the steps. You connect Gmail. You connect Drive. It runs. AutoFileEmail specifically: Free: 1 inbox, forward filing forever, 30-day historical preview on signup. Backfill Packs (one-time): $29 for one tax year, $59 for three years, $99 lifetime. No monthly fee for the basic case. Pro tier ($14.99/mo) coming with multi-inbox, post-MVP. Annual cost for a typical solo founder: $0-99 once. What it does well: The exact job, no configuration. Auto-discovers new vendors. Auto-creates folders. Survives Gmail API hiccups. Logs what it filed. What it doesn't: This narrow job. We do not move files between Slack and Trello. We don't watch your CRM. We don't hook into your podcast feed. If you wanted that, you wanted Zapier. Illustration of a purpose-built filer AutoFileEmail filing receipts automatically The honest comparison table | Tool | Setup time | Annual cost | Auto-discovers vendors | Works without coding | |------|-----------|-------------|------------------------|----------------------| | Zapier | 1-2 hours | $240-590 | Maybe (depends on Zap) | Yes | | IFTTT | 30 min | $48-180 | No | Yes | | Power Automate | 2-4 hours | $0-180 | If built well | Sort of | | Apps Script | 4+ hours | $0 | Yes | No | | AutoFileEmail | 90 seconds | $0-99 once | Yes | Yes | Where Zapier still wins Worth being clear: Zapier is a great product for what it does. It just isn't the right product for "file every receipt that lands in my inbox." Zapier wins for: Cross-system workflows. "When a Stripe payment succeeds, post to Slack and create a Trello card and update Notion." Logic across many tools. Zapier connects to 6,000 apps. AutoFileEmail connects to email and cloud storage. Custom triggers. RSS feeds, webhooks from arbitrary services, custom HTTP endpoints. Zapier eats this for breakfast. CRM integrations. AutoFileEmail will not put a row in your HubSpot. Zapier will. If you're building a multi-app automation, Zapier is the right hammer. For the specific receipt-filing job, a purpose-built filer is faster, cheaper, and stays out of your way. The same way a CSV-to-database tool is better than writing a Zapier zap to do the import. Where Power Automate is genuinely competitive If you're already on M365, Power Automate is the closest competitor for the receipt-filing use case. Free with your subscription, capable enough. The trade is time. You spend 2-4 hours building a flow that does what AutoFileEmail does out of the box. If your hourly value is high, that's expensive labor. If you enjoy building flows, it's a Saturday well spent. For Outlook users specifically, Power Automate also has the advantage of being a Microsoft product talking to a Microsoft email service. Fewer auth surprises. (AutoFileEmail Outlook+M365 support is on the roadmap. Today, the working integration is Gmail+Drive. The other connectors are coming, but if you need Outlook today, Power Automate is your stop-gap.) The full integrations roadmap lives at /integrations. The "I'll just write a script" trap The first version takes a weekend. It works. You're proud. Six months later you have 200 lines of code, a lurking double-file bug, and a trigger that quietly stopped firing when you rotated your Google password. This is the gravity of side projects. They start as 80-line scripts and become maintenance burdens. The maintenance never makes it to your calendar. (More on this trade-off in auto-filing PDFs.) The bottom line Each tool has a job: Zapier: cross-system workflows where you need 6,000 connectors. IFTTT: cheap, simple, two-action automations. Power Automate: M365 users who want a flow they own and maintain. Apps Script: developers who like maintaining code. AutoFileEmail: the specific receipt-filing job, no setup, no monthly fee. For the narrow job of "receipts from email into Drive folders," a purpose-built filer is the cheapest, fastest, lowest-overhead option. Connect Gmail in 30 seconds. Free for one inbox. The structure is the structure your accountant wants. The cost is zero unless you backfill years of history. For everything else, go pick the right tool for that job. Zapier and Power Automate are excellent. They just aren't built for this. If you're already on a tax-time deadline, the 3-Year Backfill Pack walks the inbox once and produces the same folder structure forward-filing maintains. Try the filer. If it doesn't fit, the Zap will still be there. None of these tools mind if you switch. ]]> support@autofile.email (Mitchel Kelonye) https://autofile.email/blog/stripe-aws-notion-receipts-founders-tax-checklist https://autofile.email/blog/stripe-aws-notion-receipts-founders-tax-checklist Tue, 16 Jun 2026 00:00:00 GMT 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 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 ]]> support@autofile.email (Mitchel Kelonye) https://autofile.email/blog/accountant-doesnt-need-ocr-needs-folders https://autofile.email/blog/accountant-doesnt-need-ocr-needs-folders Fri, 19 Jun 2026 00:00:00 GMT support@autofile.email (Mitchel Kelonye) https://autofile.email/blog/what-irs-needs-from-receipts https://autofile.email/blog/what-irs-needs-from-receipts Tue, 23 Jun 2026 00:00:00 GMT support@autofile.email (Mitchel Kelonye) https://autofile.email/blog/gmail-filters-for-receipts-5-to-set-today https://autofile.email/blog/gmail-filters-for-receipts-5-to-set-today Fri, 26 Jun 2026 00:00:00 GMT Settings (gear icon) -> See all settings -> Filters and Blocked Addresses -> Create a new filter. Paste the from: query, check the "Has attachment" box, hit "Create filter," then check "Apply label" and pick or create Receipts/SaaS. The good: every email from any of these vendors with an attachment now lives under one label. Searching label:Receipts/SaaS shows all your SaaS receipts in one stream. The bad: you have to keep the from: list current. New vendors don't appear. Vendors who change their billing email address (AWS does this every 18 months or so) silently stop matching the filter. You'll find out next March when there's a gap in your records. Filter 2: subject-line catch-all A broader net for invoices and receipts that don't come from your known vendor list. subject:(invoice OR receipt OR payment OR billing OR "your order") has:attachment -from:(linkedin.com OR pinterest.com OR meetup.com) Action: apply label Receipts/Pending. Skip inbox optional. The exclusions matter. LinkedIn sends "your invoice for the LinkedIn ad" emails that are not your normal SaaS bills. Pinterest sometimes uses "receipt" in marketing subject lines. Meetup occasionally sends invoice-themed promotional emails. Excluding these keeps your Receipts/Pending label clean. The good: catches new vendors automatically. A new tool you signed up for that sends "invoice for \tool name]" lands here, even if you forgot to update Filter 1. The bad: false positives. Marketing emails with "receipt" in the subject. Confirmations that aren't bills. You'll still spend 2 minutes a week reviewing the label. Inbox view with subject-line catch-all Gmail filter for invoices/receipts Filter 3: annual subscription renewals Annual subs are the silent expense killer. They charge once a year, you forget about them, the receipt buries itself, and you can't find it in March. subject:("annual" OR "yearly" OR "renewed" OR "renewal" OR "subscription renewed") has:attachment Action: apply label Receipts/Annual. Mark as important. The good: annual receipts get extra visibility. Marking important means they show up in your priority inbox. You're less likely to miss one. The bad: you still need Filter 1 or Filter 2 to catch the email in the first place if the vendor doesn't put "annual" in the subject. Belt and suspenders: this filter chains with the others. Annual subscription renewal receipts organized with a Gmail filter Filter 4: dynamic from-list builder This is the trick most Gmail-power-users discovered the hard way. When you find a new vendor invoice in your inbox, instead of editing Filter 1 by hand, do this: Open the invoice email. Click the three-dot menu next to the date. Choose "Filter messages like these." Gmail pre-fills from:billing@newvendor.com. Modify the from to use the registrable domain, not the specific email: change billing@newvendor.com to *@newvendor.com (Gmail accepts wildcard-domain matching in some contexts; for older accounts use just newvendor.com). Add has:attachment. Create the filter, apply label Receipts/SaaS. You're now up to N filters, one per vendor, each labeled the same way. This is more reliable than the OR-stuffed Filter 1 because each vendor has its own dedicated rule, and Gmail won't silently miss one if the OR query gets too long. Gmail has a hard cap of about 1500 filters per account. You're not going to hit it. The good: durable, granular, easy to debug if one vendor stops appearing. The bad: takes effort to maintain. You're doing the receipt-app's job, manually, in Gmail. Dynamic from-list builder workflow for Gmail filters Filter 5: never-spam transactional emails The single most-frustrating filter problem: Gmail occasionally marks legitimate vendor receipts as spam. New vendor, low sender reputation, generic subject line, suspicious-looking link in the email body. Gone. Fix: from:(stripe.com OR aws.amazon.com OR github.com OR vercel.com OR ...) Action: never send to spam, never mark as important (so it doesn't crowd your priority inbox), apply label Receipts/SaaS. This filter overrides Gmail's spam classifier for known senders. It does not protect against phishing pretending to be those senders, but it does prevent the legitimate receipts from being filtered out. The good: no more "where's my AWS bill" panic. The bad: same maintenance burden as Filter 1. Keep the list current. Never-spam transactional emails filter preventing legitimate receipts from being marked as spam This is the catch: filters don't actually file Here's where the post pivots. You've now set up 5 to 20 Gmail filters. Every receipt is correctly labeled. Your Receipts/SaaS label has 130 emails in it. Now: it's March. Your CPA emails you. "Send me your 2025 receipts." What do you do? You open label:Receipts/SaaS. You see 130 emails. You click the first one. You click the attachment. You click "Save to Drive" or download. You repeat for the second email. And the third. 130 emails. 90 seconds each, including renaming the file so it's not called invoice.pdf and adding it to the right folder. That's 195 minutes. Three and a half hours. Filters labeled the emails. They didn't file the attachments. The attachments still live inside the email body, and you have to extract them one by one. This is the gap nobody tells you about when they say "just use Gmail filters." What actual filing looks like The thing you actually want is: when an email with an attachment arrives, save the attachment to the right folder in Drive automatically. No manual extraction. No "save to Drive" clicks. That's what AutoFileEmail does. The setup is one connection (Gmail OAuth read-only) plus one connection (Drive drive.file scope). After that, every new email with a PDF attachment gets the PDF dropped into /AutoFileEmail/{sender-domain}/{year}/{month}/. You don't need any of the five filters above. The sender-domain logic is built in, so AWS bills go to amazon.com, Stripe bills go to stripe.com, regardless of which billing address the vendor uses. You also don't need the annual-renewal filter because every receipt lands in the year-and-month folder it was sent in. Annual subs hit December (or wherever the renewal lands), and they're trivial to find next year. The only filter you really need: has:attachment AND from:(*) -> let AutoFileEmail handle it Which is to say, no filter. Just connect [Gmail to Drive automatically and stop manually labeling things. When Gmail filters still make sense To be fair, Gmail filters aren't useless. They make sense if: You don't want a third-party app reading your Gmail and you're committed to manual filing. You only have 5 to 10 vendors and the maintenance is trivial. You're using filters for non-receipt purposes (newsletters, project tags, etc.) and adding receipts is incremental. If any of those describe you, set up filters 1, 2, and 5 above. Skip the others - they're high-maintenance, low-value. If you're filing receipts, the Gmail filter approach hits a wall. Filters label, but they don't extract attachments. Filing means extracting. TL;DR Five Gmail filters get your receipts labeled and organized inside Gmail. They don't move attachments to Drive. They don't create folders. They don't reduce the manual work of extracting PDFs in March. If your goal is "every receipt PDF lives in a Drive folder, organized by vendor and year, with zero ongoing effort," you need an actual filing tool - not a labeling system. AutoFileEmail does the filing. Free for one inbox. Two-click setup. The five-filter Gmail system becomes a zero-filter system, because the filing happens automatically and you don't need labels to find anything. Set the filters if you like. Then connect Gmail and Drive once, and watch the labels become irrelevant. ]]> support@autofile.email (Mitchel Kelonye) https://autofile.email/blog/1099-vs-w2-filing-receipts-both https://autofile.email/blog/1099-vs-w2-filing-receipts-both Tue, 30 Jun 2026 00:00:00 GMT support@autofile.email (Mitchel Kelonye) https://autofile.email/blog/ai-reads-invoices-feature-in-search-of-problem https://autofile.email/blog/ai-reads-invoices-feature-in-search-of-problem Fri, 03 Jul 2026 00:00:00 GMT support@autofile.email (Mitchel Kelonye) https://autofile.email/blog/receipt-retention-rules-by-country https://autofile.email/blog/receipt-retention-rules-by-country Tue, 07 Jul 2026 00:00:00 GMT support@autofile.email (Mitchel Kelonye) https://autofile.email/blog/apple-wallet-receipts-drive-workaround https://autofile.email/blog/apple-wallet-receipts-drive-workaround Fri, 10 Jul 2026 00:00:00 GMT support@autofile.email (Mitchel Kelonye) https://autofile.email/blog/never-charge-per-email-scanned https://autofile.email/blog/never-charge-per-email-scanned Tue, 14 Jul 2026 00:00:00 GMT support@autofile.email (Mitchel Kelonye) https://autofile.email/blog/icloud-mail-drive-missing-automation https://autofile.email/blog/icloud-mail-drive-missing-automation Fri, 17 Jul 2026 00:00:00 GMT support@autofile.email (Mitchel Kelonye) https://autofile.email/blog/outlook-onedrive-freelancer-filing-setup https://autofile.email/blog/outlook-onedrive-freelancer-filing-setup Tue, 21 Jul 2026 00:00:00 GMT support@autofile.email (Mitchel Kelonye) https://autofile.email/blog/dext-alternatives-for-one-person-businesses https://autofile.email/blog/dext-alternatives-for-one-person-businesses Wed, 23 Sep 2026 00:00:00 GMT support@autofile.email (Mitchel Kelonye) https://autofile.email/blog/dext-vs-autoentry-for-solo-operators https://autofile.email/blog/dext-vs-autoentry-for-solo-operators Wed, 23 Sep 2026 00:00:00 GMT support@autofile.email (Mitchel Kelonye)