• Payroll Year End 2026
    See our Webinars

KB Category: Sage Payroll (Micropay)

Pension Tracing Numbers

Pension Tracing Numbers

 

If you have employees that are members of an approved occupational pension scheme or a personal retirement savings accounts (PRSA), you should include their pension tracing numbers on your P35 Year End submission to Revenue.

These numbers aren’t applicable to pension related deductions (PRD) and construction workers pension schemes (CWPS).

Your pension provider tells you what the pension tracing number is for each of your policies/schemes. All employees that contribute to a company pension will have the same pension tracing number and you must then enter this information in their employee records.

If you have a large number of employees to update, to save time, you can import pension tracing numbers directly in to Sage Micropay using the Data Import option.

 

Manually enter pension tracing numbers

1. On the menu bar, click Processing then click Employee Details.

2. Next to the Surname box, click browse  and click the relevant employee.

 

3. Click the Deductions tab.

4. Under Pension, in the Pension Tracing Number box, enter the relevant number.

 

The format of the pension tracing number is “PBXXXXXX”, where XXXXXX is a number with up to 6 digits. For example, PB123456

 

5. Click Save.

If you enter an invalid pension tracing number, a warning message appears and you must repeat steps 4 and 5.

 

6. Repeat steps 2 to 5 for each employee that is a member of an Approved Occupational Pension Scheme.

 

Import pension tracing numbers

 

1. Open Sage Paryoll and log in to a payroll as normal.

2. On the menu bar, click Help then click System Information.

 

3. Make a note of the Data Directory link.

 

4. On the menu bar, click Reports then click Report Writer.

 

5. Click File, then click Open.

 

6. Select PensionT.rpt , then click Open

 

 

7. Click Process.

 

A report listing all employees in your payroll appears on-screen.

 

8. Click File, then click Save As.

 

9. Click the Save in arrow, then browse to the location you noted in step 3.

 

10. In the File name box, type pensiont.csv.

 

11. Click Save.

 

12. Close Micropay and browse to the location you noted in step 3.

 

13. Right-click the file pensiont.csv, then click Open with. Select Excel then click OK.

 

14. Under the column E, enter the pension tracing number for each relevant employee.

 

The format of the pension tracing number is “PBXXXXXX”, where XXXXXX is a number with up to 6 digits. For example, PB123456.

15. For all employees that aren’t members of an approved occupational pension scheme or a personal retirement savings accounts (PRSA), remove their values or delete the relevant row.

16. Under the column A, check your employees’ numbers are correct. Edit, if required.

 

Each employee number on the import file must match the exact employee number in Sage Micropay. For example, if the employee is set up in Sage Micropay as number 0054, the import file won’t accept 54 as the employee’s number. For more information about how to create custom number formats in Microsoft Excel, please refer to article 11995.

 

17. Click File, then click Save.

 

If the Data Directory link that you noted in step 3 is C:\ProgramData\Micropay Professional/2017, skip to step 24. If it’s not, you must correct the Sage Micropay data path specified within the import file. To do this, please complete steps 19 to 23.

 

18. Click the Data Directory link.

 

19. Right-click the file PENSIONT.IMP, then click Open with.

 

20. When prompted, select Notepad then click OK.

 

21. Locate the data= entry line, then edit the highlighted section below so it matches your Sage Payroll data directory location:

data=C:\PROGRAMDATA\MICROPAY PROFESSIONAL\2017\PENSIONT.CSV

 

22. Click File, then click Save.

23. Click File, then click Exit.

 

24. Open Sage Micropay and log in to a payroll as normal.

Before you proceed any further, you must take a back up of your payroll data.

 

25. On the menu bar, click Miscellaneous, point to Data Import then click Data Import.

 

26. Browse to the location you noted in step 3.

 

27. Select PENSIONT.IMP then click Open.

 

28. Repeat steps 4 to 7 again and check the correct pension tracing numbers appear for each of the relevant employees.

If not, you must restore the back up you took before you ran the import process and complete the steps detailed in this section again.

 

 

 

PAYE Exclusion Order [V21.1 and Higher]

PAYE Exclusion Order

 

A PAYE Exclusion Order is a certificate issued by Revenue that authorises you to not deduct income tax and/or Universal Social Charge (USC) from an employee’s pay. If you receive a PAYE exclusion order, you should enter its details immediately on the relevant employee’s record.

You can get details of how to get an exclusion order from the link below:

https://www.revenue.ie/en/employing-people/what-constitutes-pay/paye-exclusion-order-issued-by-revenue/index.aspx

The exclusion order will come in on the RPN but if you need to manually enter you can do the following:

1. Open your payroll

 

2. Select the relevant employee

 

3. Tick the box to apply PAYE Exclusion Order

 

4. Enter in the from and to dates for the exclusion order

Director setting (required for PAYE Modernisation) (V21.1)

Director setting

 

