PAYE68001 - employment maintenance: movements browser: introduction

The Movements Browser has been developed to enable blind data capture of forms P45(1), P45(3) and P46. It is possible for the forms to be captured at any location as the browser is not dependent on COP. It is a web based product and the home page can be accessed through the Intranet page (by keying in the URL).

The home page displays icons of the forms that can be processed by the browser together with two Work List icons.

The three user roles that can be allocated to operators on this system are

• Mvts Data Capture
• Mvts Worklist Operator
• Mvts Worklist Manager

It is possible for one operator to have more than one user role. When you access the browser home page a check is made of your pay identity number and the user role(s) that have been allocated to you. The icons will only be available for the user roles allocated to you.

The Organisation Unit (OU) field will default to your home OU but where you process work for a number of OUs these will be set as secondary OUs. You must

• Select the appropriate OU before you start to capture any forms or deal with Work List items

Once the information is entered onto the browser pre- processing checks are done on the NINO / temporary reference number to ensure that the details entered are in a format that can be passed through the EDI automatic processes.

Once the information is accepted by EDI, automatic processes will either

• Update an existing COP taxpayer record

Or

• Create a new record

Where automatic updating cannot take place a Work List item is created on the browser.

Where a record has been updated successfully there may be follow up action to take such as a review of the tax code. Work List items will be created where further action is due and the record has been moved within a COP region. Early Morning Output (EMO) will continue to be produced where the record has been moved across regions.

Not all forms will be suitable for capture by the browser and these should be identified by a check of the forms before data capture commences. Forms identified as not being suitable should be processed using the existing Functions MA, ML and MS.