
Rectification filings have become one of the most frequently discussed topics among company secretaries and accountants in Malaysia. With the enhanced MBRS Portal 2.0, the submission architecture now mandates stricter validation, expanded rectification options, and higher accountability for data consistency under Section 602 of the Companies Act 2016.
As of August 2025, SSM’s MBRS FAQ (v2.8, May 2025) and training circulars confirm that rectification applications are no longer limited to simple re-submissions – they now require precise categorization, supporting documents, and justification trails through the new filing interface.
For company secretaries, understanding how to prepare, classify, and minimize rectification filings is essential to maintaining compliance and protecting audit integrity.
A Rectification Application is filed when an already approved Annual Return (AR) or Financial Statement (FS) submission contains an error or omission that needs correction. MBRS 2.0 structures these applications into clearly defined categories:
1. Standard Rectification
Filed under Section 602, Companies Act 2016, allowing correction of data submitted in prior filings – whether filed through MBRS or previously Over-The-Counter (OTC). This typically covers:
2. Filing Information Rectification
Used to correct metadata or filing labels instead of data within the document, such as:
3. Rectification with Court Order
Applied when a court has directed a correction under Section 602(1). This requires attaching a supporting PDF of the court order and a compressed ZIP of related documentation.
These refinements – confirmed in the August 2025 SSM training modules – mean every rectification file must now include:
Based on SSM’s May 2025 MBRS FAQ (v2.8) and recent filings analysis, the most common rectification triggers can be grouped into three practical categories:
Tip: Validate input sheets before generating the instance document to prevent format corruption errors like “Invalid content in Annexure.”
Tip: Always double-check the taxonomy version and filing type before submission.
Tip: Use MBRS 2.0’s pre-validation and schema validation features before committing your submission.
To reduce rectification frequency and improve first-time filing success, company secretaries should focus on three control points:
1. Validation Discipline
Always validate XBRL instance documents before filing.
2. Taxonomy Awareness
Ensure financial data aligns with the correct taxonomy – MBRS 2.0 adopts IFRS Taxonomy 2022, integrated with Companies Act 1965 and 2016 frameworks.
3. Digital Signature Compliance
Expired or missing digital certificates are now key rejection triggers post–June 2025. Maintain updated certificates and renew them early to avoid filing disruption.
IRIS Instant, an AI powered XBRL tagging tool, is designed to help company secretaries handle MBRS 2.0 filings with precision – including rectification workflows:
Developed by us, the same team behind SSM’s official mTool and mPortal, IRIS Instant uses the XII-certified XBRL validation engine that powers SSM’s infrastructure, ensuring every filing adheres to the latest MBRS schema and taxonomy specifications.
With increasing regulatory scrutiny since June 2025, company secretaries need dependable systems that reduce manual risk. By combining taxonomy intelligence, validation, and compliance alerts, IRIS Instant minimizes rectification frequency and ensures precision.
Pro Tip: Use the platform’s Rectification Insights Dashboard to review recurring filing errors and receive smart recommendations for data quality improvement.
Rectification filings in MBRS 2.0 are an integral part of Malaysia’s enhanced compliance framework – not a fallback. The new structure provides transparency, accountability, and a clear digital audit trail but demands greater preparation discipline from filers.
You can also read our blog Why MBRS Filing Errors Happen – And How to Prevent Them here
By leveraging systems like IRIS Instant, company secretaries can stay in full control of their filings, prevent common rectification triggers, and maintain flawless SSM taxonomy compliance – every time.