--- title: "Dock + Sage Intacct: mid-market accounting with audit-ready agent workflows" excerpt: "Sage Intacct is the mid-market accounting choice for software, services, and nonprofits. Agents draft entries, flag variances, prep audit packets. Dock is the workspace where the agent's work persists, attributed, while Sage Intacct stays the system of record." author: mei category: Use Cases date: "2026-05-30" --- Ask a SaaS controller or a nonprofit CFO which GL they run, and you keep hearing Sage Intacct. It is the underrated cluster in AI-for-accounting, because the loud arguments are about QuickBooks at the bottom and NetSuite at the top, while the dimensional, audit-defensible middle quietly runs on Intacct. Subscription software, professional services, and 990-filing nonprofits land here for a reason. Agents in that environment have to respect dimensions, statistical accounts, and audit trails, or they are useless to the controller approving the close. Here is the architecture that makes agent work safe against an Intacct GL. Sage Intacct stays source of truth for the GL, dimensions, statistical accounts, and audit packs. Dock holds agent OUTPUT: variance memos, dimension recoding proposals, audit packet drafts, reclass worksheets. Each row carries an `intacct_transaction_id` or `intacct_entity_id` pointer back to the source object. Agents read fresh from the Intacct API every time, never from a stale mirror, and Dock's consent gate fires entries back into Intacct ONLY after a human controller approves. The ledger is never silently mutated. A concrete workflow. A B2B SaaS company recognizes subscription revenue across two product lines, three entities, and a customer-success dimension. The reclass agent reads new invoices from Intacct, checks the deferred revenue schedule, and finds an annual contract booked last quarter was coded to the wrong product dimension. It drafts a reclass entry in a Dock sheet: original Intacct journal ID, proposed debits and credits, dimension delta, and a one-paragraph rationale citing the SOW. The controller opens the row, reviews, and clicks approve. The [dangerous-ops contract](/blog/dangerous-ops-contract) fires, the journal posts under the controller's user, and the Dock row stamps with the returned `intacct_transaction_id`. Audit trail shows agent drafted, controller approved, Intacct posted, all timestamped. Five-step data flow: 1. Agent pulls open transactions and dimension mappings from the Intacct REST API. 2. Agent writes reclass or accrual proposals into a Dock sheet with full lineage columns. 3. Controller reviews proposed entries in the workspace, edits or comments inline. 4. Approval triggers a signed POST back to Intacct under the controller's session. 5. Dock row updates with the returned journal ID and posts to the audit log. Why Sage Intacct rewards this pattern more than other ledgers. First, multi-dimensional accounting means agents propose at the dimension level without flattening the GL, exactly what SaaS metrics like ARR by segment, gross margin by product, or CAC by customer cohort require. The agent does not have to invent a side-car taxonomy because Intacct already has the slices. Second, audit defensibility is built into the platform, which gives external auditors a familiar evidence trail; Dock's [audit and compliance layer](/blog/agent-audit-and-compliance) extends that trail backward to the agent's drafting steps so the SOC 1 reviewer can see who proposed and who approved. Third, for the SaaS metrics dashboards Intacct customers live in, agents populate statistical accounts (seat counts, headcount, square footage) with the same lineage rigor as financial entries, which keeps per-unit metrics defensible at quarter end. Running Intacct and figuring out where agents fit without putting the GL at risk? Start with [Dock for accounting](/blog/dock-for-accounting) and the broader [month-end close playbook](/blog/ai-for-bookkeeping-and-month-end-close). Comparing ledgers? See [Dock and NetSuite ERP](/blog/dock-netsuite-erp) and [Dock and QuickBooks bookkeeping](/blog/dock-quickbooks-bookkeeping). Spin up a Dock workspace, point an agent at your Intacct sandbox, and let it draft the next reclass. ## FAQ **How does Dock handle Intacct dimensions?** Every Dock row that proposes a journal carries the full dimension set as columns: entity, department, location, class, project, customer, vendor, item, employee. Agents propose at the dimension level, never collapse to summary. **Can agents draft subscription revenue entries?** Yes. The agent reads the deferred revenue schedule and contract metadata from Intacct, drafts recognition or reclass entries in Dock, and waits for controller approval before posting. **Does this work for multi-entity consolidations?** Each row carries `intacct_entity_id`. Agents can propose intercompany entries across entities, and the consent gate routes approval to the controller responsible for each entity. **Nonprofit fund accounting?** Intacct's fund accounting maps cleanly to Dock's lineage columns. Agents draft fund-restricted entries with the restriction class as a first-class column, and the audit packet draft groups by fund for 990 prep. Sources: - [Sage Intacct Web Services Developer documentation](https://developer.intacct.com/web-services/) - [Sage Practice of Now: how accountants are going from good to great](https://www.sage.com/en-gb/blog/the-practice-of-now-how-accountants-can-go-from-good-to-great/)