Skip to content
Connection Guide

Connect Acumatica Cloud ERP Without Breaking the Audit Trail

Use this guide to connect Acumatica Cloud ERP or confirm the export-based path that fits your environment. Aurora keeps source, timestamps, ownership, and collection history attached so the first run becomes reusable proof instead of one-off setup work.

Connector Summary
Connection typeDirect connection
CategoryErp
Checklist4 steps
Want help with rollout?
We'll confirm what can be automated, what stays export-based, and how to keep the first evidence record clean.

First-Run Checklist

Use this sequence to connect Acumatica Cloud ERP and make sure the first collection lands cleanly.

  1. 1
    Choose the supported auth_mode branch and provide the matching secrets and configuration values for that branch.
  2. 2
    Populate surface_artifact_names as structured JSON that names the exact user, role, role-assignment, and audit endpoints or OData surfaces exposed by the customer tenant.
  3. 3
    Populate config_snapshot_object_bundle as structured JSON describing each configuration object path Aurora should collect for app_config_snapshot.
  4. 4
    Validate the chosen tenant surfaces with swagger.json or OData $metadata before enabling scheduled sync.

Credentials and Secrets

The keys, secrets, or tokens Aurora uses to authenticate and collect proof.

client_secretrefresh_tokenintegration_password

Recommended Access

Aurora only asks for the minimum read access needed for collection and checks.

Access requirements depend on the collection mode and scope you choose.