Validation errors can feel opaque the first time you hit one, especially under time pressure near a deadline. In practice, the great majority of rejections trace back to one of a small number of root causes.
This guide describes categories of common problems in general terms, so you know where to start looking. For the exact error code or message your file returns, always refer to SSM's official mTool user guide and published MBRS FAQs, which document specific validation rules in full.
1. An outdated mTool version
SSM updates mTool periodically to match taxonomy changes — most significantly around events like the MBRS 2.0 rollout. A file prepared with an outdated version can fail validation for reasons that have nothing to do with your actual data. Before troubleshooting anything else, confirm you are running the current mTool release published on SSM's MBRS page.
2. Wrong reporting standard selected
The SSM Taxonomy branches based on whether Malaysian Financial Reporting Standards (MFRS) or Malaysian Private Entity Reporting Standards (MPERS) applies to your company. Selecting the wrong standard at the start of preparation means every subsequent element you tag is being checked against the wrong branch of the taxonomy — which surfaces as a cascade of validation errors rather than one obvious mistake.
3. Incomplete tagging of mandatory elements
Certain elements within the taxonomy are mandatory for a given filing type; leaving one untagged, or tagging it against the wrong element, is a common source of rejection. This is more likely when data is being manually re-entered from a separately prepared financial statement rather than built directly within mTool from the start.
Free Download
Avoid these errors before they happen
Grab the free MBRS 2.0 Filing Readiness Checklist — 20+ checks across deadlines, exemptions, and setup, in one printable page.
4. Technical environment issues
Because mTool is an Excel-based application, its correct operation depends on the preparer's local environment — including having the required .NET Framework version installed. SSM's own guidance notes that a validation window can sometimes appear hidden behind the main application window rather than failing outright, which is easy to mistake for the tool being unresponsive.
5. Digital signature and submission-stage issues
Not every rejection happens during preparation in mTool — some occur at the mPortal submission stage, most commonly around the digital certificate used to sign and lodge the filing. Only the person acting as "Lodger" needs a PKI digital certificate; confusion about who holds that certificate, or an expired certificate, can stall a submission that was otherwise ready.
A practical order to check things in
- Confirm the mTool version is current.
- Confirm the correct reporting standard (MFRS or MPERS) was selected for your company type.
- Re-check that every mandatory element for your submission type has been tagged.
- Confirm the local technical environment (Excel, .NET Framework) meets SSM's stated requirements.
- If the failure happens at submission rather than preparation, check the Lodger's digital certificate status before assuming a data problem.
If a validation error persists after working through this list, SSM's official MBRS FAQs and user guides document specific error codes and messages in detail, and are the most reliable source for a precise diagnosis beyond the general categories covered here.