CEPT Provides Clarification regarding COD Artciles

step1:.Please login to https://services.ptcmysore.gov.in/ParcelNet/  Go to COD Reports -> COD Article Details Enter the COD article number and click on the search button.  Please see report regarding COD Article Delivery and ePaymentDetails .

step2:. If the article is disposed properly, the in the status column of the COD ePayment Data report , the article should be shown as delivered. If the article is not shown as delivered in the COD ePayment Data report , there is some issue at the delivery office.    Please go though the  document available for download  and rectify the issues at ur end.

step3: If the article is  shown as delivered in the COD ePayment Data report and still there is compliant regarding non payment of COD amount to the biller , please ask the payment office to go though the document available at link "Download" on the page  and rectify the issues at their  end.

step4: If the issue is not resolved after following the procedure advised in the attached document referred to at (1) below, please forward a backup of the eCounter and Postman db along with  copy of the RNet communication folder and  article details.

 Reasons for non-transmission of COD Delivery amount  from Delivery Post Office to ePayment Server 

 1) 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. 

2) 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.   This  is  similar  to  the Submit Account for the local delivered articles.   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 SO Summary in Sub Accounts module.  COD delivered data in r/o the Branch Post offices for which verification 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, if BO Verification is pending against any particular Branch Post Office. Solution:  BO Verification can be done at any later date also by the Postman Supervisor, by selecting the concerned Account Date i.e., BO Summary Date.

 3) 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. 

Download:https://drive.google.com/file/d/0B5ceVEjyB3diX0pFbHV1SlVwSFE/view