- Log in to BrightPay using your usual credentials.
- Find the employer, whose payroll file you'd like to share.
- Navigate to the Analysis section, and run the reports that you wish to share.
- Share and Export the Report, in your preferred format (CSV, Download as PDF).
- Save the exported file to your desired location.
- Share the file securely: using password (recommended)
To download employee details to transfer information to another accountant / bureau, follow the below steps:
Export employees' details to CSV file
Go to the Employees tab > Import & Export > Export Employees to CSV File.
Select the data items you wish to export or click ‘Select All’ and click Continue.
Click Download.
When taking over payroll mid-year from another payroll processor, the first pay period you set up in BrightPay should be the next consecutive pay period that would have been run by the previous accountant or bureau.
It is crucial to ensure alignment with Year-to-Date (YTD) information entered into the Mid-Year Totals section. Year-to-date figures (gross pay, tax, PRSI, USC, pension contributions, etc.) are cumulative
and depend on continuity.
The week / fortnight / month number in BrightPay are determined by the payment date. If after setting up your schedule, the first period on BrightPay is showing as the last period processed by the old accountant, it may be either the period end or the payment date has been set up incorrectly. As you will not want to duplicate an already processed period, the schedule needs to be amended.
Click on the 'Schedules' icon in the Payroll tab > Edit Schedule. Check the period end and payment date is set up in line with the next payment that the employees are due to be paid. You can amend the payment date if it is incorrect. If the period end is also incorrect, the schedule can be deleted and set up again with the correct period end date (provided no payroll has yet been processed and submitted to Revenue). Note that deleting the schedule will remove any hours / salary entered for employees.
Comments
0 comments
Article is closed for comments.