Sage Intacct was born and bred on the Cloud, and has been built with integration in mind. It has been designed with a strong API at its core with a customisation layer that allows flexibility, and is ideal for those with either in-house systems, or looking to keep their current landscape but expand on it with a world-class finance system.
To put this into perspective, roughly 60% of Sage Intacct transactions and activities post using Web Services (i.e. the API) and most customers have 2 or more Sage Intacct integrations.
The platform has a whole suite of pre-built integrations for Sage Intacct available on the Sage Intacct Marketplace, but if you want to build your own, you can!
Sage Intacct API FAQs
1. Does it cost me to use the Sage Intacct API?
If you are using an Intacct marketplace partner, for example Yooz, then no; there is normally no additional charge to use the API as standard (there are a few exceptions to this but it’s a good rule of thumb). The only time you may incur additional costs is if your API calls go over the standard level of service but it normally takes a few heavy integrations for that to occur.
If you are building your own integration then you will need your own unique sender ID and that requires an Intacct developer API licence, which you will need to pay a small annual subscription for, but other than that the ability to integrate is part of the core.
2. Are there any volume limits around the Intacct API?
Sage Intacct has a concept called ‘Levels of Service’ which basically allocates additional resources as you go up the volume scale, so your system continues to work well. This has actually been recently reviewed (as of the writing of this blog) and the standard level of service that comes as part of your core subscription is now 250,000 transactions (or API calls). For those who have multiple integrations or high levels of volumes, you can upgrade to either a silver or gold subscription.
If you are looking to pull large chunks of data (for something like a data warehouse on a regular database), then I would suggest that the data delivery service would be a better fit. Please note that you can update/push/pull multiple records within that API call, so it is important to consider API call efficiency when building out your integration. That 250,000 is not necessarily 250,000 transactions!
3. Can I push non-financial data into Sage Intacct?
Yes you can, but where you store it depends on what you are looking to achieve! Within the Sage Intacct platform you can create custom objects and custom fields, so that is always an option, but do remember that you also have the option to import statistical info (i.e. no. of employees for reporting purposes or elements such as usage data for contract invoice generation).
It is definitely worth talking to your Sage Intacct business architect about the design of your system so that you can get the most out of your Sage Intacct deployment. If you don’t have one, then of course please feel free to reach out to us, and we will put you in touch with our award-winning Sage Intacct implementation team. They will be more than happy to offer advice and guidance.
4. Can I get a Sage Intacct test environment to build in?
Prior to going live, you will have an implementation instance on Sage Intacct that you can use to build the initial setup. However, if you are doing development (particularly for those doing so in-house), then we always recommend you get a Sage Intacct sandbox for ongoing development & maintenance. This is available at an annual charge of 10% of your subscription, but it is well worth the investment!
If you do not currently have Sage Intacct and are just looking to learn more about Sage Intacct’s features and functionality, we have a range of resources you may find useful! Access our Sage Intacct webinars here, learn more about which product is right for your industry here, and watch an on-demand demo of Sage Intacct in your own time here. Alternatively, if you would like to speak to a Sage Intacct specialist, you can get in touch with us here.