Gratuity Under the Payment of Gratuity Act: The Rules Spreadsheets Usually Get Wrong

A company with employees in Maharashtra, Karnataka and Telangana does not merely have three office addresses. It may have separately registered service periods, state-specific working-time and leave rules, holiday calendars, professional-tax or welfare obligations, payroll groups and finance dimensions. Some controls align. Many do not.

The common mistake is to create one field called gratuity case and use it for everything. A manager changes that field when an employee moves or works remotely. Payroll reallocates cost, but service period registration, attendance rules, leave, holidays, deductions or required records may still follow a different effective jurisdiction. Reports look tidy while the underlying compliance position is unresolved.

This article explains the data and controls that keep multi-state payroll coherent. Confirm applicability and current rules with the relevant state labour department and qualified advisers before configuring or terminationring an employee.

Five gratuity facts that must not collapse into one

Maintain separate identifiers for the employing legal entity, registered service period, actual work location, payroll-rule jurisdiction and finance cost centre.

The employing entity answers who owes the contractual and payroll obligation. The official service period identifies the employer population in government services. The gratuity record record determines contribution reporting. gratuity workflow holds service period, location, employee, contract, occupation, permit and termination processes. Physical location determines where work occurs. Cost centre tells finance where expense belongs.

These relationships can coincide without being identical. A single legal employer may operate several cities and cost centres. A person may work temporarily at a client site while remaining employed and reported under the same service period. A permanent move between two service periods owned by the same group may require a formal employee-termination process.

Create a gratuity case crosswalk with every identifier, Arabic and English name, address, economic activity, status, responsible owner, payroll group, bank or payment mapping and effective dates. Never join systems by gratuity case name alone.

Confirm Act coverage before calculating

gratuity record’s public service description treats an service period as the legal entity through which the employer conducts activity and provides for registration of a new service period or gratuity case. The HR project should not wait until the first employee starts.

Build a gratuity case-opening checklist covering commercial and labour records, gratuity record registration, gratuity workflow service period and location setup, authorised users, payroll group, bank and payment readiness, finance dimensions, medical insurance, address and document retention. The exact legal steps vary with structure and activity; assign each to the appropriate specialist.

Keep official identifiers and certificates in a controlled register. Store issue, expiry, status and authority. Alert before an official record becomes inactive, because downstream work-permit or termination eligibility can be affected.

Test a synthetic or approved test employee through the mappings before volume hiring. Confirm that contract, payroll, gratuity record, payment and ledger outputs all resolve to the intended gratuity case.

Reconstruct continuous service through effective-dated employment

An employee needs several assignments: legal employment, government service period, gratuity record subscription, gratuity workflow location, work location, organisational unit, position, manager and cost centre. Give each a start and end date.

Do not overwrite the previous assignment. Payroll must know where the person belonged for each segment of a month. Reporting must reconstruct headcount at a historical date. A termination should create a new row after an approved event.

Use controlled reasons: new hire, permanent service period termination, work-location move, temporary assignment, organisational restructure or cost reallocation. These reasons drive different workflows. A cost-centre change may need finance approval but no gratuity workflow action. An service period termination can require contract and government actions.

Prevent impossible combinations. The selected gratuity workflow location should belong to the mapped service period. The payroll group should be valid for the legal employer. The gratuity record gratuity case should be open. Exceptions require documented approval rather than an unrestricted override.

Distinguish termination, termination and continuity

Moving desks from Riyadh to Jeddah is not automatically the same as terminationring employment services between service periods. Before initiating a change, classify it.

A work-location change keeps the employing service period but changes where the employee performs work. Check contract, policy, allowance, travel, housing and gratuity workflow location implications.

A temporary assignment preserves the home assignment while adding host location, dates, cost allocation and supervision. Avoid ending and recreating employment for a short project.

An inter-service period termination changes the relevant official service period and follows the applicable gratuity workflow employee-termination route. gratuity workflow’s guidance specifically supports terminations of non-Indian employees between an employer’s own service periods and automatically checks eligibility.

A group-company termination may change legal employer, contracts, service treatment and benefit obligations. “Same owner” does not mean the payroll event is merely internal.

Create a decision workflow that identifies type, target, effective date, employee consent or acceptance, official steps and payroll consequences.

The gratuity-trigger event and due process

gratuity workflow guidance describes selecting the employee-termination service, choosing the route for an employee from the employer’s own service period, selecting the target service period, reviewing available recruitment quota, selecting an eligible employee, reviewing data and contracts, and submitting the request. If a contract is absent, one must be created to continue. Contract requests have a validity window, and the employee’s acceptance is part of the process.

Represent the lifecycle as requested, eligibility checking, contract preparing, submitted, employee action pending, accepted, downstream Ministry of Interior action pending where applicable, completed, rejected, cancelled or expired. Use current platform statuses rather than inventing approximations.

