A reversal changes the active effect of a recorded event while retaining its history. That distinction matters when you revisit an earlier report.
1. Read the source labels
Read the event and its dependencies before reversing it. Keep the reason and the resulting receipt or status where the workflow supplies one.
2. Keep the review defensible
Refresh related holdings, cash and reports afterward. Do not assume the absence of a row on one screen proves every linked effect was removed.
3. A simple example
An imported event can have a checkpoint history distinct from a manually entered event. Choosing the wrong undo path can leave you confused about what changed.
4. Keep an evidence note
Keep the original source available to the people authorised to review it. A short note should identify the owner, the account scope, the reporting date and any unresolved fields. A blank or missing figure means that evidence is incomplete; it should not silently become zero.
5. How Punjii.com helps
Punjii’s supported manual reversal and import rollback workflows have different scopes. Use the appropriate reviewed action and retain both original and reversal evidence.

6. One practical next step
Before any authorised correction, identify the exact event and the downstream views you will recheck.
For general record-keeping and account-safety guidance, see SEBI’s securities-market do’s and don’ts.
Build a source-backed investment inventory before trying to produce a complete household total.
Explore Punjii and its beta waitlist. Availability and supported workflows may change; check the current product before relying on a feature.
Punjii is an investment tracking app. It does not provide investment advice or product recommendations.