01 — Two identifiers, one of them books
TIN, not BRN
A Malaysian party usually carries both: the TIN issued by LHDN and the BRN from SSM. They look equally official, and a reader that takes whichever comes first will fill the column with company registration numbers on some invoices and tax numbers on others — which quietly breaks matching between batches.
The TIN wins here, and the BRN is the fallback when there is no TIN. What is never taken is anything with a different scheme: a GLN written into the tax column is worse than a blank, because it looks like a number.
02 — The column that silently empties
Description, not Name
EN 16931 puts the line name in Item/Name; MyInvois uses
Item/Description. Read by the letter of the European standard, every
Malaysian invoice comes out with an empty item column — no error, nothing
highlighted, just a blank you may not notice until someone asks what was bought.
What is read
Invoice number and date, both parties with their names and TINs, currency, taxable amount, SST by rate, and the total. Credit and debit notes come through as their own document types, and a ZIP of a whole month can be dropped as one file.
What is not done here
Nothing is submitted to LHDN, no UUID is requested and no digital signature is verified: the file is read inside the browser and stays there. This is not a MyInvois intermediary — it reads the documents you receive.
The visual PDF with only a validation QR on it is a different problem. If a file carries no structured data, the row comes out empty and marked, never invented.
Trying it
Drop files on the main page — up to 10 invoices per export and 20 a day, free, no account, and the count resets at midnight. Pro lifts both limits for 29 € once, with no renewal.
Nothing is uploaded
Files are read in the browser. There is no server they could go to, and it takes two minutes to check: open developer tools, the Network tab, and drop an invoice — not one request goes out. Which countries are read.