Overview
Redbus is India's largest online bus ticketing platform, launched in 2006 and operating under MakeMyTrip. Its footprint reaches India, Indonesia, Singapore, Malaysia, Colombia, and Peru. In Malaysia, Redbus runs a high-volume B2B operation powered by a custom-built, in-house billing engine.
That architecture is exactly what made LHDN compliance hard. Unlike companies on standard ERPs, Redbus could not simply plug in a ready-made connector. Every field and schema had to align with LHDN's structure, invoices had to submit in real time, and the platform was already handling multi-party settlements and dynamic tax rules. Any solution had to respect an engineering-first, API-native way of building.
The Challenge
Redbus had always relied on its own custom billing engine, designed long before e-invoicing became mandatory. There was no off-the-shelf connector to install. Every field and schema had to map to LHDN's structure, submission had to happen in real time, and the platform had to keep handling multi-party settlements and dynamic tax rules while it did.
The Solution
API-ready middleware. Complyance plugged directly into the Redbus billing engine through simple REST APIs, transforming every internal invoice into an LHDN-ready JSON file.
A purpose-built adapter layer. A lightweight adapter translated tax details, mapped buyer and seller TRNs, and applied the correct document classification, so Redbus did not have to reshape its data model.
A validation and monitoring engine. Automatic pre-submission checks, a full reconciliation dashboard, and asynchronous webhooks pushed real-time status updates back into the platform.
Deployment with zero disruption. No changes were required to existing billing code.
The Impact
Redbus completed data mapping in about 10 minutes, cut developer effort by 85% for each new country rollout, and reduced engineering time spent on schema changes by 98%. The billing engine stayed exactly as it was, with LHDN compliance handled entirely through the API layer.
