Invent

A new electronic message to help employers keep up to date with their PAYE


HMRC is introducing another new message to help employers keep their PAYE up to date.
This electronic message tells the employer that they haven’t sent one or more of the Full Payment Submissions (FPS) that were expected for the last month. It reminds the employer that they must send an FPS each time they pay their employees.
HMRC will start to issue these messages gradually so they can monitor and review the message service to ensure it is as efficient and thorough as possible.

Non-filing message exceptions

There are two instances where an employer may receive a non-filing message although they have filed on time.
These are:
  • when an FPS has been sent in advance for this tax year – for example, a sole director/employee planning to take the same earnings each month may have submitted 12 FPS in April for the full year
  • where HMRC has received an Employer Payment Summary (EPS) before 14 October 2013 that reports a ‘period of inactivity’ – for example, if an employer has sent an EPS in August 2013 to report a period of inactivity from September 2013 to February 2014
In either instance, if an employer receives a non-filing message they do not need to take any further action.
Employers will not necessarily receive a message in every instance of late filing or failure to file. There is therefore no need for employers to contact HMRC if they think they should have received a message but have not done so.

2013-14

Although there are no in-year penalties for late filing and/or payment for the current tax year, employers are reminded that they are liable to penalties after the end of the tax year:
  • if they do not report the final payments made to an employee or pension recipient by 19 May following the end of the tax year
  • for failure to pay on time (Schedule 56 Finance Act 2009)
Please see HMRC’s guidance on ‘What happens if you don’t report payroll information on time’.
What happens if you don’t report payroll information on time

More information on the new electronic messages

All of the electronic messages are aimed at helping employers bring their PAYE up to date and will remind employers that:
  • from April 2014, if they don’t pay or report on time, they may incur penalties in-year rather than incurring them after the end of the year as now
  • if they had no PAYE payment to make because they did not pay any employees during a particular period, they should let HMRC know by sending an Employer Payment Summary (EPS)
There’s full information on how to view these electronic messages in the What’s New message published on 21 October 2013.
Helping employers keep up to date with their PAYE

Leave a Reply

Your email address will not be published. Required fields are marked *

Visit also our social profiles:

Scroll to top
Twitter
DurantServices on Twitter
Latest Tweet:
Warning: Illegal string offset 'latest' in /home3/sdurant/public_html/wp-content/plugins/wp-flybox/includes/twitter_content.php on line 160
Y

Warning: Illegal string offset 'followers_count' in /home3/sdurant/public_html/wp-content/plugins/wp-flybox/includes/twitter_content.php on line 171

Warning: number_format() expects parameter 1 to be double, string given in /home3/sdurant/public_html/wp-content/plugins/wp-flybox/includes/twitter_content.php on line 171
people follow DurantServices

Warning: Illegal string offset 'followers' in /home3/sdurant/public_html/wp-content/plugins/wp-flybox/includes/twitter_content.php on line 180

Warning: Illegal string offset 'followers' in /home3/sdurant/public_html/wp-content/plugins/wp-flybox/includes/twitter_content.php on line 180

Warning: Illegal string offset 'followers' in /home3/sdurant/public_html/wp-content/plugins/wp-flybox/includes/twitter_content.php on line 181
Twitter Pic
Warning: Illegal string offset 'followers' in /home3/sdurant/public_html/wp-content/plugins/wp-flybox/includes/twitter_content.php on line 191

Warning: Illegal string offset 'screen_name' in /home3/sdurant/public_html/wp-content/plugins/wp-flybox/includes/twitter_content.php on line 191
Y