Skip to content
Zenocta Solutions

Mobile App Development18 Jun 2026 · 8 min read

How We Built Payslip Maker: Template-Driven Payroll for SMEs

A behind-the-build look at Payslip Maker: why manual payslips break, how a template-driven engine and role-based access work, and what we would advise anyone building payroll software.

ZEBy , Editorial Team

Payslip Maker, the payroll and salary slip app from Zenocta, shown on its social card

Every month, someone in a small company opens a spreadsheet, copies last month's figures and tries to turn them into payslips that look professional and add up correctly. We built Payslip Maker to take that job out of the spreadsheet. This is the story of how the payslip maker app was shaped: the problem, the design decisions, how the features connect, and the advice we would give to anyone building payroll software for small and medium companies.

What problem did Payslip Maker set out to solve?

The case study describes it directly. Small and medium companies without dedicated payroll software were generating payslips manually, a slow, error-prone process that made it hard to keep salary structures, employee records and payroll history consistent and organised.

That sentence contains three separate problems. The first is speed: a team that produces payslips by hand loses hours every month. The second is accuracy: a formula copied one row too far, or a figure typed with a misplaced decimal, ends up in someone's payslip. The third is memory: when an employee asks for last year's slip, finding it means searching old folders. A good solution has to tackle all three, not just the first.

For a wider look at the process from the employer's side, our earlier guide on how to create payslips for employees walks through the monthly routine. This article takes the other angle: why the app is built the way it is.

3roles named: Admin, HR and Accountant
9numbered feature areas on the Play listing
3future-scope ideas in the case study

Who is the app for?

The Play listing says Payslip Maker is built for small and medium-sized companies, HR teams and administrators who want a streamlined, secure way to manage employees and produce accurate payslips in minutes. The case study's tagline says the same: fast, secure payslip generation for small and medium companies.

It is worth noticing who is not named. This is not aimed at an enterprise with a payroll department and a dedicated payroll system. The business challenge in the case study is about giving small and medium companies professional, accurate payroll documents without the cost of enterprise payroll software. An audience like that points to a product that has to be useful quickly, with very little setup.

How did we approach the design?

According to the case study, a central admin dashboard manages employees and flexible salary structures, payslips are generated in minutes from customisable templates, and role-based access lets HR and accountant users work within defined permissions, backed by clear analytics.

The technology stack listed in the case study is Flutter with light and dark UI support, Firebase for authentication, Firestore and Cloud Storage, a template-driven document generation engine, and role-based admin access for HR, Accountant and Admin. If you are deciding between frameworks for a business app, our comparison of Flutter and native app development covers the trade-offs.

The central bet: templates, not custom code

The technical challenge the case study names is the most interesting one: building a flexible, template-driven payslip generation engine that adapts to different salary structures without custom coding per company. Think about what that means. Two companies can both pay a basic salary, but one adds house rent allowance and a travel allowance, while another has a performance component and a different set of deductions. If every difference needed a developer, the product could never serve small companies at a small price.

So the structure is data, not code. A salary structure is a list of components that can be switched on or off per employee, and a template decides how those components appear on the page. Change the data and the template, and the payslip changes with them.

How do the features fit together?

The Play listing describes nine feature areas. Read in order, they follow the path a payslip takes from setup to archive.

Dashboard and quick actions

The dashboard gives admins quick access to the most important controls: create a payslip, add an employee, bulk import where enabled, and preview templates. It also offers at-a-glance alerts for pending payslips, missing bank details and employees needing updates. The case study names the user experience goal as surfacing quick actions so admins can complete common tasks with minimal steps. The point is that the most common jobs should sit on the first screen.

Roles and permissions

Admin users can manage everything. HR users are responsible for employee data and payslip creation. Accountant users can view analytics and download payslips but may be restricted from some admin-level changes. The interface adapts, so each person sees the features that match their duties. This is a tidy way to separate the person who changes data from the person who only needs to read it.

Employee records and salary structure

Employee management covers name, employee ID, department, email, bank details, PAN, UAN, join date and status, with edit and archive options. The salary structure page lets you define a structure per employee, with Basic, HRA, allowances, PF, income tax and custom components, switch components on or off, and auto-calculate gross and net pay from the breakdown. Common structures can be saved as templates and applied across departments.

Generating and customising payslips

HR and Admin can generate payslips for a single employee or selected groups, review a final preview before download or email, add notes for record-keeping, and download a PDF or email it directly. Templates can be customised by adding or removing fields, changing the header and footer and adjusting the layout, and a history of template changes is kept.

Analytics, history and support

