The Spark Behind Nucleus Payroll
Payroll is one of those things that has to be right - every single time. But as our teams grew, payroll started taking more time and more re-checking than it should. We were doing the core work in Excel, then cross-checking with attendance records, leave sheets, overtime, holiday calendars, and salary structures - again and again.
It wasn’t that Excel was “bad.” It just wasn’t built for a growing shared service team with real-life payroll complexity. So, we built Nucleus Payroll, linked with Nucleus - our core HR and project management application, so payroll could run on approved data, not on last-minute patchwork.
The Challenge: Where Payroll Used to Get Risky
Before the app, payroll processing involved a long list of manual steps:
The toughest part was always payroll tax. Nepal’s tax rules are detailed, slab-based, and tied to annual estimates - so each month required careful projection, tracking tax deducted so far, and adjusting for items like festival allowance and changing income. Doing this cleanly in Excel required constant recalculation and cross-checking.
Termination calculations added another layer: leave encashment, festival allowance accruals, final settlement, and different tax treatment- usually under time pressure.
Even the outputs were manual:
It took time, and it demanded full attention.
The Solution: Meet Nucleus Payroll
Nucleus Payroll pulls approved hours/days from Nucleus and calculates payroll in one connected flow.
What It does:
It’s built to be easy to run - but also easy to review.
How We Built It
This was built from real payroll cycles - by the same people who run them. HR and Finance mapped the real checks that matter, team leads shared where approvals and exceptions usually slow things down, and IT built the flow around Nucleus, so everything stayed connected. We tested it using our own tricky cases (increments, partial months, overtime, terminations) until it handled them cleanly.
The goal was simple: fewer manual steps, clearer checks, and a process people can trust.
The Impact: Payroll That’s Easier to Run (and Easier to Review)
The biggest change wasn’t just fewer checks - it was time. Earlier, payroll processing and salary crediting typically took 7 days into the next month. With Nucleus Payroll, we’ve had cycles where payroll was processed and salaries were credited on Day 1 (the 1st of the next month).
| Function | Before | After |
| Payroll processing + salary crediting | Credited on Day 1 in some cycles | 7 days into the next month |
| Attendance/Leave adjustments | Manual re-checking | Auto adjusted from approved data |
| Joiners/Leavers | Spreadsheet pro-rating | Proportional salary in-app |
| Increments & salary changes | Manual updates | Reflected via salary setup |
| Tax calculation | Monthly recalculation effort | Automated with full visibility |
| Payslips | Mail merge risk | Generated + sent from system |
| Bank letter & net pay list | Prepared separately | Auto-generated templates |
What improved in practice:
And most importantly: payroll became something the team could run with confidence, not anxiety.
Closing Statement
Payroll will always be sensitive - and it should be. People rely on it. Nucleus Payroll didn’t change that responsibility - it removed the unnecessary manual work around it. It just made the process simpler, cleaner, and easier to manage.
Like our other tools, it wasn’t built to impress. It was built to work - built for how we work, built to run every month.
Feel free to reach out if you want to collaborate with us info@foursymmetrons.com or simply have a chat.