Asher's Blog

It is easy to think that payroll is primarily a software problem. A company has employee information, salary figures, deductions and bank details, so the apparent task is to build a system that performs the calculations and sends the money. If the interface is simple, the reports are accurate and the transfers are fast, it may appear that the problem has been solved.

However, that description misses the most difficult part of payroll, especially in a market like Nigeria. The hardest part of moving money for people is earning the right to move it for them. Before an employer entrusts a platform with the money that pays an entire workforce, the company must believe that the platform will be available when it matters, protect sensitive information, calculate correctly, complete every transaction and remain accountable if something goes wrong. Payroll is therefore a software product built on top of a much deeper trust problem.

This becomes even more important in a large but unevenly structured business environment. Nigeria has sophisticated banks, major corporations, globally competitive technology companies and well-run growing businesses, but it also has an enormous informal economy and many traditional businesses that still manage important processes manually. The National Bureau of Statistics reported that informal employment accounted for 93 per cent of employment in the second quarter of 2024. That figure is not a direct count of informal businesses, but it illustrates how much of the country’s economic life still happens outside highly formal organisational systems.

Many founders still mix personal and business spending, approve salaries through messages, keep employee information in disconnected files or make payment decisions according to whatever cash is available at the time. In some businesses, payroll is not a defined process with controls and predictable dates; it is a monthly improvisation performed by the founder, an accountant or one trusted administrator.

A payroll company entering this market is therefore not merely asking customers to replace one application with another. It may be asking them to replace habits, surrender some control, formalise decisions and entrust a third party with information and money they have historically guarded personally. A product can be technically excellent and still fail because it has not understood the emotional and institutional difficulty of that transition.

Payroll is one of a company’s most sensitive promises

Employees experience a company’s promises through what happens on payday. An employer may speak about culture, loyalty, purpose and long-term ambition, but if salaries arrive unpredictably, payslips are inaccurate or deductions disappear without explanation, those words gradually lose their meaning. Payroll is where the company’s values become tangible because it involves a promise that employees organise their lives around.

People plan rent, school fees, food, transportation, medical costs, debt repayments and support for extended family around the expectation that their salaries will arrive when the employer said they would. A delayed salary is therefore not merely a delayed bank transfer. It can disrupt several obligations at once and place an employee in the uncomfortable position of explaining a failure that was not theirs.

This is why payroll cannot be treated like an ordinary administrative feature. If a customer relationship management tool is unavailable for an hour, a salesperson may record notes somewhere else and return later. If a payroll platform fails while a company is paying hundreds or thousands of employees, the consequences immediately spread beyond the HR or finance department. Employees begin asking questions, management becomes anxious, the payroll team loses credibility, and the employer’s relationship with its workforce is weakened.

For a payroll provider, reliability is therefore part of the moral value of the product. The customer is not only buying calculations and transfers; the customer is buying confidence that one of the company’s most consequential promises will be kept.

Good software is necessary, but it is not sufficient

Trust in payroll is not created by branding statements that repeatedly tell customers to trust the company. Trust grows when the product behaves consistently enough that customers no longer have to wonder what will happen.

The software must calculate salaries correctly, preserve a clear approval trail, protect employee data, prevent unauthorised changes and show the customer what has happened at every important stage. It must make errors easier to detect before money leaves the account and make reconciliation straightforward after payment. These features may appear operational, but each one answers a question about trust: Who changed this figure? Who approved the payroll? Is the money safe? Did every employee receive the correct amount? Can we prove what happened if someone disputes it later?

Trust is also built by how the company behaves when the system does not perform as expected. No serious technology company should claim that nothing can ever go wrong. Banks can experience downtime, integrations can fail, incorrect data can be uploaded, and human beings can approve the wrong information. The real standard is whether the platform has designed safeguards around foreseeable failure and whether it responds with urgency, honesty and competence when an unexpected problem occurs.

