The Accounts tab in PayHero allows you to set up account codes for each of your Pay Items, allowing for easy journal reporting for your accounting system.
For companies using Xero as your accounting system you can use our Xero Integration to automatically send payroll invoices to Xero instead, and you'll see the Xero Settings tab instead.
Pay Item Account Codes
To set up your pay item Accounts, simply navigate to Manage > Accounts and click the button to select any pay items you'll be using in PayHero, then click Add Selected Pay Items.
You can then specify the appropriate account code for each of your pay items.
Team Account Codes
Using Teams in PayHero you're able to apply a different Account Code to be used depending on the employee and their Primary Team. This enables different Account Codes to be used to separate your different cost centers.
To do so, first select the 'Use Team Account Code' checkbox on any Pay Items which require multiple Account Codes.
Instead of defaulting to the GL Code set under Manage > Accounts, any pay items with the 'Use Team Account Code' option checked will default to the Account Code set on the employee's 'Primary Team'. The employee will have their Primary Team shown under the People > Employee list, and will have a star icon alongside their name in their Primary Team.
In the example below, Emma and Jane will have their Salary and Sick Leave earnings coded against the '478' Account Code as that is what is set on their Primary Team.
Building Account Code Report
Once your account codes are set up and you've processed a pay, you'll be able to create a Table Report via the Insights section of PayHero to report on payments and their associated account code, and download a CSV export. This report can be customised to suit the level of breakdown you're looking for, but would always use the Pay Detail table. A common example of which categories and measures should be included would be as follows:
This report can be filtered to only include details for a specific pay period as shown here:
Comments
0 comments
Article is closed for comments.