Airline GST recovery is not one product. It is five — extraction, reconciliation, analytics, accounting, and connectivity. Ship four of them well and the fifth, quietly, loses you the recovery you meant to capture.
SkySuite is all five, engineered as a single pipeline. One data model. One audit trail. One roadmap. Every layer's output is the next layer's input, already shaped to fit.
The invoice that arrives from Air India at 9:42 AM is a reconciled, posted, delivered journal entry by the time your controller logs in the next morning. Four steps have happened in between. You owned every one of them.
Four seconds per invoice. Five layers. One reconciliation.
There is a thing that sounds like a platform but is actually a product, and a thing that sounds like a product but is actually a platform. SkySuite is the second kind. The interface is a handful of pages. Underneath, there are five engines working in sequence on every invoice your travel programme generates.
This page is about the underneath.
Most “reconciliation platforms” are one capability wearing a marketing stretch. An OCR tool calling itself a platform. A dashboard wrapped around somebody else's matching engine. A tax calculator bolted to a spreadsheet importer. Buy any one of them and you still own the integration between the other four — because the real work spans extraction, reconciliation, analytics, accounting, and distribution, and each one of those speaks a different schema to the ones on either side of it.
Get any one layer wrong and the other four don't compound. Get the handoffs wrong and the audit trail breaks every time a quarter closes. Vendors like to talk about their layer. They don't like to talk about the seams between their layer and the ones next door.
Not in the extraction. Not in the matching. Not in the posting. In the thin gap between one of those things and the next, where a schema translation drops a field, a currency rounds, a GSTIN doesn't carry forward, an audit reference stops being traceable.
SkySuite is the bet that the only way to build this right is to build all of it. Not the layers — the seams. That's the part nobody else wants to own, and it's the part that owns the recovery.
Between the invoice arriving and the delivery confirming, five engines did eighteen discrete pieces of work — and each one passed its output to the next as a native structure, not a file. There was no ETL step. No spreadsheet in the middle. No integration broker silently dropping fields. Here's what each layer did.
This is what “one platform” actually means. Not five products sharing a login. One pipeline with no seams.
We could have shipped SkyDoc alone and called it a platform. It would have sold faster. Extraction is the most visible, the most demo-able, the easiest to benchmark. And for a year and a half, there were people, inside and outside the company, who told us that's what we should do.
We didn't. The reason we didn't is the same reason this page exists. The handoff cost is where the money is. Between extraction and reconciliation, between reconciliation and posting, between posting and the client's ERP — every layer you don't own is a seam, and every seam is a place recovery quietly disappears. You can have the most accurate extractor in the industry and still lose half the recoverable credit to a schema translation three steps downstream.
So we built all five. Slowly. Properly. With the same team writing the contracts between the layers as writing the layers themselves. The platform you see today is not five products. It is one thing, shaped like five.
When prospects ask what makes TraCarta different, the answer is not a feature comparison. A feature comparison would look like any other procurement bake-off, and it would end the same way: everyone claims everything, nobody proves anything, the RFP takes six months.
The answer is three properties that only exist when one team owns all five layers. A vendor with one layer cannot deliver them, no matter what the datasheet says. A systems integrator stitching five vendors cannot deliver them either. They are structural, not feature-level.
SkyDoc's extracted record is SkyLedger's input schema. SkyLedger's resolved match is SkyBoard's metric. SkyBoard's recovery figure is AlignIQ's journal-entry amount. No ETL. No reconciliation of the reconciliation. No lossy cast between systems that don't speak the same shape.
Pick any recovered ITC rupee on your P&L. Click back through AlignIQ's posting, SkyBoard's chart, SkyLedger's match verdict, and SkyDoc's extracted invoice. One audit trail, one retention policy, one signature chain. Auditors see provenance. Finance sees lineage.
A new GST ruling, a new airline format, a new GSTR filing schema — encoded once, into SkyDoc's extractor, SkyLedger's rules engine, SkyBoard's metrics, AlignIQ's mappings, and the SkyLink API. On the same release. No five change-windows. No five integration tests.
This is the part that doesn't show up in a demo. It shows up two quarters in, when an auditor asks to trace a single recovered rupee from your P&L back to the airline invoice that started it.
Quarter begins. Airline invoices flow in from every supplier your travel programme books with — some by EDI, some by email attachment, some landing in a TMC aggregator's feed. SkyDoc reads them as they arrive. By day three you've extracted >300,000 line items without a human touching one.
Reconciliation runs continuously, not in batches. By the end of week four, every invoice extracted is matched, variance-quantified, and verdicted. The 94.2% that auto-reconcile flow straight to AlignIQ. The 5.8% with variances sit in an exception queue with their mismatch pre-diagnosed for your finance team.
SkyBoard's recovery figure has been updating in near-real-time the whole quarter — but week eight is usually when leadership starts watching. The number on the dashboard is not a forecast. It is the actual value currently posted to your ledger, updated as AlignIQ writes journal entries. By mid-quarter you already know, to the rupee, what the quarter's recovery is going to be.
Quarter-end — historically the moment when finance teams pull the weekend shift to assemble the ITC package — arrives with the work already done. AlignIQ's entries are sitting in your ERP. Each one is tied back to an invoice, a match, and a dashboard. Your close runs on schedule. The ₹8.4 Cr average recovery is already on your P&L.
Internal audit asks for the evidence file. It is already compiled. Every recovered rupee traces forward to a journal entry and backward to an extracted invoice, with SkyLedger's match verdict and GSTR-2B reference attached. The pack is 0 analyst-hours to produce, because the audit trail is the platform, not an output of it.
The scramble at the end of the quarter isn't improved.
It simply no longer exists.
A 60-minute walkthrough. Your actual invoice sample, run through every layer live. No slideware.
You see SkyDoc read your invoices, SkyLedger match them, SkyBoard chart the recovery, and AlignIQ draft the journal entries. Then we talk about what it would look like in your quarter.