Who's Online Now
0 registered members (), 3 guests, and 17 spiders.
Key: Admin, Global Mod, Mod
Newest Members
SAI, Balasubramaniam, Dataterrain, Sarathy R, pjchiverton
1258 Registered Users
Recent Posts
Warning: VAT scam
by CT. 19/10/17 09:27 AM
EDI Replacement
by PaulD. 12/10/17 10:27 AM
Future dated records and API
by hpatel15. 10/10/17 08:04 AM
Faster Payments
by pat. 04/10/17 08:56 AM
Additional Org Info: Org Developer DF
by Sarathy R. 04/10/17 06:54 AM
Monthly Data Collection
by hpatel15. 28/09/17 07:33 AM
Top Posters(30 Days)
SBi 2
PaulD 2
CT 1
delboy 1
pat 1
Bobin 1
Popular Topics(Views)
417,709 PAYE RTI
49,884 HR_PF.K RUP4
Previous Thread
Next Thread
Print Thread
Rate This Thread
Page 2 of 2 1 2
#12014 - 29/08/17 02:30 PM Re: EDI Replacement [Re: PaulD]  
Joined: Mar 2005
Posts: 1,250
delboy Offline
The Grand Daddy
delboy  Offline
The Grand Daddy

Joined: Mar 2005
Posts: 1,250
Somewhere in South of England
White Paper is now available. Suggests that only direct interface will be available, unless I am missing something. Does anyone know if that's the case. We currently use a third party software and in the short term will have to continue. I assume we will still be able to copy the output file and continue to transmit via this method?

#12057 - 05/10/17 09:19 AM Re: EDI Replacement [Re: PaulD]  
Joined: Aug 2016
Posts: 8
PaulD Offline
PaulD  Offline

Joined: Aug 2016
Posts: 8
The Oracle User Group Public Sector SIG was well attended with a lot of enthusiastic Oracle Local Government and University end users. Here are my notes from the meeting about the EDI Decommissioning changes

EDI Decommissioning

Oracle: Alison Ford
HRMS: David Sutcliffe

21st September


The deadline for changing to the new XML format is April 19th (Last date for 2017/2018 TYE submission). Oracle advised that we pause applying the current version of the patches until the EAP has completed and any revised patches are released. Oracle confirmed that the EDI Replacement patch will include a XML Handshake Solution needed to connect to HMRC Gateway. If required an air gap may still be implemented.

HMRC said that dynamic IP addressing will be in-place for connecting to the HMRC Gateway, a static URL will not be used for security purposes.

XML File Storage Type

The new Oracle Connection Method has the options of
• File System and Database
• Secure Database
Oracle's response was that selecting Secure Database means that no output file is created, this is a security measure to better restrict access to the confidential employee information. If we are implementing an air gap between production and HMRC Gateway we will not want to select this option.

Inbound to HMRC

When running the new versions of the RTI processes (FPS, EPS, AFPS and EYU) there is a Gateway Test Indicator parameter. This allows the following options
• Yes
• No
• Test in Live
The Test in Live option is just that, the transmitted file is acknowledged as valid by HMRC but not credited to the client account.

HMRC Outbound

For the files sent from HMRC Gateway to JLP, items such as new tax codes, P6 and Student Loan notifications, SL1 & SL2, there is no facility to send a test file. Only live files may be sent.

When pulling files such as the P6, which may be sent daily, it is possible to reset the High Water Mark to be able to pull previously selected files. So if the mark was 10,000 on Monday but 12,000 on Friday, resetting it to 10,000 would allow those 2,000 records to be re-extracted from HMRC.

Once the new format linked to the HMRC Gateway account for JLP has been set to XML it cannot be changed back to the old format. This makes the testing of files from HMRC difficult to test outside of production. David did assure the audience that the file format from HMRC have been comprehensively tested (although that does not mean that Oracle will process the file correctly, as he was told by several of the audience members). That will be an issue for Oracle to help resolve but will be an issue for our testing.


According to oracle document 2262186.1, it appear that the final patch details are as follows
Patch #1D : Final Patch for EDI Decommissioning : Post EAP Program
Patches/Release Date : Tentative : 6th November 2017

Is there anyone out there on the EAP, is so how's it going?

#12060 - 11/10/17 05:33 AM Re: EDI Replacement [Re: PaulD]  
Joined: Mar 2005
Posts: 1,250
delboy Offline
The Grand Daddy
delboy  Offline
The Grand Daddy

Joined: Mar 2005
Posts: 1,250
Somewhere in South of England
Thanks for the update Paul.

#12061 - 12/10/17 10:27 AM Re: EDI Replacement [Re: PaulD]  
Joined: Aug 2016
Posts: 8
PaulD Offline
PaulD  Offline

Joined: Aug 2016
Posts: 8
We've just had a visit from David Sutcliff, HMRC to answer some questions that we had with the EDI Decommissioning work. We're looking to go live in February with the B2B solution rather than sending the RTI output files to another server and then a 3rd party tfor transmission to HMRC. So once the final EDI patch is released in November we will start our testing.

Here are some updates he provided us.

David said that with compression enabled he expected >100,000 records per 20MB limit on file size. Without compression then his estimate was 25,000 records per 20MB limit. He also said that the file transfer to and from HMRC would be much quicker using XML compared to the old EDI interface. It seems that currently HMRC 'translates' the current EDI file format into XML, which slows the validation process. He also said that certain days of the month will be potentially slower if they coincide with pay dates for big employers, so last day of the month for the civil service for example. Obvious when you think about it!

Another recommendation was to only use the live server and setting the RTI processes parameter Gateway Test Indicator to 'Test in Live' for all testing purposes. This means that only one domain needs adding for development, System Test, UAT and Live. His rational for that was that there may be an issue with sending large files to the test domain as it's only supposed to be used for low volume testing.

Prior to 19th April 2018 the Incoming (from HMRC) files may be switched between the new XML format and the old EDI format. The 19th April is a brick wall, after that the format will be XML only, no going back! If the live domain is used for testing then we can easily reset the high water mark date to assist testing P6 and SL1/2 notifications.

It's sometimes worth looking beyound our Oracle world as there are some large, non-Oracle payroll, employers currently live using the new XML format, so that part of the system works, it just the Oracle part we need to fully test and that is more something under out control, right!? He was actually complementary about Oracle compared to another system supplier!

Hope this is useful

Paul D

Page 2 of 2 1 2

Moderated by  CT, delboy 

Forum Statistics
Most Online90
Mar 5th, 2017
Today's Birthdays
No Birthdays
Recent vacancies
Top Posters(All Time)
CT 2,086
bcooper 1,285
delboy 1,250
paulgos 431
SBi 425
Gus 252
pat 249
vkumar 223
1 2 3 4 5 6 7
8 9 10 11 12 13 14
15 16 17 18 19 20 21
22 23 24 25 26 27 28
29 30 31
Powered by UBB.threads™ PHP Forum Software 7.6.0
Page Time: 0.020s Queries: 16 (0.005s) Memory: 2.7551 MB (Peak: 2.9133 MB) Zlib disabled. Server Time: 2017-10-21 19:26:46 UTC