01
Tenant-specific entities
Discover available DAC entities from OData metadata rather than assuming every Acumatica installation exposes the same tables.
Integrations · ERP
Acumatica reporting on authorized tenant data.
Connect the read-only Acumatica OData route to Permute. Discover the entities exposed by your tenant, select the records needed for a report, and align them with related operating sources.
Read-only OData connector
Acumatica
ERP data
Permute financial intelligence layer
Connected, reconciled, and ready for use
ReportingAnalyticsAI
What this connection unlocks
Put Acumatica into the same trusted layer as the rest of your business.
02
Explicit business definitions
Keep company, branch, currency, status, and posting-date scope beside the metric your team approves.
03
Repeatable source reads
Refresh selected records and retain source references. Review incomplete or failed reads before treating a result as current.
Data, setup, and reporting scope
| Source records | Reporting use |
|---|---|
| Authorized DAC collections | Read the collections the tenant exposes and the connected identity can access. |
| Authorized singleton entities | Read individual entities where the tenant metadata and endpoint support them. |
| Selected business fields | Confirm usable identifiers, dates, statuses, amounts, and currency in the discovered schema before defining a report. |
Before connecting
Confirm the customer instance URL and configure the Acumatica Connected Application for OAuth. The connector uses the tenant DAC OData endpoint; the connected identity must be able to read the selected entities.
Entity availability depends on tenant permissions, enabled modules, version, and customization. Inspect metadata and a sample of the actual records, then validate pagination and report totals against an approved source extract. Do not promise a fixed finance or inventory table list before that check.
Freshness and limits
Reporting uses completed source reads. Record the extraction time and business cutoff separately; an import completed today can still contain yesterday’s postings. Surface failed reads instead of substituting an empty dataset.
The connector reads data and does not post journals, update stock, or alter Acumatica records. Permute can apply declared reporting rules, but your finance owner chooses accounting treatment and remains responsible for corrections in the source system.
Synthetic worked example
Check the posting status before totaling
Synthetic USD example: the finance owner defines a report as released records dated through September 30. The tenant exposes both a released $20,000 record and an unreleased $3,000 record.
| Source reference | Status | Amount |
|---|---|---|
| REC100 | Released | $20,000 |
| REC101 | Unreleased | $3,000 |
The declared report totals $20,000, not $23,000. Preserve REC101 as an excluded record with the status rule, then confirm that the tenant’s actual status field means what the definition assumes. This example does not prescribe accounting policy.
One connected workflow
From Acumatica data to trusted business answers.
01
Connect
Bring Acumatica data into Permute.
02
Reconcile
Align records, fields, and definitions.
03
Use
Power reporting, analytics, and AI.
Start with one workflow
Verify an Acumatica reporting scope
Bring the tenant version, required entities, and one approved report. Review source availability and mappings before expanding reporting access.