Connect ION Factory OS to QuickBooks with AI
Early-stage hardware teams often land on this exact stack: ION Factory OS for the factory, QuickBooks Online for the books. It is a pragmatic combination — and a lopsided one. ION knows everything about parts, POs, and builds; QuickBooks only sees vendors and dollar amounts. When your bookkeeper asks what a $4,300 bill from a machine shop was actually for, the answer lives in ION, and the person who knows how to find it is usually busy building hardware.
bomrail bridges the two with a hosted MCP server rather than an accounting integration. Claude gets read-only tools for both systems through one endpoint: ION purchase orders, receipts, and parts on one side; QuickBooks bills, expenses, and vendor balances on the other. Questions that used to require two logins and tribal knowledge — "which bills this month have no matching receipt?", "what have we paid Protocase year to date, and for which parts?" — become one chat message anyone on the team can send.
There is deliberately no automatic posting, no chart-of-accounts mapping to configure, and no sync to break at month end. The books stay exactly as your bookkeeper keeps them; bomrail just makes them answerable in the context of your factory data.
What becomes answerable
bomrail exposes both systems as read-only MCP tools. These are the joins an agent can make on demand:
Bills & purchase orders
QuickBooks bills matched to ION POs by vendor and reference, with unmatched bills flagged for review.
Vendor spend
QuickBooks payment history joined to ION PO lines, so spend can be broken down by part, not just vendor.
Receipts vs. invoices
What ION received against what QuickBooks was billed — the small-team version of a three-way match.
Open payables
Unpaid QuickBooks bills for suppliers who currently hold your open ION POs — useful leverage before a "where is my payment" call.
Example: month-end without the spreadsheet
It is the third of the month and your bookkeeper has eleven uncategorized bills. Instead of a back-and-forth email thread, they ask the agent: "For each unmatched bill this month, what was it for?" The agent walks the QuickBooks bills, finds the corresponding ION POs and receipts, and returns a table: bill, vendor, matching PO, parts received, suggested description. Nine match cleanly; two genuinely have no PO — one is a rush order someone placed by email, which is its own finding.
The bookkeeper still makes every categorization decision and posts every entry. What disappeared is the archaeology: the agent did the cross-referencing, cited the ION records it used, and left an audit trail of exactly what it read.
Frequently asked questions
Will this post transactions to QuickBooks automatically?
No. The QuickBooks connection is read-only. bomrail is not a bookkeeping automation tool — it makes your existing books queryable alongside factory data, and leaves every posting decision to a human.
We only have QuickBooks Online, not Desktop. Is that supported?
QuickBooks Online is the target — it is what bomrail connects to via OAuth. QuickBooks Desktop has no comparable API surface and is not planned.
Is this overkill for a ten-person team?
The smaller the team, the fewer people know both systems — which is exactly when a shared AI endpoint helps most. Setup is one OAuth sign-in per system, and the Starter plan covers two connected systems.
When will the QuickBooks connector be available?
QuickBooks is in the "coming soon" tier and is being prioritized with design partners. If it is your stack, join the waitlist and say so — connector order is decided by exactly that signal.