Payroll input validation & export review
Workflow concept · fictional records · no live connections
Check the files moving between attendance, payroll and accounting before an approved export is produced.
For payroll/hr consultancies and accounting delivery teams.
A useful first scope
One customer, one input/export format and an agreed validation dataset, with payroll/accounting rules owned by the partner.
What goes in
- A fictional employee master, attendance input and externally calculated payroll export.
- Explicit validation rules and approved field mappings.
- A reviewer who owns payroll policy and the final output.
What comes out
- A queue of duplicate IDs, missing employees, invalid attendance and total mismatches.
- A source-to-approved-output reconciliation.
- A reviewable export enabled only after blocking errors are resolved.
How a reviewer would use it
- Input overview: list the three sample sources, row counts and validation state.
- Validation queue: show rule, employee/source IDs, evidence, severity and proposed correction.
- Review: inspect the fictional reference correction; require explicit approval before applying it in the sample.
- Export preview: show an approved accounting-summary CSV and its totals; no payroll disbursement or bank action.
Inspect the fictional records and expected results
This is a design brief for a fuller demonstration, not an upload form or a working third-party connector.
master.csv employee_id,name E001,Asha Sample E002,Dev Sample E003,Mira Sample E004,Neel Sample attendance.csv row_id,employee_id,paid_days A001,E001,30 A002,E002,31 A003,E003,30 A004,E004,30 A005,E999,30 payroll.csv row_id,employee_id,gross,deductions,net P001,E001,30000,2000,28000 P002,E002,40000,3000,37000 P003,E002,40000,3000,37000 P004,E003,35000,2500,33000 P005,E004,25000,1000,24000
Rules and assumptions
- This is a fixed fictional 30-day period. Validate paid_days from 0 to 30. Do not use this as a real payroll calendar or pay calculation rule.
- E999 is absent from the master. P003 is an explicit duplicate candidate; removal from approved output requires a reviewer decision and preserves the original row.
- P004 fails gross − deductions = net: corrected arithmetic net is ₹32,500, subject to reviewer confirmation.
- The underlying gross/deductions are supplied inputs, not calculated tax/PF/ESI outcomes. Do not compute statutory deductions.
- Block final approved export until duplicate, unknown ID, invalid attendance and arithmetic mismatch are explicitly resolved.
What should be checkable
- Four seeded issue types are visible: E002 attendance 31 days, E999 unknown employee, duplicate E002 payroll row, E003 net mismatch.
- Raw payroll totals: gross ₹170,000, deductions ₹11,500, stated net ₹159,000. Arithmetic expected raw net is ₹158,500; the ₹500 gap is visible.
- After explicit reviewer-approved duplicate exclusion and E003 arithmetic correction: 4 payroll employees; gross ₹130,000, deductions ₹8,500, net ₹121,500.
- An approved export is blocked until attendance and unknown-employee issues also have explicit sample resolutions.
- No account is credited, no payroll is filed and no real employee data is used.
Agree the boundary
Do not build a statutory payroll calculator, payment system or compliance filing engine. Preserve review and unresolved-source evidence.
The professional reviewer owns accounting treatment and business rules. DataHarmoni scopes the technical preparation, validation and output with your team.
Discuss a similar workflowA short anonymized description is enough to start.