Short answer. E-invoicing fails most often because of poor data, not poor software. Before you submit anything, clean your customer and item records, collect TINs and registration numbers, set up document numbering and credit-note handling, and decide how validated invoices will be matched to your ledger each month.
Axecta provides accounting and e-invoice readiness for companies across Malaysia. Talk to our team.
In this article
- Why clean data matters
- Customer details
- Product and service coding
- Invoice numbering and document types
- Matching MyInvois documents to your ledger
- Software and integration checklist
- Common data gaps and how to fix them
- How Axecta helps
- Where the specifications live
- A 6-week data clean-up plan
- Who should own what
- Risk checks before go-live
- Frequently asked questions
Why clean data matters
Every e-invoice is checked by MyInvois against required fields. If a customer record has a missing TIN, a wrong registration number or an incomplete address, the document can be rejected or, worse, accepted with wrong information that is difficult to correct. Cleaning the data first is cheaper than correcting submissions later.
Customer details
For each business customer, hold:
- Registered name, exactly as on their SSM record.
- Business registration number or other identity number as the guideline specifies.
- Tax identification number (TIN).
- Full address, state and country.
- SST registration number if they are registered.
- Contact details for sending validated documents.
For individual customers, the data needed is different, and the guideline has specific rules about when an individual’s details are required. Ask customers for TINs now, and check the format. Your accountant or Axecta can help with a bulk request template.
Product and service coding
Need this done for you? Axecta’s accounting and e-invoice readiness team can handle this for your company. See the accounting and e-invoice readiness service.
E-invoices require each line to be described and classified using the codes in the guideline, including tax type and unit of measure. Build a master list:
- Item or service name and a clear description.
- Classification code that fits.
- Unit of measure.
- Tax treatment (for example SST or no tax) and the reason code where needed.
- Default price and currency.
Keep the list under one owner and review it when new products are added.
Invoice numbering and document types
Decide your numbering rules before you start:
- One sequence per document type, with no gaps you cannot explain.
- Separate series for invoices, credit notes, debit notes and refund notes.
- A rule for corrections: when you cancel and re-issue, and when you issue a credit note instead.
- Special cases, such as self-billed invoices, if they apply to you.
Matching MyInvois documents to your ledger
The validated e-invoice is now a record LHDN holds. Your books should agree with it. Set a monthly routine:
- Export the list of validated and cancelled documents from MyInvois or your software.
- Compare it with your sales ledger by number, date, customer and amount.
- Investigate differences and correct them with notes, not overwrites.
- Record the review in the month-end checklist.
This also protects you at year-end when the figures feed into your tax return. See monthly bookkeeping vs annual accounts.
Software and integration checklist
- Does the software support the current LHDN version and sandbox testing?
- Who maintains the connection, and what happens when LHDN updates the specification?
- Can it handle credit notes, cancellations and consolidated submissions?
- Does it store the validated document and QR code?
- Who has access, and is the TIN and credentials management secure?
Common data gaps and how to fix them
| Gap | Fix |
|---|---|
| Customers without TINs | Send a request with a short form; chase before the first submission |
| Free-text item descriptions | Replace with a coded item master |
| Duplicate customers | Merge records and keep the legal name |
| Mixed invoice sequences | Close old series and start clean ones |
| Sales recorded in bulk journals | Move to invoice-level entry |
How Axecta helps
Axecta’s accounting team reviews customer and item records, builds the master lists, helps you select and test a submission route, and sets up the month-end reconciliation. Many clients find that fixing the data also speeds up their audit and tax filing.
Where the specifications live
LHDN publishes the data requirements in the Specific Guideline, and the technical field definitions in the MyInvois SDK. Both are updated, so work from the latest version and record the version number in your project notes. The LHDN FAQs answer common practical questions.
A 6-week data clean-up plan
| Week | Task |
|---|---|
| 1 | Export customer and item lists; identify duplicates and blanks |
| 2 | Request TINs and registration numbers from business customers |
| 3 | Build the item master with classification codes and tax treatment |
| 4 | Set numbering rules and credit-note procedure |
| 5 | Test submissions on a sample of invoices |
| 6 | Reconcile test results to the ledger and fix issues |
Who should own what
- Sales or admin: collects customer details and raises invoices.
- Accounts: owns the item master, reviews rejections and reconciles.
- Director: approves the process and is the contact if LHDN queries arise.
Risk checks before go-live
- Are validated copies stored with the sales record?
- Can you retrieve an e-invoice by number within minutes if asked?
- Does the credit-note process reference the original document?
- Who watches for LHDN updates, and who updates the software?
Axecta builds this checklist into client onboarding for e-invoicing. See also common e-Invoice mistakes made by SMEs.
Frequently asked questions
What information is needed on an e-invoice?
The seller and buyer details, including TINs and registration numbers, the date, a unique document number, item descriptions with classification codes, amounts and tax details. The exact field list is in LHDN’s specification.
What is a TIN and where do I get one?
A tax identification number is issued by LHDN. Companies already have an income tax number that serves as their TIN; confirm the format with LHDN. Individuals should check their own number.
Can accounting software submit e-invoices?
Many packages can connect to MyInvois. Check that your version supports the current LHDN specification and ask the vendor for confirmation. Axecta can help you evaluate options.
How do I handle credit notes?
Issue them as a separate document type that references the original e-invoice, following the guideline. Don’t overwrite or delete the original record.
Where do I find the field list for e-invoices?
In LHDN’s Specific Guideline and the MyInvois SDK documentation.
How long does preparation take?
It depends on the state of your data. A structured plan of around six weeks is realistic for a small business with clean records.
Who should review rejected invoices?
The accounts owner, with escalation to a director for repeated issues.
Need your records cleaned up and e-invoice ready?
Axecta Management Services is a full-suite accounting, company secretarial and consulting firm in Kuala Lumpur, serving companies from SMEs to MNCs.
Request a clean-up and setup quote
Keep reading
- Malaysia e-Invoice Guide for SMEs
- Common e-Invoice Mistakes Made by SMEs
- Monthly Bookkeeping vs Annual Accounts
- What Documents Should You Send Your Accountant Every Month?
- Company Registration Number vs Tax Identification Number (TIN)
- Tax Record-Keeping Requirements in Malaysia
- e-Invoice Implementation and Transitional Relief Explained
- e-Invoice Exemption: Who Qualifies in Malaysia?
- E-Invoicing: the full guide
Official sources to check
This article is general information and not legal, tax or accounting advice for your company. Rates, thresholds, deadlines and procedures change, so confirm current requirements with the sources above or with Axecta.