AWRA OpsHub Search

For Malaysia

Your turnover says you are exempt. Your shareholder register may disagree.

Every vendor in this market is currently selling you a countdown. We are not going to, because we have no MyInvois connection and a countdown from someone who cannot submit anything is just noise. The genuinely difficult question in Malaysia right now is not when the mandate arrives — it is whether it applies to you, and that turns out to have three separate tests. One is your revenue, which moved twice. One is your group structure, which nobody thinks of as a tax fact. And one is your customers, who need your data in a specific shape whether you are in scope or not.

MyInvois
No connection, no submission, no validated document returned. Buy that from somebody who has it. This page is about the records underneath it.
SST
Two taxes, not one. Sales tax on goods and service tax on services, at different rates and bands. We compute neither — a single "SST" field would be wrong anyway.
Payroll
No EPF, SOCSO, EIS or monthly tax deduction. Our maintained payroll engine covers Kenya only.
Support
Nairobi, remote, in English. Five hours behind you, with no local partner — weigh that against a competent local bench rather than dismissing it.

Not when — whether

Three tests, three answers, and only the first one is about you

Most businesses run the first test, get an answer, and stop. The other two are the ones that produce the surprises, and they produce them late — usually when a customer's accounts payable team asks for something nobody has been keeping. Positions and dates in this area have moved more than once; confirm your own with LHDN or your tax adviser rather than with any vendor page, including this one.

  1. Test one

    Your own turnover, which has moved twice

    The rollout has been phased by annual turnover, largest first, and the exemption floor was then raised to one million ringgit for 2026 — which cancelled a planned phase outright and moved a substantial number of businesses out of scope after they had already bought something. If you prepared against the old floor, you may have bought a solution to a problem you no longer have. That is worth checking before you renew it.

  2. Test two

    Your group, which is not a revenue question at all

    A business below the floor that is a subsidiary or related company of a business above it does not keep the exemption. This is the test that catches people, because it is decided by ownership rather than by trading, and because the person running the small entity has no particular reason to be watching the large one's turnover. If you are part of a group of any size, the answer to test one is not your answer.

  3. Test three

    Your customers, regardless of your own position

    A counterparty who is in scope has to produce a validated document that identifies you correctly, and in some transaction types has to issue one on your behalf. That means your identifiers, your registration details and your addresses have to be right in their system — so the mandate reaches your records through your customer even where it never reaches your obligations directly. Businesses genuinely out of scope still feel this, and they feel it as an accounts-receivable problem rather than a tax one.

Where we fit: we do not submit anything to MyInvois. No portal connection, no API submission, no validated document returned, no cancellation inside the rejection window. That belongs to a Malaysian compliance provider or to whichever accounting system you already file from, and there are good ones. What this page is about is the layer underneath — the operational records the document is made from, and the counterparty data it has to carry, which is the subject of the next block.

Five questions worth asking inside your own business, before you ask any vendor

  1. Which of the three tests above have you actually run, and when — before or after the exemption floor moved?
  2. If you are part of a group, does anybody in your entity know the parent's turnover position well enough to answer test two?
  3. Has a customer asked you for identifying data in the last six months that you had to go and find rather than look up?
  4. If you bought a compliance tool against the old threshold and are now out of scope, is that a renewal you are still paying?
  5. Who in your business would notice if a customer started rejecting documents because your details were wrong in their master data?

What this costs today

Four problems that a submission tool does not solve

Each of these decides the quality of what gets submitted, and each is settled long before anything reaches a portal.

Counterparty details in three places and none of them current

The registration number is in the accounting system, the address is on the delivery note, and the person who knows which is right left last year. It cost nothing for two decades and now it decides whether a document is accepted.

Two taxes treated as one

Sales tax on goods and service tax on services are different taxes with different rates, different registration positions and different scopes — and the service tax scope expanded significantly, catching businesses that had never registered for anything. A single tax field that says "SST" cannot represent that correctly.

Disputes that used to be a phone call

A short window to reject or cancel a validated document means a quantity disagreement discovered a week later is now a credit note and a reconciliation rather than a reissued invoice. The fix is upstream, at the point the goods were received.

Landed cost absorbed into overhead

Freight, forwarding, duty and handling arrive weeks after the goods on separate invoices. Once they settle into an overhead line, the unit cost behind your pricing is wrong in a way that never appears as an error.

The half we are actually good at

The fields nobody owned until they became compliance fields

