Hi all, We are building a Payroll SuiteApp because our country has a weird law 🙂 Anyway, I just wanted to ask, is there any benefits from using the standard Paycheck journals, instead of creating a normal journal? Note that the data that is associated with the paycheck (earnings & deductions), we are already saving it somewhere else.

Which jurisdiction are you doing, @Marwan? We do AU, NZ and UK atm and do it all with standard journals, custom records, etc. We don't use paycheck journals.

Egypt, a little bit messy. So standard journals works just fine, good to know, I think we will do the same.

Just a guess but if you have regular journals with payroll info it would probably be harder to lock down access for users who otherwise need journal access compared to a payroll specific record.

whilst a valid observation, that is not ever raised as an issue as anyone who is currently importing payroll journals from a 3rd party is doing so using standard journals so they're not losing anything.

If you are importing from third party payroll system at a summary level that might not be an issue. For a Payroll SuiteApp I imagine you would need more detailed postings

Which we do, and the postings are grouped by DCL and account (amongst others). We have over 700 customers using this, not once has access to those journals ever been queried.

@michoel Good point, I think we will restrict everything in the app to a few roles, and we can use a UserEvent script (beforeLoad) on the journals to restrict them too.

@Marwan keep in mind a UE can't prevent records from being accessed via searches etc

Hmm, didn't think about that 😫 Will tell my team and rethink this, thanks 🙏

If you can't use a payroll journal I guess the other option is to keep as much of the sensitive data as possible in a restricted custom record and use journals only for posting the summarized data

@michoel One of our financial team says cost centers or classes could be restricted for certain roles, I am not sure, will try it when we reach that part.