Malaysian Requirements
Three Malaysian obligations touch almost every business using BigLedger: SST, LHDN e-Invoice (MyInvois) and — for those trading with organisations that use it — Peppol. This page is what BigLedger does for each, and what stays yours.
SST
Q: What does BigLedger do about SST?
Two separate things, and the split matters.
Tax is calculated on the document, from the tax code attached to each line. Tax codes and their rates live in the Tax Configuration applet, and each item carries the input and output codes it should use. Get the code on the item right and every document that item appears on is right.
The return is produced by the MY-SST applet, which does four things: maintains your tax years and filing cycles, maintains tariff codes and tax codes, files posted documents — copying their taxed lines into a frozen snapshot — and reports, including the SST-02 itself, computed entirely from that snapshot.
Q: So the SST applet calculates my tax?
No, and this is the most useful thing on this page. It does not calculate tax on a transaction at all. It decides which already-taxed lines land in which return. If a document’s tax is wrong, the fault is in the tax code on the line or on the item — fixing it in the SST applet is not possible.
Q: What is mine to do?
Registering, deciding which of your supplies are taxable, setting the right tax code on each item, filing on time, and paying. BigLedger produces the return from what you have recorded; it does not decide what should have been recorded.
LHDN e-Invoice (MyInvois)
Q: Does BigLedger submit e-invoices to LHDN?
Yes. The e-Invoice applets carry the posting queue, the holding pools, submission, validation, consolidation, cancellation and correction, and incoming supplier documents. See the e-invoice guides.
Q: Do I have to comply, and from when?
The rollout is phased by annual turnover. The current phase table is in the Malaysia e-Invoice guide — and confirm your own date against LHDN’s current guideline before you plan around it, because the phases have moved.
Q: What is the single most common reason an e-invoice is rejected?
Buyer details, and then item classification. LHDN’s schema defines a large set of fields, most of them mandatory, and a bad field on your company record fails every document at once.
The item side is the one you control at setup: every item carries an item classification, a taxable type and an e-Invoice UOM on its E-Invoice tab. There is no working tenant default behind them — the settings that look like one were disconnected in November 2025 and are read by nothing, in the backend or the applet — so a blank classification is submitted as 022 Others and a blank unit as H87 piece, quietly. Fill these in when you create an item; see maintaining the item master. The taxable type is the exception: it is overruled at submission by the line’s tax amount in almost every case, so it is the rate on the line, not this field, that decides what LHDN is told.
For the real rejection messages and what each one means, e-invoice validation.
Q: I run a shop with hundreds of small cash sales a day. Do I e-invoice each one?
There is a consolidated mechanism for exactly this case, and BigLedger supports it. The rules about who may consolidate and what must be excluded are LHDN’s; the guide covers how it works in the product.
Peppol
Q: What is Peppol and do I need it?
A network for exchanging business documents with organisations that use it. You need it if your customers or suppliers do. BigLedger has an access point and the routing configuration behind it — see the Peppol configuration guide and e-Invoice and Peppol.
Other Malaysian things
Q: Is the chart of accounts Malaysian?
The applet is neutral; what you build in it is yours. The chart of accounts setup guide walks through a structure that produces financial statements in the shapes Malaysian accountants expect.
Q: Malay-language interface?
This documentation is published in English, Chinese, Malay and Arabic. What language the product interface offers depends on your tenant’s configuration — ask your BigLedger contact.
Q: What about PDPA?
Your business is the data user, and the policy side — purpose, consent, retention, breach handling — stays with you. What BigLedger supplies are the technical controls: role-based access, separation of view from edit from export, scoping by company and branch, multi-factor login, and a change audit trail. See teams and permissions, which sets those up.
What success looks like
Three checks before your first filing period closes:
- Open one item and confirm its tax codes and its E-Invoice tab are filled in with something specific — not the tenant default.
- Raise and finalise one document, then check it appears in the e-Invoice posting queue and goes through validation.
- Run file for a period in the MY-SST applet and look at the SST-02 it produces. If the numbers surprise you, the fault is in the tax codes on the documents, not in the return.
Common mistakes
| What goes wrong | The fix |
|---|---|
| Expecting the SST applet to fix wrong tax | It only files what was already taxed — fix the tax code on the item or the line |
| Leaving the item E-Invoice tab on tenant defaults | Set classification, taxable type and UOM at item creation |
| A bad field on the company record | It fails every submission at once — check the company record first when everything is failing |
| Planning against a phase date read on a wiki | Confirm it with LHDN; the phases have been adjusted |
| Assuming BigLedger’s compliance is your compliance | The software records and submits; registering, classifying and filing remain yours |