The droid that runs bills & approvals

Bills, handled before they’re late.

A droid that owns the inbound side of the books: it captures every incoming bill, matches it to the purchase order, routes it to the right approver, schedules the payment, and flags the duplicates and odd charges before a cent goes out — so nothing’s paid twice, late, or unseen.

Does: Captures bills, routes approvals, schedules pay
Where: Growing startup, ~30 people
Reaches people on: Slack, email
Works inside: Gmail, QuickBooks
Runs: On every bill + a weekly pay run

01The situation

Bills aren't hard, they just need handling, promptly, every time.

Bills arrived everywhere — the AP inbox, a forwarded email, a PDF in someone’s DMs — and getting them keyed in, matched to a purchase order, and approved was a manual relay that stalled the moment one person was busy. Approvals sat in inboxes; the occasional duplicate or inflated charge slipped through unchecked.

The result was late fees on bills nobody saw in time and the nagging worry that something had been paid twice. None of it was complicated — it just needed doing, promptly and every time, which is precisely what a busy 30-person company can’t guarantee by hand.

02How it works

How the droid took it on.

Rather than relay bills by hand, the team handed payables over. The moment a bill lands the droid captures it, matches it to its PO, routes the approval, and schedules payment — holding anything duplicate or odd before it’s paid.

TASK#198Bills & approvalsstanding

trigger: Any vendor bill landing in the AP inbox
also: A weekly pay run and AP digest
scope: Every incoming invoice
runs as: A contained droid action per bill
memory: Each vendor's normal amounts, terms, and PO history

Set up once, in plain language: “capture every bill, match it to its PO, route it to the right approver, schedule it on time, and stop anything duplicate or odd before it's paid.” The droid turned that into a standing job, the AP clerk a 30-person company hasn't hired.

FIG. 1The durable task, exactly as it exists in the runtime.

Every incoming bill trips the same loop:

01Bill arrivesVendor invoice, inbox
02Droid wakesJust for this bill
03Reads + matches to POExtract, verify, code
04Routes for approvalRight approver, one tap
05Schedules the paymentOn the due date
06Clean?Matches → route & schedule · Duplicate → hold · Anomaly → flag finance
07Posts to #financeAP digest + pay run

FIG. 2The loop each run walks.

03Ongoing handling

How it ran, bill after bill.

Here’s a week of payables as it actually unfolded, down to how it reached for each app. Only the one anomaly ever needed the controller.

QuickBooks — FIG. 3One night, run by run.

Isometric accounts-payable scene: an in-tray of bills, an invoice matched to a purchase order, an approval stamp and a payment calendar

See it in action

One week, bill by bill.

Incoming bills, an approval, and the weekly pay run land on the left. Watch the droid pick up each one and work it across the inbox and the ledger, pulling in a human only for the charge that doesn't add up.

The result

What changed, by the numbers.

Nothing latebills scheduled the day they arrive

Nothing twiceduplicates caught before payment

Approvals moverouted to the right person, one tap

Anomalies caughtodd charges flagged, not paid

An illustrative workflow built from real product mechanics. The connected apps, the schedules and the run handling are how a droid actually works; the companies, the people and the figures are composites rather than a customer's numbers.

Try this workflow

Run this workflow yourself.

Copy the brief below and paste it into Unify. It’ll walk you through the prerequisites, connect what it needs, and stand the workflow up with you.

Workflow brief

I'm the controller at a growing 30-person startup, and bills arrive everywhere: the AP inbox, forwarded emails, PDFs in DMs. Getting them keyed in, matched to a PO, and approved is a manual relay that stalls whenever someone's busy. Approvals sit in inboxes, the odd duplicate or inflated charge slips through, and we get late fees on bills nobody saw in time.

Own accounts payable. Apps/channels: Gmail (the AP inbox where bills land), QuickBooks (bills, the ledger, payment scheduling), Slack #finance (approvals and the digest).

Run on every incoming bill, plus a weekly pay run and digest. For each bill:
1. Read it and extract the vendor, amount, due date, and line items.
2. Match it to its purchase order and enter it as a draft bill, coded to the right account.
3. If it's over the approval threshold, route it to the right approver in Slack with one-tap approve.
4. Once approved, schedule the payment for the due date (not early) and log the approval for the audit trail.

Use judgment on what's clean: route and schedule the normal bills, hold and flag any duplicate invoice number before it's paid twice, and for an anomaly, like a charge well above the vendor's norm or with no PO, hold it and bring in the controller. On the weekly pay run, batch the approved, scheduled bills and post an AP digest. Remember each vendor's normal amounts, terms, and PO history.

What would you take off your desk?

Tell us the job that never gets done before close. We'll wire it up on a call and you can watch it work.

Try now, free Book a walkthrough