The analytics dashboard shows monthly cost, a department-wise cost breakdown, exportable summaries and filters by date range and department. Payslip history stores every generated slip in one place, searchable by employee, month or department, with options to download or re-send, which gives an auditable trail for employee requests. An About and Support page covers version, legal notes and contact details.

StageWhat the app providesWhy it matters
SetupEmployee records, salary structures, templatesData is entered once and reused every month
GenerateSingle or group payslips, preview, notesA check before anything is sent
DeliverPDF download and emailEmployees receive a clean document
ReviewAnalytics by month and departmentPayroll cost becomes visible
ArchiveSearchable payslip historyOld requests are answered in seconds

What would we tell someone building something similar?

The following is advice that follows from the decisions above. It is not a report of results.

Advice

Decide early what is configurable and what is fixed. In a payroll product, salary components and document layout should be configuration, while the calculation path and the audit trail should stay fixed and predictable.

  1. List the components your users actually have. Write down the earnings and deductions of three real companies before you design a salary structure.
  2. Treat the template as a product feature. Companies care about how a payslip looks and which fields appear. Let them change it without a developer.
  3. Separate who can change data from who can read it. Admin, HR and Accountant roles make this explicit and reduce accidental edits.
  4. Show a preview before sending. A final preview, and a place for notes, catches mistakes while they are still cheap to fix.
  5. Keep a history. A searchable archive makes employee requests easy and supports record keeping.
  6. Flag missing data on the first screen. A missing bank detail found before payroll day is a small job. Found on payroll day, it is a delay.
  • Which salary components does your company use, and do they differ by department?
  • Who may create, edit and only view payslips?
  • What must appear on the payslip, and in what layout?
  • How will you deliver payslips: download, email or both?
  • Do you need records by employee, month and department?
  • Have you checked the current statutory rules with a professional?

What about statutory calculations?

The case study lists automated statutory compliance calculations, such as tax and PF, as a future-scope idea, alongside direct bank transfer integration for salary disbursement and an employee self-service portal for downloading payslips. The current Play listing for version 3.1.0 describes payslip templates for more countries, payroll tools including PF, ESI, TDS, HRA and gratuity calculators, and a Compliance Center for statutory files and salary certificates.

Our advice here is cautious. Payroll rules change, differ by country and depend on each employee's situation. A payroll app can prepare figures and documents, but you should check the current rules with a qualified professional before relying on any number. A product that is honest about this earns more trust than one that implies it replaces professional advice.

What is live today?

Payslip Maker is live on Android and the web. The Play listing says you can add a company logo, earnings, deductions and PF or ESI figures, export a PDF or share on WhatsApp, work offline, save employee templates and generate payslips for the whole team each month. Read the Payslip Maker app page for the current details, and the listing remains the authority on what each release contains.

How do you get a similar product built?

If you want payroll, HR documents or another template-driven document app shaped around your own business, begin with the components and the roles, as above. Our guide to attendance management software for small business teams is a helpful companion if payroll depends on attendance data, and our post on building an MVP without wasting your budget will help you decide what belongs in a first version.

You can read the full Payslip Maker case study, browse our other apps, or tell us about your own project. We return a scoped, fixed-price proposal, so you know the scope before work begins.

Try it live

Open the real thing: demos run in a new tab with sample data, apps link to their own page.

Frequently asked questions

  • 01Can a payslip app handle different salary structures?

    Yes. The Payslip Maker case study says salary structures and payslip templates are fully editable per organisation, and its engine is built to adapt to different structures without custom coding per company. Components can be switched on or off per employee.

  • 02Which technologies were used to build Payslip Maker?

    The case study lists Flutter with light and dark UI support, Firebase for authentication, Firestore and Cloud Storage, a template-driven document generation engine, and role-based access for Admin, HR and Accountant users.

  • 03How should a payroll app control who can change data?

    Use roles. In Payslip Maker, admins manage everything, HR users handle employee data and payslip creation, and accountants can view analytics and download payslips but may be restricted from some admin-level changes.

  • 04Does a payroll app replace professional tax advice?

    No. A payroll app prepares figures and documents, but statutory rules change and differ by country. Check the current rules with a qualified professional before relying on any calculation, and treat the app as a helper, not an adviser.

  • 05Can Zenocta build a custom payroll or HR app for us?

    Yes. Zenocta builds custom payroll and HR management apps. Tell us how your company pays staff and which documents you need, and we will return a scoped, fixed-price proposal. Payslip Maker is live on Android and the web.

0% read ·

Get new guides in your inbox

Practical notes on billing, payroll, apps and AI for growing businesses, written from what we build. No spam.

We email occasional guides. Unsubscribe any time: reply to any email or write to contact@zenocta.com.

Ready to build something real?

Website and app development from ₹8,888. Book a free consultation and get a scoped, fixed-price proposal within 24 hours.