Maaliya started with a simple frustration: brilliant accountants in the Emirates spending their days retyping bills instead of advising clients. We set out to change that.
When VAT arrived in 2018 and corporate tax followed, UAE businesses faced a wave of compliance work with software built for other markets. Bills came in over WhatsApp and email, TRNs went unchecked, and month-end close stretched for days.
We built Maaliya to fit the way business actually happens here, covering every channel, every currency and every local rule, so accountants can spend their expertise where it matters, not on data entry.
Six things we argue about internally, written down so you can hold us to them.
Our numbers get filed with the FTA. When the model isn't sure, it says so instead of guessing. A flagged bill is cheaper than a corrected return.
We didn't localise a product built for somewhere else. AED, Arabic, the local banks and the FTA's rules were the starting point, not the roadmap.
Nobody grew up wanting to key bills off a phone screen. Every release is judged on how much of that work disappeared.
Encrypted in transit and at rest, PCI DSS compliant, and your clients' numbers never go near a public model. That's the whole policy.
The client switcher, the review queue, the rules engine: none of it came from a workshop. It came from firms telling us what was slowing them down.
The FTA changes something, we ship the same week. Filing season is a bad time to wait on a support ticket.
Our leadership team is based in Dubai and has spent years closing books, filing returns and writing the code that now does both. Founder and CEO Muneebah Khan started Maaliya after running finance and engineering teams across the region.
She's joined by Emaan Ali, Head of Engineering; Daniel Okafor, Head of Product; Rishabh Jeevi, Head of Tax & Compliance; and Yousef Nassar, Head of Customer Success. Accountants and engineers, each with time spent inside the finance function they now build for.