Sage Intacct integration options: native, Marketplace, iPaaS or custom?
Sage Intacct is a strong finance platform, but most businesses need it to exchange data with other systems: a CRM for invoicing, an HR system for employees and cost centres, time-tracking tools for project costs. There are four main ways to do that. This article compares them and explains how to choose.
1. Sage Intacct's own integrations
Sage Intacct provides some integrations itself, such as its integration with Salesforce. If one covers your process, it's well supported and maintained by Sage, which makes it a sensible first thing to check.
Good for: standard processes on platforms Sage supports directly.
Watch out for: limited flexibility when your process differs from the standard design.
2. Marketplace apps
The Sage Intacct Marketplace lists partner-built apps and connectors for payroll, expenses, payments, billing and more. Many are mature products used by hundreds of customers.
Good for: common needs such as expenses, payments or payroll journals, where a specialist product already exists.
Watch out for: ongoing subscription costs, and how well the app handles your dimensions, entities and approval steps. Ask for a demo using your own scenarios, not the vendor's.
3. Integration platforms (iPaaS)
Most major integration platforms offer a Sage Intacct connector. They suit businesses with several integrations to manage, especially if those integrations involve other systems that are already on the same platform.
Good for: organisations running many integrations that want a single place to build and monitor them.
Watch out for: platform licence costs, and the skills needed to build and maintain flows properly. A visual tool still needs careful design.
4. A custom integration using the APIs
Sage Intacct has a long-established XML Web Services API and a newer REST API, plus Smart Events that can notify other systems when records change. A custom integration uses these to do exactly what your process needs. You'll need Web Services access on your Sage Intacct subscription.
Good for: unusual processes, complex mapping, high volumes, or flows that no connector handles well.
Watch out for: more up-front design effort, and the need for clear documentation and monitoring so you aren't dependent on whoever built it.
Comparing the options
| Option | Speed to launch | Flexibility | Ongoing cost |
|---|---|---|---|
| Sage Intacct integration | Fast | Low | Usually low |
| Marketplace app | Fast | Low to medium | Subscription |
| iPaaS | Medium | Medium to high | Platform licence |
| Custom API integration | Slower | High | Support only |
What to get right, whichever option you choose
- Dimensions. Departments, locations, projects and other dimensions must match between systems, or reports won't reconcile.
- No duplicates. An integration that retries after an error must not post the same invoice or journal twice.
- Periods and entities. Decide what happens when data arrives for a closed period, or belongs to a different entity in a multi-entity setup.
- Errors and alerts. Someone needs to know when a record fails, why, and how to fix it.
- Audit trail. Your auditors will want to see where each transaction came from.
How to choose
Work through your data flows one at a time, because the best option for invoicing may not be the best option for payroll. For each flow, ask:
- Does a Sage Intacct integration or Marketplace app cover this process, including our exceptions?
- Do we already use an integration platform for other systems?
- How unusual are our mapping rules, volumes or approval steps?
- Who will monitor and maintain the integration after it's live?
Many businesses end up with a mix: a Marketplace app for expenses, for example, and a custom integration for a CRM-to-invoicing process that no connector handles well. That's fine, as long as every integration is monitored and documented.