A structured document is validated against what it contains, not against what it means. That turns a set of fields most businesses have treated as optional for twenty years into fields that decide whether a document is accepted — and almost all of them describe somebody else. Here is what changes when counterparty data stops being a convenience and starts being a dependency.

Identifiers you do not control 01

What changes

What happens: a document needs the counterparty's tax identification number, business registration number and, where relevant, their indirect-tax registration. None of that is yours. It changes without telling you, it is often held in three places in your business with three different values, and the newest one is usually in somebody's email.

What helps

What helps: one customer and supplier record per party, with the identifiers on the record rather than on a document, and a report of who is missing which field. Not clever. It is simply the difference between finding out now and finding out from a rejection.

Classification that used to be cosmetic 02

What changes

What happens: activity codes, item classifications and unit-of-measure codes that were free text for as long as anyone can remember now have to be values from a list. Free text that reads perfectly to a human fails a schema without ambiguity.

What helps

What helps: coded values held on the item and the party rather than typed per transaction, so the same product is classified the same way every time regardless of who raised the document.

A short window to disagree 03

What changes

What happens: once a document is validated there is a limited window in which either side can reject or cancel it, after which the correction is a credit note rather than an undo. Disputes that used to be settled by a phone call and a reissue now have a clock on them.

What helps

What helps: catching the disagreement before the document exists. A receipt matched against the order and the delivery, with the variance visible at the goods-in door, is a dispute that never becomes an invoice at all.

Self-billed documents about you 04

What changes

What happens: in certain transaction types the buyer raises the document, which means a document describing your sale is created in somebody else's system from data they hold about you. If that data is stale, the error is yours to reconcile and theirs to have made.

What helps

What helps: knowing which of your counterparties self-bill and reconciling what they raised against what you delivered. This is an ordinary matching problem that most businesses only discover they have after the first mismatch.

Why this lands harder in Malaysia than in the other markets we write about

Not because Malaysian record-keeping is worse. Because the transition is happening now, at scale, in a business culture with a great many small suppliers attached to a small number of very large buyers.

  • The large buyers went first, so they are already validating strictly while their suppliers are not yet in scope.
  • That asymmetry pushes the data-cleanliness cost down the supply chain to the party with the least capacity to absorb it.
  • The exemption floor moving reduced the number of businesses obliged to fix their data without reducing the number asked to.
  • Group structures are common, so test two catches more businesses here than a turnover distribution would suggest.
  • And the consequence of bad data is a rejected document rather than a warning, which converts a data problem directly into a receivable problem.

The reason this belongs on a software page: every row above is prevented by a single well-kept record per counterparty and per item, which is a thing almost every business believes it already has. The gap is rarely a decision not to keep the data. It is that the data lives in three systems and the current version is in a mailbox.

Scope, stated plainly

The first thing we do not do is the thing this market is shopping for

Read that item rather than past it. If a MyInvois connection is the requirement, buy it from somebody who has one — that is a recommendation, not a hedge.

Scope in Malaysia, stated before the demo

Running in the product today

  • One record per counterparty, with identifiers, registration numbers and addresses held on the party, plus completeness reporting so gaps are visible before somebody else finds them.
  • Coded items and units of measure, so classification is a property of the product rather than a decision taken per document.
  • Three-way matching between order, receipt and invoice, with variances surfaced at the point of receipt.
  • Multi-location stock with governed transfers, in-transit visibility and blind counts with valued variance.
  • Landed cost on the consignment, so freight, duty and handling reach the unit cost instead of an overhead line.
  • The ringgit as a base currency preset, with foreign-currency purchases held in their own currency at the rate actually applied.

Not built

  • No MyInvois connection. No portal or API submission, no validated document or QR returned, no tracking of the rejection and cancellation window, no consolidated document assembly, no self-billed document generation. This is the thing the market is currently buying and it is not ours.
  • No SST computation or filing. We do not determine whether a supply is taxable, apply the right band, or produce a return. Sales tax and service tax are two different taxes with a scope that has recently expanded, and getting that right is a Malaysian adviser's job.
  • No Malaysian statutory payroll. No EPF, no SOCSO, no EIS, no monthly tax deduction. Our maintained payroll engine covers Kenya only.
  • No Bahasa Malaysia interface. English only, documents included. Commercial and finance floors here are typically comfortable in English; a warehouse team is a separate test and worth running properly.
  • No customs or port integration. Clearance paperwork is attached to the consignment as evidence, not exchanged as data.
  • No local implementation partner. Onboarding is remote from Nairobi, against a market with a competent local bench that can be on site. That is a genuine disadvantage rather than a footnote.

