Friday Payment Run
Overview
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.
Friday Payment Run
Every week someone in accounts payable pays the bills that are due, then explains to their manager which ones they held back and why. It is routine, it is repetitive, and it is exactly the kind of thing that gets done at 5pm on a Friday when nobody is at their sharpest.
This flow prepares the run. It proposes every bill due within the next seven days, and — the part that actually earns trust — it accounts for the bills it did not pay, each with the reason it is on hold.
It runs against RAP One, a fictional SAP-style ERP used for training. All data is synthetic.
What it produces
payment-run.csv in your home folder, in two parts:
- Proposed for payment — the bills due within seven days, with the run total.
- Excluded (blocked) — the bills the run left out, each with its reason: a goods receipt not yet confirmed, a quantity or price mismatch against the purchase order, or a missing PO reference.
On the seeded ledger that is 4 bills proposed and 7 blocked.
How it works
1. Sign in
RAP One uses a SAP-style login: username, password and a client number. The session lives in memory only, so after signing in the robot navigates by clicking the menu, never by reloading a URL — a reload would drop it straight back to the login screen.
2. Build the proposal
On the payment run screen the robot narrows to bills due within seven days, selects them and creates a proposal. Blocked bills never appear here — the ERP only offers payable ones — so the proposal is clean by construction. Confirming the run posts a payment journal entry for each bill and flips it to Paid.
In a real deployment this is where the human-approval gate goes: draft the proposal, email it for sign-off, and only confirm once approved. This training version confirms it directly so you can see the whole cycle.
3. Account for what was left out
The manager's first question is always why wasn't this one paid? So the robot opens the bills list, filters to Blocked, and reads each held bill with its reason. Three of them are genuine exceptions a buyer needs to resolve — a mismatched quantity, a mismatched price, a missing PO — and the rest are simply waiting on a goods receipt.
Running it
Ready to run as-is. It signs in with the published training credentials (HTANAKA, client 100),
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.
- Invoice Inbox to LedgerReads 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.