Reference · built on requestConnectorERP & finance

Sage Intacct

Bills, invoices, payments, customers, vendors, and ledger data from Sage Intacct via its REST API and Platform Trigger webhooks.

Request accessPricing ↗

About

Sage Intacct is Sage's cloud financial management system. Its REST API addresses objects by module and name, such as accounts-payable/bill, accounts-receivable/invoice, accounts-receivable/customer, and order-entry/document, and a query service returns selected fields with filters, sorting, and paging. The XML Web Services API remains available; new objects ship on REST. Platform Triggers can deliver outbound webhooks when a record event occurs.

An operator on Fibric holds a registered application under your company's sender ID, reads the objects you grant, and proposes postings or notices for your approval. The record shows what changed, the reason, and the undo path.

This is a reference listing. It documents what Fibric would read from Sage Intacct and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • accounts-payable/bill, bill-line, payment, and vendor, with vendor-total for balances
  • accounts-receivable/invoice, invoice-line, payment, customer, and dunning-invoice
  • order-entry/document as a base object across document types, or a derived object such as order-entry/document::Sales Invoice
  • general-ledger objects such as account-group, and cash-management/bank-feed transactions
  • Query service results with ia::meta paging: totalCount, start, pageSize, next, and previous
  • Platform Trigger webhooks with X-ClientContext event metadata and an X-IA-Sage-Signature JWT, retried up to four attempts

Proposed actions

  • Target capability: propose creating an accounts-receivable/invoice or accounts-payable/bill with its lines
  • Target capability: propose recording an accounts-receivable/payment against open invoices

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Match bills to purchase orders and receipts

    Read accounts-payable/bill lines with their purchasing references and propose approval, hold, or a short-pay note for the controller.

    With Three-Way Match, Receipt Not Invoiced

  • Run dunning from the ledger, not a spreadsheet

    Query accounts-receivable/dunning-invoice and customer totals and propose the next notice per customer with the invoices listed.

    With Dunning Cadence, Balance Write-Off

  • Apply cash the morning it lands

    Read cash-management/bank-feed transactions and open invoices and propose an accounts-receivable/payment for each match.

    With Cash Application, Bank Reconciliation

Requirements

  • A Sage Intacct Web Services license: a sender ID and sender password issued to the Sage Intacct customer
  • An application registered in the Sage developer console, enrolled with the sender ID, with a Production client scope
  • The company must authorize the sender ID on its Company Security tab, or an admin approves the OAuth request
  • For webhooks: a public HTTPS endpoint that accepts POST, listed as an allowable Async URI on the application
Authentication
OAuth 2.0 against https://api.intacct.com/ia/api/v1/oauth2/token, authorization code or client credentials grant, from an application registered under a Web Services license (sender ID).

Limits

  • Access tokens expire after 43,200 seconds; refresh tokens are issued only when scope=offline_access is requested
  • Concurrency is tiered per application/company, 6/8 at Tier 1, and API transactions above the monthly tier entitlement are billed as overage
  • A web services ID may be associated with up to five production API keys
  • Webhooks retry after 10, 30, and 90 seconds on 408, 429, or 5xx; four attempts in total

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Sage Intacct ↗

Questions and answers

Does Sage Intacct push events?
Yes. A Platform Trigger with type HTTP post and Use webhook delivery sends a payload to your endpoint when the event occurs. Delivery retries up to four times, headers carry event metadata and an HS256 JWT signed with your client secret, and a unique key header supports duplicate checks.
How are rate limits expressed?
As performance tiers. Each tier sets monthly API transactions and concurrent requests per application and company, for example Tier 1 at 100,000 transactions and 6/8 concurrency. Transactions beyond the entitlement are charged as overage rather than blocked; concurrency is enforced.
Is the XML API still usable?
Yes. Sage continues to support the XML Web Services API at api.intacct.com/ia/xml/xmlgw.phtml and publishes an XML-to-REST object map for migration. New objects and features are released on REST, which Sage recommends for client applications.
Ask about Sage Intacct

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with Sage Intacct through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy