Hi, I am getting the error message below when I am...
# taxes
n
Hi, I am getting the error message below when I am trying to bill the multiple purchase order (using Administrator role Transactions->Payables->Bill Purchase Orders). Can someone please throw light on how to fix it? I have already added the missing nexus in the vendor’s subsidiary. “”The vendor you have selected is based in a nexus for which you are required to charge a different kind of tax. Click OK to change the form to one that is applicable for that Nexus.“”
k
it is likely related to non-US taxes so find PO(POs) with the shipping address to the non-US country
n
The POs I am trying to turn into a bill are for US vendors only.
When I selected multiple POs on the Bill purchase order and clicked the submit button. It is taking me to the Bill form and wiping out the Vendor value. If I add the vendor, the line items are wiped out. This is an interesting behavior
c
The error is entirely related to Nexus selection on the transaction form. Check the bill address of each vendor. Compare to subsidiary nexus available for each subsidiary. Its likely you have a mismatch somewhere and a prompt which usually comes up in the UI is happening here
n
@C_Billings I apologize, but I didn’t quite catch that. Would you like me to verify the billing addresses for all the US vendors and check if any vendor has a billing address that isn’t listed as a Nexus in the US subsidiary?
c
Maybe I'll back up. Do you understand NetSuite Nexus? For instance if you are logged into a role with a US subsidiary which only has a US State(s) as its nexus and you pick a Canada based (billing address) vendor nothing happens. But when you have Nexus setup for that Canada address on your sub (as well as US states) your instance will try to switch to a Canadian Layout to allow for Canada specific features to engage. So its first pick is USA but then realizes you have a Canada transaction and wants to present a form with Canada fields including Canada tax codes. You are experiencing that prompt but strangely in the Bulk Billing. Check each bill in your run...I would bet one of them is triggering this. Ultimately you may have to bill it independently but call support.
102 Views