How to Automate Bill.com

BILL is the queue of everything the company owes

Bill.com, which the company now brands simply as BILL, is the accounts payable and receivable platform a large share of American small businesses and accounting firms push their money through. It is the queue. Every supplier invoice, every subcontractor bill, every subscription renewal lands in it, gets coded, gets approved by whoever has to approve it, and gets paid.

That makes it one of the few systems where the order of operations really matters. A bill left unapproved for three weeks is a supplier who stops answering the phone. A bill approved twice is money gone. A bill coded to the wrong account is a conversation with your accountant in March.

The people in it are mostly not accountants. The bookkeeper lives in it, but so does the project manager who has to sign off the subcontractor invoice and the owner who approves anything over a threshold. Most of them only open it because they were emailed a reminder.

Approval chasing eats the week before payment day

Processing the bill is not the work. The work is everything around the bill that BILL cannot see.

A subcontractor invoice arrives and nobody can approve it until somebody opens the project system to check what was actually delivered. A utility bill looks high, so somebody signs into the utility portal and compares it with the last four months. Half the vendors bill through their own portal, so their invoice is not really an invoice until a person logs in, finds it and downloads the PDF. A new vendor cannot be paid until the W-9 turns up, which is three emails spread over two weeks.

Then payment day arrives. Whoever runs it opens the approval queue, finds eleven bills nobody has touched, and spends the morning asking why.

None of it is difficult. All of it is somebody's Tuesday.

Bill.com

Invoices fetched from vendor portals The suppliers who bill through their own login, checked on a schedule so the invoice is in the queue before it is late.

Approvers given something to compare A bill that jumped sitting next to last quarter's figure, so the person approving it is reading a difference and not a number.

The queue cleared before payment day What is unapproved, what is missing a W-9 and what is approved but unscheduled, listed days ahead of payment day so none of it is news on the morning.

Approval routing only moves the bills it already has

BILL automates the middle of this properly, and it is worth exhausting what is already there before adding anything.

Invoice capture reads a bill and lifts out the vendor, the amount and the dates, and its AI codes line items to the right accounts. Approval routing sends each bill to the right approver on rules you set, with thresholds that pull in a second signature. Two-way and three-way matching compares the invoice against the purchase order and the receipt and flags what does not line up. Duplicate detection catches the invoice that got submitted twice. The whole thing syncs both ways with QuickBooks, NetSuite, Xero or Sage Intacct, so coding done once is not done again.

Every one of those acts on a bill that has already reached BILL. That is the ceiling, and it is easy to miss precisely because the platform is so good at what comes after.

The invoice still sitting in a vendor's own billing portal is not in BILL. Neither is the contract that says what the rate should be, the delivery note that proves the pallet arrived, or the reason the amount changed. Three-way matching is only ever as good as the purchase order somebody typed.

Payment day can start with the exceptions already found

Fetching an invoice off a vendor's billing site is an errand with a fixed route and no decisions in it.

The vendors who bill through their own portal get checked on a schedule, their invoice downloaded and filed into the queue before anyone notices it was late. The bills whose amount jumped arrive with last quarter's figure next to them, so the approver reads a comparison instead of a total. The recurring charge that quietly went up gets named while the increase is still small enough to argue about.

The chasing works the same way. Vendors missing a W-9, listed with how long they have been missing it and a message drafted ready to send. Bills approved but never scheduled, caught before the due date rather than after it. An AP aging summary waiting on the first of the month instead of being assembled by hand on the fourth.

The line to hold is obvious and worth saying anyway. Everything up to and including the flagged exception can run unattended all week. Approving a bill and releasing a payment are decisions with money on the other side, and they belong to a person who can be held to them.

An agent can prepare a payment run, not release one

Getting a bill into the queue with its evidence attached means opening the vendor portal and reading what is there. The approval at the end is the only part that carries a signature.

WebRun is an AI agent that works a real Chrome browser, signed in as you. It opens the vendor portals, the project system and BILL itself, collects what each bill needs in order to be approved, and puts it where the approver will actually see it.

It runs on your schedule in your own private environment, and you can watch a run and stop it mid-way. It does not approve bills, schedule payments or move money. Anything with a payment on the other side is drafted and left for a person.

The workflows below are already built, and each one names what it opens.