Malaysia MyInvois: choose self-billing, consolidation and correction routes
MyInvois operating problems often begin with the wrong document family. A foreign supplier's bill is treated like an ordinary domestic supplier invoice, a retail receipt appears in both an individual and a consolidated submission, or a validated invoice is overwritten after an error is found. Correct routing prevents those errors before integration starts.
Use the MyInvois scenario worksheet to record the issuer, parties, source records and correction path. This guide provides an operating method and synthetic examples; applicability still needs an approved assessment of the actual taxpayer and transaction.
Start with the current guidance and exemption conditions
HASiL's current guidance register identifies general guideline 4.8 dated 30 August 2026 and specific guideline 4.9 dated 7 September 2026. The linked current PDFs confirm those versions. Date the decision and keep the actual files used, because older official English PDFs can remain discoverable. HASiL: current guideline register.
General guideline 4.8 sets the exemption below RM 3 million annual revenue/turnover, subject to conditions. It excludes specified cases involving non-individual shareholders, parent companies, related companies or joint ventures meeting the threshold. A small entity therefore needs a relationship assessment as well as its own revenue figure. Its phase also depends on the applicable commencement and measurement rules. HASiL: general guideline 4.8, sections 1.5–1.6.
Have tax approve legal identity, measured revenue, relevant period, related-entity facts, exemption conditions and implementation date. Do not deactivate an existing process simply because the headline threshold changed. Record the authority basis for any change in the taxpayer's obligation and its effective date.
Classify the document before mapping fields
For every scenario, identify the supplier, buyer, party creating the document and legal reason for that issuer. Ordinary supplier issuance and buyer-issued self-billing need different party roles even when the same ERP creates both files.
The MyInvois SDK defines self-billed invoices as buyer-issued and directs users to section 8 of the specific guideline for permitted circumstances. Self-billing is not a universal workaround for a missing supplier invoice or inconvenient data. MyInvois SDK: self-billed invoice.
Build an approved scenario list for ordinary purchases, foreign purchases, agent/distributor payments, employee expenses and other actual business cases. Mark which require separate review. For a self-bill, preserve the supplier's underlying commercial evidence and the reason the buyer is the issuing party. Do not swap supplier and buyer identities merely to satisfy a connector's mandatory fields.
Define what can enter consolidation
Specific guideline 4.9 describes retail/other eligible consolidated workflows, including preparation within seven calendar days after month-end in the ordinary scenario, and categories/conditions that require separate handling. It preserves underlying receipt references. Eligibility must be checked for the actual transaction and any applicable relaxation; "the customer did not ask" is not sufficient for every type of sale. HASiL: specific guideline 4.9, section 3.
Set a source-level disposition for each receipt: individual document, eligible consolidation, excluded/cancelled or investigation. The individual and consolidated paths should reference the same authoritative receipt register so that a transaction cannot enter both by accident.
Store branch/location and receipt identity even when submission is grouped. Reconcile the composition of the consolidated document, not just its final total. A balancing journal is not evidence explaining which receipts were reported.
When a buyer requests an individual document, route the request through the current prescribed procedure and your approved deadline rules. Make the original receipt's disposition visible to the consolidation operator. If the request arrives after consolidation, use the verified adjustment process rather than deleting historical receipt links.
Capture validation time and choose corrections deliberately
The general guideline's rejection/cancellation process uses 72 hours from validation. A buyer's rejection request and the issuer's cancellation are different actions. After that period, adjustment requires the applicable new document, such as a credit, debit or refund note; the guideline also permits adjustment documents instead of using cancellation where appropriate. General guideline 4.8: rejection and cancellation.
Preserve the authority validation timestamp and unique reference. An ERP posting time, the customer's reading time and a failed notification time should not reset the clock. Display the remaining window to the operator and escalate before it expires.
For each error, decide whether the source transaction is wrong, the structured data is wrong or money is actually being refunded. The correcting-document family should express the approved business event. Keep original, cancelled, replacement and adjusting documents linked, with the actual returned statuses.
Work through three connected populations
Assume Contoh Trading is already in scope and has no special relaxation relevant to this test. Tax has separately approved the document classifications. All amounts below are MYR, and tax is omitted to isolate document routing; this does not imply that real supplies are exempt from sales or service tax.
During October, the retail register contains 100 eligible receipts of RM 100, total RM 10,000. Ten buyers receive individual e-Invoices for their receipts, totalling RM 1,000. The remaining 90 receipts, total RM 9,000, form the approved consolidated population. The control expects 100 source receipts to be accounted for once, not a RM 10,000 consolidation plus RM 1,000 individual submissions.
The operator validates the individual documents and submits the eligible consolidation using the approved calendar. Store the list of 90 receipt references and the authority result. The controller reconciles RM 1,000 plus RM 9,000 back to RM 10,000 before accepting completion.
Separately, Contoh buys an approved foreign-service scenario for RM 2,000. Assume tax has confirmed that the current specific-guideline provision requires buyer-issued self-billing and has approved the timing and party identifiers. AP retains the foreign supplier's bill and procurement evidence; the self-billed document records the true supplier and buyer roles. It does not become another retail sale or join the retail consolidation.
Finally, an individually invoiced RM 100 sale needs an approved RM 20 reduction. If an applicable cancellation/replacement route is selected within its window, retain both outcomes and the replacement relationship. In a separate after-window test, issue the appropriate RM 20 adjustment with the original reference. The resulting commercial amount is RM 80. The test should distinguish one original plus one adjustment from an unlinked second sale.
Investigate failures before resubmitting
A submission acknowledgement is not the same as final document validation. Track ready, submitted, invalid/rejected, valid and cancelled states using the actual SDK/provider responses. Preserve the original codes alongside any simplified operational label.
If transmission times out, query the existing identifiers using the supported implementation before creating another document. If validation fails, assign identity errors to master-data owners, scenario errors to tax and schema/transport errors to integration. Retain the corrected relationship rather than overwriting the audit evidence.
For a rejected self-bill, confirm both the selected scenario and party roles before retrying. For a rejected consolidation, investigate receipt composition and duplicates before changing totals. A file that validates after a random default does not demonstrate a correct business record.
Ownership and monthly acceptance
Tax owns scope, eligibility and document choices. AR owns sales and corrections. Retail operations owns receipt completeness. AP owns self-billing evidence. Integration owns payloads, status retrieval and controlled retries. The controller approves population reconciliation and unresolved exceptions.
Reconcile individual, consolidated and self-billed families separately. Then explain their accounting relationship. Counts differ because consolidation groups many receipts; a raw document-count comparison without source composition can mislead.
- ☐ Applicability uses current guideline versions and relationship conditions.
- ☐ Every actual scenario has a reviewed issuer/document-family decision.
- ☐ Self-bills preserve supplier evidence and correct party roles.
- ☐ Receipt disposition prevents individual/consolidated duplication.
- ☐ Validation timestamps control any 72-hour action.
- ☐ Corrections retain originals, references and real outcomes.
- ☐ Timeout and rejection recovery have tested owners.
- ☐ The controller can reconcile source detail to valid reporting populations.
Use master-data readiness for identity cleanup and acceptance tests for the connector demonstration.
Worksheet: MyInvois scenario and reconciliation worksheet
Copy this worksheet for each case. It records decisions and evidence; it does not determine the tax or legal treatment.
Show the worksheet
Use with the Malaysia guide. Repeat scenario blocks; blanks are intended inputs.
Applicability
- Taxpayer, measured revenue, period and supporting statements:
- Shareholder/parent/related-company/JV assessment:
- Applicable guideline editions and approved phase/exemption:
- Reviewer, decision and effective date:
Scenario and document
- Transaction and authoritative source reference:
- True supplier / buyer / issuing party:
- Ordinary / self-billed / individual / consolidated route:
- Current eligibility clause and approved timing:
- Party identity evidence and payload mapping:
- Source receipts/bills and exclusion/duplicate controls:
- Authority reference, validation timestamp and status:
- Cancellation/rejection window and owner, if used:
- Adjustment family, original reference and outcome:
Reconciliation
- Receipt count/value, individual count/value and consolidated composition:
- Self-billing population and underlying supplier evidence:
- Original / cancellation / replacement / adjustment relationships:
- Missing, invalid, unknown-outcome and duplicate exceptions:
- Synthetic expectation: RM 10,000 receipts = RM 1,000 individual + RM 9,000 consolidated:
- Separate RM 2,000 self-bill; RM 100 sale less RM 20 adjustment = RM 80:
- Controller approval, evidence and unresolved conditions:
Sources checked: 17 October 2026. Current general/specific documents were retrieved in Malay. The article deliberately avoids unverified special-scenario deadlines and exhaustive consolidation exclusions; apply the exact current clause to the business's actual scenario before deployment.
Related on this site
- Country pages: key facts with sources
- E-invoicing matrix: country × ERP support
- All guides
Vendor documentation is cited only as an example of the level of evidence to ask for; it is not a recommendation or a ranking. This guide is general information, not tax or legal advice. Checked 2026-10-17.
Related: Glossary – abbreviations and terms used in these guides (SAF-T, Peppol, CTC, EN 16931, IFRS and more).
Page last updated: · Markdown version