← Articles

How a bug made it possible to pay out the same wages several times

3 min read (updated: August 24, 2026)

The button worked every time. And that was exactly the problem

An employee chose “Pay out”. The system created a confirmation and moved the operation to the history, but did not zero the balance. A second click created another payout of the same amount. So did a third.

The client first came to me with notifications that did not work. While checking the system, errors concerning money, staff access and the charging of fees came to light as well. I did not propose building everything anew. First I separated the critical problems from those that could wait.

Four risks instead of one defect

Wages could be paid out again

The confirmation and the zeroing of the balance were two independent actions. When the second did not go through, the first stayed in the history, and the money still showed as ready to be paid out.

I combined the two steps. Now they either happen together, or the whole operation is rolled back. The system can no longer stop halfway and leave a misleading state.

A Google account alone opened the door

Every person who logged in through Google immediately gained access to the system. The owner’s decision and the assignment of a scope of permissions were missing.

A new user now lands in a waiting room. Only after approval do they receive a role appropriate to their work. Logging in confirms identity, but does not in itself give the right to the company’s data.

Notifications were blocked

The main platform did not accept messages from Telegram in their original form. Instead of working around successive limitations, I built a small independent module that checks the message and passes it on in a format the system understands.

The company got its notifications back, and this element can work and be repaired independently of the rest of the application.

Some fees were charged twice

The error appeared only with specific combinations of dates and types of settlement. That is why it was hard to notice during ordinary manual checking.

I put the way fees are charged in order and added a history of operations. The owner can see when a fee was created, for what reason and from which place in the system.

What stayed, and what changed

The staff still use the tool they know. The changes covered the places where a simple system began to touch real money, personal data and permissions.

That is an important distinction. A tool built on a platform without traditional programming does not automatically become bad when the company grows. Nor does every part have to be rewritten. But you do have to know where convenience stops being enough and where hard safeguards are needed.

The result

The owner controls who sees the data. A payout cannot be made a second time by simply clicking again. Notifications arrive once more, and an unusual settlement can be traced without guessing.

The first repair began a longer cooperation. When a larger payout later revealed another limitation of the platform, the client came back — and that process was rebuilt as well.

See the full case study.

Case Study

From a single outage to ongoing care of a studio’s system

See the case study →

Have a similar problem?

Describe it in your own words — you do not need to know the names of technologies or prepare a specification.

Describe the problem