Anyone have issues with New York Sales Tax being that the NS reports split County from State taxes?

My 2 cents is, I have a client that uses oneworld, but they also subscribe to avalara. That's what I'd recommend too

Avalara is very expensive, why cant netsuite figure this out for complicated sales tax states such as California or New York? What's everyone else doing?

because even from the NS setup for Avalara, I know the US tax can get very difficult and tedious. And to get the netsuite setup perfectly for tax compliance I'd really start with a project with avalara (Im not contractually with them or benefitting from them by the way) But just to make sure your nexuses are setup correctly, and especially if you do interstate, or export related stuff the tax codes of those things you sell are configured properly. And what I mean is tariffs, a wire sold at 26m can be categorized differently from a wire that is sold 25m. To me, thats what the service can save you on. The netsuite tax codes from my understanding will differentiate the tax code but wont diferentiate by product category if it was taxable in the first place, I could be wrong, but that'll be my free two cents

got it, interesting, thank for responding. The part i cant wrap my mind around is that there should be more companies out there with the same issue

@Judah Strauss I'd say it's the scale, if you have sufficient scale, say you're a public company, it's a a necessity to shift the blame afterwards to Avalara and hence they'd make things right for you

Ha ha love the line "sue them"

I'd personally take that versus being sued, by feds, but that's me hahaha

@Judah Strauss We have no issues using standard NetSuite taxes for multiple states. You should probably read up on Tax Groups and make sure you're set up correctly.

@wes_w are you selling in states with multiple tax rates, city vs county? Do you ever also sell on one sales order to many ship to addresses? How about within a state, certain items are taxable and certain not? These are some of the complexities I don't see a easy scolition to in NS. Thoughts?

@Judah Strauss If you have items that are taxed in some states you have nexus in, but not taxed in other states you have nexus in, NetSuite will not do that. An item is either taxable or not. You could probably make kit items for those as a workaround. I thought you were having trouble reading the reports because it sounds like you are only using tax codes and not tax groups. We collect tax in states like NY and IL with multiple city/county/transportation tax rates.

@wes_w hi, how do you calculate the non-taxable sales per state (county? Or city?) which is required in NY sales tax return?

I add a new tax group for each state called

{state} non-taxable

and I only include the non-taxable tax code on customers which are not taxed. All other customers I leave that field blank, and I make sure that the 'is taxable' check box is ALWAYS checked.

@wes_w Do you have customers that have some transactions that are taxable and some are not? SUch as one customer will place an order to be shipped to multiple of their locations?

@Judah Strauss Can you clarify? Do you not have nexus in the state of one of their locations? Is one of their locations not taxable for some reason?

Both. We can potentially get an order which will ship to may ship to's where some are NFP or some ar ein states where we don't have nexus, but they are all on the same sales order. DO you ever have that?

We have customers who we will ship orders to states with and without nexus, and NetSuite works fine for that. BUT if you have some (but not all) locations on one sales order where one customer is taxable and another is not, NetSuite will not do that automatically. You could set each line on the sales order to the correct tax group, or conversely you would have to set up a separate customer for the NFP locations and set them to Not-Taxable (by state).