* 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.
Back to Contents
Transaction Engine Live Environment – last call to software developers 12 December 2017
Further to HMRC’s update in October, if you have not yet done so, please configure your products to point to the new Live Endpoint to avoid any issues with future submissions.
HMRC’s Software Developers Support Team (SDST) is encouraging developers to move over as early as possible so that they have enough time to resolve any issues that might arise.
From 14 February 2018 all message classes will be suspended in the existing Government Gateway, for both test and production environment.
The new Transaction engine is live and SDST is encouraging developers to move over early as possible so that they have enough time to resolve any issues that might arise. The results that they are seeing from the new engine are all good and there have not been any problems worth mentioning so far from the relatively high numbers of submissions. Submissions that go missing can sometimes take days to find. If your transition to the new engine is towards the last days of the deadline and some of your submissions to the old system go missing, and the old gateway is turned off, your submissions will be lost as SDST will no longer be able to search for them. This could result in a number of issues for you.
The Chartered Institute of Payroll Professionals
Policy News Journal
cipp.org.uk
Page 362 of 516
Made with FlippingBook - Online magazine maker