If the employee is a director of the company, select the Director checkbox then specify the relevant ‘Type’.

The Director Type indicates whether or not the employee is a proprietary director.

A proprietary director is the company’s beneficial owner (or director) who can control directly or indirectly more than 15% of the company’s ordinary share capital.

 

1. Select Edit Employees from Processing employees or click on Edit Employees on the process map.

 

2. Click on code … and browse for the relevant employee

 

3. In the first tab Personnel select if the employee is a director and the type of director

 

4. Click Save

 

 

 

Sage RTX Service – White list URLs – Customer guide

Sage RTX Service – Customer guide

The Sage Payroll system consists of many parts, but we will talk about them at a high-level here:

  • The Sage Payroll desktop software you interact with on a daily basis.
  • Web services (online processing of data to be submitted to revenue).

Sage has developed a web service platform that facilitates integration with government gateways including the Revenue ROS service for PAYE Modernisation. This service is provisioned with AWS.

 

Security

 

The service has been developed using secure development and test procedures and guidelines. AWS Shield is used to mitigate against attack as well as providing a level of web application firewall capability. All interfaces are secured authentication and use encrypted channels.

 

Protecting data/regulatory compliance

 

The RTX Service is fully compliant with UK Data Protection Act 1998 and supports the EU General Data Protection Regulation (GDPR).

 

URLs to be Whitelisted

 

The following URLs are used by Sage in the process of connecting to the Revenue service for PAYE Modernisation.

 

Item URL Description
Sage RTX Service* https://api-rtx-ie-prod-ros.sagertx.com The URL of the Sage Real Time Exchange (RTX) Service. This is where the product sends the data that we need to be able to process anything.
Amazon Web Service S3 buckets* https://rtx-ie-prod-ros-s3-eu-west-1-files.s3.eu-west-1.amazonaws.com Amazon Web Service is the cloud infrastructure that Sage use to host, process and store the information for the Sage Real Time Exchange (RTX) Service.
Sage Token Service* https://www.sagetokenservice.com Sage Token Service is used to authenticate your interactions with Sage Services.

* Please note that none of the above will work when viewed via a web browser. The above URLs need to be accessed via defined protocols and secured requests.

 

Data transit and storage

 

For full details of Sage Governance, please visit https://trust.sage.com/governance

 

Data in transit

 

Data in transit from desktop to Revenue is transmitted via encrypted channels and secured with authentication.

 

AWS

 

Data pertaining to submissions is stored in an S3 bucket in AWS.  This bucket has server-side encryption configured. When you use server-side encryption, Amazon S3 encrypts an object before saving it to disk in its data centres and decrypts it when you download the objects. The exact fields stored in this data differs per client but its will be a superset of the data required to generate the necessary submissions.

 

Mongo DB

 

Data pertaining to registration and the configuration of the service is stored in a MongoDB cluster. Collections are:

  • Organisation.
  • Company.
  • Subscription.
  • Tracking.
  • RequestMetadata.

There is no sensitive data stored in any of these collections. Nevertheless, all data is encrypted at rest and access is limited to appropriate personnel.

 

AWS Parameter store

 

Data pertaining to the configuration of the service is stored in AWS Parameter Store.  Typical values are database connection strings and passwords.  AWS Systems Manager Parameter Store provides secure, hierarchical storage for configuration data management and secrets management.  All values are saved as secure strings and access is limited to appropriate personnel.

What data is stored

 

Only data which is critical to the function of the RTX Service is stored, and a thorough assessment of this data has been conducted prior to the design and implementation of the system.
For the purpose of the RTX Service, the Data Processor is Sage UK Ltd.

 

 

Legislation introduced in 2018

Legislation introduced for 2019

This article highlights the legislation changes that were introduced in 2018 for January 2019.

 

Emergency tax

 

From 1 January 2019, there is an increase of €750.00 in the income tax standard rate band for all earners.

Rules of Emergency tax

Whether an employee has a PPS number or not, and the length of time the employee is on Emergency tax status have a direct impact on how their Emergency tax calculates. The following rules apply in the:

2019 tax year
If the employee has a PPS number
Length of time on emergency tax status Tax rate 1 cut-off point Tax credits
Month 1, or week 1 to 4 2942.00 monthly, or
679.00 weekly
0.00
Month 2, or week 5 to 8 0.00 0.00
Month 3, or week 9 onwards 0.00 0.00

If an employee doesn’t have a PPS number, they must pay the higher rate of tax (40%) on all of their taxable earnings in a period.

 

 

 

Universal social charge (USC)

The following rates and thresholds apply from 1 January 2018:

Rates Yearly earnings
0.5% 0.01 – 12,012.00
2% 12,012.01 – 19,372.00
4.75% 19,372.01 – 70,044.00
8% 70,044.00 and above

 

Employees aged 70 or older, and medical card holders are exempt from paying USC at rates 4.75% and 8%. If your employees earn less than €13,000 in the year, they’re exempt from USC.

 

