Employee Self-Service & Leave Portal

In most NetSuite accounts, HR runs on an inbox. Leave requests arrive by chat and email, balances live in a spreadsheet that only one person maintains, payslips are emailed out one PDF at a time, and every employee who wants to know their remaining entitlement calls HR to ask. Managers approve in a message thread, so there is no record of who approved what and when. At month end someone chases timesheets, retypes hours, and reconciles the leave taken against the accrual sheet by hand.

The frustrating part is that the data already exists in NetSuite. The Employee record holds subsidiary, department, class, location, supervisor, hire date and job title. What is missing is a place a non-finance employee can safely go. Giving two hundred field and factory staff access to the standard NetSuite interface is neither affordable nor safe, and the standard Employee Center is generic: it does not know your probation rules, your carry-forward cap, your encashment policy, or that one subsidiary observes a different holiday calendar than another.

ECOSIRE builds a self-service portal inside your own NetSuite account so employees transact against real NetSuite records, and HR stops being a message router.

The portal itself

The front end is a responsive interface served by Suitelets, built to work on a phone browser without an app install and without a separate hosting stack. It authenticates through NetSuite, so there is no shadow user database and no separate password to reset. Data operations run through RESTlets and server-side SuiteScript 2.1, so the browser never talks to a NetSuite record directly and every write is validated on the server.

Employees see a single home screen: leave balance by type, pending requests, upcoming approved leave, latest payslip, open timesheets, and any action waiting on them. Managers see the same plus an approvals queue. The layout, terminology and language are set to your organisation during the build rather than imposed.

Leave policy, accruals and balances

Leave is modelled in custom records rather than free text. A leave type record defines the entitlement basis (annual grant, monthly accrual, service-band driven), whether it is paid or unpaid, whether it requires documentary evidence, the notice period, the maximum consecutive days, the carry-forward cap and expiry, and whether the balance may be encashed on exit. A policy record binds leave types to an employee population by subsidiary, department, class, location or employee class, so a factory population and a head-office population can run different rules in the same account.

Accruals are calculated by a scheduled Map/Reduce script that writes ledger entries to a balance-transaction custom record rather than overwriting a running number. That matters: when an employee disputes their balance, HR can show every grant, accrual, deduction, carry-forward and expiry line that produced it, with dates. Pro-rata handling for joiners, leavers, probation periods and unpaid leave is configured to your rules during the build.

Holiday calendars are custom records assigned per subsidiary or location, so a request spanning a public holiday or a non-working weekend deducts only the days your policy counts.

Requests and approvals

A leave request is a custom record. On submission, server-side validation checks the balance, notice period, overlapping requests, blackout windows and any team-coverage rule you define, and rejects with a specific reason rather than a generic error. Approval routing is driven by SuiteFlow using the supervisor field on the Employee record, with configurable escalation, delegation while an approver is themselves away, and multi-level routing for longer absences.

Every state change is logged with actor and timestamp, and notifications go out through the N/email module with links straight back into the portal. Approved leave writes to the calendar view and to the balance ledger in a single server-side transaction, so an approval can never half-apply.

Timesheets

Employees enter hours in the portal against your existing structure and the entries are created as native NetSuite Time Entry records, so project costing, billing and any reporting you already run continue to work unchanged. Entry is constrained by the same server-side rules you already use: allowed customers, projects, tasks and service items for that employee, daily and weekly hour limits, and a lock after the period closes. Submission routes through the same approval framework as leave, and rejected timesheets return to the employee with the approver's comment attached.

Payslip and document access

Payslip PDFs are stored in restricted File Cabinet folders that employees cannot browse. Access is mediated by a Suitelet that resolves the requesting employee from the session, checks the file belongs to them, and streams it, so a URL cannot be guessed or shared to reach someone else's document. The same mechanism serves employment letters, contracts and policy documents, with a per-document acknowledgement record when you need proof that a policy was read.

If payslips are produced outside NetSuite, we build a bulk import that files each PDF against the right employee and period on upload.

Profile changes

Employees do not edit the Employee record directly. A change request custom record captures the proposed update to address, phone, emergency contact, bank details or dependants, routes it to HR through SuiteFlow, and applies the change to the Employee record via a server-side script only after approval, keeping a before-and-after audit entry. Bank detail changes can be given a stricter route with a second approver, because that is the field fraud targets.

Who it is for

This is for organisations already running NetSuite as their system of record who have HR headcount spent on administration rather than people, for groups whose leave policy varies by subsidiary or worker population in ways a generic tool will not model, and for finance teams who want employee hours landing on native Time Entry records instead of arriving as a spreadsheet.

If you already license NetSuite SuitePeople and its standard leave handling fits your policy, use it. This build is for accounts that do not have it, or where the local policy, approval routing or document access requirements go beyond what the standard configuration covers.

How delivery works

There is no download and nothing is pre-built. We start with a scoping call covering your leave types, accrual rules, holiday calendars, approval hierarchy, payslip source and the exact populations that differ. You receive a fixed quote and a written scope listing every record, script, screen and report to be delivered, and what is explicitly out of scope.

The build is developed as an SDF project against your sandbox account. We install there first, load a representative sample of your employees, and let HR run a full cycle — request, approve, accrue, close a period, publish payslips — against real data. Once you sign off, we install into production, migrate opening leave balances from your existing spreadsheet with a reconciliation report, and run training for employees, managers and administrators. A defect-fix support window follows go-live.

Typical lead time from signed quote to sandbox installation is two to four weeks depending on how many distinct leave policies are in scope.

What you own

The SDF project and full SuiteScript source are yours. The bundle is unmanaged and installed in your account, with no runtime licence check and no per-employee subscription for the code. Policy changes are configuration, not development. Code changes are yours to make or to commission.