Procedure for Offices Unable to Perform Previous Day’s Day End in APT 2.0

In APT 2.0, sometimes a Post Office may be unable to complete the
Day End for the previous working day due to technical,
connectivity or operational issues. In such cases, the pending Day End
must be properly completed before normal operations for the current day
are started.

Procedure for Offices Unable to Perform Previous Day’s Day End

1. Day Begin with Pending Day End

When the previous day’s Day End has not been completed, follow these steps:

1. Login to the APT Portal.
2. Open the Treasury Module.
3. The system will prompt for:
   • Day Begin for the current day.
   • Day End for the previous day.
4. Initiate Day Begin. The pending Day End for the previous day will be completed through the system process.

2. Check Previous Day Counter Status

After completing the above process, check whether any counter user has pending activities.

1. Go to Booking Solutions → Counter Operations → View Counter Status.
2. Set From Date as the previous day.
3. Set To Date as the current day.
4. Fetch the details.
5. Identify users having pending Submit Account or Shift End.

Actions Based on Counter Status

Case 1: Submit Account Difference is Zero but Account is Not Completed

Step 1 – Submit Account

1. Click the Submit and Verify option against the concerned user.
2. In the Verify Accounts window, select Generate Account.
3. Confirm the generation process.
4. Wait until the status changes from Running to Complete. Refresh the screen if required.
5. Select Fetch Account.
6. Verify the generated account.
7. The status should subsequently change to Done.

Step 2 – Forcible Shift End

If the Shift End is still pending after Submit Account completion:

1. Select Forcible Shift End.
2. Enter appropriate remarks.
3. Submit the request.
4. Confirm that the Shift End has been completed successfully.

Case 2: Submit Account is Not Tallying and Difference Amount Exists

If a difference amount is appearing in Submit Account, first complete the
normal account generation and verification process.

1. Generate the account.
2. Wait for the account generation to complete.
3. Fetch and verify the account.

If the Verify option is not active, check whether the
required cash transfer to the Treasurer has been completed and acknowledged.

• Ensure the cash transfer has been made.
• Check whether the Treasury has acknowledged the transfer.
• If already transferred, verify the acknowledgement.
• Regenerate and verify the account after acknowledgement is reflected.

Wallet / Submit Account Mismatch

In certain cases, Wallet or Submit Account may remain untallied because
of a pending cash transfer or acknowledgement issue.

Scenario 1: Counter to Treasury Cash Transfer Pending

1. Check whether the cash transfer from Counter to Treasury has been completed.
2. If the transfer is completed but acknowledgement is not reflected in Treasury, use the appropriate Wallet Adjustment Payment option in Booking Solution.
3. This may result in a corresponding difference in the Treasury Cash Book.
4. Once the actual acknowledgement is received, make the required wallet adjustment receipt entry.
5. Verify the current-day Submit Account.

Scenario 2: Treasury to Counter Cash Transfer Pending

Follow the prescribed wallet adjustment process and ensure that the cash
transfer is properly acknowledged by the concerned module.

Treasury Module – Final Verification

Before starting current-day counter operations, verify the previous day’s Treasury records.

1. Generate the Treasury Cash Book (TCB) for the previous day.
2. Generate the Daily Transaction Report (DTR).
3. Check the closing balance.
4. Match the system balance with the physical cash available.
5. Confirm that all necessary entries and adjustments have been properly recorded.

Only after completing these checks should counters be allocated
for the current day.

Delivery Module – Pending Previous Day Activities

Offices should also check the Delivery Module when the previous day’s
activities are pending.

1. Process Shift Begin for the current date.
2. The system may prompt for Force Shift End.
3. Complete the Force Shift End process.
4. Again process Shift Begin for the current date.

Pending Articles / EMOs

• Process the required returns for pending previous-day articles/EMOs first.
• Do not submit the previous day’s beat account where the system does not provide a revoke option.
• Invoice articles/EMOs for the current date as required.
• Take returns as applicable.
• The subsequent Day End Submit Account for beats may include transactions relating to both days.

Branch Office (BO) Actions

Branch Offices may also have pending activities when the previous day’s
process was not completed. The following checks are important:

• Force Shift End can be completed on the following day.
• Transactions should reflect correctly in Wallet and subsequently in BODA.
• BODA and CBR mismatches can be corrected through the prescribed mismatch entry.
• Wallet or physical cash differences can be adjusted through the appropriate Wallet Adjustment option in Miscellaneous Entry.
• Unprocessed articles can be invoiced on the next day using To be Invoiced.
• For already invoiced articles, check acknowledgement status before processing delivery.

Quick Checklist for Post Office Staff

Important Points to Remember

Conclusion

Failure to complete the previous day’s Day End in APT 2.0 should not be
treated as a routine issue. The pending counter, treasury and delivery
activities need to be checked systematically before normal operations are
continued.

By following the above procedure, Post Office staff can identify pending
accounts, resolve cash-transfer or wallet mismatches, complete required
Shift End activities and ensure that Treasury records are properly
reconciled.