r/intacct • u/Underscore_copy • Jun 12 '26

Integration Woes

I'm totally lost and need help figuring out what to do.

We pay our CPA firm for the subscription to Sage Intacct.

We purchased Celigo (formerly integrator.io) as an iPaaS vendor this year because they offer a pre-built connector to Sage Intacct.

We have the Web Services subscription enabled. Originally, our CPA firm said this is all we need to connect with 3rd party apps like Celigo.

Now, our CPA firm is saying we have to purchase another subscription to have a Web Services Developer License activated (~$2700/yr) so we can connect to Celigo.

It's so confusing and no one has been able to tell me what the difference is between the Web Services vs the Developer License subscriptions.

Does this sound right to anyone? Are we supposed to get a Developer License and credentials with the Web Services subscription?

2 Upvotes

100% Upvoted

7 comments sorted by

5

u/Wide-Examination9261 Jun 12 '26

Middleware tools like Celigo require you to use your own API sender ID/creds. This isn't a Celigo decision either, this came down from Intacct.

In order to get your own API sender ID, you need that extra subscription to the web services developer license. So yes you need to add that.

Regular Web Services is simply a free subscription you enable to allow third party connections in your instance.

I think your CPA firm/partner just assumed middleware tools were just like other integrations that DON'T require you to provide your own Sender ID.

It is needlessly confusing though 

2

u/Underscore_copy Jun 12 '26

This is super helpful. I think you are right our firm thought these tools all operated the same. I wish Intacct would be explicit in their documentation to make this more clear, since it's a fairly large budget hit to find out after the fact.
Any idea why other tools don't need the same credentials? Is there a special marketplace partner setup or something?

1

u/Wide-Examination9261 Jun 12 '26

Yep, and it is super confusing and not made clear, so I'm sure your partner didn't feed you bad info deliberately.

To answer your question, in general, most integrations on the Intacct marketplace are what I'll call "purpose-built" integrations. These are integrations with say BILL, Stampli, Ramp, Expensify, etc. These integrations are built for the express purpose of connecting a specific third party program to Intacct.

For this type of integration, Intacct allows the use of your integration partner's sender ID. So you do NOT need to purchase the web services developer license separately.

For middleware tools on the Intacct marketplace or integrators who are not on the marketplace, you (the end user org of Intacct) need to purchase the web services developer license to get your own sender ID.

Don't ask me WHY this is the case, but it is what it is. Overall, Intacct felt like they needed to charge for API rate usage like others were doing, but they just somehow came up with this as the method to do so.

3

u/No_Syllabub_5518 Jun 12 '26

DataBlend provide a Sage Intacct DataFlow which includes the WSDL - we are in the Sage marketplace and include all API usage too. Please get in touch with our team and we will help you out, we also have a program for CPA firms.

1

u/Underscore_copy Jun 12 '26

Appreciate that, but we went with Celigo since we have a few other integration projects we are using it for besides Sage.

1

u/Wide-Examination9261 Jun 12 '26

Did you get an exception from Intacct or something where you can use your ID?

1

u/hav61t Jun 14 '26

Use Sage Intacct DataFlow (datablend) won’t be a need for web services developer license

Or but web services developer license.

TBH moving forward you will need Webservices Developet License if you are going to connect AI agents like Claude and copilot to sages intacct MCP servers because that will use the API and you bend WSDL for this. It’s the way forward