Sage Intacct
Sage Intacct is a cloud-native financial management platform widely used by mid-market companies, nonprofits, and professional services firms. It covers GL, AP, AR, cash management, and reporting through a well-documented XML API that requires a specific XML envelope and sender credentials on every request.
What you can do
Read and write AR invoices
Pull open and paid AR invoices with customer details, line items, tax data, and payment terms. Post new invoices and apply payments from your billing or revenue-recognition product.
Sync GL journal entries
Read and create General Ledger journal entries across multiple entities and dimensions. Askel handles Intacct's multi-entity model so your product can post entries to the correct entity and location.
Access AP invoices and payments
Pull open vendor bills, payment runs, and ACH/check payment records from the Intacct AP module. Write back new vendor bills from your expense or procurement product.
Read dimension and chart of accounts data
Pull Intacct dimensions (department, location, project, class, customer) and the chart of accounts. Use this to let customers map their Intacct dimensional structure to your product's reporting hierarchy.
Sync vendor and customer master records
Read and write vendor and customer master data including contact details, payment terms, and credit limits. Keep your CRM or onboarding product in sync with Intacct's customer list.
Run custom Intacct reports
Execute saved Intacct report definitions and retrieve their output. Askel can call a named Intacct report on a schedule and page through the results, giving your product access to customer-defined financial views.
Posting revenue recognition entries from a SaaS billing product into Sage Intacct
Northfield Advisory Group is a professional services firm that uses your contract-billing platform for time tracking and invoicing and runs their general ledger on Sage Intacct. Every time their billing platform generates an invoice, their finance team wants a corresponding AR transaction to appear in Intacct automatically, with the correct department and project dimensions attached.
- 1
Create the Web Services user in Intacct
Northfield's Intacct administrator navigates to Company > Web Services Users, creates a new user named wsuser_askel with the Accounts Receivable and General Ledger module permissions, and notes the user ID and password. They also note the Intacct company ID and the sender ID and sender password provided to them by Askel during onboarding.
- 2
Enter credentials in Askel
Northfield's admin enters the sender ID, sender password, user ID, user password, and Intacct company ID into the Askel setup screen inside your billing platform. Askel assembles a test XML request envelope, sends it to https://api.intacct.com/ia/xml/xmlgw.phtml, and confirms connectivity by fetching the company configuration.
- 3
Schema discovery
Askel reads Northfield's Intacct dimension definitions, chart of accounts, and AR module configuration. Your CS team sees a mapping draft covering invoice fields, dimensions (department, project, location), and tax codes within minutes.
- 4
Map and validate
Northfield's invoices need to carry a project dimension that maps to their Intacct project codes. A CS rep maps the billing platform's project field to the Intacct Project dimension and runs a dry-run posting 20 test invoices to Northfield's Intacct sandbox to verify the GL entries land correctly.
- 5
Go live
When the billing platform finalizes an invoice, Askel constructs an Intacct XML request with the AR invoice payload and the correct dimension values, posts it to Intacct, and returns the Intacct record ID. Northfield's finance team sees new invoices in Intacct within seconds of them being generated in the billing platform.
Service account
The customer creates a dedicated Web Services User in Sage Intacct under Company > Web Services Users, then provides the Intacct sender ID, sender password, user ID, user password, and company ID to Askel. Askel embeds these credentials in the XML session block of every API request. No OAuth token exchange is involved; credentials travel inside the XML envelope.
How Askel sits between your product and the customer's system
FAQ for Sage Intacct
Does Askel need a separate sender ID, or does it use the customer's own sender?+
Does this work across multiple Intacct entities (multi-entity companies)?+
Can we test against an Intacct sandbox company?+
What happens if a dimension value in the request does not exist in Intacct?+
catching drift before it breaks, and hitting go-live dates.
© 2025 Askel.ai. All rights reserved.