Pay related social insurance (PRSI)

Employee PRSI rates remain unchanged, but the employer PSRI rates have increased by 0.1% for all subclasses except JO, which remains at 0.5%. Also, the employer PRSI threshold has increased from €376 per week to €386.

 

Increase in minimum wage rate

The minimum wage has increased from €9.55 to €9.80.

 

Revenue Payroll Notifications (RPNs) replacing P2C certificates

From 1 January 2019, you’ll be required to request the most up to date RPNs for your employees before you process their pay details each period. RPNs provide you with the necessary information to deduct from your employees the correct tax, universal social charge (USC) and local property tax (LPT), if applicable.

RPNs will be made available to you, for each employee that is currently registered with Revenue as working for your company, before 1 January 2019. Please ensure that you’ve registered your payrolls to use the Sage Services to ROS so you can automatically retrieve RPNs from within your Sage Payroll 2019 software.

 

Introduction of Additional Superannuation Contribution (ASC)

ASC calculations come into effect from 1 January 2019 and replace the Pension Related Deduction (PRD). ASC is provided for under Part 4 of the Public Service Pay and Pensions Act 2017. Read more about ASC >

 

P45, P46, P45 (Part 3), P30 and P35 returns no longer valid from 2019

From 1 January 2019, the traditional reporting structure that businesses used in 2018 and previous years (such as P30, P35 and P45) ceases to exist. Instead under the new Real Time Reporting (RTR) legislation, you must send a payroll submission electronically to Revenue each time you pay your employees. You can quickly and easily do this in Sage Payroll 2019 by using the Send Payroll Submission option.

The payroll submission you make each pay period to Revenue contains:

  • Details of all payments made to your employees in the pay run.
  • The total tax, universal social charge (USC), pay related social insurance (PRSI), and if applicable local property tax (LPT) paid by your employees in the pay run.
  • Employee details, such as name, PPS number, Employment ID and tax/USC status.
  • Details of any starters or leavers from the pay run, and more information.

All payroll submissions sent by you to Revenue in respect of a month will form the basis of a statement that will be provided to you by Revenue outlining your PAYE liabilities for that month.

 

Additional Superannuation Contribution (ASC) – the basics (Replacing PRD)

Additional Superannuation Contribution (ASC) – the basics

Additional Superannuation Contribution (ASC) will be introduced with effect from 1 January 2019 and replace the Pension Related Deduction (PRD). ASC is provided for under Part 4 of the Public Service Pay and Pensions Act 2017. Whereas PRD was a temporary emergency measure, ASC is a permanent contribution in respect of pensionable pay. Here are some other important points of information you need to be aware of :

  • Unlike PRD, ASC will only apply to a person who is a member of a public service pension scheme or receives a payment-in-lieu of pension.
  • Unlike PRD, ASC will only apply to pensionable remuneration, so non-pensionable allowances and non-pensionable overtime will not be subject to ASC (whereas they are subject to PRD).
  • PRD was chargeable where remuneration was taxable. Unlike PRD, ASC will apply to all pensionable remuneration whether taxable or otherwise. Thus non-taxable pensionable allowances and emoluments will become liable for ASC.
  • Unlike PRD, ASC is charged at different rates with different threshold bands depending on the pension scheme a person is a member of and the pension terms applying to such membership. Therefore, it is very important that an individual is correctly identified on the system in respect of the relevant pension scheme membership and terms applying.
  • Week 53 scenario – For those payrolls for which there is an extra pay week (week 53/fortnight 27), an extra set of thresholds should be applied in that particular week. That set of thresholds should be added on “Week 1” basis, not cumulative.
  • Like PRD, ASC is chargeable on all pensionable remuneration across multiple pension scheme employers and based on the combined pensionable remuneration in such employments. The procedure for calculating main and subsidiary employments will pertain in respect of ASC as pertained in respect of PRD.
  • There is employer PRSI relief in respect of ASC. However, ASC don’t qualify for employee PRSI relief.
  • ASC will qualify for tax relief, but not Universal Social Charge (USC) relief.
  • ASC will not be included for the purpose of calculating age-related tax relief thresholds.

 

ASC rates and annual earning thresholds

 

The following rates and thresholds apply from 1 January 2019:

 

Member of a standard accrual pension scheme
Annual earning thresholds Rates
Up to €32,000.00 0%
From €32,000.01 to €60,000.00 10%
€60,000.01 and above 10.5%
Member of a fast accrual pension scheme
Annual earning thresholds Rates
Up to €28,750.00 0%
From €28,750.01 to €60,000.00 10%
€60,000.01 and above 10.5%
Member of the single scheme
Annual earning thresholds Rates
Up to €32,000.00 0%
From €32,000.01 to €60,000.00 6.66%
€60,000.01 and above 7%

For more details on setting up ASC click here

 

Pimbrook Software
Privacy Overview

This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.