[ QuickBooks / Payments ]

Customer payments, matched in QuickBooks

engini reads remittance emails and the payment files your bank already produces, finds the open QuickBooks Online invoices each payment covers, and records the payment against them. Short pays and anything unclear go to a person with the proposed match attached. engini moves no money; it records what already arrived.

QuickBooksOutlook or GmailSFTPSlack
Read the QuickBooks guide →
One payment, three invoices
  1. Remittance arrivesone transfer, three invoices
  2. AI extracts the detailspayer, amount, invoice numbers
  3. QuickBooks logo
    Open invoices foundcustomer: Northwind, 3 open
  4. QuickBooks logo
    Payment recordedapplied to the three invoices
  5. Slack logo
    Short pay flagged#finance: 85.00 short
Illustration of the flow on this page, not a product screen.
What it does
Remittances matched to open invoices and recorded as QuickBooks payments
Systems
QuickBooks Online, Outlook or Gmail, SFTP or shared folders, Slack or Teams
Built with
A workflow with engini AI Tools extraction and an AI agent step
Your control
Only exact matches are recorded; the rest go to a person
[ 01 / The problem ]

The money arrived. The matching did not.

Blurred landscape photo with the words Payment matching and the labels Collect, Extract, Match, Record

A customer pays three invoices with one transfer and emails a remittance that lists them in their own words. Someone has to read it, find the invoices in QuickBooks Online, and record the payment against each one. Until they do, the aging report is wrong and collections chases invoices that are already paid.

Why matching takes time

  • One payment covers several invoices.
  • Remittances arrive as PDFs, email bodies or spreadsheets.
  • Short pays and deductions need a person to decide.
  • The payer on the bank line is not always the customer name.

Where the agent fits

engini AI Tools extracts the payer, amount and invoice numbers from each remittance, and an AI agent step finds the customer and their open invoices in QuickBooks and proposes the match. When the amounts add up, the workflow records the payment against those invoices. When they do not, it posts the proposed match and the gap to Slack or Teams. engini does not move money or replace your bank feed; it reads remittances and the files your bank already sends.

[ 02 / How it works ]

Read, match, record, flag the rest

01 / Collect

Remittances and files

Remittance emails start the workflow; bank files on SFTP, OneDrive or Google Drive are read on a schedule.

02 / Extract

The details

engini AI Tools pulls payer, amount, date and invoice numbers from each remittance.

03 / Match

Open invoices

An AI agent step finds the customer and their open invoices in QuickBooks and proposes the match.

04 / Record

Payment or review

Exact matches are recorded as a payment applied to the invoices; short pays go to a person with the proposed match.

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
QuickBooksCustomers, open invoicesRead
QuickBooksPayment applied to invoicesCreate
Outlook or GmailRemittance emailsRead
SFTP, OneDrive or Google DriveBank payment filesRead
Slack or TeamsShort pays and unclear itemsWrite

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 remittance: payment, match, recorded

Editorial image: one payment, several invoices.

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 a remittance email arrives in remit@ in Outlook, extract the payer, amount and invoice numbers with engini AI Tools, find those open invoices in QuickBooks, and if they add up to the amount, record a QuickBooks payment applied to them. Otherwise post the proposed match and the difference to #finance in Slack.
  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 match remittances to QuickBooks invoices?

Yes. engini AI Tools extracts the invoice numbers and amounts, and an AI agent step finds the open invoices in QuickBooks Online and proposes the match.

What about short payments?

Nothing is recorded. The agent posts the proposed match and the difference so a person can decide.

Does engini connect to our bank?

No. It reads remittance emails and the payment files your bank already sends to an inbox, SFTP or shared folder. engini moves no money.

Does it replace the QuickBooks bank feed?

No. It records customer payments against the right invoices; reconciling the bank feed stays in QuickBooks.