Incumbent ledgers · acquired

Sage Intacct

A cloud general ledger and financial suite for mid-sized businesses, owned by Sage.

sage.com/en-us/sage-business-cloud/intacct · founded 1999 · San Jose, California (parent The Sage Group plc, Newcastle upon Tyne, UK) · researched 2026-10-10

Scope: Sage Intacct is a multi-entity, dimensional general ledger with AP, AR, cash management, order management, purchasing and reporting, plus paid modules for projects, fixed assets, inventory, subscription billing, consolidation and more. It is sold through quotes and partners to finance teams that have outgrown QuickBooks or Xero. It does not run on your machine, and it does not keep a copy of your books outside Sage's cloud unless you buy or build an extract.
Backing: Raised about $130M in venture funding 2000-2014 (HWVP, Battery Ventures, Bessemer, Sigma, Emergence); last round $30M in 2014 at a $211M valuation. Acquired by The Sage Group plc (LSE: SGE) for $850M, announced 25 July 2017.
Serves: mid-market, enterprise, accountants
Covers: ledger, bank, invoicing, close, reporting, spend
To ownpurse: Neighbour. Intacct is the mid-market ledger that the AI ERPs (Rillet, Campfire, DualEntry) pitch to replace. ownpurse starts with smaller books, but Intacct shows where a growing business ends up and how a mid-market ledger rations and prices API access.

What it is

Sage Intacct is a cloud financial system for mid-sized businesses: a multi-entity general ledger with dimensions, accounts payable and receivable, cash management, purchasing and order entry, and reporting, with paid modules for projects, fixed assets, inventory, subscription billing and consolidation (Wikipedia). It was founded in San Jose in 1999 and bought by The Sage Group for $850M in July 2017 (TechCrunch). It is what a finance team moves to after QuickBooks or Xero, and it is the system Rillet, Campfire and DualEntry name when they pitch an AI-native replacement (ERP Research).

It does a lot well. Reviewers credit its dimensional reporting and multi-entity consolidation, and its growth inside Sage is real: in the year to 30 September 2025, Intacct revenue in the US grew 23% to £461m, more than 45% of Sage’s US revenue (Sage FY25 results).

How it works

You buy it on an annual quote, usually through a partner who implements it. Sage does not publish prices; third-party estimates put a single-user Core Financials subscription at about $9,000 to $15,000 a year and typical mid-market spend at $25,000 to $75,000, before implementation (ERP Research). Those figures are estimates, not Sage’s.

Intacct keeps an audit trail on records, and an Audit History data source that shows who changed what, when, and each field’s value before and after, captured since May 2016 (Intacct help). That is more history than most small-business ledgers expose, but the records themselves are current state; you cannot ask for the books as of a past moment.

Data and access

Intacct has two APIs. The REST API, with OAuth 2.0, became generally available in 2025 Release 1, and Sage says new objects and features ship only there; the XML API is legacy but supported, with no sunset date (developer.intacct.com). Both need a paid Web Services subscription and a Web Services user type (release note).

Access is metered. Sage says companies that exceed their monthly Performance Tier entitlement pay overage, and that it does not block the calls; third parties put Tier 1 at 100,000 transactions a month, with low concurrency and overage of $0.15 per 10-transaction pack, and note that Smart Events and scripts count too (ClonePartner). Bulk export is the Data Delivery Service, a paid add-on that writes CSV per object to S3, Azure, Box, Dropbox or Google Drive: full extracts once a day, changes hourly, with attachments and audit history left out. There is no single export of a whole company.

Agents

Sage builds AI in two directions. Sage Copilot sits inside the product, with a Finance Intelligence Agent for plain-language questions, rolling out to US and UK customers in a phased early adopter programme (Sage FY25). The Sage Intacct AI Gateway goes the other way: REST plus a first-party MCP server that brings Intacct data to Claude, ChatGPT or your own agent. Sage describes the MCP server as read-only and governed by Intacct roles; writes go through the REST API (Baker Tilly). Administrators enable it and choose the role. It is not in Claude’s connector directory as of 10 October 2026, so connecting it is an admin build.

