home / use cases / web automation and research / supplier-portal-downloads

Portal statements fetched and filed monthly

Every month an Aivell logs into each supplier, bank and utility portal with the Browser Agent, downloads the new invoices and statements, and files them on your network share under your naming scheme. Broken logins and missing documents are reported, not ignored — and payment pages are blocked by guardrail.

Watch the demo

starts when: The 3rd of the month, 06:00 — statement day

The problem

No supplier sends the invoice anymore; they send an email saying the invoice is ready. Behind that email is a portal, a login, a password that expired since last month, and a PDF three clicks deep. Multiply by the electricity company, two telecoms, the bank, the leasing company and every courier, and month-end starts with a scavenger hunt across a dozen websites.

It’s pure collection work — no judgment, no value, just logins and downloads — and it lands on whoever does the books, in exactly the week they can least afford it. It’s a textbook slice of the hidden admin that costs firms around $17,000 per employee per year.

How your Aivell does it

  1. Statement day starts alone. On the 3rd at 06:00 the schedule fires and the Aivell works through the portal list, one login at a time.
  2. A real browser, a real session. The Browser Agent signs in and navigates exactly as a clerk would — no APIs, no integrations, no waiting for the supplier to modernize. Credentials stay on the box, encrypted at rest.
  3. Documents are filed, not just downloaded. Each PDF lands on your network share under your convention — supplier, year, month — so the folder your accountant expects is simply full.
  4. Surprises stop the machine, politely. A new terms-of-service popup, a forced password change, a document that isn’t there yet — the chore says stop and tell Nadia, or retry tomorrow. Nothing is accepted or clicked through on your behalf.
  5. The round ends with a receipt. One email: what was fetched, where it was filed, what failed and why. Silence never means “probably fine”.

The guardrails draw the hard lines: only whitelisted portal domains, payment and settings pages unreachable, writing allowed only in the statements folder. A colleague who does the boring round every month — and physically can’t do anything else.

The chore, as you'd write it.

No flowcharts, no code — a chore is just a message to your Aivell, in your own words. It shapes it into a solid, guarded procedure and follows it to the letter. This one:

Giulia Aivell · collect monthly portal invoices ● active

on the 3rd of each month, work through the twelve portals on the list

log into each one — electricity, telecoms, the bank, the couriers

download last month's invoices and statements as PDF

file each under supplier/year-month on the accounting share

a portal demands new terms or a password change? stop and tell Nadia

document missing or portal down — retry tomorrow morning, twice

never touch account settings, never click anything under billing or payment

when the round is done, email Nadia the list — fetched, filed, failed

You
Got it — I'll start right away, and check with you whenever something needs a human.
Giulia Aivell

The tools it uses.

Connected with single-click passkeys — no copied tokens, no OAuth hell.

Schedule starts the monthly collection round
Browser Agent logs in, clicks, downloads — like a clerk
Network folders files each PDF under the right supplier
Email reports fetched, filed and failed

Sensible guardrails.

Every tool can be limited to exactly what this chore needs. For this one, you might set:

Browser Agent May visit only the whitelisted portal domains. Payment pages and account settings are blocked outright.
Network folders Write access limited to accounting/statements; the rest of the share is read-only.

Questions, answered.

Where do the portal passwords live? +

On the box, encrypted at rest, used only by the Browser Agent inside your network. They are never synced to a cloud, never typed into anyone else's automation platform, never seen by a third party.

What happens when a portal redesigns its pages? +

The Browser Agent reads the page the way a person does — by what things mean, not by pixel positions — so most redesigns are a non-event. If it genuinely can't find its way, it stops and reports rather than clicking around blindly.

Could it accidentally pay a bill or change our account? +

No. The guardrail blocks payment and settings pages at the tool — the chore couldn't go there even if it misread an instruction. Downloading documents is the whole of its world.

Do the portals need to offer an API or an export? +

No. If a human can fetch the document in a browser, the Browser Agent can. That's the point — these portals never get integrations, so the clicking had always stayed human.

Related.

What is an Aivell?

An Aivell is an on-premise AI colleague: a small box that plugs into your network, runs its own AI onboard and takes the repetitive work off your desk. Prompts, documents, data — nothing ever leaves your office. Unplug the internet: it keeps working.

You describe each task as a chore, in plain language. Your Aivell turns it into a solid, guarded procedure and runs it in the background — with guardrails on every tool, a complete audit trail, and approvals in your hand when you want them. One-time setup, fixed monthly fee. No tokens, no overages.

Watch the demo

onboard inference · air-gapped · fixed monthly fee