The problem
An ERP becomes more useful when it reflects how a business actually operates. Payments, vouchers, merchant balances and local requirements often need custom behaviour around the standard records.
My Frappe/ERPNext work combines business applications with the integration layer around them.
Professional work
As lead systems engineer at Simplex, my work includes custom Frappe/ERPNext applications and payment-related systems. The wider project family covers voucher purchase and redemption, merchant balances, transaction records, commissions and their connection to ERP accounting documents.
This is systems work: a transaction needs a clear relationship with the business record it creates, and the people operating the application need a usable workflow around that record.
Reusable integration work
I also develop Frappe tools and payment integration code, including Paynow-related work. These projects let me carry patterns from one integration into another without treating every gateway as an isolated application.
Zimbabwe compliance development
zw_compliance is my ongoing Zimbabwe-focused ERPNext application. Fiscalisation is the current focus. Payroll and NSSA-related functionality are future areas, rather than completed features.
The engineering balance
Frappe provides strong foundations for document models, administration and business logic. Customisation still needs care around permissions, upgrades, integration failures and the meaning of the resulting accounting records.
My aim is to keep the custom logic close to the business process while using the platform’s existing strengths.
What it demonstrates
This family shows Python engineering, ERP domain modelling, payment integrations and systems ownership. It belongs alongside my POS and banking work because it covers the business operations around transactions.