AlphaHelion Global LLP — HXR

Product

One system, from the joining form to the statutory return.

Each part below produces what the next one needs. That is the whole design — the alternative is a spreadsheet between every two of them, which is where the month goes.

01

Joining

From a name on a list to somebody who can be paid.

  • A candidate completes their own form from a link, on their own phone — no account to create.
  • Documents upload straight to storage with their checksum pinned, so the file on record is provably the file that was sent.
  • Activation is the moment an employee code is minted and their site, shift and salary structure are bound. Nothing before it can produce a payslip.
  • The lifecycle is a transition table, so “can this person go from bench to approved?” has one answer rather than a dozen call sites.

02

Attendance

Who turned up, where, and whether anybody had to check.

  • Punch in and out on a phone, inside a site geofence, with a photo.
  • A punch outside the fence is captured for review, never discarded — a worker at a gate whose GPS is fifty metres off has done nothing wrong.
  • A punch taken with no signal is held on the handset and delivered later as something a supervisor approves, because a time from a phone is a claim.
  • Leave is applied for, approved and counted as one decision however many days it covers.

03

Payroll

Earned days in, payslips and returns out.

  • Salary structures with formula-driven components, priced against earned attendance.
  • PF, ESI, PT and LWF from versioned per-state rule packs. Tamil Nadu ships first; a new state is data and test cases, never code.
  • Payslips printed as the bilingual statutory form, published when payroll says so and not before.
  • Statutory returns are a projection of the same register the payslips came from.

04

Kit and recovery

What was issued, what came back, what is owed.

  • Uniforms and equipment issued against a stock ledger that reconciles.
  • Recoverable items schedule a deduction the employee can see on their own phone, month by month.
  • Physical counts produce variances somebody approves rather than silently adjusting a balance.

05

Verification

Background checks, tracked rather than remembered.

  • Police, agency and manual verifications recorded per employee with their own status and expiry.
  • Reminders before a verification lapses, so it is renewed rather than discovered missing.

Where the work happens

HR, payroll and site supervisors

Web console

Everything above, plus the queues: attendance exceptions waiting for a decision, leave to approve, verifications about to lapse, and the audit trail behind any of it.

The workforce

Employee app

Punch, their own attendance, leave, payslips and the kit issued to them. English and Tamil. It works at a gate with no signal, which is where it is used.