Quote-to-Cash Gap Audit
Overview
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.
Quote-to-Cash Gap Audit
The most expensive mistake in a growing company is quiet: a deal closes, everyone celebrates, and nobody sends the invoice. The work was done, the customer is happy, and the money never arrives — because the step between "won" and "billed" fell through a crack nobody was watching.
This flow watches that crack. It reads the deal board, finds the won deals that were never invoiced, and tells you exactly how much money is sitting there uncollected.
It runs against Zapspot, a fictional CRM used for training. The data is entirely synthetic.
What it produces
billing-gaps.csv in your home folder — every won-but-unbilled deal with its customer and amount,
and a grand total. On the seeded board that is three deals worth €37,400 nobody billed.
How it works
1. Open the deal board
Sign in and open the deals kanban. Each card shows the deal's value, and the CRM chips a card unbilled when the deal is closed-won but has no invoice behind it.
2. Find the unbilled wins
The robot reads every card on the board and keeps only the ones flagged unbilled — a won deal finance never turned into money owed. Each one is revenue the company earned and forgot to ask for.
3. Total the recovery
It adds them up and writes the list finance needs — which customer, which deal, how much — with the grand total at the bottom. That list is the whole point: hand it over and the invoices get raised.
Running it
Ready to run as-is. It signs in with the published training credentials
(jonas.weber@globex.example), 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.