Reasons at Delivery Office

Published on February 2017 | Categories: Documents | Downloads: 27 | Comments: 0 | Views: 147
of 2
Download PDF   Embed   Report

Comments

Content

Reasons for non transmission of COD Delivered amount
from Delivery Office to the Payment Office
1) BO Verification not done in Postman module: In Postman module,
Supervisor has to perform verification of the amount in r/o all the
COD articles delivered by the Branch Post Offices attached to the
HO/SO. The BO Verification process will cross check as to whether the
amount of all COD articles delivered by each Branch Post Office has
been credited to the Accounts w.r.t. the BO Summary in Sub Accounts
module.
Only such COD aritcle’s amount will be transmitted to
ePayment server.
Solution:
A new report in Postman module is provided in meghdoot
version 7.9.2, which displays all the COD articles pending in that
post office and
the reasons for such pendency.
Please check this
report to know the date for which BO Verification has to be done.
BO Verification can be done at any later date by the Postman
Supervisor, by selecting the concerned Account Date i.e., BO Summary
Date.
2)
BO Names mis-match :
The names of the Branch Post Offices as
appearing in Sub Accounts module and Postman module should be exactly
same.
As the BO Verification happens based on the BO names, the
names in both these modules should exactly match.
If any mismatch
is there in the names of the Branch Post Offices, then the articles
delivered by such B.O.s will not be transmitted to ePayment Server.
Solution:
Please modify such BO names in Sub Accounts module to
exactly match with that available in Postman module.
3) Non-usage of Sub Accounts module for generating BO Summary:
Using
the Sub Accounts module is a must in all the ePayment Sub Post
Offices/Head Post Offices, as the COD amount will be transmitted only
after tallying with the BO Summary figures of each BO (for the
articles delivered through Branch Post Offices)
Solution:
Please ensure that BO transactions for those days are
entered in the Sub Accounts module.
4) Submit Account not done in Postman module: In Postman module, the
Supervisor has to perform Submit Account for each Postman beat. This
process will cross check as to whether the amount of all COD articles
delivered by that beat postman has been credited to the Treasurer or
not. COD delivered data in r/o the beats for which submit account has
been done, will be transmitted to ePayment server for further
transmission to Payment office. It is further to state that Postman

module will not allow to perform day end without completing the Submit
Account of all the beats.
Solution:
The case has to be reported to CEPT for providing suitable
solution.
5) Office became inactive in ePayment:
The delivery office might
have become inactive in ePayment server.
This may be due to the
change of the ePayment communication machine by the Post Office, for
one reason or the other. The ePayment server will take the data being
communicated by the registered communication machine only.
If the
earlier registered ePayment communication machine is changed by the
Post Office, then the COD articles delivered by that Post Offices will
not be taken as authenticated by the ePayment Server.
Solution: The Divisional System Administrator has to re-register the
office in ePayment website using the same machine which has
transmitted the COD data.
Then the ePayment server will re-process
the data earlier received by it again.

6) Last Call status in ePayment:
Many offices are not running the
ePayment Communication application on daily basis, without which the
data will not get transmitted to ePayment server, even though entire
delivery process is completed as per the procedure.
An MIS report
viz.,”Offices Not Called” is available in the ePayment Website which
shows the list of Post Offices which have not run the ePayment
communication since last 24 hours.
The ePayment Communication
application can be either scheduled OR run manually.
Solution: The ePayment Communication application need to be scheduled
atleast twice a day.
The above mentioned MIS report is available
division wise.
7) Non upgradation of ePayment Software:
Some of the offices have
not upgraded their ePayment software to the latest version 7.9.2.
Some other offices have upgraded the ePayment software from the very
old version to Version 7.9.1/7.9.2 instead of upgrading sequentially.
Both the above cases may cause problem(s) in using the options
provided in these latest versions including non transmission/non
payment of COD amounts.
Solution:
All the ePayment offices have to upgrade their ePayment
software to the latest version (7.9.2) which is available in CEPT’s
ftp website ftp://cept.gov.in/Meghdoot7/Updates/.

Sponsor Documents

Or use your account on DocShare.tips

Hide

Forgot your password?

Or register your new account on DocShare.tips

Hide

Lost your password? Please enter your email address. You will receive a link to create a new password.

Back to log-in

Close