How Malaysian reporting calendars affect dashboard cut-offs
Many dashboard applications arrive with a default calendar from another market. That default may treat a Malaysian public holiday as a business day, or it may close a day when Bursa is open. Performance engines then annualise, compound, or skip a day in a way the local team did not intend.
Unit trust and private-fund dealing days add another layer. A fund that deals on a T+1 cycle in Kuala Lumpur may still be valued in the application on a New York close because that was the vendor’s demo data. The tile will show a number. It will not be the number the offering document describes.
We ask for three calendars at the start of fieldwork: the exchange or dealing calendar the client believes it uses, the calendar configured in the application, and the calendar the custodian uses for statement cut-off. When those three differ, we do not pick a winner. We show the effect on a sample period and let the accountable owner choose which calendar is policy.
Ramadan working hours and state holidays in Selangor also affect operations even when they do not change the market calendar. File loads that usually run at 18:00 may run the next morning. If the application stamps “as at” from the load time rather than the statement date, a dashboard published for a Monday pack may quietly be a Sunday extract.
None of this is exotic. It is local practice meeting an application that was configured quickly. Writing the cut-off into the engagement letter, and into the application settings, prevents a class of arguments that otherwise reappear every financial year-end.