SB Order No. 09/2026: SOP for POSB Accounting & Verification After APT 2.0 Implementation
📌 Order Number: SB Order No. 09/2026
📅 Date of Issue: July 24, 2026
🏢 Issued By: Department of Posts (Financial Services Division), Ministry of Communications, Government of India
🎯 Target Audience: Central Government Employees, Head Post Offices (HOs), Sub Post Offices (SOs), Branch Post Offices (BOs), and SBCO Staff
Introduction to POSB Accounting SOP Under APT 2.0
The Department of Posts (Financial Services Division) has released a comprehensive Standard Operating Procedure (SOP) regarding the accounting and verification of Post Office Savings Bank (POSB) transactions following the rollout of the APT 2.0 module . This operational guideline builds upon the directives established in SB Order No. 12/2025 and SB Order No. 16/2025, ensuring seamless integration between Core Banking Services (CBS) and daily accounting procedures across all post offices .
For Central Government Employees handling postal finance and administration, this updated framework is designed to eliminate accounting discrepancies, streamline daily verification at various operational levels, and guarantee 100% data synchronization between Finacle, the DREAM App, and the APT application through Application Programming Interface (API) integration .
Key Highlights of the Updated SOP
- Same-Day API Accounting: All CBS transactions performed in Finacle and the DREAM App are automatically fetched via API integration before completing the Day-End process in the APT module .
- Strict Cut-off Procedures: No financial transactions are permitted after executing the
CSMDAYmenu in HOs/SOs or marking "Close Account" in the DREAM App at BOs . - Absolute Prohibition of Netting Off: Receipt and payment mismatches must be recorded separately under dedicated account codes . Adjusting or netting off discrepancies against cash-in-hand is strictly prohibited .
- Mandatory Daily Reconciliation: Head Postmasters and SBCO supervisors are held directly accountable for daily account-code-wise verification between Finacle reports and the Cash Book .
- Permanent Audit Records: SBCOs must maintain a permanent "CBS Daily Discrepancy Reconciliation Register," which will be scrutinized by inspecting authorities during regular audits .
Detailed Summary & Operational Guidelines
1. Procedures at Branch Post Offices (BOs)
Branch Postmasters (BPMs) must perform all CBS operations exclusively through the DREAM Application between "Day Begin" and "Close Account" . Before closing accounts for the day, BPMs must check the "Pending Transaction Status" under Core Banking Services . If any transaction is delayed due to network or technical glitches, the BPM must repeatedly click "Update Pending Transactions" until all records synchronize with Finacle .
The BPM is responsible for verifying that all entries in the Daily Transaction Report (DTR) match exactly with the BO Daily Account (BODA) . If a technical mismatch occurs, the amount must be accounted for separately as either CBS Receipt Mismatch or CBS Payment Mismatch . These details must be manually entered into the BODA and communicated to the Account Office .
2. Procedures at Head & Sub Post Offices (Own Office Transactions)
At SOs and HOs, all transactions must strictly occur within the Finacle application between Day Begin and the execution of CSMDAY . Direct manual accounting of POSB transactions in APT is strictly prohibited . Cheque payments require extra diligence to avoid duplicate posting in APT . Postmasters and Sub Postmasters (SPMs) must ensure that CBS accounting data is fetched via API and tallied with the Daily Transaction Report before executing the Day-End process in APT .
3. Accounting of Subordinate Office Transactions
Account Offices must generate previous-day CBS reports in Finacle for all subordinate offices and cross-verify them against the BODA and SODA . Any discrepancy must be reconciled immediately in the Sub Accounts Module .
| Scenario | Action by Account Office (HO/SO) | Action by Subordinate Office (SO/BO) |
|---|---|---|
| Mismatch observed in BODA/SODA | Reconcile with Finacle reports and classify under the correct account code in Sub Accounts . | Provide full details of transactions posted under Mismatch Receipts/Payments . |
| Mismatch NOT in BODA/SODA but appears in Finacle Reports |
1. Raise an Error Book entry calling for explanation . 2. Do NOT make accounting corrections in APT for that day . 3. Report repeated offenses to the Divisional Head . |
Check physical cash/balances and immediately bring the unaccounted transaction into account to close the Error Book entry . |
4. Responsibilities of Savings Bank Control Organization (SBCO)
The SBCO plays a critical supervisory role in validating POSB accounting . The SBCO In-charge must generate the consolidated GL IT 2.0 Report (GL Wise) for the previous day in Finacle using the HO SOL ID . This report must be matched account-code-wise against the HO Cash Book on a daily basis .
Whenever a discrepancy is identified, the SBCO must extract the detailed transaction report using the HO SET ID, trace the error to the specific SO or BO, and immediately report it to the Postmaster . The SBCO is required to maintain a permanent Discrepancy Register (Table 3, Annexure-IV) and submit a jointly signed Monthly Reconciliation Report to the Postal Accounts Office (PAO) by the 4th of every succeeding month .
Important Points at a Glance
- No Netting of Mismatches: If there is a receipt mismatch of ₹5,000 and a payment mismatch of ₹2,000, they must be booked separately under their respective heads . They must never be combined into a net ₹3,000 receipt .
- Daily Tallying: Closing balances of all offices must tally daily . Non-accounting of missing transactions distorts cash balances and is strictly prohibited .
- Error Book Discipline: Sub Account Personal Assistants (PAs) must provide a copy of all error book entries related to CBS discrepancies to the SBCO when handing over vouchers .
- Rectification Timelines: Postmasters must ensure that discrepancies raised by SBCO are settled on the very next working day via Transfer Entries (in HOs) or Miscellaneous Transactions .
- Monthly PAO Reports: The monthly report (Table 1 & 2 of Annexure-IV) must be signed jointly by the Postmaster and SBCO In-charge, endorsed to the Divisional Office, and submitted by the 4th of the following month .
- Data Availability: Monthly SFTP folders containing SOL-wise and account-code-wise Finacle data will be available to SBCOs for a maximum period of three months .
Conclusion
The issuance of SB Order No. 09/2026 marks a significant step toward foolproof financial synchronization across Indian Post Offices following the upgrade to APT 2.0 . Strict adherence to these Standard Operating Procedures is mandatory for all Branch Postmasters, Sub Postmasters, Head Postmasters, and SBCO personnel .
Divisional and Sub-Divisional heads are tasked with closely monitoring compliance, while Inspecting Authorities have been explicitly instructed to review the CBS Daily Discrepancy Reconciliation Register during annual inspections and incorporate their findings into formal inspection reports . All postal officials are advised to download the official order, verify all prior transactions, and maintain absolute accuracy in daily reporting .
.
Educational Purpose Only: The information provided in this article is for general informational and educational purposes only.
Accuracy & Mistakes: While every effort has been made to ensure accuracy, human errors or omissions may occur.
No Liability: Under no circumstances shall the author or this website be held liable for any loss arising from the use of this information.
Are you a Central Government Employee?
Don’t stay in the dark! Vital updates on Service Rules, Pension policies, and your career are happening right now.
Add as Preferred Source on Google
Follow us to ensure our latest exclusive reports appear first in your Google Search and Discover feed.
Comments
Post a Comment