[ QuickBooks / Collections ]

Overdue QuickBooks invoices, followed up daily

engini reads your open QuickBooks Online invoices every morning, and an AI agent sends each customer the reminder that fits how late they are, reads the replies, and records promises to pay and disputes where your team works. Before every send it checks the balance again, so nobody is chased for an invoice they paid yesterday.

QuickBooksOutlook or GmailSlackGoogle Sheets
Read the QuickBooks guide →
The morning collections run
  1. Every weekday at 7:00schedule trigger
  2. QuickBooks logo
    Read open invoicesbalance due, days overdue
  3. Agent writes reminderstone by stage, invoice numbers
  4. Reply read"paying Thursday"
  5. Slack logo
    Logged and sharedcollections sheet, #finance
Illustration of the flow on this page, not a product screen.
What it does
Daily reminders from QuickBooks, replies read and logged
Systems
QuickBooks Online, Outlook or Gmail, Google Sheets, Slack or Teams
Built with
A scheduled workflow with an AI agent step
Your control
Read access is enough; wording and stages are yours
[ 01 / The problem ]

Reminders go out. The follow-up does not.

Blurred landscape photo with the words Collections and the labels Read, Write, Listen, Stop

QuickBooks Online can send invoice reminders. What it cannot do is read the customer’s answer, remember that they promised to pay on Thursday, or tell the account owner that a line is disputed. That part happens in an inbox and a spreadsheet, when someone has time.

Where collections stall

  • Deciding each morning who to chase, from the aging report.
  • Writing reminders that mention the right invoices and amounts.
  • Keeping track of promises and disputes by hand.
  • Chasing a customer who already paid.

What the agent does

A scheduled engini workflow reads open invoices and their customers from QuickBooks, and an AI agent step writes one reminder per customer with the invoice numbers, amounts and any earlier promise, in the tone you set for each stage. It reads the replies, records promises to pay and disputes in your collections sheet and alerts the owner in Slack or Teams. Each run reads the current balance first, so paid invoices drop out.

[ 02 / How it works ]

A collector’s routine, every morning

01 / Read

Overdue invoices

A scheduled workflow reads invoices with a balance due and their customers from QuickBooks.

02 / Write

One reminder each

An AI agent step writes each customer one email with the invoice numbers and amounts, in the tone for that stage.

03 / Listen

Replies become notes

The agent reads replies and records promises to pay and disputes in your collections sheet and in Slack or Teams.

04 / Stop

Paid drops out

Every run reads the current balance first, so an invoice paid yesterday gets no reminder today.

This is the flow you will build. Start free and connect your systems.

[ 03 / What the agent reads and writes ]

What the agent reads and writes

SystemRecordsAccess
QuickBooksInvoices with a balance due, customersRead
Outlook or GmailReminders and repliesSendRead
Google Sheets or ExcelCollections log: promises, disputes, next stepWrite
Slack or TeamsDisputes and promises to the ownerWrite

Connect these systems in engini and give the agent only these tools.

[ 04 / Build it with the engini skill ]

Describe it in plain words. The engini skill builds the workflow.

engini skills is engini’s plugin for Claude Code and Codex. Its workflow agent, Flo, turns a plain-language request into an engini workflow: it designs the steps, dry-runs them against your own engini account, shows you a proposal, and creates the workflow only after you approve it, always turned off. You check it in the engini designer and turn it on.

Blurred landscape photo with the QuickBooks logo, the engini mark and a frosted tile joined by a thin line, labeled every morning: overdue, reminder, promise to pay

Editorial image: the stages of a reminder sequence.

Claude Code: install once
/plugin marketplace add engini/skills
/plugin install skills@engini
Then ask for this solution
Build a workflow in my engini account: every weekday at 7:00, read QuickBooks invoices with a balance due that are past their due date, group them by customer, send each customer one reminder email from Gmail listing the invoice numbers and amounts, and add a row per customer to the "Collections" Google Sheet.
  1. You need an engini account, the engini CLI (npm i -g @engini/cli) and a workspace-scoped API key, ideally a dedicated least-privilege one.
  2. Connect the systems this flow uses in engini first. Flo never creates or changes a connection and never handles your key; it tells you which command to run.
  3. Flo checks your login and workspace, searches the tool catalog, compiles the plan and shows a proposal table with every step. It creates the workflow only when you approve that proposal, and it creates it turned off.
  4. Open it in the engini designer, fill anything it left for you, and turn it on.
engini skills for Claude Code and Codex →
What the skill will never do on its own →
[ 05 / Agent Policy ]

The agent does only what you allow. Every run is on the record.

Agent Policy is how you govern agents in engini: the tools each agent may call, the account each tool uses, and a record of every call.

Toolsets

Scope every call

Hand the agent a toolset: only the tools it needs, each on the connection you choose, for example read only. engini enforces it on the server for CLI, SDK and REST API calls; a call outside the toolset is refused. An MCP server exposes only the connections and tools chosen when you set it up.

Identity

Acts with the account you connect

engini acts with the permissions of the connected account. Connect a person’s own account and it acts as that person; use a shared integration account and it acts as that account. Every run is recorded under the user who triggered it.

Audit

History and audit log

Each tool call and workflow run is recorded in History and the audit log, which supports export and streaming to your SIEM. Your agent never needs your credentials: engini stores them and adds them when it runs each call.

SOC 2 Type IIISO 27001GDPRHIPAA compliant
[ 06 / Try it now ]

Build it on your own data today

Start free, connect QuickBooks, and build this flow with the engini skill, in Workflow Studio, or from your own agent.

  • 01Workflow Studio. Build the flow on a visual canvas, with an AI agent step where judgment is needed. Start free →
  • 02Your own agent. Give Claude, ChatGPT or Cursor an engini MCP server with only these tools. MCP client setup →
  • 03The engini skill. Ask Flo in Claude Code or Codex and review its proposal. Install the skill →
[ 07 / Questions ]

Questions buyers ask before they start

Can QuickBooks send reminders on its own?

QuickBooks Online can send invoice reminders. The agent adds what reminders miss: reading replies, remembering promises, routing disputes and choosing the next step per customer.

Will paid customers get reminders?

No. Every run reads the current balance in QuickBooks before sending, so paid invoices drop out.

Does it need write access to QuickBooks?

No. This flow only reads invoices and customers. Payments are recorded in QuickBooks the way you do it today, or with the cash application flow.

Where are promises and disputes kept?

In a sheet or board your team already uses, plus a note to the owner in Slack or Teams.