Web Automation automation templates

Takes 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.

Builds 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.

One 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.

Cleans 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.

Downloads 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.

Prepares 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.

Reads vendor-invoice e-mails out of the mailbox and posts each one as a bill in the ERP. It reads the vendor, reference, gross and purchase-order number from each message, derives the net, and keys a new bill - handling the two controls that fire mid-batch: a duplicate reference (cancelled rather than paid twice) and a failed 3-way match against the purchase order (posted but blocked). Writes a posting report. The story is straight-through processing with judgment: the clean invoices post themselves, and the two that should not go through are caught and reported.

Checks a month's payroll before it is posted. Signs in, opens the draft run, reads the register and refuses to finalize when a row is missing its cost centre, then confirms the register's net total matches the salary debit in the operating account. Writes a check report. The story is judgment: the robot stops on bad data rather than posting it, and proves one number agrees across the HR system and the bank.

Finds revenue the business won but never billed: deals marked Won in the CRM that were never turned into an invoice. Reads the deal board, keeps the cards flagged unbilled, totals what is owed, and writes the list finance needs to raise the missing invoices. The "robot that finds money" demo.

Verifies customer refund requests against the bank before approving them. Signs in to AcmeBank through two-factor, pulls every shipment charge from the operating account and groups them by reference; then works the helpdesk's refund queue, and for each ticket looks up the disputed charge to decide whether the customer was really billed twice. Approves the genuine duplicates and escalates the rest to a human with evidence. Writes a decision CSV.

Reconciles the e-invoices a government tax portal received against the vendor bills booked in the ERP, and reports the three ways the two can disagree: an amount that drifted, an e-invoice with no matching bill (arrived in the portal, never booked), and a bill with no e-invoice (booked, never filed). Two-factor signs in to the portal, pages the received register, then filters the ERP vendor-bill worklist per enrolled vendor to compare counts. Writes a reconciliation CSV. The story is a control: two systems that should hold the same set of documents, checked against each other so a gap is caught rather than discovered at audit.

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.

Turns a procurement onboarding request into a vendor master record across two systems. Reads the "new vendor onboarding" e-mail, takes the vendor name, category and terms straight from the request, then creates the vendor in the ERP - filling the General, Payment and Contact tabs with the bank and tax details from the onboarding packet. The IBAN is mod-97 checked on save, so a bad account number is refused before it can ever become a payable. Writes a record of the created vendor. The story is a clean hand-off: a request in one system becomes a validated master record in another, with no re-keying.

Navigates to a URL, reads its title and meta tags, and returns them as structured data. Useful for link previews or SEO audits.

Launches a browser and navigates to a provided URL — the minimum viable browser-automation template.

Opens a URL in a browser and saves a screenshot of the rendered page to disk.