ProjectsSetra Sari HRISLive
Setra Sari HRIS

Setra Sari HRIS

Same problem as Prabhu, different company shape. Setra Sari reuses the engine but follows its own rules for working hours, payroll components and approval paths, with a documented API contract so the client-facing apps are not built on guesswork.

What it does

  • Attendance and time off — cuti, izin, overtime — shaped to the client's own policies.
  • Payroll components, tax and payslips configured per company rather than hardcoded.
  • Employee Android app alongside the web app, sharing the documented API.
  • Custom tools and modules for workflows the standard product did not cover.

How it fits together

  1. Step 1SetupWorking hours, payroll components, approvals
  2. Step 2OperationAttendance and requests collected
  3. Step 3PayrollRun against the configured rules
  4. Step 4OutputPayslips and reports

Diagrams

How the product behaves, and how the pieces behind it talk to each other.

Business flow
Business flow diagram for Setra Sari HRIS
System flow
System flow diagram for Setra Sari HRIS

Stack

Services
PythonBottleMicroservices
Mobile
Flutter
Web
Server-rendered web app
Data
Relational database

Worth noting

  • Configuration over forks: client differences belong in data, not in a copy of the codebase.
  • The API contract is written down, so the mobile and web clients can move independently.
Generating0%