Turn marketplace complexity into one traceable LHDN flow.
Online sellers and platforms sit between orders, payouts, fees, and logistics. MyInvoisBridge gives your team a clear place to validate and track the e-Invoice path without pretending every marketplace has the same data export.
The e-commerce and marketplace sellers reality
- 01
Marketplace data is not your ledger
Orders, cancellations, seller payouts, and platform charges arrive as separate commercial events.
- 02
Platform relationships can invert who issues
LHDN's e-commerce guidance includes cases where a platform issues a self-billed e-Invoice to a seller or related party.
- 03
Logistics can complete the transaction trail
The commercial flow can involve seller, platform, buyer, and logistics data that must remain explainable.
A practical MyInvois path for e-commerce and marketplace sellers
Model the platform boundary clearly
Keep the marketplace as the source of transaction data while MyInvoisBridge handles the LHDN-ready submission boundary.
Support self-billed flows where they apply
Use the supported document types and party relationship instead of forcing a normal supplier invoice onto a platform scenario.
Handle source differences through an adapter
The REST API gives software teams a stable destination while each marketplace mapping remains explicit.
A clearer workflow for e-commerce and marketplace sellers
- 01Collect orders, payouts, and platform context
- 02Map the relevant party and document type
- 03Submit to LHDN and follow the result
Questions from e-commerce and marketplace sellers teams
LHDN rules and implementation dates can change. Check the latest HASiL guidance for your business before relying on a sector-specific example.
Continue with the workflow that fits.
LHDN rules and implementation dates can change. Check the latest HASiL guidance for your business before relying on a sector-specific example.