Skip to app details
Back to app library
APPNEURAL APP FAMILYFinance

Payroll

A pay run you can review before it goes out

Run monthly pay for your employees with salary structures, PF, ESI, professional tax and TDS working, and release payslips.

01 / OVERVIEW

See where it fits in your day.

Employees come from People, absences from Leave, hours from Timesheets and approved claims from Expenses through service bindings and a sealed per-domain secret key; without People a small local list is used. Salary structures have components with a balancing component, templates, revisions with arrears, one-time items, loans and declarations. The calculation covers paid days, PF with its wage ceiling, ESI with contribution periods, professional tax by state, TDS under the new or old regime with surcharge and marginal relief, HRA and Chapter VI-A limits, a no-PAN rate and a regime comparison; gratuity, bonus and LWF are off until switched on. Statutory values are shipped as editable data with a source and date, each run stores a snapshot of the values it used, and they are the builder's knowledge to be confirmed with the business's accountant. A pay run goes draft, reviewed, approved, paid and locked, recalculates until approved, and releases payslips. Outputs are the salary register, CTC report, TDS working, PF ECR text, ESI sheet, PT summary, journal CSV, a generic bank CSV and an HDFC-style CSV (layouts not validated against a bank or portal), a printable payslip and an annual statement working that is not Form 16. Employees open My pay for payslips, declarations with proofs in R2 and a both-regime projection; bank accounts are sealed per employee. Optional Claude feature explains a payslip to its owner. API /api/v1/runs (totals only) and a workspace feed (run titles only); webhooks payrun.approved, payrun.paid and payslip.released. Not built: challans, 24Q, overtime, supplementary runs, employer NPS.

A LOOK INSIDEExample layout · sample content
October run
EmployeeGrossNet
AaravpayrollEXAMPLE
MeerasalaryEXAMPLE
RohanpayslipEXAMPLE
02 / CAPABILITIES

Built around the work you do.

What Payroll does for you.

01

Calculation

Salary structures, paid days, PF with its ceiling, ESI, professional tax by state, TDS under the new or old regime, arrears, loans and one-time items; the statutory values are editable data with their source and date.

02

Pay run

Draft, reviewed, approved, paid and locked; people from People, absences from Leave, hours from Timesheets and approved claims from Expenses when connected.

03

Outputs

Printable payslips, an employee page for pay and tax declarations, salary register, TDS working, PF text file, ESI sheet, journal and bank CSV files; the formats are not validated against a bank or portal.

03 / GETTING STARTED

Start small. Build from there.

A suggested path for Payroll. What you can do depends on your access in the app.

01

Set up

Company details, statutory values to confirm with your accountant, and the payroll team in Members.

02

Add salaries

Choose a structure for each employee.

03

Run the month

Review, approve, release and export.

YOUR NEXT MOVE

Make Payroll part of your workflow.

The app opens in a new tab, so your ecosystem stays close.

Open app
05 / CATALOG DETAILS

The registry record.

Live host, inventory, governance, health checks, verification, dependencies and history.

Catalog surfaceDEPLOYEDHEALTHY
InventoryACTIVE1 items
P2VERIFIEDPUBLISHED
Overview

Purpose and boundaries

Employees come from People, absences from Leave, hours from Timesheets and approved claims from Expenses through service bindings and a sealed per-domain secret key; without People a small local list is used. Salary structures have components with a balancing component, templates, revisions with arrears, one-time items, loans and declarations. The calculation covers paid days, PF with its wage ceiling, ESI with contribution periods, professional tax by state, TDS under the new or old regime with surcharge and marginal relief, HRA and Chapter VI-A limits, a no-PAN rate and a regime comparison; gratuity, bonus and LWF are off until switched on. Statutory values are shipped as editable data with a source and date, each run stores a snapshot of the values it used, and they are the builder's knowledge to be confirmed with the business's accountant. A pay run goes draft, reviewed, approved, paid and locked, recalculates until approved, and releases payslips. Outputs are the salary register, CTC report, TDS working, PF ECR text, ESI sheet, PT summary, journal CSV, a generic bank CSV and an HDFC-style CSV (layouts not validated against a bank or portal), a printable payslip and an annual statement working that is not Form 16. Employees open My pay for payslips, declarations with proofs in R2 and a both-regime projection; bank accounts are sealed per employee. Optional Claude feature explains a payslip to its owner. API /api/v1/runs (totals only) and a workspace feed (run titles only); webhooks payrun.approved, payrun.paid and payslip.released. Not built: challans, 24Q, overtime, supplementary runs, employer NPS.

Monthly pay for a connected domain's employees: salary structures, PF, ESI, professional tax and TDS working, loans, reviewed and approved pay runs, payslips with an emailed-code link, bank and statutory working files, with the statutory values kept as editable data to confirm with a chartered accountant.

Employee records belong to People; leave and timesheets stay in Leave and Timesheets; accounting entries stay outside.

Priority
P2
Portfolio
Finance
Capability
Finance
Technical owner
Not configured
Runtime
Cloudflare Workers / OpenNext
Last verified
2026-11-18 14:03:15
Semantic inventory

Every number says what it counts

1Catalog itemstrackedEntityCount · catalog-api:live
Production-ready gate

Governance evidence required

5 of 18 required controls are configured. Catalog deployment and inventory maturity remain independent until every required control is present.

MissingBusiness owner
MissingProduct owner
MissingTechnical owner
MissingMaintaining team
MissingGitHub repository
ConfiguredProduction URL
ConfiguredHealth endpoint
MissingDocumentation
MissingArchitecture document
MissingCurrent security review
ConfiguredData classification
MissingDependencies
MissingConsumers
MissingSLA / SLO
MissingOn-call
MissingLast release
ConfiguredLast verification
ConfiguredDeprecation status
Catalog details

payroll schema v1

Catalog-specific metadata is not configured.
Live host

Where it runs

payroll.appneurox.com DEPLOYED

payroll.appneurox.com

Worker
payroll-catalog
Health
HEALTHY
Last deployment
2026-11-18 14:03:15
DNS & routing

Confirmed infrastructure only

Provider inspection appears after Cloudflare credentials are configured. Mutations require dry run, idempotency and explicit confirmation.
Repository & architecture

Technical context

APPNEURAL-Catalogs/payroll-catalogLOCAL · NOT CONFIGURED

Documentation

Documentation and architecture evidence are not configured.
Dependencies

Registered relationships

No dependency edges are registered. Nothing has been inferred.
Operations

Checks and verification

No health checks have been recorded.
Security

Review posture

Security review not configured. This does not mean the catalog is secure or insecure.
Automatic reconciliation

GitHub · Cloudflare · DNS · catalog APIs

No synchronization run has completed yet. The scheduled Worker records missing credentials as Not configured, never as success.

Drift findings

No drift has been recorded.
Evidence & history

Trust record

Verification is verified. Run verification to store check-level evidence, confidence, expiry and remediation.

AI workspace

Human-reviewed drafts

AI outputs are saved as drafts with evidence references. They never replace verified catalog fields automatically.

App libraryOpen app