Upload
others
View
2
Download
0
Embed Size (px)
Citation preview
Word Excellence Day
Presentation by
Mike Boynes and Stephen Martin
E-submission Charge Registration
Companies House
Summary:
Pre-submission:
• Create charge, attach PDF Legal Instruments from DMS
• Share the document, including any attachments with an authorizer for approval – paper
sharing accommodated
• Documents can be amended by the author, or the authorizer if required
• Validation can then take place
• Once internally approved all documents can be e-submitted via XML to the Government
Gateway
Post-submission:
• On approval the CH Certificate returns via XML
• Check in to DMS or CMS
• Create and save a PDF of the transaction to DMS including legal instruments
System:
The e-submission system will minimise the risk, allowing the relevant authorization to take
place prior to submission, with the facility for file reviews at any time a complete audit
Companies house E-submissions MR01
Oyez GatewayDepartment Administration
Oyez GatewayUser Administration
Oyez GatewayMy Dashboard
Oyez GatewayGlobal Dashboard
Oyez GatewayMR01 Being Edited
Gateway Simple User Interface
• Create new, MR01, MR02, MR04, MR05
• Complete charge, save to DMS as PDF, 21 day
deadline is tracked.
• Charge validated for completeness
• Upload PDF Legal Instrument from DMS
• Upload PDF accompanying letter from DMS
• View own submission progress
• Approver view of submissions to be approved
• View Global submissions
Internal Approval Process
• Approver is invited, submission awaiting action
• Approver reviews submission
• Submission is internally approved or rejected with
details of the rejection
• Creator, informed of rejection
• Creator makes the required changes
• Creator can then E-submit to the CH Gateway
• Complete audit trail of submission progress
Companies House Gateway
• The charge is submitted via XML to Gateway
• Submission is validated by the Gateway
• Approved or Rejected, with a 2 day turn around
• On approval, the certificate is returned via XML
• On Rejection, examiners comments notified
• Creator makes the changes
• Approver re-approves and can submit
• Creator would be notified and history updated
Testing
• Security Tested
– SQL Injection Proof
• Testing
– Applied Case Use
– Usability
– Destructive
– Performance
• End to End Transaction Tested
– Application has been tested on a CH Mirror Test
server over a period of 12 months
Support• 1st Line support handled by Support desk of 4
• 2nd line Support, initially by Head of support
and IT Director
• Plan to employ additional staff as and when
required
• Response time immediate
• SQL Database will be installed on the LAN and
the responsibility of the practice
• Developer quick response support team on
hand to resolve any programming issues
Implementation Process
• Installation of Oyez Application on a LAN
• Oyez to be involved in Test Submissions to
Companies House Test Schema
• Oyez to configure for go live use
• User group hand holding and Training
• Gentle roll out to additional users
• User Guide to be in place