@Sirus Badiee sadly, that is normal behavior with most transaction scripts, including the ones we have deployed from a tax engine bundle. You could try reaching out to support for your tax engine to see if steps can be taken to temporarily disable that, possibly there is a setting in the bundle or tax service, or they may have you undeploy scripts temporarily, but I would definitely work with their support and let them know what you are trying to do. Short (but dangerous) answer is, yes, you can disable all scripts and workflows, but DON'T DO THAT without being sure what the consequences may be, and certainly not without testing in a sandbox. There may also be SuiteGL plug-ins to consider as well.