Payroll is about people.
The process should be, too.

The work before payday

Payday looks simple from the outside: calculate a salary and pay it. Inside a small business, that number is the end of a much longer chain. Someone has to collect attendance, check leave, confirm changes to compensation, reconcile deductions, and make sure the employee record is up to date. The final transfer is only one part of the job.

When that chain lives across spreadsheets, chat messages, and separate files, the owner or administrator becomes the connection between them. A change in one place has to be remembered somewhere else. A corrected attendance record can mean reopening a calculation that was already checked. The business may have all the information it needs and still struggle to arrive at an answer it trusts.

This is the problem we built Gokira to address. We want Indonesian SMEs to spend less energy assembling the story of a payroll run and more time looking after the people behind it. A small team should be able to run a dependable process without first building a miniature HR department.

The hidden cost is the handoff

Spreadsheets are useful. They are flexible, familiar, and easy to start with. The difficulty comes when the spreadsheet is expected to act as an employee database, attendance ledger, calculation engine, and record of approval at the same time. A formula can calculate a number; it cannot, on its own, explain whether the inputs were complete or who confirmed a late change.

Consider a hypothetical business with two branches. One manager sends attendance as a file. Another confirms a correction in chat. An employee asks about a deduction while the administrator is still reconciling the month. Each task sounds small. Together they create repeated checking, interruptions, and dependence on one person who remembers how everything fits together.

The cost is not just administrative time. It is the uncertainty of wondering whether a correction made it into the final run. It is the employee having to ask for an explanation that should already be clear. And it is the difficulty of handing the work to a colleague when the process exists mostly in someone’s memory.

A payslip is a record of someone’s work. Clarity is part of taking that work seriously.

Built around Indonesian reality

An HR product becomes useful when it understands the environment in which people work. For Gokira, that means Indonesian payroll, including PPh21 calculations and BPJS contributions, alongside the everyday work of maintaining employee information, attendance, and leave. These are connected responsibilities, even when a business currently manages them in separate tools.

We do not want local requirements to feel like an extra spreadsheet attached to a generic product. The design goal is to bring the relevant information into the payroll workflow, make the result understandable, and leave room for the person responsible to review it. Automation is most useful when people can see what went into the answer.

Affordability and usability matter just as much as feature breadth. A small business may have an owner or operations administrator handling HR alongside several other responsibilities. The product needs to make the next step clear without assuming a specialist is available to translate every screen.

One connected workflow, fewer loose ends

Gokira brings payroll and HR information into a common working context. Employee records establish who is being paid. Attendance and leave provide the period’s operational context. Salary components and applicable deductions contribute to the calculation. The person running payroll needs a clear opportunity to review the result before moving forward.

This is why we think about payroll as a sequence, rather than a single button. Collect the right inputs. Calculate consistently. Review what changed. Make the outcome understandable to the employee. The diagram below illustrates that design approach; it is not a screenshot of a live payroll run.

Employee self-service is part of the same idea. When people can access relevant HR information themselves, routine questions do not always have to travel through an administrator. Multi-branch workforce management addresses another source of fragmentation: teams working in different places still need a coherent record of the same business.

Give time back. Make trust visible.

The ambition is not simply to calculate faster. It is to reduce avoidable repetition and make the work easier to inspect. A useful payroll product should help an administrator understand the current state of a run, spot an unusual change, and answer an employee’s question without reconstructing the entire month.

The figure below lets you explore how repeated manual handling can accumulate as a team grows. Its inputs are illustrative assumptions that you can change. It is not a measurement of Gokira’s performance or a promise of time saved. Real effort depends on the quality of the records, the complexity of compensation, and the review a business needs.

For us, the meaningful questions are practical: how often must someone re-enter the same information? How easily can they trace an unexpected amount back to its inputs? Can another colleague understand the process? Can an employee get a clear explanation? These are the outcomes we want the product to support.

Why this belongs at Majin

Majin builds software for the real economy: the systems behind the movement of goods, services, and money. Payroll sits directly at that intersection. It connects a business’s operations to the people whose work makes those operations possible.

Our products address different parts of that everyday infrastructure. Stor focuses on business operations. Gokira focuses on the workforce and payroll. SiMahir and Galeri help people participate in service and creative markets. The shared purpose is to put useful digital tools within reach of businesses and individuals whose needs are often treated as too small or too specific.

Gokira is our response to one very concrete problem: taking care of a team should not require a monthly scramble through disconnected records. We are building toward a calmer, clearer process, where the software carries more of the repetitive work and people can give their attention to the decisions that deserve it.