Use casefinance & AR

Invoice follow-up that chases itself.

Every finance team runs the same loop: pull the aging report, cross-check payments, write the awkward nudge email, remember the account that needs kid gloves. An agent runs that loop on a schedule — and pauses for your yes before anything reaches a customer.

// the manual version

You know this week already.

The Monday aging-report ritual

Someone exports the report, sorts by days overdue, and rebuilds the same mental triage they built last week — every week.

The awkward-email tax

Each chase email is judgment work: firm but friendly, third reminder vs first, the customer who just signed a renewal. So they get postponed.

The one that slips

The invoice that aged past 60 days because it sat in a spreadsheet tab nobody reopened. Nobody decided to let it slip; it just did.

// describe it

The whole build is a brief.

No canvas, no nodes. You write instructions the way you'd brief a teammate; the lines marked with a shield pause for a human before anything irreversible happens.

Example brief — illustrative, write yours in your own words

·Every weekday morning, check invoices due or overdue in QuickBooks.

·Skip accounts with a payment recorded in the last 3 days.

·For invoices 1–14 days overdue, draft a friendly reminder from our templates.

·For 15+ days, draft a firmer follow-up and cc the account owner.

Before any email is sent to a customer, wait for my approval.

If an account passes 30 days overdue, propose an escalation plan.

·Post a summary of what was chased and what's outstanding to #finance.

// how it runs

Autonomous on the routine. Supervised on the rest.

What starts it

A weekday-morning schedule — the aging check runs before you're at your desk.
A payment event from your accounting tool, so chases stop the moment money lands.
A teammate forwarding an email to the agent's address for a one-off chase.

What waits for a human

Every customer-facing email — drafted, then held for a named approver.
Escalations past 30 days — the agent proposes, a human decides.
Anything touching a flagged account (renewal in flight, disputed invoice).

What the trace keeps

Which invoices were checked, and why each was chased or skipped.
The exact draft, who approved it, and when it went out.
A per-run record you can hand to a controller who asks what happened.

// common questions

Does the agent send emails on its own?

Not to customers. Sending a customer email is exactly the kind of irreversible step Boring gates by default — the draft waits for a named approver, from the console, the extension, or your phone. Routine internal steps (checking the ledger, posting the summary) run on their own.

What tools does it need?

Your accounting system (QuickBooks, Xero, and similar are in the 1,284-tool catalog), your email, and wherever the summary should land — Slack, or just your inbox. Internal APIs can come in via OpenAPI.

What happens when an account is weird?

You put it in the brief — 'skip anything tagged enterprise-renewal' or 'always escalate disputes to Dana.' Instructions are plain language, so the exceptions read the way you'd tell a teammate about them.

Can you build this for us?

Yes — that's the white-glove offering. We scope your AR process, build the agent on Boring, and operate it with you. You approve the sends; we do the toil.

Hand off the invoice follow-up.

Join the waitlist and describe it in a sentence — or ask about white glove and our team will build and run it with you.

Early access · we'll email when your workspace is ready