Tax Portal Morning Board
Overview
Checks every client mandate on a government tax portal and builds one status board. Signs in as an authorised representative, reads all the mandates, then switches the active company for each and reads its dashboard - unread official notices, open penalties and upcoming deadlines. Flags any client with a penalty, an audit request or a late filing, and writes a board sorted worst first. Built for accountants and agencies watching many companies at once.
Tax Portal Morning Board
An accountant who manages a dozen companies' tax compliance starts every morning the same way: log into the portal, switch to each client, check for new penalties, unread notices and looming deadlines, then switch to the next. Twelve times. Before the first coffee.
This flow does that sweep and hands back a single status board — every client on one page, the ones that need attention at the top.
It runs against FRS, a fictional government tax portal used for training. The data is entirely synthetic.
What it produces
tax-status-board.csv in your home folder — one row per client, sorted worst first: its status,
unread notices, open penalties, deadline count, and a short reason for any that need attention. On
the seeded set of twelve mandates, three surface: two clients with penalties from late filings, and
one with an audit request carrying a hard deadline.
How it works
1. Sign in as the representative
Log in as the authorised representative with two-factor. A representative acting for many companies lands on a mandate picker rather than a single dashboard — the portal needs to know which client you are acting for.
2. List the mandates
The robot reads every mandate the representative holds — client name and tax id — and turns them into a work queue: one pass per company.
3. Check each client
For each mandate it switches the active company through the mandate switcher and opens that company's dashboard, reading the unread-notice count, the open-penalty count and the deadlines. A company with penalties, an audit request or a late filing is marked for attention; the rest are clear.
Two things worth knowing if you adapt this. Each switch raises a "now acting for …" toast, and over
a dozen clients those overlays pile up over the menu — the flow disables them with the portal's
toast-kill flag. And activating a mandate only sets the active company; the flow then opens the
dashboard explicitly to read it.
4. Build the board
The board is sorted with the attention cases first, so the human opens it and immediately sees the three clients that need them — not the nine that don't.
Running it
Ready to run as-is. It signs in with the published training credentials (FD-772103944, with a
static one-time code), which are not secret. Real system credentials belong in the Robomotion Vault,
never in a flow.
More web automation templates
See all 16 →- Bank ReconciliationTakes the payments and receipts the ERP could not reconcile and confirms each one against the real bank statement. It pulls the ERP's flagged paid-bill exceptions and open invoices awaiting cash, then signs in to the bank, searches the operating account by reference and reads what actually settled - quantifying the four ways money and ledger drift apart: a missing payment, a transposed amount, a double payment and unapplied cash. Writes a reconciliation CSV. The story is evidence: the ledger raises the question, the bank statement answers it, and every discrepancy comes out with a number attached.
- Logistics Exception CenterBuilds one worklist of every active delivery exception from the carrier, then dedupes it against the systems that may already be handling it - the mailbox that was notified, and the help desk where a ticket may already exist. Joining the three on the tracking number tells the robot which exceptions were mailed, which already have a ticket, and which nobody has picked up yet. Writes a consolidated exception CSV. The story is consolidation: three systems each hold part of the picture, and the robot joins them so a stuck shipment is neither missed nor double-worked.
- Monday Morning BriefingOne robot, every system, the whole week's work on a single page. It signs in to the CRM, the mailbox, the ERP, the carrier and the help desk in turn, reads the one number that matters from each - duplicate contacts, invoices to post, ledger exceptions, stuck shipments and refund requests - and writes a consolidated briefing with a total across all five. The story is reach: the back-office queues a team would open one browser tab at a time, gathered into one report before anyone has had coffee.
- CRM Duplicate CleanupCleans up a CRM by merging duplicate contacts - the same person entered twice under name variants like Bob and Robert. Signs in, switches the contact list to its duplicates view, and merges the first remaining pair until none are left, keeping the primary record and folding each variant into it. Writes a before-and-after report. The "your CRM cleaned itself while you slept" demo.
- E-Invoice Portal HarvestDownloads every e-invoice for a tax period from a government portal and builds an index spreadsheet of what was collected. Signs in with a one-time code, walks the paged register until the portal says there are no more pages, then opens each document to read its government reference number and pull down both the XML and the PDF. Every download is gated behind a confirmation dialog and an "I am not a robot" checkbox.
- Friday Payment RunPrepares a weekly vendor payment run in the ERP. Signs in, proposes every bill due within seven days and confirms the run, then separately opens the bills list, filters to the blocked bills the run left out, and reports each one with the reason it is on hold - a pending goods receipt, a quantity or price mismatch against the purchase order, or a missing PO reference. Writes a CSV of what will be paid and what will not.