E-Invoice Compliance Checklist: 10 Steps to Get Your Malaysian Business Ready
A practical, step-by-step checklist to prepare your Malaysian SME for LHDN e-invoice compliance. Covers systems, processes, data, and team readiness.
Theory is helpful. A checklist you can actually tick off is better. If you have read our overview of the LHDN e-invoice mandate and our comparison of compliance approaches, you already understand the what and the why. So let us get practical. This post is the how.
Below are 10 concrete steps to get your business e-invoice ready. Work through them in order, because each one builds on the last. Grab a coffee, pull up your current invoices, and let us walk through it together.
Step 1: Confirm Your Compliance Deadline
First things first: when does your business actually need to be ready? It is worth nailing this down before you do anything else, because the deadline shapes everything that follows.
- Check your annual revenue against LHDN's phased rollout thresholds
- Note that revenue is based on annual turnover, not profit
- If you are unsure which phase applies, check the official MyInvois portal or consult your tax advisor
- Mark the deadline in your calendar and work backwards - you need at least 2-4 weeks for implementation, plus buffer time for testing
Action item: Write down your compliance deadline. Then subtract 4 weeks. That is your real deadline - the date by which implementation should be complete so you have time to test.
Step 2: Register on the MyInvois Portal
If you have not done this yet, get your business registered on LHDN's MyInvois platform. It is the foundation for everything else, no matter which approach you end up taking.
- You will need your company's TIN (Tax Identification Number)
- Registration is required regardless of which compliance approach you choose (manual portal, standalone tool, or ERP integration)
- Familiarise yourself with the portal interface - even if you plan to use an automated solution, understanding the portal helps you troubleshoot issues
Action item: Complete your MyInvois registration. If already registered, verify that your business details are current and accurate.
Step 3: Audit Your Current Invoicing Process
Before you change anything, you need an honest picture of how invoices actually get made today. Not how they are supposed to be made: how they really happen, messy bits and all. So map it out, step by step:
- Who creates the invoice?
- What information do they use as the source? (Quotation? Delivery order? Verbal instruction?)
- What tool do they use? (Accounting software? Excel? Word?)
- How is the invoice sent to the client? (Email? WhatsApp? Post?)
- How long does it typically take from job completion to invoice issuance?
- Where is the invoice stored after issuance?
This audit has a way of surfacing gaps you did not know were there. If your invoices are typed into Excel from memory, the structured, accurate data that e-invoicing demands is going to be a real challenge, and better to know that now than on go-live day.
Action item: Write down the step-by-step process for creating and sending an invoice in your business. Note any inconsistencies or manual steps.
Step 4: Check Your Data Quality
E-invoices are picky. They require specific fields, filled in accurately, every time. So let us see how your current invoices measure up. Go through the lists below and tick off what you already capture:
Seller details:
Buyer details:
Invoice details:
The big gap for most SMEs: customer TINs. Most businesses simply never asked for them, because until now there was no reason to. Under the e-invoice mandate, this quietly becomes a required field, and collecting it across your whole customer base takes time. Do not leave it until the day you need to issue your first compliant e-invoice. Start asking for TINs now, on every new order and every renewal.
“Start collecting customer TINs now. Do not wait until your first compliant e-invoice is the thing forcing you to chase them.
”
Action item: Check 10 recent invoices against the required fields above. Note which fields are missing or incomplete.
Step 5: Assess Your Current Software's E-Invoice Capability
If you already use accounting software, the next question is simple: can it actually talk to MyInvois? Here is what to find out:
- Does it have a MyInvois integration or module?
- If yes, is it included in your current subscription or an additional cost?
- Has the integration been certified or validated against LHDN's requirements?
- If no, does the software vendor have an e-invoice integration on their roadmap?
If your software cannot do e-invoicing and has no plans to, you will need an intermediary tool or a change of system. And if you are not using accounting software at all (invoicing straight in Excel or Word), this is the moment to either adopt software with e-invoice capability or bring in a standalone e-invoicing tool.
Action item: Contact your accounting software vendor and ask specifically: "Does your software integrate with LHDN's MyInvois system? If yes, what do I need to do to enable it?"
Step 6: Decide Your Compliance Path
By now you know your deadline, your process, and your software's limits. Time to pick a route. There is no single right answer here, just the one that fits your situation. Steps 3 to 5 should point you fairly clearly to one of these three:
Path A: Enable e-invoicing in your existing software. If your accounting software supports MyInvois integration and your data quality is good, this may be the simplest path. Estimated effort: 1-2 weeks of configuration and testing.
Path B: Add a standalone e-invoice tool. If your software does not support e-invoicing, a standalone tool can bridge the gap. This is the quick fix approach. Estimated effort: 1-2 weeks. Budget: from RM 7,000.
Path C: Implement a connected system with built-in e-invoicing. If your invoicing process is fundamentally manual and you are already feeling broader operational pain, this is your chance to solve several problems at once instead of just patching this one. Estimated effort: 4-12 weeks. Budget: from RM 15,000.
Action item: Choose your path and set a start date for implementation.
Step 7: Plan for Credit Notes and Debit Notes
Here is something that catches a lot of people out: e-invoicing is not only about invoices. Credit notes (for refunds, returns, or adjustments) and debit notes have to comply too. If these are part of your day-to-day, do not let them become a last-minute surprise.
If your business regularly issues credit notes or debit notes:
- Ensure your chosen solution handles these document types
- Understand the process for issuing e-credit notes (they reference the original e-invoice's unique identifier)
- Test the credit note workflow during your implementation, not after go-live
Action item: Review how many credit notes and debit notes your business issues per month. Ensure your compliance solution handles them.
Step 8: Train Your Team on the New Workflow
The system can be perfect, but if the people creating invoices do not know the new routine, things will still go sideways. So bring your team along. Whoever touches invoices needs to be comfortable with:
- How to create an e-invoice (the tool and the steps)
- What happens when an e-invoice is submitted (the validation process)
- What to do when an e-invoice is rejected (how to correct and resubmit)
- How to issue e-credit notes and e-debit notes
- Where validated e-invoices are stored
Do not overthink the training. This is not a week-long course. A hands-on hour or two with real invoice data usually does the trick. What matters is that people actually practise: have them create, submit, and validate a few test e-invoices themselves before the real thing goes live.
Action item: Schedule training for your invoicing team at least one week before your planned go-live date.
Step 9: Run a Parallel Test Period
Resist the urge to flip the switch overnight. The safest way to go live is to run old and new side by side for a little while first, so any surprises happen on test data rather than real client invoices.
- Continue issuing invoices through your existing process
- Simultaneously create e-invoices for the same transactions
- Compare the outputs - are the amounts correct? Are all required fields populated?
- Submit test e-invoices through the MyInvois sandbox environment
This parallel run is where the hidden problems show up: data quality issues, workflow gaps, the odd edge case nobody thought about. Far better they surface here than in front of a customer.
Action item: Plan a 1-2 week parallel testing period. Identify 10-20 representative transactions to test with (including at least one credit note and one multi-line invoice).
Step 10: Set Up Monitoring
You have gone live. Now the question is: how will you know if something quietly breaks? Submissions can fail, and you do not want to discover that weeks later when a customer asks where their invoice is. A little monitoring goes a long way.
- Set up notifications for failed e-invoice submissions
- Assign someone to check submission status daily during the first month
- Create a simple log of issues encountered and how they were resolved
- Review compliance status weekly for the first month, then monthly thereafter
The usual culprits in those early weeks: e-invoices rejected over data quality (missing TINs, dodgy tax calculations), connectivity hiccups with the MyInvois API, and edge cases that slipped past testing. None of these are disasters if someone is watching for them.
Action item: Designate one person as the e-invoice compliance owner for the first three months. This person monitors submissions, handles rejections, and escalates issues.
Summary Checklist
Want a printable version to share with your team?
Need help working through this checklist? Book a free 30-minute e-invoice readiness assessment.
Ready to Transform?
Let's discuss how we can solve your business systems challenges.
Book The Blueprint