TravelSuite / Integrations / TripStream
Integration · Corporate data

Your data, in.Raw, live, ours to read.

TripStream is the firm's connector into your corporate systems, your tax data on one side, your travel booking data on the other. Live, raw, fed directly into TripBoard. No quarterly spreadsheet exports, no version drift between what your finance team holds and what the firm sees.

Two sides
Tax data · booking data
Live
Real-time, no batch lag
Raw
No transformation in transit
What TripStream carries

Two sides of your corporate data. Both live.

TripStream reads from two parts of your business: the tax side, where your filings and registrations live, and the booking side, where your authoritative travel records live. Both sides feed TripBoard continuously, not once a quarter, not on request.

Tax sidewhat you've filed, what you're registered for
4 streams
Filed GST returnsGSTR-1 · GSTR-2B · GSTR-3B
Live
Source · your tax filing system or GSP
GSTIN masterentities, states, registration status
Live
Source · your tax registry / compliance tool
Tax positions on fileopinions, written positions, prior rulings
Daily
Source · your tax knowledge base
ITC ledgerbalance and movements, by GSTIN
Live
Source · your tax / accounting system
Booking sideyour authoritative record of who travelled and why
4 streams
Booking recordyour internal copy · cost centre, project code
Live
Source · your finance system / booking platform
Expense submissionstied back to bookings, by employee
Live
Source · your expense management tool
Cost-centre & entity mapwhich cost centre rolls up to which entity
Daily
Source · your finance master data
Employee → entity mappingwhich person belongs to which legal entity
Daily
Source · your HRMS
All eight streams land in TripBoard as raw data. No firm-side transformation in transit, no aggregation, no reshaping, the same record your system holds is the record TripBoard sees.
Raw · in transit
Why TripStream and TripConnect both exist

One PNR. Two records of it.

TripConnect reads the TMC's record of a booking. TripStream reads your own record of it. The two often differ in revealing ways, and the firm needs both, not because they overlap, but because each is partial.

Same booking
PNR 7XK3Q9 · BLR → DEL · 14 Apr 2025
two records, one event
TripConnect view · from the TMC
third-party record
PNR7XK3Q9
CarrierAI · Air India
Fare basisYOWIN · Y class corp
Policy codeDOM-Y · in policy
Cost centreENG-BLR-042 · as booked
Approver chain— not visible
Project code— not in TMC
Expense state
TripStream view · from your systems
authoritative record
PNR7XK3Q9
CarrierAI · Air India
Fare basis— not in finance system
Policy code
Cost centreENG-BLR-042 · confirmed
Approver chainBooked: Mehta → approved: VP-Eng
Project codePRJ-2024-IND-NPS
Expense stateE-4218 · approved · paid
Why the firm needs both

Neither record is complete on its own. The TMC knows what was booked and against what policy; your systems know who approved it, what project it serves, and whether the expense ever got paid. The firm reconciles the two so a claim isn't filed against a booking your finance team never authorised, and a real expense isn't missed because the TMC didn't see it.

Where the streams meet

The two streams meet inside TripBoard's analytics surface and inside the audit trail attached to each posted claim. A single PNR resolves to one event; the firm reads both perspectives of it, automatically.

What TripBoard does with it

TripStream is upstream. TripBoard is what you see.

TripStream doesn't do the analysis. It carries the raw data to TripBoard, which is where every number on every chart and every line on every report comes alive. Here is how the eight streams land.

Upstream
TripStream8 streams · raw
Tax · booking · masters · expense. Carried, not transformed.
01
Analytics surface

Tax filings drive the recovery vs. leakage trend chart. Booking data drives the carrier, state, and cost-centre breakouts. The numbers are live because TripStream is live.

TripBoard · charts
02
Reconciliation cross-checks

SkyLedger and StayLedger query TripStream's data on the fly, the GSTIN you filed under, the cost centre the booking was assigned to, the expense that did or didn't get paid.

TripBoard · recon panes
03
Audit trail anchors

Every posted claim is anchored to the booking record, expense submission, and tax filing TripStream carried at the time. Five layers deep, five years retained.

TripBoard · trail
04
Recon reports & bundles

When the firm hands over a reconciliation package, the supporting evidence includes the TripStream-sourced master records that were current at the time of each claimed line.

TripBoard · delivery
The discipline
TripStream doesn't aggregate, transform, or pre-interpret. What your systems hold is what TripBoard sees. Every claim, every chart, and every reconciliation report carries a timestamp linking back to the exact record TripStream carried at that moment.
The engine comes with the engagement

See what your data looks like in TripBoard.

During the diagnostic, the firm wires TripStream up to a sample of your tax and booking data and shows you how TripBoard reads it. No production access, no live writes, a read-only working session.