MyInvois submission errors usually occur because of incorrect invoice data, invalid taxpayer information, missing mandatory fields, insufficient user authorisation, or API integration issues. By identifying the specific error message and resolving its root cause, businesses can successfully resubmit invoices while reducing future validation failures.
Malaysia’s e-Invoicing initiative has transformed how businesses issue and report invoices to the Inland Revenue Board of Malaysia (LHDN). Whether you’re a small business submitting invoices through the MyInvois Portal or an enterprise integrating directly with the MyInvois API, submission errors are an inevitable part of the learning curve.
While seeing a rejected invoice can be frustrating, most MyInvois errors are straightforward to resolve once you understand what the system is validating. Rather than repeatedly submitting the same invoice, it’s more effective to identify the root cause and correct the underlying issue.
If you’re still getting familiar with Malaysia’s e-Invoicing framework, our guide to What Is MyInvois Malaysia? explains how the platform works, while the Complete Guide to e-Invoice Malaysia provides a broader overview of the compliance requirements for Malaysian businesses.
Why do MyInvois submission errors happen?
Every invoice submitted to MyInvois is validated against LHDN’s requirements before it is accepted. These checks ensure that invoice information is complete, accurate, and compliant with Malaysia’s e-Invoice specifications.
Most submission issues fall into two categories:
Validation errors
Validation errors occur when the invoice data itself contains problems, such as:
- Missing mandatory fields
- Incorrect Taxpayer Identification Number (TIN)
- Invalid tax codes
- Incorrect classification codes
- Inconsistent invoice totals
These errors require corrections to the invoice before it can be successfully submitted.
Submission errors
Submission errors happen after the invoice has been prepared but before it reaches MyInvois successfully. They commonly involve:
- Authentication failures
- Expired API access tokens
- Incorrect user permissions
- Invalid API payloads
- Temporary system or network issues
Understanding which category an error belongs to helps narrow down the troubleshooting process and reduces unnecessary resubmissions.
Common MyInvois submission errors and how to fix them
- Incorrect Submitter
What it means
The person or application attempting to submit the invoice is not authorised to act on behalf of the taxpayer.
Why it happens
Common reasons include:
- Representative authorisation has expired.
- The wrong taxpayer profile is selected.
- Intermediary permissions have been revoked.
- The submitting user lacks sufficient access rights.
How to fix it
Check the representative authorisation settings in MyTax and confirm that the correct taxpayer account is being used. If your organisation works with external accountants or finance service providers, verify that delegated permissions are still active.
How to prevent it
Review user permissions whenever staff responsibilities change and schedule periodic checks for intermediary authorisations.
- TIN Mismatch
What it means
The Taxpayer Identification Number provided in the invoice does not match the information registered with LHDN.
Why it happens
This error is usually caused by:
- Typographical mistakes
- Outdated customer or supplier records
- Incorrect company registration information
- Legacy master data that has not been updated
How to fix it
Compare the TIN against the official taxpayer records before resubmitting the invoice. Correct any discrepancies in your accounting system so that future invoices use the updated information automatically.
Businesses preparing for long-term compliance should also review the recommendations in our Malaysia e-Invoicing Challenges & Solutions guide, which discusses how clean master data reduces recurring validation issues.
- Missing Mandatory Fields
What it means
One or more required invoice fields are missing or incomplete.
Common examples include:
- Invoice number
- Invoice issue date
- Supplier details
- Buyer information
- Tax amount
- Currency
- Classification code
How to fix it
Review every mandatory field before submitting the invoice again. Even a single missing value can cause the entire submission to fail.
If you’re unsure which information is compulsory, our Mandatory e-Invoice Fields Malaysia guide explains every required field and how it is validated during submission.
- Duplicate Submission
What it means
The invoice has already been submitted successfully.
Why it happens
Typical causes include:
- Users clicking Submit multiple times
- Automatic retry mechanisms
- API timeout responses
- Failure to check the previous submission status
How to fix it
Before resubmitting, verify the invoice status using the MyInvois Portal or your ERP system. If the invoice has already been accepted, there is no need to send it again.
How to prevent it
Introduce duplicate detection within your accounting workflow and avoid automatic retries without first checking the submission result.
Organisations implementing automated invoice processing often reduce these issues by adopting structured workflows similar to those discussed in Invoice Automation Malaysia.
- Invalid Classification Code
What it means
The classification code entered on the invoice is invalid or no longer recognised by MyInvois.
Why it happens
This may occur because:
- An outdated classification list is being used.
- Manual entry errors have been made.
- The ERP mapping has not been updated.
How to fix it
Update your classification code reference to the latest version published by LHDN and verify that your accounting software is using the current mapping.
- Invalid Tax Type
What it means
The tax treatment assigned to the invoice does not match the transaction.
Why it happens
This is commonly caused by:
- Incorrect SST settings
- Outdated tax configuration
- Incorrect tax category selection
How to fix it
Review your tax configuration and ensure the selected tax type reflects the actual transaction before generating the invoice.
Businesses reviewing their compliance processes may also benefit from our e-Invoicing Tax Compliance article, which outlines practical approaches to maintaining accurate tax settings across finance systems.
- BadStructure (Invalid Payload)
This error primarily affects businesses submitting invoices through API integrations.
What it means
The JSON or XML payload does not conform to the schema expected by MyInvois.
Why it happens
Typical causes include:
- Missing properties
- Invalid data types
- Incorrect formatting
- Syntax errors
- Unsupported field values
How to fix it
Validate the payload against the latest MyInvois schema before submitting the request. Logging detailed API responses instead of generic error messages also makes troubleshooting much easier.
If your organisation is integrating accounting software with MyInvois, reviewing our Integration with Xero or Integration with QuickBooks resources can help you understand how invoice data flows between systems and where validation issues commonly occur.
Quick reference table
| Error | Most common cause | Recommended action |
| Incorrect Submitter | Missing authorisation | Verify representative access |
| TIN Mismatch | Incorrect taxpayer details | Update and validate TIN |
| Missing Mandatory Fields | Incomplete invoice | Complete all required fields |
| Duplicate Submission | Invoice already submitted | Check document status first |
| Invalid Classification Code | Outdated mapping | Update classification codes |
| Invalid Tax Type | Incorrect tax configuration | Review tax settings |
| BadStructure | Invalid API payload | Validate against schema |
While these are among the most frequently reported issues, they represent only part of the MyInvois troubleshooting process. Authentication failures, API rate limits, portal-versus-API differences, and preventive best practices are equally important for maintaining reliable e-Invoice operations and will be covered in the next section.
- Authentication Token Expired
Businesses that submit invoices through API integrations may encounter authentication errors instead of invoice validation issues. These errors occur before the invoice reaches MyInvois for validation.
What it means
The access token used to authenticate your application has expired or is no longer valid.
Why it happens
Common causes include:
- Expired OAuth access token
- Authentication session timeout
- Incorrect token management
- Refresh token failure
How to fix it
Generate a new access token before submitting the invoice again. If your organisation processes invoices continuously, automate token renewal instead of waiting until authentication fails.
How to prevent it
Implement automatic token refresh logic and monitor authentication failures through your integration logs. Businesses integrating multiple accounting platforms should also follow the implementation guidance in our Integrating with Xero & QuickBooks guide to ensure authentication and synchronisation remain stable.
- Submission Forbidden
What it means
The request has been received, but MyInvois rejects it because the authenticated user is not permitted to submit invoices for the selected taxpayer.
Why it happens
This error is commonly caused by:
- Missing representative authorisation
- Expired intermediary approval
- Incorrect taxpayer account
- Revoked user permissions
How to fix it
Review representative permissions in MyTax, confirm that the correct taxpayer profile is selected, and ensure delegated authority remains active.
For businesses managing multiple entities or finance teams, documenting approval responsibilities can reduce permission-related issues. Our User Guide for Approval Matrix offers practical guidance on structuring approval workflows.
- HTTP 429 (Too Many Requests)
What it means
Your application has exceeded the API request limit within a short period.
Why it happens
Typical reasons include:
- Excessive batch submissions
- Aggressive retry mechanisms
- High-frequency automated requests
How to fix it
Instead of immediately retrying failed submissions, implement exponential backoff and retry after the recommended waiting period.
How to prevent it
Schedule large submission batches intelligently and monitor API usage. Organisations processing high invoice volumes often improve stability by adopting automated workflows such as those described in Automating LHDN e-Invoicing with Assist.
- Internal Server Error (HTTP 5xx)
What it means
This error usually indicates a temporary issue within the MyInvois platform rather than a problem with your invoice.
Why it happens
Possible causes include:
- Temporary maintenance
- Network interruptions
- Unexpected server-side issues
How to fix it
Wait a few minutes before retrying. However, always confirm whether the original invoice was successfully processed before resubmitting to avoid duplicate submissions.
If the issue continues, review official MyInvois announcements or contact LHDN support for further assistance.
MyInvois Portal vs API: Why the same error may have different causes
Although MyInvois displays similar error messages regardless of submission method, the underlying cause often differs depending on whether you’re using the MyInvois Portal or an integrated accounting system.
| MyInvois Portal | API Integration |
| Manual invoice entry | Automated invoice submission |
| User-driven validation | System-driven validation |
| Errors usually originate from manual input | Errors often originate from integration logic |
| Suitable for smaller invoice volumes | Suitable for medium and high-volume businesses |
For example, a TIN mismatch entered manually may simply require correcting customer information. The same error through an API integration could indicate outdated master data being synchronised automatically from your ERP.
If your organisation is evaluating integration options, our articles on Xero Integration and QuickBooks Integration explain how accounting systems exchange invoice data with MyInvois while reducing manual intervention.
A 10-step checklist before resubmitting an invoice
Before clicking Submit again, take a few minutes to complete this checklist.
- Verify supplier and buyer TINs.
- Confirm all mandatory invoice fields are complete.
- Review tax codes and classification codes.
- Check invoice totals and tax calculations.
- Confirm the invoice has not already been submitted.
- Verify representative authorisation.
- Refresh API authentication tokens if required.
- Validate the API payload against the latest schema.
- Review the detailed error message carefully.
- Resubmit only after correcting the identified issue.
Many businesses significantly reduce rejected invoices simply by introducing a structured pre-submission review. Our User Guide for the e-Invoice Feature provides additional operational guidance for organisations implementing regular e-Invoice processes.
Best practices to minimise MyInvois submission errors
Maintain clean master data
Incorrect customer or supplier information is one of the most common causes of recurring validation failures. Regularly reviewing taxpayer information helps prevent repeated corrections.
Automate validation where possible
Automated validation catches missing fields and inconsistent data before invoices reach MyInvois. Businesses exploring automation can learn more from our article on AI Automation for e-Invoicing Malaysia.
Keep compliance knowledge current
LHDN requirements continue to evolve. Staying informed helps finance teams avoid outdated practices and configuration issues. Our Malaysia e-Invoicing 2026 resource covers the latest developments affecting businesses.
Monitor integrations continuously
Successful integrations require ongoing monitoring, not just initial implementation. Reviewing API logs, authentication events, and synchronisation status helps identify issues before they affect invoice processing.
Train finance teams regularly
Even the best systems rely on knowledgeable users. Providing regular training on invoice preparation, validation rules, and approval processes reduces human error and improves compliance.
Additional resources that may help include:
- Everything You Need to Know on e-Invoice Malaysia 2025
- Malaysia e-Invoicing SME Guide
- Frequently Asked Questions About Malaysia e-Invoice
- MyInvois Portal Registration
Final thoughts
Most MyInvois submission errors are preventable. Rather than treating every rejection as an isolated issue, businesses should use each error as an opportunity to improve data quality, strengthen approval workflows, and enhance system integration. A structured validation process not only reduces rejected invoices but also improves operational efficiency as e-Invoicing volumes grow.
If your organisation is preparing for long-term e-Invoice compliance or exploring how AI can simplify finance operations, it’s worth evaluating whether your current infrastructure is ready for the next stage of digital transformation. Explore Our Solution to see how Assist supports intelligent document processing and e-Invoice automation, discover the available Features & Benefits, learn How It Works, compare Pricing, or Book a Demo to speak with an infrastructure specialist about building an AI-ready finance operation.
