SOP — Data correction

Purpose: correct verified errors while preserving history and accountability.

Field	Standard
Trigger	Verified incorrect or incomplete operational data.
Responsible role	Record owner; Admin/Super Admin for sensitive corrections.
Required information	Record ID, source of truth, correction reason, downstream impact.
Steps in platform	Verify original record and links; correct through authorized workflow; add reason/note where supported; recheck reports/balances/statuses.
Expected status changes	Only the necessary record status changes; use void/cancel/archive for history-preserving changes.
Required documents	Evidence supporting the correction, if required by policy.
Financial checks	Reconcile related payment/request/contract values before and after correction.
Follow-up deadline	Immediately for material financial/lot/customer errors.
Escalation conditions	Financial history, signed contract, lot conflict, unknown cause, destructive action.
Completion criteria	Correct authoritative data and explanation; effects verified.
Audit/accountability evidence	Audit Trail, notes, reason fields, supporting records.
Common mistakes	Purging real history; correcting only a report symptom; editing without reason.

Media: Decision diagram, checklist, fictional scenario.