Hmmmm so intercompany transactions and foreign currency transactions will incur more ERP transactions ? What about those from coming from API calls?

Oh wow, that is indeed unpredictable. Personally, I totally get that Acumatica is cracking down on ERP Transactions because of “noisy neighbors” in the Acumatica Cloud. In my opinion, the main solution for those “noisy neighbors” is to look at hosting Acumatica somewhere outside the Acumatica Cloud so they can fine-tune their hardware resources better without having to pay a ton more money to Acumatica.

The weird thing though is that Acumatica changed their pricing a couple of years ago to make self-hosted customers pay exactly the same amount as customer who are hosted in the Acumatica Cloud. There was an official explanation for why they did it, but personally I don’t think it made any sense. Regardless, it’s strange that self-hosted customers have to pay the same amount, even though they are taking care of the hardware costs.

So, I think we should start campaigning for things to go back to where they were a couple of years ago where self-hosted customers pay less than customers who are hosted in the Acumatica Cloud. I think that would solve the problem because then you could look at self-hosting or hosting with a 3rd party if you find that you have a high ratio of ERP Transactions to Commercial Transactions.

Yes, that’s correct @bbohn. This is really more of an issue for people who have been on Acumatica for years because their existing contract legally restricts the number of ERP Transactions. The new agreement is a bit of a “correction” on the part of Acumatica.

However, my understanding at this point is that, even though ERP Transactions are no longer part of the legal agreement, you won’t be able to complain to Acumatica about slowness in your SaaS environment if you are over on ERP Transactions. Which makes sense. I’m just making the point that ERP Transactions still have “teeth” under the new agreement.