Source connector

Intacct connector

Intacct integration for databases, warehouses and BI tools

Cloud financial management and general ledger. Datrise captures Intacct entities such as journal entries, accounts, invoices, bills, customers and GL transactions, then lands normalized and typed models for warehouse reporting, attribution, and AI workflows.

The Sage Intacct Web Services XML API (xmlgw.phtml) authenticates with username / password, service account, incremental runs key on WHENMODIFIED.

Of the 6 objects, 4 sync as upserts keyed on the primary key and 2 as append-only streams, so each incremental run moves only what changed since the last watermark. Every object lands in its own table (for example `intacct_journal_entries`) with a schema derived from the Intacct API rather than a flattened CSV, in any of the 43 supported destinations.

Datrise is in early access: pick a destination below to open the Intacct pipeline page, and join the waitlist to get the Intacct connector with guided onboarding.

Incremental syncSchema-aware mapping43 destinations available

What Intacct data Datrise extracts

Each object lands in its own typed table. Sync mode is derived from the object: history-style objects append, everything else upserts.

Object	Landing table	Sync mode
journal entries	intacct_journal_entries	Upsert by primary key, incremental on updated-at
accounts	intacct_accounts	Upsert by primary key, incremental on updated-at
invoices	intacct_invoices	Append-only, incremental by timestamp
bills	intacct_bills	Upsert by primary key, incremental on updated-at
customers	intacct_customers	Upsert by primary key, incremental on updated-at
GL transactions	intacct_gl_transactions	Append-only, incremental by timestamp

Intacct API: setup facts for the connector

Verified against the vendor documentation on 2026-09-02. Unknown values are left blank rather than guessed.

API	Sage Intacct Web Services XML API (xmlgw.phtml)
Authentication	username / password, service account — Two-level auth: a Sage-issued Web Services sender ID/password plus company credentials (company ID + user ID + password), or a session ID from getAPISession reused across calls.
Pagination	offset — get_list / readByQuery use numeric offset with a documented recommendation to keep each page under 1,000 records.
Rate limit	Not published
Incremental cursor	WHENMODIFIED — A newly created record has WHENMODIFIED equal to WHENCREATED, so filtering OBJECT.WHENMODIFIED > lastPolledAt captures both new and updated rows in one query; splitting them requires comparing WHENCREATED client-side.
Webhooks	Not published
Bulk export	No
Deletes detectable	No

Official API reference

What bites when replicating Intacct

Intacct documents no fixed per-minute rate limit; instead the gateway processes roughly 5 requests concurrently per tenant out of 100 simultaneous requests, queuing the rest for about 5 seconds in first-in-first-out order before a GW-0010 429 is returned.
The docs explicitly recommend limiting `get_list`/`readByQuery` queries to fewer than 1,000 records and manipulation calls (create/update) to fewer than 100 records per request to avoid the 15-minute request timeout.
Sage's own guidance says never to use the delete operation because it severs audit-history linkage; most objects are deactivated rather than deleted, so a WHENMODIFIED poll alone cannot detect true row removals.
The API is XML-only over HTTP POST to a single xmlgw.phtml endpoint with Content-Type application/xml; there is no JSON request format.

Compare this against every other documented API

Popular destinations for Intacct

Choose a destination below to open the ready pipeline page.

A
Airtable
Relational spreadsheet destination for ops and go-to-market teams.
View pipeline
A
Amazon Athena
Serverless SQL over S3 data lake tables.
View pipeline
A
Amazon DynamoDB
Serverless key-value and document store on AWS.
View pipeline
A
Amazon QuickSight
AWS serverless BI with SPICE and embedded analytics.
View pipeline
A
Amazon Redshift
AWS petabyte-scale warehouse with Spectrum.
View pipeline
A
Amazon S3 Data Lake
Object storage landing zone for parquet and snapshots.
View pipeline
A
Apache Superset
Open-source BI for SQL exploration, charts, and dashboard publishing.
View pipeline
A
Azure Data Lake Storage
ADLS Gen2 object storage for analytics workloads.
View pipeline
A
Azure Synapse
Microsoft analytics workspace with SQL pools.
View pipeline

Intacct connector FAQ

What Intacct data does the connector extract?: 6 objects: journal entries, accounts, invoices, bills, customers and GL transactions. Each lands in its own table with types preserved; history-style objects (2: invoices and GL transactions) load as append-only streams.
Is the Intacct integration incremental?: Yes. After the initial full load, every run reads only records changed since the last watermark (updated-at or event timestamp) and applies an upsert or an append depending on the object.
Where can I load Intacct data?: Into 43 destinations: relational databases, cloud warehouses, data lakes, spreadsheets and BI tools. Each Intacct → destination pair has its own page with the object-to-table mapping.

Related sources

Other sources in the same category, each with its own connector page.

Early access

Launch your Intacct pipeline with guided onboarding

Join the waitlist to get priority access for Intacct integrations with guided setup, schema-aware mapping, and production-grade incremental sync.