MyInvois Phase 2: get your documents ready before the deadline bites.
LHDN’s MyInvois rollout moves in phases. Phase 2 brings more businesses into mandatory e-Invoicing — and the delays we see are almost always missing master data, not software capability. Use this checklist to close gaps before your go-live date.
Updated 2026-07-14
Who is in Phase 2
Phase 2 typically covers businesses above a lower revenue threshold than Phase 1 — check the latest LHDN gazette and MyInvois portal announcements for your exact classification.
If you already invoice with SST, you are likely in scope or will be soon. Treat Phase 2 as a firm deadline, not a “we’ll see” item.
Accountants serving multiple clients should map each book against LHDN phase dates — one late client drags the whole firm’s reputation.
Document checklist: TIN, SST, address
Tax Identification Number (TIN) on every customer and supplier master — validate against LHDN records before first submission.
SST registration number where applicable; confirm whether each product line is taxable, exempt, or zero-rated.
Registered business address, contact details, and invoice numbering sequence that does not collide with legacy Excel runs.
Bank details and payment terms are not always mandatory for MyInvois, but gaps here slow internal approval before you even reach LHDN.
The pipeline: Issue → Validate → Submit → Archive
Issue: raise the invoice in your accounting system with correct tax and customer identifiers.
Validate: run pre-submission checks — TIN format, mandatory fields, SST totals, UUID and timestamp rules per LHDN schema.
Submit: push to MyInvois; handle rejections with a clear retry path, not a manual retype.
Archive: store validated UUID, QR data, and submission receipts alongside the PDF your customer received — auditors will ask for both.
How BukuCloud prepares you
Customer and product masters are the same records your SST invoices use — no duplicate “e-Invoice only” spreadsheet.
MyInvois pipeline status is visible on the e-Invoice page; BukuCloud is building toward full Issue→Validate→Submit→Archive inside the product.
Your accountant can review documents via firm-staff access or Practice console before anything hits LHDN.
CSV export remains available if your firm needs a parallel archive during transition.
Common delays — and how to avoid them
Missing or wrong TIN on B2B customers — fix masters two weeks before go-live, not on submission day.
Invoice numbers that restart mid-year after Excel migration — agree a clean sequence with your accountant.
SST figures that do not match the PDF — usually a sign you are still editing tax in a side workbook.
No named owner for rejections — assign one person (or your firm) to clear MyInvois errors within 24 hours.
Frequently asked
BukuCloud is on the MyInvois preparation path with pipeline stages documented on the e-Invoice page. Use this checklist to get masters and SST clean now so submission is a switch, not a rebuild.
B2B e-Invoices generally require valid TINs. Collect them during onboarding; for B2C, follow the latest LHDN guidance for consolidated or simplified documents.
Yes. Practice console gives firms cross-client visibility and one-click entry into each book — far safer than tracking phase dates in a shared spreadsheet.