How a Growing Bandung Company Centralized HR with Odoo Employees

A company in Bandung — a services business that had grown from 8 to 55 people in under three years — had HR that never grew up with it. What worked fine for a small team became a quiet liability at scale: employee data scattered across spreadsheets, contracts in a shared drive nobody could navigate, and an onboarding process that depended entirely on one overworked office manager remembering everything.

The cost of HR-by-spreadsheet

At eight people, the founder knew everyone’s situation by heart. At fifty-five, that was impossible, and nothing had replaced it. Employee details lived in a master spreadsheet that was always slightly out of date. Contracts — a mix of PKWT and PKWTT — sat in folders with inconsistent names, so finding a specific one meant opening files until you got lucky.

The real pain points were predictable. A couple of PKWT contracts lapsed without anyone noticing until after the expiry, creating awkward legal scrambles. Onboarding a new hire was chaotic — collecting KTP, NPWP, and BPJS details, getting the contract signed, setting up access — all tracked in the office manager’s head and a checklist she sometimes forgot. When she took leave, onboarding effectively stopped.

What changed

They implemented Odoo Employees as the central HR record.

One employee database. Every person’s details, job, contract, statutory numbers (NPWP, BPJS), and documents moved into structured records in Odoo. The scattered spreadsheets and the unnavigable drive were replaced by one place where any HR question could be answered in seconds.

Contract tracking with reminders. Each contract was recorded with its type and dates, and approaching PKWT expiries now surfaced to HR ahead of time. The “we forgot the contract lapsed” problem ended — renewals became deliberate decisions made before the deadline.

Document management on the person. KTP, NPWP, BPJS, and signed contracts were attached to each employee record, organised and instantly producible. No more digging through folders.

Permissions for privacy. Salary and statutory data were restricted to HR and finance, with managers seeing only what they needed — sensible practice as the company grew and as PDP expectations rose.

The result

The most immediate win was simply being able to find things. Any HR query — whose contract expires next month, what someone’s BPJS number is, who reports to whom — became a quick lookup instead of a search expedition. The lapsed-contract problem disappeared because expiries were now visible in advance.

Onboarding became a repeatable process rather than a feat of memory. New hires’ documents and contracts went onto their record as part of a defined routine, so it no longer depended on one person remembering every step — and it kept working when she was away.

Why it worked

The company did not have an HR-effort problem; it had an HR-structure problem. The office manager was capable and diligent, but no individual can reliably hold fifty-five people’s contracts, documents, and statutory details in their head and a spreadsheet. Centralising the data into structured records did not replace her judgement; it removed the impossible memory burden and the single-point-of-failure risk.

It is worth noting they treated the migration carefully — cleaning up inconsistent spreadsheet data before importing rather than carrying the mess into Odoo. That upfront effort is why the new database was trustworthy from day one.

If your company has grown past the point where one person can hold all the HR details, and contracts or onboarding are starting to slip, centralising into a proper employee record is usually the fix. We are happy to look at how your HR is organised and show you what centralising would change, in a free one-hour conversation.