Skip to main content
An invoice can match last month’s total and still be wrong. The rate changed. The contract ended. The same invoice arrived twice. Someone notices three weeks later because the real work is buried across Gmail, Drive, and a tracking sheet. Give that checking job to an AI employee. They bring you the exceptions on schedule. You still approve every payment.
Writes follow your tool permissions. Keep messages, records, and approvals on Ask while you test. Runner stages each write as an Action Card. Allow acts without asking. Off blocks the tool unless the Runner has its own override.

Recurring jobs for finance and operations

Each Runner works independently. Runners can read the same source apps, but they don’t pass work or results to one another automatically.
The safest first AI employee doesn’t move money. They tell you where to look.

Start with: invoice check

A user-created Runner becomes active as soon as it’s created. Review its schedule and permissions, then click Run now. Run it against a small set first. Five invoices you already checked will tell you more than a perfect-looking prompt.

Add the rules to the saved prompt

Put these in the Runner’s saved prompt:
  • Where current agreements and approved vendor records live.
  • Required fields and matching tolerances.
  • Escalation timing.
  • Actions Runner must never take without a person.
Use Project context for background such as vendor owners and business-unit names. Keep invoice, contract, and checklist status in the source files. Each run starts in a separate session and doesn’t automatically receive the last run’s output. Start every financial write on Ask. In many cases, the right permission is Off. Runner can collect and compare without approving anything.

Other jobs to schedule

Vendor renewal watch

Run Monday morning. Find agreements renewing in the next 60 days, then show owner, current cost, notice deadline, and any renewal email. Draft the question. Don’t renew or cancel.

Receivables follow-up

Run twice a week. Read the approved open-invoice list and matching customer thread. Draft a follow-up only when the source says the invoice is past due and no payment or dispute is recorded.

Weekly operating report

Run after the reporting deadline. Pull submitted numbers into the agreed format, identify missing inputs, and draft reminders for the owners. Don’t invent a number to complete the page.

Close readiness

Run each weekday morning. If the close checklist isn’t active, stop. During close, list open items and missing support, then name the source or owner shown. Keep reconciliations and sign-off with finance.

The useful result is a shorter exception list

Runner doesn’t need to “run finance.” It needs to take a long list and show only the items that deserve a human decision. Measure exceptions caught before approval and the report assembly you no longer do by hand.

What’s next?

Which AI employee should you add next?

Find the next job tied to cost, time, or risk.

Connect your apps

Link the sources where invoices, agreements, and trackers live.

Tool permissions

Keep high-stakes writes behind a person.