How to automate downloading invoices in 2026: 5 methods compared, from email rules to AI agents
To automate downloading invoices, you have five options: email rules, an invoice collection tool, the vendor’s API, a browser script you write yourself, or an AI agent that opens each billing portal for you. Email rules are free but only catch vendors that attach a PDF. The other four reach the billing portal, and the difference between them is who signs in, where, and who fixes the script when the portal changes.
This guide compares the five methods for a team that pays a dozen or more SaaS tools, and shows the last one step by step with Reduck.
Why invoice downloads stay manual
At month-end, your accountant asks for every invoice. For most teams, that means someone signs in to each tool, finds the billing page, downloads the PDF, renames it and sends it on. It is slow for four reasons:
- The invoice is often not in your inbox. Many vendors send a payment notice and keep the PDF behind a login. Notion and Cursor, for example, send no invoice by email at all.
- Every billing portal is different. Each vendor puts its invoices in a different menu, with a different download button. Some show one month at a time, some split one bill in two (a ChatGPT plan and the OpenAI API are billed apart).
- Only some people can see billing. On team plans, only an owner or a billing admin opens the invoice list, so the task falls on the same person every month.
- One missing invoice holds up the close. With 15 subscriptions, it is easy to forget one.
What a good invoice automation must do
Whatever the method, check it against this list:
- Reach invoices that are not emailed. This is most of the work.
- Sign in safely. Billing portals hold payment data. The fewer places your passwords and two-factor codes are stored, the better.
- Get past bot detection. Many portals sit behind Cloudflare or a similar service, which blocks browsers it thinks are automated.
- Survive a portal redesign. A script that breaks silently is worse than no script.
- Cover your long tail. The big vendors are easy. The niche tool you pay 9 dollars a month is the one nobody supports.
- Deliver the files. To your accountant, to a shared folder, or attached to the bank transaction.
The 5 methods compared
| Method | Invoices not emailed | Where it signs in | Breaks when the portal changes | Long-tail vendors |
|---|---|---|---|---|
| Email rules or inbox scanner | No | Nowhere | No | Only if they email |
| Invoice collection tool | Yes, for its list | Usually its cloud | The tool fixes it | If it is on the list |
| Vendor API | Yes, when one exists | API key | Rarely | Few vendors have one |
| Your own Playwright script | Yes | Where you run it | Yes, you fix it | You write each one |
| AI agent with saved scripts | Yes | Your own browser | The script is fixed and saved | The agent writes it |
1. Email rules and inbox scanners
A Gmail filter, a Zapier flow or your accounting tool’s inbox address catches every invoice that arrives as an attachment. Set this up first: it is free and it never breaks. It does nothing for the vendors that only email a link or a payment notice.
2. Invoice collection tools
Tools such as GetMyInvoices, Dext or Hubdoc keep a list of supported vendors and fetch the invoices on a schedule. They work well when all your vendors are on the list. Most of them sign in to the portals from their own cloud, so they hold your portal passwords, and a vendor that is not on the list stays manual. We compare them one by one in Invoice collection tools compared.
3. The vendor’s API
When a vendor gives you an API for your own billing history, use it: it is the most stable option. Few SaaS vendors do. Their billing page is made for people, often through a Stripe customer portal, and there is no endpoint you can call with an API key.
4. Your own browser script
A developer can write a Playwright or Selenium script per portal: sign in, open the billing page, click download. It works, but you own every part of it. You store the passwords, you handle the two-factor codes, you deal with the bot checks a headless browser gets in a datacenter, and you fix the selectors each time a portal is redesigned. With 15 vendors, that is 15 scripts to keep alive.
5. An AI agent with saved scripts
An AI agent such as Claude or ChatGPT can open a billing portal and find the invoices without a script written in advance. Left alone, it clicks its way through the portal each time: it is slow, and it can take a different path every month. The reliable setup gives the agent one saved script per portal. The agent picks which scripts to run and for which month, and the scripts do the clicking, the same way every time.
This is what Reduck does. The next section shows how.
How to automate downloading invoices with Reduck
Reduck gives your AI agent a catalogue of browser scripts, through its MCP server. For invoices, more than 35 billing portals already have a ready-made script: OpenAI and ChatGPT, Claude and the Anthropic Console, Notion, Slack, Cursor, Atlassian, Google Workspace, GitHub, Vercel, Cloudflare, Supabase, Linear, Asana, Miro, HubSpot, Zapier and more. You can search them all.
The scripts run in your own Chrome, through the Reduck extension, where you are already signed in. Your passwords and two-factor codes never leave your computer, and portals see your usual browser and IP, so bot checks rarely stop it.
Step 1: Connect your agent
- Create an account at reduck.ai
- Install our Chrome extension in the Chrome you are signed in with, and pair it with your account
- Install Reduck MCP
On Claude Code CLI:
claude mcp add reduck --transport http --scope user https://mcp.reduck.ai
On Codex CLI:
codex mcp add reduck --url https://mcp.reduck.ai
In claude.ai or Claude Desktop, add a custom connector with the URL https://mcp.reduck.ai. For
other MCP clients, see our Onboarding Guide.
Step 2: Sign in to your vendors once
Open each billing portal in that Chrome and sign in, as you would by hand. Use an account that can see billing: an owner or billing admin on team plans. You do this once; the sessions stay.
Step 3: Ask for the month
Using Reduck MCP, download my September invoices from OpenAI, Notion, Slack, Cursor and Atlassian, and email them to accountant@example.com.
Step 4: The agent runs one script per portal
For each vendor, the agent runs two scripts:
- a
list_invoicesscript, which reads the billing history and returns each invoice’s date, amount, status and link; - a download script, which gets the PDF. Many vendors bill through Stripe, so one Stripe script downloads their PDFs from the invoice link.
Then it sends the files with a Gmail script, saves them in a folder, or attaches each one to its transaction in Qonto or Wise. At the end, it lists any vendor it could not reach, so you know what is missing.
Step 5: A vendor with no script
If a portal has no script yet, the agent opens it in your browser, finds the invoice list, and saves what it did as a new script. Next month, that vendor runs like the others.
Step 6: Every month
Ask the same prompt next month, or schedule it with your agent. When a portal changes and a catalogue script fails, the failure is reported and the script is fixed and saved, so you do not keep your own copy up to date.
Guides for single vendors: Notion, OpenAI and ChatGPT, Claude, Cursor, Slack. By group: AI tools, cloud and dev tools, workspace apps.
Limits
- Your Chrome has to be open. The scripts run in your browser, so a scheduled run needs your computer on. For runs while it is off, use a managed browser in the cloud with a connector.
- You still need billing access. The agent sees what your account sees. If only a colleague is billing admin, the scripts run in their Chrome.
- Some portals have no PDF file. A few show the invoice as a web page only; the script then saves the page as a PDF, or returns its link.
FAQ
How long does it take to set up?
About ten minutes: create an account, install the extension, add the MCP server to your agent, and make sure you are signed in to your vendors. The first prompt runs right after.
Do I have to give my vendor passwords to Reduck?
No. The scripts run in the Chrome where you are already signed in. Reduck never sees your portal passwords or your two-factor codes.
What happens when a vendor redesigns its billing page?
The script for that portal fails and the failure is reported. The script is fixed and a new version is saved, so your next run uses it. Your agent also tells you which vendors it could not reach on a given run.
Can I download the invoices of past months?
Yes. Ask for a range (“all of 2026”, “since January”), and the agent downloads each invoice in the billing history for those months.
How much does it cost?
Reduck is free for 100 script runs a month. A list and one download for each of 10 vendors is about 20 runs. See pricing for more.
Is it better than an invoice collection tool?
It depends on how you work. If your vendors are all on a collection tool’s list and you want a dashboard, use one. If you already work with an AI agent, want to keep your passwords on your own computer, or pay for tools no collector supports, an agent with saved scripts covers them.
Final thoughts
Start with email rules: they catch the vendors that attach a PDF, for free. For the rest, the choice is about who signs in to your billing portals and who fixes the scripts. With an AI agent and Reduck, the answer is: you sign in, in your own Chrome, once; the scripts are saved and fixed for you; and month-end becomes one prompt.