< Back to all integrations

Acumatica

ERP & Finance

Connect AI agents and workflows to Acumatica: customers, items, sales orders, shipments, invoices, bills, payments and inquiries, with push notifications.

Book a demo
[ Acumatica + engini ]

Acumatica for AI agents and workflows.

engini lets your AI agents and workflows work in Acumatica Cloud ERP: read and create customers, vendors and stock items, enter sales orders and create shipments, release invoices and payments, enter bills and journal transactions, read any generic inquiry, and start a workflow the moment Acumatica pushes a change. Distribution, manufacturing and services teams keep one record of the business without keying it twice. Connect from Claude, ChatGPT or Cursor over MCP, from your code, or build in Workflow Studio.

MCPPython and TypeScript SDKCLIREST APIWorkflow Studio
Sign-inOAuth 2 through a connected application in Acumatica
ReachCustomers, vendors, stock items, sales orders, shipments, invoices, bills, payments, journal transactions, purchase orders, projects and generic inquiries
TriggersPush notifications from Acumatica, as records change
[ 01 / What agents can do ]

What your agent can do in Acumatica. Every tool is one you allow or leave out.

The Acumatica tools in engini, grouped by what they change. Read tools are safe to hand out widely. Write and delete tools go only to the agents that need them.

Read

Get Customers, Get Vendors, Get Stock Items

Find a customer, vendor or item, with balances and quantities.

Read
Get Sales Orders, Get Shipments, Get Invoices

Read orders, what shipped and what was billed.

Read
Get Bills, Get Payments, Get Purchase Orders

Read payables and purchasing.

Read
Get Inventory Summary

Read quantities on hand and available, by warehouse.

Read
Run Generic Inquiry

Read any generic inquiry your team built.

Read

Write

Create or Update Customer, Vendor or Stock Item

Keep master data current.

Write
Create Sales Order, Create Shipment, Confirm Shipment

Enter an order and ship it.

Write
Create Invoice, Release Invoice, Email Invoice

Bill a customer and send the invoice.

Write
Create Bill, Create Payment, Release Payment

Enter supplier bills and record payments.

Write
Create Journal Transaction, Create Purchase Order

Post to the ledger or raise an order.

Write
Add Attachment

Attach a file to any record.

Write

Delete

Delete Record

Remove a record that is not yet released.

Delete

Any endpoint

Send API Request

Call any Acumatica endpoint or custom endpoint, with the sign-in added for you.

Any call

Triggers

Push Notification Received

A record in a generic inquiry you choose was added, changed or removed.

Event
Check for New Sales Orders, Check for New Invoices

Orders and invoices created.

Scheduled

A trigger starts a workflow, and a workflow can include an AI agent step. In Code, a trigger delivers the event to your own endpoint.

[ 02 / Connect your agent ]

Connect your AI agent to Acumatica. Four ways in, one set of permissions.

MCP

Claude, ChatGPT, Cursor

Create an MCP server in engini with your Acumatica connection and only the tools you choose. Add its address to your client and sign in through engini. There is no key to copy.

MCP client setup →
SDK

Python and TypeScript

Hand your agent a toolset of Acumatica tools. The SDK gives OpenAI and Anthropic models the tools in the format they expect and runs the ones they pick.

SDK guide →
CLI

For coding agents

The engini CLI connects Acumatica and runs its tools from a terminal, with machine-readable output, so an AI coding agent can drive it without getting stuck.

CLI guide →
REST API

Any language

Every Acumatica tool is an endpoint. Call it with exact inputs from a scheduled job or a sync, with no model in the loop.

API reference →
MCP in four steps
In engini, connect Acumatica and create an MCP server with that connection and the tools this agent may use.
Claude: Settings, Connectors, Add custom connector, then paste the server address.
Cursor: add the address to .cursor/mcp.json. Claude Code: claude mcp add.
Sign in through engini when the client asks. The agent sees only the tools you chose.
Cursor, connected to Acumatica through engini
// .cursor/mcp.json: Cursor, connected to Acumatica through engini
{
"mcpServers": {
"engini-acumatica": {
"url": "<your engini MCP server address>"
}
}
}