There is no approval gate on agent writes beyond Intacct’s own roles and approval workflows.

Customers

Intacct had 11,000 customers in 2017. Sage now cites strength in construction, real estate, not-for-profit and financial services, and rapid growth in the UK, Canada and South Africa. G2 shows about 4.3 of 5 from roughly 4,000 reviews. The complaints are consistent: a steep learning curve, custom reports that are rigid or complex, modular pricing that rises at renewal, and support that runs through partners (Capterra reviews).

History

Intacct was one of the first cloud ledgers and raised about $130M before Sage bought it. Sage, a UK company built on desktop accounting, bought Intacct to get a cloud product in North America, and has since made it its flagship for mid-sized businesses. Now the venture money has moved to AI ledgers that want to replace it, and Sage’s answer is automation inside the product plus an MCP gateway.

For ownpurse

Intacct is a neighbour, not a near-term connector. It shows the ceiling of the market ownpurse starts below, and what happens to API access as a ledger moves up-market: it becomes a line on the quote, metered by the transaction, with bulk export sold separately. Worth borrowing is the audit history (field, before, after, who, when), which maps directly onto facts with provenance, and a read-only MCP surface that obeys the same roles as people. A future Intacct connector would have to budget its reads against the monthly entitlement, which is the argument for an owner-held record that answers questions without calling Sage.

Data and access

Public API: Yes. REST (OAuth 2.0, generally available from 2025 Release 1) and a legacy XML Web Services API that still covers some objects and functions REST lacks (readReport, attachments).
Auth: OAuth 2.0 for REST; XML uses sender credentials plus company login. Both require the Web Services subscription and a Web Services user type.
Limits: Performance Tier 1 entitlement of 100,000 API transactions a month by third-party accounts; Sage says it does not block calls over the entitlement but charges overage. REST concurrency limits exist but are not published as numbers; Tier 1 reportedly allows about two synchronous connections. XML queries return up to 2,000 records a call.
What access costs: Web Services subscription is a paid part of the quote (price not published). Overage beyond the monthly entitlement is charged; one third party quotes $0.15 per 10-transaction pack. Data Delivery Service is a paid add-on. Apideck reports partner connector terms of $2,500 a year plus $0.015 per call.
Export: Report exports (CSV, Excel, PDF, Word, text); Data Delivery Service bulk CSV extracts per object to S3, Azure, Box, Dropbox, Google Drive or HTTP (full once a day, changes hourly); API reads. Attachments and some objects (supporting documents, audit history) are not in DDS. No single full-tenant export.
Notes: Sage says all new objects and features ship only in REST; XML is supported but legacy, with no published sunset date. Smart Events and scripts also consume the transaction entitlement.

Price

Model: Annual subscription, quote-based, priced by modules, entities and users, sold mostly through partners.
Entry: Not published. Third-party estimates put a single-user Core Financials subscription at about $9,000-$15,000 a year (2025-26 estimates).
Top: Not published. Third-party estimates put typical mid-market spend at $25,000-$75,000 a year and large multi-entity deployments over $100,000, plus implementation.
Notes: All figures are third-party estimates, not Sage's. A UK partner reported rate plans rising about 9% from 1 January 2024. Reviewers mention renewal price creep and modules adding cost.

Agents

MCP: official
AI features: Sage Copilot embedded in Intacct; a Finance Intelligence Agent for plain-language questions over Intacct data (US and UK, phased early adopter in 2026); Close Assistant, AI variance explanations and AP/reconciliation automation; the Sage Intacct AI Gateway (REST plus an MCP server) for outside AI tools.
Agent writes: The MCP server is read-only by Sage's own description. Agents can write through the REST API with a Web Services user whose role permits it.
Approval: No approval gate on API writes beyond Intacct's own role permissions and workflow approvals (for bills, payments, journal entries where configured). MCP access is limited by the assigned role; administrators enable the gateway and AI features.
Notes: Not listed as a Claude connector as of 10 October 2026. Third parties (CData and others) sell their own Intacct MCP servers. Some areas (project accounting, fixed assets) reportedly still rely on the XML API.

