It's a warning you can't turn off.

Good morning Jay, 

Thank you for the quick reply.  I thought it would be like the PO field where you could choose to verify if it was a duplicate.  I just want to be sure I am not missing anything.  There was some old post about coding it out but I rather not do that.  I don't like modifying the core system options. 

Do you have any experience with eBridge/JitterBit integrations?  If so, is there another work around for overcoming this warning?

I never heard of eBridge or JitterBit until I just Googled them.  No thanks.  For my integrations, I use Orchid Extender's Python, or the Sage COMAPI with VB6, VBA, C#, or VbDotNet.

Thanks again for your feedback. 

Are you changing the tax group due to a different location for the customer??  What about using ship-to locations??

Hi Terry, 

Yes, we are changing the tax group based on ship to province/state. 

Thank you for the suggestion.  I will see if that is a valid option.  They would need to map ship to province/state to a specific ship to code before entering line details and we would have to do that for all customers.  

Just an update and to document the process for anyone else considering JitterBit and Sage 300 integration.  

The work around we tried was setting up a tax group specific for importing orders from JitterBit to Sage 300.  First we had all the tax authorities loaded with the default to non-taxable.  We also setup a specific ship to code for importing with the above tax group so it brings up the tax group automatically, bypassing the tax warning message. 

Using this setup, we sent tax authority, tax class (in our setup it is taxable or non-taxable), tax base amount and tax amount through API header values.  Error message came back stating tax authority field is empty. 

We then changed the tax group to NOT include any tax authorities.  Tried the same four tax field imports and got the same error message.  

JitterBit will not touch Sage API and could only troubleshoot their own script and connector.  

Therefore, I was wondering if there are any developers on this forum that could help us with Sage API?  If so, please send me a PM with your rates. 

Thank you, 

We resolved this by turning off "Calculate Tax Reporting Amounts Automatically" in O/E Setup Options. 

However, this does not just turn off the pop up, it also affect the calculation and distribution of taxes for multicurrency as well.  So before you use this see how it affects your business with regards to tax authority reporting.  Since most of our orders that have taxes are in the same currency as Sage functional currency it didn't affect us much.