Getting Paid and e-Invoice: Connecting Payment to MyInvois
Taking payment and issuing an e-Invoice are two separate obligations, and the join between them is where duplicated work appears. The single decision that saves the most effort is what you capture at checkout — because a buyer's tax details are easy to collect before payment and nearly impossible to collect afterwards.
Payment and invoicing feel like one event to a customer and are two separate obligations to you. Taking the money is a commercial transaction. Issuing an e-Invoice — a structured invoice validated by LHDN in real time through the MyInvois platform — is a tax obligation with its own rules about who, when and in what form. Businesses that treat them separately end up doing the same work twice, chasing customers for details they could have collected at checkout. The good news is that the fix is almost entirely a data capture decision made once, and it costs nothing to implement early.
Where you stand today
The rules, as covered in full in our e-Invoice guide:
- Businesses turning over less than RM1 million a year are currently exempt and may keep issuing normal invoices or receipts, though voluntary adoption is allowed.
- Above that, mandatory phases have rolled out by turnover tier since August 2024.
- Regardless of phase, any single transaction exceeding RM10,000 requires an individual e-Invoice — it cannot be folded into a consolidated one.
- B2C transactions are typically handled through consolidated e-Invoices covering many small transactions over a period, rather than one per receipt.
That third point is the one that catches otherwise-exempt businesses, and it is the reason this matters even if you are below the threshold: an occasional large sale can create an individual e-Invoice obligation on a business that issues none the rest of the year.
The one decision that saves the most work
Decide at checkout whether this sale might need an individual e-Invoice, and capture the buyer's details then.
A buyer's tax identification details are easy to collect while they are completing a purchase and want the goods. They are very hard to collect two weeks later by email. So:
- Add an optional "I need a tax invoice / e-Invoice" checkbox at checkout that reveals fields for business name, registration number and Tax Identification Number.
- Make it mandatory above your threshold. If a single transaction exceeds RM10,000, those details are not optional — collect them before payment completes rather than chasing afterwards.
- Store them against the order, not in a separate list. The point is that the invoice can be issued from the order record without anybody re-typing.
This is a checkout change, not a systems project, and it is the difference between e-Invoice being a background process and being a monthly scramble. Our checkout guide covers making it without hurting conversion — the checkbox stays collapsed for the majority who do not need it.
A workflow that does not duplicate effort
- Customer pays. The gateway confirms and produces a transaction record with a reference.
- Your system records the sale against that reference, including any tax details captured at checkout.
- Decide the route:
- Individual e-Invoice — required for B2B buyers who request it and for any single transaction over RM10,000.
- Consolidated e-Invoice — for the B2C transactions that qualify, batched over the period.
- Submit to MyInvois for validation. LHDN validates and returns a unique identifier and QR code.
- Share the validated e-Invoice with the buyer. The validated version, not your original draft, is the document with legal standing.
- Reconcile the payment record against the invoice record, so nothing is invoiced twice and nothing is missed.
Step 6 is where most manual effort hides. If your payment records and your invoice records live in two systems that do not talk, someone reconciles them by hand every month, forever. That is exactly the kind of money-touching process that should be digitised first — see digital transformation on an SME budget.
Things that trip people up
- The RM10,000 threshold is per transaction, not per customer per month. One large sale triggers it.
- Refunds and cancellations need handling too. A validated e-Invoice cannot simply be deleted — there is a defined process for adjustments. Build the refund case into your workflow rather than discovering it during your first return.
- Payment gateway fees are your expense, not a reduction of the sale value. The invoice reflects what the customer paid, and the fee is booked separately. Netting it off understates revenue and misstates SST if you are registered. See accounting basics and SST.
- Marketplace sales follow the platform's arrangements. Shopee, Lazada and TikTok Shop have their own handling for buyer invoices; do not assume it matches your webstore process. Check with each.
- SST and e-Invoice are separate. Getting the tax treatment right on the invoice is its own job — the SST calculator and the SST guide cover it.
If you are currently exempt
You do not have to do anything. But two things are cheap now and expensive later:
- Capture buyer tax details at checkout anyway. It costs one collapsed checkbox and it means you are never retrofitting a data field into historical orders.
- Keep invoice records structured, not as loose PDFs. Whether the trigger is crossing the threshold, a single large sale, or a B2B customer who requires it, structured records make compliance a configuration change rather than a project.
Frequently asked questions
Does a payment confirmation count as an e-Invoice?
No. A payment receipt confirms money moved. An e-Invoice is a structured document validated by LHDN through MyInvois, and only the validated version has standing for tax purposes. They are different documents produced by different systems.
My gateway sends an email receipt. Is that enough?
For a customer's own records, usually. For e-Invoice compliance, no — see above. Where a provider offers e-Invoice support as a feature, confirm exactly what it does: some produce a compliant invoice, others only produce a receipt that looks like one.
What if a customer asks for an e-Invoice after they have already paid?
You will need their tax details, which is precisely the chase this guide is written to avoid. It is doable but manual, which is why capturing at checkout is worth the small amount of work.
I sell on marketplaces only. Does this apply to me?
Your obligations still exist, but the mechanics depend on each platform's arrangements. Ask each marketplace directly what they issue on your behalf and what remains yours, and do not assume the answer is the same across platforms.
Where do I confirm the current rules?
The official LHDN e-Invoice portal at hasil.gov.my/en/e-invois/. This area has changed more than once since the rollout began — particularly the relaxation-period terms — so check the source rather than any secondary summary, including ours.
Sources: Lembaga Hasil Dalam Negeri Malaysia (LHDN) official e-Invoice guidance (hasil.gov.my/en/e-invois). The phase timeline, the RM1 million exemption threshold, the RM10,000 single-transaction rule and the consolidated e-Invoice mechanism are as set out in our e-Invoice guide, which was fact-checked against LHDN's published position. Relaxation-period terms have changed more than once — verify the current position directly with LHDN before relying on any date. Payment gateway e-Invoice features vary by provider; confirm what yours actually produces.
Work out the sales or service tax to add to an invoice, and the gross total your customer pays.