Dine-in, takeaway, delivery: every channel submits to LHDN.
F&B in Malaysia is multi-channel by default: dine-in, takeaway, delivery aggregator (GrabFood, Foodpanda, ShopeeFood), QR ordering, and walk-in retail. Each channel emits a different receipt format. The bridge consolidates them into a single MyInvois pipeline so the LHDN side stays simple no matter how many channels you run.
Three structural pressures unique to Malaysian F&B.
- 01
Aggregator payouts need self-billed
When GrabFood or Foodpanda pays you out, the aggregator is effectively the buyer: they should be issuing a self-billed invoice (type 11). Most aggregators ignore this. The bridge lets you issue the self-billed invoice yourself, with the aggregator as the customer party.
- 02
Mixed-channel daily close
End-of-day sources often expose different formats. A developer can normalize them and submit through the live REST API today; direct multi-source CSV import is coming soon.
- 03
Service charge and SST need structured handling
F&B receipts carry 6% service charge plus 8% SST plus discounts. LHDN wants each component structured. The bridge maps your POS's tax + service columns to the right LHDN tax category fields automatically.
Three F&B-specific patterns.
Per-channel CSV mappings (coming soon)
Reusable per-channel CSV mappings are coming soon. Today, normalize channel data in your adapter and submit through the REST API.
Self-billed for aggregator payouts
Issue type-11 self-billed invoices on aggregator payouts: the bridge handles the party flip, the supplier MSIC code, the audit trail. Closes the LHDN side of the aggregator relationship cleanly.
Daily bulk submission with structured rejection surfacing
Daily CSV batch import is coming soon. Today, submit idempotent JSON requests through the REST API and review validation results in the dashboard.
Last updated · July 2026
Independent reference. MyInvois is operated by LHDN. We are not affiliated with LHDN.