[ QuickBooks / Month-end close ]

A faster QuickBooks close, reconciled by an agent

engini reads QuickBooks Online accounts and transactions next to your bank file and billing export, and an AI agent reconciles them, explains each difference in plain words and prepares the adjusting entries in your close checklist. When your accountant marks an item ready, engini creates the journal entry in QuickBooks.

QuickBooksSFTPExcel or SheetsSlack
Read the QuickBooks guide →
Day one of the close
  1. First business day, 6:00schedule trigger
  2. QuickBooks logo
    Read QuickBooksaccounts, invoices, bills for the period
  3. Read the other sidebank file, billing export
  4. Agent reconciles and explains3 differences, each with a reason
  5. Checklist updatedproposed entries for review
Illustration of the flow on this page, not a product screen.
What it does
Reconciles QuickBooks against outside data and prepares entries
Systems
QuickBooks Online, bank and billing files, Excel or Sheets, Slack or Teams
Built with
A scheduled workflow with an AI agent step, plus a create-on-ready workflow
Your control
Your accountant marks each entry ready before it is created
[ 01 / The problem ]

Small finance teams close in spreadsheets

Blurred landscape photo with the words Month-end close and the labels Pull, Reconcile, Prepare, Post

For a team on QuickBooks Online, month end means exporting from QuickBooks, exporting from the billing system and the bank, lining them up in a spreadsheet and chasing the differences. Then the adjusting journal entries are keyed by hand. The work is careful rather than hard, and it lands on the same person every month.

Where close days go

  • Exporting the same reports with the same filters.
  • Matching invoices and payments line by line.
  • Writing down why each difference exists.
  • Keying adjusting entries into QuickBooks.

What the agent takes on

A scheduled engini workflow reads the period’s accounts and transactions from QuickBooks and the matching bank file or billing export from an inbox, SFTP or a shared folder. An AI agent step finds the differences, writes a reason for each and proposes the adjusting entry, all in your close checklist. When your accountant marks an item ready, a second workflow creates the journal entry in QuickBooks. engini has no QuickBooks triggers, so the reads run on your schedule.

[ 02 / How it works ]

Reconcile, explain, prepare, post on ready

01 / Pull

Both sides

A scheduled workflow reads QuickBooks accounts and transactions for the period and the bank file or billing export.

02 / Reconcile

Find what differs

An AI agent step lines them up and writes a reason for each difference.

03 / Prepare

Proposed entries

It proposes the adjusting entry for each item in your close checklist.

04 / Post

After review

When your accountant marks an item ready, a second workflow creates the journal entry in QuickBooks.

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
QuickBooksAccounts, invoices, bills, payments for the periodRead
QuickBooksJournal entries marked readyCreate
SFTP, inbox or shared folderBank file and billing exportRead
Excel or Google SheetsThe close checklistWrite

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 thin line, labeled reconciled: QuickBooks + bank, differences, entries for review

Editorial image: the close, reconciled.

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: on the first business day of each month at 6:00, read last month's QuickBooks invoices and the billing export CSV from my SFTP folder, list every invoice that differs or is missing on either side with a one-line reason, and add each one as a row in the "Close checklist" 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 AI reconcile QuickBooks against our bank and billing data?

Yes. A workflow reads QuickBooks and the bank file or billing export, and an AI agent step finds and explains each difference.

Does it post journal entries on its own?

Only after your accountant marks an item ready in the checklist; that change starts the workflow that creates the entry. engini has no approval step of its own.

Where do the bank and billing files come from?

From an inbox, SFTP or a shared folder where your bank or billing system already sends them. engini does not connect to your bank.

Does it replace the QuickBooks bank feed?

No. Bank feed matching stays in QuickBooks; the agent covers the reconciliation and entries around it.