High-volume daily transactions, every receipt on the right side of LHDN.
Retail in Malaysia is high-volume, multi-location, and POS-first. MyInvois Bridge meets retail teams where the day actually happens — the POS export, the daily close, the returns and refunds. Whether you run a single store or fifty, the bridge handles the LHDN side without changing how your floor staff issue receipts.
Three operational pressures every Malaysian retailer feels.
- 01
POS doesn't speak MyInvois natively
Your POS issues thousands of receipts a day. None of them carry LHDN's MSIC, tax classification, or structured tax category. The bridge consolidates the POS export into MyInvois submissions without touching the till workflow.
- 02
Returns and refunds happen daily
Every retail business runs returns. LHDN distinguishes credit notes (reducing balance) from refund notes (money physically returned). The bridge wires both into the same workflow as the original invoice with the parent UUID enforced automatically.
- 03
Multi-location adds complexity
If you run multiple stores under separate entity TINs, each one needs its own LHDN onBehalfOf scoping. Multi-company tenancy in the bridge isolates each store at the query level — submissions never cross.
Three patterns retail teams settle into.
Daily POS export + bulk upload
End-of-day POS export becomes a single CSV upload. The bridge validates every row, surfaces flagged transactions, submits the rest. Your manager closes the till and moves on.
Per-location scoping
Each store sits as its own company under your account, with its own audit trail. Group-level reporting rolls up; floor-level submissions stay isolated.
Returns + refunds with parent linking
When a customer returns a product, your POS already knows the original receipt. The bridge picks up the parent UUID from the catalog and files the credit or refund note automatically — no manual reconciliation.
Last updated · May 2026
Independent reference. MyInvois is operated by LHDN. We are not affiliated with LHDN.