Sage Intacct to Microsoft Fabric: ERP Data Integration Guide
Sage Intacct offers three distinct data extraction mechanisms for analytics - DDS, REST API, and XML Web Services - each mapping to a different Fabric integration architecture depending on volume, latency, and engineering capacity.
Connecting Sage Intacct to Microsoft Fabric gives finance-led organisations something most mid-market ERP integrations have historically lacked: a direct, governed path from the general ledger, accounts receivable, accounts payable, and project accounting data into a unified analytics estate where it can be combined with operational, CRM, and workforce data without manual exports or reconciled spreadsheets. Sage Intacct's open API architecture and its native Data Delivery Service make it one of the more analytically extensible mid-market ERPs - but there is no native Fabric connector, and the right extraction path depends on data volume, latency requirements, and the engineering capacity your team wants to invest.
This guide covers every production-viable path for Sage Intacct to Microsoft Fabric integration: DDS exports landed in OneLake, REST and XML API pipelines in Fabric Data Factory, CData Sync continuous replication, and Fivetran's fully managed connector. It is written for data engineers, analytics managers, and finance-technology leaders who want to build a trustworthy financial analytics layer on Fabric without owning a custom pipeline indefinitely.
As of July 2026, Microsoft Fabric Data Factory does not include a native first-party Sage Intacct connector. All production-grade Sage Intacct to Microsoft Fabric integration paths use DDS exports, Sage Intacct's REST or XML API via the generic REST connector, CData Sync, or a managed third-party connector such as Fivetran. Sage Intacct has also designated its XML API as legacy as of 2025 - all new features and objects are released via the REST API only, though the XML API remains fully supported for existing integrations.
Why Move Sage Intacct Data to Microsoft Fabric
Sage Intacct is built for financial control - multi-entity consolidation, dimensional accounting, project-based revenue recognition, and ASC 606 compliance. It does these things well. What it does not do well is answer the cross-functional questions that a finance leader or CFO needs for strategic decision-making: gross margin by customer segment combining ERP and CRM data, headcount cost allocation joined to project profitability, cash flow forecasting that incorporates pipeline data from the sales system. These questions require Sage Intacct data to live alongside data from other systems in a shared analytical environment - which is exactly what Microsoft Fabric's OneLake architecture provides.
The specific value for Sage Intacct customers landing data in Fabric is that Power BI can operate in DirectLake mode against the Lakehouse SQL endpoint - meaning financial dashboards refresh against live data without import overhead, sensitivity labels from Fabric apply to financial data automatically, and the same GL data that powers a Power BI P&L also feeds an AI agent or a notebook running a cash flow forecast. For Power BI consulting teams building financial analytics on Fabric, Sage Intacct's dimensional data model - entities, departments, locations, projects - maps cleanly to a star schema without heavy transformation.
"A finance leader who can only see Intacct data inside Intacct is flying half-blind. The value of landing Intacct in Fabric is that the GL, AP, and project data that lives in the ERP becomes usable alongside everything else the business runs on - without a spreadsheet in between."
Sage Intacct Extraction Mechanisms: What's Available
Sage Intacct offers more native extraction flexibility than most mid-market ERPs. Understanding the three available mechanisms - DDS, REST API, and XML Web Services - is a prerequisite for choosing the right Fabric integration architecture, because each carries different volume limits, latency characteristics, and setup complexity.
https://api.intacct.com/ia/api/v1/. Authenticated with OAuth 2.0. All new Sage Intacct objects and features are released on the REST API only. Suitable for Fabric Data Factory REST connector pipelines and for organisations that want a clean, maintainable API-based integration without the XML overhead of the legacy SOAP API.Path 1 - Data Delivery Service (DDS) to OneLake
For organisations that need to export large volumes of Sage Intacct financial data into Fabric - full GL transaction history, complete AR aging, multi-year project actuals - DDS is the most purpose-built extraction mechanism available. It is designed specifically for cross-system analytics use cases, processes millions of records without API rate limit constraints, and runs asynchronously so it doesn't impact live Intacct users during business hours.
How the DDS to OneLake path works
GLENTRY), GL account balances (GLACCOUNTBALANCE), AR invoices (ARINVOICE), AP bills (APBILL), vendors, customers, employees, projects, and any custom objects. Configure delivery frequency - daily, weekly, or on-demand. Enable change-extract (delta) mode after the initial full extract; change extracts are limited to one per hour per object. DDS separates created/updated records from deleted records, allowing your Fabric pipeline to handle each independently.Only one DDS job per object type can be in the queue or processing at a time - if a second job is submitted while one is running, it is cancelled. Run full extracts no more than once per 24 hours per object. DDS is not configured separately per Intacct entity in multi-entity companies - extraction always occurs from the top level. The GLACCOUNTBALANCE and GLResolve objects don't support the Synchronization option, which means they may reflect data at different points in time than other objects in the same batch - account for this when building consolidated financial reports.
Path 2 - Fabric Data Factory REST API Pipeline
For organisations that don't have a DDS subscription, want more control over extraction logic, or need to extract specific objects on a triggered basis rather than a scheduled batch, the Sage Intacct REST API via Fabric Data Factory's generic REST connector is the alternative. As of 2025, Sage Intacct recommends the REST API for all new integrations - it uses standard OAuth 2.0, returns JSON, and covers all current Intacct objects and features.
REST API authentication and pipeline pattern
The Sage Intacct REST API is accessed at https://api.intacct.com/ia/api/v1/ using OAuth 2.0 bearer token authentication. Configure the REST linked service in Fabric Data Factory with your OAuth credentials. For incremental loads, use the whenModified query parameter (where supported by the object) to filter records changed since a stored watermark timestamp. Store the watermark in a Fabric Lakehouse metadata table and update it after each successful pipeline run.
For objects where the REST API does not support whenModified filtering, a full extract with deduplication in the Lakehouse is the pragmatic approach - Sage Intacct's financial objects tend to be append-heavy (transactions don't change once posted) so full extracts of core GL objects are smaller than the row counts suggest once filtering by fiscal period is applied.
XML API (for existing integrations)
Teams with existing XML Web Services integrations can continue using them via the generic HTTP connector in Fabric Data Factory - constructing the SOAP XML request body in a Web Activity and parsing the XML response. The XML API uses Sender ID and password authentication rather than OAuth 2.0, which requires storing credentials securely in Azure Key Vault. Because Sage has designated the XML API as legacy, any new build should start with the REST API - but existing XML integrations work and are fully supported.
Path 3 - CData Sync Replication to OneLake
CData Sync provides automated, continuous Sage Intacct data replication directly to OneLake in Microsoft Fabric - listed explicitly as one of CData's most popular integration sources alongside Salesforce, Workday, and Dynamics 365. The integration handles Sage Intacct's API authentication, object discovery, incremental change detection, schema mapping, and delivery to OneLake without requiring custom pipeline engineering.
CData Sync connects to Sage Intacct via the XML Web Services or REST API under the hood, abstracts the SOAP XML complexity into a SQL-like interface, and replicates selected objects continuously into OneLake in a format the Fabric Lakehouse can query immediately. For organisations where the engineering investment in a custom Fabric pipeline is not justified - either because the team is small, because Intacct is one of many source systems in a broader Fabric programme, or because time-to-production is the priority - CData Sync is the most operationally complete path currently available.
CData Sync is also the connector listed in the Open Mirroring partner ecosystem for Sage Intacct, meaning the replication architecture aligns with the same framework Microsoft uses for Salesforce and NetSuite in its Fabric mirroring partner network.
Path 4 - Fivetran Managed Connector
Fivetran provides a fully managed Sage Intacct connector that is part of its 700+ connector expansion for Microsoft Fabric and OneLake (March 2025). The Fivetran Sage Intacct connector handles the full ELT lifecycle: extraction from Intacct using the XML API with Sender ID authentication, incremental sync using timestamp-based attributes, schema representation in the destination, and delivery to OneLake. Fivetran also provides pre-built dbt data models for Sage Intacct - including general ledger, balance sheet, and profit and loss statements - which significantly reduce the transformation work required to turn raw Intacct data into analytics-ready financial tables.
One configuration note specific to Fivetran's Sage Intacct connector: the Needs Login for API setting on your Sender ID must be set to No in Sage Intacct - if it is set to Yes, all Fivetran API calls will fail. This is confirmed in Fivetran's setup guide and is a common configuration oversight that causes integration failures during initial setup. Fivetran stores timestamp-based attributes as TIMESTAMP in the destination - if previous syncs stored them as VARCHAR, dropping and re-syncing the affected tables is required to restore data integrity.
Sage Intacct API Reference for Fabric Engineers
https://api.intacct.com/ia/api/v1/objects/. OAuth 2.0 bearer token authentication. REST API reached full GA in 2025 and is recommended for all new integrations. New Sage Intacct objects and features are released on REST only.GLENTRY (general ledger detail transactions), GLACCOUNTBALANCE (account balances by period), ARINVOICE / ARINVOICEITEM (AR invoices and line items), APBILL / APBILLITEM (AP bills and line items), VENDOR, CUSTOMER, EMPLOYEE, PROJECT, DEPARTMENT, LOCATION. Custom objects created via Intacct Platform Services are accessible via both APIs.Sage Intacct to Microsoft Fabric: Path Comparison
| Dimension | DDS → Azure Blob → OneLake | REST API (Fabric Data Factory) | CData Sync | Fivetran |
|---|---|---|---|---|
| Engineering effort | Medium - DDS config + Fabric pipeline for blob pickup | High - OAuth, pagination, watermark logic | Low - configure and run | Low - point-and-click |
| Best for volume | ✓ Millions of records - designed for bulk export | Medium volumes - API rate limits apply | Any - API-based with managed throttling | Any - fully managed |
| Latency | Scheduled (daily / on-demand) | Scheduled (hourly / daily) | Near continuous replication | Scheduled or near real-time |
| Connector cost | DDS subscription (Sage) + Fabric Data Factory only | ✓ None beyond Fabric | CData Sync licence | Fivetran per-row pricing |
| Schema change handling | Manual - DDS schema changes require pipeline update | Manual | ✓ Automatic | ✓ Automatic |
| Pre-built financial models | ✗ - raw CSV, transformation required | ✗ - raw JSON, transformation required | ✗ - replicated tables, modelling required | ✓ dbt GL, P&L, balance sheet models included |
| Multi-entity support | ✓ - top-level extract includes all entities | ✓ - entity-scoped via API parameter | ✓ | ✓ |
| Custom objects | ✓ - DDS supports custom objects | ✓ - REST API covers custom objects | ✓ | ◑ - varies by connector version |
Financial Reporting on Sage Intacct Data in Fabric
Once Sage Intacct data is in OneLake, the analytics opportunities fall into two categories: pure financial reporting that replicates what Intacct's own reports produce - P&L by entity, AR aging, AP liability - but with Power BI's formatting, distribution, and self-service capabilities, and cross-functional analysis that combines Intacct data with other systems to answer questions the ERP alone cannot.
In the first category, the Fabric Lakehouse SQL endpoint makes GL and AP/AR data directly queryable via T-SQL, which means standard financial report patterns - period-over-period variance, entity consolidation, budget vs actuals - can be built in Power BI against live Intacct data without import latency. Sage Intacct's dimensional model (entity, department, location, project, class) maps directly to Power BI's slicer and cross-filter capabilities, making it straightforward to build CFO-level dashboards that match Intacct's own dimensions.
In the second category, landing Intacct alongside CRM data from Salesforce or Zoho CRM enables margin analysis by customer - combining Intacct's invoice and cost data with CRM's deal and opportunity data. Landing it alongside HR or payroll data enables project profitability analysis that incorporates actual labour costs. These are the reports that create strategic value for finance leaders and that no single system can produce alone. For data engineering teams building the transformation layer, Sage Intacct's dimensional GL model is well-structured for a star schema - dimensions replicate cleanly into dimension tables, and GL transactions become the fact table for most financial analytical queries.
Common Mistakes in Sage Intacct to Microsoft Fabric Migrations
Attempting DDS without confirming the subscription is active. DDS is a paid add-on subscription, not a default Sage Intacct feature. Teams that assume it's available and start building a DDS-based Fabric pipeline before confirming the subscription is active lose weeks. Confirm DDS is enabled under Company > Admin > Subscriptions before any architecture decision is made.
Running multiple DDS jobs for the same object simultaneously. If a second DDS job for the same object is submitted while one is already queued or processing, the second job is cancelled without warning. Build explicit job-status monitoring into any orchestration that triggers DDS jobs from outside Intacct - poll for completion before triggering the downstream Fabric pipeline that picks up the CSV files.
Building new integrations on the XML API. Sage Intacct designated the XML API as legacy in 2025. While it remains supported and existing integrations are unaffected, new Fabric pipeline builds should use the REST API. Teams that build on the XML API today are creating technical debt that will need to be migrated as Sage continues to shift its development investment to REST.
Missing the Fivetran Sender ID setting. Fivetran's Sage Intacct connector requires the Needs Login for API setting on the Sender ID to be set to No in Intacct. This is a non-obvious configuration that is not visible during Fivetran setup - it must be confirmed in Sage Intacct by contacting Sage Support or navigating to the Sender ID configuration. All API calls fail silently if this setting is wrong.
Treating GLACCOUNTBALANCE as a transaction log. The GLACCOUNTBALANCE object in Sage Intacct represents period-end balances, not individual transactions. Teams that use it as their primary GL extract miss the transaction-level detail in GLENTRY, which is required for most audit, variance, and drill-down use cases. Extract both objects - GLACCOUNTBALANCE for balance-sheet views and GLENTRY for transaction-level reporting.
Conclusion
Sage Intacct to Microsoft Fabric integration is well-supported by both Sage's own extraction capabilities and a mature partner ecosystem - but it requires a deliberate choice between four distinct paths rather than a single native connector. For high-volume financial data at scale, DDS to Azure Blob to OneLake is the most architecturally appropriate path. For teams building a multi-source Fabric programme with existing API pipeline capabilities, the REST API approach provides full control without connector cost. For the fastest time to production with pre-built financial models, Fivetran's managed connector is the most complete offering. For near-continuous replication without custom engineering, CData Sync is the clean mid-ground.
Whichever path you choose, the outcome is the same: Sage Intacct's GL, AP, AR, and project data in OneLake alongside the rest of your operational estate - queryable in Power BI, usable by AI agents, and governed by Fabric's sensitivity and access control layer. Numlytics specialises in Microsoft Fabric migration and financial analytics delivery for mid-market organisations. Speak with a certified Fabric consultant to scope the right Sage Intacct integration path for your estate.