Budget compliance - Malaynova
Work that keeps budgets honest
A record of engagements where fiscal discipline was the central challenge. Each project here involved real constraints, competing priorities, and organisations that needed more than a spreadsheet to stay on track.
Selected work
Projects that shaped the practice
Municipal spending review, Sabah state authority
A regional authority was running a consistent gap between approved allocations and actual departmental spend - not through fraud, but through fragmented approval chains and late reporting. The engagement mapped every approval touchpoint across nine departments, identified where delays compounded into overruns, and produced a revised workflow that reduced reconciliation time from six weeks to eleven days.
Read the case studyProcurement audit, private hospital group
Three hospitals under one ownership structure were purchasing identical supplies at different prices, with no central visibility. The audit traced purchasing decisions back to individual ward managers and surfaced RM 1.4 million in avoidable variance across one financial year. A consolidated procurement policy replaced the informal system.
Read the case studyGrant compliance framework, university foundation
A university foundation managing multiple donor grants had no consistent method for tracking restricted versus unrestricted funds. Expenditure was being coded incorrectly, creating compliance exposure with two international funders. The project built a classification system and reporting template that the finance team could maintain without specialist input going forward.
Read the case studyHow this practice works
Practical discipline over theoretical frameworks
Malaynova was founded in 2014 with a specific focus: budget compliance as a discipline in its own right, not a subset of general auditing. The distinction matters because compliance failures in budgeting rarely come from bad intentions - they come from systems that were designed for a different scale, or approval processes that were never updated as organisations grew.
Each engagement starts with observation before recommendation. Spending patterns, approval chains, reporting cadences - these are mapped before any gap analysis begins. The goal is to understand why the current system behaves as it does, not just to measure how far it deviates from policy.
Deliverables are written for the people who will use them, not for the record. That means plain-language reports, process diagrams that a department head can follow without a finance background, and implementation notes that account for the actual capacity of the team taking things forward.
Budget variance analysis
Procurement compliance
Grant fund management
Process documentation
Reporting system design