[ NetSuite / Accounts payable ]

NetSuite AP automation, run by an AI agent

engini reads each emailed invoice, finds the vendor, purchase order and item receipt in NetSuite, and creates the vendor bill when they match. When they do not, it tells a person exactly what is off. You build it once in engini, with Workflow Studio, your own agent or the engini skill, and your NetSuite roles and approval routing stay as they are.

NetSuiteOutlook or GmailSlackengini AI Tools
Read the NetSuite guide →
One invoice, from inbox to vendor bill
  1. Invoice arrives in the AP inboxOutlook: ap@ trigger, PDF attached
  2. AI reads the invoicevendor, invoice no., lines, totals
  3. Agent matches PO and receiptNetSuite: vendor, PO 4512, item receipt
  4. NetSuite logo
    Vendor bill createdlines and PO reference set
  5. Slack logo
    Or an exception, explained#ap-exceptions: qty 40 billed, 36 received
Illustration of the flow on this page, not a product screen.
What it does
Turns emailed invoices into NetSuite vendor bills, matched to PO and receipt
Systems
NetSuite, Outlook or Gmail, Slack or Teams
Built with
A workflow with an AI agent step and the invoice reader in engini AI Tools
Your control
A NetSuite role you choose; your approval routing stays in NetSuite
[ 01 / The problem ]

AP on NetSuite is still typed in by hand

NetSuite holds the purchase order, the item receipt and the vendor. The invoice, though, arrives as a PDF in an inbox, and someone types it into a vendor bill: vendor, invoice number, each line, the GL account, the totals. Then they open the purchase order and the item receipt to check that what was billed was ordered and received.

Capture tools help with the reading, but the checking and the follow-up stay with people. A NetSuite user quoted by Stampli summed it up: the AP automation is not really automated. Month end then arrives with a pile of bills nobody has matched yet.

What slows an AP team down

  • Re-keying header and line data from PDFs that every vendor formats differently.
  • Opening three records to do a three-way match, invoice by invoice.
  • Chasing the buyer or the warehouse when quantities or prices do not line up.
  • Answering vendors who ask whether their invoice was received.

How an AI agent changes it

The reading, the lookups and the comparison are exactly the work an agent does well, and they are repetitive enough to run on every invoice. engini gives the agent the NetSuite tools it needs to read vendors, purchase orders and item receipts and to create vendor bills, and nothing else. A clean match becomes a vendor bill in seconds. A mismatch becomes a short, specific note to the person who can fix it, with the numbers side by side.

Because engini creates the bill through the NetSuite account you connect, NetSuite’s own controls still apply: the role on that account decides what can be created, and if you route vendor bills for approval in NetSuite, the new bill follows that routing like any other.

[ 02 / How it works ]

From PDF to vendor bill in four steps

01 / Trigger

An invoice arrives

A new email in the AP inbox (Outlook or Gmail) starts the workflow. Invoices dropped in a shared folder can be picked up on a schedule instead.

02 / Read

AI reads the invoice

The invoice reader in engini AI Tools pulls the vendor, invoice number, date, lines and totals from the PDF. No prompt to write.

03 / Match

The agent checks NetSuite

An AI agent step finds the vendor, the open purchase order and its item receipt with get-records calls, and compares items, quantities and prices.

04 / Act

Bill or exception

On a match, it creates the vendor bill with its lines and the PO reference. On a mismatch, it posts the difference to Slack or Teams for the buyer or AP lead to resolve, and creates nothing.

[ 03 / What the agent reads and writes ]

What the agent reads and writes

Give the agent a toolset with only these tools, on a NetSuite connection whose role fits AP.

SystemRecordsAccess
NetSuiteVendor, Purchase Order, Item ReceiptRead
NetSuiteVendor Bill (with lines and the PO reference)Create
Outlook or GmailThe AP inbox and its PDF attachmentsRead
Slack or TeamsException notes to the buyer or AP leadWrite
enginiHistory and audit log of every callRecorded
[ 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 NetSuite logo, the engini mark and a frosted tile joined by a thin line, labeled three-way match: invoice, match, vendor bill

Editorial image: invoice, match, 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 a new email with a PDF invoice arrives in ap@ in Outlook, read the invoice with engini AI Tools, find the vendor, the open purchase order and its item receipt in NetSuite, and if items, quantities and prices match, create a NetSuite vendor bill with the lines and the PO reference. If they do not match, post the differences to #ap-exceptions 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 NetSuite, 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

Does NetSuite have AP automation built in?

NetSuite holds vendors, purchase orders, item receipts and vendor bills, and Oracle offers add-ons for capturing bills. Reading each invoice, matching it and following up on differences is still largely manual. engini automates that part on top of NetSuite, through the NetSuite account you connect.

Can AI create vendor bills in NetSuite from emailed PDF invoices?

Yes. The workflow reads each PDF with the invoice reader in engini AI Tools, and an AI agent step creates the vendor bill in NetSuite when the invoice matches the purchase order and the item receipt.

How does the three-way match work?

The agent reads the purchase order and its item receipt from NetSuite and compares them with the invoice lines: item, quantity and unit price. You decide the tolerance in the agent’s instructions, for example exact quantities and prices within one percent.

What happens when an invoice does not match?

Nothing is created. The agent posts a short note to Slack or Teams with the invoice, the purchase order and the exact difference, for example 40 units billed and 36 received, so the buyer or the warehouse can resolve it.

Do our NetSuite approvals still apply?

Yes. engini creates the bill through the NetSuite account you connect, so that account’s role limits what it can do, and if you route vendor bills for approval in NetSuite, new bills follow that routing. engini itself has no approval step before an agent action.

How is this different from NetSuite Bill Capture or an AP SuiteApp?

Those work inside NetSuite. engini runs the whole flow across your inbox, NetSuite and Slack or Teams, with an AI agent doing the matching, and the same connection serves your other agents and workflows. It complements NetSuite rather than replacing anything in it.

How fast can we try it?

Start free, connect NetSuite with token-based authentication (your NetSuite administrator sets up the integration record and role), connect your inbox, and build the workflow in Workflow Studio or with the engini skill.