Sage Intacct's AI invoice workspace: what NZ firms should check

What Sage announced

Sage used its partner event in Atlanta on 5 November to set out plans for AI Workspaces in Sage Intacct. Each workspace is a single place where finance staff supervise software agents alongside the records, tasks and approval steps those agents touch. The first one covers accounts payable and is due to reach selected customers in a limited rollout this month. ERP News' report gives no wider release date, region or price, so most buyers can only assess a stated plan for now.

The workspace builds on Sage's AP Agent, which helps process invoices, match them to purchase orders, identify exceptions and route work for approval. Sage's model has agents doing routine work while finance staff review and approve under controls each company configures. ERP News describes the practical change as putting a flagged discrepancy, its related records and the approval step in one view.

Why the announcement matters beyond Sage customers

Accounts payable suits early agent deployment because the work is repetitive and each invoice leaves a document trail. Sage isn't alone in going there. On 4 November, Infor detailed distribution ERP agents that include supplier statement reconciliation, with unmatched items left for manual resolution. Both vendors keep a person at the exception stage.

We think the review screen deserves more attention than the agent. When software prepares most bills, staff spend less time keying and more time judging exceptions, and the approval design decides whether anyone is exercising judgement or just clicking through a queue.

Payment fraud raises the stakes. A 30 October opinion piece on CFOtech, written by a Jaggaer executive, cites the 2026 AFP survey: 76% of US organisations reported attempted or actual payments fraud in the prior year. The figure is American and comes through a procurement vendor, and the article offers no NZ equivalent. Its advice still applies here, because it treats every bank-detail change as a red flag to verify through a controlled workflow. An agent can confirm that an invoice agrees with a purchase order and a receipt, but a clean match says nothing about whether the bank account on the supplier record is genuine.

The New Zealand gap

Sage's own release notes show how uneven the rollout is. The 2026 R4 notes, dated 6 November and marked as a work in progress until release, list the Finance Intelligence Agent as generally available in Australia, Canada, Singapore, South Africa, the UK and the US. New Zealand doesn't appear anywhere on the page. The R3 note on AI agents limits Marketplace agents to Canada, the UK and the US, which at that release left out Australia as well. Neither the R3 nor the R4 release-note home page names an AP Agent, so its regional availability can't be read from those pages.

New Zealand does feature on Sage's Australia region page, where the NZ tax solution and NZ tax submission both carry an Early Adopter label. Sage describes those programmes as access to features before general release. Sage has had a local channel since partnering with BDO Information Systems in December 2024, but the published agent lists haven't caught up with that push.

The older automation layer looks better for NZ users. AP Automation, AI line-level three-way matching and anomaly detection are all listed for "All regions". Those notes don't name New Zealand, so get a written answer from Sage or your partner before counting on them. Trans-Tasman groups should ask the same question for each entity, since an Australian entity may get features earlier than its NZ sibling.

Controls to review before an agent arrives

Intacct's bill approval rules show where an agent could pass work through with little scrutiny. A bill below the first value level posts automatically, and a vendor with no assigned approver skips the vendor-based step. Those settings may have been tolerable when a person keyed each bill, because the clerk was an informal check. An agent preparing bills removes that check and can raise the volume going through the same gaps.

Approval paths are also split. Bill approvals cover bills created in Accounts Payable, while Purchasing transactions use separate approvals, and ERP News notes that Sage hasn't said how the first workspace will treat the two paths. Match tolerances deserve the same attention. The three-way matching feature offers optional thresholds to cut review of minor differences, and a generous setting could let small, repeated overcharges through without a human seeing them.

Cost forecasting needs care too. Marketplace agents are bought through AWS Marketplace on a tiered subscription, and the R3 note counts each Send in an agent conversation as one request. Pricing for the AP Workspace hasn't been published.

NZ suppliers to government have a separate date in the same part of the finance stack. Under Government Procurement Rule 44.2, agencies handling more than 2,000 domestic trade invoices a year must require large suppliers to send eInvoices over Peppol from 1 January 2027. A large supplier has revenue above $33 million in each of the two preceding accounting periods. Sage's region page doesn't mention Peppol, so anyone reviewing Intacct or another finance platform should raise e-invoicing in the same conversation as AI features.

Next steps

If you're running or shortlisting a mid-market ERP, these checks apply whichever vendor you use. Our ERP team's page covers system selection and implementation if you'd like outside help.

• Ask your vendor or partner, in writing, which AI and automation features are available for NZ entities today, and which are only labelled "all regions" or Early Adopter.
• Export your approval policies and list every supplier with no assigned approver, then record the value below which bills post automatically.
• Review match tolerances and reset them as if nobody will read the invoice, because for matched items nobody might.
• Move supplier bank-detail changes into a controlled workflow with call-back verification to a known contact, and keep the workflow outside any agent's permissions.
• Capture a baseline before any pilot: invoices per month, exception rate, time to approval and duplicate payments caught. Our process and automation work starts from the same kind of measurement.
• Ask how pricing is metered and what happens to the bill if volumes double, then model both cases.
• If you sell to government and exceed the $33 million test, confirm your Peppol sending capability now, ahead of 1 January 2027.