Batch Element Entries

 

Secure Connection Failed

     

          An error occurred during a connection to email.gov.in.

 

Peer reports incompatible or unsupported protocol version.

 

(Error code: ssl_error_protocol_version_alert)

 

  The page you are trying to view cannot be shown because the authenticity of the received data could not be verified.

  Please contact the website owners to inform them of this problem. Alternatively, use the command found in the help menu to report this broken site.

 

Cannot open database "WebPayRoll20172018" requested by the login. The login failed. Login failed for user 'payroll'.

 

Click here for ePayslip

 

Error: Stale Data

 

The requested page contains stale data. This error could have been caused through the use of the browser's navigation buttons (the browser Back button, for example).

 

To proceed, please select the Home link at the top of the application page to return to the main menu. Then, access this page again using the application's navigation controls (menu, links, and so on) instead of using the browser's navigation controls like Back and Forward.

 

Batch Element Entries

* Search for a batch by specifying the partial criteria for the batch name and then choose "Go".

* To create a new batch click Create Batch.

* To update a batch, select the batch and click the Update icon.

* Select a batch from the list of batches and choose "Create Lines" to create the batch lines for an element.

* Select a batch from the list of batches and choose "Update Lines" to update the batch lines for an element.

* To create the totals for a batch, select the batch, choose Create Totals, and click Process.

* To update the totals for a batch, select the batch, choose Update Totals, and click Process.

* Select a batch from the batch list, specify the batch process that you wish to perform, and then choose "Process" .

 

Error 404--Not Found

From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:

10.4.5 404 Not Found

The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent.

If the server does not wish to make this information available to the client, the status code 403 (Forbidden) can be used instead. The 410 (Gone) status code SHOULD be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address.