Can someone tell if there is a way to enable these...
# accounting
n
Can someone tell if there is a way to enable these columns on the Vendor Bills ?
c
Setup Taxes and Line vs Transaction taxes.
n
Where is that setting ? I am unable to find
c
image.png
if you dont have this checked for US transactions only the Transaction Body field tax fields show on forms. With this checked the body ones will grey out and then the line ones show
n
I think i already have that checked
but still the Tax columns are not visible and when i try to customize the form, those options are greyed out
c
SuiteTax or Legacy Tax Model? Also which nexus are we working with here?
n
SuiteTax
USA
s
sorry my responses are out of sync - but you can't enable PST on a US entity - it would be in the wrong currency for starters (assuming CAD or other PST taxing authority)
n
So , what is the best way to record Tax on Purchase (Vendor Bills) for US Subsidiary? Should it be recorded as a separate line (May be service for purchase item). Or should i record it as a custom field on the header ? or is there any other way to do that ?
c
What you need is the Canadian Nexus which should allow for this. Somehow I missed the Canada reference
n
if i select the Canadian NExus for US transaction, will it not disturb the Sales and the USD amount?
s
Can you share a screenshot sample of the actual bill you’re trying to record? I’m a little confused on whether this is a US or Canadian vendor purchase/sale and what country the subsidiary making the purchase resides in. Please make sure currency is visible in the screenshot since CAD/USD can be confused easily with $.
n
image.png
This is a a standard vendor bill. being created for a Test vendor , Subsidiary is. US
Currency is USD
s
Gotcha - can you share why you care about showing sales tax for this bill?
And is the test vendor a US based vendor?
n
This is thwe standard practice . PO doesnt have Tax. VB has Tax We need to make sure PO amount matches with VB amount , but excluding TAX. But we have to include tax on bill because we have to pay the amount (including tax).
That is standard practice.
My only question is. , How can i enable the Tax code & Tax amount columns for US subsidiuary
NEtSuite Docuemented it here. SuiteAnswer # 72245
They say its resolved using SuiteTax
i have SuiteTax enabled , but i dont see any option to enable these options
s
If SuiteTax is enabled, your next step is to setup the tax Codes: Go to:
Setup > Tax > Tax Codes
. Create new tax code: Provide the required information, such as: • Name: e.g., "State Sales Tax". • Description: e.g., "Applicable state sales tax for U.S. subsidiary". • Tax Type: Select the appropriate tax type. • Tax Rate: Input the applicable tax rate. Next - Customize the Vendor Bill FormEnable Tax Columns: ▪︎ Items Subtab: Ensure that the Tax Code and Tax Amount columns are checked to be visible. ◦ Expenses Subtab: Similarly, verify that these columns are enabled. Last Step: Assign the Customized Form to the U.S. Subsidiary:
Setup > Company > Subsidiaries
.
If you've done all of this and still having issues, I suspect it has something to do with the fact that you see PST fields (grayed out) in the form customization view. You really shouldn't see this as its a conflicting tax code.
n
I am on Legacy system, not on SuiteTax. How people enter Tax on Vendor Bills ? I want to enter at the header level. Isn't it a standard Practice ?
c
Well I'm literally the expert on legacy tax model....to add tax in the way its intended would be to have an active nexus for the Canadian province you are being charged. That way it goes to the books for proper handling. That said I would bet you are not registered in Canada and a vendor simply charged you tax. In that case its an expense and you simply add it as an Expense NOT ITEM line on the bill. Knowing how your business is setup goes a long way to understanding the right next steps
n
First thing: its not Canada. We are Talking about US only. We are Registered in US . The Vendor is also in US. When vendor gives us the Bill, it has 2 lines Line 1: The itemX ....Qty...Rate...Amount (USD 100) Line 2: Tax ........13% ...Amount (USD 13) When we enter this bill in our system , We want to enter the USD100 & USD 13 separately. I dont see any place to select the Tax Code or enter this amount. For all other subsidiaries "Except US", it works fine, showing the Tax code and Tax amount column on each line. But not for US
As per my understanding , the following things can be done: -Tax can be entered on the Expense tab -A Tax (expense for purchase) item can be crated and it can be entered as separate line But those approaches will not give the Tax column on each line Total of bill is Amount Payable, My intent is to calculate Amount Without Tax and Tax total on the bill How can i do that?
c
Ugh I feel dumb. Been using SuiteTax and Third Party for so long I forgot this....there is no tax available for US purchases. all tax are assumed as expenses. This is one of the reasons they created SuiteTax (way back in 2014) to allow for a uniform approach to tax.
a
Exactly. Legacy tax doesn't allow you to add taxes to a US bill. I assume the assumption was that taxes aren't recoverable in the US so there's no need to break out taxes separately.
c
Yeah that was literally the explanation by the tax product group at NetSuite. Most of the time the tax for an item is considered part of the item expense...of course there are all kinds of ways that conflicts with data etc
s
Circling back to this - from a functional perspective (I'm the techy finance/accounting user), I've usually solved for the US tax debacle with some custom development to enable header-level tax subtotaling, that breaks down total with and without tax (plus a total aggregate tax amount that ties to total sales tax line on the bill). Can dig more up on this if helpful.
n
Thanks. I have the custom solution ready, but i wanted to be sure there is no standard way of doing that.
I have the custom code to allow to enter the tax and can programmatically distribute the tax amongst the lines based upon the amount weightage, if i need to.
s
Makes sense. I would say the one "gotcha" that you'll want to have a solution for is when different line items have different taxability - example: new software subscription with an implementation (professional services) fee attached to it - the software sub is taxable, while the pro serv isn't (varies tbd on the state). So having this variable / lockup trigger is worthy mapping out in advance. The other "gotcha"... and (hopefully) less common scenario .. is when you have states with multi-jurisdictional tax codes that require sales tax feeds to truly manage at scale - State of Texas is good example. In these cases, a tax code becomes unmanageable unless maintained by, say, Avalara/Anrok, etc. This also assumes you aren't already registered and collecting tax from a sales perspective in these states --- in which case, I would expect the suitetax config is mostly there to build on.
building in PO price tolerances that allows for variances within a reasonable sales tax rate markup is never a bad fallback plan as well 🙂