Shift Roster Management for Nepal Payroll: BS Calendar, Weekend Shading, and Allowance Sync

Roster tools designed for Western markets work fine until you put them in front of a Nepali HR team. The first thing that breaks is the calendar — most rostering products only show Gregorian dates, while Nepali public holidays, fiscal periods, and many internal communications run on Bikram Sambat (BS). The second thing that breaks is the allowance integration — Nepali shift work generates festival allowances, public-holiday work compensation, and shift differentials that have to flow into payroll.

PayrollApp’s shift roster handles both. This is a practical guide to how it works and what it gives back to HR.

What “BS calendar support” actually means

Surface-level BS support — showing the BS date next to the Gregorian date — is the easy part. Most calendars can do that with a date converter.

Real BS support means:

• The roster grid shows BS dates as the primary axis, with Gregorian secondary
• Nepali week starts on Sunday (not Monday)
• Saturday is the default weekend, not Sunday
• Public holidays auto-populate from the BS calendar
• Festivals (Dashain, Tihar, Holi, Eid, etc.) are recognised as multi-day events
• Fiscal-year boundaries align to mid-Shrawan (mid-July), not 1 January
• Date inputs accept BS or AD format and convert silently

PayrollApp’s roster does all of this. The roster is BS-native — Gregorian is shown as a hint, not the primary axis.

Weekend shading and the current-time indicator

Two small UI affordances that matter more than they sound:

Weekend shading

Saturdays render with a subtle background colour so managers can see weekend cover at a glance. Shifts scheduled on Saturdays trigger the weekend-allowance flag automatically (where the company’s policy includes one). Friday is normal in most organisations; Saturday-only weekend is the standard, but PayrollApp respects whatever you configure as your weekend.

Current-time indicator

A vertical line on the calendar grid shows the current BS date and time. Staff filtering, shift assignment, and “who’s on now” queries all anchor against this line, which makes shift-start and shift-end management intuitive.

These are the kinds of details that don’t show up in a feature list but make daily operation either pleasant or maddening. We borrowed both from how Google Calendar’s week view works, then adapted for BS rendering and Saturday weekends.

Shift allowances flow to payroll automatically

Shift work in Nepal commonly generates four kinds of allowance:

1. Shift differential

For employees on rotating or non-standard shifts (night shift, evening shift), a differential is added per shift worked. Configure the rate per shift type; PayrollApp tags each completed shift with the corresponding allowance.

2. Public holiday compensation

Under the Labour Act, employees who work on a gazetted public holiday are entitled to either compensatory time off (a “comp leave” credited automatically) or compensatory pay. PayrollApp’s roster recognises public holidays from the BS calendar and tags shifts on those days with the comp-leave credit or comp-pay flag based on policy.

3. Overtime

Hours worked beyond the standard daily/weekly limits trigger overtime pay at the statutory rate. The roster captures planned hours; the time-clock or attendance integration captures actual hours; the difference flows to payroll as OT.

4. Festival allowance pro-rating

Festival allowance (typically Dashain bonus) is pro-rated based on service and attendance. The roster contributes the attendance side — days worked, days absent, days on approved leave — to the calculation.

All four flow to PayrollApp as part of the monthly payroll run. No double entry, no end-of-month allowance reconciliation.

Where this fits vs dedicated rostering tools

We’re not trying to replace Deputy or Connecteam for companies whose primary product is workforce scheduling. Those tools have more sophisticated forecasting, demand prediction, and compliance for high-volume shift work.

PayrollApp’s shift module is designed for Nepali SMBs where:

• Shift scheduling is part of operations, but not the entire business
• Roster sizes are 20–500 employees per location
• The most important thing is payroll integration — the allowances flow correctly to the payslip
• BS calendar support is non-negotiable
• Companies want one tool for HR + leave + payroll + roster, not four

If those describe your team, this is a fit. If you’re running a 1,000-person hospitality chain with fifteen locations and demand forecasting needs, layer Deputy on top and we’ll integrate.

A typical roster workflow

Roster planning (weekly or bi-weekly)

1. Open the Shift Roster in PayrollApp.
2. View the BS calendar grid with current employee assignments.
3. Drag employees onto shift slots, or use bulk assignment for repeating patterns.
4. Confirm public holiday cover (the calendar flags upcoming public holidays).
5. Publish the roster — employees see their shifts in LeaveBalanceApp under “My Shift.”

Mid-week adjustments

• Last-minute swap requests come in via LeaveBalanceApp.
• Manager approves; the roster updates in PayrollApp.
• Allowance flags update accordingly.

Payroll run

• Allowances tagged during the period flow into the monthly payroll.
• Public-holiday work generates either comp leave (credited to LeaveBalanceApp) or comp pay (added to payslip).
• Overtime captured against planned shifts.
• Final payslip reflects the full allowance picture.

Audit

• Every roster change is logged with timestamp and actor.
• Employees can see their attended-vs-scheduled history in their own profile.
• HR can pull a per-employee allowance report for any period.

How the LeaveBalanceApp integration works

The split between admin and employee UX:

• Admin shift management lives in PayrollApp — the manager creates the roster, assigns shifts, and approves changes.
• Employee shift self-service lives in LeaveBalanceApp — each employee sees their upcoming shifts in “My Shift,” requests swaps, and triggers absence flows.

The two stay in sync via the same webhook fabric that ties leave and payroll. The employee never opens PayrollApp; the admin never has to switch contexts to see leave conflicts on a planned shift.

What’s coming

The first release covers admin rostering, BS calendar, public holiday awareness, and allowance flow. Roadmap items in the next quarter:

• Self-service shift swaps with peer approval
• Open-shift bidding for last-minute coverage
• Mobile push notifications for roster changes
• Time clock integration with biometric devices (we already have a ZKTeco sync; rostering integration is the next step)

The bigger point

Roster tools that don’t speak BS, don’t know Nepali public holidays, and don’t flow allowances into payroll are tools that create extra work for the team using them. The right tool for a Nepali SMB roster is one that handles all three out of the box — and ideally one that lives next to leave and payroll so the integrations don’t break.

PayrollApp’s shift roster is built for that exact case. If you’re running rosters today on a spreadsheet and reconciling allowances by hand at month-end, the migration is one configuration session.