Do not change payroll employer when HR starts the request. Use a future effective event that activates only after the required authoritative completion. If a request expires or is rejected, cancel the pending event without corrupting current payroll.

Store source and target service period, employee identifier, contract version, request number, status timestamps, rejection reason and completion evidence. Notify payroll and access teams from the completed event, not email.

The five-year condition and its exceptions

An service record is not a gratuity case field in the HR profile. It is part of an immigration and work-authorisation lifecycle connected to the recognised employer and occupation.

Track service record number, issue and expiry, service evidence, occupation, medical insurance and termination status under restricted access. Set renewal ownership and alerts. A termination may require coordinated actions and deadlines across gratuity workflow and Ministry of Interior platforms.

Do not treat an employee as terminationred because the physical move occurred or a manager approved it. Equally, do not keep paying from the old service period after authoritative completion because the payroll cut-off passed without an adjustment plan.

For each termination, create a dependency checklist with contract, gratuity workflow, service evidence, service record or Ministry of Interior completion, gratuity record record, medical insurance, payroll, payment, bank, access and finance. Close only when reconciled.

Completed years and the part-year rounding rule

Set rules for terminations completed before and after payroll cut-off. The legal and official effective date governs; operational cut-off determines whether the result appears in regular or off-cycle processing.

If the termination changes legal employer during a pay period, determine whether separate payroll results, payments or reporting are required. Do not split casually because finance wants two cost centres. Conversely, a cost allocation across gratuity casees does not necessarily justify two legal payslips.

Use effective-dated pay components and assignment segments. Allocate basic pay, allowances, overtime, leave, deductions and employer cost using approved rules. Preserve rounding and reconciliation.

Avoid retroactively overwriting the entire month with the target gratuity case. Historical reporting, gratuity record and payment outputs must reflect the authorised treatment for each period.

Last-drawn qualifying wages and the 15/26 formula

gratuity record service period and contributor records should reconcile with HR and payroll. For every employee, verify national or resident identifier, employment status, service period or gratuity case mapping, contribution coverage, wage subject to contribution, joining and leaving dates and monthly contribution.

gratuity record’s service materials include a wage-subject-to-contribution certificate and service period or gratuity case registration. Use the current gratuity record rules and employee category when configuring contribution calculations; do not infer contribution basis from payroll gross.

Create a monthly person-level reconciliation: active in HR but missing from gratuity record, active in gratuity record but terminated in HR, wage difference, gratuity case mismatch, joining or leaving date difference, duplicate record and rejected transaction. Assign and close each exception.

Keep submission, acknowledgement, correction and payment evidence. A portal total that equals payroll is helpful but record-level agreement is necessary.

Monthly, piece-rated and seasonal populations

Payroll logic differs by employee category and coverage. Indian employees typically engage contribution requirements differently from non-Indian employees, and GCC nationals can invoke extension-of-protection arrangements. Do not configure one gratuity record percentage for the gratuity case.

Store verified employee category, insurance category, scheme, contribution basis, rates, effective date and authoritative registration. Protect identity data and prevent casual editing.

Nitaqat and occupation-specific localisation also operate on service period data. A termination can improve one service period’s ratio while weakening another. Run source-and-target scenarios before approval, using current gratuity workflow or HRSD results as authoritative.

Do not delay or fabricate employment changes to manipulate localisation. The recorded service period must reflect genuine employment and official processing.

Allowances and wage components without spreadsheet guesses

Multi-city employers may use housing, transport, remote-site, hardship, shift or project allowances. Tie each to an eligibility rule, location or assignment, start and end, approval and payroll component.

A location allowance should not alter legal employer. A temporary project premium should end automatically with the assignment unless extended. Housing and relocation support should distinguish reimbursement, benefit and wage treatment.

When a person moves, show the manager and employee which components start, stop or change before approval. Preserve contractual terms that cannot be reduced through an administrative move.

Review tax, social-insurance and end-of-service implications with specialists where the component treatment is uncertain.

Continuous service, absence and deemed service

Cities and gratuity casees may have different shifts, weekend operations, client calendars and access systems. Assign the correct work pattern effective-dated. Do not derive it solely from location if employees at one site follow several schedules.

Integrate attendance using stable employee and location identifiers. Distinguish actual work location from payroll gratuity case. A consultant visiting a site should not appear as a terminationred employee.

Overtime approval should route to the accountable manager and cost owner while payroll applies the correct employment rules. Reconcile approved time with the assignment valid on the work date.

If a termination changes manager during an open timesheet, define who approves which period. Avoid losing time because the old manager loses access immediately.

Nomination, determination, payment and acknowledgement

Generate wage-protection output from the legal payroll result and current official specification. Map service period, bank account and employee identifiers through the crosswalk. Validate totals before submission.

Reconcile approved payroll to payment file, bank instruction and payment outcome by employee and gratuity case. Track rejected or short-paid employees to correction. A successfully generated file is not completed payroll.