A trustworthy payroll company does not hide behind the software when a customer needs help. It accepts that the product includes the support team, the escalation process, the communication sent during an incident, the speed of resolution and the quality of the explanation afterwards. Customers often decide whether to deepen their trust not when everything is working perfectly, but when they see how the company behaves under pressure.

This is what it means for payroll to be personable. The platform should be simple enough to reduce anxiety, but the company behind it must also feel reachable and responsible. Particularly in a market where many businesses are moving from manual processes for the first time, customers need to know that they have not handed a critical obligation to an anonymous machine.

You must earn the right to move a customer’s money

When we began thinking deeply about payroll infrastructure at Eazipay, one of our most important responsibilities was ensuring that payroll would not fail on the day an employer decided to pay. It was not enough for the product to produce an accurate schedule if the final transfer remained uncertain. The last mile was the moment at which every earlier promise was tested.

We therefore had to examine the infrastructure behind the payment experience and make difficult decisions about providers and partnerships. We built a relationship with some of the strongest payment infrastructure available to us because an employer should be able to approve payroll and have employees receive their salaries immediately. The customer should not have to understand the complexity behind the transaction; our responsibility is to manage that complexity and provide the certainty for which the customer came to us.

That kind of reliability is expensive to build because it requires more than connecting to an application programming interface and displaying a successful message. It requires careful reconciliation, monitoring, liquidity planning, escalation paths, redundancy and relationships with institutions that can respond when something unusual happens. Much of the work that creates trust is invisible to the customer, but the customer experiences its absence immediately.

Every payroll processed successfully adds a small deposit into what might be called a trust account between the platform and the customer. Each accurate calculation, timely payment, useful report and resolved support request increases the customer’s willingness to depend on the system. A serious failure can withdraw much of that trust at once, particularly if the provider communicates poorly or appears careless with the customer’s funds.

This is why a payroll company must grow at the speed at which its controls, infrastructure and service quality can support. Transaction volume may look impressive, but volume without reliability simply increases the number of people who can be harmed by a weakness in the system. Scale should amplify a trustworthy process, not conceal an unstable one.

The second trust relationship is between employer and employee

A payroll platform should not think only about earning the employer’s trust. It should also help the employer earn and retain the trust of employees. The best payroll products strengthen both relationships at the same time.

Employees should be able to understand how their salaries were calculated, see their payslips, confirm deductions and know what benefits are available to them. When information is hidden, delayed or difficult to interpret, employees begin to suspect that something may be wrong even when the employer has acted properly. Clarity prevents avoidable distrust.

Statutory deductions are an important example. An employee may see pension, PAYE or another obligation deducted from a salary, but a deduction on a payslip does not automatically mean that the money has reached the appropriate institution. Nigeria’s National Pension Commission requires covered employers to remit pension contributions within seven working days after salary payment. When employers deduct contributions but fail to remit them, they do not merely create a compliance problem; they break an employee’s trust by withholding money for a stated purpose and failing to complete that purpose.

A payroll platform that helps employers calculate, schedule, document and complete these obligations is therefore doing more than automating administration. It is helping the employer keep promises that employees may otherwise find difficult to verify. The employee can begin to trust that the amount deducted for pension will reach the retirement account, that tax obligations will be handled properly and that the records needed in the future will still be available.

We also think about products such as salary advances, earned-wage access, employee loans and other benefits through this trust lens. These features should not be added merely because they increase the number of things available inside an application. They should solve real problems without creating new forms of confusion or exploitation. If an employee can responsibly access earned income or appropriate credit when an urgent need arises, the employer becomes more helpful to the employee’s financial life. However, pricing, deductions, eligibility and repayment must be clear, because a financial benefit that employees do not understand can quickly produce the opposite of trust.

The design question is therefore broader than, “What feature can we add?” It is, “Will this feature make the relationship between the business and its employees more dependable, transparent and fair?” That question changes how products are built because it forces the company to consider the human outcome rather than only the usage metric.

Traditional businesses do not need to be insulted into becoming structured

