1. Event Name Here
12/02/2007
Government Gateway Transition and Transformation Brief for Software Developers
March 2017
Project Name: HMRC v1.8

2. Changes to the Government Gateway 2016 - 2018
Event Name Here
12/02/2007
Background
Changes to the Government Gateway
The Government Gateway developed in 2002 is nearing end of life and the current arrangements and support contract for it’s delivery will end by March 2018.
HMRC currently uses Government Gateway to provide some functionality which needs to be migrated to the HMRC multi digital tax platform (MDTP) as part of the introduction of the new version of Government Gateway.
This includes:
Document submission protocol via transaction engine
Enrolment management and Client-Agent relationship migration
Government Gateway will be redeveloped and redesigned with the current version / technology of the service decommissioned and replaced with a new version (currently referred to as Government Gateway 3) providing improvements to security, design and usability.
Project Name: HMRC v1.8

3. Changes to the Government Gateway 2016 - 2018
Introduction
Changes to the Government Gateway
This communication provides information on changes to the current Government Gateway service over the next two years, impacts on software developers and actions required.
This presentation provides an update to the communication issued between July 2016 and January 2017.
Update section headings are highlighted in bold italics

4. Changes to the Government Gateway between 2017 – 2018
Services
ISV VSIPS
Live Gateway
ETS support for all message classes
Live Transaction engine to begin supporting message classes
NOW
April 2017
August 2017
February 2018
Onward

5. Project RATE (Replication of APIs for Transaction Engine)
Event Name Here
12/02/2007
Document submission protocol via transaction engine
Project RATE (Replication of APIs for Transaction Engine)
HMRC is building a replacement Transaction Engine that will support those Government Gateway message classes defined in HMRC tech packs.
The new transaction engine will replicate the Government Gateway Submission Protocol as defined at
The change
Impact on Software Developers
Current domain names
New domains
Available from
secure.dev.gateway.gov.uk
03 April 2017
secure.gateway.gov.uk
01 August 2017
Change in the domain name of the URL for the Transaction Engine end point.
The replacement interaction will give revised end points for poll and submission. If this is hard coded in your products, the URL will need to be changed.
Software developers will need to change their product to use the new end point. A new VSIPS service will be provided to support integration testing.
Timing will NOT support the annual year on year changes for relevant regimes (PAYE inc. RTI and SA).
Software developers will need to support an ‘in-year’ change.
Project Name: HMRC v1.8 5

