The Payroll Earthquake
A short story about enforcing integrity and rebuilding trust.
Episode 1 — The Calm Before the Quake
11 AM, Thursday morning. Keerthi Raj, HR Operations Lead at Blue Cargo Logistics, walked into her office, her new normal time of entry. Ever since HRMS the Human Resources Management System, implementation began three months ago, late arrivals and late nights had taken over her routine.
The last few weeks had been especially punishing. Preparing decades of employee records for migration was no small task. Blue Cargo was a fifty-year-old company with a workforce spanning every age group, grade, and employment type, including permanent staff, contract workers, retirees, and even family pensioners. Collecting accurate data for all of them was a logistical marathon.
As employee records were confidential, Keerthi couldn’t simply delegate the work. She and her two trusted interns spent long evenings and sacrificed weekends, combing through files, verifying dates, correcting mismatches, and ensuring every detail would survive the migration. Then came UAT, the User Acceptance Testing phase, where she had to test every workflow, every screen, every calculation, and every report. Hours disappeared into validation cycles.
But the promise of the new HRMS kept her going.
It was supposed to be a giant leap in Blue Cargo’s automation landscape. The Time Office, HR, and Finance teams were eager to experience payroll processing in minutes instead of days. They dreamed of days of instant wage transfers, auto-generated payslips, accurate statutory reports for income tax, group insurance, provident fund, and other compliance requirements.
The promise of real-time attendance capture, seamless shift management, a self-service portal where employees could view timesheets, pay structures, pay-slips, policies, certificates, and raise queries directly caught every employee’s imagination.
For Keerthi, it wasn’t just a system upgrade. It was her chance to prove that HR could lead transformation and not merely support it.
She sat down at her desk with quiet confidence. The data migration had gone smoothly. Every department involved, including the Time Office, HR, Finance, and even the regional hubs, had tested the workflows and confirmed accuracy. User training had gone better than expected. The IT team and the implementation partners had repeatedly assured her that everything was “production ready.”
Across the organization, faces looked genuinely excited. Even the delivery teams, loaders, drivers, security guards, and contract workers, usually indifferent to system changes, were eager to try the new portal. For many of them, this was the first time they would have direct access to HR without standing in queues or chasing supervisors.
Then there was Manoj, the Logistics Head, the man who had questioned every automation initiative for years. He had congratulated Keerthi that morning. It was the first time he had ever done that, with an unusually warm tone.
Keerthi had smiled, but a small part of her wondered why he seemed so invested in this rollout. She brushed the thought aside.
By afternoon, the HR bay was calm. Employees were exploring the new interface. Queries were minimal. For the first time in weeks, Keerthi allowed herself a moment of relief.
Then her phone buzzed.
“Salary mismatch. Please check.”
She frowned. Probably a one-off error.
Another message arrived.
“Wrong deductions this month.”
Then another.
“No overtime added.”
Keerthi opened the HRMS dashboard. Everything looked normal. She refreshed the screen. There weren’t any alerts or errors logged.
She leaned back, exhaled, and told herself not to overreact.
But at 8:47 PM, her phone lit up again, this time with a flood of notifications.
Twenty-seven messages. All saying the same thing. “Wrong salary credited.”
Something was seriously wrong.
**
Subscribe to my newsletter, “Quiet Lives, Loud Truths,” and read on …
Explore more stories and management fiction books on my website rsundar.com.
***
Episode 2 — The First Tremors
Friday mornings at Blue Cargo were usually busy. This was when they loaded containers onto trucks that would traverse the entire country over the weekend. Delivery staff checked routes, supervisors shouted instructions, and forklifts hummed in the background.
But today, the noise had a different texture. It wasn’t operational chaos. It was anger.
Keerthi Raj walked into the HR bay and froze.
A crowd of delivery staff had gathered outside, holding salary slips and printouts from the HRMS portal.
“Madam, this is wrong.”
“My overtime is missing.”
“They cut my pay by ₹4,200.”
“I worked night shifts all week. Why does it show zero hours?”
She was unprepared for this. She looked around instinctively for support. The CHRO wasn’t there. The CFO and the CIO weren’t there.
Her mind flicked to Manoj, the Logistics Head. Would he step in? He had opposed the HRMS from the beginning, loudly and repeatedly. But yesterday, he had congratulated her. Will he be of help?
Within minutes, the complaints crossed 200 employees.
Her phone rang. Manoj.
His voice sounded the urgency. “Keerthi, they’re threatening a strike. If they stop deliveries today, we will lose our biggest client. You are not fair to the Night shift workers. Address their concerns before the afternoon shift.”
Keerthi looked at the angry workers. She signalled them to stay calm and give her time to check what had happened. She switched on her computer. A minute later, the bold new HRMS logo filled her screen.
She toggled to her email.
Finance had already written: “Payroll data incorrect. HR to resolve immediately.”
The IT team had responded too: “Attendance integration working as expected. No issue on our side. Software implementation partners to check.”
HR blamed IT. IT blamed the partners. Finance blamed HR. Delivery staff blamed everyone. Every finger pointed at someone else, and Keerthi stood at the centre of it all.
Her position had suddenly become the most vulnerable. She knew, painfully well, that every issue, even those unrelated to the HRMS, would now fall on her shoulders. That was the unwritten rule of system rollouts: success belonged to everyone and failure belonged to HR.
She opened the HRMS dashboard again. The numbers still looked normal. She scanned the error logs. There were no warnings or alerts. What could be the reason for the chaos outside?
She compared the salary slips employees were waving with the stack-up in the system. The amounts inside the HRMS were correct.
But the salary slips told a different story.
She pulled up the attendance summary for one delivery associate. Zero hours logged for the entire week. No overtime or night-shift allowance.
Impossible.
She opened the access control system. The biometric logs showed he had logged in and out every day of the month, on time. He had worked overtime for an entire week. He wasn’t absent.
She checked another employee. Attendance correct and payslip correct.
The next one. Overtime missing.
Another. Night-shift allowance missing.
Some records were perfect. Many were wrong.
A delivery supervisor stepped forward, voice shaking with frustration.
“If you don’t correct this today, we will stop all deliveries. No trucks move.”
The words hit her like a physical blow.
Keerthi felt the weight of the moment settle on her shoulders. This wasn’t a minor error. This was an earthquake, and the tremors were only getting stronger, and there was no one coming to her rescue. Not even Manoj, who had been unusually supportive yesterday. She swallowed hard, steadied herself, and turned back to the screen.
**
Subscribe to my newsletter, “Quiet Lives, Loud Truths,” and read on …
Explore more stories and management fiction books on my website rsundar.com.
***
Episode 3 — The Blame Game
By mid-morning, Blue Cargo’s conference room felt like a pressure chamber.
Finance arrived with spreadsheets. The IT Head arrived with logs. HR arrived with complaints. Delivery supervisors arrived with frustration.
Manoj stood at the head of the table arms folded, with an expression unreadable. He wasn’t here for explanations or for collaboration. He was here for a moment. Whether that moment was to demand a solution or to sabotage the rollout, Keerthi couldn’t tell yet.
Finance opened the attack.
“Attendance data is wrong. Payroll rules are correct. HR needs to fix this.”
The IT head fired back immediately. “Our integration is working. The HRMS is calculating incorrectly. Not our issue.”
HR responded sharply. “The system is new. If attendance isn’t syncing, it’s an integration problem.”
The implementation partner, joining remotely, added the classic line: “You guys tested everything in UAT. We addressed all concerns raised.”
The room erupted into a cacophony. Fingers pointed and accusations flew.
Then Manoj slammed his palm on the table.
“From the beginning, I’ve been saying this system is a waste and not suitable for the organization. See where we are now.”
He aimed the words at the room, but Keerthi felt the intent was against her. This wasn’t just frustration. This was Manoj’s attack on her, on HR, and on the entire transformation effort.
Whatever his motive was, resistance to change, or something else, she knew it was safer to stay quiet. She steadied her breath and opened her laptop. Data should speak for itself.
“You cannot condemn the system like that. This is part of our overall automation drive. We cannot have the Time Office, Payroll and HR outside the platform,” the IT Head shot back, visibly irritated.
Manoj didn’t stop. “If deliveries stop today, Blue Cargo loses ₹1.2 crore. I don’t care whose fault it is. Fix it, Keerthi.”
He didn’t wait for a response but walked out of the room, closing the door with a thud that felt heavier than it should have.
Others continued to argue. The noise rose again, but Keerthi tuned it out. She wasn’t interested in the blame game, but in the truth.
She opened the attendance log again.
Employee: Ravi Kumar Biometric: 9 hours HRMS: 0 hours
Employee: Sandeep Biometric: 10 hours HRMS: 0 hours
Employee: Priya Biometric: 8 hours HRMS: 8 hours
Employee: Raghuram Biometric: 8 hours HRMS: 8 hours
A pattern was forming, and it wasn’t random.
Every employee working on the night shift had exactly zero hours logged.
Her pulse quickened. This wasn’t a payroll or a finance mistake or a random glitch.
She looked up at the room full of arguing teams and said firmly:
“Stop. I think I’ve found something.”
The room fell silent instantly.
**
Subscribe to my newsletter, “Quiet Lives, Loud Truths,” and read on …
Explore more stories and management fiction books on my website rsundar.com.
***
Episode 4 — The Hidden Fault Line
Keerthi Raj stayed back in the conference room after everyone left. The arguments still echoed in her head: HR blaming IT, IT blaming the partner, Finance blaming HR, and Manoj blaming the entire software implementation project.
But none of that mattered now. The workers were on the brink of agitation. If they stopped the work, Blue Cargo’s operations would collapse. She had no choice but to find the root cause before the situation spiralled.
She opened the biometric logs again. Employee after employee showed the same pattern:
Biometric: 8–10 hours HRMS: 0 hours
Only night-shift employees were affected. Day-shift employees’ entries were perfectly normal.
Keerthi pulled up the integration script, the one the implementation partner had deployed. She wasn’t a developer, but years in HR operations had taught her enough to spot trouble.
She scrolled through the shift-mapping section.
Day shift → mapped
General shift → mapped
Weekend shift → mapped
Night shift → missing
Her heart thumped rapidly. She checked the conditional logic:
If Shift Type = “Day” Then
Fetch Hours ()
End If
That was it.
There was no code for Night, Late Night or Double Night.
The system had simply ignored every night shift entry. The system had considered two hundred employees as absent for an entire week because of one missing line of code.
Keerthi felt a mix of anger and relief. Anger at the partner for pushing an incomplete script. Relief that she finally understood the root cause.
She took screenshots, documented the issue, and called Manoj.
“Manoj, I found it. The night shift mapping is missing. The system never read their hours. We shall correct this immediately. Kindly inform the staff who are protesting.”
There was silence on the other end.
Then Manoj spoke sharply. “Keerthi, this explains everything,” and he cut the call abruptly.
It sounded unprofessional. Was he busy with something? Or did he not want to talk to her? The abruptness lingered in her mind longer than the words.
Keerthi pushed the thought aside and opened the User Acceptance Test logs. She needed to confirm whether anyone had reported this issue during UAT.
Surprisingly, no one had.
She probed deeper into the test cases, the requirement specification documents, and the reviewer comments. They had clearly included the Night shift data in the requirements. Code reviewers had confirmed adherence to the specifications. Unit testers, module testers, integration testers: none had reported an anomaly.
Then how did this happen?
A call from Manoj interrupted her thoughts. “I have collected the payslips of the Night Shift employees. Sending them to your desk,” he said. He did not sound apologetic for the abrupt closing of the call minutes earlier.
A bunch of papers. Will it be of any use? I can see their payslips in the system? Does Manoj believe he is helping me? And how did he collect only the night shift people’s payslips so soon?
She opened the deployment logs. There lay the shocker.
One of the partner’s employees had pushed a new script after UAT, without informing HR or IT. An undocumented change. A fault line hidden beneath the rollout.
Get Sundar R’s stories in your inbox
Join Medium for free to get updates from this writer.
Keerthi stared at the screen.
This wasn’t just a mistake. It was negligence. Or was it deliberate? If deliberate, why? Under whose prompt? Who had approved the change?
This demanded a detailed audit of the system.
Programmers could correct the code immediately. But addressing an exposure like this, which hinted at intent, would be far more complicated than she had expected.
**
Subscribe to my newsletter, “Quiet Lives, Loud Truths,” and read on …
Explore more stories and management fiction books on my website rsundar.com.
***
Episode 5 — The Race Against the Strike
By Saturday morning, Blue Cargo Logistics felt like a building sunk under tons of rubble.
Delivery staff had gathered again, this time in larger numbers. Some held placards, others held salary slips, but all of them held frustration. They weren’t tech-savvy; they didn’t want explanations, and they certainly didn’t want to understand the issue. They only wanted the immediate release of their salaries and corrected payslips.
At the entrance, Manoj stood addressing the crowd. Trying to calm them. Or was he stirring them?
“Give us a few hours. HR is fixing it. No one will lose a rupee.”
But the crowd stood unconvinced. Union leaders shouted slogans against HR and the management. They yelled about every issue, most of them unrelated to the system implementation.
Then someone yelled, “Keerthi, down, down!”
The chant spread instantly.
Keerthi froze for a moment. She was far too junior in the leadership hierarchy for anyone to single out and abuse her publicly. This wasn’t spontaneous anger. Was it orchestrated?
Yes, there was a technical error, and she was resolving it. But she wasn’t accountable for policies or management decisions, the things the crowd was shouting about.
Inside the HR bay, she heard the chants clearly. Tears trickled down her cheeks, but she forced herself to stay calm and focus on the issue.
She had already documented the missing night shift mapping. She had already confronted the implementation partner and had already escalated the issue to the CIO, the CHRO, and the CFO.
Now she was manually recalculating overtime for 200 employees, one by one, because she could no longer trust the system.
The crowd was growing, and the strike was inching closer.
Keerthi checked every number in the spreadsheets, biometric logs, attendance summaries, overtime sheets, all of them crowding her laptop screen. She verified every shift, recalculated every allowance, and cross-checked every discrepancy.
Finance hovered nearby.
“We need proof before we release corrected salaries,” they insisted.
IT hovered too.
“We’re deploying the new patch sent by the partner. Testing will take time.”
Time was the one thing Keerthi didn’t have.
Her phone rang again. Manoj.
“Keerthi, they’re planning to stop deliveries at 4 PM. If trucks don’t move, we lose the pharma client. That’s ₹18 crore a month.”
Keerthi didn’t look up. “I know. I’m working.”
She opened the test environment. The IT team had already started the sync with the new integration patch.
Attendance → HRMS Overtime → HRMS Night shift → HRMS
The progress bar crawled forward. 20% 40% 60% 80% 100%
Keerthi exhaled.
Then the screen flashed red.
“ERROR: Attendance Sync Failed.”
The patch had crashed.
Sweat trickled down her forehead. She wiped it quickly, her hands trembling.
Outside, the delivery staff were chanting again. She looked through the glass door for a moment. Mahesh stood at the front of the crowd, staring at her.
Was he defending her? Or had he joined them?
Inside, Keerthi stared at the error message. This wasn’t just a race against time. It was a race against a shutdown. A race to defend the HRMS system and her own credibility within the company.
**
Subscribe to my newsletter, “Quiet Lives, Loud Truths,” and read on …
Explore more stories and management fiction books on my website rsundar.com.
***
Episode 6 — The Patch That Saved the Day
The error message on Keerthi’s screen felt like a punch.
“Attendance Sync Failed.”
Outside, the delivery staff’s chants grew louder, angrier. Inside, the HR bay was painfully silent. Except for the two interns who had helped her during the data migration, she had no support. All the leaders had vanished when the situation was slipping out of control.
For the first time, she regretted being in the department at all.
The shouting intensified. Keerthi looked up just as Manoj pushed open the glass door and rushed in.
“What happened?”
Keerthi didn’t sugarcoat it.
“The new patch crashed. The system still isn’t reading night shift hours.”
Manoj didn’t hesitate.
“I think we should take the system off. I will report to the CEO. The manual process for timekeeping was better. It ran for fifty years. Why change it?”
His words were rude and deliberate. Front-end teams often saw only their part of the process. They didn’t understand the struggle behind the scenes: collating data, validating records, processing payroll, storing and retrieving information. But they complained loudly when there was a delay or an error.
Keerthi wasn’t here to convince the Head of Logistics about the need for automation.
She was here to address the problem. She pulled the integration script onto her screen again. The missing night-shift mapping was obvious, and the conditional logic for calculating time was flawed. The new patch IT deployed had only added a partial fix and not the full mapping.
She took a deep breath.
“I’ll rewrite the logic myself.”
She grabbed her laptop and walked straight to the IT department.
“Keerthi, this is production code,” said the IT engineer, the one person who had consistently supported her throughout the rollout.
She opened a new script window and typed out the corrected mapping:
Code
If Shift Type = “Day” Then
Fetch Hours ()
ElseIf Shift Type = “Night” Then
Fetch Night Hours ()
ElseIf Shift Type = “Late Night” Then
Fetch Late Night Hours ()
ElseIf Shift Type = “Double Night” Then
Fetch Double Night Hours ()
End If
She handed it to IT.
“Deploy this. Now.”
The IT engineer pushed the patch. The sync began again.
20% 40% 60% 80% 100%
No error.
Keerthi opened the attendance dashboard. Night shift hours appeared. Overtime appeared. Allowances appeared. Everything aligned.
Finance validated the numbers.
Keerthi walked out and informed Manoj that they had corrected the system and that they would credit the corrected salaries by evening.
Manoj stepped out to the delivery staff and announced:
“We have corrected the errors. HR will credit the corrected salaries by tonight.”
The crowd slowly dispersed. The tension in the air finally settled.
But Keerthi didn’t feel relief.
Why had the partner’s employee updated the patch without approval from HR or Finance? Who prompted him to push a change after UAT? Who benefited from the chaos?
As she packed her laptop, one delivery associate walked up to her.
“Madam, will this happen again?”
Keerthi paused.
She didn’t want to give a corporate answer. She wanted to give an honest one.
“We’ll make sure it doesn’t.”
But doubt lingered deep within her. Someone in the system knew how to violate the code. Fixing the code was easy. Rebuilding trust would be much harder.
**
Subscribe to my newsletter, “Quiet Lives, Loud Truths,” and read on …
Explore more stories and management fiction books on my website rsundar.com.
***
Episode 7 — Aftershocks and Trust Rebuilt
By Monday morning, Blue Cargo Logistics looked normal again. Workers had received their corrected salaries. Delivery staff were back on their routes. The logistics floor sounded familiar with the hum of forklifts, the chatter of supervisors, and the rhythm of operations settling back into place.
But inside the HR bay, Keerthi Raj wasn’t celebrating. She was documenting and probing. She had called for a meeting at 11 AM.
Keerthi laid out the timeline with calm precision:
- Night shift mapping was missing in the integration script
- The partner pushed a silent and unapproved update after UAT
- Attendance sync ignored 200 employees
- Payroll calculated based on incomplete data
- New patch code from the partner failed because of partial logic
- Manual recalculation required
- Final fix deployed directly in the production system under crisis conditions
Finance listened quietly. IT took notes. Manoj nodded through every point with a neutral expression.
Then Keerthi presented the safeguards:
- HRMS rollout checklist updated: Three levels of sign-off required from HR, Finance, and IT heads for every patch code or configuration update.
- Mandatory end-to-end testing: No script goes live without two full rounds of validation.
- Partner governance tightened: No undocumented changes and no silent or unapproved deployments.
- Attendance Audit every Friday: Catch issues in the time and attendance records before payroll processing, not after.
Manoj leaned back and smiled.
“Keerthi, you have won this time. This could have gone differently.”
She smiled politely but said nothing.
Manoj didn’t know yet that she had already sent a detailed and confidential note to the Managing Director and the Audit Committee of the Board.
Included in that note were deployment logs, timestamps, the identity of the partner employee who pushed the silent update and the one suspected to have instructed him.
The aftershocks had settled. But the investigation had just begun.
Later that afternoon, whispers floated through the corridors about a heated discussion that was underway between Manoj and the Managing Director.
By 3 PM, a group of systems auditors arrived at Keerthi’s office. They collected every piece of evidence she had documented: deployment logs, screenshots, timestamps, attendance mismatches, and the silent patch update.
Another whisper followed soon after.
The Managing Director had asked Manoj, the Logistics Head, to go on long leave. Advice went to IT and HR to disable his access to all systems and revoke all communication channels with the company, its suppliers, customers, employees, and other stakeholders.
The audit team was now probing everything including the HRMS, the integration scripts, and even the earlier manual records used by the delivery team over the last several years. They already knew Manoj was the saboteur of the system and that he had tampered with the manual records of the time-office for years.
That evening, Keerthi walked past the delivery bay. Except for the sound of trucks parking and forklifts moving, the place felt unusually quiet.
The same delivery associate who had asked her, “Madam, will this happen again?” waved at her.
This time, his expression wasn’t frustration. It was trust.
Keerthi smiled back.
Payroll and system errors aren’t just numbers. Employees, their families, and their livelihoods depend on them. When trust breaks, fixing the software code is only the first step. Enforcing integrity and rebuilding confidence take much longer. Blue Cargo had taken that step today.
The earthquake had passed the aftershocks had settled, and the ground beneath Blue Cargo was steady again.
THE END
**
Subscribe to my newsletter, “Quiet Lives, Loud Truths,” and read on …
Explore more stories and management fiction books on my website rsundar.com.
#HRTransformation #PayrollManagement #DigitalTransformation #LeadershipInCrisis #WorkplaceStories #CorporateFiction #ChangeManagement #Operations #DataIntegrity #EmployeeExperience #Storytelling #HRMS #ERPImplementation