When technology companies encounter manual processes, there can be a temptation to speak about the customer as though the customer is unsophisticated and simply needs to be educated. That approach misunderstands why many traditional businesses operate as they do.

Some founders have retained control because they have experienced fraud, poor advice or unreliable employees. Some businesses work with thin margins and unpredictable cash flow, which makes formal monthly processes difficult. Others have grown from family enterprises in which trust is personal rather than institutional. Their systems may be inefficient, but those systems often developed as responses to the environment in which the business was built.

The task of a payroll company is not to mock these habits. It is to understand them well enough to offer a safer and more useful alternative. A customer who has always approved every payment personally may need visibility and control before accepting automation. A business with inconsistent employee records may need a gradual onboarding process rather than a complicated implementation project. A founder who worries about losing access to cash may need to understand exactly when money moves, who can authorise it and what happens if payroll needs to be changed.

Software adoption accelerates when the product respects the customer’s current reality while making a better future easy to enter. The goal is not to force every business to behave like a multinational company on the first day. The goal is to help the business become more structured through repeated experiences that feel safe, useful and understandable.

This is particularly important in Africa, where many large opportunities exist precisely because formal infrastructure has not yet reached much of the market. The companies that win will not necessarily be those that copy the most advanced product from another country. They will be those that combine strong technology with a patient understanding of how trust is formed locally.

Trust must be designed into the company, not added to its marketing

If payroll is a trust problem, then trust cannot remain the responsibility of the communications team. It must influence product design, engineering, finance, compliance, customer support and leadership.

Engineering must treat reliability and security as essential features rather than invisible technical matters. Finance must reconcile funds and maintain controls that prevent customer money from being confused with company money. Compliance must ensure that the product reflects the obligations businesses are expected to meet. Customer success must understand that payroll issues carry emotional urgency, because the person reporting a problem may be facing hundreds of anxious employees. Leadership must resist decisions that create short-term growth while placing funds, data or business continuity at unreasonable risk.

The company must also be honest about what it can guarantee. Trust is damaged when a provider promises instant results that depend on systems it does not control and then disappears when those systems fail. A more responsible company designs around its dependencies, communicates limitations clearly and builds enough operational capacity to honour the commitments it makes.

Certifications, audits and documented controls can help customers evaluate a provider, particularly as the company begins to serve larger organisations. They establish minimum standards and provide external scrutiny. However, certificates do not replace daily behaviour. A company can display impressive badges and still lose trust if salaries fail, reports are wrong or customer concerns are handled casually. Formal assurance matters most when it confirms a culture that already takes responsibility seriously.

The real product is certainty

Payroll software may calculate gross pay, deductions and net pay, but the deeper product is certainty. The employer wants to know that salaries will be paid accurately and on time. The finance team wants to know where the money went and whether every figure can be reconciled. The HR team wants records that can answer employee questions. Employees want to know that their pay, pension, taxes and benefits are being handled as promised.

Once a platform provides that certainty consistently, it becomes more than a tool used at the end of the month. It becomes part of the institution through which the company keeps faith with its people. That position is valuable, but it also carries enormous responsibility because a payroll provider participates in the relationship between work and livelihood.

This is why I believe payroll is a trust problem before it is a software problem. The code matters, the interface matters and the payment infrastructure matters, but all of them serve a larger purpose. They must give an employer the confidence to hand over a sensitive recurring obligation and give employees confidence that the promises attached to their work will be honoured.

The hardest question for a payroll company is therefore not whether it can move money. Many systems can move money. The harder question is whether businesses will trust it enough to move the money that matters most, and whether every successful payroll will justify that trust again.

References and further reading

• National Bureau of Statistics, Nigeria Labour Force Survey, Q2 2024.
• National Pension Commission, Circular on Compliance with Provisions of the Pension Reform Act, May 2025.
• National Pension Commission, Framework for Recovery of Outstanding Pension Contributions and Interest Penalty from Defaulting Employers.