Integration and customers

Connects to: Sage Intacct Marketplace of partner apps (count not confirmed), bank feeds, Sage's own add-ons (AP automation, expense management via the acquired Fyle), and every major unified API (Apideck, Merge, Rutter, Codat and others).
Notes: Integrations are often built and maintained by implementation partners. API activity from every integration counts against one monthly entitlement, a common source of overages.
Scale: 11,000 customers at acquisition (July 2017). In Sage's FY25 (year to 30 September 2025), Sage Intacct revenue in the US grew 23% to £461m, over 45% of Sage's US revenue; ARR grew over 20% in the US and about 50% outside it.
Ratings: G2: about 4.3 of 5 from roughly 4,000-4,100 reviews (G2 comparison page snapshots, 2026). Capterra rating not confirmed.
What customers say: Praised for dimensions, multi-entity consolidation, reporting depth and fit for mid-market controllership. Complaints: a steep learning curve, rigid or complex custom reporting that pushes teams to BI tools, modular pricing that rises at renewal, and dependence on partners for support.

Timeline

1999
Founded in San Jose by Odysseas Tsatalos and David Chandler Thomas as one of the first cloud accounting applications.
2000
$10M Series A led by HWVP.
2014
Last venture round, $30M at a $211M valuation; about $130M raised in total.
2017-07-25
The Sage Group announces it will buy Intacct for $850M; Intacct reports 11,000 customers and about $88M revenue for the year to June 2017.
2025-02
REST API generally available (2025 Release 1); XML becomes legacy, new features REST only.
2025-11-04
Sage Intacct AI Gateway with an MCP server presented at Sage Future for Partners (per partner reports).
2025-11-19
Sage FY25 results: Intacct US revenue £461m, up 23%; Finance Intelligence Agent for US and UK customers.
2026-05
Sage announces expanded automation across core finance workflows; AI Gateway in an early adopter programme.

Borrow and avoid

Borrow: The audit history model: every change records who, when, field, value before and value after, and is reportable. Dimensions on line items as first-class facts. A read-only MCP surface that follows the same role permissions as people.
Avoid: Pricing API access by monthly transaction counts with overage fees, making bulk export a paid add-on, and offering no single export of the whole company.

Sources

Not confirmed against a primary source

The 100,000 transactions a month Tier 1 entitlement, the $0.15 per 10-transaction overage price and the concurrency figures come from third parties; Sage's own page returned 403 and does not publish numbers in what was retrieved.
Price of the Web Services subscription is not published.
All subscription price figures are third-party estimates.
The AI Gateway launch date (Sage Future for Partners, 4-5 November 2025) comes from partner and consultancy sources, not a Sage page read directly.
Early adopter status of the AI Gateway in May 2026 comes from a search summary of a Sage newsroom page that returned 403 when fetched.
G2 rating (about 4.3, roughly 4,000-4,100 reviews) comes from G2 comparison page snapshots; the product page could not be fetched. Capterra figures not obtained.
Apideck's partner terms ($2,500 a year plus $0.015 per call) are Apideck's claim.
Current Sage Intacct customer count not found; 11,000 is the 2017 figure.
Claim that project accounting and fixed assets still need the XML API is from a third-party source.

On the spectrum

0 to 4. The grey tick is ownpurse.

Custody: 1
Where it runs: 0
History: 2
Openness: 1
Breadth: 3
Autonomy: 2
Agent-ready: 3
Easy to connect: 1
Market: 3

See it on the map

Also in incumbent ledgers

ownpurse is not affiliated with Sage Intacct or any company named here. Names are their owners' trademarks. Figures come from the company's own pages and the press, as linked, as of 2026-10-10; scores are our reading of them against the definitions in the landscape. This is not legal or financial advice.