Hi, when we use an account in a journal entry , re...
# accounting
a
Hi, when we use an account in a journal entry , related to salaries and we refer to the employee, is there a way to avoid specific finance users to extract transactions related to that account? We protected the journal entry with a workflow and we are showing only the summary account in reporting but I can't find a way to exclude the account from being extracted in saves searches? Is there any permission or trick to get this behavior?
c
All of the NS implementations I've seen journal a summary by department for exactly this reason. I'd be interested to see an "official" way of doing this.
k
Yeah best idea is to not link to an employee. 😂
a
Same here… but I also know that is possible to pay employees using NetSuite… so somehow there will be employee bank details … in Europe is not common but I've been told that in US is a common practice to pay employees salaries using NetSuite.
k
Yeah but then they would use the NetSuite payroll system normally and that would have the eft payment system.
You are right in the uk when using Infinet Clouds payroll you have payslips etc and reporting so it's not required on the journals.
a
Ah ok, thank you for your answer. Then maybe the best is to refer to the employee in a custom field (we just need it to inherit the department right now) so that we can then subject the field to permissions
k
Yeah or have custom forms per role and lock them so they are unable to see that column.
Or change the form
a
From a firm perspective is already working since If one of the accounts are used the journal entry is blocked and cannot be viewed. Same in reporting, using summary account. So the problem is journal entries only.
k
Using NS payroll in combination with SuitePeople can give you the control to prevent that - but that's a lot of money for something that doesn't seem that valuable reporting wise to me.
If you use a custom field you can definitely turn off the ability to search it using the role level permissions on the field
a
that's an issue I'm struggling also. I tried to use a class segment to implement such restriction however that didn't end well as other transactions not related to payroll started to inherit the class from employee object and that ruined my idea. I can't use custom employee field as we prepare EFT payments payments from Netsuite. So one more issue is how to restrict for some roles to access payments to employees as Vendor payments and Paycheck payments has the same type of transaction 😭
j
We use NetSuite Payroll w/ SuitePeople, I believe it's only available in the US. I would agree with @KevinJ of Kansas, one of the downsides to NS payroll, is reporting limitations.
a
Agree, we don't have it in EMEA. Anyhow I'm now using a custom field instead of the standard name
Since we don't have to pay using EFT