Announcing o11's backing from Y Combinator.

AI for NetSuite

AI that closes the books inside the ERP.

Post journals and clean records without leaving NetSuite.
Reconcile AP and AR with the agent in the loop.

o11 for NetSuite: an AI agent layer for the ERP

o11 is an AI execution layer that runs inside NetSuite. The agent posts journals, cleans AP and AR, updates custom records, and keeps the GL in shape — without sending a controller into a side script to retype what they already approved over email.

If you have searched for AI for NetSuite, a NetSuite AI agent, or an alternative to SuiteAnalytics for actual workflow execution, the difference is simple: does the AI describe the close or do the close.

What teams use o11 for in NetSuite

GL close in flow. Post recurring journals, accruals, and reclassifications without leaving the system of record.
AP and AR cleanup. Match open items, code invoices, and resolve unapplied cash with the agent in the loop.
Custom record updates. Maintain custom records, fields, and saved searches the same way operators would by hand.
Cross-system reconciliation. Pull source documents from email, drives, and spreadsheets into NetSuite without retyping.

Why o11 differs from NetSuite-native AI

SuiteAnalytics and Oracle’s AI features are scoped to dashboards and prompts. They surface insight, but the journal entry, vendor payment, or record edit still ends with a human clicking through the UI. o11 drives the UI. The chat is the control surface, NetSuite is where the work lands.

Built for teams that live across systems

NetSuite is one part of a much larger finance stack — usually paired with Excel, a bank portal, an FP&A tool, and an inbox of vendor PDFs. o11 is positioned to act across all of them. A vendor email becomes a coded bill, a journal draft, a Slack message to the approver, and an updated workbook without the controller stitching the tools together by hand.

Where NetSuite teams typically start with o11

Controllers with close tasks, journals, and reclassifications.
AP and AR clerks with invoice coding and cash application.
FP&A with variance lookups and ledger pulls.
Operations finance with custom record cleanup and saved-search hygiene.

How o11 respects NetSuite permissions

The agent operates with the user’s own role. Permission lists, restrictions, and segment-level access apply exactly the way they do for that user in the UI. Nothing is bypassed. That is what makes o11 deployable in regulated finance orgs that cannot trust a tool that runs as an over-privileged integration user.