6. Project RATE (Replication of APIs for Transaction Engine)
Event Name Here
12/02/2007
Document submission protocol via transaction engine
Project RATE (Replication of APIs for Transaction Engine)
The replacement transaction engine service will be run in parallel with the existing transaction engine to allow for testing (so you can assure yourselves that you get the same behaviour with the replacement functionality) and a managed migration.
The expectation is that the migration will be conducted between 03 April 2017 and 14 Feb 2018:
HMRC is making all message classes available in the new transaction engine called External Test Service ( ) from 03 April 2017.
The test services for both current and new transaction engine (VSIPS and new External Test Service)will remain available until 14 Feb 2018.
HMRC will start making message classes available in the new transaction engine on Live environment ( from 01 August 2017.
Software Developers will need to update their software to change from using the old end points and start using the new end points.
Recommendation for software developers is to test their software against the new end points using External Test Service before migrating their software in production environment.
From 14 Feb 2018 all message classes will be suspended in the existing Government Gateway, for both test and production environment. After which any submissions for these message classes to the existing Government Gateway will result in rejection.
Migration approach
March 2017
Project Name: HMRC v1.8 6

7. Project RATE (Replication of APIs for Transaction Engine)
Event Name Here
12/02/2007
Document submission protocol via transaction engine
Project RATE (Replication of APIs for Transaction Engine)
What is expected from software developers between April 2017 and Feb 2018?
Software developers will be asked to test their software against the new HMRC Transaction Engine using the External Test Service . HMRC will make the message classes shown in the next slide available in the new External test Service
Software developers should exercise the Document Submission Protocol against the new endpoint by:
Making submission requests
Processing the returned submission acknowledgement
Poll for the response
Processing the returned business response
Making a delete request
Processing the returned delete response
Making a data request (if supported by their product)
Processing the returned data response
Whilst this is exercising the 'happy path' vendors may also want to undertake some negative testing to assure the behaviour is as expected for their product(s).
Test Approach for new External Test Service
Note
We encourage software developers to update to live service as soon as possible after 01 August 2017, after successfully testing their software using the external test service
Project Name: HMRC v1.8

8. Project RATE (Replication of APIs for Transaction Engine)
Document submission protocol via transaction engine
HMRC-PSA-PRAC-DEAUTH
HMRC-PSA-RAS
HMRC-PSA-REG
HMRC-PSA-RET
HMRC-SA-SA100
HMRC-SA-SA100-ATT
HMRC-SA-SA100-ATT-TIL
HMRC-SA-SA100-TIL
HMRC-SA-SA800
HMRC-SA-SA800-ATT
HMRC-SA-SA800-ATT-TIL
HMRC-SA-SA800-TIL
HMRC-SA-SA900
HMRC-SA-SA900-ATT
HMRC-SA-SA900-ATT-TIL
HMRC-SA-SA900-TIL
HMRC-VAT-DEC
HMRC-VAT-DEC-TIL
IR-AA-CT
IR-AA-PAYE
IR-AA-SA
IR-CIS-CIS300MR
IR-CIS-VERIFY
IR-CTF-annualReturn (Not for Testing)
IR-PAYE-EOY
IR-PAYE-EXB
IR-PAYE-MOV
IR-PAYE-MOV-TIL
IR-PAYE-P38A
IR-SDLT-LTR
List of
External
Message Classes
HMCE-ECSL-ORG-V101
HMCE-NES-EDIFACT
HMRC-CHAR-CLM
HMRC-CHAR-CLM-MULTI
HMRC-CT-CT600
HMRC-CT-CT600-TIL
HMRC-PAYE-RTI-EAS
HMRC-PAYE-RTI-EAS-TIL
HMRC-PAYE-RTI-EPS
HMRC-PAYE-RTI-EPS-TIL
HMRC-PAYE-RTI-EYU
HMRC-PAYE-RTI-EYU-TIL
HMRC-PAYE-RTI-FPS
HMRC-PAYE-RTI-FPS-TIL
HMRC-PAYE-RTI-NVR
HMRC-PAYE-RTI-NVR-TIL
HMRC-PP-ACCT-TAX
HMRC-PP-AMD-DETS
HMRC-PP-EVNT-REP
HMRC-PP-MAINT-SCM
HMRC-PP-PRAC-DEAUTH
HMRC-PP-RAS
HMRC-PP-RET
HMRC-PSA-ACCT-TAX
HMRC-PSA-ADD-SCHA
HMRC-PSA-AMD-DETS
HMRC-PSA-ASSC-SA
HMRC-PSA-EVNT-REP
HMRC-PSA-MAINT-SCM
HMRC-PSA-PRAC-AUTH

9. Document submission protocol via transaction engine
Event Name Here
12/02/2007
Document submission protocol via transaction engine
Project RATE (Replication of APIs for Transaction Engine)
What is the new endpoint for the test HMRC Transaction Engine service?
The test HMRC Transaction Engine Service can be accessed using endpoint. The following URI’s will be available:
/submission - for submission requests, delete requests and data requests
/poll - for poll requests
ISV Test
End Points for Public Beta
Note
Poll requests will not be accepted on the /submission URI
Submission requests, delete requests or data requests will not be accepted on the /poll URI
GovTalk envelope version
Which GovTalk envelope versions will be accepted by the HMRC Transaction Engine?
Only GovTalk envelope versions 1.0 and 2.0 will be accepted by the HMRC Transaction Engine?
Project Name: HMRC v1.8