Thousands of NetSuite users are at SuiteWorld in Las Vegas this week. Good place to talk about odds. 🎲
AI agents are starting to buy things. Google’s Universal Commerce Protocol and OpenAI's / Stripe’s Agentic Commerce Protocol both define a checkout where the merchant returns a full total, tax included, before anyone commits.
The protocols carry the tax number. They don’t calculate it. That’s still someone else's job.
So: who calculates tax when there’s no transaction yet?
In most ERP setups, tax is something that happens to a transaction. In SuiteTax, it’s calculated when someone previews or saves the order. That’s a good design for a person, a form, and a Save button.
An agent doesn’t use the form.
An agent 🤖 needs tax 💲 :
→ before the order exists
→ for every line, on every change
→ fast
→ matching what posts to the ledger
Can you get that out of NetSuite? With effort. Oracle’s own guidance is a custom script that builds a sales order in memory, asks it for the tax, and throws it away. On every cart update. For every agent session.
It’s counting cards by hand. It works until the table gets busy.
The bigger risk isn’t speed. It’s getting two answers.
When the workaround is too heavy, teams calculate the checkout quote somewhere else, and the ERP calculates it again when the order posts. If those disagree, the customer approved one total and your ledger recorded another. In this casino, the house doesn’t win. The auditor does.
B2B raises the stakes. If exemption status only lives in the ERP’s transaction flow, the agent quotes the sale as taxable, the invoice posts it as exempt, and someone reconciles the difference by hand.
The fix isn’t ripping out the ERP. It’s treating tax determination as a service every system calls the same way: the agent before the order exists, the ERP when it posts, and the auditor two years later asking why. The ERP records the result. It shouldn’t be the only place that can produce it.
Remember “someone else’s job”? That’s the job we built
Orchestrate.tax for. The agent, the ERP, and the auditor all get the same answers from the same source. It plugs into the stack you already run. No rip and replace.
One more Vegas note. What happens in Vegas stays in Vegas 🤫 . What happens when you enable SuiteTax stays in NetSuite 🔓 : it’s a one-way, account-wide switch. Before placing bets like that, ask:
→ Can we get a binding quote without creating a transaction?
→ What does it cost to quote every cart update?
→ If checkout and the ERP calculate separately, how do we catch disagreements?
→ Does exemption status reach the quote, or only the invoice?
→ Who decides which engine answers: us, or the platform?
Your tax stack was built for a buyer who clicks Save. That buyer is changing.
At SuiteWorld and thinking about this? Our DMs are open.
#SuiteWorld #SalesTax #AgenticCommerce #NetSuite #OrchestrateTax