To download supplier invoices every month from a portal with no integration, brief an AI agent in a chat. It signs in to the portal in its own browser, downloads the invoices as PDFs and files them in Google Drive under each supplier's name. You type any password or one-time code yourself. Once a run works in chat, a workflow can repeat it on a schedule.
Can an AI agent download supplier invoices from a portal?
Yes, if the portal works in an ordinary browser. Kaer's supplier portal page says it signs in the way your team does, on the site your supplier already runs. Your supplier does not have to set anything up. The same page warns that some suppliers restrict automated access, so read the portal's terms of use first.
What does the monthly job involve?
Three things repeat every month: the sign-in, the download and the filing. Only the sign-in can need you. Passwords, one-time codes and card details are typed by you, and the browser stops at those screens until you hand it back. For the download and the filing, nothing waits for you, and filing sends nothing. A portal that asks for a code at every sign-in still needs a person at that step, because only you receive the code.
A sequence to try, as advice rather than a rule from any page:
- List the portals you need invoices from, with the sign-in each one uses and whether it asks for a code.
- Brief the job once in a chat and watch the first run in the live browser beside it.
- Check that each supplier's folder holds the invoices the portal lists for that month.
- Once the run is right, turn it into a workflow with a monthly schedule.
How do you brief it so it picks the right month?
Name the site, the sign-in, the month and where the files should go. The guide to working on a website with no integration describes the same approach: brief the job in a chat the way you would a colleague, naming the site. For a hypothetical five-person print shop, the brief could read like this:
Log in to the paper supplier's portal, download the invoices dated in October, and file each one under that supplier's name in Google Drive. Tell me if the portal asks for a code before you go further.
Putting the month in the brief, rather than a phrase like this month, makes the result easy to check against the portal. That is our advice, not something the guide sets out.
What happens at a password, a one-time code or a captcha?
Kaer stops and tells you it is your turn. When a site asks for a password, a one-time code or card details, the footer says so. You click Take over, type the details yourself, then click Hand back. The guide says Kaer can't see or keep your password. Captchas and sites that block automated browsers are handed to you in the same way. Kaer tells you and offers you control, and it does not work around them.
Can the monthly download run without you?
It can where the sign-in does not need you each time. Kaer Workflows run on a schedule, and the run starts whether or not anyone remembers to start it. The workflows page gives the first working day of the month as one example of a schedule.
A worked example: one month for a print shop
Take a hypothetical five-person print shop with three paper and ink suppliers, each with its own portal. The owner logs in to all three on the first working day, finds the month's invoices and saves each one into a folder by hand.
With the job briefed and scheduled, the run repeats the three sign-ins and downloads, then files each invoice under its supplier's name in Google Drive. If one portal asks for a code at sign-in, the run stops at that screen and waits for the owner. Kaer reports what it did in the chat, so the owner can read the outcome there.
Where does the download happen, and what is kept?
The download happens on Kaer's own computer, not on yours. That machine is a separate, sandboxed machine, and the computer page lists downloading statements and exports among the steps Kaer finishes without asking. Each task keeps a list of the steps it took and what you approved, so the record of a month's run is there to read.
What should you check after the first run?
The first run is the test, and the check is yours to make. This is our advice, not a step any page sets out. Open each supplier's folder and count the invoices against the list the portal shows you for that month, because a run that files fewer than the portal lists has missed something. Open two or three files at random and confirm that each one is the right supplier and the right month. If a run stopped at a sign-in screen, find out which supplier it was and whether a code was needed, since that tells you which portals will need you each month.
Keep a short note of what the run did and where it stopped, in the same place each month. The note shows which part of the job is still yours, so the list of jobs you do by hand stays accurate.
Is an agent the right tool for every supplier?
Not always, and this is our judgement rather than something a page says. If a supplier emails its invoices as attachments, a rule in your mailbox may be enough, and that is simpler. An agent is more useful where the invoices sit behind a login and there is no email to read. Keep any portal that asks for a code on your own list of jobs you do by hand, and move the rest across once a run has been checked.
Frequently asked questions
What happens if the portal changes its layout?
Kaer looks at the page as it is on each run, instead of replaying a stored set of clicks. When it cannot find what it needs, it puts a card in the chat and asks you, rather than guessing.
Which plan do I need to run the download on a schedule?
Kaer's workflows and its own computer both come with paid plans. The pricing page shows what each plan includes.





