Problems in Implementation of APT 2.0 and suggestions

Federation of National Postal Organisations

Sivaji Vasireddy, Secretary General

T-24, Atul Grove Road, New Delhi – 110001

Mobile: 9959538622, email: sivajivasireddy@gmail.com, Web: fnpo.org

No. IT 2.0/Misc/Solutions

Dated: 25-07-2025

To

The Chairman Postal Services Board,

&The Secretary,

Department of Posts,

Dak Bhavan,

New Delhi - 110001.

Subject: APT 2.0 – Implementation – Reg.

Respected Madam,

My federation appreciates the initiation taken up by the Department for implementation of IT 2.0 software which was prepared by its own employees and it’s really a remarkable record not only in the India Post history and globally also.

Being a responsible stakeholder federation/union, we always welcome such innovative advanced technology and suggested to implement the same in PAN India after making kind of tests in pilot project.

Initially, the project has been started at Mysore Division and in entire Karnataka Circle as pilot project. During that period staff were faced a lot of problems and continuing till now also.

On 22.07.2025, 2nd phase rollout has been done in AP, Telangana, Maharashtra and some other circles. The Departmental and GDS staff are facing much difficulties and forced to stay in the office till 11pm and all the staff are undergoing for mental agony. Hence the following problems and suggestions are brought to the notice of authority for solutions:

1. Wallet balance, cash balance and BO daily account CB are different in BOs and there is no use for BPMs showing balance of wallet and cash balance without statement of cash transaction. After doing transactions more auto fetch to wallet/cash balance keep on failing.
2. In case leave of an official who is working on officiating/substitute arrangement and applies for leave and arrangement made in APT for original post but not in the present working post.
3. Whatever transactions fetching for DTR the same should be brought to wallet directly without adjustment may give solutions for many issues.
4. PLI/RPLI revival premium collection by a separate counter or by the official working in CPC is not at all suggestible and the same work should be entrusted to MPCM/Booking solutions dealing assistant.
5. Though SOP is followed, IPPB figures are not fetched/partially fetched due to which unable to identify the mismatch figures in DTR and TCB. Validation must be provided during day end only as not consumed and day end should be permitted only after consumption of data.
6. In booking solutions yesterday QR receipts today appearing in payments side and the QR payment discrepancy. Yesterday BNPL booking amount today appearing in payments side (Part B).
7. In booking solutions yesterday Ship Rocket figure comes in payment side today so couldn’t submit today.
8. Wallet adjustment done not reflected in two counters till day end and has not performed.
9. SO booking figures are seen as minus figures hence unable to transfer cash and do submit accounts in counter.
10. SB figure wallet adjustment not reflected and hence not possible to submit counter account.
11. Day end not done as the UPI figure of yesterday transaction reflected in submit account payment’s part.
12. If any VPMO delivered and the reflecting in all counters as ‘Pending MO to be booked’ though they are not concerned and unable to do day end.
13. eMO cash not reflecting in wallet.
14. PLI/RPLI collection not showing in the wallet immediately.
15. BO ECB also appearing in the Head Postmaster ID even there is no role.
16. If SPM keeps cash in excess of authorised balance and ECB memo not generated/submits alert should be gone to concerned SDI. Excess cash details should be reflected in the dash board of Division Head on vigilance grounds.
17. Sometimes when UL.app.indiapost entered into any user without asking user ID and password or OTP. It has allowed to continue the work.
18. Validation to receive articles by BPM in IMA app. Many are not receiving articles and just opening bag which is badly affecting delivery. There should be some validation not to allow without receiving a single article.
19. Support desk also to monitor at L1 if already any issues are solved by CEPT may be kept as reference to search. If a problem is raised by end user and if already such case has solution OA DO can search and reply else will just escalate and tickets will be pending.
20. Now while assigning roles there are cards but those cards are having sub cards but when one card is assigned total card is made available if option to select sub cards is given it will be useful.
21. The printers provided in the counters are not compatible and suitable should be provided for all.
22. Pin code search option should be provided by the name of city or pin code. While booking articles against a pin code all the BOs including account office will figure. If a BO is selected, booked article directly fetch to that BO at the office of delivery. But articles have to be delivered by SO and in such cases those articles are not allowed to invoice for Postmen in SO.
23. Cancelled article details should not be fetched for dispatch.
24. All offices should be provided value metric scales.
25. Due to delay in huge consumption of time while booking solutions operation the customers are disappointing and there is a huge chances to lose our valuable customer base if speed of the software not increased.
26. In bag management there is no proper validation and even bag label is also considering as an article and at the end throws an error. Proper validation in respect of SR, RL and Parcel should be there and proper validation only can resolve major despatch problems.
27. In delivery management imposition of redirection charges Rs.6/- is not possible when proper address is not there, when offices are shifted from one place to another place such issues many delivery staff are unaware about this and in such case inquiry later redirection also reflecting such fee.
28. The font size of BO devices and postmen devices is very small. It will have impact stress on eyes and huge delay may took place while performing work. GDS are very happy with the Darpan 2.0.
29. It came to notice that there are huge variations in accounts, the TCB and DTR are not being tallied due to technical issues but not for any human errors. It may be happening due improper fetching. For these there is no solution at SO or HO.
30. There are many issues of day begin and day end in case of BOs as the transactions are not being fetched the BPMs are not able to perform the day end. The transaction may able to fetch even after performing the day end.
31. The Subaccounts module should be reviewed and redefined. The IPPB figures, revenue in respect of booking articles of BOs are not being fetched and the postmasters have no role to change anything in this. HO instructing SO to tally the BO accounts and submit the BO daily accounts as to how no one is there to inform.
32. While closing cash bag the names of the officials working in the cash office but the same is not required for remittance made through cash bag and remitting cash through the official of the same office.
33. In the Payroll management there is no provision for audit recoveries AOR in case of Pensioners and GDS.
34. In case of commuted leave only Half pay leave salary is being drawn in APT 2.0
35. There is no separate for FHR payments.
36. There is no option for verifying head of account wise monthly reports of all offices under HO/division to submit NPC bill and account returns.
37. In case of departmental employees dies-non cases HRA has been deducting twice.
38. In booking solutions card while booking any article “Bill hold” option should be provided like in SAP instead starting the article booking again when ever technical break is there.
39. While bulk booking there should be and dialog provision for RESET button otherwise previous booked data also will disappear.
40. Sender or receiver mobile number should not be mandatory keeping in view of firms/offices etc. For dummy mobile number also some else address has been reflecting in the module even though the same was not saved through OTP.
41. PLI/RPLI premium collected in IT 2.0 for HO/SO is not reflecting in Mcmin day end report but only premium collected in BOs is reflecting. There is no MIS report card for all offices.
42. Premium updation procedure for pay recovery policies in IT2.0 is also not in a clear state.
43. During drawing cheque using misc payment/receipt in treasury module receipt/payment entry can’t be initiated collectively. Due to this claim amount can't processed for the customers in the policies where receipt/recovery exists.
44. Revival amount of lapsed policies unable to collect at counter in IT 2.0 there should be provision for misc collection.
45. In booking solutions particularly quick book service should made easy by reducing some fields also. Conclusion:

It is to submit that the operative staffs in all these years have satisfied all the pressure whenever the new technology has been introduced and it has been made total success also. Now IT 2.0 is rolled out and again the staff are being faced same situation. It is therefore requested the authority for timely action in respect of these persisting issues and directions to allow the staff to leave offices after working hours without any restrictions. It is further request to hold and meeting with stake holders with technology team exclusively for IT 2.0 related issues for getting amicable solutions.

Thanking you Madam,

Yours faithfully,

(SIVAJI VASIREDDY)

Secretary General

Copy to:

1. The Member Technology, Dak Bhavan, New Delhi for information and n/a
2. The GM, CEPT, Bengaluru for information and n/a