Bookings, in.Spreadsheets, out.
TripConnect is the firm's TMC handshake. Direct ingest from your travel management company's booking system, the booking record reaches us before the traveller has landed. No manual exports, no spreadsheets in transit, no version mismatches.
Before the invoice exists. That is the point.
Most travel-GST recovery work happens months after the booking, on invoices that are already wrong. TripConnect intervenes earlier, at the booking moment itself, so problems are caught before they become invoices. Here is the booking moment captured as it unfolds inside TravelSuite.
Traveller or admin completes the booking in the TMC console. PNR is generated; the booking record is now live in the TMC's system.
The booking arrives via the TMC's webhook or push API. Acknowledged, persisted, indexed by PNR.
The booking's cost centre and policy code are matched against your entity map to identify the correct buying GSTIN.
Fare class, cabin, route, and corporate policy verified. Out-of-policy bookings flagged for finance, not blocked.
The booking is queued in SkyDoc's pre-stage. When the carrier invoice arrives days later, it will match to this record in milliseconds.
Wrong entity at booking · wrong GSTIN on the invoice.
In multi-entity groups, this is the most common silent ITC leak. The booking is made against a default entity, the carrier raises the invoice against that GSTIN, and your tax desk can't claim the credit. TripConnect intercepts at booking.
Three categories. Different connections, honest about which.
India corporate travel runs through a small set of TMCs. Each has its own booking system, its own integration surface, and its own readiness to talk to a third party. Here is where the firm actually stands across the three categories.
See if your TMC is integration-ready.
During the diagnostic, we check whether TripConnect can be enabled for your specific TMC and what the integration window looks like.