Correction updates existing member data on an active policy via Excel upload (files.action = correction). The final step creates pending correction endorsements on the employees table — data is not updated until those endorsements are applied downstream.

Processing is in EmployeeServiceController::employeesCorrectionProcess, queued after the same format and data validation steps used for inception and deletion.

Overview

flowchart LR A["Upload Excel action correction"] --> B["excelFileFormatValidation"] B --> C["excelFileDataValidation"] C --> D["employeesCorrectionProcess job"] D --> E["emp_endorsement pending on employees"] B -->|errors| F["files.status failed"] C -->|errors| F D -->|loop done| G["files.status success"]

In short:

Step 1 — Format: 8 columns (A–H); field must be one of four allowed names; dates d-M-Y.
Step 2 — Data: Member must exist (emp code + name + active policy); code 10 if not found.
Step 3 — Correction: One pending endorsement per row per field (skips duplicate pending corrections).
Each Excel row = one field change for one member (not a full-family operation).

Key files and routes

Area	Location
UI	`app/Views/employee_upload.php` — action Correction
Upload	`EmployeeController::employeesUplodWithEvents`
Validation	`excelFileFormatValidation`, `excelFileDataValidation`
Correction process	`EmployeeServiceController::employeesCorrectionProcess`
Column config API	`getCorrectionExcelColumns()` — used when building correction Excel programmatically
Job	`employeesCorrectionProcess` in `JobWorker.php`
Endorsements	`EmpEndorsementModel` — `actions = c`, `table_name = employees`, `status = pending`

Routes (group /employee, authMVC):

GET /employee/upload — upload screen
POST /employee/upload — upload-action-type=correction
GET /employee/excel_error/{file_id} — validation errors

files.policy_id is the client policy id. Lookup requires active employees + employee_polices on that policy and branch.

Sync vs background jobs

Step	< 1 MB	≥ 1 MB
Format validation	Inline on upload	Job `excelFileFormatValidation`
Data validation	Job `excelFileDataValidation`	Same
Correction process	Job `employeesCorrectionProcess`	Same

Step 1: excelFileFormatValidation

Uses $correction_excel_columns — 8 columns (A–H).
Action code C for mandatory rules on correction-specific columns.
Field (column D): only name, dob, relationship, email_corporate.
Date of Correction (F): d-M-Y.
Change event (G) and Value (E) are mandatory.

Format error codes

Code	Meaning
1	Mandatory missing
2	Wrong format
3	Not in allowed list (e.g. invalid Field value)
4	Custom validation failed
5	File / policy problem
6	Column headers wrong

Step 2: excelFileDataValidation

Rows grouped by EMP ID; for correction the critical check is name_and_empid_check_in_db:

Each row must match an active employee on the uploaded policy (emp code + name).
Not found → error code 10 (“Record Not found”).

On success → queues employeesCorrectionProcess (with optional batch_file_id for TPA multi-file flows).

Step 3: employeesCorrectionProcess

flowchart TD A["Read each Excel row"] --> B["Match emp_code plus name on active policy"] B --> C{"Pending correction for same field?"} C -->|Yes| D["Skip row"] C -->|No| E["Insert emp_endorsement actions c"] E --> F["old_value from DB new_value from Excel"]

Per row:

field_name ← column D (name, dob, relationship, email_corporate)
new_value ← column E; if field is dob, converted from d-M-Y to Y-m-d
date_of_correction ← column F (converted to Y-m-d)
remarks ← column H (optional)
old_value ← current value from employees.{field_name}

Skips insert when a pending correction endorsement already exists for the same emp_code, name, and field_name (actions = c, endorsement_id IS NULL, status != truncated).

Sets files.status = success when the loop completes and sends a success pull notification. Rows with no DB match are not endorsed (no row-level failure on the file record).

TPA batch: If batch_file_id is set, also queues updateEmployeeDataFromTpa, reconTpaApiDataWithEmployeepolicies, and initializeDeletionProcessForTpaApiData.

Correction Excel columns

Col	Header	Required	Notes
A	S.No	Yes
B	EMP ID	Yes
C	NAME OF EMP/DEP	Yes	Must match DB before correction
D	Field	Yes	`name`, `dob`, `relationship`, `email_corporate`
E	Value	Yes	New value; DOB as `d-M-Y`
F	Date of Correction	Yes	`d-M-Y`
G	Change event	Yes	e.g. `correction`
H	Remarks	No	Stored on endorsement

Row layout examples

Fix DOB — one row, one field:

EMP ID	NAME	Field	Value	Date of Correction	Change event	Remarks
EMP001	Raj Kumar	dob	15-Jan-1985	19-May-2026	correction	Typo in upload

Multiple fixes — use separate rows (same or different members):

EMP ID	NAME	Field	Value
EMP001	Raj Kumar	email_corporate	raj.kumar@company.com
EMP001	Priya Kumar	relationship	Spouse

Developer steps

Upload with upload-action-type=correction; note file_id.
On validation failure, check /employee/excel_error/{file_id} for code 10.
After success, query emp_endorsement where file_id = upload id, actions = 'c', status = 'pending'.
Compare field_name, old_value, new_value per row to the Excel.
To generate correction Excel in code, use getCorrectionExcelColumns() for header layout.

Common pitfalls

Name must match DB — correction identifies the member by current emp_code + name; rename via a name field row uses the old name in column C.
Only four fields — mobile, SI, band, etc. are not supported in this upload path.
Duplicate pending correction — second upload for the same field is skipped until the first endorsement is processed or truncated.
File success vs rows — files.status = success does not mean every row created an endorsement.
Not live update — employees columns change only after endorsement approval/application.

Related: Inception, Deletion.