Skip to main content
GullySystem
Legal and accounting · Software for payroll service providers

Build one payroll workflow for many clients, with one import, one approval trail and statutory files prepared.

Payroll service providers run salaries for many clients from attendance in a dozen formats, Excel salary templates and the government payroll and social-security portals. A multi-client payroll workflow is built around your own process. It would give one import per client, one approval trail, and statutory files in each portal’s layout.

At a glance

Your clients are small factories, shops, clinics and offices that would rather not deal with pension, insurance, local payroll levies and withholding themselves, so they pay you to carry that worry.

Each has its own salary structure, attendance machine and habit about approvals, and all of them want salaries paid on the first. Month end is crowded.

How the work runs today

At month end, attendance, leave and overtime arrive as an Excel file, a biometric export or a photograph of a muster roll. Your team cleans it, adds joiners, removes exits, marks loss of pay, and runs the salary sheet.

The client approves the sheet, usually after three changes on WhatsApp. Then come bank transfer files, payslips, pension and insurance contribution returns, withholding and local levy filings, each with its own portal and due date.

Across the year there are quarterly withholding returns, tax declaration proofs near the year end, annual tax certificates and the inspection where a client needs registers by tomorrow. A settlement for someone who left on the 3rd must carry the leave balance, the notice period and the last pension contribution, and it is always wanted the same week.

Where it breaks

What goes wrong for payroll service providers without a proper system.

Attendance arrives in every format

One client sends a biometric file and another a photo of a muster roll, and cleaning the data takes longer than running the payroll. That is unpaid effort.

Approvals drag to the due date

The client approves on the 12th, and the pension contribution payment is still due on the 15th. Nobody waits for you.

Structures differ by client

Every client has its own allowances and deductions in separate Excel templates that break when somebody copies a row.

Proofs land in the last week

Investment proofs arrive in the final days of January, and the February deduction has to be reworked for a few hundred people at once.

Employees call for payslips

A worker wants a payslip for a loan application, asks the client, and the client asks you. It joins forty other requests.

What the software does

What we would build for payroll service providers.

Named the way your team already talks about the work. We start with whichever part the audit shows is costing you most.

Client-wise salary structures

Built to hold allowances, deductions and statutory settings per client for reuse every month. Nothing then depends on last month’s file being copied correctly.

Attendance import

A template would be set up for each client’s format. Days present, overtime and loss of pay carry across, and errors are listed before payroll runs.

Approval workflow

Salary sheets would go to the client from the system. Every change the client asks for, and the hour they approve, is recorded against that month’s run.

Statutory files

The build prepares pension, insurance, withholding, local levy and bank transfer files in the layout each portal requires, so nobody fixes columns at midnight.

Arrears, off-cycle runs and settlements

Built to handle a revision paid in arrears, a mid-month payout and a leaver’s full and final settlement with the leave balance and notice period on it.

Employee self-service

A worker login would put payslips, employee ID and tax certificate on their own phone. They fetch them without calling anyone.

Compliance calendar

A calendar would show due dates by client and filing, with the status of each one beside it.

Before you talk to a supplier

A requirements checklist for payroll service providers.

What to cover, which reports to ask for and what to put to every vendor, ready to print or save as a PDF.

Open the checklist
Ready product

A product already built for payroll service providers.

It is adapted to how your business works before it goes live, and anything your trade needs that it lacks is added then.

Payroll Service Provider Management Software

Client salary structures, attendance imports, payroll runs, client sign-off, bank and contribution files, payslips and bureau fee invoices for payroll service providers.

See the product
How it works

How the work runs from Bengaluru for your city.

  1. 1

    The audit, by call

    A screen-share and a look at the sheets, accounting reports and WhatsApp groups your team uses. No travel needed.

  2. 2

    A written proposal

    Scope, what we build first and the cost, agreed in writing before anything starts.

  3. 3

    Build in short rounds

    Working screens shared every few weeks. Your team tests them from your own office.

  4. 4

    Go-live, in person when it helps

    For data migration and training we can come to your city. Travel is agreed in advance.

  5. 5

    Support online

    Fixes, changes and hosting handled remotely by the same team that built it.

Common questions

Questions payroll service providers ask before they call.

Can salary entries post to our clients’ accounting software?

Not built in. A per-client salary journal file for the accounting package can be added, and it carries a separate price.

Why not use ready payroll software?

A bureau serving only a few employers can run well on an off-the-shelf multi-company package. Custom work suits providers carrying many clients, odd structures, or a portal with their own name on it.

Is statutory compliance automatic?

No. What is built calculates and prepares files from the rules you configure, and your team reviews and files them. Which rules apply to a client is a matter for that client’s accountant or adviser.

How is employee data protected?

Access would be set by client. Bank details, national ID and salary figures open only for staff assigned to that client, and every export is logged.

Which factors move the quotation for a payroll bureau?

Client count, employee volume and the formats attendance arrives in matter most. Each statutory portal file and a self-service view are separate modules. A single client’s month is rehearsed on screen. Costs then follow module by module.

What should the bureau have ready?

One client’s salary structure, an attendance file in its usual mess, last month’s approved sheet, the statutory return layouts you use and a settlement example. A payroll lead and a compliance person should join reviews. Keep it brief.

Who owns client payroll data if we leave?

The bureau does, and the programme with it. Salary structures, runs and filings leave in standard formats when requested. Its developers carry on supporting it. Employee data sits on servers you can name.

What happens after I share my requirements?

An engineer reads what you send and replies within one business day. We then look at the software, spreadsheets and WhatsApp groups your business runs on today and write down what works, what slows your team down and what is missing. A demo login, a screen-share or a few screenshots are enough. You get a short written summary ordered by priority, with no obligation to hire us afterwards.

How much will the software cost?

We don’t publish a price, because it depends on what the system has to do. That first review settles the scope, and the cost goes into a written proposal before any work starts.

Category

Part of a wider group.

Talk to us

Tell us how your business runs today.

A few lines on your spreadsheets, software and WhatsApp groups is enough. We reply the same working day.

What happens after you share your requirements

  1. A senior engineer reads your answers. Nobody phones first.
  2. Within one business day you get a written note: what we understood, what we would start with, and the questions we still have.
  3. If it fits, a proposal follows with the order of work, what we need from you and what you receive at each step.
  4. No call is booked and nothing is paid until you have read the note. Your details stay with us.

Start with your requirements

Seven short steps that tell us what you need. A senior engineer reads them before anyone gets in touch.

Share your requirements