← Acumatica integration

The partner in the room

Acumatica sells almost exclusively through VARs. There is no direct sales force, which means **every live instance has an implementation partner behind it** — they configured it, they customized it, they hold the admin rights, and they are the customer's first call when something breaks.

You will not connect to an instance without meeting this fact. Plan for it.

Why it dominates the complaints

The recurring theme in customer feedback is not the software. It is variance in implementation. The same product produces a delighted customer and a frustrated one depending on who deployed it, and users say so directly — the common read on Acumatica frustration is that it is sold through partners, so the partner is the experience. Practitioners put it plainly: with Acumatica the partner matters more than the software, because they become the implementation team, the configuration advisor, and the long-term support extension of the customer's own staff.

Two consequences that are ours to handle:

Their instance is not a stock instance. Custom fields, renamed entities, sometimes an entirely separate contract endpoint. This is why discovery is a step in this provider rather than a hardcoded catalogue — see schema-discovery.

Integration problems are usually cataloguing problems. The pattern integrators report: a client believes they need three integrations, discovery finds seven, two of which are spreadsheets nobody documented as part of the operational picture. Expect the map of where data actually lives to be wrong, and expect finding out to be half the work.

Working with them, not around them

The partner can hand over a read-only user and an instance URL in ten minutes, or they can be the reason nothing moves for six weeks. Which one you get depends largely on whether they read you as a threat.

Useful framing: we read, we do not re-implement. We are not bidding for their configuration work, and a customer who gets more value from their ERP is a customer who renews with them. That is true, and it is worth saying early.

Practical asks, in rising order of how much you need them:

  1. Instance URL and tenant name — the customer knows these; no partner needed.
  2. A read-only user — five minutes of admin time. Ask for read-only explicitly; it is a much easier yes than "an account."
  3. A sandbox instance — customers on Always Current can get one free from their partner. Real schema, real customizations, no production risk. This is the best first target and worth asking for before anyone offers prod.
  4. Push notification setup — a screen, not a build, but it needs their hands. See push-notifications.

Know what the platform now ships

Acumatica shipped an AI Assistant in 2026 R1 — natural-language questions over ERP data, returning text, charts, and tables with drill-down, plus an AI Studio for workflow automation. Assume the customer and their partner have seen it.

The honest distinction is not "we can ask questions in English"; that is now a checkbox in the product. It is that a scene spans systems the ERP cannot see — the floor, the spreadsheets, the other ERP in another country — and holds the result as something durable and shareable rather than a chat answer. Lead with the join, not the chat.