Create the MCP server in engini with your Acumatica connection and the tools this agent may use, then paste its address. The client signs in through engini on first use. Claude, VS Code and other clients take the same address: see the MCP client setup guide.

Try asking your agent
“What is Acme's open balance, and which invoices are overdue?”
“Create a sales order for 30 units of AACOMPUT01 for ABARTENDE.”
“How many units of item CONAIRT1 are available in the wholesale warehouse?”
“Release yesterday's invoices and email them.”
“Which purchase orders from Contoso are still open?”
“Run the Open Sales Orders generic inquiry for this week.”

Each request runs through the Acumatica tools in the agent's toolset or MCP server. If a tool is not allowed, the agent cannot call it.

[ 03 / What teams build ]

What teams build on Acumatica. Agents and workflows, across systems.

Order to cash

Store orders into Acumatica

Paid orders from Shopify or WooCommerce become Acumatica sales orders, and tracking numbers go back to the store when they ship.

ShopifyWooCommerceAcumatica
Revenue operations

Won deals become customers and orders

A deal won in HubSpot or Salesforce creates the customer and the sales order in Acumatica.

HubSpotSalesforceAcumatica
Accounts payable

Bills from the inbox

A supplier invoice from Outlook is read by an agent and entered as an Acumatica bill against the purchase order.

OutlookAcumatica
Operations

Stock and orders on request

An agent in Slack answers availability, order status and what shipped. Its toolset holds read tools only.

SlackAcumatica

Every integration runs both ways, so any of these flows can also run in reverse. These are examples, not the limit: any flow between Acumatica and another system engini connects is available.

[ 04 / Agent Policy ]

You decide what each agent may do in Acumatica. engini enforces it on every call.

Toolsets

Only the tools you allow

A toolset lists the Acumatica tools an agent may call and the connection each one uses. Give one agent read tools only and another the write it needs. engini refuses any call outside the toolset.

MCP servers

Scoped when you set them up

An MCP server exposes only the connections and tools chosen when it is created, and engini shows who uses each server.

Identity

Whose permissions apply

Connect a person's own Acumatica account and engini acts as that person, with their Acumatica permissions. Use a shared integration account and it acts as that account. Every run is recorded under the user who started it.

Credentials

Kept out of prompts

Your agent never needs your credentials: engini stores them and adds them when it runs each call, so keys stay out of prompts and tool inputs.

Audit

Every call on record

Every call lands in History and the audit log, which you can export or stream to your SIEM.

Environments

Test before production

Workspaces keep teams apart, and development, staging and production environments keep a test agent away from live data.

SOC 2 Type IIISO 27001GDPRSecurity at engini →
[ 05 / Set up ]

Connect Acumatica in three steps. Then decide what each agent may do.

Step 01

Sign in to Acumatica

In Acumatica, add a connected application for engini, then add an Acumatica connection with your instance URL and tenant and sign in with a user whose role covers only what the workflows need.

Step 02

Choose the tools

Add the connection to an MCP server or a toolset with only the tools each agent needs.

Step 03

Build or ask

Use the connection as a step in a workflow, or ask your agent to work in Acumatica from Claude, ChatGPT, Cursor or your own code.

[ 06 / Questions ]

Acumatica and engini. Straight answers.

Can an AI agent write to Acumatica, or only read?

Both. engini has tools to create and update customers, vendors, items, orders, shipments, invoices, bills, payments and journal transactions, release documents, and delete records. Whether a given agent may use them is up to you: give it a toolset or an MCP server with read tools only, and it cannot call the rest.

Can it read our generic inquiries and custom endpoints?

Yes. Run Generic Inquiry reads any inquiry your team built, and Send API Request reaches custom endpoints and fields you added.

Does the agent act as me in Acumatica?

It acts as the Acumatica user who signed in, with that user's role and branch access. Every run is recorded under the person who started it.

Can a change in Acumatica start work?

Yes. Set up a push notification on a generic inquiry and Acumatica tells engini the moment a record changes. Scheduled triggers check for new sales orders and invoices. A workflow can include an AI agent step.

What if the tool I need is not listed?

Use Send API Request to call any Acumatica API endpoint through the same connection, and give it only to the agents that need it.