Software developers: PAYE for employers API

04 December 2017

Following on from a workshop on 1 November, HMRC’s Software Developers Support Team (SDST) is asking for views and a level of interest in developing an API which provides data at employee level.

HMRC is planning to deliver a new PAYE for employers API. The API will retrieve RTI data at PAYE scheme level; the list of functionality and data fields that can be called is below.

Monthly totals for all outstanding RTI bills, including interest

List of fields that will be displayed:

  •  Employer ID (UTR)
  • Tax month
  • Due date
  • Start date
  • End date
  • Monthly total for RTI
  • Associated interest
  • Itemised non-RTI charges
  • Associated interest for non-RTI charges
  • Date and time stamp (current time)

Display: Outstanding amount - by tax period by month for all taxes and credits

List of fields that will be displayed:

All taxes and credits by month including:

  • Credits
  • Charges
  • Payments
  • Date and time stamp (current time)

Breakdown by tax/credit type

List of fields that will be displayed:

  • RTI charges
  • Non RTI charges
  • Credits
  • Date and time stamp (current time)
  • Payment allocations

Current plans are to release this API to the testing environment – the Developer Sandbox – in January 2018, and to the Live environment by the end of February 2018.

SDST invited interested parties to a developer workshop on 1 November to assess attendees’ appetite to develop against these. SDST is now asking for your views and level of interest in developing to an API which provides data at employee level.

To help with this understanding SDST would really appreciate it if you could reply to the following question (by Thursday 7 December please):

If the API remains limited to scheme level data – that is, if HMRC do not build an API supplying employer RTI data at employee level – will you still consider building against the API at only scheme level in your product(s)? SDST would like to understand if the answer to that would be no, and the reasons why.

Thank you for your input.