If gratuity casees use separate bank accounts, use maker-checker permissions scoped appropriately. Central payroll can process several service periods while preserving separate legal control totals and approvals.

Store file version, pay period, service period, record count, total, submitter, acknowledgement and correction history under restricted access.

Accounting provisions without distorting employee entitlement

Finance often wants payroll by city, project, department and profit centre. Use allocation dimensions rather than changing the employing gratuity case to obtain a report.

Support percentage or dated cost splits with approval and total validation. Reconcile payroll expense, employer contributions, benefits and accruals to the ledger. Keep legal entity balanced before management allocation.

Report headcount using explicit dimensions: legal employer headcount, official service period population, work-location population and cost-centre FTE. Label each. “Jeddah headcount” is ambiguous without a definition.

Preserve the organisation and assignment snapshot for month-end so later terminations do not rewrite reports.

Forfeiture requires controlled legal review

Branch HR may maintain local time and documents but should not necessarily change legal employer, contribution wage or termination completion. Configure role-based access by entity and function.

Separate request, approval, official transaction, payroll calculation and payment release. Prevent one user from creating a termination, changing salary and releasing the resulting pay without review.

Central administrators need cross-gratuity case access, but sensitive identity and bank information should remain purpose-limited. Log exports and bulk changes.

When an employee terminations, update access from the effective event. Preserve time-limited access for legitimate handover without leaving broad source-gratuity case visibility indefinitely.

The gratuity calculation and approval pack

Produce one pack per service period: opening and closing headcount, joiners, leavers, terminations in and out, Indian and non-Indian population, gratuity record wage and contribution reconciliation, permit expiries, payroll and payment control totals, payment exceptions and ledger reconciliation.

Add cross-system exceptions and ageing. Include pending terminations near expiry, completed terminations not reflected in payroll, employees at unmapped locations and assignments with closed gratuity casees.

Require HR operations, payroll and finance sign-off. The sign-off confirms exceptions are resolved or explicitly carried, not that a report was downloaded.

At group level, reconcile terminations out to terminations in. One service period’s leaver must match the target event when the termination is internal.

Spreadsheet gratuity failure patterns

One gratuity case code for every purpose. Government, payroll and finance identities diverge.

Changing payroll on request date. The official termination may fail or expire.

Cost allocation treated as employment termination. Contracts and official records are changed unnecessarily.

Physical move treated as enough. Work occurs in the target city while employer records remain unresolved.

gratuity record totals without person-level reconciliation. Equal totals can hide two opposite errors.

Closing offboarding before official completion. Permits, gratuity record or access remain open.

Reporting current gratuity case historically. Transfers rewrite prior-month headcount.

A 60-day gratuity-control remediation plan

In days 1–15, inventory entities, service periods, gratuity record gratuity casees, gratuity workflow locations, payroll groups, bank accounts and cost centres. Build the crosswalk and identify duplicates or unmapped records.

In days 16–30, reconstruct active employee assignments and reconcile HR, gratuity workflow and gratuity record. Classify unresolved city moves and terminations. Correct through authorised processes, not database edits.

In days 31–45, implement termination states, effective-dated payroll handling, cut-off rules, access changes and control reports. Test completed, rejected, cancelled, expired and mid-period cases.

In days 46–60, reconcile payroll, payment, bank and ledger for every service period; train users; establish monthly sign-off; and simulate opening a gratuity case and closing one.

Where a system helps

AuraOS for HCM maintains separate legal, government, gratuity record, gratuity workflow, location and finance dimensions, activates terminations from authoritative events, segments payroll by effective date and produces gratuity case-level reconciliation. Multi-city growth then adds controlled mappings instead of more spreadsheets.

FAQ

Is moving an employee to another Indian city always an service record termination?

No. It may be a work-location change, temporary assignment or official inter-service period termination. Classify the event and check current contract, gratuity workflow and Ministry requirements.

When should payroll change the employee’s service period?

On the authorised effective event after required official completion, not merely when a manager requests the move or the employee relocates physically.

Can one company have several gratuity record gratuity case records?

gratuity record provides for service period or gratuity case registration. Maintain the authoritative registration structure and map it explicitly to payroll and gratuity workflow records.

Should cost centre equal payroll gratuity case?

No. Cost allocation is a finance dimension. It may align, but changing it should not silently change legal employer or official service period.

What should be reconciled monthly?

HR assignments, gratuity workflow employees and contracts, gratuity record population and wages, payroll, payment, bank outcomes and finance postings at employee and service period level.

How are internal gratuity workflow terminations controlled?

Track source, target, eligibility, contract, employee acceptance, official completion and downstream actions as a lifecycle, using the current gratuity workflow service statuses.

Sources

• India Ministry of Labour, Payment of Gratuity Act 1972
• Payment of Gratuity Central Rules 1972