[ QuickBooks / Bills ]

QuickBooks bills, entered for you

engini reads every supplier invoice that lands in your inbox, finds the vendor and the right expense account in QuickBooks Online, and creates the bill. Anything it cannot place with confidence, a new vendor, an unclear line, a possible duplicate, goes to a person instead. Your books stay in QuickBooks; the typing goes away.

QuickBooksOutlook or GmailSlackengini AI Tools
Read the QuickBooks guide →
One supplier invoice, into QuickBooks
  1. Invoice arrivesbills@ inbox, PDF attached
  2. AI reads the invoicevendor, date, lines, total
  3. QuickBooks logo
    Vendor and account foundQuickBooks vendor, expense account
  4. QuickBooks logo
    Bill createdlines, due date, PDF reference
  5. Slack logo
    Or a question for a person#bookkeeping: new vendor, please confirm
Illustration of the flow on this page, not a product screen.
What it does
Emailed supplier invoices become QuickBooks Online bills
Systems
QuickBooks Online, Outlook or Gmail, Slack or Teams
Built with
A workflow with engini AI Tools and an AI agent step
Your control
New vendors and unclear lines go to a person
[ 01 / The problem ]

Bookkeepers still type every bill

Blurred landscape photo with the words Bills and the labels Trigger, Read, Match, Act

For a small finance team on QuickBooks Online, accounts payable is mostly data entry: open the PDF, find the vendor, pick the expense account, type each line into a bill, attach the file, set the due date. Then do it again for the next supplier, in a different format.

The errors are small and costly: a bill entered twice, a supplier coded to the wrong account, a due date missed because the invoice sat in someone’s inbox.

Where the time goes

  • Reading invoices that every supplier formats differently.
  • Looking up the vendor and the usual expense account.
  • Checking whether this invoice was already entered.
  • Chasing the person who ordered something unfamiliar.

What the agent does

engini AI Tools reads each invoice, and an AI agent step does what a bookkeeper would: finds the vendor in QuickBooks, picks the account that vendor is usually coded to, checks for an existing bill with the same number, and creates the bill. When the vendor is new or a line is unclear, it asks in Slack or Teams instead of guessing.

engini works through the QuickBooks Online account you connect with OAuth 2, in production or a sandbox. QuickBooks has no engini triggers, so the flow starts from the email itself.

[ 02 / How it works ]

From inbox to bill in four steps

01 / Trigger

An invoice arrives

A new email in the bills inbox, in Outlook or Gmail, starts the workflow.

02 / Read

AI reads it

engini AI Tools extracts the vendor, invoice number, date, lines and total from the PDF.

03 / Match

The agent checks QuickBooks

An AI agent step finds the vendor and its usual expense account and checks that no bill with this number exists.

04 / Act

Bill or question

It creates the bill with its lines and due date, or asks a person in Slack or Teams when something is new or unclear.

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
QuickBooksVendors, accounts, existing billsRead
QuickBooksBill with lines and due dateCreate
Outlook or GmailThe bills inbox and PDF invoicesRead
Slack or TeamsQuestions about new vendors and unclear linesWrite

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 bills: invoice, vendor, bill

Editorial image: invoice, vendor, bill.

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: when an email with a PDF invoice arrives in bills@ in Gmail, read it with engini AI Tools, find the vendor in QuickBooks, check there is no bill with the same invoice number, and create a QuickBooks bill with the lines and the due date. If the vendor is not found, post the invoice details to #bookkeeping in Slack and create nothing.
  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 AI create bills in QuickBooks Online from emailed invoices?

Yes. engini AI Tools reads each invoice, and an AI agent step creates the bill in QuickBooks Online through the connection you set up with OAuth 2.

How does it pick the expense account?

From what you tell it and what QuickBooks already shows: the agent can read how a vendor’s earlier bills were coded and use the same account, and asks a person when it is not sure.

What about duplicate invoices?

Before creating a bill, the agent looks for an existing bill from the same vendor with the same number, and stops if it finds one.

What happens with a new vendor?

It creates nothing and asks in Slack or Teams, with the invoice details, so a person can add the vendor or tell it which one to use.

Does it work with QuickBooks Desktop?

This flow is for QuickBooks Online. engini connects to QuickBooks with OAuth 2, in production or a sandbox.