Appearance
Payroll Runs
Application address: /payroll/runs · Product baseline: 0.4.0
Reference status
Screen inventory extracted from the implementation. Labels and explicitly declared input constraints are recorded below. This is not a claim that every control, calculation, or business workflow has been verified in a running system.
Open this screen
Use OSERP navigation to find Payroll Runs, or open /payroll/runs on your OSERP application after signing in. Confirm the active company before reading or changing records.
Menu access: payroll:read
Menu access only determines whether the screen is offered. Saving, posting, deleting, exporting, and approving can require additional server permissions.
Fields and input controls
Limits in this section are interface declarations. A missing maximum is not a promise of unlimited storage. Read how field limits work. Labels may differ with language and configuration.
Type
| Property | Reference |
|---|---|
| Reference key | runType |
| Location | Screen / contextual panel |
| Input control | select |
| Required in interface | not declared on control |
| Maximum characters | Not explicitly declared on this control |
| Editing | No disabled/read-only condition declared directly on this control. |
Period from
| Property | Reference |
|---|---|
| Reference key | periodStart |
| Location | Screen / contextual panel |
| Input control | date |
| Required in interface | not declared on control |
| Maximum characters | Not explicitly declared on this control |
| Editing | No disabled/read-only condition declared directly on this control. |
Period to
| Property | Reference |
|---|---|
| Reference key | periodEnd |
| Location | Screen / contextual panel |
| Input control | date |
| Required in interface | not declared on control |
| Maximum characters | Not explicitly declared on this control |
| Editing | No disabled/read-only condition declared directly on this control. |
Payment date
| Property | Reference |
|---|---|
| Reference key | paymentDate |
| Location | Screen / contextual panel |
| Input control | date |
| Required in interface | not declared on control |
| Maximum characters | Not explicitly declared on this control |
| Editing | No disabled/read-only condition declared directly on this control. |
Find by name or code
| Property | Reference |
|---|---|
| Reference key | find-by-name-or-code |
| Location | Screen / contextual panel |
| Input control | input |
| Required in interface | not declared on control |
| Maximum characters | Not explicitly declared on this control |
| Placeholder | Find by name or code |
| Editing | No disabled/read-only condition declared directly on this control. |
Named actions
These are labels found in screen components; availability and consequences depend on record state. Confirm the operation before executing it.
- Approve
- Payslips
- Journal
- Set up India statutory rules
- Close
- Open
- ⓘ
- ·
Help text and messages
The following wording is embedded in this screen. It describes interface guidance, rather than independently verified system guarantees.
- When the money is paid. Some statutory rules follow this date rather than the period.
- No payroll runs yet — create the first one above.
- A deduction missing from a payslip with no explanation is indistinguishable from a bug — so each one says why.
- The rest of the run completed. Correct these and calculate again — one unusable record does not hold up everybody else.
- This is not a month’s pay. It settles the difference between what this period has already paid and what it should have paid — only the figures that moved are listed.
- Contributed by the employer in addition to the pay above. Not deducted from you and not part of net pay.
- The figure contributions are computed on, which is not always the basic salary.
- Deductions exceeded earnings, so this remains recoverable.
- A deduction missing from a payslip with no explanation is indistinguishable from a mistake, so each one says why it was not taken.
- The named totals every rule reads. Nothing reads a pay component directly, so these are what the statutory calculations actually saw.
Verification still required
Business purpose for each control, dynamically generated fields, backend limits, saved defaults, permission combinations, audit effects, and complete workflow outcomes require manual review against the published application.
See the operating manual, coverage register, and troubleshooting guide.