Acumatica

Status: planned — not available to connect in Tack yet. These steps prepare the integration; creating vendor credentials does not enable it in the app.

Planned workflows

Planned for Acumatica:

You text	What would happen in Acumatica
“What did Dale’s Hardware order last quarter?”	Reads order history
“Reorder the same”	Drafts a sales order

These are intended workflows, not a guarantee that every operation is exposed by the vendor. Each must pass the API and permission checks below before release.

Before you start

Record the HTTPS instance URL, Acumatica version, tenant, branch and the endpoint/version the customer exposes. An administrator and the customer’s implementation partner may both be needed for customized workflows.

Developer setup — once

1. Use the contract-based REST API and OAuth authorization-code flow. Build against the customer’s supported contract, not an assumed universal endpoint version.
2. Supply the callback URL and requested api and, if needed, offline_access scopes. Implement refresh and tenant-specific token storage.
3. Identify the entities, fields and actions needed for customer lookup and draft sales orders. Consult the current Integration Development Guide.

Customer setup — repeat for each instance/tenant

1. Sign in to the target tenant as an administrator and open Connected Applications (SM303010).
2. Create the agreed application, choose the Authorization Code flow and register the developer’s exact redirect URI.
3. Add a shared secret where required and store it securely with the generated client ID. Confirm the tenant in that ID; registrations are tenant-specific.
4. Give the authorizing user the necessary screen/entity permissions and branch access. Confirm the required fields/actions exist in the published web-service endpoint.
5. Complete OAuth authorization and save the instance, tenant, branch and contract version with the connection.

Use Acumatica’s application registration guidance and authorization-code reference. Menu details can differ by release.

Verify write access

Read a test customer and stock item in a test tenant. Create an order on hold, then read it back and verify branch, warehouse, unit of measure, prices and custom fields. Do not invoke release, shipment or invoicing as a connection test.

Disconnect and troubleshoot

Have the admin revoke the application’s access through Connected Applications and retire its secret/tokens. Check contract version, missing custom fields, role rights and API-session limits independently. An entity absent from the endpoint needs a contract change, not a more privileged login.

Who completes the work?

An agent/developer can implement the connector, field mappings and automated checks. A customer administrator must authorize account access and permissions; the vendor must approve any restricted partner access. A business operator verifies the test records before production use. Follow the shared setup and release checklist for credential handling, approval gates and launch checks.

Setup guidance reviewed October 23, 2026. Vendor menus and entitlements can change; unresolved details are called out above.