The first item on that list is the one the market is shopping for this year, so read it carefully rather than past it. If a MyInvois connection is what you need, buy it from somebody who has one — that is a real recommendation, not a hedge. The argument for us is orthogonal: whatever files your documents can only be as good as the records it reads from, and those records are stock, receipts, orders and counterparty data. That is the layer we build.

How this starts

Three moves, and none of them is a demo

01

Run all three scope tests, not just the first

Your turnover against the current floor, your group position, and what your largest customers already require of you. The second one takes a phone call to whoever holds the shareholder register and it is the test most often skipped. Confirm the current thresholds and dates with LHDN or your tax adviser — they have moved, and they may move again.

02

Audit your counterparty records before somebody else does

Take your twenty largest customers and twenty largest suppliers and check whether you hold a complete, current set of identifiers for each. Not whether the data exists somewhere — whether one person can produce it in one place in five minutes. This is an afternoon of work and it is the cheapest thing on this page.

03

Then fix the upstream, not the document

Most rejected documents are not invoicing failures. They are receiving failures, master-data failures and pricing failures that became visible at the moment a schema looked at them. Whatever you buy to submit documents, the quality of what it submits is decided before it ever runs.

Questions we are asked here

Answered in full, including the ones that lose us the deal

Do you submit to MyInvois?

No. There is no portal connection, no API submission, no validated document or QR returned onto an invoice, no tracking of the rejection window, and no self-billed document generation. Given that MyInvois is what most of this market is buying right now, we would rather put that in the first answer than let a feature list imply otherwise. Buy submission from a Malaysian provider or use whichever accounting system you already file from. What we build is the operational record underneath it.

Are we in scope if our turnover is below the exemption floor?

Possibly, for two reasons that have nothing to do with your revenue. First, a business below the floor that is a subsidiary or related company of one above it is generally brought back into scope — that is decided by ownership, not by trading. Second, even a business genuinely outside the mandate is affected through its counterparties, who need correct identifying data about you in order to issue valid documents naming you, and who in some transaction types will raise documents on your behalf. Thresholds and dates in this area have already changed more than once, so confirm your specific position with LHDN or your tax adviser rather than with any vendor.

What is the SST rate?

There is no single answer, and treating it as one field is a common and expensive modelling error. SST is two taxes: sales tax on goods, charged at five or ten per cent depending on the goods, and service tax on taxable services, which rose from six to eight per cent on 1 March 2024 with a named list of services remaining at six. The scope of service tax also expanded substantially in 2025 to reach areas including leasing, construction and financial services, which brought in businesses that had never registered for anything. Our country profile carries eight per cent as the standard service tax rate; what applies to you is a question for a Malaysian adviser.

Why does counterparty data suddenly matter so much?

Because a structured document is validated against what it contains rather than what it means. A registration number that is one digit out, an address that has not been updated since a move, an activity code that was free text — all of these read perfectly to a person and fail a schema. The awkward part is that most of the fields describe somebody else, so they change without telling you and they are usually held in several places in your business with several different values. Keeping one record per party, with the identifiers on the record, is unglamorous and it is most of the fix.

We already bought a compliance tool. Do we need anything else?

Quite possibly not, and it is worth asking the opposite question first: if you bought against the old exemption floor and the floor has since moved, check whether you are still in scope before you renew. Assuming you are, a submission tool solves submission. It does not decide whether the quantity on the document matches what was delivered, whether the price matches what was agreed, or whether the counterparty record is current. Those are upstream questions and they determine what your compliance tool is submitting.

Is there a Bahasa Malaysia interface?

No. The interface and all documents are English only. In our experience Malaysian commercial and finance teams are comfortable working in English and this is rarely the blocker it would be in Jakarta or Bangkok — but a warehouse or production floor is a genuinely different test, and it is one you should run with the people who would actually be keying transactions rather than with the people evaluating the software. If it fails that test, it fails, and we would rather you found out in week one.

Where does support come from, and what about the time difference?

Nairobi, remote, in English. Malaysia is UTC+8 and Nairobi is UTC+3, a five-hour difference — your afternoon is our morning, which is a workable overlap but a real constraint if you need somebody at eight in the morning your time. There is no local office and no partner who can be on site, which against a market with a competent local bench is a disadvantage worth weighing rather than dismissing. The working week and public holidays are configured rather than assumed.

Run the second scope test

Not the turnover one — the group one. Find out whether anybody above you in the shareholder register is over the threshold, because that decides your position and almost nobody checks it. It takes one phone call and it is free.