Introduction of trans_date for Transfer Entries (TEs) by PAOs

A new field trans_date has been introduced for TEs created by PAOs. This ensures that:

• Budget validation is performed based on the financial year derived from trans_date, instead of the earlier created_date.
• PFMS posting will also be aligned with the financial year of the trans_date.

Example:

• For 01.04.2026 – 31.03.2027 → Financial Year considered: 2026
• For 01.04.2027 – 31.03.2028 → Financial Year considered: 2027

2. Extension of trans_date mechanism to DDO TEs

The same trans_date logic has now been implemented for Transfer Entries created by DDOs for budget check and push to PFMS.

• This ensures consistency across the system.
• All reports will now reflect data based on trans_date.

3. Cashbook visibility enhancement for PAOs

• On the Verify Cashbook page, the cashbook generation date is now displayed, enabling better review and traceability of cashbook submission by DDOs.

4. Cash Account Reversion enabled for PAF Wing

The Cash Account Reversion functionality is now available to the PAF wing with the following validations:

• Only the latest cashaccount can be reverted. Subsequent reversions allowed in the descending order.
• Reversion is allowed only if the PAOs data is not submitted to PRAO

5. Improved TE verification workflow for DDO entries

• For DDO-generated TEs requiring budget validation, a workflow status will now be maintained.
• In case of budget failure:
• A clear error message with reason will be provided
• PAOs can take appropriate action (e.g., rejection)

6. PFMS Reversal handling for reverted cashbooks

• When a cashbook submitted to PFMS is reverted, the system now supports posting reversal entries in PFMS.
• A Reversal Unique ID will be generated.
• In the Cashbook Reversion Records Report, an Update button is provided to generate the corresponding Reversal TE Number.

7. Automatic TE number generation via PFMS integration

• PFMS Unique IDs are now automatically pushed to PFMS for TE number generation in the background.
• Since this is handled at multiple stages across the module on opening of tabs, the need for manual intervention via the Update button would be minimal.